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

Abstract

The application discloses an uplink transmission processing method and device, a terminal and a network side equipment, and belongs to the technical field of communication. The uplink transmission processing method comprises the following steps: in the case that a first physical uplink shared channel (PUSCH) and a second PUSCH do not satisfy a first rule, a terminal performs a first operation: wherein the first operation comprises any one of the following: the second PUSCH is backed off to a third PUSCH, and the third PUSCH does not apply the first rule; the transmission of the first PUSCH or the second PUSCH is delayed; the transmission of the first PUSCH or the second PUSCH is discarded; wherein the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by a first downlink control information (DCI), and the second PUSCH is scheduled by a second DCI; and the first rule is used to represent the timing relationship requirement between any two PUSCHs on the same frequency domain object.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an uplink transmission processing 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 processing method, apparatus, terminal, and network-side device, which can solve the problem of poor uplink transmission performance.

[0004] Firstly, an uplink transmission processing method is provided, including:

[0005] If the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule, the terminal performs the first operation:

[0006] The first operation includes any one of the following:

[0007] The second PUSCH is rolled back to the third PUSCH, and the third PUSCH is not subject to the first rule.

[0008] Delay the transmission of the first PUSCH or the second PUSCH;

[0009] Discard the transmission of the first PUSCH or the second PUSCH;

[0010] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

[0011] Secondly, an uplink transmission processing method is provided, including:

[0012] If the first physical uplink shared channel (PUSCH) and the second PUSCH for the same terminal do not satisfy the first rule, the network-side device performs the second operation:

[0013] The second operation includes any one of the following:

[0014] Receive a third PUSCH that is rolled back from the second PUSCH, and the third PUSCH is not subject to the first rule;

[0015] Delay receiving the first PUSCH or the second PUSCH;

[0016] We do not expect to receive the first PUSCH or the second PUSCH;

[0017] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

[0018] Thirdly, an uplink transmission processing apparatus is provided, comprising:

[0019] The transmitting module is configured to perform a first operation when the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule:

[0020] The first operation includes any one of the following:

[0021] The second PUSCH is rolled back to the third PUSCH, and the third PUSCH is not subject to the first rule.

[0022] Delay the transmission of the first PUSCH or the second PUSCH;

[0023] Discard the transmission of the first PUSCH or the second PUSCH;

[0024] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

[0025] Fourthly, an uplink transmission processing apparatus is provided, comprising:

[0026] The receiving module is configured to perform a second operation when the first physical uplink shared channel (PUSCH) and the second PUSCH for the same terminal do not satisfy the first rule:

[0027] The second operation includes any one of the following:

[0028] Receive a third PUSCH that is rolled back from the second PUSCH, and the third PUSCH is not subject to the first rule;

[0029] Delay receiving the first PUSCH or the second PUSCH;

[0030] We do not expect to receive the first PUSCH or the second PUSCH;

[0031] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

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

[0033] 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.

[0034] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to perform a first operation when the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy a first rule:

[0035] The first operation includes any one of the following:

[0036] The second PUSCH is rolled back to the third PUSCH, and the third PUSCH is not subject to the first rule.

[0037] Delay the transmission of the first PUSCH or the second PUSCH;

[0038] Discard the transmission of the first PUSCH or the second PUSCH;

[0039] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

[0040] 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.

[0041] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to perform a second operation when a first physical uplink shared channel (PUSCH) and a second PUSCH for the same terminal do not satisfy a first rule:

[0042] The second operation includes any one of the following:

[0043] Receive a third PUSCH that is rolled back from the second PUSCH, and the third PUSCH is not subject to the first rule;

[0044] Delay receiving the first PUSCH or the second PUSCH;

[0045] We do not expect to receive the first PUSCH or the second PUSCH;

[0046] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] In this embodiment, when the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule, the terminal performs a first operation: The first operation includes any one of the following: reverting the second PUSCH to a third PUSCH, where the third PUSCH is not subject to the first rule; delaying the transmission of the first PUSCH or the second PUSCH; or discarding the transmission of the first PUSCH or the second PUSCH. The first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI. The first rule characterizes the timing relationship requirements between any two PUSCHs on the same frequency domain object. Because this embodiment clearly defines the terminal's behavior when the first rule is not satisfied between PUSCHs, the impact of the first rule on PUSCH transmission can be avoided or mitigated. Therefore, this embodiment can improve uplink transmission performance. Attached Figure Description

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

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

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

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

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

[0057] Figure 6 This is a schematic diagram of another uplink transmission processing device provided in an embodiment of this application;

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

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

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

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

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

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

[0067] 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:

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

[0069] 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.

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

[0071] 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 transmitting 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.

[0072] 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.

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

[0074] 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.

[0075] 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.

[0076] Table 1:

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

[0078] Table 2:

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

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

[0081] 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.

[0082] 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.

[0083] 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:

[0084] 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;

[0085] 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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 and Table 4: CSI computation delay requirement 2.

[0090] Table 3:

[0091]

[0092] Table 4:

[0093]

[0094] 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 dynamically granted (DG) PUSCH carrying A-CSI is scheduled serially with a DG PUSCH not carrying A-CSI, the scheduling of the DG PUSCH without A-CSI may face significant limitations under the OoO rule.

[0095] 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.

[0096] 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 processing method of this application is proposed.

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

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

[0099] Step 301: If the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule, the terminal performs the first operation:

[0100] The first operation includes any one of the following:

[0101] The second PUSCH is rolled back to the third PUSCH, and the third PUSCH is not subject to the first rule.

[0102] Delay the transmission of the first PUSCH or the second PUSCH;

[0103] Discard the transmission of the first PUSCH or the second PUSCH;

[0104] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

[0105] In this embodiment of the application, the first rule mentioned above can be understood as the OoO rule or a relaxed OoO rule.

[0106] Optionally, the DCI used to schedule the first PUSCH is later than the DCI used to schedule the second PUSCH. That is, the first PUSCH can be understood as a subsequently scheduled PUSCH, and the second PUSCH can be understood as either a PUSCH that has already been scheduled or a PUSCH that was scheduled earlier. The first and second PUSCHs can be dynamically scheduled PUSCHs, and a first rule needs to be applied to both. Specifically, the first and second PUSCHs are PUSCHs that the terminal expects to carry UL-SCH, i.e., DG PUSCH with UL-SCH. In some embodiments, the second PUSCH can be a PUSCH that the terminal expects to carry A-CSI, i.e., DG PUSCH with A-CSI and UL-SCH.

[0107] Optionally, in some embodiments, if the first PUSCH and the second PUSCH do not satisfy the first rule, the second PUSCH is fallback to the third PUSCH. This way, transmitting the third PUSCH does not require applying the first rule, thereby avoiding the second PUSCH's restriction on subsequent PUSCH scheduling, reducing the latency of uplink data carried by subsequently scheduled PUSCHs, and improving uplink transmission throughput. In this embodiment, the aforementioned third PUSCH is a PUSCH without UL-SCH, i.e., the third PUSCH is a DG PUSCH without UL-SCH. Optionally, in some embodiments, the aforementioned third PUSCH is a PUSCH without UL-SCH but carrying A-CSI, i.e., the third PUSCH is a DG PUSCH with A-CSI and without UL-SCH.

[0108] Optionally, in some embodiments, if the first PUSCH and the second PUSCH do not satisfy the first rule, the transmission of the first PUSCH or the second PUSCH is delayed. This can ensure that the first PUSCH and the second PUSCH do not fail to satisfy the first rule, thereby ensuring the effective utilization of the DCI scheduling. Furthermore, by further clarifying the delay rule, the uplink transmission latency can be controlled, and the flexibility of uplink scheduling can be improved.

[0109] Optionally, in some cases, if the first PUSCH and the second PUSCH do not meet the first rule, the transmission of the first PUSCH or the second PUSCH can be discarded. This can ensure that the transmission of PUSCH can meet the first rule and that the remaining PUSCH can be transmitted in a timely manner to meet the transmission needs of urgent data and ensure the performance of urgent data such as latency.

[0110] In this embodiment, when the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule, the terminal performs a first operation: The first operation includes any one of the following: reverting the second PUSCH to a third PUSCH, where the third PUSCH is not subject to the first rule; delaying the transmission of the first PUSCH or the second PUSCH; or discarding the transmission of the first PUSCH or the second PUSCH. The first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI. The first rule characterizes the timing relationship requirements between any two PUSCHs on the same frequency domain object. Because this embodiment clearly defines the terminal's behavior when the first rule is not satisfied between PUSCHs, the impact of the first rule on PUSCH transmission can be avoided or mitigated. Therefore, this embodiment can improve uplink transmission performance.

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

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

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

[0114] 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.

[0115] Wherein, the first target PUSCH and the second target PUSCH correspond to the same second 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, the target time is the start time or the end time, and the target processing channel is the uplink shared channel processing channel corresponding to the second frequency domain object.

[0116] In this embodiment of the application, 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.

[0117] When the start time of the first target PUSCH is earlier than the end time of the second target PUSCH, and the end time of the first target PUSCH is earlier than or no later than the 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 at this time.

[0118] 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.

[0119] In this embodiment of the application, the definition of the relaxed OoO rule is clearly defined, which can further improve the throughput of PUSCH transmission and thus improve the performance of uplink transmission.

[0120] 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:

[0121] PUSCH is dynamically scheduled by DCI;

[0122] PUSCH carries the uplink shared channel;

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

[0124] Optionally, in some embodiments, the step of falling back the second PUSCH to the third PUSCH includes:

[0125] When the second PUSCH carries aperiodic channel state information (A-CSI) and the time-domain interval between the first DCI and the second PUSCH is greater than or equal to a first preset duration, the second PUSCH is reverted to the third PUSCH.

[0126] In this embodiment of the application, for A-CSI triggered scenarios, when the time interval between the first DCI and the second PUSCH is greater than or equal to the first preset duration, the terminal can fall back the second PUSCH to the third PUSCH. While ensuring timely feedback of A-CSI, this avoids the second PUSCH restricting the scheduling of subsequent PUSCHs and reduces the latency of uplink data carried by the subsequently scheduled PUSCHs.

[0127] Optionally, the first preset duration can be agreed upon by the protocol or configured by higher-level signaling.

[0128] Optionally, in some embodiments, the UE expects that when the subsequently scheduled DG PUSCH with UL-SCH does not satisfy the OoO rule with the already scheduled DG PUSCH with A-CSI and UL-SCH, the DG PUSCH with A-CSI and UL-SCH will satisfy the predefined timing requirements.

[0129] Optionally, in some embodiments, the time-frequency resources of the third PUSCH satisfy any of the following:

[0130] It has the same time-frequency resources as the second PUSCH;

[0131] The time-frequency resources of the second PUSCH are determined after resource reduction based on the number of resource units required by A-CSI.

[0132] In this embodiment, the resource unit can be a modulation symbol. In some embodiments, the terminal can calculate the number of modulation symbols Q' required for the CSI part 1 of the A-CSI on each transport layer of the PUSCH carrying this A-CSI. CSI-1 When A-CSI includes CSI part 2, the number of modulation symbols Q' required for CSI part 2 on each transport layer of the PUSCH carrying this A-CSI is further calculated. CSI-2 Among them, Q' CSI-1 and Q' CSI-2 The calculation of Q' can be referred to relevant technologies, and will not be elaborated here. In some embodiments, Q' CSI-1 and Q' CSI-2 The calculation needs to consider the target code rate R and modulation order Q of the PUSCH carrying this A-CSI. m Attributes such as...

[0133] Optionally, in some embodiments, the fact that the time-frequency resources of the third PUSCH are the same as those of the second PUSCH can be understood as the time-frequency resources of the PUSCH remaining unchanged. In this case, because the time-frequency resources of the PUSCH are only used to map the coded bit sequence corresponding to A-CSI (when UCI multiplexing occurs, it may further carry the coded bit sequence corresponding to other UCIs based on predefined rules), the effective code rate of A-CSI reporting can be significantly reduced, thereby improving the reliability of A-CSI reporting.

[0134] Optionally, in some embodiments, the time-frequency resources of the third PUSCH can be adaptively reduced based on the number of modulation symbols expected to be required by A-CSI.

[0135] Optionally, in some embodiments, the resource reduction includes at least one of the following:

[0136] Reduce the occupied time domain units;

[0137] The number of frequency domain units occupied is reduced.

[0138] In this embodiment of the application, the above-mentioned resource reduction can be understood to include any of the following reduction methods:

[0139] Scaling is performed only in the time domain, while frequency domain resources remain unchanged;

[0140] The reduction is performed only in the frequency domain, while the time domain resources remain unchanged;

[0141] First, reduce resources in the frequency domain. If the number of resource elements (REs) contained in the remaining time-frequency resources is still greater than the number of REs required by A-CSI, continue to reduce resources in the time domain.

[0142] First, reduce resources in the time domain. If the number of REs contained in the remaining time-frequency resources is still greater than the number of REs required by A-CSI, continue to reduce resources in the frequency domain.

[0143] Optionally, the REs included in the remaining time-frequency resources mentioned above, as well as the REs required by A-CSI, can only consider REs that can carry data, i.e., data REs.

[0144] Optionally, in some embodiments, time-domain resource reduction can begin with the time-domain unit with the smallest / largest number (e.g., all Symbols, or Symbols containing only data REs, or Symbols containing at least one data RE). For example, assuming the current time-domain unit is removed, the number of REs corresponding to the remaining time-domain resources is calculated: if the number of REs corresponding to the remaining time-domain resources is greater than or not less than the number of REs required by A-CSI, the current time-domain unit is actually removed; if the number of data REs corresponding to the remaining time-domain resources is less than or not greater than the number of REs required by A-CSI, the current time-domain unit is actually retained, and execution stops. These operations can be called time-domain reduction operations. After actually removing the current time-domain unit, if the remaining time-domain resources still contain multiple time-domain units, the above-mentioned time-domain reduction operation continues; otherwise, execution stops, and only a single time-domain unit remains.

[0145] Optionally, in some embodiments, for time-domain resource reduction, the number of REs contained in each time-domain unit can be calculated (assuming that the number of REs contained in each time-domain unit is consistent, or considering the average number of REs contained in each time-domain unit), and the number of time-domain units to be occupied is determined as M = ceiling(number of REs required for A-CSI / number of REs contained in each time-domain unit), where ceiling() is a rounding up operation; starting from the time-domain unit with the smallest / largest number, M time-domain units are reserved for carrying A-CSI, and other time-domain units (if they exist) are removed.

[0146] Optionally, in some embodiments, frequency domain resource reduction can begin with the smallest / largest numbered frequency domain unit (e.g., VRB (Virtual Resource Block) or PRB (Physical Resource Block)). For example, assuming the current frequency domain unit is removed, the number of REs corresponding to the remaining frequency domain resources is calculated: if the number of REs corresponding to the remaining frequency domain resources is greater than or not less than the number of REs required by A-CSI, the current frequency domain unit is actually removed; if the number of data REs corresponding to the remaining frequency domain resources is less than or not greater than the number of REs required by A-CSI, the current frequency domain unit is actually retained, and execution stops. These operations can be called frequency domain reduction operations. After actually removing the current frequency domain unit, if the remaining frequency domain resources still contain multiple frequency domain units, the above frequency domain reduction operation continues; otherwise, execution stops, and only a single frequency domain unit remains.

[0147] Optionally, in some embodiments, for the reduction of frequency domain resources, the number of REs contained in each frequency domain unit can also be calculated (assuming that the number of REs contained in each frequency domain unit is consistent, or considering the average number of REs contained in each frequency domain unit), and the number of frequency domain units that need to be occupied is determined as M = ceiling(number of REs required for A-CSI / number of REs contained in each frequency domain unit), where ceiling() is a rounding up operation; starting from the frequency domain unit with the smallest / largest number, M frequency domain units are reserved to carry A-CSI, and other frequency domain units (if they exist) are removed.

[0148] Optionally, in some embodiments, the number of resource units that can support A-CSI corresponding to the remaining time domain units after reducing the occupied time domain units is the minimum value that is greater than or equal to the first number.

[0149] Alternatively, after reducing the occupied frequency domain units, the number of resource units corresponding to the remaining frequency domain units that can support A-CSI is the minimum value that is greater than or equal to the first number.

[0150] Wherein, the first quantity is the number of resource units required by the A-CSI.

[0151] In this embodiment, the time-domain units occupied by the second PUSCH can be reduced and / or the frequency-domain units occupied can be reduced until the number of REs in the remaining time-frequency resources best matches the number of REs required by A-CSI. Here, "best match" can be understood as: if the time-frequency domain resources of the second PUSCH are further reduced, the number of REs in the remaining time-frequency resources will be less than the number of REs required by A-CSI.

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

[0153] The terminal assumes that the first transport block and the first HARQ process are not actually scheduled.

[0154] The terminal assumes that the first transport block and the first HARQ process are actually scheduled, and that the second PUSCH is not actually transmitted or the transmission of the second PUSCH is canceled.

[0155] Wherein, the first transport block is the transport block (TB) carried by the second PUSCH plan, the first HARQ process is the HARQ process that the first transport block plan occupies, and the first HARQ process is indicated by the second DCI.

[0156] In this embodiment of the application, the first transport block can be understood as the transport block that the second PUSCH was originally intended to carry.

[0157] Optionally, the terminal's assumption that the first transport block and the first HARQ process were not actually scheduled can be understood as follows: the terminal's subsequent operations are completely consistent with when the DCI only schedules DG PUSCH with A-CSI and without UL-SCH, neither assembling TB nor occupying the target HARQ process, nor expecting subsequent HARQ retransmissions.

[0158] Optionally, in some embodiments, after the terminal assumes that the first transport block and the first HARQ process are actually scheduled, and the second PUSCH is not actually transmitted or the transmission of the second PUSCH is canceled, the method further includes:

[0159] If the second PUSCH plan is used for the initial transmission, the terminal performs the first action;

[0160] If the second PUSCH plan is used for retransmission, the terminal performs the second action;

[0161] The first behavior includes at least one of the following:

[0162] Assemble the first transport block and occupy the first HARQ process;

[0163] Waiting for the PUSCH to retransmit the first transport block;

[0164] The first transport block is transmitted using a single, defined PUSCH.

[0165] The second action includes: ignoring retransmissions corresponding to the second PUSCH, or transmitting the first transport block using a determined single PUSCH.

[0166] Optionally, the PUSCH waiting for retransmission of the first transport block can be a configured PUSCH or a dynamically scheduled PUSCH.

[0167] Optionally, using a specific single PUSCH to transmit the first transport block can be understood as using a configured PUSCH determined based on predefined rules to transmit the first transport block, which may correspond to the initial transmission (when included in the first line) or retransmission (when included in the second line) of the first transport block.

[0168] Optionally, in some embodiments, delaying the transmission of the first PUSCH or the second PUSCH includes any one of the following:

[0169] The first PUSCH or the second PUSCH is delayed until a first moment for transmission, where the first moment is the earliest moment when the delayed PUSCH and the reference PUSCH satisfy the first rule.

[0170] Delay the first PUSCH or the second PUSCH by a second number of time domain units;

[0171] Wherein, the delayed PUSCH is the delayed first PUSCH or the second PUSCH, and the reference PUSCH is all other PUSCHs in the dynamically scheduled PUSCH except for the delayed PUSCH.

[0172] In this embodiment of the application, after delaying the transmission of the first PUSCH or the second PUSCH, the PUSCH to be transmitted with delay can satisfy the first rule with any other scheduled PUSCH (PUSCH that needs to occupy the UL-SCH processing channel).

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

[0174] The terminal determines the first moment based on the first requirement;

[0175] The terminal expects the delayed PUSCH to meet the first requirement;

[0176] The first requirement includes at least one of the following:

[0177] The delayed PUSCH is determined to be a valid PUSCH;

[0178] The delayed PUSCH does not overlap with the fourth PUSCH in the time domain within the corresponding frequency domain object range;

[0179] The fourth PUSCH includes any fifth PUSCH other than the delayed PUSCH, and the fifth PUSCH includes any of the following: PUSCH, configuration grant (CG) PUSCH, and dynamic scheduling (DG) PUSCH.

[0180] In this embodiment of the application, the determination of the first moment described above needs to meet the first requirement, or in other words, the delayed PUSCH needs to meet the first requirement. When the fifth PUSCH includes a PUSCH, the delayed PUSCH does not overlap with the fourth PUSCH in the time domain within the corresponding frequency domain object range, which can be understood as: the delayed PUSCH does not overlap with any PUSCH in the time domain within the corresponding frequency domain object range.

[0181] Optionally, the delayed PUSCH being judged as a valid PUSCH can be understood as follows: any symbol occupied by the delayed PUSCH does not overlap in the time domain with semi-static DL symbols (e.g., symbols configured as downlink by higher-layer parameters tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and synchronization signal block (SSB) symbols (e.g., symbols actually used for SSB transmission indicated by higher-layer parameter ssb-PositionsInBurst).

[0182] Optionally, the aforementioned second quantity can be agreed upon by the protocol, or reported by the terminal or configured by higher-level signaling.

[0183] Optionally, the terminal expects that the delayed PUSCH, after a second number of time-domain units of delay, satisfies the first requirement mentioned above.

[0184] Optionally, in some embodiments, the discarding of the transmission of the first PUSCH or the second PUSCH includes any one of the following:

[0185] The terminal ignores the sixth PUSCH.

[0186] The terminal does not transmit the sixth PUSCH;

[0187] The sixth PUSCH includes either the first PUSCH or the second PUSCH.

[0188] In this embodiment of the application, when the terminal ignores the sixth PUSCH, the terminal may assume that it has not received the scheduling DCI corresponding to the sixth PUSCH, that is, ignore all the indication information in this scheduling DCI.

[0189] Optionally, if the terminal does not transmit the sixth PUSCH, the second HARQ process in the scheduling DCI corresponding to the sixth PUSCH, which originally planned to carry the second transport block, can further perform related actions. For example, after the terminal does not transmit the sixth PUSCH, the method further includes any of the following:

[0190] The terminal assumes that the second transport block and the second HARQ process are not actually scheduled.

[0191] The terminal assumes that the second transport block and the second HARQ process are actually scheduled, and that the sixth PUSCH is not actually transmitted or that the transmission of the sixth PUSCH is canceled.

[0192] Wherein, the second transport block is the transport block carried by the sixth PUSCH plan, the second HARQ process is the HARQ process that the second transport block plan occupies, and the second HARQ process is indicated by the DCI that schedules the sixth PUSCH.

[0193] Optionally, other indication information in the scheduling DCI corresponding to the untransmitted sixth PUSCH may be ignored or invalidated, or may remain in effect. For example, such other indication information may include, but is not limited to, at least one of the following: A-CSI triggering, Aperiodic Sounding Reference Signal (A-SRS) triggering, and Transmit Power Control (TPC) command indication, etc.

[0194] Optionally, in some embodiments, after the terminal assumes that the second transport block and the second HARQ process are actually scheduled, and the sixth PUSCH is not actually transmitted or the transmission of the sixth PUSCH is canceled, the method further includes:

[0195] In the case that the sixth PUSCH plan is used for the initial transmission, the terminal performs the third action;

[0196] If the sixth PUSCH plan is used for retransmission, the terminal performs the fourth action;

[0197] The third act includes at least one of the following:

[0198] Assemble the second transport block and occupy the second HARQ process;

[0199] Waiting for the PUSCH to retransmit the second transport block;

[0200] The second transport block is transmitted using a single, defined PUSCH;

[0201] The fourth action includes: ignoring the retransmission corresponding to the sixth PUSCH, or using a determined single PUSCH to transmit the second transport block.

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

[0203] If it is desired to reuse at least one first uplink control information (UCI) on the sixth PUSCH, the terminal will reuse the second UCI on the seventh PUSCH;

[0204] Wherein, the second UCI includes some or all of the first UCI, and the seventh PUSCH includes any one of the following:

[0205] The PUSCHs in the dynamically scheduled PUSCHs, excluding the sixth PUSCH.

[0206] PUSCHs in the PUSCH set that satisfy the second requirement;

[0207] Wherein, the PUSCH set includes all PUSCHs on the frequency domain object corresponding to the sixth PUSCH or all PUSCHs of the terminal; the second requirement includes at least one of the following:

[0208] The start time of the PUSCH is after the start time of the sixth PUSCH;

[0209] The start time of the PUSCH is after the end time of the sixth PUSCH;

[0210] The end time of the PUSCH is after the end time of the sixth PUSCH;

[0211] The PUSCH is a dynamically scheduled PUSCH, or a dynamically scheduled PUSCH that is expected to carry the uplink shared channel, or a PUSCH with configuration authorization.

[0212] PUSCH does not reuse UCI or does not reuse UCI that is expected to be carried by PUCCH;

[0213] The total number of resources in PUSCH is greater than or equal to the number of resources required to reuse the second UCI;

[0214] The number of time-domain resources for PUSCH is greater than or equal to the first threshold;

[0215] The number of frequency domain resources for PUSCH is greater than or equal to the second threshold;

[0216] The total number of PUSCH resources is greater than or equal to the third threshold;

[0217] The time interval between the start time of PUSCH and the start time of PUCCH that is expected to carry the second UCI is greater than or equal to the second preset duration.

[0218] The time interval between the start time of PUSCH and the end time of PUCCH that is expected to carry the second UCI is greater than or equal to the third preset duration.

[0219] The time interval between the end time of PUSCH and the end time of PUCCH that is expected to carry the second UCI is greater than or equal to the fourth preset duration.

[0220] The time interval between the start time of the PUSCH and the start time of the sixth PUSCH is greater than or equal to the fifth preset duration;

[0221] The time interval between the start time of the PUSCH and the end time of the sixth PUSCH is greater than or equal to the sixth preset duration;

[0222] The time interval between the end time of the PUSCH and the end time of the sixth PUSCH is greater than or equal to the seventh preset duration.

[0223] Optionally, the time requirements associated with the second, third, fourth, fifth, sixth, and seventh preset durations can be understood as multiplexing time requirements. Since the seventh PUSCH is a PUSCH that meets the multiplexing time requirements, this ensures that the second UCI can be multiplexed normally, thereby improving the reliability of UCI transmission.

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

[0225] When the first frequency domain object corresponds to a single uplink shared channel processing channel, and the first PUSCH and the second PUSCH do not satisfy the first rule, the terminal performs the first operation.

[0226] In the case where the first frequency domain object corresponds to multiple uplink shared channel processing channels, the terminal allocates the eighth PUSCH to a first PUSCH subset. The first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset. Each second PUSCH subset includes all PUSCHs associated with the same processing channel subset, and any two PUSCHs included in each second PUSCH subset satisfy the first rule. The processing channel subset includes at least one uplink shared channel processing channel among the multiple uplink shared channel processing channels corresponding to the first frequency domain object.

[0227] In this embodiment of the application, for the scenario where the first frequency domain object corresponds to a single uplink shared channel processing channel, if the first PUSCH and the second PUSCH do not satisfy the first rule, the terminal performs the first operation.

[0228] Optionally, for scenarios where the first frequency domain object corresponds to multiple uplink shared channel processing channels, the terminal may allocate the eighth PUSCH to a subset of the first PUSCH.

[0229] Alternatively, the aforementioned eighth PUSCH can be understood as a newly scheduled DG PUSCH with UL-SCH.

[0230] Optionally, in some embodiments, when the first frequency domain object corresponds to multiple uplink shared channel processing channels, before the terminal allocates the eighth PUSCH to the first PUSCH subset, the method further includes:

[0231] If a predefined condition is met, the terminal performs any of the following:

[0232] Discard the eighth PUSCH;

[0233] According to the second rule, the eighth PUSCH is assigned to the third PUSCH subset, and the ninth PUSCH in the third PUSCH subset that does not satisfy the first rule with the eighth PUSCH is discarded.

[0234] The predefined conditions include: the terminal determines that the eighth PUSCH needs to be allocated to the fourth PUSCH subset, and the number of first processing channels is greater than a processing channel number threshold; the fourth PUSCH subset is a single second PUSCH subset other than the at least one second PUSCH subset; the first number of processing channels is the sum of the number of second processing channels and the number of third processing channels; the second number of processing channels is the number of uplink shared channel processing channels required by the at least one second PUSCH subset; the third number of processing channels is the number of uplink shared channel processing channels required by the fourth PUSCH subset; and the processing channel number threshold is any one of the following:

[0235] The number of uplink shared channel processing channels that the terminal can process in parallel;

[0236] The number of uplink shared channel processing channels corresponding to the first frequency domain object;

[0237] The third PUSCH subset is a single second PUSCH subset from the at least one second PUSCH subset.

[0238] In this embodiment of the application, the operation of discarding the eighth PUSCH can be performed if the predefined conditions are met, or the eighth PUSCH can be allocated to the third PUSCH subset according to the second rule, and the ninth PUSCH in the third PUSCH subset that does not satisfy the first rule with the eighth PUSCH can be discarded.

[0239] Optionally, if predefined conditions are not met, the terminal may assign the eighth PUSCH to a subset of the first PUSCH.

[0240] Optionally, in some embodiments, the second rule includes at least one of the following:

[0241] The second PUSCH subset containing at least one tenth PUSCH is not considered the third PUSCH subset.

[0242] The second subset of PUSCHs containing the fewest eleventh PUSCHs is taken as the third subset of PUSCHs;

[0243] The second subset of PUSCHs, which includes the twelfth PUSCH, is the third subset of PUSCHs;

[0244] Wherein, the tenth PUSCH is a PUSCH that satisfies the following: the PUSCH and the eighth PUSCH do not satisfy the first rule; the second time of the PUSCH and the third time of the eighth PUSCH do not satisfy the first timing requirement, the first timing requirement including that the time domain interval between the third time and the second time is greater than or equal to the eighth preset duration;

[0245] Wherein, the eleventh PUSCH is a PUSCH that does not satisfy the first rule with the eighth PUSCH;

[0246] Wherein, the twelfth PUSCH is the earliest eleventh PUSCH at the fourth time;

[0247] Wherein, the second moment is any one of the following:

[0248] The start time of PUSCH;

[0249] The end time of PUSCH;

[0250] The start time of the first time domain unit where PUSCH is located;

[0251] The end time of the first time domain unit where PUSCH is located;

[0252] The third moment is any one of the following:

[0253] The start time of the fourth DCI of the eighth PUSCH is scheduled;

[0254] The end time of the fourth DCI of the eighth PUSCH;

[0255] The start time of the second CORESET where the fourth DCI is located;

[0256] The end time of the second CORESET where the fourth DCI is located;

[0257] The start time of the first time domain unit where the second CORESET is located;

[0258] The end time of the first time-domain unit where the second CORESET is located;

[0259] The fourth moment is any one of the following:

[0260] The start time of the third DCI for scheduling PUSCH;

[0261] The end time of the third DCI of the PUSCH scheduler;

[0262] The start time of the first control resource set CORESET where the third DCI is located;

[0263] The end time of the first CORESET where the third DCI is located;

[0264] The start time of the first time domain unit where the first CORESET is located;

[0265] The end time of the first time domain unit where the first CORESET is located;

[0266] The start time of PUSCH;

[0267] The end time of PUSCH;

[0268] The start time of the first time domain unit where PUSCH is located;

[0269] The end time of the first time-domain unit where PUSCH is located.

[0270] Optionally, the aforementioned time-domain unit is a unit divided in the time domain, which can be a system time-domain unit, such as a radio frame, sub-frame, slot, sub-slot, symbol, etc., or an absolute time unit, such as a second (s), millisecond (ms), etc. The aforementioned first time-domain unit includes, but is not limited to, a slot, and the second time-domain unit includes, but is not limited to, a symbol.

[0271] It should be noted that the second and fourth moments mentioned above can be the same moment or different moments, and no further restrictions are made here.

[0272] Optionally, rule 1 can be understood as the second PUSCH subset containing at least one tenth PUSCH not being considered the third PUSCH subset; rule 2 can be understood as the second PUSCH subset containing the fewest eleventh PUSCHs being considered the third PUSCH subset; and rule 3 can be understood as the second PUSCH subset containing the twelfth PUSCH being considered the third PUSCH subset. In some embodiments, PUSCH subsets that do not meet the first timing requirement can be excluded first based on rule 1; when there are multiple remaining PUSCH subsets, the terminal can select the PUSCH subset with the fewest scheduled eleventh PUSCHs to be discarded based on rule 2; when there are multiple remaining PUSCH subsets, the terminal can further select a single PUSCH subset as the third PUSCH subset based on rule 3.

[0273] 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.

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

[0275] Step 401: If the first physical uplink shared channel (PUSCH) and the second PUSCH for the same terminal do not satisfy the first rule, the network-side device performs the second operation:

[0276] The second operation includes any one of the following:

[0277] Receive a third PUSCH that is rolled back from the second PUSCH, and the third PUSCH is not subject to the first rule;

[0278] Delay receiving the first PUSCH or the second PUSCH;

[0279] We do not expect to receive the first PUSCH or the second PUSCH;

[0280] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

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

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

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

[0284] 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.

[0285] Wherein, the first target PUSCH and the second target PUSCH correspond to the same second 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, the target time is the start time or the end time, and the target processing channel is the uplink shared channel processing channel corresponding to the second frequency domain object.

[0286] In this embodiment, the uplink shared channel processing channel is implemented by the terminal, or it is a concept that the terminal needs to consider when processing and sending PUSCH. That is, the uplink shared channel processing channel is a terminal-side concept, belonging to the capabilities that the terminal needs to consider. Network-side devices need to follow the terminal's capabilities and schedule uplink shared channel transmissions that conform to the terminal's capabilities (or within its capabilities).

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

[0288] PUSCH is dynamically scheduled by DCI;

[0289] PUSCH carries the uplink shared channel;

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

[0291] Optionally, receiving the third PUSCH that is backed up by the second PUSCH includes:

[0292] When the second PUSCH carries aperiodic channel state information (A-CSI) and the time interval between the first DCI and the second PUSCH is greater than or equal to a first preset duration, the network-side device receives the third PUSCH that is backed up from the second PUSCH.

[0293] Optionally, the time-frequency resources of the third PUSCH satisfy any of the following:

[0294] It has the same time-frequency resources as the second PUSCH;

[0295] The time-frequency resources of the second PUSCH are determined after resource reduction based on the number of resource units required by A-CSI.

[0296] Optionally, the resource reduction includes at least one of the following:

[0297] Reduce the occupied time domain units;

[0298] The number of frequency domain units occupied is reduced.

[0299] Optionally, the number of resource units that can support A-CSI corresponding to the remaining time domain units after reducing the occupied time domain units is the minimum value that is greater than or equal to the first number;

[0300] Alternatively, after reducing the occupied frequency domain units, the number of resource units corresponding to the remaining frequency domain units that can support A-CSI is the minimum value that is greater than or equal to the first number.

[0301] Wherein, the first quantity is the number of resource units required by the A-CSI.

[0302] Optionally, the delayed reception of the first PUSCH or the second PUSCH includes any one of the following:

[0303] The first PUSCH or the second PUSCH is received at a first moment, where the first moment is the earliest moment when the delayed PUSCH and the reference PUSCH satisfy the first rule.

[0304] The first PUSCH or the second PUSCH is received with a second number of time-domain units delayed;

[0305] Wherein, the delayed PUSCH is the delayed first PUSCH or the second PUSCH, and the reference PUSCH is all other PUSCHs in the dynamically scheduled PUSCH except for the delayed PUSCH.

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

[0307] The network-side device determines the first moment based on the first requirement;

[0308] The network-side device expects the PUSCH delay to meet the first requirement;

[0309] The first requirement includes at least one of the following:

[0310] The delayed PUSCH is determined to be a valid PUSCH;

[0311] The delayed PUSCH does not overlap with the fourth PUSCH in the time domain within the corresponding frequency domain object range;

[0312] The fourth PUSCH includes any fifth PUSCH other than the delayed PUSCH, and the fifth PUSCH includes any of the following: PUSCH, configuration-authorized PUSCH, and dynamically scheduled PUSCH.

[0313] Optionally, the method further includes:

[0314] When the first frequency domain object corresponds to a single uplink shared channel processing channel, and the first PUSCH and the second PUSCH do not satisfy the first rule, the network-side device performs the second operation.

[0315] In the case where the first frequency domain object corresponds to multiple uplink shared channel processing channels, the network-side device allocates the eighth PUSCH to a first PUSCH subset. The first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset. Each second PUSCH subset includes all PUSCHs associated with the same processing channel subset, and any two PUSCHs included in each second PUSCH subset satisfy the first rule. The processing channel subset includes at least one uplink shared channel processing channel among the multiple uplink shared channel processing channels corresponding to the first frequency domain object.

[0316] In this embodiment, the single uplink shared channel processing channel or the multiple uplink shared channel processing channels are implemented by the terminal. Optionally, the above-mentioned multiple uplink shared channel processing channels corresponding to the first frequency domain object refers to the expected corresponding situation on the terminal side reported by the network-side device based on the terminal capability.

[0317] Optionally, when the first frequency domain object corresponds to multiple uplink shared channel processing channels, before the network-side device allocates the eighth PUSCH to the first PUSCH subset, the method further includes:

[0318] If predefined conditions are met, the network-side device performs any of the following:

[0319] We do not expect to receive the eighth PUSCH;

[0320] According to the second rule, the eighth PUSCH is assigned to the third PUSCH subset, and it is not expected to receive the ninth PUSCH in the third PUSCH subset that does not satisfy the first rule with the eighth PUSCH.

[0321] The predefined conditions include: the network-side device determines that the eighth PUSCH needs to be allocated to the fourth PUSCH subset, and the number of first processing channels is greater than a processing channel number threshold; the fourth PUSCH subset is a single second PUSCH subset other than the at least one second PUSCH subset; the first processing channel number is the sum of the number of second processing channels and the number of third processing channels; the second processing channel number is the number of uplink shared channel processing channels required by the at least one second PUSCH subset; the third processing channel number is the number of uplink shared channel processing channels required by the fourth PUSCH subset; and the processing channel number threshold is any one of the following:

[0322] The number of uplink shared channel processing channels that the terminal can process in parallel;

[0323] The number of uplink shared channel processing channels corresponding to the first frequency domain object;

[0324] The third PUSCH subset is a single second PUSCH subset from the at least one second PUSCH subset.

[0325] Optionally, the second rule includes at least one of the following:

[0326] The second PUSCH subset containing at least one tenth PUSCH is not considered the third PUSCH subset.

[0327] The second subset of PUSCHs containing the fewest eleventh PUSCHs is taken as the third subset of PUSCHs;

[0328] The second subset of PUSCHs, which includes the twelfth PUSCH, is the third subset of PUSCHs;

[0329] Wherein, the tenth PUSCH is a PUSCH that satisfies the following: the PUSCH and the eighth PUSCH do not satisfy the first rule; the second time of the PUSCH and the third time of the eighth PUSCH do not satisfy the first timing requirement, the first timing requirement including that the time domain interval between the third time and the second time is greater than or equal to the eighth preset duration;

[0330] Wherein, the eleventh PUSCH is a PUSCH that does not satisfy the first rule with the eighth PUSCH;

[0331] Wherein, the twelfth PUSCH is the earliest eleventh PUSCH at the fourth time;

[0332] Wherein, the second moment is any one of the following:

[0333] The start time of PUSCH;

[0334] The end time of PUSCH;

[0335] The start time of the first time domain unit where PUSCH is located;

[0336] The end time of the first time domain unit where PUSCH is located;

[0337] The third moment is any one of the following:

[0338] The start time of the fourth DCI of the eighth PUSCH is scheduled;

[0339] The end time of the fourth DCI of the eighth PUSCH;

[0340] The start time of the second CORESET where the fourth DCI is located;

[0341] The end time of the second CORESET where the fourth DCI is located;

[0342] The start time of the first time domain unit where the second CORESET is located;

[0343] The end time of the first time-domain unit where the second CORESET is located;

[0344] The fourth moment is any one of the following:

[0345] The start time of the third DCI for scheduling PUSCH;

[0346] The end time of the third DCI of the PUSCH scheduler;

[0347] The start time of the first control resource set CORESET where the third DCI is located;

[0348] The end time of the first CORESET where the third DCI is located;

[0349] The start time of the first time domain unit where the first CORESET is located;

[0350] The end time of the first time domain unit where the first CORESET is located;

[0351] The start time of PUSCH;

[0352] The end time of PUSCH;

[0353] The start time of the first time domain unit where PUSCH is located;

[0354] The end time of the first time-domain unit where PUSCH is located.

[0355] In this embodiment, the first 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, symbol, etc., or an absolute time unit, such as a second (s) or millisecond (ms). For example, the first time-domain unit includes, but is not limited to, a slot.

[0356] 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.

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

[0358] The UE's UL-SCH processing channel can be understood as being used for baseband processing (focusing on digital signal processing) such as TB assembly, encoding, modulation, and resource mapping, as well as radio frequency processing (focusing on radio frequency signal processing) such as air interface transmission.

[0359] Solution 1: A solution for when the terminal has only a single UL-SCH processing channel for a single frequency domain object.

[0360] Optionally, a frequency domain object may correspond to one or more continuous or discrete resources in the frequency domain.

[0361] Optionally, when the following text mentions whether two DG PUSCH with UL-SCH satisfy or do not satisfy the OoO rule or the relaxed OoO rule, these two DG PUSCH with UL-SCH necessarily correspond to the same frequency domain object (i.e., the OoO rule or the relaxed OoO rule is only considered / applied between DG PUSCH with UL-SCH corresponding to the same frequency domain object). The relaxed OoO rule here can be understood as follows: before a target DG PUSCH with UL-SCH with an earlier scheduling DCI occupies the UL-SCH processing channel (assuming that the start time and end time of the target DG PUSCH with UL-SCH occupying the UL-SCH processing channel are the target start time and the target end time, respectively), it is allowed not to follow 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 than or no later than the target start time.

[0362] Under scheme 1, the following processing methods 1 to 3 are included:

[0363] Method 1: For A-CSI triggered scenarios, when the OoO rule is not satisfied between the subsequently scheduled DG PUSCH with UL-SCH and the already scheduled DG PUSCH with A-CSI and UL-SCH, the DG PUSCH with A-CSI and UL-SCH (i.e., the second PUSCH) falls back to the DG PUSCH with A-CSI and without UL-SCH (i.e., the third PUSCH).

[0364] Optionally, for processing method 1, the UE performs the aforementioned rollback only if the DG PUSCH with A-CSI and UL-SCH meets the predefined timing requirements. These predefined timing requirements include: the time deviation between the start / end time of the scheduling DCI corresponding to the subsequently scheduled DG PUSCH with UL-SCH (or the start / end time of the CORESET that issues the scheduling DCI, or the start / end time of the time slot where this CORESET is located) and the start / end time of the DG PUSCH with A-CSI and UL-SCH to be rolled back (or the start / end time of the time slot where this DG PUSCH is located) is longer than or not shorter than the predefined time offset. This predefined time offset can be specified by the protocol or configured by higher-layer signaling.

[0365] Optionally, the UE expects that when the subsequently scheduled DG PUSCH with UL-SCH does not satisfy the OoO rule with the already scheduled DG PUSCH with A-CSI and UL-SCH, the DG PUSCH with A-CSI and UL-SCH should meet the predefined timing requirements.

[0366] Processing Method 2: When the subsequent scheduled DG PUSCH with UL-SCH (i.e., the first PUSCH) does not satisfy the OoO rule or the relaxed OoO rule between the already scheduled DGPUSCH with UL-SCH (i.e., the second PUSCH), the UE delays the transmission of the subsequent scheduled DG PUSCH with UL-SCH or the already scheduled DG PUSCH with UL-SCH.

[0367] Method 3: The UE discards the unprocessable DG PUSCH with UL-SCH (i.e., the first PUSCH or the second PUSCH).

[0368] Optionally, processing method 3 includes the following discarding method 1 and discarding method 2.

[0369] Discarding Method 1: The UE discards the DG PUSCH with UL-SCH based on predefined rules until the OoO rule is met or the OoO rule is relaxed.

[0370] Discarding Method 2: UE autonomously discards DG PUSCH with UL-SCH that it cannot process on its own.

[0371] Optionally, for discarding method 2, the UE discards the DG PUSCH with UL-SCH based on its own implementation. For the discarded DG PUSCH with UL-SCH, the UE can ignore this DG PUSCH with UL-SCH (see discarding method 1-1 below for specific operation) or not transmit this DG PUSCH with UL-SCH (see discarding method 1-2 below for specific operation).

[0372] Optionally, the UE can notify the network side of the discarded DG PUSCH with UL-SCH using UCI or MAC CE.

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

[0374] The UE can use the operation in Embodiment 3 to determine 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 allocate the DG PUSCH with UL-SCH that has been scheduled and still involves UL-SCH processing channels to the corresponding UL-SCH processing channels. When a newly scheduled DGPUSCH with UL-SCH needs to allocate a new subset of DG PUSCH with UL-SCH based on the OoO rule or a relaxed OoO rule, but the number of parallel UL-SCH processing channels required after allocating this new subset exceeds the number of UL-SCH processing channels that the UE has capable of parallel processing or the upper limit of such number, the UE can perform one of the following:

[0375] The UE discards the newly scheduled DG PUSCH with UL-SCH (i.e., the eighth PUSCH). Optionally, the discarding operation can follow the corresponding description in processing method 3.

[0376] The UE places the newly scheduled DG PUSCH with UL-SCH into the target subset and discards any scheduled DG PUSCH with UL-SCH in the target subset that does not satisfy the OoO rule or the relaxed OoO rule with the newly scheduled DG PUSCH with UL-SCH. Optionally, the discard operation for each scheduled DG PUSCH with UL-SCH can follow the corresponding description in processing method 3.

[0377] Optionally, the above scheme can be used for a single TRP scenario. For multiple TRP scenarios, based on UE capability reporting, one of the following can be adopted:

[0378] The above scheme is applied to the DG PUSCH with UL-SCH scheduling for each TRP. Generally, the mDCI-based mTRP scenario is mainly considered, in which the DG PUSCH with UL-SCH scheduling for each TRP is relatively independent, and the UE can clearly distinguish the DG PUSCH with UL-SCH scheduling for each TRP.

[0379] The above scheme is applied uniformly to all TRPs. That is, when the UE applies the above scheme, it does not distinguish the correspondence between DG PUSCH with UL-SCH scheduling and TRP.

[0380] Optionally, the above scheme can be used in scenarios of single PUSCH scheduling without repetition. For single PUSCH scheduling with repetition or single PUSCH scheduling with TBoMS using Transport Block over Multiple Slots (TBoMS), the above scheme can be applied separately for 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).

[0381] Optionally, the above scheme can be used in multi-PUSCH scheduling scenarios. For multi-PUSCH scheduling, the above scheme 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).

[0382] Optionally, the above scheme can be applied to multi-cell scheduling scenarios. 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.

[0383] Example 1: Dynamically scheduled PUSCH.

[0384] 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.

[0385] 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.

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

[0387] 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.

[0388] 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.

[0389] 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.

[0390] 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.

[0391] 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.

[0392] 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.

[0393] 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.

[0394] Example 3: Under Scheme 2, the terminal 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.

[0395] 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.

[0396] 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.

[0397] 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.

[0398] 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.

[0399] 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.

[0400] Operation 1 includes the following steps:

[0401] 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).

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

[0403] 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).

[0404] 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:

[0405] 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.

[0406] 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.

[0407] 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.

[0408] 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).

[0409] 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.

[0410] 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.

[0411] 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:

[0412] 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.

[0413] 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.

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

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

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

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

[0418] 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).

[0419] 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).

[0420] 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.

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

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

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

[0424] Herein, M may be determined based on at least 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.

[0425] For example, in some embodiments, in the case that M is determined based on the number of DG PUSCH with UL-SCH included in the corresponding subset, 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>1 predefined thresholds that are different from each other and arranged in ascending order may be defined, 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 higher layer signaling.

[0426] For the attribute of each DG PUSCH with UL-SCH in the subset, the attribute 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, TB size, and PHY priority. The number of UL-SCH processing channels that need to be occupied by each DG PUSCH with UL-SCH 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 need to be occupied by each DG PUSCH with UL-SCH in the subset is taken as M.

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

[0428] 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).

[0429] 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.

[0430] 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.

[0431] 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.

[0432] Operation 2 includes the following steps:

[0433] 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).

[0434] 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.

[0435] 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).

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

[0437] 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.

[0438] Example 4: The DG PUSCH with A-CSI and UL-SCH under Scheme 1 is reverted to DG PUSCH with A-CSI and without UL-SCH.

[0439] For Scheme 1 and the A-CSI triggered scenario, when the subsequently scheduled DG PUSCH with UL-SCH does not satisfy the OoO rule with the already scheduled DG PUSCH with A-CSI and UL-SCH, DG PUSCH with A-CSI and UL-SCH will fall back to DG PUSCH with A-CSI and without UL-SCH to avoid applying the OoO rule.

[0440] Specifically, the UE performs at least one of the following operations:

[0441] Determine the time and frequency resources of PUSCH, for example, the time and frequency resources of the rollback DG PUSCH with A-CSI and without UL-SCH satisfy either PUSCH resource mode 1 or PUSCH resource mode 2.

[0442] Process the TB originally planned to be carried.

[0443] In PUSCH resource mode 1, the time and frequency resources of PUSCH remain unchanged. In this case, because the time and frequency resources of PUSCH are only used to map the coded bit sequence corresponding to A-CSI (when UCI multiplexing occurs, it may further carry the coded bit sequence corresponding to other UCI based on predefined rules), the effective code rate of A-CSI reporting can be significantly reduced, thereby improving the reliability of A-CSI reporting.

[0444] PUSCH Resource Method 2: The time-frequency resources of PUSCH are adaptively reduced based on the expected number of modulation symbols required by A-CSI. This is done after calculating the number of modulation symbols Q' required for each layer of CSI part 1 in A-CSI. CSI-1 (And when A-CSI includes CSI part 2, the number of modulation symbols Q' required per layer of CSI part 2) CSI-2 After that, one of the following methods can be used to reduce the time-frequency resources corresponding to PUSCH until the number of data REs contained in the remaining time-frequency resources best matches the target number of data REs (Q' when A-CSI only includes CSI part 1). CSI-1 When A-CSI includes both CSI part 1 and CSI part 2, it is Q'. CSI-1 +Q' CSI-2 ).

[0445] For PUSCH resource mode 2, any of the following operations may be included:

[0446] Resources are reduced only in the frequency domain, while the time domain resources remain unchanged. Optionally, in some implementations, starting from the frequency domain unit with the smallest / largest number (e.g., VRB / PRB), the following reduction operation is performed: assuming the current frequency domain unit is removed, the number of data REs corresponding to the remaining frequency domain resources is calculated; if the number of data REs corresponding to the remaining frequency domain resources is greater than or not less than the target number of data REs, the current frequency domain unit is actually removed. If the remaining frequency domain resources still contain multiple frequency domain units, the reduction operation continues; otherwise, execution stops (at which point only a single frequency domain unit remains). Optionally, if the number of data REs corresponding to the remaining frequency domain resources is less than or not greater than the target number of data REs, the current frequency domain unit is actually retained, and execution stops. Optionally, in some implementations, the number of data REs contained in each frequency domain cell is calculated (assuming that the number of data REs contained in each frequency domain cell is consistent, or considering the average number of data REs contained in each frequency domain cell), and the number of frequency domain cells to be occupied is determined as N = ceiling(target number of data REs / number of data REs contained in each frequency domain cell), where ceiling() is a round-up operation; starting from the frequency domain cell with the smallest / largest number, N frequency domain cells are reserved for carrying A-CSI, and other frequency domain cells are removed (if they exist).

[0447] Resources are reduced only in the time domain, while the frequency domain resources remain unchanged. Optionally, in some implementations, starting from the time domain unit with the smallest / largest number (e.g., all Symbols, or Symbols containing only data REs, or Symbols containing at least one data RE), the following reduction operation is performed: the reduction operation includes assuming the current time domain unit is removed, calculating the number of data REs corresponding to the remaining time domain resources; if the number of data REs corresponding to the remaining time domain resources is greater than or not less than the target number of data REs, the current time domain unit is actually removed. If the remaining time domain resources still contain multiple time domain units, the reduction operation continues; otherwise, execution stops (at which point only a single time domain unit remains); if the number of data REs corresponding to the remaining time domain resources is less than or not greater than the target number of data REs, the current time domain unit is actually retained, and execution stops. Optionally, in some implementations, the number of data REs contained in each time domain unit is calculated (assuming that the number of data REs contained in each time domain unit is consistent, or considering the average number of data REs contained in each time domain unit), and the number of time domain units to be occupied is determined as M = ceiling(target number of data REs / number of data REs contained in each time domain unit); starting from the time domain unit with the smallest / largest number, M time domain units are reserved for carrying A-CSI, and other time domain units are removed (if they exist).

[0448] First, reduce resources in the frequency domain. If the number of data REs contained in the remaining time-frequency resources is still greater than the target number of data REs, continue to reduce resources in the time domain.

[0449] First, reduce resources in the time domain. If the number of data REs contained in the remaining time-frequency resources is still greater than the target number of data REs, continue to reduce resources in the frequency domain.

[0450] Optionally, for the TB originally scheduled to be carried, before the rollback, the TB originally scheduled to be carried by DG PUSCH with A-CSI and UL-SCH (assuming it is the first TB) occupies the second HARQ process indicated in the scheduling DCI. After DG PUSCH with A-CSI and UL-SCH rolls back to DG PUSCH with A-CSI and without UL-SCH, for the TB originally scheduled to be carried, the UE performs one of the following:

[0451] TB processing method 1: The UE assumes that the first TB and the second HARQ process are not actually scheduled. This can be understood as the UE's subsequent operations being completely consistent with the scheduling of DCI, which only schedules DG PUSCH with A-CSI and without UL-SCH. It will neither assemble TB nor occupy the first HARQ process, nor expect subsequent HARQ retransmissions.

[0452] TB Handling Method 2: The UE assumes that the first TB and the first HARQ process are actually scheduled, but the corresponding DG PUSCH is not actually transmitted (or the transmission is canceled). Optionally, when the scheduling DCI indicates initial transmission, the UE will still determine the TB size and assemble the corresponding TB based on the indication information in the scheduling DCI, occupy the first HARQ process, and wait for subsequent retransmission scheduling, or use a configuration PUSCH determined based on predefined rules for transmission. Optionally, when the scheduling DCI indicates retransmission, the UE can ignore this retransmission, or use a configuration PUSCH determined based on predefined rules for transmission.

[0453] Example 5: UE delayed transmission of DG PUSCH with UL-SCH under Scheme 1.

[0454] For Scheme 1, when the subsequently scheduled DG PUSCH with UL-SCH does not satisfy the OoO rule or the relaxed OoO rule with the already scheduled DG PUSCH with UL-SCH, the UE delays the transmission of the subsequently scheduled DG PUSCH with UL-SCH or the already scheduled DG PUSCH with UL-SCH.

[0455] Generally, the UE can delay subsequent scheduled DG PUSCH with UL-SCH or already scheduled DG PUSCH with UL-SCH (which can be called delayed transmission DG PUSCH with UL-SCH; typically, it delays already scheduled DG PUSCH with UL-SCH, and both sides have a consistent understanding of the delayed target transmission time; for subsequent scheduled DG PUSCH with UL-SCH, the network side can make reasonable decisions during scheduling, such as issuing the DCI later, or using a larger k2 to schedule DG PUSCH with UL-SCH, without introducing further delayed transmission operations), until the delayed transmission DG PUSCH with UL-SCH satisfies the OoO rule or a relaxed OoO rule with any other already scheduled DG PUSCH with UL-SCH that still involves UL-SCH processing channels. Here, k2 represents the offset between the slot where the DCI is located and the slot where the PUSCH is located.

[0456] Optionally, the UE performs one of the following for delayed transmission of DG PUSCH with UL-SCH:

[0457] The UE delays the delayed transmission of DG PUSCH with UL-SCH to the earliest time (i.e., the first time) between the reference DG PUSCH with UL-SCH and the DG PUSCH with UL-SCH that satisfies the OoO rule or the relaxed OoO rule; wherein, the reference DG PUSCH with UL-SCH can be any DG PUSCH with UL-SCH other than the delayed transmission of DG PUSCH with UL-SCH among the subsequently scheduled DG PUSCH with UL-SCH and the already scheduled DG PUSCH with UL-SCH.

[0458] The UE will delay the start / end time of the DG PUSCH with UL-SCH transmission by X time domain units; X can be specified by the protocol, reported by the UE, or configured by higher-layer signaling.

[0459] Optionally, the UE expects that the delayed transmission of DG PUSCH with UL-SCH satisfies the first requirement after a delay of X time domain units.

[0460] Optionally, the determination of the first moment described above can satisfy the first requirement, wherein the first requirement includes at least one of the following:

[0461] The delayed PUSCH is determined to be a valid PUSCH, for example, if any Symbol it occupies does not overlap with the time domain of the Semi-static DL symbol and the SSB symbol. Here, the SSB symbol can be configured or indicated by the higher-level parameter ssb-PositionsInBurst.

[0462] The delayed PUSCH does not overlap with the fourth PUSCH in the time domain within the corresponding frequency domain object range;

[0463] The fourth PUSCH includes any fifth PUSCH other than the delayed PUSCH, and the fifth PUSCH includes any of the following: PUSCH, configuration-authorized PUSCH, and dynamically scheduled PUSCH.

[0464] Example 6: Under Scheme 1, the UE discards the DG PUSCH with UL-SCH based on predefined rules.

[0465] Discarding Method 1: The UE discards the DG PUSCH with UL-SCH based on predefined rules until the OoO rule is met or the OoO rule is relaxed.

[0466] Optionally, discarding method 1 includes any one of the following discarding methods 1-1 and 1-2:

[0467] Discarding Method 1-1: When a subsequently scheduled DG PUSCH with UL-SCH does not satisfy the OoO rule or a relaxed OoO rule with an already scheduled DG PUSCH with UL-SCH, the UE ignores the subsequently scheduled DG PUSCH with UL-SCH or the already scheduled DG PUSCH with UL-SCH. Optionally, for ignored DG PUSCHs, the UE assumes that it has not received the corresponding scheduling DCI at all, that is, ignores all indication information in this scheduling DCI.

[0468] Discarding Method 1-2: When the subsequently scheduled DG PUSCH with UL-SCH does not satisfy the OoO rule or the relaxed OoO rule with the already scheduled DG PUSCH with UL-SCH, the UE will not transmit the subsequently scheduled DG PUSCH with UL-SCH or the already scheduled DG PUSCH with UL-SCH.

[0469] Optionally, for a DG PUSCH that is not transmitted, for the TB it was originally scheduled to carry (assuming it is the second TB, and is indicated in the scheduling DCI to occupy the second HARQ process), the terminal performs either TB processing method 3 or TB processing method 4 as follows:

[0470] TB processing method 3: The UE assumes that the second TB and the second HARQ process have not actually been scheduled. This can be understood as the UE's subsequent operations being completely consistent with the scheduling of DCI corresponding to the non-transmitted DG PUSCH, neither assembling the TB nor occupying the second HARQ process, nor expecting subsequent HARQ retransmissions.

[0471] TB processing method 4: The UE assumes that the second TB and the second HARQ process are actually scheduled, but the corresponding DG PUSCH is not actually transmitted (or the transmission is canceled).

[0472] Optionally, when the scheduling DCI indication corresponding to the non-transmitted DG PUSCH is transmitted for the first time, the UE will still determine the TB size and assemble the corresponding TB based on the indication information in the scheduling DCI, occupy the second HARQ process, and wait for subsequent retransmission scheduling, or use a configuration PUSCH determined based on predefined rules for transmission.

[0473] Optionally, when the scheduling DCI corresponding to the non-transmitted DG PUSCH indicates a retransmission, the UE may ignore the retransmission, or use a configuration PUSCH determined based on predefined rules for transmission.

[0474] Optionally, other indication information in the scheduling DCI corresponding to the DG PUSCH that is not transmitted is ignored (or invalidated), or it remains in effect, including A-CSI triggering, A-SRS triggering, TPC command indication, etc.

[0475] Optionally, for DG PUSCHs that are ignored or not transmitted, when UCIs originally carried by PUCCHs are multiplexed on them based on Intra-UE UCI multiplexing rules, the UE may perform any of the following actions: the UE multiplexes all or part of the UCIs (which may be referred to as the second UCIs) into the seventh PUSCH; the UE directly discards all UCIs, that is, it no longer considers reporting any of the UCIs to the network-side equipment; the UE transmits the PUCCHs that were planned to be transmitted before the UCI multiplexing, and each PUCCH still carries the corresponding UCIs that were planned to be carried before the UCI multiplexing.

[0476] Alternatively, the seventh PUSCH can be one of the following:

[0477] In subsequent scheduled DG PUSCH with UL-SCH and already scheduled DG PUSCH with UL-SCH, except for DG PUSCH that is ignored or not transmitted;

[0478] PUSCHs in the PUSCH set that satisfy the second requirement;

[0479] Wherein, the PUSCH set includes all PUSCHs on the frequency domain object corresponding to the sixth PUSCH or all PUSCHs of the terminal; the second requirement includes at least one of the following:

[0480] The start / end time is located after the start / end time of the DG PUSCH that is ignored or not transmitted;

[0481] It is DG PUSCH, DG PUSCH with UL-SCH or CG PUSCH;

[0482] UCI that is not reused or that was originally carried by PUCCH;

[0483] The total amount of resources is greater than or not less than the amount of resources required to reuse the target UCI;

[0484] Frequency domain resources / time domain resources / total resources meet predefined thresholds;

[0485] The time interval between the start / end time and the start / end time of the PUCCH originally planned to carry the target UCI meets the multiplexing time requirement;

[0486] The time interval between the start / end time and the start / end time of the DG PUSCH that is ignored or not transmitted meets the multiplexing time requirement.

[0487] Example 7: Under Scheme 2, the UE will place the newly scheduled DG PUSCH with UL-SCH (i.e., the eighth PUSCH) into the target subset.

[0488] For scheme 2, placing the newly scheduled DG PUSCH with UL-SCH into the target subset (i.e., the third PUSCH subset) means that every scheduled DG PUSCH with UL-SCH in this target subset that does not satisfy the OoO rule or the relaxed OoO rule with the newly scheduled DG PUSCH with UL-SCH will be discarded thereafter.

[0489] The terminal can select a target subset based on at least one of the following rules:

[0490] Rule 1: If, within a subset, at least one of the scheduled DGPUSCH with UL-SCH (i.e., the tenth PUSCH) that does not satisfy the OoO rule or the relaxed OoO rule with the newly scheduled DG PUSCH with UL-SCH (i.e., the eighth PUSCH) does not satisfy the first timing requirement, this subset shall not be considered as the target subset.

[0491] The first timing requirement may include: the time deviation between the start / end time of the scheduling DCI corresponding to the newly scheduled DG PUSCH with UL-SCH (or the start / end time of the CORESET that issues the scheduling DCI, or the start / end time of the time slot where this CORESET is located) and the start / end time of the already scheduled DG PUSCH with UL-SCH (or the start / end time of the time slot where this DG PUSCH is located) is longer than or not shorter than the target time offset (i.e., the eighth preset duration). The target time offset here can be specified by the protocol or configured by higher-layer signaling.

[0492] Optionally, in some embodiments, the UE can discard a scheduled DG PUSCH with UL-SCH only if the scheduled DG PUSCH with UL-SCH meets the first timing requirement.

[0493] Rule 2: The UE selects the subset with the smallest number of scheduled DG PUSCHs with UL-SCHs (i.e., the eleventh PUSCH) that do not satisfy the OoO rule or the relaxed OoO rule with the newly scheduled DG PUSCH with UL-SCH (i.e., the eighth PUSCH) as the target subset. In other words, Rule 2 can be understood as: the UE selects the subset with the smallest number of scheduled DG PUSCHs with UL-SCHs that need to be discarded as the target subset.

[0494] Rule 3: The UE will take the earliest subset of the scheduled DG PUSCH with UL-SCH (i.e., the fourth time) that does not satisfy the OoO rule or the relaxed OoO rule between the subset and the newly scheduled DG PUSCH with UL-SCH (i.e. the eighth PUSCH) as the target subset.

[0495] Optionally, the target time can be the start / end time of the scheduling DCI corresponding to the already scheduled DG PUSCH with UL-SCH that does not satisfy the OoO rule or the relaxed OoO rule with the newly scheduled DG PUSCH with UL-SCH (or the start / end time of the CORESET that issues the scheduling DCI, or the start / end time of the time slot where this CORESET is located), or the start / end time of this already scheduled DG PUSCH with UL-SCH (or the start / end time of the time slot where this DG PUSCH is located). This can be understood as the earlier a DG PUSCH with UL-SCH is scheduled, the greater the likelihood that it will be discarded (the base station can obtain more information during subsequent scheduling, the input for scheduling decisions is more comprehensive, and necessary overriding can be performed as needed).

[0496] Optionally, when there are multiple scheduled DG PUSCH with UL-SCH within the subset that do not satisfy the OoO rule or the relaxed OoO rule between the newly scheduled DG PUSCH with UL-SCH, the target time of the earliest scheduled DGPUSCH with UL-SCH can be selected as the target time of the subset.

[0497] For example, the UE can first exclude subsets that do not meet the target timing requirements based on rule 1; when there are multiple remaining subsets, the UE can select the subset with the smallest number of scheduled DG PUSCH with UL-SCH that needs to be discarded based on rule 2; when there are still multiple remaining subsets, the UE can further select a single subset as the target subset based on rule 3.

[0498] It should be noted that when the network side does not guarantee that the scheduling of DG PUSCH with UL-SCH meets the OoO rule or the relaxed OoO rule, corresponding solutions are given for different situations such as the UE having one or more UL-SCH processing channels. These solutions can avoid or mitigate the impact of the OoO rule on the scheduling of DCI and the scheduled PUSCH on DG PUSCH transmission, thereby improving the performance of uplink data transmission latency, throughput and other aspects.

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

[0500] This application provides an uplink transmission processing apparatus. As an example, the uplink transmission processing apparatus 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.

[0501] The uplink transmission processing 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.

[0502] For details, see Figure 5 When the uplink transmission processing device is a terminal or a component within a terminal, the uplink transmission processing device 500 includes:

[0503] The transmitting module 501 is configured to perform a first operation when the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule:

[0504] The first operation includes any one of the following:

[0505] The second PUSCH is rolled back to the third PUSCH, and the third PUSCH is not subject to the first rule.

[0506] Delay the transmission of the first PUSCH or the second PUSCH;

[0507] Discard the transmission of the first PUSCH or the second PUSCH;

[0508] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

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

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

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

[0512] 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.

[0513] Wherein, the first target PUSCH and the second target PUSCH correspond to the same second 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, the target time is the start time or the end time, and the target processing channel is the uplink shared channel processing channel corresponding to the second frequency domain object.

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

[0515] PUSCH is dynamically scheduled by DCI;

[0516] PUSCH carries the uplink shared channel;

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

[0518] Optionally, the sending module 501 is specifically configured to: when the second PUSCH carries aperiodic channel state information A-CSI and the time-domain interval between the first DCI and the second PUSCH is greater than or equal to a first preset duration, the second PUSCH is rolled back to the third PUSCH.

[0519] Optionally, the time-frequency resources of the third PUSCH satisfy any of the following:

[0520] It has the same time-frequency resources as the second PUSCH;

[0521] The time-frequency resources of the second PUSCH are determined after resource reduction based on the number of resource units required by A-CSI.

[0522] Optionally, the resource reduction includes at least one of the following:

[0523] Reduce the occupied time domain units;

[0524] The number of frequency domain units occupied is reduced.

[0525] Optionally, the number of resource units that can support A-CSI corresponding to the remaining time domain units after reducing the occupied time domain units is the minimum value that is greater than or equal to the first number;

[0526] Alternatively, after reducing the occupied frequency domain units, the number of resource units corresponding to the remaining frequency domain units that can support A-CSI is the minimum value that is greater than or equal to the first number.

[0527] Wherein, the first quantity is the number of resource units required by the A-CSI.

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

[0529] Assume that the first transport block and the first HARQ process were not actually scheduled;

[0530] Assume that the first transport block and the first HARQ process are actually scheduled, and the second PUSCH is not actually transmitted or the transmission of the second PUSCH is canceled;

[0531] Wherein, the first transport block is the transport block carried by the second PUSCH plan, the first HARQ process is the HARQ process that the first transport block plans to occupy, and the first HARQ process is indicated by the second DCI.

[0532] Optionally, the sending module 501 is further configured to:

[0533] If the second PUSCH plan is used for the initial transfer, perform the first action;

[0534] If the second PUSCH plan is used for retransmission, execute the second action;

[0535] The first behavior includes at least one of the following:

[0536] Assemble the first transport block and occupy the first HARQ process;

[0537] Waiting for the PUSCH to retransmit the first transport block;

[0538] The first transport block is transmitted using a single, defined PUSCH.

[0539] The second action includes: ignoring retransmissions corresponding to the second PUSCH, or transmitting the first transport block using a determined single PUSCH.

[0540] Optionally, the sending module 501 is specifically configured to perform any of the following:

[0541] The first PUSCH or the second PUSCH is delayed until a first moment for transmission, where the first moment is the earliest moment when the delayed PUSCH and the reference PUSCH satisfy the first rule.

[0542] Delay the first PUSCH or the second PUSCH by a second number of time domain units;

[0543] Wherein, the delayed PUSCH is the delayed first PUSCH or the second PUSCH, and the reference PUSCH is all other PUSCHs in the dynamically scheduled PUSCH except for the delayed PUSCH.

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

[0545] The first moment is determined based on the first requirement;

[0546] It is expected that the delayed PUSCH will satisfy the first requirement;

[0547] The first requirement includes at least one of the following:

[0548] The delayed PUSCH is determined to be a valid PUSCH;

[0549] The delayed PUSCH does not overlap with the fourth PUSCH in the time domain within the corresponding frequency domain object range;

[0550] The fourth PUSCH includes any fifth PUSCH other than the delayed PUSCH, and the fifth PUSCH includes any of the following: PUSCH, configuration-authorized PUSCH, and dynamically scheduled PUSCH.

[0551] Optionally, the sending module 501 is specifically configured to perform any of the following:

[0552] Ignore the sixth PUSCH;

[0553] Do not transmit the sixth PUSCH;

[0554] The sixth PUSCH includes either the first PUSCH or the second PUSCH.

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

[0556] Assume that the second transport block and the second HARQ process were not actually scheduled;

[0557] Assume that the second transport block and the second HARQ process are actually scheduled, and the sixth PUSCH is not actually transmitted or the transmission of the sixth PUSCH is canceled;

[0558] Wherein, the second transport block is the transport block carried by the sixth PUSCH plan, the second HARQ process is the HARQ process that the second transport block plan occupies, and the second HARQ process is indicated by the DCI that schedules the sixth PUSCH.

[0559] Optionally, the sending module 501 is further configured to:

[0560] If the sixth PUSCH plan is used for the initial transmission, the third action is performed;

[0561] If the sixth PUSCH plan is used for retransmission, the fourth action is executed;

[0562] The third act includes at least one of the following:

[0563] Assemble the second transport block and occupy the second HARQ process;

[0564] Waiting for the PUSCH to retransmit the second transport block;

[0565] The second transport block is transmitted using a single, defined PUSCH;

[0566] The fourth action includes: ignoring the retransmission corresponding to the sixth PUSCH, or using a determined single PUSCH to transmit the second transport block.

[0567] Optionally, the transmitting module 501 is further configured to: multiplex the second UCI onto the seventh PUSCH if it is desired to multiplex at least one first uplink control information UCI on the sixth PUSCH;

[0568] Wherein, the second UCI includes some or all of the first UCI, and the seventh PUSCH includes any one of the following:

[0569] The PUSCHs in the dynamically scheduled PUSCHs, excluding the sixth PUSCH.

[0570] PUSCHs in the PUSCH set that satisfy the second requirement;

[0571] Wherein, the PUSCH set includes all PUSCHs on the frequency domain object corresponding to the sixth PUSCH or all PUSCHs of the terminal; the second requirement includes at least one of the following:

[0572] The start time of the PUSCH is after the start time of the sixth PUSCH;

[0573] The start time of the PUSCH is after the end time of the sixth PUSCH;

[0574] The end time of the PUSCH is after the end time of the sixth PUSCH;

[0575] The PUSCH is a dynamically scheduled PUSCH, or a dynamically scheduled PUSCH that is expected to carry the uplink shared channel, or a PUSCH with configuration authorization.

[0576] PUSCH does not reuse UCI or does not reuse UCI that is expected to be carried by PUCCH;

[0577] The total number of resources in PUSCH is greater than or equal to the number of resources required to reuse the second UCI;

[0578] The number of time-domain resources for PUSCH is greater than or equal to the first threshold;

[0579] The number of frequency domain resources for PUSCH is greater than or equal to the second threshold;

[0580] The total number of PUSCH resources is greater than or equal to the third threshold;

[0581] The time interval between the start time of PUSCH and the start time of PUCCH that is expected to carry the second UCI is greater than or equal to the second preset duration.

[0582] The time interval between the start time of PUSCH and the end time of PUCCH that is expected to carry the second UCI is greater than or equal to the third preset duration.

[0583] The time interval between the end time of PUSCH and the end time of PUCCH that is expected to carry the second UCI is greater than or equal to the fourth preset duration.

[0584] The time interval between the start time of the PUSCH and the start time of the sixth PUSCH is greater than or equal to the fifth preset duration;

[0585] The time interval between the start time of the PUSCH and the end time of the sixth PUSCH is greater than or equal to the sixth preset duration;

[0586] The time interval between the end time of the PUSCH and the end time of the sixth PUSCH is greater than or equal to the seventh preset duration.

[0587] Optionally, the sending module 501 is further configured to: perform the first operation when the first frequency domain object corresponds to a single uplink shared channel processing channel and the first PUSCH and the second PUSCH do not satisfy the first rule;

[0588] In the case where the first frequency domain object corresponds to multiple uplink shared channel processing channels, the eighth PUSCH is assigned to a first PUSCH subset. The first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset. Each second PUSCH subset includes all PUSCHs associated with the same processing channel subset, and any two PUSCHs included in each second PUSCH subset satisfy the first rule. The processing channel subset includes at least one uplink shared channel processing channel among the multiple uplink shared channel processing channels corresponding to the first frequency domain object.

[0589] Optionally, the sending module 501 is further configured to: perform any of the following actions when a predefined condition is met:

[0590] Discard the eighth PUSCH;

[0591] According to the second rule, the eighth PUSCH is assigned to the third PUSCH subset, and the ninth PUSCH in the third PUSCH subset that does not satisfy the first rule with the eighth PUSCH is discarded.

[0592] The predefined conditions include: the terminal determines that the eighth PUSCH needs to be allocated to the fourth PUSCH subset, and the number of first processing channels is greater than a processing channel number threshold; the fourth PUSCH subset is a single second PUSCH subset other than the at least one second PUSCH subset; the first number of processing channels is the sum of the number of second processing channels and the number of third processing channels; the second number of processing channels is the number of uplink shared channel processing channels required by the at least one second PUSCH subset; the third number of processing channels is the number of uplink shared channel processing channels required by the fourth PUSCH subset; and the processing channel number threshold is any one of the following:

[0593] The number of uplink shared channel processing channels that the terminal can process in parallel;

[0594] The number of uplink shared channel processing channels corresponding to the first frequency domain object;

[0595] The third PUSCH subset is a single second PUSCH subset from the at least one second PUSCH subset.

[0596] Optionally, the second rule includes at least one of the following:

[0597] The second PUSCH subset containing at least one tenth PUSCH is not considered the third PUSCH subset.

[0598] The second subset of PUSCHs containing the fewest eleventh PUSCHs is taken as the third subset of PUSCHs;

[0599] The second subset of PUSCHs, which includes the twelfth PUSCH, is the third subset of PUSCHs;

[0600] Wherein, the tenth PUSCH is a PUSCH that satisfies the following: the PUSCH and the eighth PUSCH do not satisfy the first rule; the second time of the PUSCH and the third time of the eighth PUSCH do not satisfy the first timing requirement, the first timing requirement including that the time domain interval between the third time and the second time is greater than or equal to the eighth preset duration;

[0601] Wherein, the eleventh PUSCH is a PUSCH that does not satisfy the first rule with the eighth PUSCH;

[0602] Wherein, the twelfth PUSCH is the earliest eleventh PUSCH at the fourth time;

[0603] Wherein, the second moment is any one of the following:

[0604] The start time of PUSCH;

[0605] The end time of PUSCH;

[0606] The start time of the first time domain unit where PUSCH is located;

[0607] The end time of the first time domain unit where PUSCH is located;

[0608] The third moment is any one of the following:

[0609] The start time of the fourth DCI of the eighth PUSCH is scheduled;

[0610] The end time of the fourth DCI of the eighth PUSCH;

[0611] The start time of the second CORESET where the fourth DCI is located;

[0612] The end time of the second CORESET where the fourth DCI is located;

[0613] The start time of the first time domain unit where the second CORESET is located;

[0614] The end time of the first time-domain unit where the second CORESET is located;

[0615] The fourth moment is any one of the following:

[0616] The start time of the third DCI for scheduling PUSCH;

[0617] The end time of the third DCI of the PUSCH scheduler;

[0618] The start time of the first control resource set CORESET where the third DCI is located;

[0619] The end time of the first CORESET where the third DCI is located;

[0620] The start time of the first time domain unit where the first CORESET is located;

[0621] The end time of the first time domain unit where the first CORESET is located;

[0622] The start time of PUSCH;

[0623] The end time of PUSCH;

[0624] The start time of the first time domain unit where PUSCH is located;

[0625] The end time of the first time-domain unit where PUSCH is located.

[0626] 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.

[0627] See Figure 6 When the uplink transmission processing device is a network-side device or a component within a network-side device, the uplink transmission processing device 600 includes:

[0628] The receiving module 601 is configured to perform a second operation when the first physical uplink shared channel (PUSCH) and the second PUSCH for the same terminal do not satisfy the first rule:

[0629] The second operation includes any one of the following:

[0630] Receive a third PUSCH that is rolled back from the second PUSCH, and the third PUSCH is not subject to the first rule;

[0631] Delay receiving the first PUSCH or the second PUSCH;

[0632] We do not expect to receive the first PUSCH or the second PUSCH;

[0633] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

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

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

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

[0637] 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.

[0638] Wherein, the first target PUSCH and the second target PUSCH correspond to the same second 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, the target time is the start time or the end time, and the target processing channel is the uplink shared channel processing channel corresponding to the second frequency domain object.

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

[0640] PUSCH is dynamically scheduled by DCI;

[0641] PUSCH carries the uplink shared channel;

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

[0643] Optionally, the receiving module 601 is specifically configured to: receive a third PUSCH that is backed up from the second PUSCH when the second PUSCH carries aperiodic channel state information A-CSI and the time interval between the first DCI and the second PUSCH is greater than or equal to a first preset duration.

[0644] Optionally, the time-frequency resources of the third PUSCH satisfy any of the following:

[0645] It has the same time-frequency resources as the second PUSCH;

[0646] The time-frequency resources of the second PUSCH are determined after resource reduction based on the number of resource units required by A-CSI.

[0647] Optionally, the resource reduction includes at least one of the following:

[0648] Reduce the occupied time domain units;

[0649] The number of frequency domain units occupied is reduced.

[0650] Optionally, the number of resource units that can support A-CSI corresponding to the remaining time domain units after reducing the occupied time domain units is the minimum value that is greater than or equal to the first number;

[0651] Alternatively, after reducing the occupied frequency domain units, the number of resource units corresponding to the remaining frequency domain units that can support A-CSI is the minimum value that is greater than or equal to the first number.

[0652] Wherein, the first quantity is the number of resource units required by the A-CSI.

[0653] Optionally, the receiving module 601 is specifically configured to perform any of the following:

[0654] The first PUSCH or the second PUSCH is received at a first moment, where the first moment is the earliest moment when the delayed PUSCH and the reference PUSCH satisfy the first rule.

[0655] The first PUSCH or the second PUSCH is received with a second number of time-domain units delayed;

[0656] Wherein, the delayed PUSCH is the delayed first PUSCH or the second PUSCH, and the reference PUSCH is all other PUSCHs in the dynamically scheduled PUSCH except for the delayed PUSCH.

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

[0658] The first moment is determined based on the first requirement;

[0659] It is expected that the delayed PUSCH will satisfy the first requirement;

[0660] The first requirement includes at least one of the following:

[0661] The delayed PUSCH is determined to be a valid PUSCH;

[0662] The delayed PUSCH does not overlap with the fourth PUSCH in the time domain within the corresponding frequency domain object range;

[0663] The fourth PUSCH includes any fifth PUSCH other than the delayed PUSCH, and the fifth PUSCH includes any of the following: PUSCH, configuration-authorized PUSCH, and dynamically scheduled PUSCH.

[0664] Optionally, the receiving module is further configured to:

[0665] If the first frequency domain object corresponds to a single uplink shared channel processing channel, and the first PUSCH and the second PUSCH do not satisfy the first rule, then the second operation is performed.

[0666] In the case where the first frequency domain object corresponds to multiple uplink shared channel processing channels, the eighth PUSCH is assigned to a first PUSCH subset. The first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset. Each second PUSCH subset includes all PUSCHs associated with the same processing channel subset, and any two PUSCHs included in each second PUSCH subset satisfy the first rule. The processing channel subset includes at least one uplink shared channel processing channel among the multiple uplink shared channel processing channels corresponding to the first frequency domain object.

[0667] Optionally, the receiving module 601 is further configured to: perform any of the following actions when a predefined condition is met:

[0668] Discard the eighth PUSCH;

[0669] According to the second rule, the eighth PUSCH is assigned to the third PUSCH subset, and the ninth PUSCH in the third PUSCH subset that does not satisfy the first rule with the eighth PUSCH is discarded.

[0670] The predefined conditions include: the terminal determines that the eighth PUSCH needs to be allocated to the fourth PUSCH subset, and the number of first processing channels is greater than a processing channel number threshold; the fourth PUSCH subset is a single second PUSCH subset other than the at least one second PUSCH subset; the first processing channel number is the sum of the number of second processing channels and the number of third processing channels; the second processing channel number is the number of uplink shared channel processing channels required by the at least one second PUSCH subset; the third processing channel number is the number of uplink shared channel processing channels required by the fourth PUSCH subset; and the processing channel number threshold is any one of the following:

[0671] The number of uplink shared channel processing channels that the terminal can process in parallel;

[0672] The number of uplink shared channel processing channels corresponding to the first frequency domain object;

[0673] The third PUSCH subset is a single second PUSCH subset from the at least one second PUSCH subset.

[0674] Optionally, the second rule includes at least one of the following:

[0675] The second PUSCH subset containing at least one tenth PUSCH is not considered the third PUSCH subset.

[0676] The second subset of PUSCHs containing the fewest eleventh PUSCHs is taken as the third subset of PUSCHs;

[0677] The second subset of PUSCHs, which includes the twelfth PUSCH, is the third subset of PUSCHs;

[0678] Wherein, the tenth PUSCH is a PUSCH that satisfies the following: the PUSCH and the eighth PUSCH do not satisfy the first rule; the second time of the PUSCH and the third time of the eighth PUSCH do not satisfy the first timing requirement, the first timing requirement including that the time domain interval between the third time and the second time is greater than or equal to the eighth preset duration;

[0679] Wherein, the eleventh PUSCH is a PUSCH that does not satisfy the first rule with the eighth PUSCH;

[0680] Wherein, the twelfth PUSCH is the earliest eleventh PUSCH at the fourth time;

[0681] Wherein, the second moment is any one of the following:

[0682] The start time of PUSCH;

[0683] The end time of PUSCH;

[0684] The start time of the first time domain unit where PUSCH is located;

[0685] The end time of the first time domain unit where PUSCH is located;

[0686] The third moment is any one of the following:

[0687] The start time of the fourth DCI of the eighth PUSCH is scheduled;

[0688] The end time of the fourth DCI of the eighth PUSCH;

[0689] The start time of the second CORESET where the fourth DCI is located;

[0690] The end time of the second CORESET where the fourth DCI is located;

[0691] The start time of the first time domain unit where the second CORESET is located;

[0692] The end time of the first time-domain unit where the second CORESET is located;

[0693] The fourth moment is any one of the following:

[0694] The start time of the third DCI for scheduling PUSCH;

[0695] The end time of the third DCI of the PUSCH scheduler;

[0696] The start time of the first control resource set CORESET where the third DCI is located;

[0697] The end time of the first CORESET where the third DCI is located;

[0698] The start time of the first time domain unit where the first CORESET is located;

[0699] The end time of the first time domain unit where the first CORESET is located;

[0700] The start time of PUSCH;

[0701] The end time of PUSCH;

[0702] The start time of the first time domain unit where PUSCH is located;

[0703] The end time of the first time-domain unit where PUSCH is located.

[0704] 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.

[0705] The uplink transmission processing 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.

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

[0707] 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 5 The uplink transmission processing device shown. Specifically, Figure 8 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0708] The terminal 800 includes, but is not limited to, at least some of the following components: radio frequency unit 801, network module 802, audio output unit 803, input unit 804, sensor 805, display unit 806, user input unit 807, interface unit 808, memory 809, and processor 810.

[0709] Those skilled in the art will understand that the terminal 800 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 810 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 8 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.

[0710] It should be understood that, in this embodiment, the input unit 804 may include a graphics processor 8041 and a microphone 8042. The graphics processor 8041 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 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 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.

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

[0712] The memory 809 can be used to store software programs or instructions, as well as various data. The memory 809 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 809 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 809 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0713] Processor 810 may include one or more processing units; optionally, processor 810 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 810.

[0714] The radio frequency unit 801 is configured to perform a first operation when the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule:

[0715] The first operation includes any one of the following:

[0716] The second PUSCH is rolled back to the third PUSCH, and the third PUSCH is not subject to the first rule.

[0717] Delay the transmission of the first PUSCH or the second PUSCH;

[0718] Discard the transmission of the first PUSCH or the second PUSCH;

[0719] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

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

[0721] 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.

[0722] Specifically, embodiments of this application also provide a network-side device, which may be... Figure 6 The uplink transmission processing device shown. For example... Figure 9 As shown, the network-side device 900 includes: an antenna 901, a radio frequency (RF) device 902, a baseband device 903, a processor 904, and a memory 905. The antenna 901 is connected to the RF device 902. In the uplink direction, the RF device 902 receives information through the antenna 901 and transmits the received information to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes the information to be transmitted and sends it to the RF device 902. The RF device 902 processes the received information and transmits it through the antenna 901.

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

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

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

[0726] The radio frequency device 902 is used to perform a second operation when the first physical uplink shared channel (PUSCH) and the second PUSCH for the same terminal do not satisfy the first rule:

[0727] The second operation includes any one of the following:

[0728] Receive a third PUSCH that is rolled back from the second PUSCH, and the third PUSCH is not subject to the first rule;

[0729] Delay receiving the first PUSCH or the second PUSCH;

[0730] We do not expect to receive the first PUSCH or the second PUSCH;

[0731] Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

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

[0733] 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 processing method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0734] 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.

[0735] 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 processing method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0736] 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.

[0737] 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 processing method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0739] 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.

[0740] 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.

[0741] 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 processing method, characterized in that, include: If the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule, the terminal performs the first operation: The first operation includes any one of the following: The second PUSCH is rolled back to the third PUSCH, and the third PUSCH is not subject to the first rule. Delay the transmission of the first PUSCH or the second PUSCH; Discard the transmission of the first PUSCH or the second PUSCH; Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

2. The method according to claim 1, characterized in that, 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 second 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, the target time is the start time or the end time, and the target processing channel is the uplink shared channel processing channel corresponding to the second frequency domain object.

3. The method according to claim 2, 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.

4. The method according to any one of claims 1 to 3, characterized in that, The step of reverting the second PUSCH to the third PUSCH includes: When the second PUSCH carries aperiodic channel state information (A-CSI) and the time-domain interval between the first DCI and the second PUSCH is greater than or equal to a first preset duration, the terminal will revert the second PUSCH to the third PUSCH.

5. The method according to any one of claims 1 to 4, characterized in that, The time-frequency resources of the third PUSCH satisfy any of the following: It has the same time-frequency resources as the second PUSCH; The time-frequency resources of the second PUSCH are determined after resource reduction based on the number of resource units required by A-CSI.

6. The method according to claim 5, characterized in that, The resource reduction includes at least one of the following: Reduce the occupied time domain units; The number of frequency domain units occupied is reduced.

7. The method according to claim 6, characterized in that, After reducing the occupied time domain units, the number of resource units that can support A-CSI corresponding to the remaining time domain units is the minimum value that is greater than or equal to the first number; Alternatively, after reducing the occupied frequency domain units, the number of resource units corresponding to the remaining frequency domain units that can support A-CSI is the minimum value that is greater than or equal to the first number. Wherein, the first quantity is the number of resource units required by the A-CSI.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes any one of the following: The terminal assumes that the first transport block and the first HARQ process are not actually scheduled. The terminal assumes that the first transport block and the first HARQ process are actually scheduled, and that the second PUSCH is not actually transmitted or the transmission of the second PUSCH is canceled. Wherein, the first transport block is the transport block carried by the second PUSCH plan, the first HARQ process is the HARQ process that the first transport block plans to occupy, and the first HARQ process is indicated by the second DCI.

9. The method according to claim 8, characterized in that, The method further includes, assuming that the first transport block and the first HARQ process are actually scheduled, and the second PUSCH is not actually transmitted or the transmission of the second PUSCH is canceled: If the second PUSCH plan is used for the initial transmission, the terminal performs the first action; If the second PUSCH plan is used for retransmission, the terminal performs the second action; The first behavior includes at least one of the following: Assemble the first transport block and occupy the first HARQ process; Waiting for the PUSCH to retransmit the first transport block; The first transport block is transmitted using a single, defined PUSCH. The second action includes: ignoring retransmissions corresponding to the second PUSCH, or transmitting the first transport block using a determined single PUSCH.

10. The method according to any one of claims 1 to 3, characterized in that, The delay in transmitting the first PUSCH or the second PUSCH includes any one of the following: The first PUSCH or the second PUSCH is delayed until a first moment for transmission, where the first moment is the earliest moment when the delayed PUSCH and the reference PUSCH satisfy the first rule. Delay the first PUSCH or the second PUSCH by a second number of time domain units; Wherein, the delayed PUSCH is the delayed first PUSCH or the second PUSCH, and the reference PUSCH is all other PUSCHs in the dynamically scheduled PUSCH except for the delayed PUSCH.

11. The method according to claim 10, characterized in that, The method further includes any one of the following: The terminal determines the first moment based on the first requirement; The terminal expects the delayed PUSCH to meet the first requirement; The first requirement includes at least one of the following: The delayed PUSCH is determined to be a valid PUSCH; The delayed PUSCH does not overlap with the fourth PUSCH in the time domain within the corresponding frequency domain object range; The fourth PUSCH includes any fifth PUSCH other than the delayed PUSCH, and the fifth PUSCH includes any of the following: PUSCH, configuration-authorized PUSCH, and dynamically scheduled PUSCH.

12. The method according to any one of claims 1 to 3, characterized in that, The transmission that discards the first PUSCH or the second PUSCH includes any one of the following: The terminal ignores the sixth PUSCH. The terminal does not transmit the sixth PUSCH; The sixth PUSCH includes either the first PUSCH or the second PUSCH.

13. The method according to claim 12, characterized in that, After the terminal stops transmitting the sixth PUSCH, the method further includes any one of the following: The terminal assumes that the second transport block and the second HARQ process are not actually scheduled. The terminal assumes that the second transport block and the second HARQ process are actually scheduled, and that the sixth PUSCH is not actually transmitted or that the transmission of the sixth PUSCH is canceled. Wherein, the second transport block is the transport block carried by the sixth PUSCH plan, the second HARQ process is the HARQ process that the second transport block plan occupies, and the second HARQ process is indicated by the DCI that schedules the sixth PUSCH.

14. The method according to claim 13, characterized in that, The method further includes the following steps after the terminal assumes that the second transport block and the second HARQ process are actually scheduled, and the sixth PUSCH is not actually transmitted or the transmission of the sixth PUSCH is canceled: In the case that the sixth PUSCH plan is used for the initial transmission, the terminal performs the third action; If the sixth PUSCH plan is used for retransmission, the terminal performs the fourth action; The third act includes at least one of the following: Assemble the second transport block and occupy the second HARQ process; Waiting for the PUSCH to retransmit the second transport block; The second transport block is transmitted using a single, defined PUSCH; The fourth action includes: ignoring the retransmission corresponding to the sixth PUSCH, or using a determined single PUSCH to transmit the second transport block.

15. The method according to any one of claims 12 to 14, characterized in that, The method further includes: If it is desired to reuse at least one first uplink control information (UCI) on the sixth PUSCH, the terminal will reuse the second UCI on the seventh PUSCH. Wherein, the second UCI includes some or all of the first UCI, and the seventh PUSCH includes any one of the following: The PUSCHs in the dynamically scheduled PUSCHs, excluding the sixth PUSCH. PUSCHs in the PUSCH set that satisfy the second requirement; Wherein, the PUSCH set includes all PUSCHs on the frequency domain object corresponding to the sixth PUSCH or all PUSCHs of the terminal; the second requirement includes at least one of the following: The start time of the PUSCH is after the start time of the sixth PUSCH; The start time of the PUSCH is after the end time of the sixth PUSCH; The end time of the PUSCH is after the end time of the sixth PUSCH; The PUSCH is a dynamically scheduled PUSCH, or a dynamically scheduled PUSCH that is expected to carry the uplink shared channel, or a PUSCH with configuration authorization. PUSCH does not reuse UCI or does not reuse UCI that is expected to be carried by PUCCH; The total number of resources in PUSCH is greater than or equal to the number of resources required to reuse the second UCI; The number of time-domain resources for PUSCH is greater than or equal to the first threshold; The number of frequency domain resources for PUSCH is greater than or equal to the second threshold; The total number of PUSCH resources is greater than or equal to the third threshold; The time interval between the start time of PUSCH and the start time of PUCCH that is expected to carry the second UCI is greater than or equal to the second preset duration. The time interval between the start time of PUSCH and the end time of PUCCH that is expected to carry the second UCI is greater than or equal to the third preset duration. The time interval between the end time of PUSCH and the end time of PUCCH that is expected to carry the second UCI is greater than or equal to the fourth preset duration. The time interval between the start time of the PUSCH and the start time of the sixth PUSCH is greater than or equal to the fifth preset duration; The time interval between the start time of the PUSCH and the end time of the sixth PUSCH is greater than or equal to the sixth preset duration; The time interval between the end time of the PUSCH and the end time of the sixth PUSCH is greater than or equal to the seventh preset duration.

16. The method according to any one of claims 1 to 3, characterized in that, The method further includes: When the first frequency domain object corresponds to a single uplink shared channel processing channel, and the first PUSCH and the second PUSCH do not satisfy the first rule, the terminal performs the first operation. In the case where the first frequency domain object corresponds to multiple uplink shared channel processing channels, the terminal allocates the eighth PUSCH to a first PUSCH subset. The first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset. Each second PUSCH subset includes all PUSCHs associated with the same processing channel subset, and any two PUSCHs included in each second PUSCH subset satisfy the first rule. The processing channel subset includes at least one uplink shared channel processing channel among the multiple uplink shared channel processing channels corresponding to the first frequency domain object.

17. The method according to claim 16, characterized in that, In cases where the first frequency domain object corresponds to multiple uplink shared channel processing channels, before the terminal allocates the eighth PUSCH to the first PUSCH subset, the method further includes: If a predefined condition is met, the terminal performs any of the following: Discard the eighth PUSCH; According to the second rule, the eighth PUSCH is assigned to the third PUSCH subset, and the ninth PUSCH in the third PUSCH subset that does not satisfy the first rule with the eighth PUSCH is discarded. The predefined conditions include: the terminal determines that the eighth PUSCH needs to be allocated to the fourth PUSCH subset, and the number of first processing channels is greater than a processing channel number threshold; the fourth PUSCH subset is a single second PUSCH subset other than the at least one second PUSCH subset; the first number of processing channels is the sum of the number of second processing channels and the number of third processing channels; the second number of processing channels is the number of uplink shared channel processing channels required by the at least one second PUSCH subset; the third number of processing channels is the number of uplink shared channel processing channels required by the fourth PUSCH subset; and the processing channel number threshold is any one of the following: The number of uplink shared channel processing channels that the terminal can process in parallel; The number of uplink shared channel processing channels corresponding to the first frequency domain object; The third PUSCH subset is a single second PUSCH subset from the at least one second PUSCH subset.

18. The method according to claim 17, characterized in that, The second rule includes at least one of the following: The second PUSCH subset containing at least one tenth PUSCH is not considered the third PUSCH subset. The second subset of PUSCHs containing the fewest eleventh PUSCHs is taken as the third subset of PUSCHs; The second subset of PUSCHs, which includes the twelfth PUSCH, is the third subset of PUSCHs; Wherein, the tenth PUSCH is a PUSCH that satisfies the following: the PUSCH and the eighth PUSCH do not satisfy the first rule; the second time of the PUSCH and the third time of the eighth PUSCH do not satisfy the first timing requirement, the first timing requirement including that the time domain interval between the third time and the second time is greater than or equal to the eighth preset duration; Wherein, the eleventh PUSCH is a PUSCH that does not satisfy the first rule with the eighth PUSCH; Wherein, the twelfth PUSCH is the earliest eleventh PUSCH at the fourth time; Wherein, the second moment is any one of the following: The start time of PUSCH; The end time of PUSCH; The start time of the first time domain unit where PUSCH is located; The end time of the first time domain unit where PUSCH is located; The third moment is any one of the following: The start time of the fourth DCI of the eighth PUSCH is scheduled; The end time of the fourth DCI of the eighth PUSCH; The start time of the second CORESET where the fourth DCI is located; The end time of the second CORESET where the fourth DCI is located; The start time of the first time domain unit where the second CORESET is located; The end time of the first time-domain unit where the second CORESET is located; The fourth moment is any one of the following: The start time of the third DCI for scheduling PUSCH; The end time of the third DCI of the PUSCH scheduler; The start time of the first control resource set CORESET where the third DCI is located; The end time of the first CORESET where the third DCI is located; The start time of the first time domain unit where the first CORESET is located; The end time of the first time domain unit where the first CORESET is located; The start time of PUSCH; The end time of PUSCH; The start time of the first time domain unit where PUSCH is located; The end time of the first time-domain unit where PUSCH is located.

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. An uplink transmission processing method, characterized in that, include: If the first physical uplink shared channel (PUSCH) and the second PUSCH for the same terminal do not satisfy the first rule, the network-side device performs the second operation: The second operation includes any one of the following: Receive a third PUSCH that is rolled back from the second PUSCH, and the third PUSCH is not subject to the first rule; Delay receiving the first PUSCH or the second PUSCH; We do not expect to receive the first PUSCH or the second PUSCH; Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

21. The method according to claim 20, characterized in that, 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 second 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, the target time is the start time or the end time, and the target processing channel is the uplink shared channel processing channel corresponding to the second frequency domain object.

22. The method according to claim 21, 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.

23. The method according to any one of claims 20 to 22, characterized in that, The receiving of the third PUSCH backed by the second PUSCH includes: When the second PUSCH carries aperiodic channel state information (A-CSI) and the time interval between the first DCI and the second PUSCH is greater than or equal to a first preset duration, the network-side device receives the third PUSCH that is backed up from the second PUSCH.

24. The method according to any one of claims 20 to 23, characterized in that, The time-frequency resources of the third PUSCH satisfy any of the following: It has the same time-frequency resources as the second PUSCH; The time-frequency resources of the second PUSCH are determined after resource reduction based on the number of resource units required by A-CSI.

25. The method according to claim 24, characterized in that, The resource reduction includes at least one of the following: Reduce the occupied time domain units; The number of frequency domain units occupied is reduced.

26. The method according to claim 25, characterized in that, After reducing the occupied time domain units, the number of resource units that can support A-CSI corresponding to the remaining time domain units is the minimum value that is greater than or equal to the first number; Alternatively, after reducing the occupied frequency domain units, the number of resource units corresponding to the remaining frequency domain units that can support A-CSI is the minimum value that is greater than or equal to the first number. Wherein, the first quantity is the number of resource units required by the A-CSI.

27. The method according to any one of claims 20 to 22, characterized in that, The delayed reception of the first PUSCH or the second PUSCH includes any one of the following: The first PUSCH or the second PUSCH is received at a first moment, where the first moment is the earliest moment when the delayed PUSCH and the reference PUSCH satisfy the first rule. The first PUSCH or the second PUSCH is received with a second number of time-domain units delayed; Wherein, the delayed PUSCH is the delayed first PUSCH or the second PUSCH, and the reference PUSCH is all other PUSCHs in the dynamically scheduled PUSCH except for the delayed PUSCH.

28. The method according to claim 27, characterized in that, The method further includes any one of the following: The network-side device determines the first moment based on the first requirement; The network-side device expects the PUSCH delay to meet the first requirement; The first requirement includes at least one of the following: The delayed PUSCH is determined to be a valid PUSCH; The delayed PUSCH does not overlap with the fourth PUSCH in the time domain within the corresponding frequency domain object range; The fourth PUSCH includes any fifth PUSCH other than the delayed PUSCH, and the fifth PUSCH includes any of the following: PUSCH, configuration-authorized PUSCH, and dynamically scheduled PUSCH.

29. The method according to any one of claims 20 to 22, characterized in that, The method further includes: When the first frequency domain object corresponds to a single uplink shared channel processing channel, and the first PUSCH and the second PUSCH do not satisfy the first rule, the network-side device performs the second operation. In the case where the first frequency domain object corresponds to multiple uplink shared channel processing channels, the network-side device allocates the eighth PUSCH to a first PUSCH subset. The first PUSCH subset is one of the second PUSCH subsets in at least one second PUSCH subset. Each second PUSCH subset includes all PUSCHs associated with the same processing channel subset, and any two PUSCHs included in each second PUSCH subset satisfy the first rule. The processing channel subset includes at least one uplink shared channel processing channel among the multiple uplink shared channel processing channels corresponding to the first frequency domain object.

30. The method according to claim 29, characterized in that, In the case where the first frequency domain object corresponds to multiple uplink shared channel processing channels, before the network-side device allocates the eighth PUSCH to the first PUSCH subset, the method further includes: If predefined conditions are met, the network-side device performs any of the following: We do not expect to receive the eighth PUSCH; According to the second rule, the eighth PUSCH is assigned to the third PUSCH subset, and it is not expected to receive the ninth PUSCH in the third PUSCH subset that does not satisfy the first rule with the eighth PUSCH. The predefined conditions include: the network-side device determines that the eighth PUSCH needs to be allocated to the fourth PUSCH subset, and the number of first processing channels is greater than a processing channel number threshold; the fourth PUSCH subset is a single second PUSCH subset other than the at least one second PUSCH subset; the first processing channel number is the sum of the number of second processing channels and the number of third processing channels; the second processing channel number is the number of uplink shared channel processing channels required by the at least one second PUSCH subset; the third processing channel number is the number of uplink shared channel processing channels required by the fourth PUSCH subset; and the processing channel number threshold is any one of the following: The number of uplink shared channel processing channels that the terminal can process in parallel; The number of uplink shared channel processing channels corresponding to the first frequency domain object; The third PUSCH subset is a single second PUSCH subset from the at least one second PUSCH subset.

31. The method according to claim 30, characterized in that, The second rule includes at least one of the following: The second PUSCH subset containing at least one tenth PUSCH is not considered the third PUSCH subset. The second subset of PUSCHs containing the fewest eleventh PUSCHs is taken as the third subset of PUSCHs; The second subset of PUSCHs, which includes the twelfth PUSCH, is the third subset of PUSCHs; Wherein, the tenth PUSCH is a PUSCH that satisfies the following: the PUSCH and the eighth PUSCH do not satisfy the first rule; the second time of the PUSCH and the third time of the eighth PUSCH do not satisfy the first timing requirement, the first timing requirement including that the time domain interval between the third time and the second time is greater than or equal to the eighth preset duration; Wherein, the eleventh PUSCH is a PUSCH that does not satisfy the first rule with the eighth PUSCH; Wherein, the twelfth PUSCH is the earliest eleventh PUSCH at the fourth time; Wherein, the second moment is any one of the following: The start time of PUSCH; The end time of PUSCH; The start time of the first time domain unit where PUSCH is located; The end time of the first time domain unit where PUSCH is located; The third moment is any one of the following: The start time of the fourth DCI of the eighth PUSCH is scheduled; The end time of the fourth DCI of the eighth PUSCH; The start time of the second CORESET where the fourth DCI is located; The end time of the second CORESET where the fourth DCI is located; The start time of the first time domain unit where the second CORESET is located; The end time of the first time-domain unit where the second CORESET is located; The fourth moment is any one of the following: The start time of the third DCI for scheduling PUSCH; The end time of the third DCI of the PUSCH scheduler; The start time of the first control resource set CORESET where the third DCI is located; The end time of the first CORESET where the third DCI is located; The start time of the first time domain unit where the first CORESET is located; The end time of the first time domain unit where the first CORESET is located; The start time of PUSCH; The end time of PUSCH; The start time of the first time domain unit where PUSCH is located; The end time of the first time-domain unit where PUSCH is located.

32. The method according to any one of claims 20 to 31, 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.

33. An uplink transmission processing device, characterized in that, include: The transmitting module is configured to perform a first operation when the first physical uplink shared channel (PUSCH) and the second PUSCH do not satisfy the first rule: The first operation includes any one of the following: The second PUSCH is rolled back to the third PUSCH, and the third PUSCH is not subject to the first rule. Delay the transmission of the first PUSCH or the second PUSCH; Discard the transmission of the first PUSCH or the second PUSCH; Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

34. The apparatus according to claim 33, characterized in that, 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 second 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, the target time is the start time or the end time, and the target processing channel is the uplink shared channel processing channel corresponding to the second frequency domain object.

35. The apparatus according to claim 33 or 34, characterized in that, The sending module is specifically used to: when the second PUSCH carries aperiodic channel state information A-CSI and the time-domain interval between the first DCI and the second PUSCH is greater than or equal to a first preset duration, the second PUSCH is backed up to the third PUSCH.

36. An uplink transmission processing device, characterized in that, include: The receiving module is configured to perform a second operation when the first physical uplink shared channel (PUSCH) and the second PUSCH for the same terminal do not meet the first rule: The second operation includes any one of the following: Receive a third PUSCH that is rolled back from the second PUSCH, and the third PUSCH is not subject to the first rule; Delay receiving the first PUSCH or the second PUSCH; We do not expect to receive the first PUSCH or the second PUSCH; Wherein, the first PUSCH and the second PUSCH correspond to the same first frequency domain object, the first PUSCH is scheduled by the first downlink control information (DCI), and the second PUSCH is scheduled by the second DCI; the first rule is used to characterize the timing relationship requirements between any two PUSCHs on the same frequency domain object.

37. The apparatus according to claim 36, characterized in that, 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 second 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, the target time is the start time or the end time, and the target processing channel is the uplink shared channel processing channel corresponding to the second frequency domain object.

38. 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 processing method as described in any one of claims 1 to 32.

39. 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 processing method as described in any one of claims 1 to 32.

40. 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 processing method as described in any one of claims 1 to 32.

41. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps of the uplink transmission processing method as described in any one of claims 1 to 32.

Images