WO2022028604A1 - 上行传输方法、装置及终端设备 - Google Patents

上行传输方法、装置及终端设备 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
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.)
Ceased
Application number
PCT/CN2021/111299
Other languages
English (en)
French (fr)
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
Publication of WO2022028604A1 publication Critical patent/WO2022028604A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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 signalling, 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

本申请公开了一种上行传输方法、装置及网络设备，属于通信技术领域。该方法包括：在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在MAC层按照以下任一项处理方式，生成MAC PDU：如果MAC层获知上述上行共享信道的时域资源与上述上行控制信道的时域资源重叠，则生成MAC PDU；根据物理层通知给MAC层的复用信息，生成MAC PDU；其中，上述至少一个上行控制信道上承载有至少一个上行控制信息。

Description

上行传输方法、装置及终端设备
相关申请的交叉引用
本申请主张在2020年8月7日在中国提交的中国专利申请号No.202010790993.2的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种上行传输方法、装置及终端设备。
背景技术
当终端设备的上行共享信道(如，物理上行共享信道(Physical Uplink Shared Channel，PUSCH))为配置授权的信道、且终端设备的数据存储器中没有需要传输的数据时，终端也可以忽略配置授权(configured grant)PUSCH，不进行上行传输。
在相关技术中，当终端设备的上行共享信道(如，物理上行共享信道(Physical Uplink Shared Channel，PUSCH))为配置授权的信道，如果上行控制信道(如，物理上行控制信道(Physical Uplink Control Channel，PUCCH))的时域资源和动态调度的上行共享信道的时域资源有资源冲突，由于PUSCH可能没有数据要发送，媒体接入控制(Medium Access Control，MAC)层基于是否有数据生成协议数据单元(Protocol Data Unit，PDU)，无法根据是否有上行控制信息(Uplink Control Information，UCI)要复用来生成PDU。
发明内容
本申请实施例的目的是提供一种上行传输方法、装置及终端设备，以实现MAC层可以基于是否有UCI要复用来生成PDU。
第一方面，提供了一种上行传输方法，应用于终端设备，上述方法包括：
在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在媒体访问控制MAC层按照以下任一项处 理方式，生成MAC协议数据单元PDU：
如果MAC层获知所述上行共享信道的时域资源与所述上行控制信道的时域资源重叠，则生成MAC PDU；
根据物理层通知给MAC层的复用信息，生成MAC PDU；
其中，所述至少一个上行控制信道用于承载上行控制信息。
第二方面，提供了一种上行传输装置，上述装置包括：执行模块，用于在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在媒体访问控制MAC层按照以下任一项处理方式，生成MAC协议数据单元PDU：
如果MAC层获知所述上行共享信道的时域资源与所述上行控制信道的时域资源重叠，则生成MAC PDU；
根据物理层通知给MAC层的复用信息，生成MAC PDU；
其中，所述至少一个上行控制信道用于承载上行控制信息。
第三方面，提供了一种终端设备，该终端设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第四方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤。
第五方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如第一方面所述的方法。
第六方面，提供了一种程序产品，所述程序产品被存储在非易失的存储介质中，所述程序产品被配置成被至少一个处理器执行以实现上述第一方面所述的方法。
第七方面，提供了一种终端设备，所述终端设备被配置成用于执行如第一方面所述的方法。
在本申请实施例中，在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在媒体访问控制MAC层按照以下任一项处理方式，生成MAC协议数据单元PDU：方式1，如果 MAC层获知所述上行共享信道的时域资源与所述上行控制信道的时域资源重叠，则生成MAC PDU；方式2，根据物理层通知给MAC层的复用信息，生成MAC PDU；其中，所述至少一个上行控制信道用于承载上行控制信息，如此，在上行共享信道与上行控制信道冲突的情况下，可以通过MAC层生成MAC PDU，使得终端设备即使在没有数据传输的情况下，还可以支持将该上行控制信道上承载的上行控制信息可以复用到配置授权的上行共享信道上，进而使得网络侧设备无需进行盲检测便可准确的确定出上行控制信道复用的资源，降低了网络侧盲检测的复杂度，提高了系统通信能效。
附图说明
图1是本申请实施例提供的一种通信系统的系统架构图；
图2是本申请实施例提供的一种上行传输方法的方法流程图；
图3是本申请实施例提供的一种上行传输装置的结构示意图；
图4是本申请实施例提供的一种终端设备的结构示意图；
图5是本申请实施例提供的一种终端设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
以下将对本申请实施例提供的技术方案所涉及的技术术语进行解释说明：
1、传输资源时域重叠(或称为时域冲突)
与以往的移动通信系统相比，第五代(5 th Generation，5G)移动通信系统需要适应更加多样化的场景和业务需求。5G的主要场景包括增强的移动宽带(Enhanced Mobile Broad Band，eMBB)、大规模机器类通信(massive Machine Type Communications，mMTC)和超可靠的低延迟通信(Ultra-Reliable and Low Latency Communications，URLLC)，这些场景对移动通信系统提出 了高可靠，低时延，大带宽，广覆盖等要求。UE可以支持不同的业务，例如UE既支持低时延高可靠的URLLC业务，又可以支持大容量高速率的eMBB业务。新无线技术(New Radio，NR)系统由于不同的信道可以具有不同的起始符号和长度，因此会出现传输资源时域重叠的情况。通常，为了维持上行单载波特性，当一个时隙有多个重叠的上行传输资源进行传输时，会破坏UE的单载波特性，并且发射功率的不同会引起信道估计性能的恶化。对于这种情况通常被视为一种冲突，需要设计相应的冲突解决方案，合并或丢弃一些信息。
2、上行信道
上行控制信道包括：物理上行控制信道(physical uplink control channel，PUCCH)。
上行共享信道包括：物理上行共享信道(physical uplink shared channel，PUSCH)。
3、物理层定义的UCI复用在PUSCH上
上行控制信息(如，UCI)通常在上行控制信道(如，PUCCH)上传输。若终端设备正在上行共享信道(如，PUSCH)上传输数据，原则上是可以同时发送PUCCH和PUSCH，即UCI保留在PUCCH。但是，这样会增加立方度量(Cubic Metric)；此外，如果要在更高的发射功率下满足带外发射的要求，并且PUSCH和PUCCH同时传输时在在频域上的间隔较大(PUCCH一般在频带的两端发送)，这将对射频(radio frequency，RF)的实施带来挑战。因此，通常情况下，如果需要传输UCI的PUCCH资源与PUSCH的资源在时间上有重合时，并且基站会在调度该PUSCH时保证满足UCI复用处理时间的条件，UCI会和数据复用在PUSCH上，避免同时发送PUCCH。
4、PUCCH和PUSCH冲突处理
NR R15中，在一个PUCCH组(PUCCH group)内，无论PUCCH和PUSCH在相同的服务小区或不同的服务小区，均不支持PUCCH和PUSCH同时传输。当PUCCH和PUSCH时域资源重叠时(包括部分时域资源重叠和全部时域资 源重叠)，UE会在满足一定时间要求的情况下，根据相应的规则丢弃或合并。
示例性的，若承载调度请求(Scheduling Request，SR)的PUCCH和未承载上行共享信道(Uplink Shared Channel，UL-SCH)的PUSCH时域重叠，则UE丢弃PUSCH，并传输SR PUCCH。或者UE将PUCCH上承载的上行控制信息(Uplink Control Information，UCI)(除SR)复用到PUSCH中传输。例如，承载混合自动重传请求应答(Hybrid Automatic Repeat Request Acknowledgement，HARQ-ACK)或承载信道状态信息(Channel State Information，CSI)的PUCCH 1和PUSCH 2重叠，则UE将PUCCH 1上承载的HARQ-ACK/CSI复用到PUSCH 2中传输。
具体的，UE首先处理多个PUCCH之间的时域资源重叠(如果有)，处理得到的结果是一个或者多个非时域资源重叠的PUCCH，然后UE处理PUCCH和PUSCH之间的时域资源重叠，若PUCCH只与一个PUSCH重叠，则UE将UCI(不包括SR)复用在该PUSCH中，若PUCCH与多个PUSCH重叠，则UE根据相关技术中的复用规则，选择一个PUSCH进行复用，该第一复用规则(即指示UE选择复用UCI的PUSCH的先后顺序)如下：
规则1：承载非周期性信道状态信息(Aperiodic CSI，A-CSI)的PUSCH。
规则2：起始时隙最早的PUSCH。
规则3：动态调度的PUSCH>配置授权的PUSCH或半持续(semi-persistent)的PUSCH。
规则4：所在服务小区索引(index)小的PUSCH>所在服务小区索引大的PUSCH。
规则5：传输符号早的PUSCH>传输符号晚的PUSCH。
示例性的，PUCCH的物理层优先级由其承载的UCI的优先级确定。例如SR的优先级通过无线资源控制(Radio Resource Control，RRC)配置，周期性CSI和半持续CSI(SP-CSI)优先级预定义为低优先级，HARQ-ACK的优先级由其对应的DCI指示或者根据半持续调度(Semi-Persistent Scheduling，SPS)的配置确定。PUSCH的传输优先级由PUSCH对应的调度下行控制信 息(Downlink Control Information，DCI)指示，或者对于配置授权的PUSCH，其优先级由RRC配置。
当PUCCH和PUCCH的时域资源重叠或者PUCCH和PUSCH的时域资源重叠时，UE先处理优先级相同的传输(规则同R15)，然后处理不同优先级的传输，在处理不同优先级时，在满足一定时间要求的情况下，UE取消传输(或称为丢弃)低优先级的上行资源，传输高优先级的上行资源。
而在载波聚合(Carrier Aggregation)场景下，其规则如下：
第一优先级：有A-CSI的PUSCH；
第二优先级：动态调度的PUSCH(DG PUSCH)>配置授权PUSCH(CG-PUSCH)或semiPersistentOnPUSCH(SP-CSI on PUSCH)；
第三优先级：载波索引(CC index)小的PUSCH>CC index大的PUSCH；
第四优先级：时间上，传输早的PUSCH>传输晚的PUSCH。
5、MAC层定义的上行传输跳过功能
MAC层在协议TS38.321定义了终端实行上行传输跳过(UL skipping)的过程。如果满足以下条件，MAC实体将不会为HARQ实体生成MAC PDU：
条件1：MAC实体配置了参数skipUplinkTxDynamic并且该参数的值被设置为真(true)的，MAC定位到了上行授权(UL grant)中指示的HARQ实体。
条件2：该UL grant中没有如TS 38.212中所规定的为此PUSCH传输请求非周期性CSI。
条件3：MAC PDU包括零个MAC服务数据单元(service data unit,SDU)。
条件4：MAC PDU仅包含周期性缓存状态报告(Buffer Status Report，BSR)，并且没有可用于任何逻辑通道组(Logical Channel Group，LCG)的数据，或者MAC PDU仅包含填充BSR。
在相关技术中，在终端设备的上行共享信道使能了UL skipping功能的情况下，如果上行控制信道(如，PUCCH)的时域资源和动态调度的上行共享信道的时域资源有资源冲突，由于PUSCH可能没有数据要发送，MAC层基 于是否有数据生成PDU，无法根据是否有UCI要复用来生成PDU。
具体的，在上行控制信道(如，PUCCH)的时域资源和动态调度的上行共享信道的时域资源有资源冲突的情况下，终端设备可能选择不生成PUSCH，以使上行控制信息(如，UCI)在PUCCH上传输，也可以选择生成PUSCH，以使上行控制信息复用在PUSCH上传输。
如此，会导致UCI复用的资源在网络端无法确定，进而导致网络侧无法准确的接收到UCI。尤其在载波数较多时，网络侧设备需要在每个载波上，基于上行控制信息是否复用在该载波的PUSCH的两种假设进行盲检测，会增加网络侧盲检测的复杂度，为网络侧造成较大的负担。
6、上行配置授权
针对低时延业务或周期业务的需求，NR支持上行半静态配置授权(Configured Grant)的传输方式，减少信令交互流程，保证低时延要求。配置授权传输的资源可通过RRC信令半静态地配置，当有优先级高的业务如URLLC业务数据到来时，UE可在配置授权的上行信道(PUSCH)上发送数据。
Configured grant传输有两种类型，type 1和type 2。其中，type 1配置授权传输的特点为所有传输参数均由RRC配置；当RRC配置了type 1配置授权时，该配置即进行了激活。type 2配置授权传输的特点为，RRC配置部分参数，如周期等，同时需要由下行激活信令，对type 2配置授权配置进行激活。
具体的，在上行控制信道(如，PUCCH)的时域资源和配置授权的上行共享信道的时域资源有资源冲突的情况下，终端设备可能选择不生成PUSCH，以使上行控制信息(如，UCI)在PUCCH上传输，也可以选择生成PUSCH，以使上行控制信息复用在PUSCH上传输。
如此，会导致UCI复用的资源在网络端无法确定，进而导致网络侧无法准确的接收到UCI。尤其在载波数较多时，网络侧设备需要在每个载波上，基于上行控制信息是否复用在该载波的PUSCH的两种假设进行盲检测，会 增加网络侧盲检测的复杂度，为网络侧造成较大的负担。
为了解决上述问题，本申请实施例提供了一种上行传输方法、装置及设备，如果至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠，则在MAC层可以按照以下任一项处理方式，生成MAC PDU：方式1，如果MAC层获知上述上行共享信道的时域资源与上述上行控制信道的时域资源重叠，则生成MAC PDU；方式2，根据物理层通知给MAC层的复用信息，生成MAC PDU；其中，上述至少一个上行控制信道上承载有上行控制信息(一个或多个)。
如此，在上行共享信道与上行控制信道冲突的情况下，可以通过MAC层生成MAC PDU，使得终端设备即使在没有数据传输的情况下，还可以支持将该上行控制信道上承载的上行控制信息可以复用到配置授权的上行共享信道上，进而使得网络侧设备无需进行盲检测便可准确的确定出上行控制信道复用的资源，降低了网络侧盲检测的复杂度，提高了系统通信能效。
7、其他术语
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，如码分多址(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)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述技术既可用于以上的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，这些技术也可应用于NR系统应用以外的应用，如第6代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(vehicle user equipment，VUE)、行人终端(pedestrian user equipment，PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。而本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(evolved Node B，eNB)、家用B节点、家用演进型B节点、无线局域网(wireless local area network，WLAN)接入点、无线保真(wireless fidelity，WiFi)节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的上行传输方法进行详细地说明。
本申请实施例提供的一种上行传输方法，该上行传输方法可以应用于终 端设备，换言之，该上行传输方法可以由安装在终端设备中的软件或硬件来执行。如图2所示，本申请实施例提供的数据传输方法可以包括下述的步骤201。
步骤201：在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在MAC层按照以下任一项处理方式，生成MAC PDU。
第一种处理方式：如果至少一个配置授权上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠，且如果是MAC层获知上述至少一个上行共享信道的时域资源与上述至少一个上行控制信道的时域资源重叠，则在MAC层生成MAC PDU。
第二种处理方式：在MAC层(或层2，Layer 2)根据物理层(或层1，Layer 1)通知给MAC层的复用信息，生成MAC PDU。
上述配置授权可以是非授权配置，免授权配置，半静态调度，configured grant等。
在本申请实施例中，上述至少一个上行控制信道上承载有至少一个上行控制信息。
在本申请实施例中，所述至少一个配置授权的上行共享信道位于一个或多个载波上。
应注意的是，上述至少一个上行共享信道的时域资源与上述至少一个上行控制信道的时域资源重叠是指：上述至少一个上行共享信道与上述至少一个上行控制信道间在时间上存在冲突。示例性的，上述时域资源可以是一个或多个时隙/子时隙/符号/子帧。
在本申请实施例中，上述MAC PDU与上行控制信息(如UCI)之间存在以下关系：1)如果目标上行共享信道与上行控制信道资源重叠，MAC PDU与UCI复用在目标上行共享信道上传输；或者，2)如果目标上行共享信道与目标上行控制信道资源不重叠，UCI在目标上行控制信道上传输，MAC PDU在目标上行共享信道上传输。
可选地，在本申请实施例中，上述复用信息用于指示：所述至少一个配置授权的上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠。
可选地，在本申请实施例中，上述复用信息还可以用于指示目标上行共享信道，即：上述至少一个配置授权的上行共享信道中，用于承载上述至少一个上行控制信道的上行控制信息的上行共享信道。进一步的，此时，MAC层可能不需要物理层来通知当前有上行控制信道与上述共享信道间存在冲突，MAC层只需要根据物理层告知的复用信息，直接生成MAC PDU。
可选地，在本申请实施例中，上述复用信息还可以用于指示以下至少一项：
所述至少一个上行控制信道中，用于承载所述上行控制信息的目标上行控制信道；
所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道；
所述至少一个配置授权的上行共享信道中，与所述至少一个上行控制信道存在时域资源重叠的信道；
所述至少一个上行控制信道中，与所述至少一个配置授权的上行共享信道存在时域资源重叠的信道。
上述前两种目标上行共享信道确定方式可直接告知MAC层哪一个是目标上行共享信道，后两种目标上行共享信道需要由MAC层去确定哪一个是目标上行共享信道。
上述目标PUSCH可为编号最小的载波上的多个PUSCH中起始时间最早的PUSCH，或者，目标PUSCH为编号最小的载波上的多个PUSCH中触发了非周期CSI上报的PUSCH，或，目标PUSCH为多个载波中，位于动态UL调度的且编号最小的载波的PUSCH，或，目标PUSCH为多个载波中，位于触发了非周期CSI上报且编号最小的载波的PUSCH，或者，目标PUSCH为所述至少一个配置授权中，编号最小或最大的配置授权的PUSCH，或者， 目标PUSCH为所述至少一个配置授权中，位于编号最小或最大的载波上的配置授权的PUSCH。
其中，目标上行共享信道的优先级与至少一个配置授权的上行共享信道对应的优先级相同或不同，如目标上行共享信道的优先级可大于、等于或小于所述至少一个配置授权的上行共享信道对应的优先级。配置授权的PUSCH的优先级可以是配置授权的PUSCH对应的优先级或者配置授权对应的优先级。
PUCCH对应的优先级，可以是该PUCCH携带的UCI的优先级，还可以是PUCCH携带的UCI对应的物理下行共享信道的优先级，或者PUCCH对应的PDSCH对应的HARQ-ACK码本的优先级。
应注意的是，本申请实施例中目标上行共享信道可以是一个也可以是多个，目标上行控制信道可以是一个也可以是多个，本申请实施例对此不做限定。
可选地，在本申请实施例中，上述复用信息可以是终端设备在接收到调度授权(下行调度授权或上行调度授权)时由物理层通知给MAC层的。
进一步可选地，在本申请实施例中，在上述调度授权为下行调度授权的情况下，上述下行调度授权为调度上述至少一个上行控制信道中的部分或全部上行控制信道的DCI。示例性的，下行调度授权为调度上述一个或多个承载UCI的PUCCH的最近(latest)的DCI。
进一步可选地，在本申请实施例中，在上述调度授权为上行调度授权的情况下，上述上行调度授权为调度与所述至少一个上行控制信道的时域资源重叠的上行共享信道的DCI，
或者，在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个上行控制信道在一个时间单元重叠，
或者，在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个配置授权的上行共享信道在一个时间单元重叠，其中，上行调度授权调度的上行共享信道与所述至少一个配置授权的 上行共享信道的优先级相同或不相同。
示例性的，在上述上行调度授权为调度上述至少一个上行共享信道中的部分或全部上行共享信道的DCI的情况下，上述上行调度授权为调度PCell上的PUSCH的DCI。
示例性的，上述时间单元可为：子帧，时隙，子时隙(sub-slot)，符号等。
进一步的，终端设备在接收该调度授权的DCI的结束时隙或符号时，由物理层通知给MAC层；或，终端设备在接收该调度授权的DCI的结束时隙或符号后X个时间单元，由物理层通知给MAC层。其中，X是预定义或网络配置或与UE能力有关，进一步的，X可以是下行控制信道(physical downlink control channel，PDCCH)的处理时间。
可选地，在本申请实施例中，上述步骤201中终端设备生成MAC PDU的过程中还可以包括如下步骤201a：
步骤201a：所述至少一个配置授权的上行共享信道中，目标上行共享信道没有数据需要传输的情况下，生成MAC填充PDU。
其中，上述目标上行共享信道为：所述至少一个配置授权的上行共享信道中，用于承载所述至少一个上行控制信道的上行控制信息的上行共享信道。
示例性的，当终端设备没有数据时，生成MAC填充PDU(MAC padding PDU)。终端设备没有数据，具体可以是在PUSCH对应的逻辑信道组(Logical Channel Group)中没有数据。
示例性的，当MAC层根据复用信息，为上述至少一个PUSCH生成MAC PDU时，当任意一个PUSCH上没有UL-SCH时，MAC生成MAC填充(padding)PDU。
示例性的，当MAC层根据复用信息生成MAC PDU时，若目标PUSCH上没有UL-SCH或没有数据，MAC层生成MAC padding PDU。
进一步可选地，在本申请实施例中，本申请实施例提供的上行传输方法还可以包括如下步骤A1：
步骤A1：在冲突信道或目标载波上，禁止使能所述上行传输跳过功能；
所述冲突信道为：所述至少一个配置授权的上行共享信道中，与所述下行调度授权调度的上行控制信道的时域资源重叠的信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个上行控制信道的时域资源重叠的上行共享信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个配置授权的上行共享信道的时域资源重叠的信道；
所述目标载波为所述冲突信道所在的载波。
示例性的，当至少一个PUCCH与PUSCH在时间上有重叠，UE禁止使能(disable)PUSCH UL skipping功能。进一步的，与PUCCH有冲突的PUSCH所在的载波上，禁止使能PUSCH UL skipping功能。
可选地，在本申请实施例中，针对上述处理方式2，本申请实施例提供的上行传输方法还可以包括如下步骤B1或步骤B2或步骤B3：
步骤B1：在上行控制信道包括多个信道的情况下，在物理层或MAC层根据第一复用规则，从所述多个上行控制信道中确定出所述目标上行控制信道。
步骤B2：在所述至少一个配置授权的上行共享信道包括多个信道的情况下，在物理层或MAC层根据第二复用规则，从所述多个配置授权的上行共享信道中确定出所述目标上行共享信道。
步骤B3：在上述至少一个上行共享信道包括多个上行共享信道、上述目标上行控制信道的时域资源与上述多个上行共享信道的时域资源重叠的情况下，在物理层或MAC层根据第二复用规则以及上述目标上行控制信道，从上述多个上行共享信道中确定出上述目标上行共享信道。
示例性的，上述第一复用规则可以为UCI on PUCCH的PUCCH复用规则。
在一种示例中，HARQ-ACK on PUCCH的复用规则和调度请求(Scheduling request，SR)on PUCCH的复用规则如下表1所示：
表1
Figure PCTCN2021111299-appb-000001
Figure PCTCN2021111299-appb-000002
需要说明的是，上表中的PF0为PUCCH Format 0，上表中的PF1为PUCCH Format 1，上表中的PF2/3/4为PUCCH Format 2/3/4。
针对CSI+SR
在CSI的PUCCH上传输SR和CSI，[1og 2(K+1)]bits预置在周期/半静态CSI信息比特前，以升序的方式，指示SR资源Id中对应的SR状态(激活或非激活)。
针对HARQ-ACK/SR/CSI
如果HARQ-ACK是对没有PDCCH调度的PDSCH的反馈，则HARQ-ACK或HARQ-ACK+SR将复用在CSI PUCCH上传输。
如果HARQ-ACK是对有PDCCH调度的PDSCH的反馈，则HARQ-ACK或HARQ-ACK+SR+CSI将复用在一个PUCCH上传输。其中，该PUCCH为 基于HARQ-ACK、CSI以及SR比特数在RRC配置的多个资源集中确定的PUCCH。
示例性的，针对上述步骤B2，在上述至少一个配置授权的上行共享信道包括多个上行共享信道、且该多个上行共享信道位于单载波上的情况下，上述目标上行共享信道是基于以下至少一项确定的：
上述多个上行共享信道中起始时域位置最早的上行共享信道；
上述多个上行共享信道中触发了非周期CSI上报的上行共享信道；
物理层通知MAC层在上述目标上行共享信道上复用所述上行控制信息；
物理层通知MAC层上述多个上行共享信道中的每个上行共享信道是否复用所述上行控制信息。
举例说明，以上行共享信道为PUSCH为例，当单载波且有多个PUSCH时，物理层(physical，PHY)层需要根据第二复用规则，确定承载UCI的目标PUSCH。
具体的复用方式包括：
复用方式1：目标PUSCH为该载波上的多个PUSCH中起始时间最早的PUSCH；
复用方式2：目标PUSCH为该载波上的多个PUSCH中触发了非周期CSI上报(Aperiodic-CSI，A-CSI)的PUSCH。
示例性的，针对上述步骤B2，在上述至少一个配置授权的上行共享信道包括多个上行共享信道、且上述多个上行共享信道位于多个载波上的情况下，上述目标上行共享信道满足以下至少一项：
第一载波上的多个上行共享信道中起始时域位置最早的上行共享信道；
第一载波上的多个上行共享信道中触发了非周期CSI上报的上行共享信道；
第二载波上的上行共享信道；
第三载波上的上行控制信道。
其中，上述第一载波为上述多个载波中编号满足预定条件(如，编号最 小)的载波；上述第二载波为上述多个载波中上行调度的且编号满足上述预定条件的载波；上述第三载波为上述多个载波中触发了非周期CSI上报且编号满足上述预定条件的载波。
举例说明，以上行共享信道为PUSCH为例，当多载波且有多个PUSCH时，PHY层需要根据第二复用规则，确定承载该UCI的目标PUSCH以及目标PUSCH所在的载波。
具体的，复用方式包括：复用方式1：目标PUSCH为编号最小的载波上的多个PUSCH中起始时间最早的PUSCH；
复用方式2：目标PUSCH为编号最小的载波上的多个PUSCH中触发了非周期CSI上报(Aperiodic-CSI，A-CSI)的PUSCH；
复用方式3：目标PUSCH为多个载波中，位于动态UL调度的且编号最小的载波的PUSCH；
复用方式4：目标PUSCH为多个载波中，位于触发了非周期CSI上报且编号最小的载波的PUSCH；
复用方式5：目标PUSCH为所述至少一个配置授权的PUSCH中，编号最小或最大的配置授权的PUSCH；
复用方式6：目标PUSCH为所述至少一个配置授权的PUSCH中，对应的配置授权所在的载波的编号最小或最大的配置授权的PUSCH。
另外，复用方式还可以包括：目标PUSCH为位于单载波上的所述至少一个配置授权的上行共享信道中，起始时间最早的信道；或者，位于多载波上的所述至少一个配置授权的上行共享信道中，位于编号最小的载波上的，起始时间最早的信道；或者，位于多载波上的所述至少一个配置授权的上行共享信道中，位于动态调度的载波中编号最小的载波上的信道。
示例性的，MAC层或物理层将会根据第二复用规则，确定目标上行共享信道。在一种示例中，当PHY层通知MAC层目标PUCCH与上述至少一个PUSCH冲突时，MAC层会根据上述目标PUCCH以及UCI on PUSCH的复用规则，确定承载UCI的目标PUSCH。
可选地，在本申请实施例中，针对上述处理方式1，如果MAC层获知所述至少一个上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠，本申请实施例提供的上行传输方法还可以包括如下步骤C1：
步骤C1：在MAC层根据第二复用规则，从所述至少一个上行共享信道中确定出用于承载所述上行控制信息的目标上行共享信道。
示例性的，以上行共享信道为PUSCH为例，当MAC层根据第二复用规则(即UCI on PUSCH的PUCCH复用规则)，确定了承载这些一个或多个UCI的目标PUCCH时，若上述目标PUCCH与至少一个PUSCH冲突时，MAC层根据目标PUCCH以及第二复用规则，确定承载UCI的目标PUSCH。
示例性的，以上行共享信道为PUSCH为例，当一个或多个载波上的至少一个PUSCH位于多载波时，MAC层根据第二复用规则，确定用于承载UCI的目标PUSCH以及目标PUSCH所在的载波
示例性的，以上行共享信道为PUSCH、上行控制信道为PUCCH为例，MAC层根据第一复用规则(即UCI on PUCCH的PUCCH复用规则)，确定承载这些一个或多个UCI的目标PUCCH。
示例性的，如果MAC层获知一个或多个承载了UCI的PUCCH，与一个或多个载波上的至少一个PUSCH存在冲突，且当目标PUSCH上没有UL-SCH时，MAC生成MAC padding PDU。
以下将以上行共享信道为PUSCH、上行控制信道为PUCCH为例，以三个示例对本申请实施例提供的上行传输方法进行解释说明。
示例1：
当UE在一个或多个载波上，配置了至少一个配置授权的PUSCH，如果UE接收到一个或多个UL grant，调度了一个或多个载波上至少一个PUSCH，且UE接收到一个或多个DL grant，调度了一个或多个承载UCI的PUCCH时，UE可以根据以下步骤确定UCI的传输：
步骤11：解码DL grant和/或UL grant。
步骤12：如果存在多个PUCCH，PHY层根据UCI on PUCCH的复用规 则确定承载UCI的目标PUCCH的资源。
步骤13：如果目标PUCCH资源与上述一个或多个载波上的至少一个PUSCH存在冲突，则PHY层在至少一个PUSCH中，根据UCI on PUSCH复用优先级，确定用于承载UCI的目标PUSCH的资源。
步骤14：PHY层通知MAC层UCI复用信息(即步骤13中的内容)，MAC根据该UCI复用信息生成MAC PDU。
步骤15：如果没有UL-SCH，则MAC层生成padding PDU。
步骤16：在目标PUSCH上进行UCI的映射。
步骤17：在目标PUSCH上进行(padding)data的映射。
需要说明的是，本实施例对上述步骤16和步骤17间的执行顺序并不做限定，可以先执行步骤16再执行步骤17(即先进行UCI映射，后进行data映射)，也可以先执行17再执行16(即先进行data映射，后进行UCI映射)。
示例2：
当UE在一个或多个载波上，配置了至少一个配置授权的PUSCH，如果UE接收到一个或多个UL grant，调度了一个或多个载波上的至少一个PUSCH，且UE接收到一个或多个DL grant，调度了一个或多个承载UCI的PUCCH，UE根据以下步骤确定UCI的传输：
步骤21：解码DL grant和/或UL grant。
步骤22：如果存在多个PUCCH，PHY层根据UCI on PUCCH的复用规则确定承载UCI的目标PUCCH的资源。
步骤23：PHY层通知MAC层UCI复用信息(即步骤12中的内容)，MAC层根据该UCI复用信息生成MAC PDU。
步骤24：如果目标PUCCH资源与一个或多个载波上至少一个PUSCH存在冲突，则MAC层在至少一个PUSCH中，根据UCI on PUSCH复用规则，确定用于承载UCI的目标PUSCH的资源。
步骤25：MAC为该目标PUSCH生成PDU，如果没有UL-SCH，则生成padding PDU。
步骤26：在目标PUSCH上进行UCI的映射。
步骤27：在目标PUSCH上进行(padding)data的映射。
需要说明的是，本实施例对上述步骤26和步骤27间的执行顺序并不做限定，可以先执行步骤26再执行步骤27(即先进行UCI映射，后进行data映射)，也可以先执行27再执行26(即先进行data映射，后进行UCI映射)。
示例3：
当UE在一个或多个载波上，配置了至少一个配置授权的PUSCH，如果UE接收到一个或多个UL grant，调度了一个或多个载波上至少一个PUSCH，且UE接收到一个或多个DL grant，调度了一个或多个承载UCI的PUCCH，UE根据以下步骤确定UCI的传输：
步骤31：解码DL grant和/或UL grant。
步骤32：PHY层在步骤31后通知MAC层，上述一个或多个承载了UCI的PUCCH，与上述一个或多个载波上的至少一个PUSCH存在冲突。
步骤33：MAC根据该UCI复用信息为存在冲突的第一PUSCH(集合)生成MAC PDU。
步骤34：如果没有UL-SCH，则MAC生成padding PDU。
步骤35：如果存在多个PUCCH，PHY层根据UCI on PUCCH的复用规则确定承载UCI的目标PUCCH的资源。
步骤36：如果目标PUCCH资源与一个或多个载波上至少一个PUSCH存在冲突，则PHY层在至少一个PUSCH中，根据UCI on PUSCH复用规则，确定用于承载UCI的目标PUSCH的资源。
步骤37：如果目标PUSCH有UL-SCH，则在目标PUSCH上进行UCI和数据(data)的映射。
步骤38：否则，在目标PUSCH上进行UCI和padding data的映射。
步骤39：如果目标PUSCH不属于第一PUSCH(集合)，则在第一PUSCH(集合)上进行(padding)data的映射.
步骤40：如果第一PUSCH(集合)中的一个PUSCH没有数据，则进行 padding data的映射。
需要说明的是，本实施例对于UCI映射和data映射的执行顺序并不做限定，可以先进行UCI映射，后进行data映射，也可以先进行data映射，后进行UCI映射。
除上述生成MAC PDU的方式之外，本申请还提供一种方式生成MAC PDU，包括：
所述至少一个配置授权的物理上行共享信道中，用于承载所述上行控制信息的目标物理上行共享信道被配置为重复传输M次的情况下，生成N个MAC PDU，所述M为正整数，所述N为小于或等于M的正整数。
定义终端内部物理层到MAC层的内部层级(即inter-layer)信令，当终端的物理层获知到一个配置授权的PUSCH和PUCCH的资源在时域上有重叠时，终端的物理层会通知MAC层无条件地为当前混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)实体产生MAC PDU。若该配置授权的PUSCH配置了重复K次传输，物理层向MAC层递交的内部信令可以是：
无条件的产生K个相同的MAC PDU；或
无条件的产生K个中的M个MAC PDU，其中1≤M≤K。
若重复传输类型为B，则MAC PDU为nominal PUSCH，即所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道被配置为重复传输类型B的情况下，所述MAC PDU为用于nominal上行共享信道的PDU。
进一步的，还可以不定义任何空口或者终端内部的信令，直接在MAC层定义相关的MAC PDU生成条件，使得物理层PUCCH和PUSCH传输资源的重叠对MAC层可见。
具体的，如果满足以下条件，MAC实体将不会为HARQ实体生成MAC PDU：
MAC实体配置了参数skipUplinkTxDynamic，并且该参数的值被设置为 真(true)，MAC定位到了上行授权(UL grant)中指示的HARQ实体；
该UL grant中没有为此PUSCH传输请求非周期性CSI，且该HARQ实体对应一个配置上行传输授权(configured uplink grant)，且没有UCI将要复用至该配置授权的PUSCH传输上；
MAC PDU包括零个MAC SDU；和MAC PDU仅包含周期性缓冲区状态上报(Buffer Status Report，BSR)，并且没有可用于任何逻辑信道组(Logical Channel Group，LCG)的数据，或者MAC PDU仅包含填充BSR。
若该调度的PUSCH配置或被上行传输授权(UL grant)指示了重复K次传输，相应地MAC层将会产生多个重复的MAC PDU。
本申请中的方案可适用于单载波和多载波，以及授权频段或非授权频段。
本申请实施例提供的上行传输方法，在终端设备配置授权的情况下，如果至少一个上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠，则在MAC层可以按照以下任一项处理方式，生成MAC PDU：方式1，如果MAC层获知上述上行共享信道的时域资源与上述上行控制信道的时域资源重叠，则生成MAC PDU；方式2，根据物理层通知给MAC层的复用信息，生成MAC PDU；其中，上述至少一个上行控制信道上承载有至少一个上行控制信息。如此，在上行共享信道与上行控制信道冲突的情况下，可以通过MAC层生成MAC PDU，使得终端设备即使在没有数据传输的情况下，还可以支持将该上行控制信道上承载的上行控制信息可以复用到配置授权的上行共享信道上，进而使得网络侧设备无需进行盲检测便可准确的确定出上行控制信道复用的资源，降低了网络侧盲检测的复杂度，提高了系统通信能效。
需要说明的是，本申请实施例提供的上行传输方法，执行主体可以为上行传输装置，或者，该上行传输装置中的用于执行上行传输方法的控制模块。本申请实施例中以上行传输装置执行上行传输方法为例，说明本申请实施例提供的上行传输方法的装置。
本申请实施例提供的一种上行传输装置，如图3所示，本申请实施例提 供的上行传输装置300可以包括：执行模块301，其中：
执行模块301，用于在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在媒体访问控制MAC层按照以下任一项处理方式，生成MAC协议数据单元PDU：
若MAC层获知所述上行共享信道的时域资源与所述上行控制信道的时域资源重叠，则生成MAC PDU；
根据物理层通知给MAC层的复用信息，生成MAC PDU；
其中，所述至少一个上行控制信道用于承载上行控制信息。
进一步的，所述复用信息用于指示：所述至少一个配置授权的上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠。
进一步的，所述至少一个配置授权的上行共享信道位于一个或多个载波上。
进一步的，所述复用信息用于指示以下至少一项：
所述至少一个上行控制信道中，用于承载所述上行控制信息的目标上行控制信道；
所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道；
所述至少一个配置授权的上行共享信道中，与所述至少一个上行控制信道存在时域资源重叠的信道；
所述至少一个上行控制信道中，与所述至少一个配置授权的上行共享信道存在时域资源重叠的信道。
进一步的，上行传输装置300还包括：
第一确定模块，用于在所述至少一个上行控制信道包括多个上行控制信道的情况下，在物理层或MAC层根据第一复用规则，从所述多个上行控制信道中确定出所述目标上行控制信道；
或者，
在所述至少一个配置授权的上行共享信道包括多个配置授权的上行共享 信道的情况下，在物理层或MAC层根据第二复用规则，从所述多个配置授权的上行共享信道中确定出所述目标上行共享信道；
或者，
在所述至少一个配置授权的上行共享信道包括多个配置授权的上行共享信道，且所述目标上行控制信道的时域资源与所述至少一个配置授权的上行共享信道的时域资源重叠的情况下，在物理层或MAC层根据第二复用规则以及所述目标上行控制信道，从所述至少一个配置授权的上行共享信道中确定出所述目标上行共享信道。
进一步的，所述目标上行共享信道为：
所述至少一个配置授权的上行共享信道中，对应的配置授权编号最大的信道；
或
所述至少一个配置授权的上行共享信道中，对应的配置授权编号最小的信道；
或
所述至少一个配置授权的上行共享信道中，对应的配置授权所在的载波的编号最大的信道；
或
所述至少一个配置授权的上行共享信道中，对应的配置授权所在的载波的编号最小的信道。
进一步的，所述复用信息是所述终端设备在接收到调度授权时由物理层通知给MAC层的。
进一步的，在所述调度授权为下行调度授权的情况下，所述下行调度授权为调度所述上行控制信道的下行控制信息DCI；
或
在所述调度授权为上行调度授权的情况下，所述上行调度授权为调度与所述至少一个上行控制信道的时域资源重叠的上行共享信道的DCI；
或
在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个上行控制信道在一个时间单元重叠；
或
在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个配置授权的上行共享信道在一个时间单元重叠。
进一步的，上行传输装置300还包括禁止使能模块，用于在冲突信道或目标载波上，禁止使能所述上行传输跳过功能；
所述冲突信道为：所述至少一个配置授权的上行共享信道中，与所述下行调度授权调度的上行控制信道的时域资源重叠的信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个上行控制信道的时域资源重叠的上行共享信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个配置授权的上行共享信道的时域资源重叠的信道；
所述目标载波为所述冲突信道所在的载波。
进一步的，若MAC层获知所述至少一个上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠，上行传输装置300还包括第二确定模块，用于：
在MAC层根据第二复用规则，从所述至少一个上行共享信道中确定出用于承载所述上行控制信息的目标上行共享信道。
进一步的，所述执行模块301，包括：
所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道没有数据需要传输的情况下，生成MAC填充PDU。
进一步的，所述执行模块301，包括：
所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道被配置为重复传输M次的情况下，生成N个MAC PDU，所述M为正整数，所述N为小于或等于M的正整数。
本申请实施例提供的终端能够实现图2的方法实施例中各个过程以及达 到相同的技术效果，为避免重复，这里不再赘述。
图3所示的上行传输装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
图3所示的上行传输装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
可选的，如图4所示，本申请实施例还提供一种终端700，包括处理器701，存储器702，存储在存储器702上并可在所述处理器701上运行的程序或指令，该程序或指令被处理器701执行时实现上述上行传输方法实施例的各个过程，且能达到相同的技术效果。
图5为实现本申请各个实施例的一种终端的硬件结构示意图。
该终端1000包括但不限于：射频单元1001、网络模块1002、音频输出单元1003、输入单元1004、传感器1005、显示单元1006、用户输入单元1007、接口单元1008、存储器1009以及处理器1010等部件。
本领域技术人员可以理解，终端1000还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1010逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图5中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1004可以包括图形处理器(Graphics Processing Unit，GPU)10041和麦克风10042，图形处理器10041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1006可包括显示面板10061， 可以采用液晶显示器、有机发光二极管等形式来配置显示面板10061。用户输入单元1007包括触控面板10071以及其他输入设备10072。触控面板10071，也称为触摸屏。触控面板10071可包括触摸检测装置和触摸控制器两个部分。其他输入设备10072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1001将来自网络侧设备的下行数据接收后，给处理器1010处理；另外，将上行的数据发送给网络侧设备。通常，射频单元1001包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1009可用于存储软件程序或指令以及各种数据。存储器109可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1009可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器1010可包括一个或多个处理单元；可选的，处理器1010可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1010中。
其中，处理器1010，用于在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在媒体访问控制MAC层按照以下任一项处理方式，生成MAC协议数据单元PDU：
若MAC层获知所述上行共享信道的时域资源与所述上行控制信道的时域资源重叠，则生成MAC PDU；
根据物理层通知给MAC层的复用信息，生成MAC PDU；
其中，所述至少一个上行控制信道用于承载上行控制信息。
进一步的，所述复用信息用于指示：所述至少一个配置授权的上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠。
进一步的，所述至少一个配置授权的上行共享信道位于一个或多个载波上。
进一步的，所述复用信息用于指示以下至少一项：
所述至少一个上行控制信道中，用于承载所述上行控制信息的目标上行控制信道；
所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道；
所述至少一个配置授权的上行共享信道中，与所述至少一个上行控制信道存在时域资源重叠的信道；
所述至少一个上行控制信道中，与所述至少一个配置授权的上行共享信道存在时域资源重叠的信道。
进一步的，处理器1010，还用于在所述至少一个上行控制信道包括多个上行控制信道的情况下，在物理层或MAC层根据第一复用规则，从所述多个上行控制信道中确定出所述目标上行控制信道；
或者，
在所述至少一个配置授权的上行共享信道包括多个配置授权的上行共享信道的情况下，在物理层或MAC层根据第二复用规则，从所述多个配置授权的上行共享信道中确定出所述目标上行共享信道；
或者，
在所述至少一个配置授权的上行共享信道包括多个配置授权的上行共享信道，且所述目标上行控制信道的时域资源与所述至少一个配置授权的上行共享信道的时域资源重叠的情况下，在物理层或MAC层根据第二复用规则以及所述目标上行控制信道，从所述至少一个配置授权的上行共享信道中确 定出所述目标上行共享信道。
进一步的，所述目标上行共享信道为：
所述至少一个配置授权的上行共享信道中，对应的配置授权编号最大的信道；
或
所述至少一个配置授权的上行共享信道中，对应的配置授权编号最小的信道；
或
所述至少一个配置授权的上行共享信道中，对应的配置授权所在的载波的编号最大的信道；
或
所述至少一个配置授权的上行共享信道中，对应的配置授权所在的载波的编号最小的信道。
进一步的，所述复用信息是所述终端设备在接收到调度授权时由物理层通知给MAC层的。
进一步的，在所述调度授权为下行调度授权的情况下，所述下行调度授权为调度所述上行控制信道的下行控制信息DCI；
或
在所述调度授权为上行调度授权的情况下，所述上行调度授权为调度与所述至少一个上行控制信道的时域资源重叠的上行共享信道的DCI；
或
在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个上行控制信道在一个时间单元重叠；
或
在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个配置授权的上行共享信道在一个时间单元重叠。
进一步的，处理器1010，还用于在冲突信道或目标载波上，禁止使能所 述上行传输跳过功能；
所述冲突信道为：所述至少一个配置授权的上行共享信道中，与所述下行调度授权调度的上行控制信道的时域资源重叠的信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个上行控制信道的时域资源重叠的上行共享信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个配置授权的上行共享信道的时域资源重叠的信道；
所述目标载波为所述冲突信道所在的载波。
进一步的，若MAC层获知所述至少一个上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠，处理器1010，还用于在MAC层根据第二复用规则，从所述至少一个上行共享信道中确定出用于承载所述上行控制信息的目标上行共享信道。
进一步的，处理器1010，还用于在所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道没有数据需要传输的情况下，生成MAC填充PDU。
进一步的，处理器1010，还用于在所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道被配置为重复传输M次的情况下，生成N个MAC PDU，所述M为正整数，所述N为小于或等于M的正整数。
应理解，本实施例中，上述处理器1010和射频单元1001能够实现图2的方法实施例中终端实现的各个过程，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现图2所示的上行传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的电子设备中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现上述图2所示的上行传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的 划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者基站等)执行本申请各个实施例所述的方法。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，模块、单元、子单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的， 本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (29)

  1. 一种上行传输方法，应用于终端设备，包括：
    在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在媒体访问控制MAC层按照以下任一项处理方式，生成MAC协议数据单元PDU：
    如果MAC层获知所述上行共享信道的时域资源与所述上行控制信道的时域资源重叠，则生成MAC PDU；
    根据物理层通知给MAC层的复用信息，生成MAC PDU；
    其中，所述至少一个上行控制信道用于承载上行控制信息。
  2. 根据权利要求1所述的方法，其中，所述复用信息用于指示：所述至少一个配置授权的上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠。
  3. 根据权利要求1所述的方法，其中，所述至少一个配置授权的上行共享信道位于一个或多个载波上。
  4. 根据权利要求1所述的方法，其中，所述复用信息用于指示以下至少一项：
    所述至少一个上行控制信道中，用于承载所述上行控制信息的目标上行控制信道；
    所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道；
    所述至少一个配置授权的上行共享信道中，与所述至少一个上行控制信道存在时域资源重叠的信道；
    所述至少一个上行控制信道中，与所述至少一个配置授权的上行共享信道存在时域资源重叠的信道。
  5. 根据权利要求4所述的方法，还包括：
    在所述至少一个上行控制信道包括多个信道的情况下，在物理层或MAC层根据第一复用规则，从所述多个上行控制信道中确定出所述目标上行控制信道；
    或者，
    在所述至少一个配置授权的上行共享信道包括多个信道的情况下，在物理层或MAC层根据第二复用规则，从所述多个配置授权的上行共享信道中确定出所述目标上行共享信道；
    或者，
    在所述至少一个配置授权的上行共享信道包括多个，且所述目标上行控制信道的时域资源与所述至少一个配置授权的上行共享信道的时域资源重叠的情况下，在物理层或MAC层根据第二复用规则以及所述目标上行控制信道，从所述至少一个配置授权的上行共享信道中确定出所述目标上行共享信道。
  6. 根据权利要求4所述的方法，其中，所述目标上行共享信道为：
    所述至少一个配置授权的上行共享信道中，对应的配置授权编号最大的信道；
    或
    所述至少一个配置授权的上行共享信道中，对应的配置授权编号最小的信道；
    或
    所述至少一个配置授权的上行共享信道中，对应的配置授权所在的载波的编号最大的信道；
    或
    所述至少一个配置授权的上行共享信道中，对应的配置授权所在的载波的编号最小的信道。
  7. 根据权利要求1所述的方法，其中，所述复用信息是所述终端设备在接收到调度授权时由物理层通知给MAC层的。
  8. 根据权利要求7所述的方法，其中：
    在所述调度授权为下行调度授权的情况下，所述下行调度授权为调度所述上行控制信道的下行控制信息DCI；
    或
    在所述调度授权为上行调度授权的情况下，所述上行调度授权为调度与 所述至少一个上行控制信道的时域资源重叠的上行共享信道的DCI；
    或
    在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个上行控制信道在一个时间单元重叠；
    或
    在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个配置授权的上行共享信道在一个时间单元重叠。
  9. 根据权利要求8所述的方法，还包括：
    在冲突信道或目标载波上，禁止使能所述上行传输跳过功能；
    所述冲突信道为：所述至少一个配置授权的上行共享信道中，与所述下行调度授权调度的上行控制信道的时域资源重叠的信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个上行控制信道的时域资源重叠的上行共享信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个配置授权的上行共享信道的时域资源重叠的信道；
    所述目标载波为所述冲突信道所在的载波。
  10. 根据权利要求1所述的方法，其中，如果MAC层获知所述至少一个上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠，所述方法还包括：
    在MAC层根据第二复用规则，从所述至少一个上行共享信道中确定出用于承载所述上行控制信息的目标上行共享信道。
  11. 根据权利要求1至10中任一项所述的方法，其中，所述生成MAC PDU，包括：
    所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道没有数据需要传输的情况下，生成MAC填充PDU。
  12. 根据权利要求1至10中任一项所述的方法，其中，所述生成MAC PDU，包括：
    所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道被配置为重复传输M次的情况下，生成N个MAC PDU，M为正整数，N为小于或等于M的正整数。
  13. 一种上行传输装置，包括：
    执行模块，用于在至少一个配置授权的上行共享信道的时域资源与至少一个上行控制信道的时域资源重叠的情况下，则在媒体访问控制MAC层按照以下任一项处理方式，生成MAC协议数据单元PDU：
    若MAC层获知所述上行共享信道的时域资源与所述上行控制信道的时域资源重叠，则生成MAC PDU；
    根据物理层通知给MAC层的复用信息，生成MAC PDU；
    其中，所述至少一个上行控制信道用于承载上行控制信息。
  14. 根据权利要求13所述的装置，其中，所述复用信息用于指示：所述至少一个配置授权的上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠。
  15. 根据权利要求13所述的装置，其中，所述至少一个配置授权的上行共享信道位于一个或多个载波上。
  16. 根据权利要求13所述的装置，其中，所述复用信息用于指示以下至少一项：
    所述至少一个上行控制信道中，用于承载所述上行控制信息的目标上行控制信道；
    所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道；
    所述至少一个配置授权的上行共享信道中，与所述至少一个上行控制信道存在时域资源重叠的信道；
    所述至少一个上行控制信道中，与所述至少一个配置授权的上行共享信道存在时域资源重叠的信道。
  17. 根据权利要求16所述的装置，还包括第一确定模块，用于：
    在所述至少一个上行控制信道包括多个信道的情况下，在物理层或MAC层根据第一复用规则，从所述多个上行控制信道中确定出所述目标上行控制信道；
    或者，
    在所述至少一个配置授权的上行共享信道包括多个信道的情况下，在物 理层或MAC层根据第二复用规则，从所述多个配置授权的上行共享信道中确定出所述目标上行共享信道；
    或者，
    在所述至少一个配置授权的上行共享信道包括多个，且所述目标上行控制信道的时域资源与所述至少一个配置授权的上行共享信道的时域资源重叠的情况下，在物理层或MAC层根据第二复用规则以及所述目标上行控制信道，从所述至少一个配置授权的上行共享信道中确定出所述目标上行共享信道。
  18. 根据权利要求16所述的装置，其中，所述目标上行共享信道为：
    所述至少一个配置授权的上行共享信道中，对应的配置授权编号最大的信道；
    或
    所述至少一个配置授权的上行共享信道中，对应的配置授权编号最小的信道；
    或
    所述至少一个配置授权的上行共享信道中，对应的配置授权所在的载波的编号最大的信道；
    或
    所述至少一个配置授权的上行共享信道中，对应的配置授权所在的载波的编号最小的信道。
  19. 根据权利要求13所述的装置，其中，所述复用信息是终端设备在接收到调度授权时由物理层通知给MAC层的。
  20. 根据权利要求19所述的装置，其中：
    在所述调度授权为下行调度授权的情况下，所述下行调度授权为调度所述上行控制信道的下行控制信息DCI；
    或
    在所述调度授权为上行调度授权的情况下，所述上行调度授权为调度与所述至少一个上行控制信道的时域资源重叠的上行共享信道的DCI；
    或
    在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个上行控制信道在一个时间单元重叠；
    或
    在所述调度授权为上行调度授权的情况下，所述上行调度授权调度的上行共享信道与所述至少一个配置授权的上行共享信道在一个时间单元重叠。
  21. 根据权利要求20所述的装置，还包括禁止使能模块，用于：
    在冲突信道或目标载波上，禁止使能所述上行传输跳过功能；
    所述冲突信道为：所述至少一个配置授权的上行共享信道中，与所述下行调度授权调度的上行控制信道的时域资源重叠的信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个上行控制信道的时域资源重叠的上行共享信道，或，所述上行调度授权调度的上行共享信道中，与所述至少一个配置授权的上行共享信道的时域资源重叠的信道；
    所述目标载波为所述冲突信道所在的载波。
  22. 根据权利要求13所述的装置，其中，如果MAC层获知所述至少一个上行共享信道的时域资源与所述至少一个上行控制信道的时域资源重叠，所述装置还包括第二确定模块，用于：
    在MAC层根据第二复用规则，从所述至少一个上行共享信道中确定出用于承载所述上行控制信息的目标上行共享信道。
  23. 根据权利要求13至22中任一项所述的装置，其中，所述执行模块用于，所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道没有数据需要传输的情况下，生成MAC填充PDU。
  24. 根据权利要求13至22中任一项所述的装置，其中，所述执行模块用于，所述至少一个配置授权的上行共享信道中，用于承载所述上行控制信息的目标上行共享信道被配置为重复传输M次的情况下，生成N个MAC PDU，M为正整数，N为小于或等于M的正整数。
  25. 一种终端设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至12中任一项所述的上行传输方法的步骤。
  26. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程 序或指令被所述处理器执行时实现如权利要求1-12中任一项所述的上行传输方法的步骤。
  27. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如权利要求1-12中任一项所述的上行传输方法。
  28. 一种程序产品，所述程序产品被存储在非易失的存储介质中，所述程序产品被配置成被至少一个处理器执行以实现如权利要求1-12中任一项所述的上行传输方法。
  29. 一种终端设备，所述终端设备被配置成用于执行如权利要求1-12中任一项所述的上行传输方法。
PCT/CN2021/111299 2020-08-07 2021-08-06 上行传输方法、装置及终端设备 Ceased WO2022028604A1 (zh)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=80117082

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/111299 Ceased WO2022028604A1 (zh) 2020-08-07 2021-08-06 上行传输方法、装置及终端设备

Country Status (2)

Country Link
CN (1) CN114071743B (zh)
WO (1) WO2022028604A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220104478A (ko) * 2021-01-18 2022-07-26 삼성전자주식회사 무선 통신 시스템에서 상향링크 데이터 전송 스키핑을 위한 방법 및 장치
CN120712871A (zh) * 2023-05-15 2025-09-26 Oppo广东移动通信有限公司 信息传输方法及装置、终端设备、网络设备
WO2025208439A1 (zh) * 2024-04-03 2025-10-09 富士通株式会社 发送或接收信息的方法、装置和通信系统

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的传输方法、用户终端及基站

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7309335B2 (ja) * 2018-09-19 2023-07-18 シャープ株式会社 端末装置、基地局装置、および、通信方法

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
CN114071743B (zh) 2026-03-20
CN114071743A (zh) 2022-02-18

Similar Documents

Publication Publication Date Title
CN115225217B (zh) 旁链路反馈资源的确定方法、装置、终端及存储介质
CN114374486B (zh) Harq-ack的传输方法、终端及网络侧设备
CN113939023B (zh) 一种冲突处理方法及装置
WO2022063072A1 (zh) 上行信道传输方法、装置及终端
JP7662792B2 (ja) 通信処理方法、装置と通信機器
CN114521019B (zh) 上行控制信息传输方法及相关设备
WO2022078451A1 (zh) 配置授权的重复传输方法、装置、设备及可读存储介质
WO2022028604A1 (zh) 上行传输方法、装置及终端设备
WO2022152072A1 (zh) 信道信息发送方法、信道信息接收方法及相关设备
WO2022068869A1 (zh) 传输处理方法、装置及相关设备
JP2024501711A (ja) Ｕｃｉ多重化の方法、装置、機器及び可読記憶媒体
CN113938259B (zh) Harq-ack的反馈方法和设备
CN113965301B (zh) 物理上行控制信道资源重叠的处理方法及装置
WO2021204257A1 (zh) 一种上行传输方法、终端及网络设备
CN114374955A (zh) 传输方法、优先级定义方法、装置及通信设备
CN114745083B (zh) 信息传输方法、装置、终端及网络设备
CN113890701B (zh) 旁链路传输方法、传输装置和终端
CN113839728B (zh) Dci检测方法、发送方法及相关设备
CN115334676A (zh) 上行传输的复用指示方法、装置、终端及网络侧设备
WO2024140634A1 (zh) 传输方法、设备及可读存储介质
WO2023280211A1 (zh) Pucch时域资源重叠的处理方法及装置
CN113965997B (zh) 上行传输方法、装置及设备
WO2022068798A1 (zh) 传输处理方法、装置、终端及可读存储介质
WO2022002248A1 (zh) 旁链路传输方法、传输装置和通信设备
US20230361942A1 (en) Uplink data sending method and configuration method, terminal, and network side device

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)

122 Ep: pct application non-entry in european phase

Ref document number: 21852838

Country of ref document: EP

Kind code of ref document: A1