Uplink transmission method, apparatus, terminal and network-side device

Abstract

The application discloses an uplink transmission method, device, terminal and network side equipment, and belongs to the technical field of communication. The uplink transmission method comprises at least one of the following: a terminal transmits a first physical uplink shared channel (PUSCH) according to a first rule; in the case that a second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the terminal expects that the second PUSCH does not use the first rule; in the case that a first downlink control information (DCI) is used to trigger A-CSI measurement, the terminal does not expect to always carry A-CSI report corresponding to the A-CSI measurement on a third PUSCH, and the third PUSCH is scheduled by the first DCI.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an uplink transmission method, apparatus, terminal, and network-side equipment. Background Technology

[0002] With the development of communication technology, out-of-order (OoO) rules (or rules that do not expect out-of-order processing) have been introduced into communication systems to reduce the complexity of terminal processing. Network-side devices typically need to satisfy OoO rules during configuration or scheduling, or ensure that out-of-order processing is not performed. In multi-service multiplexing scenarios, the aforementioned OoO rules will affect the performance of urgent data transmission. Therefore, existing technologies suffer from poor uplink transmission performance. Summary of the Invention

[0003] This application provides an uplink transmission method, apparatus, terminal, and network-side device that can solve the problem of poor uplink transmission performance.

[0004] Firstly, an uplink transmission method is provided, including at least one of the following:

[0005] The terminal transmits the first physical uplink shared channel (PUSCH) according to the first rule;

[0006] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the terminal expects the second PUSCH not to apply the first rule.

[0007] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, the terminal does not expect to always carry the A-CSI report corresponding to the A-CSI measurement on the third PUSCH, which is scheduled by the first DCI.

[0008] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0009] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0010] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0011] If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time when the first target PUSCH occupies the target processing channel, and the target start time of the second target PUSCH is the start time when the second target PUSCH occupies the target processing channel.

[0012] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0013] Secondly, an uplink transmission method is provided, comprising at least one of the following:

[0014] Network-side devices schedule and receive the first physical uplink shared channel (PUSCH) according to the first rule;

[0015] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the network-side device guarantees that the first rule will not be applied to the second PUSCH.

[0016] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, the network-side device is able to receive an A-CSI report corresponding to the A-CSI measurement on an uplink channel different from the third PUSCH, wherein the third PUSCH is scheduled by the first DCI.

[0017] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0018] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0019] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0020] When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, the time when preparation for processing is completed, the time of transmission start or transmission end. The target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel.

[0021] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0022] Thirdly, an uplink transmission device is provided, comprising:

[0023] The sending module is configured to perform at least one of the following:

[0024] Transmit the first physical uplink shared channel (PUSCH) according to the first rule;

[0025] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), it is expected that the first rule will not be applied to the second PUSCH.

[0026] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, it is not expected that the A-CSI report corresponding to the A-CSI measurement will always be carried on the third PUSCH, which is scheduled by the first DCI.

[0027] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0028] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0029] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0030] If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time when the first target PUSCH occupies the target processing channel, and the target start time of the second target PUSCH is the start time when the second target PUSCH occupies the target processing channel.

[0031] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0032] Fourthly, an uplink transmission device is provided, comprising:

[0033] The receiving module is configured to perform at least one of the following:

[0034] The first physical uplink shared channel (PUSCH) is scheduled and received according to the first rule;

[0035] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the first rule is guaranteed not to be applied to the second PUSCH.

[0036] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, an A-CSI report corresponding to the A-CSI measurement can be received on an uplink channel different from the third PUSCH, which is scheduled by the first DCI.

[0037] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0038] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0039] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0040] When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, the time when preparation for processing is completed, the time of transmission start or transmission end. The target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel.

[0041] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0042] Fifthly, an uplink transmission apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0043] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0044] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to perform at least one of the following:

[0045] Transmit the first physical uplink shared channel (PUSCH) according to the first rule;

[0046] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), it is expected that the first rule will not be applied to the second PUSCH.

[0047] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, it is not expected that the A-CSI report corresponding to the A-CSI measurement will always be carried on the third PUSCH, which is scheduled by the first DCI.

[0048] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0049] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0050] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0051] If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time when the first target PUSCH occupies the target processing channel, and the target start time of the second target PUSCH is the start time when the second target PUSCH occupies the target processing channel.

[0052] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0053] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0054] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to perform at least one of the following:

[0055] The first physical uplink shared channel (PUSCH) is scheduled and received according to the first rule;

[0056] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the first rule is guaranteed not to be applied to the second PUSCH.

[0057] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, an A-CSI report corresponding to the A-CSI measurement can be received on an uplink channel different from the third PUSCH, which is scheduled by the first DCI.

[0058] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0059] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0060] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0061] When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, the time when preparation for processing is completed, the time of transmission start or transmission end. The target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel.

[0062] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0063] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0064] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0065] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0066] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0067] In this embodiment, the terminal performs at least one of the following: the terminal transmits a first Physical Uplink Shared Channel (PUSCH) according to a first rule; when a second PUSCH is scheduled to carry aperiodic Channel State Information (A-CSI), the terminal expects the second PUSCH not to apply the first rule; when a first Downlink Control Information (DCI) is used to trigger an A-CSI measurement, the terminal does not expect to always carry an A-CSI report corresponding to the A-CSI measurement on a third PUSCH, which is scheduled by the first DCI; wherein, the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following: the start time of the first target PUSCH is not earlier than the end time of the second target PUSCH; the start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH. The target PUSCH's end time is determined by the following: If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, and the target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel. The first target PUSCH and the second target PUSCH correspond to the same first frequency domain object. The target time for scheduling the first target PUSCH's first target DCI is later than the target time for scheduling the second target PUSCH's second target DCI. The target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object. This reduces the impact of the OoO rule on emergency data transmission and improves uplink transmission performance. Attached Figure Description

[0068] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0069] Figure 2 This is a schematic diagram of a traditional uplink transmission scenario;

[0070] Figure 3 This is a flowchart illustrating an uplink transmission method provided in an embodiment of this application;

[0071] Figure 4 This is a flowchart illustrating another uplink transmission method provided in an embodiment of this application;

[0072] Figure 5 This is an example diagram of a transmission scenario in an uplink transmission method provided in an embodiment of this application;

[0073] Figure 6This is a schematic diagram of the structure of an uplink transmission device provided in an embodiment of this application;

[0074] Figure 7 This is a schematic diagram of another uplink transmission device provided in the embodiments of this application;

[0075] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0076] Figure 9 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0077] Figure 10 This is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0078] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0079] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0080] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0081] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0082] For ease of understanding, the following describes some aspects of the embodiments of this application:

[0083] I. OoO rules for scheduling downlink control information (DCI) and scheduled physical uplink shared channel (PUSCH).

[0084] To reduce the complexity of terminal processing, OoO rules (or rules that discourage out-of-order processing) are introduced. Specifically, the following OoO rules are introduced between the scheduling DCI and the scheduled PUSCH on a given scheduled serving cell:

[0085] 1. For general scenarios other than mDCI-based mTRP.

[0086] On this Scheduled serving cell, a PUSCH that is scheduled later (based on the ending symbol to compare the timing of the scheduled DCI) cannot be transmitted earlier (i.e., its start time can only be later than the end time of the PUSCH that was scheduled earlier). Specifically, unless the following conditions are met: The serving cell's active bandwidth part (BWP) for the user equipment (UE) is configured with the higher-layer parameter PDCCH-Config, which contains two different coresetPoolIndex values ​​in the ControlResourceSet configuration information, and the two Physical Downlink Control Channels (PDCCHs) that schedule two PUSCHs are associated with ControlResourceSets having different coresetPoolIndex values, and the UE reports its ability to support outOfOrderOperationUL-r16 or outOfOrderOperationUL-r18; otherwise, for any two Hybrid Automatic Repeat Request (HARQ) process IDs (IDs) on a given scheduled cell, if the UE is scheduled by the scheduling cell... If a PDCCH ending at symbol i in a cell schedules a PUSCH transmission 1 starting at symbol j, then the UE does not expect a PUSCH transmission starting earlier than the end time of PUSCH transmission 1 to be scheduled from a PDCCH ending at symbol i in the scheduled cell.

[0087] 2. Specific scenarios for mDCI-based mTRP.

[0088] On this Scheduled serving cell, PUSCHs scheduled later in the DCI can be transmitted earlier (i.e., their start time can be earlier than the end time of PUSCHs scheduled earlier in the DCI). Specifically, if the Activated Bandwidth Part (BWP) of the serving cell of a User Equipment (UE) is configured with the higher-layer parameter PDCCH-Config, and this higher-layer parameter contains two different coresetPoolIndex values ​​in the configuration information of the ControlResourceSet, and the two PDCCHs that schedule two PUSCHs are respectively associated with ControlResourceSets with different coresetPoolIndex values, and the UE reports the capability to support outOfOrderOperationUL-r16 or outOfOrderOperationUL-r18, then for any two HARQ process IDs on a given scheduled cell: if the UE schedules a PUSCH transmission 1 that starts at symbol j from a PDCCH associated with a certain coresetPoolIndex value and ends at symbol i, the UE can still schedule a PUSCH transmission that starts transmission earlier than the end time of PUSCH transmission 1 from another PDCCH associated with a different coresetPoolIndex value and whose end time is later than symbol i.

[0089] Optionally, the above OoO rule applies only when the scheduled PUSCH occupies a HARQ process; otherwise, it does not apply. Furthermore, the above OoO rule applies only when the scheduled PUSCH carries an Uplink Shared Channel (UL-SCH) (indicated by setting the UL-SCH indicator field in the scheduling DCI to 1), in which case it will actually occupy a HARQ process.

[0090] II. UE PUSCH preparation procedure time requirements.

[0091] The UE PUSCH preparation procedure time requirement can also be understood as the timing requirement between the UE-side scheduling DCI and the scheduled PUSCH. Specifically, if the first uplink symbol of a transport block's PUSCH allocation is not earlier than symbol L2 after considering the timing advance effect, the UE is required to transmit this transport block; otherwise, the UE may ignore the scheduling DCI that allocated this PUSCH. The first uplink symbol here includes DM-RS (or can be DM-RS), defined by the slot offset K2 and Koffset (if configured), and by the start symbol S and length L of the PUSCH allocation indicated by the Time domain resource assignment field in the scheduling DCI. L2 is defined as the start time of the CP being later than or no earlier than the next or most recent uplink symbol at the target time, where the target time is the time offset T from the end time of the last symbol of the PDCCH carrying the DCI that scheduled this PUSCH. proc,2 =max((N2+d 2,1 +d2)(2048+144)·κ2 -μ ·T C +T ext +T switch ,d 2,2 The time corresponding to the duration.

[0092] The value of N2 is shown in Table 1 below: PUSCH preparation time for PUSCH timing capability 1 or Table 2: PUSCH preparation time for PUSCH timing capability 2.

[0093] Table 1:

[0094] μ <![CDATA[PUSCH preparation time N2[symbols]]]> 0 10 1 12 2 23 3 36 5 144 6 288

[0095] Table 2:

[0096] μ <![CDATA[PUSCH preparation time N2[symbols]]]> 0 5 1 5.5 2 11 (for frequency range 1)

[0097] III. UE Channel State Information (CSI) Calculation Time Requirements.

[0098] The UE CSI computation time requirement primarily considers the additional timeline requirements between the UE-side DCI scheduling and the scheduled PUSCH when the scheduled PUSCH carries aperiodic CSI (A-CSI). It is understood that in this case, the scheduled PUSCH requirement simultaneously satisfies both the UE PUSCH preparation procedure time requirement and the UE CSI computation time requirement.

[0099] The UE can indicate whether to carry A-CSI on the scheduled PUSCH via the CSI request field in the scheduling DCI. When the CSI request field indicates that A-CSI is carried on the scheduled PUSCH, the CSI request field indicates a single aperiodic CSI trigger state in the CSI-AperiodicTriggerStateList configured by the higher layer. Each aperiodic CSI trigger state corresponds to a CSI-ReportConfig list and indicates the resource set ID used for channel and interference measurements for each CSI-ReportConfig.

[0100] The UE is required to provide a valid CSI report for the nth triggered CSI report (which can be understood as the nth CSI report configured in the non-periodic CSI trigger state indicated by the scheduling DCI) when the following two conditions are met:

[0101] Condition 1: The first uplink symbol carrying the corresponding CSI report, after considering the effect of timing advance, is not earlier than symbol Z. ref start;

[0102] Condition 2: The first uplink symbol carrying the nth CSI report is not earlier than symbol Z' after considering the effect of timing advance. ref (n) Begins.

[0103] Condition 1 considers the minimum time interval between the scheduled DCI and the PUSCH carrying the A-CSI when the UE provides valid A-CSI on the scheduled PUSCH.

[0104] Z ref The CP start time is later than or no earlier than the next or most recent uplink symbol of the target time, where the target time is offset by T from the end time of the last symbol of the PDCCH that triggered the CSI report. proc,CSI=(Z)(2048+144)·κ2 -μ ·T C The time corresponding to the duration.

[0105] When Z ref If not satisfied: If there is no HARQ-ACK or transport block multiplexed on this PUSCH, the UE may ignore this scheduling DCI.

[0106] Z = max m＝0,...,M-1 (Z(m)), where M is the number of CSI reports that need to be updated, and Z(m) corresponds to the m-th CSI report that needs to be updated; depending on the different CSI reporting configurations, Z(m) can be Z1, Z2, or Z3. The values ​​of Z1, Z2, and Z3 are shown in Table 3: CSI computation delay requirement 1 or Table 4: CSI computation delay requirement 2.

[0107] Table 3:

[0108]

[0109] Table 4:

[0110]

[0111] It should be noted that when referring to CSI computation delay requirement 2 (see Table 4 above), the UE CSI computation time is significantly longer than the UE PUSCH preparation procedure time. In this case, for a given scheduled serving cell, when a Dynamic Grant (DG) PUSCH carrying A-CSI is scheduled serially with a DG PUSCH not carrying A-CSI, the scheduling of the DG PUSCH not carrying A-CSI may face significant limitations under the OoO rule.

[0112] exist Figure 2In this context, for a given Scheduled serving cell, assuming the network-side device schedules a PUSCH that does not carry A-CSI, considering the UE PUSCH preparation procedure time requirement of N2 = 23 (corresponding to μ = 2), when scheduling a PUSCH that carries A-CSI, it needs to further consider the UE CSI computation time requirement of Z2 = 141 (corresponding to μ = 2). Based on these time requirements, the network-side device first schedules PUSCH0, which does not carry A-CSI, within Slot n-1 in slot n-4, and then schedules PUSCH1, which carries A-CSI, within Slot n+11 in slot n (assuming PUSCH1 needs to carry UL-SCH, i.e., the UL-SCH indicator field in the scheduling DCI indicates 0). At this point, based on the OoO rule for scheduling DCI and scheduled PUSCH, the network-side device cannot further schedule other PUSCHs between Slot n and Slot n+10 on this Scheduled serving cell, thus restricting PUSCH scheduling and potentially severely impacting uplink throughput performance.

[0113] based on Figure 2 It is known that for a given Scheduled serving cell, if a DG PUSCH carrying A-CSI has already been scheduled following the OoO rule, further scheduling a DG PUSCH that does not carry A-CSI may present significant limitations. Furthermore, in multi-service multiplexing scenarios, after scheduling a DG PUSCH carrying A-CSI, when more urgent data arrives and needs to be transmitted promptly, the aforementioned limitations may affect the transmission performance of this urgent data. Therefore, it is necessary to introduce corresponding solutions to avoid or mitigate the impact of the OoO rule for scheduling DCI and scheduled PUSCH on DG PUSCH transmission. To this end, the uplink transmission method of this application is proposed.

[0114] The uplink transmission method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0115] Reference Figure 3 This application provides an uplink transmission method, such as... Figure 3 As shown, the uplink transmission method includes:

[0116] Step 301, the terminal performs at least one of the following:

[0117] The terminal transmits the first physical uplink shared channel (PUSCH) according to the first rule;

[0118] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the terminal expects the second PUSCH not to apply the first rule.

[0119] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, the terminal does not expect to always carry the A-CSI report corresponding to the A-CSI measurement on the third PUSCH, which is scheduled by the first DCI.

[0120] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0121] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0122] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0123] If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time when the first target PUSCH occupies the target processing channel, and the target start time of the second target PUSCH is the start time when the second target PUSCH occupies the target processing channel.

[0124] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0125] In this embodiment, the terminal transmitting the first PUSCH according to the first rule can be understood as transmitting the first PUSCH when the first PUSCH satisfies any one of the rules in the first rule, or in other words, the terminal expects the first PUSCH to be transmitted to satisfy any one of the rules in the first rule. The first PUSCH can be understood as the PUSCH that the terminal expects to carry UL-SCH, i.e., DGPUSCH with UL-SCH. Further, the first PUSCH can also be the PUSCH that the terminal expects to carry A-CSI, i.e., DGPUSCH with A-CSI and UL-SCH. Alternatively, the first PUSCH can also be the PUSCH that the terminal expects not to carry A-CSI, i.e., DG PUSCH without A-CSI and UL-SCH.

[0126] Optionally, when the start time of the first target PUSCH is not earlier than the end time of the second target PUSCH, or when the start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH, it can be considered that the first target PUSCH and the second target PUSCH satisfy the OoO rule, that is, the first rule can be understood as the OoO rule at this time.

[0127] When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, and the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH, it can be considered that the first target PUSCH and the second target PUSCH do not satisfy the OoO rule, but satisfy the relaxed OoO rule. That is, the first rule can be understood as the relaxed OoO rule in this case. In the embodiments of this application, since the relaxed OoO rule is defined in the first rule, PUSCH transmission can be performed whether the OoO rule or the relaxed OoO rule is satisfied. Therefore, the impact of the OoO rule on urgent data transmission is reduced, and the uplink transmission performance is improved.

[0128] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the terminal expects the second PUSCH not to apply the first rule. This can be understood as the network-side device only triggering the second PUSCH, thus avoiding the application of the OoO rule and improving uplink transmission performance. In this embodiment, the second PUSCH can be understood as a DG PUSCH that the terminal expects to carry A-CSI but not UL-SCH, i.e., a DG PUSCH with A-CSI and without UL-SCH.

[0129] Optionally, when the first downlink control information (DCI) is used to trigger A-CSI measurements, the terminal does not expect to always carry the A-CSI report corresponding to the A-CSI measurement on the third PUSCH. This can be understood as follows: for A-CSI triggering scenarios, the network-side device decouples the scheduling / determination of the A-CSI triggering DCI from the scheduling of the A-CSI reporting PUSCH to avoid the impact of long PUSCH preparation times on PUSCH scheduling when combined with OoO rules. For example, when the network-side device uses the first DCI to trigger A-CSI reporting, it does not mean that the corresponding A-CSI report is carried by the DG PUSCH scheduled by this first DCI. Accordingly, a corresponding mechanism can be introduced to determine when and by which PUSCH the A-CSI report is carried.

[0130] Optionally, the aforementioned target processing channel can be understood as a subset of processing channels, that is, the first target PUSCH and the second target PUSCH are associated with the same subset of processing channels, and each subset of processing channels includes at least one UL-SCH processing channel.

[0131] It should be noted that, in other embodiments, the first rule described above may further include, but is not limited to, the following rules:

[0132] The start time of the first target PUSCH is no earlier than the start time of the second target PUSCH;

[0133] The end time of the first target PUSCH is no earlier than the end time of the second target PUSCH.

[0134] In this embodiment, the terminal performs at least one of the following: the terminal transmits a first Physical Uplink Shared Channel (PUSCH) according to a first rule; when a second PUSCH is scheduled to carry aperiodic Channel State Information (A-CSI), the terminal expects the second PUSCH not to apply the first rule; when a first Downlink Control Information (DCI) is used to trigger an A-CSI measurement, the terminal does not expect to always carry an A-CSI report corresponding to the A-CSI measurement on a third PUSCH, which is scheduled by the first DCI; wherein, the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following: the start time of the first target PUSCH is not earlier than the end time of the second target PUSCH; the start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH. The target PUSCH's end time is determined by the following: If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, and the target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel. The first target PUSCH and the second target PUSCH correspond to the same first frequency domain object. The target time for scheduling the first target PUSCH's first target DCI is later than the target time for scheduling the second target PUSCH's second target DCI. The target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object. This reduces the impact of the OoO rule on emergency data transmission and improves uplink transmission performance.

[0135] Optionally, in some embodiments, the first target PUSCH and / or the second target PUSCH satisfy predefined requirements, said predefined requirements including at least one of the following:

[0136] PUSCH is dynamically scheduled by DCI;

[0137] PUSCH carries the uplink shared channel;

[0138] PUSCH transmission requires the HARQ process to be used.

[0139] Optionally, in some embodiments, the target time is any of the following:

[0140] The start or end time of DCI;

[0141] The start or end time of the first time domain unit of DCI;

[0142] The start or end time of the first time domain unit of DCI;

[0143] The start or end time of the second time-domain unit of the DCI is detected;

[0144] The start or end time of the DCI's Control Resource Set (CORESET) is detected;

[0145] The start or end time of the second time-domain unit where the CORESET of the DCI is located is detected;

[0146] The start or end time of the detected monitoring occasion for the Physical Downlink Control Channel (PDCCH) of the DCI;

[0147] The start or end time of the second time-domain unit where the DCI's PDCCH monitoring occasion is located is detected.

[0148] In this embodiment, the first or second time-domain unit is a unit divided in the time domain. It can be a system time-domain unit, such as a radio frame, sub-frame, slot, sub-slot, or symbol, or an absolute time unit, such as a second (s) or millisecond (ms). Optionally, a single second time-domain unit may include at least one first time-domain unit. For example, the first time-domain unit includes, but is not limited to, a symbol, and the second time-domain unit includes, but is not limited to, a slot.

[0149] Optionally, the target time of the first target DCI for scheduling the first target PUSCH being later than the target time of the second target DCI for scheduling the second target PUSCH can be understood as: the scheduling of the first target PUSCH is later than the scheduling of the second target PUSCH, that is, the first target PUSCH is the PUSCH scheduled later, and the second target PUSCH is the PUSCH scheduled earlier.

[0150] Optionally, in some embodiments, the first rule further includes at least one of the following:

[0151] The time when the first target PUSCH is ready to be processed is earlier than or no later than the target start time;

[0152] The transmission start time of the first target PUSCH is earlier than or no later than the target start time;

[0153] The end time of the transmission of the first target PUSCH is earlier than or no later than the start time of the target.

[0154] In this embodiment of the application, the above-mentioned preparation process includes completing the baseband processing of the first target PUSCH, and the transmission of the first target PUSCH can be performed after the preparation process of the first target PUSCH is completed.

[0155] Optionally, in some embodiments, the target start time is earlier than or no later than the start time of the second target PUSCH, and the interval between the target start time and the start time of the second target PUSCH is the first duration corresponding to the second target PUSCH.

[0156] In this embodiment of the application, the aforementioned first duration can be understood as T1, and T1 can be determined based on any of the following:

[0157] The terminal reports its capabilities to the network-side equipment via capability signaling.

[0158] As agreed in the agreement;

[0159] Configured by higher-level signaling.

[0160] Optionally, in some embodiments, the start time of the second target PUSCH is determined based on any of the following:

[0161] The first moment;

[0162] First moment and time in advance;

[0163] Wherein, the first moment is any one of the following:

[0164] The start time of the first time domain unit occupied by the second target PUSCH;

[0165] The start time of the first time domain unit of the first data carried by the second target PUSCH;

[0166] The start time of the first time-domain unit of the first bearer demodulation reference signal (DMRS) occupied by the second target PUSCH;

[0167] The start time of the second time domain unit or the first second time domain unit where the second target PUSCH is located.

[0168] In this embodiment, the first time-domain unit may include, but is not limited to, a symbol. In some embodiments, the start time of the first time-domain unit carrying data can be understood as the start time of the first data symbol; the start time of the first time-domain unit carrying demodulation reference signals can be understood as the start time of the first DMRS symbol, such as the start time of the first dedicated demodulation reference signal (DM-RS) symbol. For example, the first time may be the start time of the first symbol occupied by the second target PUSCH, the start time of the first data symbol, or the start time of the first DM-RS symbol.

[0169] Optionally, in some embodiments, the second time-domain unit may include, but is not limited to, a slot. For example, when considering PUSCH repetition or Transport Block over Multiple Slots (TBoMS), the first time may be the start time of the first second time-domain unit where the second target PUSCH is located.

[0170] Optionally, in some embodiments, the first duration satisfies any one of the following:

[0171] The first duration is the same for all target PUSCHs scheduled by the terminal on any frequency domain object.

[0172] The first duration is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object.

[0173] The first duration corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on the first attribute or a combination of the first attributes.

[0174] The first duration corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on the first attribute or a combination of the first attributes.

[0175] Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

[0176] In this embodiment of the application, the aforementioned "same first duration" can be understood as the first duration having the same value. The fact that the first duration is the same for all target PUSCHs scheduled by the terminal on any frequency domain object can be understood as: applying a single, uniform first duration value to any DG PUSCH with UL-SCH scheduled by the terminal on any frequency domain object.

[0177] The fact that the first duration is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object can be understood as: applying a specific value to the first duration of each frequency domain object, and uniformly applying the specific value corresponding to this frequency domain object to any DG PUSCH with UL-SCH corresponding to a certain frequency domain object.

[0178] The determination of the first duration corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object based on the first attribute or a combination of the first attributes can be understood as follows: for a DG PUSCH with UL-SCH corresponding to a certain frequency domain object, the first attribute or a combination of the first attributes is distinguished and the corresponding specific value is applied.

[0179] The determination of the first duration corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object based on the first attribute or a combination of the first attributes can be understood as: for DG PUSCHs with UL-SCHs scheduled by the terminal on any frequency domain object, distinguishing the first attribute or a combination of the first attributes, and applying the corresponding specific value.

[0180] Optionally, in some embodiments, the second duration for which the target PUSCH occupies the target processing channel is determined based on at least one of the following:

[0181] The duration reported by the terminal;

[0182] The duration agreed upon in the agreement;

[0183] The third duration is determined based on the first duration corresponding to the target PUSCH, where the first duration is the start time when the target PUSCH occupies the target processing channel;

[0184] Duration of high-level signaling configuration;

[0185] Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

[0186] Optionally, in some embodiments, the third duration satisfies any one of the following:

[0187] The third duration is equal to the first duration;

[0188] The third duration is equal to the sum of the first duration and the duration of the target PUSCH;

[0189] The third duration is equal to the sum of the first duration, the duration of the target PUSCH, and the first offset value;

[0190] The third duration is equal to the sum of the first duration and the second offset value.

[0191] Optionally, in some embodiments, the first information satisfies at least one of the following:

[0192] The first information is the same for all target PUSCHs scheduled by the terminal on any frequency domain object;

[0193] The first information is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object;

[0194] The first information corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on a first attribute or a combination of first attributes.

[0195] The first information corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on a first attribute or a combination of first attributes.

[0196] The first information includes at least one of the second duration, the first offset value, and the second offset value.

[0197] Optionally, in some embodiments, the first attribute or combination of the first attributes includes at least one of the following:

[0198] PUSCH timing capability;

[0199] First subcarrier spacing (SCS);

[0200] Transport block size;

[0201] The first number of time-domain cells occupied by PUSCH;

[0202] Duration of PUSCH;

[0203] The number of resource units corresponding to PUSCH, the number of data resource units, or the number of demodulation reference signal resource units;

[0204] The time-domain location of the first time-domain unit or resource unit carrying the demodulation reference signal in the PUSCH;

[0205] The type of the first time domain unit of PUSCH, or the contents of the first time domain unit of PUSCH;

[0206] Does the scheduling DCI corresponding to PUSCH simultaneously trigger a bandwidth portion BWP switch?

[0207] PUSCH physical layer priority (PHY priority);

[0208] Whether PUSCH reuses uplink control information (UCI);

[0209] When PUSCH multiplexes UCI, the information of the physical uplink control channel PUCCH with time-domain overlap is included.

[0210] When PUSCH reuses UCI, does it involve UCI reuse across physical layer priorities?

[0211] When PUSCH reuses UCI, it reuses either the UCI type or a combination of UCI types.

[0212] This can be understood as follows: each of the listed items corresponds to an attribute; the first attribute includes any one of the listed items; the first attribute combination includes at least one of the listed items.

[0213] In this embodiment, the type of the first time-domain unit of the PUSCH may include a first time-domain unit carrying data and a first time-domain unit carrying DM-RS. For example, when the first time-domain unit is a symbol, the type of the first time-domain unit of the PUSCH may include data symbols and DM-RS symbols. The content contained in the first time-domain unit of the PUSCH can be understood as whether the first time-domain unit of the PUSCH contains only data REs or only DM-RS REs.

[0214] Information about time-domain overlapping PUCCHs may include, but is not limited to, at least one of the following: the number of time-domain overlapping PUCCHs; the relationship between the time-domain and / or frequency-domain positions of at least one time-domain overlapping PUCCH.

[0215] UCI types include, but are not limited to, at least one of the following: HARQ-ACK, SR, and CSI. Each UCI type can further be considered for its corresponding temporal behavior. Temporal behavior includes periodic, semi-persistent, or aperiodic behaviors.

[0216] Optionally, in some embodiments, the first SCS includes any of the following:

[0217] PUSCH's SCS;

[0218] The SCS of the scheduling DCI corresponding to PUSCH;

[0219] The maximum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH.

[0220] The minimum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH.

[0221] The SCS corresponding to the largest or smallest of the first duration determined by the SCS based on PUSCH and the first duration determined by the SCS based on the scheduling DCI corresponding to PUSCH.

[0222] Optionally, in some embodiments, the method further includes:

[0223] In the case where the second frequency domain object corresponds to multiple uplink shared channel processing channels, the terminal performs a first operation and / or a second operation before transmitting the first PUSCH according to the first rule;

[0224] The first operation includes at least one of the following:

[0225] Assign the first PUSCH to the first PUSCH subset;

[0226] Determine the number of second PUSCH subsets for all scheduled PUSCH partitions;

[0227] Wherein, the second frequency domain object is the frequency domain object corresponding to the first PUSCH, the first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset, and each second PUSCH subset satisfies at least one of the following:

[0228] Includes all PUSCHs associated with the first processing channel subset;

[0229] Corresponding to the first processing channel subset;

[0230] Any two PUSCHs included satisfy the first rule;

[0231] The first processing channel subset includes at least one uplink shared channel processing channel among a plurality of uplink shared channel processing channels corresponding to the second frequency domain object.

[0232] The second operation includes at least one of the following:

[0233] If the fourth PUSCH that has already been scheduled finishes occupying the second processing channel subset, the terminal will remove the fourth PUSCH from the third PUSCH subset.

[0234] The terminal re-determines the number of the second PUSCH subset;

[0235] Before performing the second operation, the terminal has already allocated the fourth PUSCH to the third PUSCH subset, and the third PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset; the third PUSCH subset corresponds to the second processing channel subset.

[0236] Optionally, in some embodiments, assigning the first PUSCH to a subset of the first PUSCH includes at least one of the following:

[0237] If all scheduled PUSCHs other than the first PUSCH on the second frequency domain object have finished occupying the uplink shared channel processing channel corresponding to the second frequency domain object, a new first PUSCH subset is created, and the first PUSCH is allocated to the newly created first PUSCH subset.

[0238] If at least one fourth PUSCH subset exists in the at least one second PUSCH subset, the first PUSCH is assigned to the first fourth PUSCH subset determined by traversing each of the second PUSCH subsets in a predefined subset order, wherein the first fourth PUSCH subset is the first PUSCH subset and the fourth PUSCH subset is a single second PUSCH subset that satisfies the first condition.

[0239] If the fourth PUSCH subset does not exist in at least one second PUSCH subset, a new first PUSCH subset is created, and the first PUSCH is assigned to the newly created first PUSCH subset.

[0240] Wherein, the second attribute of each of the at least one second PUSCH subset is the same; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

[0241] In this embodiment of the application, the second attribute may include the corresponding DG PUSCH with UL-SCH attribute (e.g., the corresponding PHY priority), the processing capacity of the expected allocated UL-SCH processing channel (e.g., processing time), etc.

[0242] Optionally, in some embodiments, the at least one second PUSCH subset is divided into at least one second PUSCH subset group based on the second attribute of each second PUSCH subset, wherein the second attribute of each second PUSCH subset in each second PUSCH subset group is the same, and the assignment of the first PUSCH to the first PUSCH subset includes at least one of the following:

[0243] If a first PUSCH subset group does not exist in at least one second PUSCH subset group, a new first PUSCH subset group is created, and the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group.

[0244] If a first PUSCH subset group exists in the at least one second PUSCH subset group, and at least one fifth PUSCH subset exists in the first PUSCH subset group, the first PUSCH is assigned to the first fifth PUSCH subset determined by traversing each of the second PUSCH subsets in the first PUSCH subset group based on a predefined subset order. The first fifth PUSCH subset is the first PUSCH subset, and the fifth PUSCH subset is a single second PUSCH subset in the first PUSCH subset group that satisfies the first condition.

[0245] If a first PUSCH subset exists in at least one second PUSCH subset group, and the fifth PUSCH subset does not exist in the first PUSCH subset group, the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group.

[0246] Wherein, the first PUSCH subset group matches the first PUSCH; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

[0247] Optionally, in some embodiments, the predefined subset order is determined based on at least one of the following:

[0248] The creation time of the PUSCH subset;

[0249] Physical layer priority corresponding to the PUSCH subset;

[0250] The number of PUSCHs contained in the PUSCH subset;

[0251] The start or end time of the scheduling DCI corresponding to PUSCH in the PUSCH subset;

[0252] The start or end time of the first control resource set where the scheduling DCI corresponding to the PUSCH in the PUSCH subset is located.

[0253] The start or end time of the second time-domain unit where the first control resource set is located;

[0254] The start or end time of PUSCH in the PUSCH subset;

[0255] The start or end time of the second time-domain unit where PUSCH is located in the PUSCH subset.

[0256] Optionally, in some embodiments, the method further includes:

[0257] The terminal determines the number of uplink shared channel processing channels that the scheduled PUSCH needs to occupy based on the number of the second PUSCH subsets and the number of uplink shared channel processing channels contained in the first processing channel subset corresponding to each second PUSCH subset.

[0258] In this embodiment of the application, the number of uplink shared channel processing channels that the scheduled PUSCHs need to occupy is determined in order to avoid the number of uplink shared channel processing channels that all scheduled PUSCHs need to occupy exceeding the maximum number of parallel uplink shared channel processing channels supported by the terminal.

[0259] Optionally, in some embodiments, each of the first processing channel subsets includes a single uplink shared channel processing channel, or each of the first processing channel subsets includes M uplink shared channel processing channels;

[0260] M is determined based on at least one of the following:

[0261] The number of PUSCHs contained in the corresponding second PUSCH subset;

[0262] The attributes of the PUSCH contained in the corresponding second subset of PUSCH;

[0263] The corresponding second subset of PUSCH contains the attributes of the scheduling DCI corresponding to the PUSCH.

[0264] In this embodiment, the PUSCH included in the second PUSCH subset can be understood as DG PUSCH with UL-SCH. In some embodiments, when M is determined based on the number of PUSCHs included in the corresponding second PUSCH subset, if the number of PUSCHs included in the second PUSCH subset does not exceed a predefined threshold, the second PUSCH subset occupies a single uplink shared channel processing channel; if the number of PUSCHs included in the second PUSCH subset exceeds the predefined threshold, the second PUSCH subset may occupy two uplink shared channel processing channels.

[0265] Optionally, the attributes of the PUSCH mentioned above include at least one of the following: number of allocated symbols, number of data symbols, number of pilot symbols, number of layers, frequency domain resource allocation type, number of allocated frequency domain resources (for resource allocation type 0, it can be the number of RBGs; for resource allocation type 1, it can be the number of PRBs), number of allocated REs, number of data REs, number of pilot REs, TB size, and PHYpriority.

[0266] Optionally, when different second PUSCH subsets have different attributes, different second PUSCH subsets may occupy only the UL-SCH processing channel that matches their attributes.

[0267] Optionally, when the UE detects that a scheduled DG PUSCH with UL-SCH no longer involves (or no longer corresponds to) a UL-SCH processing channel, the number of parallel UL-SCH processing channels required for all scheduled DG PUSCH with UL-SCH that still involve UL-SCH processing channels (excluding this scheduled DG PUSCH with UL-SCH that no longer involves UL-SCH processing channels) can be re-determined. Here, "no longer involved" can be understood as the PUSCH ending its UL-SCH processing channel usage.

[0268] Optionally, in some embodiments, the frequency domain object includes any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain element, frequency band, frequency band combination, and frequency range; or, the frequency domain object includes at least one first frequency domain object, the first frequency domain object including any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain element, frequency band, frequency band combination, and frequency range.

[0269] Optionally, in some embodiments, the method further includes any one of the following:

[0270] The terminal expects that the number of uplink shared channel processing channels occupied by the scheduled PUSCHs does not exceed the maximum number of uplink shared channel processing channels that the terminal supports for parallel processing.

[0271] The terminal expects any scheduled PUSCH to be assigned to the corresponding uplink shared channel processing channel.

[0272] Optionally, in this embodiment, the UE does not expect that the number of parallel UL-SCH processing channels required by a DGPUSCH with UL-SCH that has been scheduled and still involves UL-SCH processing channels exceeds the maximum number of UL-SCH processing channels that the UE has capable of parallel processing. Alternatively, the UE does not expect that any DGPUSCH with UL-SCH that has been scheduled and still involves UL-SCH processing channels cannot be allocated to the corresponding UL-SCH processing channel.

[0273] It should be noted that the uplink processing method in this application embodiment can be applied to single TRP scenarios or multiple TRP scenarios. For multiple TRP scenarios, based on UE capability reporting, one of the following can be adopted:

[0274] For the DG PUSCH with UL-SCH scheduling of each TRP, the above-described scheme of this application is applied. Generally, the scenario of multi-TRP based on multiple DCI (mDCI-based mTRP) is mainly considered. In this case, the DG PUSCH with UL-SCH scheduling of each TRP is relatively independent, and the UE can clearly distinguish the DG PUSCH with UL-SCH scheduling for each TRP.

[0275] The scheme of this application is uniformly applied to all TRPs. That is, when the UE applies the scheme of this application, it does not distinguish the correspondence between DGPUSCH with UL-SCH scheduling and TRP.

[0276] Optionally, in some embodiments, when multiple TRPs are configured, the fifth PUSCH satisfies any of the following:

[0277] Corresponds to the target TRP among the plurality of TRPs;

[0278] Corresponds to any one of the plurality of TRPs;

[0279] Wherein, the fifth PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target TRP is one of the plurality of TRPs.

[0280] In this application embodiment, it can be used for single PUSCH scheduling without repetition scenarios. For single PUSCH scheduling with repetition or single PUSCH scheduling with TBoMS using Transport Block over Multiple Slots (TBoMS), the scheme of this application can be applied to each PUSCH transmission involved (e.g., for a PUSCH repetition of PUSCH repetition type A, or an actual repetition of PUSCH repetition type B, or a PUSCH transmission of TBoMS). Optionally, when a PUSCH repetition or TBoMS expects to occupy a UL-SCH processing channel, all repetitions, all TBoMS, or all PUSCH transmissions corresponding to a single PUSCH occupy the same UL-SCH processing channel of the same frequency domain object (e.g., a scheduled serving cell).

[0281] Optionally, in some embodiments, the sixth PUSCH satisfies at least one of the following:

[0282] When using type A repetition transmission, the sixth PUSCH is any one of the at least one PUSCH repetition transmissions corresponding to a PUSCH.

[0283] When using type B repetition transmission, the sixth PUSCH is any one of the at least one actual PUSCH repetition transmissions corresponding to a PUSCH.

[0284] In the case of using multi-timeslot transport block (TBoMS) transmission, the sixth PUSCH is any one of the PUSCH transmissions in at least one PUSCH transmission corresponding to a TBoMS transmission.

[0285] In the case where a single DCI can schedule multiple PUSCHs, the sixth PUSCH is any one of at least one PUSCH scheduled by a DCI.

[0286] The sixth PUSCH is either the first PUSCH, the second PUSCH, or the third PUSCH.

[0287] In this embodiment, it can be used in a multi-PUSCH scheduling scenario. For multi-PUSCH scheduling, the above scheme can be applied to each PUSCH scheduled by the DCI. Optionally, when a scheduled PUSCH expects to occupy a UL-SCH processing channel, all PUSCHs scheduled by the same DCI occupy the same UL-SCH processing channel of the same frequency domain object (e.g., a scheduled serving cell).

[0288] Optionally, in some embodiments, when a single DCI can schedule PUSCHs on multiple serving cells, the seventh PUSCH is any one of at least one PUSCH scheduled by a DCI on the target serving cell.

[0289] Wherein, the seventh PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target serving cell is any one of the at least one serving cell in the one DCI scheduling.

[0290] In this embodiment, the scheme can be applied to a multi-cell scheduling scenario. For multi-cell scheduling, the above scheme can be applied separately to the DCI and each PUSCH scheduled on each scheduled serving cell. When the frequency domain object is a scheduled serving cell, the UL-SCH processing channels expected to be occupied by each PUSCH scheduled on each scheduled serving cell are independent of each other.

[0291] Reference Figure 4 This application also provides an uplink transmission method, such as... Figure 4 As shown, the uplink transmission method includes:

[0292] Step 401, the network-side device performs at least one of the following:

[0293] Network-side devices schedule and receive the first physical uplink shared channel (PUSCH) according to the first rule;

[0294] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the network-side device guarantees that the first rule will not be applied to the second PUSCH.

[0295] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, the network-side device is able to receive an A-CSI report corresponding to the A-CSI measurement on an uplink channel different from the third PUSCH, wherein the third PUSCH is scheduled by the first DCI.

[0296] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0297] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0298] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0299] When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, the time when preparation for processing is completed, the time of transmission start or transmission end. The target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel.

[0300] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0301] Optionally, the first target PUSCH and / or the second target PUSCH meet predefined requirements, which include at least one of the following:

[0302] PUSCH is dynamically scheduled by DCI;

[0303] PUSCH carries the uplink shared channel;

[0304] PUSCH transmission requires the HARQ process to be used.

[0305] Optionally, the target time is any one of the following:

[0306] The start or end time of DCI;

[0307] The start or end time of the first time domain unit of DCI;

[0308] The start or end time of the first time domain unit of DCI;

[0309] The start or end time of the second time-domain unit of the DCI is detected;

[0310] The start or end time of the DCI control resource set CORESET was detected;

[0311] The start or end time of the second time-domain unit where the CORESET of the DCI is located is detected;

[0312] The start or end time of the detected monitoring occasion for the Physical Downlink Control Channel (PDCCH) of the DCI;

[0313] The start or end time of the second time-domain unit where the DCI's PDCCH monitoring occasion is located is detected.

[0314] Optionally, the first rule further includes at least one of the following:

[0315] The time when the first target PUSCH is ready to be processed is earlier than or no later than the target start time;

[0316] The transmission start time of the first target PUSCH is earlier than or no later than the target start time;

[0317] The end time of the transmission of the first target PUSCH is earlier than or no later than the start time of the target.

[0318] Optionally, the target start time is earlier than or no later than the start time of the second target PUSCH, and the interval between the target start time and the start time of the second target PUSCH is the first duration corresponding to the second target PUSCH.

[0319] Optionally, the start time of the second target PUSCH is determined based on any of the following:

[0320] The first moment;

[0321] First moment and time in advance;

[0322] Wherein, the first moment is any one of the following:

[0323] The start time of the first time domain unit occupied by the second target PUSCH;

[0324] The start time of the first time domain unit of the first data carried by the second target PUSCH;

[0325] The start time of the first time-domain unit of the first bearer demodulation reference signal occupied by the second target PUSCH;

[0326] The start time of the second time domain unit or the first second time domain unit where the second target PUSCH is located.

[0327] Optionally, the first duration satisfies any one of the following:

[0328] The first duration is the same for all target PUSCHs scheduled by the terminal on any frequency domain object.

[0329] The first duration is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object.

[0330] The first duration corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on the first attribute or a combination of the first attributes.

[0331] The first duration corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on the first attribute or a combination of the first attributes.

[0332] Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

[0333] Optionally, the second duration for which the target PUSCH occupies the target processing channel is determined based on at least one of the following:

[0334] The duration reported by the terminal;

[0335] The duration agreed upon in the agreement;

[0336] The third duration is determined based on the first duration corresponding to the target PUSCH, where the first duration is the start time when the target PUSCH occupies the target processing channel;

[0337] Duration of high-level signaling configuration;

[0338] Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

[0339] Optionally, the third duration satisfies any one of the following:

[0340] The third duration is equal to the first duration;

[0341] The third duration is equal to the sum of the first duration and the duration of the target PUSCH;

[0342] The third duration is equal to the sum of the first duration, the duration of the target PUSCH, and the first offset value;

[0343] The third duration is equal to the sum of the first duration and the second offset value.

[0344] Optionally, the first information satisfies at least one of the following:

[0345] The first information is the same for all target PUSCHs scheduled by the terminal on any frequency domain object;

[0346] The first information is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object;

[0347] The first information corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on a first attribute or a combination of first attributes.

[0348] The first information corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on a first attribute or a combination of first attributes.

[0349] The first information includes at least one of the second duration, the first offset value, and the second offset value.

[0350] Optionally, the first attribute or combination of the first attributes includes at least one of the following:

[0351] PUSCH timing capability;

[0352] First subcarrier spacing (SCS);

[0353] Transport block size;

[0354] The first number of time-domain cells occupied by PUSCH;

[0355] Duration of PUSCH;

[0356] The number of resource units corresponding to PUSCH, the number of data resource units, or the number of demodulation reference signal resource units;

[0357] The time-domain location of the first time-domain unit or resource unit carrying the demodulation reference signal in the PUSCH;

[0358] The type of the first time domain unit of PUSCH, or the contents of the first time domain unit of PUSCH;

[0359] Does the scheduling DCI corresponding to PUSCH simultaneously trigger a bandwidth portion BWP switch?

[0360] PUSCH physical layer priority;

[0361] Whether PUSCH reuses uplink control information (UCI);

[0362] When PUSCH multiplexes UCI, the information of the physical uplink control channel PUCCH with time-domain overlap is included.

[0363] When PUSCH reuses UCI, does it involve UCI reuse across physical layer priorities?

[0364] When PUSCH reuses UCI, it reuses either the UCI type or a combination of UCI types.

[0365] Optionally, the first SCS includes any of the following:

[0366] PUSCH's SCS;

[0367] The SCS of the scheduling DCI corresponding to PUSCH;

[0368] The maximum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH.

[0369] The minimum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH.

[0370] The SCS corresponding to the largest or smallest of the first duration determined by the SCS based on PUSCH and the first duration determined by the SCS based on the scheduling DCI corresponding to PUSCH.

[0371] Optionally, the method further includes:

[0372] In the case where the second frequency domain object corresponds to multiple uplink shared channel processing channels, the network-side device performs a first operation and / or a second operation before transmitting the first PUSCH according to the first rule;

[0373] The first operation includes at least one of the following:

[0374] Assign the first PUSCH to the first PUSCH subset;

[0375] Determine the number of second PUSCH subsets for all scheduled PUSCH partitions;

[0376] Wherein, the second frequency domain object is the frequency domain object corresponding to the first PUSCH, the first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset, and each second PUSCH subset satisfies at least one of the following:

[0377] Includes all PUSCHs associated with the first processing channel subset;

[0378] Corresponding to the first subset of processing channels;

[0379] Any two PUSCHs included satisfy the first rule;

[0380] The first processing channel subset includes at least one uplink shared channel processing channel among a plurality of uplink shared channel processing channels corresponding to the second frequency domain object.

[0381] The second operation includes at least one of the following:

[0382] If the fourth PUSCH that has already been scheduled finishes occupying the second processing channel subset, the network-side device will remove the fourth PUSCH from the third PUSCH subset;

[0383] The network-side device redetermines the number of the second PUSCH subset;

[0384] Before performing the second operation, the network-side device has already allocated the fourth PUSCH to the third PUSCH subset, and the third PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset; the third PUSCH subset corresponds to the second processing channel subset.

[0385] Optionally, assigning the first PUSCH to a subset of the first PUSCH includes at least one of the following:

[0386] If all scheduled PUSCHs other than the first PUSCH on the second frequency domain object have finished occupying the uplink shared channel processing channel corresponding to the second frequency domain object, a new first PUSCH subset is created, and the first PUSCH is allocated to the newly created first PUSCH subset.

[0387] If at least one fourth PUSCH subset exists in the at least one second PUSCH subset, the first PUSCH is assigned to the first fourth PUSCH subset determined by traversing each of the second PUSCH subsets in a predefined subset order, wherein the first fourth PUSCH subset is the first PUSCH subset and the fourth PUSCH subset is a single second PUSCH subset that satisfies the first condition.

[0388] If the fourth PUSCH subset does not exist in at least one second PUSCH subset, a new first PUSCH subset is created, and the first PUSCH is assigned to the newly created first PUSCH subset.

[0389] Wherein, the second attribute of each of the at least one second PUSCH subset is the same; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

[0390] Optionally, the at least one second PUSCH subset is divided into at least one second PUSCH subset group based on the second attribute of each second PUSCH subset, wherein the second attribute of each second PUSCH subset in each second PUSCH subset group is the same, and the assignment of the first PUSCH to the first PUSCH subset includes at least one of the following:

[0391] If a first PUSCH subset group does not exist in at least one second PUSCH subset group, a new first PUSCH subset group is created, and the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group.

[0392] If a first PUSCH subset group exists in the at least one second PUSCH subset group, and at least one fifth PUSCH subset exists in the first PUSCH subset group, the first PUSCH is assigned to the first fifth PUSCH subset determined by traversing each of the second PUSCH subsets in the first PUSCH subset group based on a predefined subset order. The first fifth PUSCH subset is the first PUSCH subset, and the fifth PUSCH subset is a single second PUSCH subset in the first PUSCH subset group that satisfies the first condition.

[0393] If a first PUSCH subset exists in at least one second PUSCH subset group, and the fifth PUSCH subset does not exist in the first PUSCH subset group, the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group.

[0394] Wherein, the first PUSCH subset group matches the first PUSCH; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

[0395] Optionally, the order of the predefined subsets is determined based on at least one of the following:

[0396] The creation time of the PUSCH subset;

[0397] Physical layer priority corresponding to the PUSCH subset;

[0398] The number of PUSCHs contained in the PUSCH subset;

[0399] The start or end time of the scheduling DCI corresponding to PUSCH in the PUSCH subset;

[0400] The start or end time of the first control resource set where the scheduling DCI corresponding to the PUSCH in the PUSCH subset is located.

[0401] The start or end time of the second time-domain unit where the first control resource set is located;

[0402] The start or end time of PUSCH in the PUSCH subset;

[0403] The start or end time of the second time-domain unit where PUSCH is located in the PUSCH subset.

[0404] Optionally, the method further includes:

[0405] The network-side device determines the number of uplink shared channel processing channels that the scheduled PUSCH needs to occupy based on the number of the second PUSCH subset and the number of uplink shared channel processing channels contained in the first processing channel subset corresponding to each second PUSCH subset.

[0406] Optionally, each of the first processing channel subsets includes a single uplink shared channel processing channel, or each of the first processing channel subsets includes M uplink shared channel processing channels;

[0407] M is determined based on at least one of the following:

[0408] The number of PUSCHs contained in the corresponding second PUSCH subset;

[0409] The attributes of the PUSCH contained in the corresponding second subset of PUSCH;

[0410] The corresponding second subset of PUSCH contains the attributes of the scheduling DCI corresponding to the PUSCH.

[0411] Optionally, the frequency domain object includes any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range; or, the frequency domain object includes at least one first frequency domain object, the first frequency domain object including any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range.

[0412] Optionally, the method further includes any of the following:

[0413] The network-side device expects that the number of uplink shared channel processing channels occupied by the scheduled PUSCHs does not exceed the maximum number of uplink shared channel processing channels supported by the terminal for parallel processing.

[0414] The network-side device expects any scheduled PUSCH to be assigned to the corresponding uplink shared channel processing channel.

[0415] Optionally, when multiple TRPs are configured, the fifth PUSCH satisfies any of the following:

[0416] Corresponds to the target TRP among the plurality of TRPs;

[0417] Corresponds to any one of the plurality of TRPs;

[0418] Wherein, the fifth PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target TRP is one of the plurality of TRPs.

[0419] Optionally, the sixth PUSCH satisfies at least one of the following:

[0420] When using type A repetition transmission, the sixth PUSCH is any one of the at least one PUSCH repetition transmissions corresponding to a PUSCH.

[0421] When using type B repetition transmission, the sixth PUSCH is any one of the at least one actual PUSCH repetition transmissions corresponding to a PUSCH.

[0422] In the case of using multi-timeslot transport block (TBoMS) transmission, the sixth PUSCH is any one of the PUSCH transmissions in at least one PUSCH transmission corresponding to a TBoMS transmission.

[0423] In the case where a single DCI can schedule multiple PUSCHs, the sixth PUSCH is any one of at least one PUSCH scheduled by a DCI.

[0424] The sixth PUSCH is either the first PUSCH, the second PUSCH, or the third PUSCH.

[0425] Optionally, if a single DCI can schedule PUSCHs on multiple serving cells, the seventh PUSCH is any one of at least one PUSCH scheduled by a DCI on the target serving cell.

[0426] Wherein, the seventh PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target serving cell is any one of the at least one serving cell in the one DCI scheduling.

[0427] To better understand this application, some examples are provided below.

[0428] NR assumes that the UE has only one UL-SCH processing channel for a single Scheduled serving cell (this processing channel can be understood as the baseband processing (focusing on digital signal processing) such as TB assembly, encoding, modulation, and resource mapping, and radio frequency processing (focusing on radio frequency signal processing) such as air interface transmission). Therefore, it only supports serial processing of DG PUSCH with UL-SCH. Accordingly, the network-side equipment ensures that only serially processed DG PUSCH with UL-SCH is scheduled for a single Scheduled serving cell.

[0429] To avoid or mitigate the impact of OoO rules on DG PUSCH transmission for scheduling DCI and scheduled PUSCH, when the network side guarantees that DG PUSCH with UL-SCH meets the OoO rule (i.e., when the network side issues the scheduling DCI corresponding to DG PUSCH with UL-SCH, it guarantees that the OoO rule or a relaxed OoO rule is met), it can distinguish whether the UE has one or more UL-SCH processing channels for a single frequency domain object and adopt the corresponding scheme.

[0430] Option 1: When the UE has only a single UL-SCH processing channel for a single frequency domain object, the scheduling method includes any one of scheduling method 1, scheduling method 2 and scheduling method 3.

[0431] Optionally, in the embodiments of this application, when two DG PUSCHs with UL-SCHs satisfy or do not satisfy the first rule (i.e., the OoO rule or the relaxed OoO rule), these two DG PUSCHs with UL-SCHs necessarily correspond to the same frequency domain object. That is, the OoO rule or the relaxed OoO rule is considered / applied only between DG PUSCHs with UL-SCHs corresponding to the same frequency domain object.

[0432] Scheduling Method 1: For A-CSI triggered scenarios, the network-side device only triggers the DG PUSCH with A-CSI and without UL-SCH (i.e., the second PUSCH) to avoid applying the OoO rule.

[0433] Optionally, the A-CSI triggering scenario can be understood as a scenario where the network-side device needs to trigger A-CSI. Scheduling method 1 can be understood as a method implemented by the network-side device, without the need to introduce functional enhancements on the UE side.

[0434] Scheduling Method 2: For A-CSI triggered scenarios, the network-side device decouples the scheduling / determination of A-CSI triggered DCI from the scheduling of A-CSI reported PUSCH, in order to avoid the impact of long PUSCH preparation time on PUSCH scheduling when combined with OoO rules.

[0435] Optionally, when a network-side device triggers an A-CSI report using a scheduled DCI (i.e., the first DCI), it does not mean that the corresponding A-CSI report is carried by the DG PUSCH scheduled by that DCI. Accordingly, a mechanism can be introduced to determine when and by which PUSCH the A-CSI report is carried.

[0436] Scheduling method 3 allows for the relaxation of OoO rules when predefined timeline requirements are met, allowing the scheduling of DG PUSCH with UL-SCH (i.e., the first PUSCH) to alleviate the limitations imposed by OoO rules.

[0437] Optionally, before a target DG PUSCH with UL-SCH occupies the UL-SCH processing channel (assuming the start time of the target DG PUSCH with UL-SCH occupying the UL-SCH processing channel is the target start time) occupies the UL-SCH processing channel, it is permissible to disregard the OoO rule and use a later scheduling DCI to schedule other DG PUSCH with UL-SCH that can end occupying the UL-SCH processing channel earlier or no later than the target start time.

[0438] Option 2: A solution for when the UE has multiple parallel UL-SCH processing channels for a single frequency domain object.

[0439] Optionally, the number or upper limit of UL-SCH processing channels capable of parallel processing provided by the UE is specified by the protocol, reported by the UE, or configured by higher-layer signaling. The processing capabilities (e.g., Processing time) of different UL-SCH processing channels, or the processing / corresponding DG PUSCH with UL-SCH attributes (e.g., corresponding PHY priority), may be the same or different, and can be specified by the protocol, reported by the UE, or configured by higher-layer signaling. When reported by the UE, this information can be included in the capability information reported by the UE. For each UL-SCH processing channel, the UE and the network side can use the corresponding method in Scheme 1, such as scheduling method 3.

[0440] Optionally, the UE determines the number of parallel UL-SCH processing channels required for DGPUSCH with UL-SCH that has been scheduled and still involves UL-SCH processing channels, and / or allocates the DGPUSCH with UL-SCH that has been scheduled and still involves UL-SCH processing channels to the corresponding UL-SCH processing channels.

[0441] Optionally, the UE does not expect that the number of parallel UL-SCH processing channels required by a scheduled DG PUSCH with UL-SCH that still involves UL-SCH processing channels exceeds the number of UL-SCH processing channels that the UE has capable of parallel processing or the upper limit of such number. Alternatively, any scheduled DG PUSCH with UL-SCH that still involves UL-SCH processing channels cannot be allocated to a corresponding UL-SCH processing channel. In this embodiment, the network-side device ensures that the scheduled DG PUSCH with UL-SCH that still involves UL-SCH processing channels meets the above requirements.

[0442] It should be noted that the uplink processing method in this application embodiment can be applied to single TRP scenarios or multiple TRP scenarios. For multiple TRP scenarios, based on UE capability reporting, one of the following can be adopted:

[0443] For the DG PUSCH with UL-SCH scheduling of each TRP, the above-described scheme of this application is applied. Generally, the scenario of multi-TRP based on multiple DCI (mDCI-based mTRP) is mainly considered. In this case, the DG PUSCH with UL-SCH scheduling of each TRP is relatively independent, and the UE can clearly distinguish the DG PUSCH with UL-SCH scheduling for each TRP.

[0444] The scheme of this application is uniformly applied to all TRPs. That is, when the UE applies the scheme of this application, it does not distinguish the correspondence between DGPUSCH with UL-SCH scheduling and TRP.

[0445] Optionally, Scheme 1 or Scheme 2 described above can be used in the Single PUSCH scheduling without repetition scenario. For Single PUSCH scheduling with repetition or Single PUSCH scheduling with TBoMS, Scheme 1 or Scheme 2 can be applied to each PUSCH transmission involved (e.g., a PUSCH repetition of PUSCH repetition Type A, an Actual repetition of PUSCH repetition Type B, or a PUSCH transmission of TBoMS). Optionally, when a PUSCH repetition or TBoMS expects to occupy a UL-SCH processing channel, all repetitions, all TBoMS, or all PUSCH transmissions corresponding to a single PUSCH occupy the same UL-SCH processing channel of the same frequency domain object (e.g., a scheduled serving cell).

[0446] Optionally, Scheme 1 or Scheme 2 described above can be used in a Multi-PUSCH scheduling scenario. For Multi-PUSCH scheduling, the above schemes can be applied separately to the DCI and each PUSCH it schedules. Optionally, when a scheduled PUSCH expects to occupy a UL-SCH processing channel, all PUSCHs scheduled by the same DCI occupy the same UL-SCH processing channel of the same frequency domain object (e.g., a Scheduled serving cell).

[0447] Optionally, Scheme 1 or Scheme 2 described above can be used in multi-cell scheduling scenarios. For multi-cell scheduling, the above schemes can be applied separately to the DCI and each PUSCH scheduled on each scheduled serving cell. When the frequency domain object is a scheduled serving cell, the UL-SCH processing channels expected to be occupied by each PUSCH scheduled on each scheduled serving cell are independent of each other.

[0448] Example 1: Dynamically scheduled PUSCH.

[0449] When the CSI request field in the scheduling DCI is set to a non-zero value, an A-CSI report corresponding to the Aperiodic CSItrigger state corresponding to this value is triggered, and the A-CSI report corresponding to the triggered Aperiodic CSI trigger state is carried in the DG PUSCH corresponding to the scheduling DCI; otherwise, when the CSI request field in the scheduling DCI is set to 0, no A-CSI report is triggered.

[0450] When the UL-SCH indicator field in the scheduling DCI is set to 1, the UL-SCH is carried in the form of TB in the DG PUSCH corresponding to the scheduling DCI; otherwise, when the UL-SCH indicator field in the scheduling DCI is set to 0, the DG PUSCH does not carry the UL-SCH, but only carries the physical layer UCI.

[0451] In this application example, the type of DG PUSCH includes at least one of the following:

[0452] DG PUSCH with A-CSI and UL-SCH: This means that the DG PUSCH needs to carry the triggered A-CSI report and UL-SCH.

[0453] DG PUSCH without A-CSI and with UL-SCH: This means that DG PUSCH does not need to carry the triggered A-CSI report, but it does need to carry the UL-SCH.

[0454] DG PUSCH with A-CSI and without UL-SCH: This means that the DG PUSCH needs to carry the triggered A-CSI report, but does not need to carry the UL-SCH.

[0455] DG PUSCH without A-CSI and without UL-SCH: This means that DG PUSCH does not need to carry either the triggered A-CSI report or the UL-SCH.

[0456] DG PUSCH with UL-SCH: This means that the DG PUSCH needs to carry UL-SCH. It can be either DG PUSCH with A-CSI and UL-SCH or DG PUSCH without A-CSI and with UL-SCH.

[0457] Example 2: The frequency domain object may include at least one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain element, frequency band, frequency band combination, and frequency range.

[0458] Optionally, a frequency domain object may contain one or more target objects, or all target objects configured for the UE. The target objects here are at least one of the items listed above.

[0459] Example 3: Under Scheme 1, relax the OoO rule when scheduling DG PUSCH with UL-SCH.

[0460] For Scheme 1, when the UE has only a single UL-SCH processing channel, a predefined Timeline requirement can be introduced to relax the OoO rule to a certain extent, thereby alleviating the restrictions brought by the OoO rule.

[0461] Optionally, the predefined Timeline requirement is used to specify the moment when the UE begins or at the latest begins preparing for DG PUSCH with UL-SCH, and it is expected that the UE will occupy the UL-SCH processing channel from this moment to process DG PUSCH with UL-SCH until the DG PUSCH with UL-SCH baseband processing is completed / transmission begins / transmission is completed.

[0462] Optionally, such as Figure 5As shown, both sides (terminal and network-side devices) assume that each DG PUSCH with UL-SCH starts preparing at or at the latest by the first duration (t-T1) before the start time t, and occupies the UL-SCH processing channel during the second duration (T2) starting from t-T1. Before a target DG PUSCH with UL-SCH (i.e., the second target PUSCH) with an earlier scheduled DCI occupies the UL-SCH processing channel (assuming the start and end times of the target DG PUSCH with UL-SCH occupying the UL-SCH processing channel are the target start time and target end time, respectively), it is allowed to disregard the OoO rule and use a later scheduled DCI to schedule other DG PUSCH with UL-SCH that can end occupying the UL-SCH processing channel earlier than or no later than the target start time. Understandably, if other DG PUSCH with UL-SCH (using a later scheduling DCI) cannot end their occupation of the UL-SCH processing channel at or before the target start time, they are not allowed to be scheduled; the UE can send the target DG PUSCH with UL-SCH normally without being affected by other DGPUSCH with UL-SCH (if they exist) scheduled using a later scheduling DCI.

[0463] Optionally, the target DG PUSCH with UL-SCH and other DG PUSCHs with UL-SCHs scheduled using a later scheduling DCI (i.e., the first target PUSCH) occupy different HARQ processes; for the same HARQ process, the relevant NR rules must still be followed (other scheduling DCIs that use this HARQ process can only be received after the last DG PUSCH of a certain HARQ process has been transmitted).

[0464] Alternatively, using a later DCI scheduler, and ensuring that other DG PUSCHs occupying UL-SCH processing channels terminate earlier than or no later than the target start time, can also be understood as satisfying one of the following:

[0465] Other DG PUSCH with UL-SCH can complete preparation processing (including baseband processing, etc.) earlier than or no later than the target start time, that is, the time when other DG PUSCH with UL-SCH completes preparation processing can be earlier than or no later than the target start time.

[0466] Other DG PUSCH with UL-SCH can start transmitting earlier or no later than the target start time, that is, the start time of other DGPUSCH with UL-SCH can be earlier or no later than the target start time;

[0467] Other DG PUSCH with UL-SCH can be sent earlier or no later than the target start time, that is, other DGPUSCH with UL-SCH can end earlier or no later than the target start time.

[0468] Alternatively, the comparison of the early and late times of two scheduling DCIs can be determined based on one of the following:

[0469] Schedule the start / end times of DCI;

[0470] Start / end symbols for scheduling DCI;

[0471] The CORESET where the DCI is located is scheduled;

[0472] The start / end time of the PDCCH monitoring occasion where the DCI is scheduled.

[0473] The start time t of each DG PUSCH with UL-SCH is determined based on one of the following:

[0474] The start time of the first symbol / first data symbol / first DM-RS symbol occupied by DG PUSCH with UL-SCH;

[0475] Based on the above starting time, and after further considering the influence of TA, the determined time is.

[0476] Example 4: In Case 2, the UE determines the number of parallel UL-SCH processing channels that the scheduled DG PUSCH with UL-SCH needs to occupy, and / or allocates the scheduled DG PUSCH with UL-SCH to the UL-SCH processing channels.

[0477] For scheme 2, when the terminal determines the number of parallel UL-SCH processing channels that the DG PUSCH with UL-SCH that has been scheduled and still involves UL-SCH processing channels needs to occupy, and / or allocates the DG PUSCH with UL-SCH that has been scheduled and still involves UL-SCH processing channels to the corresponding UL-SCH processing channels, at least one of determination operation 1 and determination operation 2 is performed.

[0478] Operation 1: When the UE detects a newly scheduled DG PUSCH with UL-SCH, determine the number of parallel UL-SCH processing channels required by all already scheduled DG PUSCH with UL-SCH (including the newly scheduled DG PUSCH with UL-SCH) that still involve UL-SCH processing channels, and / or, allocate the newly scheduled DG PUSCH with UL-SCH to the corresponding UL-SCH processing channel.

[0479] Optionally, for each newly scheduled DG PUSCH with UL-SCH, the UE needs to first detect the corresponding scheduling DCI, and then, based on the scheduling DCI and the various attributes (including timing relationships) of the newly scheduled DG PUSCH with UL-SCH, determine whether it satisfies the OoO rule or the relaxed OoO rule with the already scheduled DG PUSCH with UL-SCH that still involves (or still corresponds to) the UL-SCH processing channel, and whether it needs to occupy a new UL-SCH processing channel, thereby determining the number of parallel UL-SCH processing channels that all already scheduled DG PUSCH with UL-SCH (including newly scheduled DGPUSCH with UL-SCH) that still involve the UL-SCH processing channel need to occupy.

[0480] It should be noted that the duration for the UE to decode the scheduling DCI is not explicitly defined in the current protocol. The UE can implement this itself by performing the determination operation 1 described above after decoding the scheduling DCI. When the network guarantees that the number of parallel UL-SCH processing channels required by a scheduled DG PUSCH with UL-SCH that still involves UL-SCH processing channels does not exceed the number of UL-SCH processing channels that the UE is capable of parallel processing or the upper limit of such number, or when all scheduled DG PUSCH with UL-SCH that still involves UL-SCH processing channels can be allocated to the corresponding UL-SCH processing channels, the network needs to check and ensure that for this UE, after scheduling this new DG PUSCH with UL-SCH, until any time when this new DG PUSCH with UL-SCH ends occupying UL-SCH processing channels (e.g., from the start / end time of the DCI scheduling, or from the start / end time of the CORESET that issued the DCI scheduling, or from the start / end time of the time slot where this CORESET is located, until this new DG PUSCH with UL-SCH ends...), the network must ensure that... At any point between when UL-SCH no longer involves (or no longer corresponds to) the UL-SCH processing channel, the number of parallel UL-SCH processing channels required by all DGPUSCH with UL-SCH that have been scheduled for this UE and still involve the UL-SCH processing channel does not exceed the number of UL-SCH processing channels that the UE has capable of parallel processing or the upper limit of such number. Alternatively, this new DGPUSCH with UL-SCH can be allocated to the corresponding UL-SCH processing channel. In this case, the network-side equipment does not need to know the exact time when the UE decodes and schedules the DCI.

[0481] Optionally, the terminal may assume that all scheduled DG PUSCH with UL-SCH (including newly scheduled DG PUSCH with UL-SCH) that still involve UL-SCH processing channels are considered as a set of DG PUSCH with UL-SCH. This set of DG PUSCH with UL-SCH can be divided into one or more subsets of DG PUSCH with UL-SCH. Each subset of DG PUSCH with UL-SCH is further allocated to the corresponding UL-SCH processing channel (when the processing capabilities of different UL-SCH processing channels or the corresponding DG PUSCH with UL-SCH attributes are different, the allocation must ensure the matching between the subset of DG PUSCH with UL-SCH and the UL-SCH processing channel). When each subset of DG PUSCH with UL-SCH contains more than one DG PUSCH with UL-SCH, any two DG PUSCH with UL-SCH satisfy the OoO rule or a relaxed OoO rule.

[0482] Operation 1 includes the following steps:

[0483] Step S11: The UE determines whether a new DG PUSCH with UL-SCH subset needs to be allocated for the newly scheduled DG PUSCH with UL-SCH, and / or determines the number of DG PUSCH with UL-SCH subsets divided from all DG PUSCH with UL-SCH that have already been scheduled and still involve UL-SCH processing channels (including the newly scheduled DG PUSCH with UL-SCH).

[0484] Specifically, the UE can perform the following operations:

[0485] When the UE has no other scheduled DG PUSCH with UL-SCH that still involves UL-SCH processing channels, except for the newly scheduled DG PUSCH with UL-SCH, the newly scheduled DG PUSCH with UL-SCH is placed into a newly created subset (there is a total of 1 subset at this time).

[0486] When the UE has other scheduled DG PUSCH with UL-SCH that still involve UL-SCH processing channels, in addition to the newly scheduled DG PUSCH with UL-SCH, assuming these scheduled DG PUSCH with UL-SCH that still involve UL-SCH processing channels are divided into N subsets, the following situations can be distinguished to perform the corresponding operations:

[0487] Case 1: Different subsets have the same attributes. These attributes may include the corresponding DG PUSCH with UL-SCH attributes (such as the corresponding PHY priority), the expected processing capacity of the allocated UL-SCH processing channel (such as processing time), etc.

[0488] Based on a predefined subset order, the UE checks whether the newly scheduled DG PUSCH with UL-SCH satisfies the OoO rule or a relaxed OoO rule between each subset and any other scheduled DG PUSCH with UL-SCH in the subset.

[0489] When the UE finds a subset, and any scheduled DG PUSCH with UL-SCH in this subset satisfies the OoO rule or a relaxed OoO rule with the newly scheduled DG PUSCH with UL-SCH, the UE will include the newly scheduled DG PUSCH with UL-SCH in this subset.

[0490] When no subset in the N subsets meets the above inclusion conditions, the UE will place the newly scheduled DG PUSCH with UL-SCH into a newly created subset (at this time there are a total of N+1 subsets).

[0491] Scenario 2: Different subsets can have different attributes. UE can group subsets with completely identical attributes (or attributes that need to be considered when assigning subsets) into the same subset group based on the attributes of different subsets.

[0492] If the UE has not yet created a subset group that matches the newly scheduled DG PUSCH with UL-SCH, the newly scheduled DG PUSCH with UL-SCH is placed into a newly created subset, which is then assigned to a separate subset group.

[0493] When the UE has created a subset group (which can be called the target subset group) that matches the newly scheduled DG PUSCH with UL-SCH, the UE checks, based on a predefined subset order, whether the newly scheduled DG PUSCH with UL-SCH satisfies the OoO rule or a relaxed OoO rule with any other scheduled DG PUSCH with UL-SCH in the subset and for each subset within the target subset group:

[0494] When the UE finds a subset, and any scheduled DG PUSCH with UL-SCH in this subset satisfies the OoO rule or a relaxed OoO rule with the newly scheduled DG PUSCH with UL-SCH, the UE will include the newly scheduled DG PUSCH with UL-SCH in this subset.

[0495] When no subset in the N subsets meets the above inclusion conditions, the UE will place the newly scheduled DG PUSCH with UL-SCH into a newly created subset, which will be assigned to the target subset group.

[0496] Optionally, the order of the predefined subsets can be determined based on at least one of the following:

[0497] The chronological order in which the subsets were created;

[0498] The physical layer priority (PHY priority) of the subset is in ascending or descending order;

[0499] The subset contains DG PUSCH with UL-SCH in ascending or descending order of the number of DG PUSCHs;

[0500] The order of the earliest / latest times of the start / end times of the scheduling DCI corresponding to the DG PUSCH with UL-SCH in the subset (or the start / end times of the CORESET that issues the scheduling DCI, or the start / end times of the time slot in which this CORESET is located).

[0501] The order of the earliest / latest times of the start / end times of DG PUSCH with UL-SCH in the subset (or the start / end times of the time slot in which DG PUSCH with UL-SCH is located).

[0502] Step S12: Based on the number of DG PUSCH with UL-SCH subsets and the number of UL-SCH processing channels occupied by each subset, the UE determines the number of parallel UL-SCH processing channels required for all scheduled DG PUSCH with UL-SCH (including newly scheduled DG PUSCH with UL-SCH) that still involve UL-SCH processing channels.

[0503] When determining the number of UL-SCH processing channels occupied by each subset, one of the following can be used:

[0504] Each subset occupies only a single UL-SCH processing channel;

[0505] Each subset occupies M UL-SCH processing channels.

[0506] Herein, the determination of M may be made based on one of the following: the number of DG PUSCH with UL-SCH included in the subset, the attribute of each DG PUSCH with UL-SCH in the subset, and the attribute of the scheduling DCI corresponding to each DG PUSCH with UL-SCH in the subset.

[0507] For the number of DG PUSCH with UL-SCH included in the subset. For example, when the number of DG PUSCH with UL-SCH included in the subset does not exceed a predefined threshold, this subset occupies a single UL-SCH processing channel; otherwise, this subset occupies two UL-SCH processing channels. Optionally, A predefined thresholds that are greater than 1, are not equal to each other, and are arranged in ascending order may be defined, so as to divide the number of DG PUSCH with UL-SCH included in the subset into A+1 intervals. When the number of DG PUSCH with UL-SCH included in the subset (assumed to be n) does not exceed the first predefined threshold, this subset occupies a single UL-SCH processing channel; when n exceeds the A-th predefined threshold, this subset occupies A+1 UL-SCH processing channels; when n exceeds the i-th predefined threshold (the predefined thresholds are numbered starting from 1, 1≤i<A) but does not exceed the (i+1)-th predefined threshold, this subset occupies i+1 UL-SCH processing channels. The predefined thresholds herein may be specified by a protocol or configured by high-layer signaling.

[0508] For the attribute of each DG PUSCH with UL-SCH in the subset, it may include at least one of the following: the number of allocated symbols, the number of data symbols, the number of pilot symbols, the number of layers, the frequency domain resource allocation type, the number of allocated frequency domain resources (for resource allocation type 0, it may be the number of RBGs; for resource allocation type 1, it may be the number of PRBs), the number of allocated REs, the number of data REs, the number of pilot REs, the TB size, and the PHY priority. The number of UL-SCH processing channels that each DG PUSCH with UL-SCH needs to occupy may be determined based on the attribute of said DG PUSCH with UL-SCH. The maximum value of the number of UL-SCH processing channels that each DG PUSCH with UL-SCH in the subset needs to occupy is taken as M.

[0509] Optionally, when attributes of different subsets may be different, different subsets only occupy UL-SCH processing channels matching their attributes.

[0510] Operation 2: When the UE detects that a scheduled DG PUSCH with UL-SCH no longer involves (or no longer corresponds to) a UL-SCH processing channel, determine the number of parallel UL-SCH processing channels required by all scheduled DG PUSCH with UL-SCH that still involve UL-SCH processing channels (excluding this scheduled DG PUSCH with UL-SCH that no longer involves UL-SCH processing channels).

[0511] When still using the OoO rule in NR, the moment when "the UE detects that a scheduled DG PUSCH with UL-SCH no longer involves (or corresponds to) the UL-SCH processing channel" can be understood as the moment when the UE completes the transmission of this DG PUSCH with UL-SCH, or the moment when this DG PUSCH with UL-SCH ends. Optionally, other time points can also be considered, such as the start time of this DG PUSCH with UL-SCH, or the moment after the end time of this DG PUSCH with UL-SCH is superimposed with a predefined time offset.

[0512] When a relaxed OoO rule is adopted, the moment when "the UE detects that a scheduled DG PUSCH with UL-SCH no longer involves (or no longer corresponds to) the UL-SCH processing channel" can be understood as the moment when the DG PUSCH with UL-SCH ends its occupation of the UL-SCH processing channel.

[0513] Optionally, the terminal may assume that all scheduled DG PUSCH with UL-SCH (including newly scheduled DG PUSCH with UL-SCH) that still involve UL-SCH processing channels are considered as a set of DG PUSCH with UL-SCH. This set of DG PUSCH with UL-SCH can be divided into one or more subsets of DG PUSCH with UL-SCH. Each subset of DG PUSCH with UL-SCH is further allocated to the corresponding UL-SCH processing channel (when the processing capabilities of different UL-SCH processing channels or the corresponding DG PUSCH with UL-SCH attributes are different, the allocation must ensure the matching between the subset of DG PUSCH with UL-SCH and the UL-SCH processing channel). When each subset of DG PUSCH with UL-SCH contains more than one DG PUSCH with UL-SCH, any two DG PUSCH with UL-SCH satisfy the OoO rule or a relaxed OoO rule. Among them, all DG PUSCH with UL-SCH that have been scheduled and still involve the UL-SCH processing channel do not include the aforementioned DG PUSCH with UL-SCH that have been scheduled and no longer involve the UL-SCH processing channel.

[0514] Operation 2 includes the following steps:

[0515] Step S21: The UE removes the DG PUSCH with UL-SCH that has been scheduled and no longer involves the UL-SCH processing channel from the corresponding subset, and determines the number of DGPUSCH with UL-SCH subsets divided from all DG PUSCH with UL-SCH that has been scheduled and still involves the UL-SCH processing channel (excluding this DG PUSCH with UL-SCH that has been scheduled and no longer involves the UL-SCH processing channel).

[0516] Specifically, the terminal removes the DG PUSCH with UL-SCH that has been scheduled and no longer involves the UL-SCH processing channel from the corresponding subset; when this subset becomes empty, the UE deletes this subset.

[0517] Step S22: Based on the number of DG PUSCH with UL-SCH subsets and the number of UL-SCH processing channels occupied by each subset, the UE determines the number of parallel UL-SCH processing channels required for all scheduled DG PUSCH with UL-SCH that still involve UL-SCH processing channels (excluding DG PUSCH with UL-SCH that are scheduled but no longer involve UL-SCH processing channels).

[0518] Here we can use the operation corresponding to step S12 in operation 1.

[0519] It should be noted that the network-side device can also perform the above-mentioned determination operation 1 and / or determination operation 2 to determine the number of parallel UL-SCH processing channels that the DG PUSCH with UL-SCH that has been scheduled by the UE and still involves the UL-SCH processing channel needs to occupy on the UE side, and / or to allocate the DG PUSCH with UL-SCH that has been scheduled and still involves the UL-SCH processing channel to the corresponding UL-SCH processing channel.

[0520] The uplink transmission method provided in this application can be executed by an uplink transmission device. This application uses an uplink transmission device executing the uplink transmission method as an example to illustrate the uplink transmission device provided in this application.

[0521] This application provides an uplink transmission device. As an example, the uplink transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0522] The uplink transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0523] For details, see Figure 6 When the uplink transmission device is a terminal or a component within a terminal, the uplink transmission device 600 includes:

[0524] Sending module 601 is configured to perform at least one of the following:

[0525] Transmit the first physical uplink shared channel (PUSCH) according to the first rule;

[0526] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), it is expected that the first rule will not be applied to the second PUSCH.

[0527] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, it is not expected that the A-CSI report corresponding to the A-CSI measurement will always be carried on the third PUSCH, which is scheduled by the first DCI.

[0528] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0529] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0530] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0531] If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time when the first target PUSCH occupies the target processing channel, and the target start time of the second target PUSCH is the start time when the second target PUSCH occupies the target processing channel.

[0532] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0533] Optionally, the first target PUSCH and / or the second target PUSCH meet predefined requirements, which include at least one of the following:

[0534] PUSCH is dynamically scheduled by DCI;

[0535] PUSCH carries the uplink shared channel;

[0536] PUSCH transmission requires the HARQ process to be used.

[0537] Optionally, the target time is any one of the following:

[0538] The start or end time of DCI;

[0539] The start or end time of the first time domain unit of DCI;

[0540] The start or end time of the first time domain unit of DCI;

[0541] The start or end time of the second time-domain unit of the DCI is detected;

[0542] The start or end time of the DCI control resource set CORESET was detected;

[0543] The start or end time of the second time-domain unit where the CORESET of the DCI is located is detected;

[0544] The start or end time of the detected monitoring occasion for the Physical Downlink Control Channel (PDCCH) of the DCI;

[0545] The start or end time of the second time-domain unit where the DCI's PDCCH monitoring occasion is located is detected.

[0546] Optionally, the first rule further includes at least one of the following:

[0547] The time when the first target PUSCH is ready to be processed is earlier than or no later than the target start time;

[0548] The transmission start time of the first target PUSCH is earlier than or no later than the target start time;

[0549] The end time of the transmission of the first target PUSCH is earlier than or no later than the start time of the target.

[0550] Optionally, the target start time is earlier than or no later than the start time of the second target PUSCH, and the interval between the target start time and the start time of the second target PUSCH is the first duration corresponding to the second target PUSCH.

[0551] Optionally, the start time of the second target PUSCH is determined based on any of the following:

[0552] The first moment;

[0553] First moment and time in advance;

[0554] Wherein, the first moment is any one of the following:

[0555] The start time of the first time domain unit occupied by the second target PUSCH;

[0556] The start time of the first time domain unit of the first data carried by the second target PUSCH;

[0557] The start time of the first time-domain unit of the first bearer demodulation reference signal occupied by the second target PUSCH;

[0558] The start time of the second time domain unit or the first second time domain unit where the second target PUSCH is located.

[0559] Optionally, the first duration satisfies any one of the following:

[0560] The first duration is the same for all target PUSCHs scheduled by the terminal on any frequency domain object.

[0561] The first duration is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object.

[0562] The first duration corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on the first attribute or a combination of the first attributes.

[0563] The first duration corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on the first attribute or a combination of the first attributes.

[0564] Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

[0565] Optionally, the second duration for which the target PUSCH occupies the target processing channel is determined based on at least one of the following:

[0566] The duration reported by the terminal;

[0567] The duration agreed upon in the agreement;

[0568] The third duration is determined based on the first duration corresponding to the target PUSCH, where the first duration is the start time when the target PUSCH occupies the target processing channel;

[0569] Duration of high-level signaling configuration;

[0570] Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

[0571] Optionally, the third duration satisfies any one of the following:

[0572] The third duration is equal to the first duration;

[0573] The third duration is equal to the sum of the first duration and the duration of the target PUSCH;

[0574] The third duration is equal to the sum of the first duration, the duration of the target PUSCH, and the first offset value;

[0575] The third duration is equal to the sum of the first duration and the second offset value.

[0576] Optionally, the first information satisfies at least one of the following:

[0577] The first information is the same for all target PUSCHs scheduled by the terminal on any frequency domain object;

[0578] The first information is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object;

[0579] The first information corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on a first attribute or a combination of first attributes.

[0580] The first information corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on a first attribute or a combination of first attributes.

[0581] The first information includes at least one of the second duration, the first offset value, and the second offset value.

[0582] Optionally, the first attribute or combination of the first attributes includes at least one of the following:

[0583] PUSCH timing capability;

[0584] First subcarrier spacing (SCS);

[0585] Transport block size;

[0586] The first number of time-domain cells occupied by PUSCH;

[0587] Duration of PUSCH;

[0588] The number of resource units corresponding to PUSCH, the number of data resource units, or the number of demodulation reference signal resource units;

[0589] The time-domain location of the first time-domain unit or resource unit carrying the demodulation reference signal in the PUSCH;

[0590] The type of the first time domain unit of PUSCH, or the contents of the first time domain unit of PUSCH;

[0591] Does the scheduling DCI corresponding to PUSCH simultaneously trigger a bandwidth portion BWP switch?

[0592] PUSCH physical layer priority;

[0593] Whether PUSCH reuses uplink control information (UCI);

[0594] When PUSCH multiplexes UCI, the information of the physical uplink control channel PUCCH with time-domain overlap is included.

[0595] When PUSCH reuses UCI, does it involve UCI reuse across physical layer priorities?

[0596] When PUSCH reuses UCI, it reuses either the UCI type or a combination of UCI types.

[0597] Optionally, the first SCS includes any of the following:

[0598] PUSCH's SCS;

[0599] The SCS of the scheduling DCI corresponding to PUSCH;

[0600] The maximum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH.

[0601] The minimum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH.

[0602] The SCS corresponding to the largest or smallest of the first duration determined by the SCS based on PUSCH and the first duration determined by the SCS based on the scheduling DCI corresponding to PUSCH.

[0603] Optionally, the uplink transmission device 600 further includes a first processing module, configured to perform a first operation and / or a second operation before transmitting the first PUSCH according to the first rule when the second frequency domain object corresponds to multiple uplink shared channel processing channels.

[0604] The first operation includes at least one of the following:

[0605] Assign the first PUSCH to the first PUSCH subset;

[0606] Determine the number of second PUSCH subsets for all scheduled PUSCH partitions;

[0607] Wherein, the second frequency domain object is the frequency domain object corresponding to the first PUSCH, the first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset, and each second PUSCH subset satisfies at least one of the following:

[0608] Includes all PUSCHs associated with the first processing channel subset;

[0609] Corresponding to the first processing channel subset;

[0610] Any two PUSCHs included satisfy the first rule;

[0611] The first processing channel subset includes at least one uplink shared channel processing channel among a plurality of uplink shared channel processing channels corresponding to the second frequency domain object.

[0612] The second operation includes at least one of the following:

[0613] If the fourth PUSCH that has already been scheduled finishes occupying the second processing channel subset, the terminal will remove the fourth PUSCH from the third PUSCH subset.

[0614] The terminal re-determines the number of the second PUSCH subset;

[0615] Before performing the second operation, the terminal has already allocated the fourth PUSCH to the third PUSCH subset, and the third PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset; the third PUSCH subset corresponds to the second processing channel subset.

[0616] Optionally, assigning the first PUSCH to a subset of the first PUSCH includes at least one of the following:

[0617] If all scheduled PUSCHs other than the first PUSCH on the second frequency domain object have finished occupying the uplink shared channel processing channel corresponding to the second frequency domain object, a new first PUSCH subset is created, and the first PUSCH is allocated to the newly created first PUSCH subset.

[0618] If at least one fourth PUSCH subset exists in the at least one second PUSCH subset, the first PUSCH is assigned to the first fourth PUSCH subset determined by traversing each of the second PUSCH subsets in a predefined subset order, wherein the first fourth PUSCH subset is the first PUSCH subset and the fourth PUSCH subset is a single second PUSCH subset that satisfies the first condition.

[0619] If the fourth PUSCH subset does not exist in at least one second PUSCH subset, a new first PUSCH subset is created, and the first PUSCH is assigned to the newly created first PUSCH subset.

[0620] Wherein, the second attribute of each of the at least one second PUSCH subset is the same; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

[0621] Optionally, the at least one second PUSCH subset is divided into at least one second PUSCH subset group based on the second attribute of each second PUSCH subset, wherein the second attribute of each second PUSCH subset in each second PUSCH subset group is the same, and the assignment of the first PUSCH to the first PUSCH subset includes at least one of the following:

[0622] If a first PUSCH subset group does not exist in at least one second PUSCH subset group, a new first PUSCH subset group is created, and the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group.

[0623] If a first PUSCH subset group exists in the at least one second PUSCH subset group, and at least one fifth PUSCH subset exists in the first PUSCH subset group, the first PUSCH is assigned to the first fifth PUSCH subset determined by traversing each of the second PUSCH subsets in the first PUSCH subset group based on a predefined subset order. The first fifth PUSCH subset is the first PUSCH subset, and the fifth PUSCH subset is a single second PUSCH subset in the first PUSCH subset group that satisfies the first condition.

[0624] If a first PUSCH subset exists in at least one second PUSCH subset group, and the fifth PUSCH subset does not exist in the first PUSCH subset group, the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group.

[0625] Wherein, the first PUSCH subset group matches the first PUSCH; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

[0626] Optionally, the order of the predefined subsets is determined based on at least one of the following:

[0627] The creation time of the PUSCH subset;

[0628] Physical layer priority corresponding to the PUSCH subset;

[0629] The number of PUSCHs contained in the PUSCH subset;

[0630] The start or end time of the scheduling DCI corresponding to PUSCH in the PUSCH subset;

[0631] The start or end time of the first control resource set where the scheduling DCI corresponding to the PUSCH in the PUSCH subset is located.

[0632] The start or end time of the second time-domain unit where the first control resource set is located;

[0633] The start or end time of PUSCH in the PUSCH subset;

[0634] The start or end time of the second time-domain unit where PUSCH is located in the PUSCH subset.

[0635] Optionally, the uplink transmission device 600 further includes a first processing module, configured to determine the number of uplink shared channel processing channels that the scheduled PUSCH needs to occupy based on the number of the second PUSCH subsets and the number of uplink shared channel processing channels contained in the first processing channel subset corresponding to each second PUSCH subset.

[0636] Optionally, each of the first processing channel subsets includes a single uplink shared channel processing channel, or each of the first processing channel subsets includes M uplink shared channel processing channels;

[0637] M is determined based on at least one of the following:

[0638] The number of PUSCHs contained in the corresponding second PUSCH subset;

[0639] The attributes of the PUSCH contained in the corresponding second subset of PUSCH;

[0640] The corresponding second subset of PUSCH contains the attributes of the scheduling DCI corresponding to the PUSCH.

[0641] Optionally, the frequency domain object includes any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range; or, the frequency domain object includes at least one first frequency domain object, the first frequency domain object including any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range.

[0642] Optionally, the uplink transmission device 600 further includes a first processing module for performing any of the following:

[0643] The number of uplink shared channel processing channels that the scheduled PUSCH needs to occupy should not exceed the maximum number of uplink shared channel processing channels that the terminal supports for parallel processing.

[0644] It is expected that any scheduled PUSCH can be assigned to the corresponding uplink shared channel processing channel.

[0645] Optionally, when multiple TRPs are configured, the fifth PUSCH satisfies any of the following:

[0646] Corresponds to the target TRP among the plurality of TRPs;

[0647] Corresponds to any one of the plurality of TRPs;

[0648] Wherein, the fifth PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target TRP is one of the plurality of TRPs.

[0649] Optionally, the sixth PUSCH satisfies at least one of the following:

[0650] When using type A repetition transmission, the sixth PUSCH is any one of the at least one PUSCH repetition transmissions corresponding to a PUSCH.

[0651] When using type B repetition transmission, the sixth PUSCH is any one of the at least one actual PUSCH repetition transmissions corresponding to a PUSCH.

[0652] In the case of using multi-timeslot transport block (TBoMS) transmission, the sixth PUSCH is any one of the PUSCH transmissions in at least one PUSCH transmission corresponding to a TBoMS transmission.

[0653] In the case where a single DCI can schedule multiple PUSCHs, the sixth PUSCH is any one of at least one PUSCH scheduled by a DCI.

[0654] The sixth PUSCH is either the first PUSCH, the second PUSCH, or the third PUSCH.

[0655] Optionally, if a single DCI can schedule PUSCHs on multiple serving cells, the seventh PUSCH is any one of at least one PUSCH scheduled by a DCI on the target serving cell.

[0656] Wherein, the seventh PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target serving cell is any one of the at least one serving cell in the one DCI scheduling.

[0657] See Figure 7 When the uplink transmission device is a network-side device or a component within a network-side device, the uplink transmission device 700 includes:

[0658] Receiver module 701 is configured to perform at least one of the following:

[0659] The first physical uplink shared channel (PUSCH) is scheduled and received according to the first rule;

[0660] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the first rule is guaranteed not to be applied to the second PUSCH.

[0661] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, an A-CSI report corresponding to the A-CSI measurement can be received on an uplink channel different from the third PUSCH, which is scheduled by the first DCI.

[0662] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0663] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0664] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0665] When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, the time when preparation for processing is completed, the time of transmission start or transmission end. The target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel.

[0666] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0667] Optionally, the first target PUSCH and / or the second target PUSCH meet predefined requirements, which include at least one of the following:

[0668] PUSCH is dynamically scheduled by DCI;

[0669] PUSCH carries the uplink shared channel;

[0670] PUSCH transmission requires the HARQ process to be used.

[0671] Optionally, the target time is any one of the following:

[0672] The start or end time of DCI;

[0673] The start or end time of the first time domain unit of DCI;

[0674] The start or end time of the first time domain unit of DCI;

[0675] The start or end time of the second time-domain unit of the DCI is detected;

[0676] The start or end time of the DCI control resource set CORESET was detected;

[0677] The start or end time of the second time-domain unit where the CORESET of the DCI is located is detected;

[0678] The start or end time of the detected monitoring occasion for the Physical Downlink Control Channel (PDCCH) of the DCI;

[0679] The start or end time of the second time-domain unit where the DCI's PDCCH monitoring occasion is located is detected.

[0680] Optionally, the first rule further includes at least one of the following:

[0681] The time when the first target PUSCH is ready to be processed is earlier than or no later than the target start time;

[0682] The transmission start time of the first target PUSCH is earlier than or no later than the target start time;

[0683] The end time of the transmission of the first target PUSCH is earlier than or no later than the start time of the target.

[0684] Optionally, the target start time is earlier than or no later than the start time of the second target PUSCH, and the interval between the target start time and the start time of the second target PUSCH is the first duration corresponding to the second target PUSCH.

[0685] Optionally, the start time of the second target PUSCH is determined based on any of the following:

[0686] The first moment;

[0687] First moment and time in advance;

[0688] Wherein, the first moment is any one of the following:

[0689] The start time of the first time domain unit occupied by the second target PUSCH;

[0690] The start time of the first time domain unit of the first data carried by the second target PUSCH;

[0691] The start time of the first time-domain unit of the first bearer demodulation reference signal occupied by the second target PUSCH;

[0692] The start time of the second time domain unit or the first second time domain unit where the second target PUSCH is located.

[0693] Optionally, the first duration satisfies any one of the following:

[0694] The first duration is the same for all target PUSCHs scheduled by the terminal on any frequency domain object.

[0695] The first duration is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object.

[0696] The first duration corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on the first attribute or a combination of the first attributes.

[0697] The first duration corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on the first attribute or a combination of the first attributes.

[0698] Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

[0699] Optionally, the second duration for which the target PUSCH occupies the target processing channel is determined based on at least one of the following:

[0700] The duration reported by the terminal;

[0701] The duration agreed upon in the agreement;

[0702] The third duration is determined based on the first duration corresponding to the target PUSCH, where the first duration is the start time when the target PUSCH occupies the target processing channel;

[0703] Duration of high-level signaling configuration;

[0704] Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

[0705] Optionally, the third duration satisfies any one of the following:

[0706] The third duration is equal to the first duration;

[0707] The third duration is equal to the sum of the first duration and the duration of the target PUSCH;

[0708] The third duration is equal to the sum of the first duration, the duration of the target PUSCH, and the first offset value;

[0709] The third duration is equal to the sum of the first duration and the second offset value.

[0710] Optionally, the first information satisfies at least one of the following:

[0711] The first information is the same for all target PUSCHs scheduled by the terminal on any frequency domain object;

[0712] The first information is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object;

[0713] The first information corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on a first attribute or a combination of first attributes.

[0714] The first information corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on a first attribute or a combination of first attributes.

[0715] The first information includes at least one of the second duration, the first offset value, and the second offset value.

[0716] Optionally, the first attribute or combination of the first attributes includes at least one of the following:

[0717] PUSCH timing capability;

[0718] First subcarrier spacing (SCS);

[0719] Transport block size;

[0720] The first number of time-domain cells occupied by PUSCH;

[0721] Duration of PUSCH;

[0722] The number of resource units corresponding to PUSCH, the number of data resource units, or the number of demodulation reference signal resource units;

[0723] The time-domain location of the first time-domain unit or resource unit carrying the demodulation reference signal in the PUSCH;

[0724] The type of the first time domain unit of PUSCH, or the contents of the first time domain unit of PUSCH;

[0725] Does the scheduling DCI corresponding to PUSCH simultaneously trigger a bandwidth portion BWP switch?

[0726] PUSCH physical layer priority;

[0727] Whether PUSCH reuses uplink control information (UCI);

[0728] When PUSCH multiplexes UCI, the information of the physical uplink control channel PUCCH with time-domain overlap is included.

[0729] When PUSCH reuses UCI, does it involve UCI reuse across physical layer priorities?

[0730] When PUSCH reuses UCI, it reuses either the UCI type or a combination of UCI types.

[0731] Optionally, the first SCS includes any of the following:

[0732] PUSCH's SCS;

[0733] The SCS of the scheduling DCI corresponding to PUSCH;

[0734] The maximum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH.

[0735] The minimum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH.

[0736] The SCS corresponding to the largest or smallest of the first duration determined by the SCS based on PUSCH and the first duration determined by the SCS based on the scheduling DCI corresponding to PUSCH.

[0737] Optionally, the uplink transmission device 100 further includes a second processing module, configured to perform a first operation and / or a second operation before transmitting the first PUSCH according to the first rule when the second frequency domain object corresponds to multiple uplink shared channel processing channels.

[0738] The first operation includes at least one of the following:

[0739] Assign the first PUSCH to the first PUSCH subset;

[0740] Determine the number of second PUSCH subsets for all scheduled PUSCH partitions;

[0741] Wherein, the second frequency domain object is the frequency domain object corresponding to the first PUSCH, the first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset, and each second PUSCH subset satisfies at least one of the following:

[0742] Includes all PUSCHs associated with the first processing channel subset;

[0743] Corresponding to the first processing channel subset;

[0744] Any two PUSCHs included satisfy the first rule;

[0745] The first processing channel subset includes at least one uplink shared channel processing channel among a plurality of uplink shared channel processing channels corresponding to the second frequency domain object.

[0746] The second operation includes at least one of the following:

[0747] If the fourth PUSCH that has already been scheduled finishes occupying the second processing channel subset, the network-side device will remove the fourth PUSCH from the third PUSCH subset;

[0748] The network-side device redetermines the number of the second PUSCH subset;

[0749] Before performing the second operation, the network-side device has already allocated the fourth PUSCH to the third PUSCH subset, and the third PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset; the third PUSCH subset corresponds to the second processing channel subset.

[0750] Optionally, assigning the first PUSCH to a subset of the first PUSCH includes at least one of the following:

[0751] If all scheduled PUSCHs other than the first PUSCH on the second frequency domain object have finished occupying the uplink shared channel processing channel corresponding to the second frequency domain object, a new first PUSCH subset is created, and the first PUSCH is allocated to the newly created first PUSCH subset.

[0752] If at least one fourth PUSCH subset exists in the at least one second PUSCH subset, the first PUSCH is assigned to the first fourth PUSCH subset determined by traversing each of the second PUSCH subsets in a predefined subset order, wherein the first fourth PUSCH subset is the first PUSCH subset and the fourth PUSCH subset is a single second PUSCH subset that satisfies the first condition.

[0753] If the fourth PUSCH subset does not exist in at least one second PUSCH subset, a new first PUSCH subset is created, and the first PUSCH is assigned to the newly created first PUSCH subset.

[0754] Wherein, the second attribute of each of the at least one second PUSCH subset is the same; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

[0755] Optionally, the at least one second PUSCH subset is divided into at least one second PUSCH subset group based on the second attribute of each second PUSCH subset, wherein the second attribute of each second PUSCH subset in each second PUSCH subset group is the same, and the assignment of the first PUSCH to the first PUSCH subset includes at least one of the following:

[0756] If a first PUSCH subset group does not exist in at least one second PUSCH subset group, a new first PUSCH subset group is created, and the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group.

[0757] If a first PUSCH subset group exists in the at least one second PUSCH subset group, and at least one fifth PUSCH subset exists in the first PUSCH subset group, the first PUSCH is assigned to the first fifth PUSCH subset determined by traversing each of the second PUSCH subsets in the first PUSCH subset group based on a predefined subset order. The first fifth PUSCH subset is the first PUSCH subset, and the fifth PUSCH subset is a single second PUSCH subset in the first PUSCH subset group that satisfies the first condition.

[0758] If a first PUSCH subset exists in at least one second PUSCH subset group, and the fifth PUSCH subset does not exist in the first PUSCH subset group, the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group.

[0759] Wherein, the first PUSCH subset group matches the first PUSCH; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

[0760] Optionally, the order of the predefined subsets is determined based on at least one of the following:

[0761] The creation time of the PUSCH subset;

[0762] Physical layer priority corresponding to the PUSCH subset;

[0763] The number of PUSCHs contained in the PUSCH subset;

[0764] The start or end time of the scheduling DCI corresponding to PUSCH in the PUSCH subset;

[0765] The start or end time of the first control resource set where the scheduling DCI corresponding to the PUSCH in the PUSCH subset is located.

[0766] The start or end time of the second time-domain unit where the first control resource set is located;

[0767] The start or end time of PUSCH in the PUSCH subset;

[0768] The start or end time of the second time-domain unit where PUSCH is located in the PUSCH subset.

[0769] Optionally, the uplink transmission device 700 further includes a second processing module, configured to determine the number of uplink shared channel processing channels that the scheduled PUSCH needs to occupy based on the number of the second PUSCH subsets and the number of uplink shared channel processing channels contained in the first processing channel subset corresponding to each second PUSCH subset.

[0770] Optionally, each of the first processing channel subsets includes a single uplink shared channel processing channel, or each of the first processing channel subsets includes M uplink shared channel processing channels;

[0771] M is determined based on at least one of the following:

[0772] The number of PUSCHs contained in the corresponding second PUSCH subset;

[0773] The attributes of the PUSCH contained in the corresponding second subset of PUSCH;

[0774] The corresponding second subset of PUSCH contains the attributes of the scheduling DCI corresponding to the PUSCH.

[0775] Optionally, the frequency domain object includes any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range; or, the frequency domain object includes at least one first frequency domain object, the first frequency domain object including any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range.

[0776] Optionally, the uplink transmission device 700 further includes a second processing module for performing any of the following:

[0777] The number of uplink shared channel processing channels that the scheduled PUSCH needs to occupy should not exceed the maximum number of uplink shared channel processing channels that the terminal supports for parallel processing.

[0778] It is expected that any scheduled PUSCH can be assigned to the corresponding uplink shared channel processing channel.

[0779] Optionally, when multiple TRPs are configured, the fifth PUSCH satisfies any of the following:

[0780] Corresponds to the target TRP among the plurality of TRPs;

[0781] Corresponds to any one of the plurality of TRPs;

[0782] Wherein, the fifth PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target TRP is one of the plurality of TRPs.

[0783] Optionally, the sixth PUSCH satisfies at least one of the following:

[0784] When using type A repetition transmission, the sixth PUSCH is any one of the at least one PUSCH repetition transmissions corresponding to a PUSCH.

[0785] When using type B repetition transmission, the sixth PUSCH is any one of the at least one actual PUSCH repetition transmissions corresponding to a PUSCH.

[0786] In the case of using multi-timeslot transport block (TBoMS) transmission, the sixth PUSCH is any one of the PUSCH transmissions in at least one PUSCH transmission corresponding to a TBoMS transmission.

[0787] In the case where a single DCI can schedule multiple PUSCHs, the sixth PUSCH is any one of at least one PUSCH scheduled by a DCI.

[0788] The sixth PUSCH is either the first PUSCH, the second PUSCH, or the third PUSCH.

[0789] Optionally, if a single DCI can schedule PUSCHs on multiple serving cells, the seventh PUSCH is any one of at least one PUSCH scheduled by a DCI on the target serving cell.

[0790] Wherein, the seventh PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target serving cell is any one of the at least one serving cell in the one DCI scheduling.

[0791] Optionally, the frequency domain object includes any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range; or, the frequency domain object includes at least one first frequency domain object, the first frequency domain object including any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range.

[0792] The uplink transmission device provided in this application embodiment can achieve Figures 3 to 4 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0793] like Figure 8As shown, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores a program or instructions that can run on the processor 801. When the program or instructions are executed by the processor 801, they implement the various steps of the above-described uplink transmission method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0794] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 3 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 6 The upstream transmission device shown. Specifically, Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0795] The terminal 900 includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.

[0796] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 910 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0797] It should be understood that, in this embodiment, the input unit 904 may include a graphics processor 9041 and a microphone 9042. The graphics processor 9041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0798] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 901 can transmit it to the processor 910 for processing; in addition, the radio frequency unit 901 can send uplink data to the network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0799] The memory 909 can be used to store software programs or instructions, as well as various data. The memory 909 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 909 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 909 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0800] Processor 910 may include one or more processing units; optionally, processor 910 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 910.

[0801] The radio frequency unit 901 is used to perform at least one of the following:

[0802] Transmit the first physical uplink shared channel (PUSCH) according to the first rule;

[0803] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), it is expected that the first rule will not be applied to the second PUSCH.

[0804] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, it is not expected that the A-CSI report corresponding to the A-CSI measurement will always be carried on the third PUSCH, which is scheduled by the first DCI.

[0805] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0806] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0807] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0808] If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time when the first target PUSCH occupies the target processing channel, and the target start time of the second target PUSCH is the start time when the second target PUSCH occupies the target processing channel.

[0809] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0810] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0811] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 4 The steps of the method embodiment shown are illustrated. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0812] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 7 The upstream transmission device shown. For example... Figure 10As shown, the network-side device 1000 includes: an antenna 1001, a radio frequency (RF) device 1002, a baseband device 1003, a processor 1004, and a memory 1005. The antenna 1001 is connected to the RF device 1002. In the uplink direction, the RF device 1002 receives information through the antenna 1001 and transmits the received information to the baseband device 1003 for processing. In the downlink direction, the baseband device 1003 processes the information to be transmitted and sends it to the RF device 1002. The RF device 1002 processes the received information and transmits it through the antenna 1001.

[0813] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1003, which includes a baseband processor.

[0814] The baseband device 1003 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 10 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1005 via a bus interface to call the program or instructions in the memory 1005 to execute the network-side device operation shown in the above method embodiment.

[0815] The network-side device may also include a network interface 1006, such as a Common Public Radio Interface (CPRI).

[0816] The radio frequency device 1002 is used to perform at least one of the following:

[0817] The first physical uplink shared channel (PUSCH) is scheduled and received according to the first rule;

[0818] When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the first rule is guaranteed not to be applied to the second PUSCH.

[0819] When the first downlink control information (DCI) is used to trigger an A-CSI measurement, an A-CSI report corresponding to the A-CSI measurement can be received on an uplink channel different from the third PUSCH, which is scheduled by the first DCI.

[0820] The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following:

[0821] The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH;

[0822] The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH;

[0823] When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, the time when preparation for processing is completed, the time of transmission start or transmission end. The target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel.

[0824] Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

[0825] Furthermore, the network-side device 1000 in this embodiment of the application also includes: a program or instructions stored in memory 1005 and executable on processor 1004, wherein processor 1004 calls the program or instructions in memory 1005 to execute. Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0826] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described uplink transmission method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0827] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0828] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described uplink transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0829] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0830] This application also provides a computer program / program product, which includes computer instructions. The computer program / program product is executed by at least one processor to implement the various processes of the above-described uplink transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0831] This application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the uplink transmission method on the terminal side as described above, and the network-side device can be used to perform the steps of the uplink transmission method on the network-side device as described above.

[0832] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0833] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0834] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. An uplink transmission method, characterized in that, Includes at least one of the following: The terminal transmits the first physical uplink shared channel (PUSCH) according to the first rule; When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the terminal expects the second PUSCH not to apply the first rule. When the first downlink control information (DCI) is used to trigger an A-CSI measurement, the terminal does not expect to always carry the A-CSI report corresponding to the A-CSI measurement on the third PUSCH, which is scheduled by the first DCI. The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following: The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH; The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH; If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time when the first target PUSCH occupies the target processing channel, and the target start time of the second target PUSCH is the start time when the second target PUSCH occupies the target processing channel. Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

2. The method according to claim 1, characterized in that, The first target PUSCH and / or the second target PUSCH meet predefined requirements, which include at least one of the following: PUSCH is dynamically scheduled by DCI; PUSCH carries the uplink shared channel; PUSCH transmission requires the HARQ process to be used.

3. The method according to claim 1, characterized in that, The target time is any one of the following: The start or end time of DCI; The start or end time of the first time domain unit of DCI; The start or end time of the first time domain unit of DCI; The start or end time of the second time-domain unit of the DCI is detected; The start or end time of the DCI control resource set CORESET was detected; The start or end time of the second time-domain unit where the CORESET of the DCI is located is detected; The start or end time of the detected monitoring occasion for the Physical Downlink Control Channel (PDCCH) of the DCI; The start or end time of the second time-domain unit where the DCI's PDCCH monitoring occasion is located is detected.

4. The method according to any one of claims 1 to 3, characterized in that, The first rule also includes at least one of the following: The time when the first target PUSCH is ready to be processed is earlier than or no later than the target start time; The transmission start time of the first target PUSCH is earlier than or no later than the target start time; The end time of the transmission of the first target PUSCH is earlier than or no later than the start time of the target.

5. The method according to any one of claims 1 to 4, characterized in that, The target start time is earlier than or no later than the start time of the second target PUSCH, and the interval between the target start time and the start time of the second target PUSCH is the first duration corresponding to the second target PUSCH.

6. The method according to claim 5, characterized in that, The start time of the second target PUSCH is determined based on any of the following: The first moment; First moment and time in advance; Wherein, the first moment is any one of the following: The start time of the first time domain unit occupied by the second target PUSCH; The start time of the first time domain unit of the first data carried by the second target PUSCH; The start time of the first time-domain unit of the first bearer demodulation reference signal occupied by the second target PUSCH; The start time of the second time domain unit or the first second time domain unit where the second target PUSCH is located.

7. The method according to claim 5, characterized in that, The first duration satisfies any one of the following: The first duration is the same for all target PUSCHs scheduled by the terminal on any frequency domain object. The first duration is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object. The first duration corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on the first attribute or a combination of the first attributes. The first duration corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on the first attribute or a combination of the first attributes. Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

8. The method according to any one of claims 1 to 7, characterized in that, The second duration for which the target PUSCH occupies the target processing channel is determined based on at least one of the following: The duration reported by the terminal; The duration agreed upon in the agreement; The third duration is determined based on the first duration corresponding to the target PUSCH, where the first duration is the start time when the target PUSCH occupies the target processing channel; Duration of high-level signaling configuration; Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

9. The method according to claim 8, characterized in that, The third duration satisfies any one of the following: The third duration is equal to the first duration; The third duration is equal to the sum of the first duration and the duration of the target PUSCH; The third duration is equal to the sum of the first duration, the duration of the target PUSCH, and the first offset value; The third duration is equal to the sum of the first duration and the second offset value.

10. The method according to claim 9, characterized in that, The first piece of information satisfies at least one of the following: The first information is the same for all target PUSCHs scheduled by the terminal on any frequency domain object; The first information is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object; The first information corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on a first attribute or a combination of first attributes. The first information corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on a first attribute or a combination of first attributes. The first information includes at least one of the second duration, the first offset value, and the second offset value.

11. The method according to claim 7 or 10, characterized in that, The first attribute or combination of the first attributes includes at least one of the following: PUSCH timing capability; First subcarrier spacing (SCS); Transport block size; The first number of time-domain cells occupied by PUSCH; Duration of PUSCH; The number of resource units corresponding to PUSCH, the number of data resource units, or the number of demodulation reference signal resource units; The time-domain location of the first time-domain unit or resource unit carrying the demodulation reference signal in the PUSCH; The type of the first time domain unit of PUSCH, or the contents of the first time domain unit of PUSCH; Does the scheduling DCI corresponding to PUSCH simultaneously trigger a bandwidth portion BWP switch? PUSCH physical layer priority; Whether PUSCH reuses uplink control information (UCI); When PUSCH multiplexes UCI, the information of the physical uplink control channel PUCCH with time-domain overlap is included. When PUSCH reuses UCI, does it involve UCI reuse across physical layer priorities? When PUSCH reuses UCI, it reuses either the UCI type or a combination of UCI types.

12. The method according to claim 11, characterized in that, The first SCS includes any one of the following: PUSCH's SCS; The SCS of the scheduling DCI corresponding to PUSCH; The maximum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH. The minimum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH. The SCS corresponding to the largest or smallest of the first duration determined by the SCS based on PUSCH and the first duration determined by the SCS based on the scheduling DCI corresponding to PUSCH.

13. The method according to claim 1, characterized in that, The method further includes: In the case where the second frequency domain object corresponds to multiple uplink shared channel processing channels, the terminal performs a first operation and / or a second operation before transmitting the first PUSCH according to the first rule; The first operation includes at least one of the following: Assign the first PUSCH to the first PUSCH subset; Determine the number of second PUSCH subsets for all scheduled PUSCH partitions; Wherein, the second frequency domain object is the frequency domain object corresponding to the first PUSCH, the first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset, and each second PUSCH subset satisfies at least one of the following: Includes all PUSCHs associated with the first processing channel subset; Corresponding to the first subset of processing channels; Any two PUSCHs included satisfy the first rule; The first processing channel subset includes at least one uplink shared channel processing channel among a plurality of uplink shared channel processing channels corresponding to the second frequency domain object. The second operation includes at least one of the following: If the fourth PUSCH that has already been scheduled finishes occupying the second processing channel subset, the terminal will remove the fourth PUSCH from the third PUSCH subset. The terminal re-determines the number of the second PUSCH subset; Before performing the second operation, the terminal has already allocated the fourth PUSCH to the third PUSCH subset, and the third PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset; the third PUSCH subset corresponds to the second processing channel subset.

14. The method according to claim 13, characterized in that, The process of assigning the first PUSCH to a subset of the first PUSCH includes at least one of the following: If all scheduled PUSCHs other than the first PUSCH on the second frequency domain object have finished occupying the uplink shared channel processing channel corresponding to the second frequency domain object, a new first PUSCH subset is created, and the first PUSCH is allocated to the newly created first PUSCH subset. If at least one fourth PUSCH subset exists in the at least one second PUSCH subset, the first PUSCH is assigned to the first fourth PUSCH subset determined by traversing each of the second PUSCH subsets in a predefined subset order, wherein the first fourth PUSCH subset is the first PUSCH subset and the fourth PUSCH subset is a single second PUSCH subset that satisfies the first condition. If the fourth PUSCH subset does not exist in at least one second PUSCH subset, a new first PUSCH subset is created, and the first PUSCH is assigned to the newly created first PUSCH subset. Wherein, the second attribute of each of the at least one second PUSCH subset is the same; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

15. The method according to claim 13, characterized in that, The at least one second PUSCH subset is divided into at least one second PUSCH subset group based on the second attribute of each second PUSCH subset, wherein the second attribute of each second PUSCH subset in each second PUSCH subset group is the same, and the assignment of the first PUSCH to the first PUSCH subset includes at least one of the following: If a first PUSCH subset group does not exist in at least one second PUSCH subset group, a new first PUSCH subset group is created, and the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group. If a first PUSCH subset group exists in the at least one second PUSCH subset group, and at least one fifth PUSCH subset exists in the first PUSCH subset group, the first PUSCH is assigned to the first fifth PUSCH subset determined by traversing each of the second PUSCH subsets in the first PUSCH subset group based on a predefined subset order. The first fifth PUSCH subset is the first PUSCH subset, and the fifth PUSCH subset is a single second PUSCH subset in the first PUSCH subset group that satisfies the first condition. If a first PUSCH subset exists in at least one second PUSCH subset group, and the fifth PUSCH subset does not exist in the first PUSCH subset group, the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group. Wherein, the first PUSCH subset group matches the first PUSCH; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

16. The method according to claim 14 or 15, characterized in that, The order of the predefined subsets is determined based on at least one of the following: The creation time of the PUSCH subset; Physical layer priority corresponding to the PUSCH subset; The number of PUSCHs contained in the PUSCH subset; The start or end time of the scheduling DCI corresponding to PUSCH in the PUSCH subset; The start or end time of the first control resource set where the scheduling DCI corresponding to the PUSCH in the PUSCH subset is located. The start or end time of the second time-domain unit where the first control resource set is located; The start or end time of PUSCH in the PUSCH subset; The start or end time of the second time-domain unit where PUSCH is located in the PUSCH subset.

17. The method according to claim 13, characterized in that, The method further includes: The terminal determines the number of uplink shared channel processing channels that the scheduled PUSCH needs to occupy based on the number of the second PUSCH subsets and the number of uplink shared channel processing channels contained in the first processing channel subset corresponding to each second PUSCH subset.

18. The method according to claim 17, characterized in that, Each of the first processing channel subsets includes a single uplink shared channel processing channel, or each of the first processing channel subsets includes M uplink shared channel processing channels; M is determined based on at least one of the following: The number of PUSCHs contained in the corresponding second PUSCH subset; The attributes of the PUSCHs contained in the corresponding second subset of PUSCHs; The corresponding second subset of PUSCH contains the attributes of the scheduling DCI corresponding to the PUSCH.

19. The method according to any one of claims 1 to 18, characterized in that, The frequency domain object includes any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range; or, the frequency domain object includes at least one first frequency domain object, the first frequency domain object including any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range.

20. The method according to any one of claims 1 to 19, characterized in that, The method further includes any one of the following: The terminal expects that the number of uplink shared channel processing channels occupied by the scheduled PUSCHs does not exceed the maximum number of uplink shared channel processing channels that the terminal supports for parallel processing. The terminal expects any scheduled PUSCH to be assigned to the corresponding uplink shared channel processing channel.

21. The method according to any one of claims 1 to 20, characterized in that, When multiple TRPs are configured, the fifth PUSCH satisfies any of the following: Corresponds to the target TRP among the plurality of TRPs; Corresponds to any one of the plurality of TRPs; Wherein, the fifth PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target TRP is one of the plurality of TRPs.

22. The method according to any one of claims 1 to 20, characterized in that, The sixth PUSCH satisfies at least one of the following: When using type A repetition transmission, the sixth PUSCH is any one of the at least one PUSCH repetition transmissions corresponding to a PUSCH. When using type B repetition transmission, the sixth PUSCH is any one of the at least one actual PUSCH repetition transmissions corresponding to a PUSCH. In the case of using multi-timeslot transport block (TBoMS) transmission, the sixth PUSCH is any one of the PUSCH transmissions in at least one PUSCH transmission corresponding to a TBoMS transmission. In the case where a single DCI can schedule multiple PUSCHs, the sixth PUSCH is any one of at least one PUSCH scheduled by a DCI. The sixth PUSCH is either the first PUSCH, the second PUSCH, or the third PUSCH.

23. The method according to any one of claims 1 to 20, characterized in that, In the case where a single DCI can schedule PUSCHs on multiple serving cells, the seventh PUSCH is any one of at least one PUSCH scheduled by a DCI on the target serving cell. Wherein, the seventh PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target serving cell is any one of the at least one serving cell in the one DCI scheduling.

24. An uplink transmission method, characterized in that, Includes at least one of the following: Network-side devices schedule and receive the first physical uplink shared channel (PUSCH) according to the first rule; When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the network-side device guarantees that the first rule will not be applied to the second PUSCH. When the first downlink control information (DCI) is used to trigger an A-CSI measurement, the network-side device is able to receive an A-CSI report corresponding to the A-CSI measurement on an uplink channel different from the third PUSCH, wherein the third PUSCH is scheduled by the first DCI. The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following: The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH; The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH; When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, the time when preparation for processing is completed, the time of transmission start or transmission end. The target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel. Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

25. The method according to claim 24, characterized in that, The first target PUSCH and / or the second target PUSCH meet predefined requirements, which include at least one of the following: PUSCH is dynamically scheduled by DCI; PUSCH carries the uplink shared channel; PUSCH transmission requires the HARQ process to be used.

26. The method according to claim 24, characterized in that, The target time is any one of the following: The start or end time of DCI; The start or end time of the first time domain unit of DCI; The start or end time of the first time domain unit of DCI; The start or end time of the second time-domain unit of the DCI is detected; The start or end time of the DCI control resource set CORESET was detected; The start or end time of the second time-domain unit where the CORESET of the DCI is located is detected; The start or end time of the detected monitoring occasion for the Physical Downlink Control Channel (PDCCH) of the DCI; The start or end time of the second time-domain unit where the DCI's PDCCH monitoring occasion is located is detected.

27. The method according to any one of claims 24 to 26, characterized in that, The first rule also includes at least one of the following: The time when the first target PUSCH is ready to be processed is earlier than or no later than the target start time; The transmission start time of the first target PUSCH is earlier than or no later than the target start time; The end time of the transmission of the first target PUSCH is earlier than or no later than the start time of the target.

28. The method according to any one of claims 24 to 27, characterized in that, The target start time is earlier than or no later than the start time of the second target PUSCH, and the interval between the target start time and the start time of the second target PUSCH is the first duration corresponding to the second target PUSCH.

29. The method according to claim 28, characterized in that, The start time of the second target PUSCH is determined based on any of the following: The first moment; First moment and time in advance; Wherein, the first moment is any one of the following: The start time of the first time domain unit occupied by the second target PUSCH; The start time of the first time domain unit of the first data carried by the second target PUSCH; The start time of the first time-domain unit of the first bearer demodulation reference signal occupied by the second target PUSCH; The start time of the second time domain unit or the first second time domain unit where the second target PUSCH is located.

30. The method according to claim 29, characterized in that, The first duration satisfies any one of the following: All target PUSCHs scheduled by the terminal on any frequency domain object have the same first duration; The first duration is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object. The first duration corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on the first attribute or a combination of the first attributes. The first duration corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on the first attribute or a combination of the first attributes. Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

31. The method according to any one of claims 24 to 30, characterized in that, The second duration for which the target PUSCH occupies the target processing channel is determined based on at least one of the following: The duration of terminal reporting; The duration agreed upon in the agreement; The third duration is determined based on the first duration corresponding to the target PUSCH, where the first duration is the start time when the target PUSCH occupies the target processing channel; Duration of high-level signaling configuration; Wherein, the target PUSCH is the first target PUSCH and / or the second target PUSCH.

32. The method according to claim 31, characterized in that, The third duration satisfies any one of the following: The third duration is equal to the first duration; The third duration is equal to the sum of the first duration and the duration of the target PUSCH; The third duration is equal to the sum of the first duration, the duration of the target PUSCH, and the first offset value; The third duration is equal to the sum of the first duration and the second offset value.

33. The method according to claim 32, characterized in that, The first piece of information satisfies at least one of the following: The first information is the same for all target PUSCHs scheduled by the terminal on any frequency domain object; The first information is the same for all target PUSCHs scheduled by the terminal on the same frequency domain object; The first information corresponding to all target PUSCHs scheduled by the terminal on the same frequency domain object is determined based on a first attribute or a combination of first attributes. The first information corresponding to all target PUSCHs scheduled by the terminal on any frequency domain object is determined based on a first attribute or a combination of first attributes. The first information includes at least one of the second duration, the first offset value, and the second offset value.

34. The method according to claim 30 or 33, characterized in that, The first attribute or combination of the first attributes includes at least one of the following: PUSCH timing capability; First subcarrier spacing (SCS); Transport block size; The first number of time-domain cells occupied by PUSCH; Duration of PUSCH; The number of resource units corresponding to PUSCH, the number of data resource units, or the number of demodulation reference signal resource units; The time-domain location of the first time-domain unit or resource unit carrying the demodulation reference signal in the PUSCH; The type of the first time domain unit of PUSCH, or the contents of the first time domain unit of PUSCH; Does the scheduling DCI corresponding to PUSCH simultaneously trigger a bandwidth portion BWP switch? PUSCH physical layer priority; Whether PUSCH reuses uplink control information (UCI); When PUSCH multiplexes UCI, the information of the physical uplink control channel PUCCH with time-domain overlap is included. When PUSCH reuses UCI, does it involve UCI reuse across physical layer priorities? When PUSCH reuses UCI, it reuses either the UCI type or a combination of UCI types.

35. The method according to claim 34, characterized in that, The first SCS includes any one of the following: PUSCH's SCS; The SCS of the scheduling DCI corresponding to PUSCH; The maximum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH. The minimum SCS between the SCS of PUSCH and the SCS of the corresponding scheduling DCI of PUSCH. The SCS corresponding to the largest or smallest of the first duration determined by the SCS based on PUSCH and the first duration determined by the SCS based on the scheduling DCI corresponding to PUSCH.

36. The method according to claim 26, characterized in that, The method further includes: In the case where the second frequency domain object corresponds to multiple uplink shared channel processing channels, the network-side device performs a first operation and / or a second operation before transmitting the first PUSCH according to the first rule; The first operation includes at least one of the following: Assign the first PUSCH to the first PUSCH subset; Determine the number of second PUSCH subsets for all scheduled PUSCH partitions; Wherein, the second frequency domain object is the frequency domain object corresponding to the first PUSCH, the first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset, and each second PUSCH subset satisfies at least one of the following: Includes all PUSCHs associated with the first processing channel subset; Corresponding to the first subset of processing channels; Any two PUSCHs included satisfy the first rule; The first processing channel subset includes at least one uplink shared channel processing channel among a plurality of uplink shared channel processing channels corresponding to the second frequency domain object. The second operation includes at least one of the following: If the fourth PUSCH that has already been scheduled finishes occupying the second processing channel subset, the network-side device will remove the fourth PUSCH from the third PUSCH subset; The network-side device redetermines the number of the second PUSCH subset; Before performing the second operation, the network-side device has already allocated the fourth PUSCH to the third PUSCH subset, and the third PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset; the third PUSCH subset corresponds to the second processing channel subset.

37. The method according to claim 36, characterized in that, The process of assigning the first PUSCH to a subset of the first PUSCH includes at least one of the following: If all scheduled PUSCHs other than the first PUSCH on the second frequency domain object have finished occupying the uplink shared channel processing channel corresponding to the second frequency domain object, a new first PUSCH subset is created, and the first PUSCH is allocated to the newly created first PUSCH subset. If at least one fourth PUSCH subset exists in the at least one second PUSCH subset, the first PUSCH is assigned to the first fourth PUSCH subset determined by traversing each of the second PUSCH subsets in a predefined subset order, wherein the first fourth PUSCH subset is the first PUSCH subset and the fourth PUSCH subset is a single second PUSCH subset that satisfies the first condition. If the fourth PUSCH subset does not exist in at least one second PUSCH subset, a new first PUSCH subset is created, and the first PUSCH is assigned to the newly created first PUSCH subset. Wherein, the second attribute of each of the at least one second PUSCH subset is the same; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

38. The method according to claim 36, characterized in that, The at least one second PUSCH subset is divided into at least one second PUSCH subset group based on the second attribute of each second PUSCH subset, wherein the second attribute of each second PUSCH subset in each second PUSCH subset group is the same, and the assignment of the first PUSCH to the first PUSCH subset includes at least one of the following: If a first PUSCH subset group does not exist in at least one second PUSCH subset group, a new first PUSCH subset group is created, and the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group. If a first PUSCH subset group exists in the at least one second PUSCH subset group, and at least one fifth PUSCH subset exists in the first PUSCH subset group, the first PUSCH is assigned to the first fifth PUSCH subset determined by traversing each of the second PUSCH subsets in the first PUSCH subset group based on a predefined subset order. The first fifth PUSCH subset is the first PUSCH subset, and the fifth PUSCH subset is a single second PUSCH subset in the first PUSCH subset group that satisfies the first condition. If a first PUSCH subset exists in at least one second PUSCH subset group, and the fifth PUSCH subset does not exist in the first PUSCH subset group, the first PUSCH is assigned to the newly created first PUSCH subset in the first PUSCH subset group. Wherein, the first PUSCH subset group matches the first PUSCH; the first condition includes: the first PUSCH and any PUSCH in the second PUSCH subset satisfy the first rule.

39. The method according to claim 37 or 38, characterized in that, The order of the predefined subsets is determined based on at least one of the following: The creation time of the PUSCH subset; Physical layer priority corresponding to the PUSCH subset; The number of PUSCHs contained in the PUSCH subset; The start or end time of the scheduling DCI corresponding to PUSCH in the PUSCH subset; The start or end time of the first control resource set where the scheduling DCI corresponding to the PUSCH in the PUSCH subset is located. The start or end time of the second time-domain unit where the first control resource set is located; The start or end time of PUSCH in the PUSCH subset; The start or end time of the second time-domain unit where PUSCH is located in the PUSCH subset.

40. The method according to claim 36, characterized in that, The method further includes: The network-side device determines the number of uplink shared channel processing channels that the scheduled PUSCH needs to occupy based on the number of the second PUSCH subset and the number of uplink shared channel processing channels contained in the first processing channel subset corresponding to each second PUSCH subset.

41. The method according to claim 40, characterized in that, Each of the first processing channel subsets includes a single uplink shared channel processing channel, or each of the first processing channel subsets includes M uplink shared channel processing channels; M is determined based on at least one of the following: The number of PUSCHs contained in the corresponding second PUSCH subset; The attributes of the PUSCHs contained in the corresponding second subset of PUSCHs; The corresponding second subset of PUSCH contains the attributes of the scheduling DCI corresponding to the PUSCH.

42. The method according to any one of claims 24 to 41, characterized in that, The frequency domain object includes any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range; or, the frequency domain object includes at least one first frequency domain object, the first frequency domain object including any one of the following: serving cell, scheduled serving cell, active serving cell, non-dormant serving cell, carrier, bandwidth portion (BWP), a continuous frequency domain resource, frequency portion, frequency domain unit, frequency band, frequency band combination, and frequency range.

43. The method according to any one of claims 24 to 42, characterized in that, The method further includes any one of the following: The network-side device expects that the number of uplink shared channel processing channels occupied by the scheduled PUSCHs does not exceed the maximum number of uplink shared channel processing channels supported by the terminal for parallel processing. The network-side device expects any scheduled PUSCH to be assigned to the corresponding uplink shared channel processing channel.

44. The method according to any one of claims 24 to 43, characterized in that, When multiple TRPs are configured, the fifth PUSCH satisfies any of the following: Corresponds to the target TRP among the plurality of TRPs; Corresponds to any one of the plurality of TRPs; Wherein, the fifth PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target TRP is one of the plurality of TRPs.

45. The method according to any one of claims 24 to 43, characterized in that, The sixth PUSCH satisfies at least one of the following: When using type A repetition transmission, the sixth PUSCH is any one of the at least one PUSCH repetition transmissions corresponding to a PUSCH. When using type B repetition transmission, the sixth PUSCH is any one of the at least one actual PUSCH repetition transmissions corresponding to a PUSCH. In the case of using multi-timeslot transport block (TBoMS) transmission, the sixth PUSCH is any one of the PUSCH transmissions in at least one PUSCH transmission corresponding to a TBoMS transmission. In the case where a single DCI can schedule multiple PUSCHs, the sixth PUSCH is any one of at least one PUSCH scheduled by a DCI. The sixth PUSCH is either the first PUSCH, the second PUSCH, or the third PUSCH.

46. ​​The method according to any one of claims 24 to 43, characterized in that, In the case where a single DCI can schedule PUSCHs on multiple serving cells, the seventh PUSCH is any one of at least one PUSCH scheduled by a DCI on the target serving cell. Wherein, the seventh PUSCH is the first PUSCH, the second PUSCH, or the third PUSCH; the target serving cell is any one of the at least one serving cell in the one DCI scheduling.

47. An uplink transmission device, characterized in that, include: The sending module is configured to perform at least one of the following: Transmit the first physical uplink shared channel (PUSCH) according to the first rule; When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), it is expected that the first rule will not be applied to the second PUSCH. When the first downlink control information (DCI) is used to trigger an A-CSI measurement, it is not expected that the A-CSI report corresponding to the A-CSI measurement will always be carried on the third PUSCH, which is scheduled by the first DCI. The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following: The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH; The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH; If the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time when the first target PUSCH occupies the target processing channel, and the target start time of the second target PUSCH is the start time when the second target PUSCH occupies the target processing channel. Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

48. The apparatus according to claim 47, characterized in that, The first target PUSCH and / or the second target PUSCH meet predefined requirements, which include at least one of the following: PUSCH is dynamically scheduled by DCI; PUSCH carries the uplink shared channel; PUSCH transmission requires the HARQ process to be used.

49. An uplink transmission device, characterized in that, include: The receiving module is configured to perform at least one of the following: The first physical uplink shared channel (PUSCH) is scheduled and received according to the first rule; When the second PUSCH is scheduled to carry aperiodic channel state information (A-CSI), the first rule is guaranteed not to be applied to the second PUSCH. When the first downlink control information (DCI) is used to trigger an A-CSI measurement, an A-CSI report corresponding to the A-CSI measurement can be received on an uplink channel different from the third PUSCH, which is scheduled by the first DCI. The first rule is used to characterize the timing relationship requirement between any two PUSCHs on the same frequency domain object, and the first rule includes at least one of the following: The start time of the first target PUSCH is no earlier than the end time of the second target PUSCH; The start time of the first target PUSCH is equal to or later than the end time of the second target PUSCH; When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, the target end time of the first target PUSCH is earlier than or no later than the target start time of the second target PUSCH. The target end time of the first target PUSCH is the end time of the first target PUSCH occupying the target processing channel, the time when preparation for processing is completed, the time of transmission start or transmission end. The target start time of the second target PUSCH is the start time of the second target PUSCH occupying the target processing channel. Wherein, the first target PUSCH and the second target PUSCH correspond to the same first frequency domain object, the target time of scheduling the first target DCI of the first target PUSCH is later than the target time of scheduling the second target DCI of the second target PUSCH, and the target processing channel includes the uplink shared channel processing channel corresponding to the first frequency domain object.

50. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the uplink transmission method as described in any one of claims 1 to 23.

51. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the uplink transmission method as described in any one of claims 24 to 46.

52. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the uplink transmission method as described in any one of claims 1 to 46.

53. A computer program product, characterized in that, Includes computer instructions, which, when executed by a processor, implement the steps of the uplink transmission method as described in any one of claims 1 to 46.

Images