Channel determination method and apparatus, channel scheduling method and apparatus, and communication device

Abstract

The present application belongs to the technical field of communications. Disclosed are a channel determination method and apparatus, a channel scheduling method and apparatus, and a communication device. The channel determination method in the embodiments of the present application comprises: a terminal receiving downlink control information (DCI) from a network-side device, wherein the DCI is used for scheduling N physical shared channels, and the N physical shared channels are all PUSCHs, or the N physical shared channels are all PDSCHs, N being an integer greater than or equal to 1; and on the basis of the DCI, the terminal determining a correspondence between a target physical shared channel and a hybrid automatic repeat request (HARQ) process, wherein the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

Description

Channel determination method, channel scheduling method, device and communication equipment

[0001] Cross-references

[0002] This disclosure claims priority to Chinese patent application No. 202410171134.3 filed on February 6, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a channel determination method, a channel scheduling method, an apparatus and a communication device. Background Art

[0004] The physical shared channel is scheduled using downlink control information (DCI). In related technologies, a single DCI can typically schedule only one physical shared channel in the same transmission direction (uplink or downlink), and HARQ-ACK feedback is performed for each downlink physical shared channel. This results in a lack of flexibility in physical shared channel scheduling, and the HARQ-ACK feedback overhead for downlink physical shared channels is high. Summary of the Invention

[0005] The embodiments of the present application provide a channel determination method, a channel scheduling method, an apparatus, and a communication device, which can solve the problems in related technologies of lack of flexibility in scheduling of physical shared channels and large HARQ-ACK feedback overhead of downlink physical shared channels.

[0006] In a first aspect, a channel determination method is provided, which is performed by a terminal. The method includes:

[0007] The terminal receives downlink control information DCI from a network-side device, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels PUSCH, or the N physical shared channels are all downlink physical shared channels PDSCH, where N is an integer greater than or equal to 1;

[0008] The terminal determines a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel based on the DCI, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

[0009] In a second aspect, a channel scheduling method is provided, which is performed by a network-side device. The method includes:

[0010] The network-side device sends downlink control information DCI to the terminal, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels PUSCH, or the N physical shared channels are all downlink physical shared channels PDSCH, where N is an integer greater than 1;

[0011] The DCI is used to determine a correspondence between a target physical shared channel and a hybrid automatic repeat request HARQ process, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

[0012] In a third aspect, a channel determination device is provided, which is applied to a terminal. The device includes:

[0013] a receiving unit, configured to receive downlink control information DCI from a network-side device, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels PUSCH, or the N physical shared channels are all downlink physical shared channels PDSCH, where N is an integer greater than or equal to 1;

[0014] The first processing unit is configured to determine, based on the DCI, a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

[0015] In a fourth aspect, a channel scheduling device is provided, which is applied to a network-side device, and includes:

[0016] a sending unit, configured to send downlink control information DCI to a terminal, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels PUSCH, or the N physical shared channels are all downlink physical shared channels PDSCH, where N is an integer greater than 1;

[0017] The DCI is used to determine a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

[0018] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0019] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to: receive downlink control information DCI from a network side device, the DCI being used to schedule N physical shared channels, the N physical shared channels being all uplink physical shared channels PUSCH, or the N physical shared channels being all downlink physical shared channels PDSCH, where N is an integer greater than or equal to 1; the processor being used to: determine, based on the DCI, a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel, the target physical shared channel being the N physical shared channels, or the target physical shared channel being a valid physical shared channel among the N physical shared channels.

[0020] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0021] In an eighth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to: send downlink control information (DCI) to a terminal, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels (PUSCHs), or where the N physical shared channels are all downlink physical shared channels (PDSCHs), where N is an integer greater than 1;

[0022] The DCI is used to determine a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

[0023] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0024] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0025] In the eleventh aspect, a chip is provided, which includes 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 the method as described in the first aspect, or to implement the method as described in the second aspect.

[0026] In the twelfth 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 channel determination method as described in the first aspect, or to implement the steps of the channel scheduling method as described in the second aspect.

[0027] In an embodiment of the present application, a terminal receives a DCI from a network-side device, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all PUSCHs, or where the N physical shared channels are all PDSCHs, and N is an integer greater than or equal to 1; the terminal determines the HARQ process corresponding to the target physical shared channel based on the DCI, where the target physical shared channel is the N physical shared channels, or where the target physical shared channel is a valid physical shared channel among the N physical shared channels. Since a single DCI can schedule N PUSCHs or N PDSCHs, the embodiment of the present application can improve the flexibility of physical shared channel scheduling and, in addition, reduce the scheduling overhead of the physical shared channel. Furthermore, these N physical shared channels occupy one or more HARQ processes, which can reduce the HARQ process occupancy overhead and HARQ-ACK feedback overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a schematic diagram of a network structure applicable to an embodiment of the present application;

[0029] Figure 2 is a schematic diagram of the BWP switching mechanism in NR;

[0030] FIG3 is a flow chart of a channel determination method provided in an embodiment of the present application;

[0031] FIG4 is a schematic diagram of a single DCI scheduling multiple PXSCHs for parallel transmission provided by an embodiment of the present application;

[0032] FIG5 is a flow chart of a channel scheduling method provided in an embodiment of the present application;

[0033] FIG6 is a structural diagram of a channel determination device provided in an embodiment of the present application;

[0034] FIG7 is a structural diagram of a channel scheduling device provided in an embodiment of the present application;

[0035] FIG8 is a structural diagram of a communication device provided in an embodiment of the present application;

[0036] FIG9 is a structural diagram of a terminal provided in an embodiment of the present application;

[0037] FIG10 is a structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0039] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0040] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication 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 operation to be performed or the requested result, etc. based on the judgment result.

[0041] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, 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 the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0042] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the 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 (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0043] Before describing the embodiments of the present application, the following briefly introduces the relevant technologies:

[0044] 1. Aggregation Requirements for Discrete / Fragmented Spectrum

[0045] Sub-3GHz spectrum (i.e., frequencies below 3GHz) offers advantages such as wide coverage and low penetration loss, playing a vital role in cellular network deployment. Compared to higher-frequency bands, the sub-3GHz spectrum is fragmented and allocated to different wireless communication systems. Competition among mobile operators further fragments the spectrum available to each operator.

[0046] From the perspective of a single operator, almost all operators around the world have multiple Sub-3GHz frequency bands, such as 700MHz, 800MHz, 900MHz, 1.4GHz, 1.8GHz, 2.1GHz, 2.3GHz or 2.6GHz bands. Related technologies such as Carrier Aggregation (CA) or Dual Connectivity (DC) can aggregate multiple discrete or cross-band spectrums to provide higher throughput performance for a single user equipment (UE, also known as a terminal). However, the CA / DA mechanism will bring greater complexity and overhead both from the network side and from the terminal side. It can be expected that if multiple discrete spectrums can be aggregated into a single carrier or cell in a more efficient way, the complexity and overhead on both the network side and the terminal side can be significantly reduced; at the same time, data transmission performance, such as throughput and latency, as well as operational flexibility, can also be improved.

[0047] 2. Bandwidth Part (BWP) Mechanism in NR

[0048] Mobile communication systems need to adapt to increasingly diverse scenarios and service requirements. For example, key 5G scenarios include enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine type communications (mMTC). These scenarios place high demands on the system for low latency, high reliability, large bandwidth, and wide coverage. Terminals require different transmission bandwidths for different application scenarios. In NR, base stations can configure and / or schedule terminals to transmit on different bandwidths based on their needs.

[0049] In NR, the network can configure one or more BWPs for the UE for data transmission. A single BWP corresponds to a continuous range of frequency domain resources. By selecting and activating different BWPs, the available bandwidth for communication between the network and the UE can be adaptively adjusted. Furthermore, within a BWP in effect at a given moment, the actual occupied bandwidth can be controlled through appropriate resource configuration and scheduling, enabling more flexible and precise resource allocation. This reduces power consumption, time-frequency resources, and other overhead while meeting data transmission requirements.

[0050] Figure 2 illustrates the BWP switching mechanism, using the following example. At the first moment, the UE's downlink traffic is high, so the network activates a larger bandwidth for the UE (i.e., DL BWP1). At the second moment, the UE's downlink traffic is low, so the network activates a smaller bandwidth for the UE (i.e., DL BWP2) to meet basic communication needs. At the third moment, the network detects severe frequency-selective fading in the spectrum corresponding to DL BWP1, or that resources in the frequency domain corresponding to DL BWP2 are scarce, and activates a new bandwidth for the UE (i.e., DL BWP3) in another frequency domain.

[0051] Each BWP can be independently configured with corresponding parameters, including common parameters such as cyclic prefix (CP) or subcarrier spacing (SCS), as well as common parameters or dedicated parameters corresponding to each channel or signal.

[0052] 3. Hybrid Automatic Repeat Request (HARQ) Process Management in NR

[0053] 1. Downward direction

[0054] A medium access control (MAC) entity includes a corresponding HARQ entity for each serving cell, and the HARQ entity maintains multiple parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier.

[0055] When downlink spatial multiplexing is not enabled (or turned on) at the physical layer, a single HARQ process supports the transmission of only one transport block (TB) at a time. When downlink spatial multiplexing is enabled (or turned on) at the physical layer, each HARQ process can support the transmission of one or two TBs at a time.

[0056] 2. Upward direction

[0057] The MAC entity includes a corresponding HARQ entity for each serving cell configured with an uplink (including a supplementary uplink), and the HARQ entity maintains multiple parallel HARQ processes. Each HARQ process supports only one TB transmission at a time.

[0058] To address the need for aggregating discrete / fragmented spectrum in related technologies, one possible solution is to aggregate multiple discrete spectrums into a single cell to reduce complexity and overhead on both the terminal and network sides. However, related technologies lack a corresponding physical shared channel scheduling solution for aggregating multiple discrete spectrums into a single cell, which results in data transmission failures for terminals.

[0059] In view of this, the embodiments of the present application provide a channel determination method, a channel scheduling method, an apparatus and a communication device to solve the problem that in the scenario where multiple discrete spectrums are aggregated into a single cell, the terminal cannot transmit data due to the lack of corresponding physical shared channel scheduling scheme in the relevant technology.

[0060] In an embodiment of the present application, for a single cell formed by the aggregation of multiple discrete spectrums, a single downlink control information (DCI) is allowed to schedule multiple physical shared channels in a certain transmission direction. Taking the uplink transmission direction as an example, a single DCI is allowed to schedule multiple physical uplink shared channels (PUSCH). Taking the downlink transmission direction as an example, a single DCI is allowed to schedule multiple physical downlink shared channels (PDSCH).

[0061] The channel determination method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0062] FIG3 shows a flow chart of a channel determination method provided by an embodiment of the present application. As shown in FIG3 , the channel determination method includes the following steps:

[0063] Step 301: The terminal receives DCI from a network-side device, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all PUSCHs, or the N physical shared channels are all PDSCHs, where N is an integer greater than or equal to 1.

[0064] Step 302: The terminal determines a HARQ process corresponding to a target physical shared channel based on the DCI, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

[0065] For ease of description, the embodiments of the present application do not distinguish whether the physical shared channel is PUSCH or PDSCH, and PXSCH is uniformly used to represent the physical shared channel of a certain transmission direction.

[0066] In an embodiment of the present application, N PXSCHs may be transmitted in parallel or not, that is, a single DCI may schedule multiple PXSCHs that may be transmitted in parallel, or in other words, a single DCI may schedule multiple PXSCHs that are allowed to be transmitted in parallel. Assume that a single PXSCH is located in a single BWP, but multiple PXSCHs are allowed to be transmitted in parallel within at least one BWP of the same service cell. The "parallel transmission" here can be understood as at least two of the multiple PXSCHs overlapping in the time domain (including partial overlap, complete overlap, etc.). For example, there are 3 PXSCHs, of which PXSCH1 and PXSCH2 overlap, PXSCH2 and PXSCH3 overlap, and PXSCH1 and PXSCH3 may or may not overlap. Figure 4 shows a schematic diagram of a single DCI scheduling multiple PXSCHs for parallel transmission.

[0067] It should be noted that the embodiment of the present application does not limit N PXSCHs to parallel transmission, so as to enhance the flexibility of the mechanism and accommodate more situations.

[0068] The N PXSCHs may include, for example, at least one of the following:

[0069] Configured Grant (CG) PUSCH with Type 1 (CG PUSCH with Type 1);

[0070] CG PUSCH with Type 2;

[0071] Semi-Persistent Scheduling (SPS) PDSCH;

[0072] Dynamically Granted (DG) PUSCH;

[0073] DG PDSCH.

[0074] The embodiments of the present application mainly consider multiple PXSCHs in the same transmission direction. When there are multiple PXSCHs in different transmission directions, the operations of the embodiments of the present application can be applied separately to each transmission direction.

[0075] Each of the N PXSCHs scheduled by DCI can be collectively referred to as a scheduled PXSCH, that is, any PXSCH or each PXSCH scheduled based on the time / frequency domain resource allocation in DCI, regardless of whether it is a valid PXSCH or an invalid PXSCH.

[0076] When a Scheduled PXSCH satisfies at least one of the following conditions, it is determined to be Invalid (i.e., Invalid PXSCH); otherwise, it is determined to be Valid (i.e., Valid PXSCH):

[0077] Corresponds to Invalid frequency domain resource allocation (FDRA). Invalid FDRA can be one of the following: resource allocation type 0 is used, and the bits corresponding to the frequency domain resource allocation information are all 0; resource allocation type 1 is used, and the bits corresponding to the frequency domain resource allocation information are all 1; resource allocation adopts dynamic switching mode, and the bits corresponding to the frequency domain resource allocation information are all 0 or all 1.

[0078] Overlapping with at least one invalid symbol in the time domain. For PUSCH, the invalid symbol can include at least one of the following: a semi-static downlink (DL) symbol, a synchronization signal block (SSB) symbol, or a control resource set (CORESET) #0 symbol. For PDSCH, the invalid symbol can be a semi-static uplink (UL) symbol. The semi-static DL / UL / flexible symbol in a serving cell can be understood as a DL / UL / flexible symbol determined based on the cell-common time division duplex (TDD) pattern configuration information of the serving cell (for example, determined by the higher-layer parameter TDD-UL-DL-ConfigCommon) and / or the UE-specific TDD pattern configuration information (for example, determined by the higher-layer parameter TDD-UL-DL-ConfigDedicated). When neither the cell-common TDD pattern configuration information nor the UE-specific TDD pattern configuration information exists in the serving cell, all symbols in the serving cell can be understood as semi-static flexible symbols or processed as semi-static flexible symbols. For PUSCH, only invalid symbols in the serving cell where the PUSCH is located are considered; for PDSCH, only invalid symbols in the serving cell where the PDSCH is located are considered.

[0079] When subband full duplex (SBFD) is deployed within a BWP, it overlaps with at least one resource block (RB) or resource element (RE) of the reverse subband and / or guard band. For the PUSCH, the reverse subband can be a DL subband. For the PDSCH, the reverse subband can be a UL subband.

[0080] In an embodiment of the present application, a terminal receives a DCI from a network-side device, wherein the DCI is used to schedule N PXSCHs, wherein the N PXSCHs are all PUSCHs, or the N PXSCHs are all PDSCHs, and N is an integer greater than or equal to 1; the terminal determines the HARQ process corresponding to the target PXSCH based on the DCI, wherein the target PXSCH is the N PXSCHs, or the target PXSCH is a valid PXSCH among the N PXSCHs. Since a single DCI can schedule N PUSCHs or N PDSCHs, the embodiment of the present application can improve the flexibility of physical shared channel scheduling, and in addition, can reduce the scheduling overhead of the physical shared channel. Moreover, these N physical shared channels occupy one or more HARQ processes, which can reduce the HARQ process occupancy overhead and HARQ-ACK feedback overhead.

[0081] The embodiments of the present application can be applied to scenarios where multiple discrete spectrums are aggregated into a single cell. In this scenario, a single DCI can schedule N PXSCHs on one or more BWPs in the same service cell. These N PXSCHs allow for parallel transmission, which can fully utilize the frequency domain resources of the cell, improve data throughput, and reduce transmission latency.

[0082] In the embodiment of the present application, determining the HARQ process corresponding to the target PXSCH can also be understood as determining the HARQ process ID corresponding to (or occupied by) the target PXSCH. The following describes the implementation method for determining the HARQ process.

[0083] In some embodiments, the terminal determines, based on the DCI, a HARQ process corresponding to the target physical shared channel, including:

[0084] The terminal determines, based on the DCI and the correspondence between the target physical shared channel and the HARQ process, the HARQ process corresponding to the target physical shared channel;

[0085] The correspondence between the target physical shared channel and the HARQ process includes any one of the following:

[0086] The target PXSCH corresponds to the same HARQ process;

[0087] Each PXSCH in the target PXSCH corresponds to a different HARQ process;

[0088] Each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process.

[0089] Specifically, the HARQ process may be determined in any of the following ways:

[0090] HARQ process ID determination method 1: All scheduled / valid PXSCHs scheduled by a single DCI correspond to the same HARQ process;

[0091] HARQ process ID determination method 2: Multiple Scheduled / Valid PXSCHs scheduled by a single DCI correspond to different HARQ processes;

[0092] HARQ process ID determination method 3: Each group of scheduled / valid PXSCHs in multiple scheduled / valid PXSCHs scheduled by a single DCI corresponds to the same HARQ process.

[0093] Among them, HARQ process ID determination method 1 can follow the mechanism in the relevant technology to indicate a single HARQ process ID in the DCI to identify the HARQ processes corresponding to all Scheduled / Valid PXSCHs scheduled by this DCI.

[0094] Since any of the above methods can be used to determine the HARQ process corresponding to the target PXSCH, the HARQ process corresponding to the PXSCH can be determined more flexibly.

[0095] The terminal performs transceiver processing on at least one TB corresponding to this HARQ process (i.e., the single HARQ process corresponding to the single HARQ process ID indicated by this DCI) based on all scheduled / valid PXSCHs scheduled by this DCI. The transmitting end processing may include: determining the valid PXSCH set corresponding to each TB; determining the transport block size (TBS) corresponding to each TB; and performing rate matching and RE mapping operations for each TB.

[0096] The following describes an implementation method related to HARQ process ID determination method 1.

[0097] In some embodiments, when multiple PXSCHs correspond to the same HARQ process, the multiple PXSCHs meet a predefined condition; the multiple PXSCHs are the target PXSCHs, or the multiple PXSCHs are PXSCHs located in the same PXSCH group;

[0098] The predefined conditions include at least one of the following:

[0099] Each of the multiple PXSCHs corresponds to the same activated (Active) BWP;

[0100] Each of the multiple PXSCHs corresponds to a different activated BWP;

[0101] The SCS corresponding to each PXSCH in the multiple PXSCHs is the same;

[0102] The CPs corresponding to the respective PXSCHs in the multiple PXSCHs are the same;

[0103] The time domain resource corresponding to each PXSCH in the multiple PXSCHs meets the first preset condition;

[0104] The number of physical resource blocks (PRBs) occupied by each of the multiple PXSCHs is less than or equal to a first preset threshold;

[0105] The total number of PRBs occupied by the multiple PXSCHs is less than or equal to a second preset threshold;

[0106] The TBSs of the multiple PXSCHs are less than or equal to a third preset threshold;

[0107] The difference in channel quality of the multiple PXSCHs is less than or equal to a fourth preset threshold;

[0108] The number of layers of each PXSCH mapping in the multiple PXSCHs is equal;

[0109] The maximum number of TBs supported by each PXSCH in the multiple PXSCHs is equal;

[0110] The number of TBs actually scheduled by each PXSCH in the multiple PXSCHs is equal.

[0111] Optionally, the first preset condition includes at least one of the following:

[0112] The duration of time domain resources overlaps;

[0113] The interval between the start times of the time domain resources is less than or equal to a fifth preset threshold;

[0114] The interval between the end times of the time domain resources is less than or equal to a sixth preset threshold;

[0115] The time domain resources are located in the same time domain unit.

[0116] That is, when HARQ process ID determination mode 1 is adopted, it may be required (or UE expected, or network side guaranteed) that all Scheduled / Valid PXSCHs scheduled by this DCI meet predefined conditions, and the predefined conditions include at least one of the following (a) to (h):

[0117] (a) are located in the same Active BWP, or, are located in different Active BWPs;

[0118] (b) SCS / CP are the same;

[0119] (c) Time domain resource allocation and occupancy meet predefined requirements. The predefined requirements here may include at least one of the following (c.1) to (c.3):

[0120] (c.1) The durations of the time domain resources completely overlap, or at least partially overlap, or the overlap ratio is greater than or equal to a predefined threshold;

[0121] (c.2) The interval between the start and end times of the time domain resource is less than or equal to a predefined threshold;

[0122] (c.3) Time domain resources must be located within the same radio frame / sub-frame / time slot. Optionally, when time-frequency resources are required to be located within the same slot, the scheduled / valid PXSCH must be located within the same Active BWP, or the slot boundaries of multiple Active BWPs involved must be aligned (for example, the SCS / CP corresponding to these multiple Active BWPs must be the same).

[0123] (d) The number of PRBs meets the requirements, for example, the number of PRBs occupied by a single valid PXSCH is less than or equal to a predefined threshold, and / or the sum of the number of PRBs occupied by all valid PXSCHs is less than or equal to a predefined threshold.

[0124] (e) The TB size meets the requirements, which can be understood as: based on the time-frequency resources and transmission attributes corresponding to all valid PXSCHs, the determined TB size is less than or equal to a predefined threshold.

[0125] (f) The channel qualities are similar, for example, the corresponding modulation and coding schemes (MCS) are equal or the difference is less than or equal to a predefined threshold.

[0126] (g) The number of mapping layers is equal;

[0127] (h) The maximum number of TBs supported is equal, and / or the number of TBs actually scheduled is equal, for example, each valid PXSCH supports dual codeword transmission, and / or a single TB is actually scheduled or two TBs are actually scheduled.

[0128] It is understandable that when two TBs are actually scheduled, it may be determined for each TB whether the above-mentioned “TBS meets the requirement” item and / or “channel quality is similar” item is satisfied.

[0129] The following describes an implementation method related to HARQ process ID determination method 2.

[0130] In some embodiments, when each PXSCH in the target PXSCH corresponds to a different HARQ process, determining the HARQ process corresponding to the target PXSCH includes any one of the following:

[0131] Determine, according to the first information included in the DCI, the HARQ process corresponding to each PXSCH in the target PXSCH;

[0132] Determine the HARQ process corresponding to each PXSCH in the target PXSCH according to the second information included in the DCI and the first rule;

[0133] The first information is used to indicate the HARQ process corresponding to each PXSCH in the target PXSCH;

[0134] The second information is used to indicate that the first HARQ process identifier corresponds to the first PXSCH in the target PXSCH;

[0135] The first rule is predefined by a protocol, configured by a network, or indicated by the DCI.

[0136] Optionally, the first information indicates the HARQ processes corresponding to each PXSCH in the target PXSCH in sequence based on the PXSCH order of the target PXSCH.

[0137] Optionally, the first information includes at least one of the following:

[0138] X first indication fields, where the X first indication fields are used to respectively indicate the HARQ processes corresponding to the respective PXSCHs in the target PXSCH;

[0139] A second indication field, where the second indication field is used to jointly indicate the HARQ processes corresponding to each PXSCH in the target PXSCH;

[0140] A first bitmap, wherein X bits in the first bitmap are set to predetermined values ​​and are used to respectively indicate the HARQ processes corresponding to each PXSCH in the target PXSCH;

[0141] Here, the value of X is equal to the number of PXSCHs included in the target PXSCH.

[0142] Each indication field in the DCI involved in the embodiments of the present application can also be understood as a corresponding indication bit in the DCI. For example, the first indication field can be replaced by the first indication bit, the second indication field can be replaced by the second indication bit, and so on.

[0143] The “predetermined value” mentioned in the first bitmap may be 1. That is, when the value of a bit in the first bitmap is 1, it indicates that the corresponding HARQ process is assigned to a Scheduled / Valid PXSCH, or is occupied by this Scheduled / Valid PXSCH, or corresponds to this Scheduled / Valid PXSCH.

[0144] That is, when HARQ process ID determination method 2 is adopted, the HARQ process corresponding to each Scheduled / Valid PXSCH can be determined by using any of the following HARQ process ID determination methods 2-1 and 2-2:

[0145] HARQ process ID determination method 2-1: Indicate the HARQ process corresponding to each Scheduled / Valid PXSCH separately

[0146] Specifically, the HARQ process ID determination method 2-1 may adopt any one of the HARQ process ID determination methods 2-1-1 to 2-1-3:

[0147] HARQ process ID determination method 2-1-1: Use independent indication fields / indication bits to indicate the HARQ process corresponding to each Scheduled / Valid PXSCH

[0148] Specifically, the indication field / indication bit corresponding to each Scheduled / Valid PXSCH can completely independently indicate a HARQ process of the current serving cell in a given transmission direction. For example, for the uplink, the indication field / indication bit corresponding to each Scheduled / Valid PXSCH contains 4 bits or 5 bits, which can independently indicate any HARQ process among the 16 or 32 HARQ processes corresponding to the current serving cell.

[0149] Optionally, a differential indication method can be introduced to save indication overhead. For example, the indication field / indication bit corresponding to the first Scheduled / Valid PXSCH can indicate any HARQ process of the current serving cell in a given transmission direction, for example, occupying 4 or 5 bits for the uplink; the indication field / indication bit corresponding to a subsequent Scheduled / Valid PXSCH adopts a differential method, only indicating the increment or decrement of the HARQ process ID corresponding to the first Scheduled / Valid PXSCH, so that based on the HARQ process ID corresponding to the first Scheduled / Valid PXSCH and the indicated increment or decrement, the HARQ process ID corresponding to this Scheduled / Valid PXSCH can be determined. At this time, the indication field / indication bit corresponding to this Scheduled / Valid PXSCH can occupy fewer bits, for example, only occupying 2 or 3 bits for the uplink. When indicating an increment or decrement, the indication field / indication bit can directly indicate the numerical value and / or direction corresponding to the increment or decrement, or indicate a value in the increment and / or decrement list specified by the protocol or configured by high-level signaling.

[0150] HARQ process ID determination method 2-1-2: adopt joint coding method, use the same indication field / indication bit to simultaneously indicate the HARQ process corresponding to each Scheduled / Valid PXSCH

[0151] For example, some HARQ process combinations that are desired to be scheduled or preferably scheduled may be pre-defined or configured; and then an indication field / indication bit may be used in the scheduling DCI to indicate the ID / index of the selected HARQ process combination.

[0152] HARQ process ID determination method 2-1-3: Use Bitmap to indicate the HARQ process corresponding to each Scheduled / Valid PXSCH

[0153] Considering that the scheduling here is for the same service cell, the HARQ processes corresponding to each Scheduled / Valid PXSCH are not allowed to conflict with each other (that is, the same HARQ process is not allowed to correspond to more than one Scheduled / Valid PXSCH), and Bitmap can be used in DCI to indicate the HARQ processes corresponding to each Scheduled / Valid PXSCH.

[0154] Specifically, the number of bits in the Bitmap is determined based on the number of HARQ processes available in the current serving cell in a given transmission direction, and each bit in the Bitmap corresponds one by one to each HARQ process in the current serving cell in a given transmission direction in ascending order based on the HARQ process ID. For example, the first bit in the Bitmap corresponds to HARQ process 0. When the value of a bit is 1, it indicates that the corresponding HARQ process is assigned to a Scheduled / Valid PXSCH, or is occupied by this Scheduled / Valid PXSCH, or corresponds to this Scheduled / Valid PXSCH.

[0155] Optionally, at least one HARQ process allocated based on the Bitmap in the DCI corresponds one-to-one to at least one Scheduled / Valid PXSCH scheduled by this DCI based on the ascending order of the HARQ process ID and the order between PXSCHs (which may be referred to as PXSCH order) (see the relevant description below). Optionally, the UE expects that the number of HARQ processes allocated based on the Bitmap in the DCI is equal to the number of Scheduled / Valid PXSCHs scheduled by this DCI.

[0156] For HARQ process ID determination method 2-1-1 or HARQ process ID determination method 2-1-2, the order between the HARQ process information corresponding to each scheduled PXSCH (for example, for HARQ process ID determination method 2-1-1, the order between the indication fields / indication bits used to indicate the HARQ processes corresponding to each scheduled PXSCH; for HARQ process ID determination method 2-1-2, the order between the HARQ process information corresponding to each scheduled PXSCH in the HARQ process combination) can follow the order between PXSCHs (see the relevant description below), for example, based on the order between the BWPs corresponding to the PXSCHs (which may be referred to as the BWP order) (see the corresponding description below), the ascending order of the starting time of the PXSCH and / or the ascending order of the lowest frequency corresponding to the frequency domain resources occupied by the PXSCH, etc.

[0157] HARQ process ID determination method 2-2: Determine the HARQ process corresponding to each scheduled / valid PXSCH based on a single HARQ process indication and predefined rules

[0158] A single HARQ process ID is indicated in the DCI. The single HARQ process ID indicated by the DCI applies to the first Scheduled / Valid PXSCH scheduled by this DCI. The HARQ process ID corresponding to the subsequent Scheduled / Valid PXSCH = (HARQ process ID corresponding to the previous Scheduled / Valid PXSCH + 1) modulo the predefined number of HARQ processes, where mod represents modulo. The "predefined number of HARQ processes" here can be: the number of HARQ processes available in the current serving cell in a given transmission direction, as specified by the protocol or configured by higher-layer signaling.

[0159] The following describes an implementation method related to HARQ process ID determination method 3.

[0160] In some embodiments, when each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process, the method further includes any one of the following:

[0161] The terminal divides the target PXSCH into at least one PXSCH group based on a second number and a PXSCH order of the target PXSCH, where the second number is the number of PXSCHs included in a single PXSCH group, and the second number is predefined by a protocol or configured by a network or indicated by the DCI;

[0162] The terminal divides the target PXSCH into at least one PXSCH group based on whether a predefined condition is satisfied, wherein each PXSCH in the same PXSCH group satisfies the same predefined condition;

[0163] The terminal divides the target PXSCH into at least one PXSCH group based on a predefined number of PXSCH groups and a PXSCH order of the target PXSCH;

[0164] The terminal divides the target PXSCH into at least one PXSCH group based on the PXSCH group division information indicated by the DCI;

[0165] The terminal divides the PXSCH corresponding to the same HARQ process into the same PXSCH group based on the correspondence between the target PXSCH indicated by the DCI and the HARQ process.

[0166] Here, the number of PXSCHs contained in a single PXSCH group can also be understood as the maximum number of PXSCHs contained in a single PXSCH group.

[0167] Optionally, the PXSCH group division information is located in the time domain resource allocation information indicated by the DCI; or,

[0168] The DCI includes a third indication field, and the third indication field is used to indicate the PXSCH group division information.

[0169] Optionally, the PXSCH group division information includes at least one of the following:

[0170] Information used to indicate the boundary of a PXSCH group;

[0171] Information used to indicate the number of PXSCHs contained in each PXSCH group.

[0172] That is, when HARQ process ID determination method 3 is adopted, at least one of PXSCH grouping methods 1 to 4 can be used to group multiple Scheduled / Valid PXSCHs scheduled by a single DCI:

[0173] PXSCH grouping method 1: divide the scheduled / valid PXSCH groups based on the maximum number of scheduled / valid PXSCHs contained in a single PXSCH group

[0174] For multiple Scheduled / Valid PXSCHs scheduled by a certain DCI, starting from the first Scheduled / Valid PXSCH, every X Scheduled / Valid PXSCHs are divided into a Scheduled / Valid PXSCH group until the last Scheduled / Valid PXSCH; when the number of remaining Scheduled / Valid PXSCHs is <= X, these Scheduled / Valid PXSCHs are divided into a single Scheduled / Valid PXSCH group. The order between Scheduled / Valid PXSCHs (referred to as PXSCH order) is described below. X can be specified by the protocol or configured by high-level signaling, or the DCI can directly indicate its value or indicate an index / subscript in a predefined list of X values ​​(specified by the protocol or configured by high-level signaling).

[0175] PXSCH grouping method 2: divide the scheduled / valid PXSCH groups based on the satisfaction of predefined conditions

[0176] Based on the different predefined conditions met, one or more scheduled / valid PXSCHs that meet a certain predefined condition or a combination of predefined conditions are divided into the same scheduled / valid PXSCH group. The predefined conditions are described in the corresponding section above.

[0177] For example, when the predefined condition is "SCS is Y", assuming that among the three PXSCHs scheduled by a DCI, the SCS corresponding to PXSCH1 and PXSCH2 is 15kHz, and the SCS corresponding to PXSCH3 is 30kHz, then PXSCH1 and PXSCH2 can be classified as PXSCH group 1 (corresponding to the predefined condition: SCS is 15kHz), and PXSCH3 can be classified as PXSCH group 2 (corresponding to the predefined condition: SCS is 30kHz).

[0178] For another example, when the predefined condition is "located in Slot n", assuming that among the three PXSCHs scheduled by a DCI, PXSCH1 is located in Slot 1, and PXSCH2 and PXSCH3 are located in Slot 2, then PXSCH1 can be classified as PXSCH group 1 (corresponding to the predefined condition: located in Slot 1), and PXSCH2 and PXSCH3 can be classified as PXSCH group 2 (corresponding to the predefined condition: located in Slot 2).

[0179] Other predefined conditions include "MCS is Z", "actual scheduling of 1 TB", "actual scheduling of 2 TB", etc., which are not listed here one by one.

[0180] When determining the order between the scheduled / valid PXSCH groups obtained by the division, one of the following methods can be used:

[0181] Based on the attributes of the first / last / designated Scheduled / Valid PXSCH in each Scheduled / Valid PXSCH group, the order between these Scheduled / Valid PXSCH groups is determined by following the "order between multiple Scheduled / Valid PXSCHs scheduled by a single DCI" determination rule (this determination rule can also be used to select the first / last / designated Scheduled / Valid PXSCH within a certain Scheduled / Valid PXSCH group).

[0182] The order of these scheduled / valid PXSCH groups is determined based on the ascending / descending order of the values ​​corresponding to the predefined conditions or predefined condition combinations used for grouping. For example, when two scheduled / valid PXSCH groups correspond to the predefined conditions "SCS is 15 kHz" and "SCS is 30 kHz," respectively, the scheduled / valid PXSCH group corresponding to the predefined condition "SCS is 15 kHz" can be sorted before the scheduled / valid PXSCH group corresponding to the predefined condition "SCS is 30 kHz" in ascending order of SCS values. When grouping based on a combination of predefined conditions, the order of the scheduled / valid PXSCH groups can be determined using only a single or partial predefined condition in the combination, or all predefined conditions. When multiple predefined conditions are involved, each of these predefined conditions can be used sequentially in a predefined order; the predefined order here can be the traversal order of all possible predefined conditions that are uniformly specified or configured, or the order in which the predefined conditions appear in the combination.

[0183] PXSCH grouping mode 3: Scheduled / Valid PXSCH group division information indicated by DCI

[0184] PXSCH grouping mode 3 can adopt any of PXSCH grouping modes 3-1 to 3-3:

[0185] PXSCH grouping mode 3-1: There is Scheduled / Valid PXSCH group division information in the predefined time domain resource allocation information. DCI indicates the time domain resource allocation information and also indicates the corresponding Scheduled / Valid PXSCH group division.

[0186] For example, when a joint coding method is adopted and the same indication field / indication bit is used to simultaneously indicate the time domain resource allocation information corresponding to each scheduled PXSCH, there is Scheduled / Valid PXSCH group division information in each pre-defined or configured time domain resource allocation combination. Based on this information, the group division of the Scheduled / Valid PXSCH corresponding to this time domain resource allocation combination can be determined.

[0187] PXSCH grouping mode 3-2: Indicate the HARQ process corresponding to each Scheduled / Valid PXSCH in the DCI. At least one Scheduled / Valid PXSCH corresponding to the same HARQ process is grouped into the same Scheduled / Valid PXSCH group and uses this HARQ process.

[0188] The method of indicating the HARQ process corresponding to each Scheduled / Valid PXSCH in the DCI may follow the HARQ process ID determination method 2-1-1 or the HARQ process ID determination method 2-1-2.

[0189] PXSCH grouping mode 3-3: Independently indicate Scheduled / Valid PXSCH group division information in DCI

[0190] A new indication field may be introduced, or the reserved indication field / padding bit in the existing indication field / DCI may be redefined. For the indicated Scheduled / Valid PXSCH group division information, the PXSCH grouping mode 3-3 may be any one of the PXSCH grouping modes 3-3-1 to 3-3-2:

[0191] PXSCH grouping method 3-3-1: indicating the boundaries of adjacent scheduled / valid PXSCH groups in DCI

[0192] Assuming that each Scheduled / Valid PXSCH group corresponds to a Scheduled / Valid PXSCH with a consecutive number / index (for the determination of the order between Scheduled / Valid PXSCHs, please refer to the description below. Based on the determined order, the number / index corresponding to each Scheduled / Valid PXSCH can be determined), the number / index of the first / last Scheduled / Valid PXSCH in each Scheduled / Valid PXSCH group can be indicated in sequence (for example, in order of the Scheduled / Valid PXSCH group number / index from small to large). Optionally, the information of the last Scheduled / Valid PXSCH group can be omitted and derived based on all Scheduled / Valid PXSCHs scheduled by this DCI, as well as the indication information of other previous Scheduled / Valid PXSCH groups.

[0193] When actually indicating, the DCI may directly indicate the above information, or indicate the subscript / index of the above information in a pre-configured information list (specified by the protocol or configured by higher layer signaling).

[0194] PXSCH grouping method 3-3-2: Indicate the number of scheduled / valid PXSCHs contained in each scheduled / valid PXSCH group in the DCI

[0195] Assuming that each Scheduled / Valid PXSCH group corresponds to a Scheduled / Valid PXSCH with a consecutive number / index, the number of Scheduled / Valid PXSCHs corresponding to each Scheduled / Valid PXSCH group can be indicated in sequence (for example, in ascending order of the Scheduled / Valid PXSCH group number / index). Optionally, the information of the last Scheduled / Valid PXSCH group can be omitted and derived based on all Scheduled / Valid PXSCHs scheduled by this DCI, as well as the indication information of other previous Scheduled / Valid PXSCH groups.

[0196] When actually indicating, the DCI may directly indicate the above information, or indicate the subscript / index of the above information in a pre-configured information list (specified by the protocol or configured by higher layer signaling).

[0197] PXSCH grouping method 4: Divide scheduled / valid PXSCH groups based on the number of scheduled / valid PXSCH groups

[0198] It is assumed here that the number of scheduled / valid PXSCH groups is known, for example, specified by the protocol, configured by higher-layer signaling, or explicitly indicated by the DCI. In this case, all scheduled / valid PXSCHs scheduled by a single DCI can be evenly (or as evenly as possible) divided into S scheduled / valid PXSCH groups. For example, assuming a DCI schedules K scheduled / valid PXSCHs, then for the first S1 = K mod S scheduled / valid PXSCH groups, each scheduled / valid PXSCH group contains ceiling (K / S) PDSCHs, and for the next S2 = S–S1 scheduled / valid PXSCH groups, each scheduled / valid PXSCH group contains floor (K / S) scheduled / valid PXSCHs (or, the first S2 groups each contain floor (K / S) and the next N1 groups each contain ceiling (K / S)). Ceiling() indicates rounding up and floor() indicates rounding down. When K is divisible by S, for the S scheduled / valid PXSCH groups, each scheduled / valid PXSCH group contains K / S scheduled / valid PXSCHs. Here, K>0 and S>0 are required.

[0199] Generally, when determining the scheduled / valid PXSCH group division information corresponding to multiple scheduled / valid PXSCHs scheduled by a single DCI, the scheduled / valid PXSCHs contained in each scheduled / valid PXSCH group and the order between the scheduled / valid PXSCH groups are also determined.

[0200] To determine the HARQ process corresponding to each Scheduled / Valid PXSCH group, the corresponding description in HARQ process ID determination method 2 can be used.

[0201] For the operations corresponding to a certain Scheduled / Valid PXSCH group, including the conditions that need to be met, TB transmission and reception processing, etc., the corresponding operations when using HARQ process ID determination method 1 can be used.

[0202] The determination of the HARQ process ID and the order of the Scheduled / Valid PXSCH groups mentioned above all involve the order of the Scheduled / Valid PXSCHs. The following describes how to determine the order of multiple Scheduled / Valid PXSCHs scheduled by a single DCI (PXSCH order for short).

[0203] In some embodiments, the PXSCH order of the target PXSCH is determined based on at least one of the following:

[0204] Resource allocation information of each PXSCH in the target PXSCH, the resource allocation information including at least one of frequency domain resource allocation information and time domain resource allocation information;

[0205] The BWP sequence corresponding to each PXSCH in the target PXSCH;

[0206] The starting time of each PXSCH in the target PXSCH;

[0207] The end time of each PXSCH in the target PXSCH;

[0208] The frequency of the frequency domain resources of each PXSCH in the target PXSCH;

[0209] The HARQ process occupied by each PXSCH in the target PXSCH;

[0210] The effective code rate of each PXSCH in the target PXSCH.

[0211] Specifically, the order between multiple Scheduled / Valid PXSCHs scheduled by a single DCI may be determined based on at least one of the following:

[0212] The order of Scheduled / Valid PXSCHs determined in the frequency domain resource allocation and / or time domain resource allocation. For example, when independent indicator fields / indicator bits in the DCI are used to indicate the frequency domain resource allocation information or time domain resource allocation information corresponding to each Scheduled PXSCH, the order of the corresponding Scheduled / Valid PXSCHs can be determined based on the order of the indicator fields / indicator bits; when a joint coding method is adopted and the same indicator field / indicator bit in the DCI is used to simultaneously indicate the frequency domain resource allocation information or time domain resource allocation information corresponding to each Scheduled PXSCH, the order of the corresponding Scheduled / Valid PXSCHs can be determined based on the order of the allocation information in the frequency domain resource allocation combination or time domain resource allocation combination indicated in the DCI.

[0213] Based on the order of the BWPs corresponding to the Scheduled / Valid PXSCHs (see the corresponding description below for details), it is assumed that at least one Scheduled / Valid PXSCH corresponds to a different BWP than the remaining Scheduled / Valid PXSCHs.

[0214] Arrange in ascending / descending order based on the start / end time of Scheduled / Valid PXSCH.

[0215] Arrange in ascending / descending order based on the frequency of the first / last / specified RB / RE occupied by Scheduled / Valid PXSCH, or the lowest / highest frequency corresponding to the occupied frequency domain resources.

[0216] Arrange the HARQ processes in ascending / descending order based on the Scheduled / Valid PXSCH occupied.

[0217] Arrange in ascending / descending order based on the effective bit rate of Scheduled / Valid PXSCH.

[0218] In some embodiments, the BWP order is determined based on at least one of the following:

[0219] BWP logo;

[0220] The frequency of the frequency domain resource to which the BWP is configured;

[0221] The order of each BWP in the predefined BWP subset;

[0222] The DCI indicates the order of BWPs.

[0223] Specifically, the order between BWPs can be determined based on at least one of the following:

[0224] Sort in ascending / descending order based on the BWP index / ID corresponding to the BWP.

[0225] Arrange in ascending / descending order based on the lowest / highest frequency corresponding to the frequency domain resources configured for the BWP; for example, arrange in ascending / descending order based on the position of the lowest / highest frequency PRBs configured for the BWP in the CRB grid of the serving cell.

[0226] When all BWPs to be sorted are in the same predefined BWP subset, the order of the BWPs contained in the predefined BWP subset is determined.

[0227] When all BWPs to be sorted are directly indicated by the same DCI, the order is based on the indication order in the DCI.

[0228] In the embodiment of the present application, after determining the HARQ process corresponding to the target PXSCH, the terminal also needs to perform operations related to HARQ-ACK feedback. The following describes the implementation methods related to the HARQ-ACK feedback operation.

[0229] In order to avoid introducing additional complexity, it is assumed that all scheduled / valid PDSCHs scheduled by a single DCI feed back corresponding HARQ-ACK in the same HARQ-ACK codebook.

[0230] The HARQ-ACK feedback operation is related to the HARQ process ID determination method. The following describes the HARQ process ID determination methods separately.

[0231] In some embodiments, the method further comprises:

[0232] When the target PXSCH corresponds to the same HARQ process, the target reference point of the HARQ-ACK feedback timing is determined based on the reference PDSCH (Reference PDSCH), and the target reference point is the reference point for applying the feedback time offset.

[0233] Here, the reference point for applying the feedback time offset is the starting moment when applying the feedback time offset when determining the PUCCH slot where the HARQ-ACK codebook transmission corresponding to the HARQ-ACK feedback of the PDSCH is located. The starting moment here and the granularity of the feedback time offset are both PUCCH slots. The feedback time offset here can be, for example, K1 or k indicated by the scheduling DCI, or K1 or k indicated by the activation DCI, or K1 or k configured by high-level parameters. The reference point of the feedback time offset can also be called the K1 reference point (or k reference point), for example, it can be the PUCCH slot corresponding to K1=0 or k=0. Based on the determined K1 reference point (or k reference point) and further applying the feedback time offset, the PUCCH slot where the HARQ-ACK codebook transmission corresponding to the HARQ-ACK feedback of the PDSCH is located can be determined. For example, after determining that the K1 reference point is the PUCCH slot corresponding to K1=0 (or determining that the k reference point is the PUCCH slot corresponding to k=0), starting from this PUCCH slot, the number of PUCCH slots corresponding to the feedback time offset (K1 or k) is offset backward on the time axis to obtain the PUCCH slot where the HARQ-ACK codebook transmission corresponding to the HARQ-ACK feedback of the PDSCH is located.

[0234] Optionally, the reference PDSCH includes at least one of the following:

[0235] The first PDSCH among the PDSCHs scheduled by the DCI;

[0236] The last PDSCH in the PDSCH scheduled by the DCI;

[0237] A designated PDSCH in the PDSCH scheduled by the DCI;

[0238] The first PDSCH among the PDSCHs corresponding to the second BWP;

[0239] The last PDSCH in the PDSCH corresponding to the second BWP;

[0240] a designated PDSCH among the PDSCHs corresponding to the second BWP;

[0241] The first PDSCH in the PDSCH corresponding to the first SCS;

[0242] The last PDSCH in the PDSCH corresponding to the first SCS;

[0243] A designated PDSCH in the PDSCH corresponding to the first SCS;

[0244] Wherein, the second BWP is a predefined BWP;

[0245] The first SCS is a predefined SCS.

[0246] That is to say, for HARQ process ID determination method 1, the target reference point involved in the HARQ-ACK feedback timing (including the PUCCH slot corresponding to K1=0) can be determined based on the Reference PDSCH. For example, the last PUCCH slot overlapping with the DL slot where the Reference PDSCH is located, or the PUCCH slot overlapping with the end time of the Reference PDSCH, is used as the PUCCH slot corresponding to K1=0 or k=0. The Reference PDSCH here can be any one of Reference PDSCH determination method 1 to Reference PDSCH determination method 2:

[0247] Reference PDSCH determination method 1: the first / last / specified scheduled / valid PDSCH among multiple scheduled / valid PDSCHs scheduled by DCI

[0248] The order of Scheduled / Valid PXSCHs is determined as described above and will not be repeated here. For example, the Reference PDSCH is the Scheduled PDSCH with the latest end time among the Scheduled PDSCHs scheduled by the DCI.

[0249] Reference PDSCH determination method 2: Among multiple scheduled / valid PDSCHs scheduled by DCI, the first / last / specified scheduled / valid PDSCH corresponding to the predefined BWP / SCS

[0250] The predefined BWP / SCS can be determined based on predefined rules. For example, the predefined BWP is the BWP with the minimum / maximum / specified index / ID among the BWPs corresponding to each Scheduled / Valid PDSCH scheduled by the DCI, or the predefined SCS is the minimum / maximum / specified SCS among the SCSs corresponding to each Scheduled / Valid PDSCH scheduled by the DCI. For example, the Reference PDSCH is the Scheduled PDSCH with the latest end time among the Scheduled PDSCHs corresponding to the minimum SCS scheduled by the DCI.

[0251] In some embodiments, the method further comprises:

[0252] When each PXSCH in the target PXSCH corresponds to a different HARQ process, or when each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process, based on the type of the HARQ-ACK codebook, perform HARQ-ACK feedback related operations;

[0253] In which case, when the type of the HARQ-ACK codebook is type 1 (i.e., Type-1 codebook), the performing of HARQ-ACK feedback-related operations includes:

[0254] determining a target HARQ-ACK bit sequence in the HARQ-ACK codebook, where the target HARQ-ACK bit sequence is a HARQ-ACK bit sequence corresponding to the target serving cell; or

[0255] When the HARQ-ACK codebook type is Type 2 (i.e., Type-2 codebook), performing HARQ-ACK feedback-related operations includes:

[0256] Determine a mapping relationship between HARQ-ACK feedback and two HARQ-ACK subcodebooks included in the HARQ-ACK codebook, where the two HARQ-ACK subcodebooks include a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook; or,

[0257] When the HARQ-ACK codebook type is Type 3 (i.e., Type-3 codebook), performing HARQ-ACK feedback-related operations includes:

[0258] Determine the number of codewords for each HARQ process of the target serving cell;

[0259] Among them, the target service cell is the service cell where the target PXSCH is located.

[0260] In some embodiments, when the type of the HARQ-ACK codebook is type 1, determining the target HARQ-ACK bit sequence in the HARQ-ACK codebook includes:

[0261] Determine, based on a time domain resource allocation TDRA table corresponding to the i-th BWP of the target serving cell, a timing set corresponding to the i-th BWP; wherein i ranges from 1 to M, and M is the number of BWPs configured in the target serving cell;

[0262] Constructing a HARQ-ACK bit sequence corresponding to the i-th BWP based on the opportunity set corresponding to the i-th BWP;

[0263] Perform end-to-end concatenation of the HARQ-ACK bit sequences corresponding to the M BWPs of the target serving cell based on a predefined order to obtain a target HARQ-ACK bit sequence in the HARQ-ACK codebook;

[0264] or,

[0265] The HARQ-ACK feedback corresponding to the first PXSCH group is included in the HARQ-ACK bit sequence corresponding to the first BWP, where the first PXSCH group is a PXSCH group corresponding to at least two BWPs, and the first BWP is the BWP corresponding to the reference PDSCH in the first PXSCH group.

[0266] Here, the first BWP belongs to one of the BWPs configured in the target serving cell.

[0267] In some embodiments, when the type of the HARQ-ACK codebook is type 2, determining a mapping relationship between the HARQ-ACK feedback and two HARQ-ACK subcodebooks included in the HARQ-ACK codebook includes at least one of the following:

[0268] When the HARQ-ACK feedback is the first HARQ-ACK feedback, determine the first HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the first HARQ-ACK feedback;

[0269] When the HARQ-ACK feedback is the second HARQ-ACK feedback, determining the second HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the second HARQ-ACK feedback;

[0270] When the HARQ-ACK feedback is the third HARQ-ACK feedback, determine the first HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the third HARQ-ACK feedback;

[0271] When the HARQ-ACK feedback is the fourth HARQ-ACK feedback, determine the second HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the fourth HARQ-ACK feedback;

[0272] The first HARQ-ACK feedback includes any one of the following: HARQ-ACK feedback when the DCI schedules a single PDSCH; HARQ-ACK feedback when the DCI does not schedule a PDSCH; SPS HARQ-ACK feedback;

[0273] The second HARQ-ACK feedback includes: HARQ-ACK feedback when the DCI schedules multiple PDSCHs;

[0274] The third HARQ-ACK feedback includes any one of the following: HARQ-ACK feedback when the DCI schedules a single PDSCH group; HARQ-ACK feedback when the DCI does not schedule PDSCH; SPS HARQ-ACK feedback;

[0275] The fourth HARQ-ACK feedback includes: HARQ-ACK feedback when the DCI schedules multiple PDSCH groups.

[0276] In some embodiments, when the type of the HARQ-ACK codebook is type 3, determining the number of codewords for each HARQ process of the target serving cell includes any one of the following:

[0277] uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as a single codeword, or uniformly determining the number of codewords as a double codeword;

[0278] The number of codewords corresponding to the first HARQ process in the HARQ process configured for the target serving cell is determined as a single codeword, and the number of codewords corresponding to the second HARQ process in the HARQ process configured for the target serving cell is determined as a double codeword.

[0279] It should be noted that this implementation method is applicable not only to the case where each PXSCH in the target PXSCH corresponds to a different HARQ process, but also to the case where each PXSCH group in the target PXSCH corresponds to a different HARQ process. For the case where each PXSCH group in the target PXSCH corresponds to a different HARQ process, the number of codewords corresponding to the HARQ process of each PXSCH group can be uniformly determined as a single codeword, or uniformly determined as a double codeword; or, the number of codewords corresponding to the HARQ process of some PXSCH groups can be determined as a single codeword, and the number of codewords corresponding to the HARQ process of some PXSCH groups can be determined as a double codeword.

[0280] Optionally, the uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as a single codeword, or uniformly determining the number of codewords as a double codeword, includes at least one of the following:

[0281] In a case where at least one of the BWPs configured for the target serving cell supports dual codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as dual codewords;

[0282] In a case where none of the BWPs configured for the target serving cell supports dual-codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as a single codeword;

[0283] In a case where at least one BWP in the BWP combination that can be scheduled by the DCI supports dual codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as dual codewords;

[0284] In a case where all BWPs in the BWP combination that can be scheduled by the DCI do not support dual-codeword transmission, the number of codewords corresponding to all HARQ processes configured in the target serving cell is uniformly determined to be a single codeword.

[0285] Here, for the BWP combinations that can be scheduled by the DCI, it can be understood that any BWP included in these BWP combinations that can be scheduled is a BWP configured for the target serving cell.

[0286] Optionally, when a second physical shared channel group in the target physical shared channel corresponds to at least two BWPs, and a reference BWP in the at least two BWPs only supports single codeword transmission, the second physical shared channel group can use the first HARQ process;

[0287] or,

[0288] When a third physical shared channel group in the target physical shared channel corresponds to at least two BWPs and a reference BWP in the at least two BWPs only supports single codeword transmission, the third physical shared channel group can use the second HARQ process;

[0289] or,

[0290] When a fourth physical shared channel group in the target physical shared channel corresponds to at least two BWPs and a reference BWP in the at least two BWPs supports dual codeword transmission, the fourth physical shared channel group can use the second HARQ process.

[0291] Optionally, the reference BWP includes at least one of the following:

[0292] The BWP corresponding to the reference PDSCH in the PXSCH group;

[0293] Among the BWPs corresponding to the PXSCHs contained in the PXSCH group, the BWP that supports the least number of codewords;

[0294] Among the BWPs corresponding to the PXSCHs contained in the PXSCH group, the BWP that supports the largest number of codewords.

[0295] The HARQ-ACK feedback operations of HARQ process ID determination method 2 and HARQ process ID determination method 3 are described below respectively.

[0296] 1. Method 2 for determining HARQ process ID

[0297] As described above, multiple PXSCHs scheduled by a single DCI may be located on more than one BWP. Furthermore, different BWPs may have different channel quality, configuration parameters, and other parameters. For example, if the parameter PDSCH-Config->maxNrofCodeWordsScheduledByDCI is configured differently for different BWPs, the number of TBs actually carried by each PDSCH may differ.

[0298] For different HARQ-ACK codebook types, corresponding enhancements / extensions can be introduced respectively.

[0299] 1. For Type-1 codebook

[0300] For a certain Serving cell, for each BWP configured for the current Serving cell (or each BWP in the BWP combination that can be scheduled by DCI), the Occasion set is determined based on its corresponding TDRA table and the corresponding HARQ-ACK bit sequence is constructed; then, the HARQ-ACK bit sequences corresponding to each BWP involved in this Serving cell can be concatenated head to tail based on the BWP index / ID in ascending / descending order to form the HARQ-ACK bit sequence corresponding to this Serving cell in the Type-1 codebook.

[0301] The above operation determines the corresponding Occasion set for each BWP configured by this Serving cell (or each BWP in the BWP combination that can be scheduled by DCI) based on its corresponding TDRA table, and does not take into account the scenario in which PDSCH is transmitted in parallel within this BWP and corresponds to different HARQ processes. If this scenario is considered, the operation of determining the HARQ-ACK bit sequence corresponding to this BWP needs to be further enhanced, for example, determining Occasion based on Reference PDSCH (using the Occasion determination mechanism of the related technology), but extending the number of HARQ-ACK bits corresponding to each Occasion to support HARQ-ACK feedback corresponding to multiple PDSCH / HARQ processes transmitted in parallel, for example, each Occasion corresponds to A HARQ-ACK bits in the HARQ-ACK codebook, where A is the maximum number of PDSCH / HARQ processes that can be transmitted in parallel within this BWP.

[0302] 2. For Type-2 codebook

[0303] Two HARQ-ACK subcodebooks can be introduced: the first HARQ-ACK subcodebook is used for HARQ-ACK feedback of a single DCI scheduling only a single Scheduled / Valid PDSCH, as well as HARQ-ACK feedback of DCI that does not schedule PDSCH, SPS HARQ-ACK feedback, etc.; the second HARQ-ACK subcodebook is used for HARQ-ACK feedback of a single DCI scheduling multiple Scheduled / Valid PDSCHs.

[0304] 3. For Type-3 codebook

[0305] When a serving cell can have multiple active BWPs at the same time, the parameter PDSCH-Config->maxNrofCodeWordsScheduledByDCI configured for each of these BWPs may be different, and single codeword or dual codeword transmission needs to be supported accordingly.

[0306] The number of codewords supported by each HARQ process of this serving cell during data transmission and reception, and / or the number of codewords corresponding to the HARQ-ACK reported by each HARQ process when reporting the Type-3 codebook, can be determined in one of the following ways:

[0307] Codeword number determination method 1: The codeword number corresponding to all HARQ processes configured in this serving cell is uniformly determined as single codeword or double codeword

[0308] When at least one of the following (a) and (b) is met, it is uniformly determined as a double codeword; otherwise, it is uniformly determined as a single codeword:

[0309] (a) At least one of the BWPs configured for this serving cell has dual codewords enabled (for example, when the parameter PDSCH-Config->maxNrofCodeWordsScheduledByDCI configured for a BWP is n2, it is determined that the downlink physical shared channel of this BWP has dual codewords enabled; when the parameter PDSCH-Config->maxNrofCodeWordsScheduledByDCI configured for a BWP is n1, it is determined that the downlink physical shared channel of this BWP does not have dual codewords enabled);

[0310] (b) Among the BWP combinations that can be scheduled by DCI, at least one BWP has dual codewords enabled.

[0311] In (a) and (b), a BWP "turns on dual codewords", which can be understood as that this BWP is specified or configured to turn on dual codewords, or supports dual codeword transmission; when a BWP is not specified or configured to turn on dual codewords, or does not support dual codeword transmission, it can also be understood or replaced as supporting only single codeword transmission (that is, this BWP only supports single codeword transmission); the same description can be understood in the same way, and to avoid repetition, it will not be repeated.

[0312] For (b), it is assumed that this serving cell is only configured with / supports scheduling based on a BWP combination, or that scheduling for any configured BWP is not considered.

[0313] Codeword number determination method 2: In the HARQ process configured by this serving cell, the codeword number corresponding to some HARQ processes is determined to be single codeword, and the codeword number corresponding to other HARQ processes is determined to be double codeword.

[0314] The HARQ process subset corresponding to a single codeword and / or corresponding to a double codeword may be specified by the protocol or configured by high-level signaling. When specifying / configuring the HARQ process subset corresponding to a single codeword or corresponding to a double codeword, it may be based on a Bitmap method, for example, each bit in the Bitmap corresponds one-to-one to each HARQ process configured for this Serving cell, and when a certain bit takes a predefined value (for example, the bit takes a value of 1), it indicates that the HARQ process corresponding to this bit belongs to the HARQ process subset corresponding to the single codeword or corresponding to the double codeword. Alternatively, the starting HARQ process ID and the number of HARQ process IDs corresponding to the HARQ process subset corresponding to the single codeword or corresponding to the double codeword are specified / configured, and at this time, each HARQ process subset contains HARQ processes with consecutive IDs (or, before the HARQ process ID is modulo the number of HARQ processes configured for this Serving cell, the IDs are consecutive).

[0315] When only a subset of HARQ processes corresponding to a single codeword (or corresponding to a dual codeword) is specified / configured, the remaining HARQ processes (if any) in the HARQ processes configured by this serving cell except this subset of HARQ processes can be considered to correspond to a dual codeword (or corresponding to a single codeword).

[0316] Optionally, only when at least one BWP in the BWP configured by this Serving cell is configured to enable dual codewords (or at least one BWP in the BWP combination that can be scheduled by DCI has dual codewords enabled), there is a HARQ process subset corresponding to the dual codeword (or, the HARQ process subset corresponding to the dual codeword is effective).

[0317] Optionally, only when at least one of the BWPs configured by this Serving cell is not configured to enable dual codewords (or at least one of the BWPs in the BWP combination that can be scheduled by DCI does not enable dual codewords), there is a HARQ process subset corresponding to a single codeword (or, the HARQ process subset corresponding to a single codeword is effective).

[0318] Optionally, a BWP that only supports single-codeword transmission only uses a HARQ process corresponding to the single codeword; a BWP that supports dual-codeword transmission only uses a HARQ process corresponding to the dual codeword.

[0319] Optionally, a BWP that only supports single-codeword transmission can also use the HARQ process corresponding to the dual-codeword, but a BWP that supports dual-codeword transmission cannot use the HARQ process corresponding to the single-codeword (or, it is allowed to use, but it is required that only a single codeword is actually scheduled, or only the scheduling corresponding to the predefined codeword is actually effective).

[0320] 2. Method 3 for determining HARQ process ID

[0321] Generally speaking, the description of HARQ process ID determination method 2 can be followed. In some scenarios, the following processing can be further considered:

[0322] 1. For Type-1 codebook

[0323] When a Scheduled / Valid PXSCH group contains Scheduled / Valid PXSCH corresponding to more than one BWP, the HARQ-ACK corresponding to this Scheduled / Valid PXSCH group can be included in the HARQ-ACK bit sequence corresponding to the BWP corresponding to the Reference PDSCH (for its determination, see the corresponding description in the previous text) and fed back.

[0324] 2. For Type-2 codebook

[0325] When determining the mapping relationship between the scheduling situation and the HARQ-ACK subcodebook, "Scheduled / Valid PDSCH" can be replaced with "Scheduled / Valid PXSCH group", that is, the first HARQ-ACK subcodebook is used for HARQ-ACK feedback of a single DCI scheduling only a single Scheduled / Valid PDSCH group, as well as HARQ-ACK feedback of DCI that does not schedule PDSCH, SPS HARQ-ACK feedback, etc.; the second HARQ-ACK subcodebook is used for HARQ-ACK feedback of multiple Scheduled / Valid PDSCH groups scheduled by a single DCI.

[0326] 3. For Type-3 codebook

[0327] When using Codeword Determination Method 2, when a Scheduled / Valid PXSCH group contains Scheduled / Valid PXSCHs corresponding to more than one BWP, some provisions may be applied based on the single / double codeword configuration of the Reference BWP, including:

[0328] Optionally, the Scheduled / Valid PXSCH group corresponding to the Reference BWP that only supports single codeword transmission only uses the HARQ process corresponding to the single codeword; the Scheduled / Valid PXSCH group corresponding to the Reference BWP that supports dual codeword transmission only uses the HARQ process corresponding to the dual codeword.

[0329] Optionally, the Scheduled / Valid PXSCH group corresponding to the Reference BWP that only supports single codeword transmission can also use the HARQ process corresponding to the dual codeword, but the Scheduled / Valid PXSCH group corresponding to the Reference BWP that supports dual codeword transmission cannot use the HARQ process corresponding to the single codeword (or, it is allowed to be used, but it is required that only a single codeword is actually scheduled, or only the scheduling corresponding to the predefined codeword is actually effective).

[0330] The Reference BWP here can be one of the following (a) and (b):

[0331] (a) The BWP corresponding to the Reference PDSCH in this Scheduled / Valid PXSCH group (for its determination, see the corresponding description above);

[0332] (b) Among the BWPs corresponding to the Scheduled / Valid PXSCHs contained in this Scheduled / Valid PXSCH group, the BWP that supports the least / most codewords.

[0333] For the above (b), when there are multiple BWPs that support the least / most codewords, you can select any one of them, or select the BWP with the smallest / largest index / ID.

[0334] In summary, the embodiments of the present application provide a specific and feasible solution for scheduling multiple shared channels that may (or are allowed to) be transmitted in parallel in a given transmission direction within the same serving cell for a single DCI, in key aspects such as HARQ process occupancy and HARQ-ACK feedback. The embodiments of the present application can not only improve the flexibility of physical shared channel scheduling, but also reduce the scheduling overhead of physical shared channels. In addition, these N physical shared channels occupy one or more HARQ processes, which can reduce the HARQ process occupancy overhead and HARQ-ACK feedback overhead.

[0335] The above is an embodiment of the method on the terminal side. The following describes an embodiment of the method on the network side.

[0336] FIG5 shows a flow chart of a channel scheduling method provided by an embodiment of the present application. As shown in FIG5 , the channel scheduling method includes the following steps:

[0337] Step 501: The network side device sends DCI to the terminal, where the DCI is used to schedule N PXSCHs, where the N PXSCHs are all PUSCHs, or where the N PXSCHs are all PDSCHs, and N is an integer greater than 1; the DCI is used to determine the HARQ process corresponding to the target PXSCH, where the target PXSCH is the N PXSCHs, or where the target PXSCH is a valid PXSCH among the N PXSCHs.

[0338] Optionally, the correspondence between the target PXSCH and the HARQ process includes any one of the following:

[0339] The target PXSCH corresponds to the same HARQ process;

[0340] Each PXSCH in the target PXSCH corresponds to a different HARQ process;

[0341] Each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process.

[0342] Optionally, in the case where multiple PXSCHs correspond to the same HARQ process, the multiple PXSCHs meet a predefined condition; the multiple PXSCHs are the target PXSCHs, or the multiple PXSCHs are PXSCHs located in the same PXSCH group;

[0343] The predefined conditions include at least one of the following:

[0344] Each PXSCH in the plurality of PXSCHs corresponds to the same activated bandwidth part BWP;

[0345] Each of the multiple PXSCHs corresponds to a different activated BWP;

[0346] The subcarrier spacing SCS corresponding to each PXSCH in the multiple PXSCHs is the same;

[0347] The cyclic prefix CP corresponding to each PXSCH in the multiple PXSCHs is the same;

[0348] The time domain resource corresponding to each PXSCH in the multiple PXSCHs meets the first preset condition;

[0349] The number of PRBs occupied by each of the multiple PXSCHs is less than or equal to a first preset threshold;

[0350] The total number of PRBs occupied by the multiple PXSCHs is less than or equal to a second preset threshold;

[0351] The transport block size TBS of the multiple PXSCHs is less than or equal to a third preset threshold;

[0352] The difference in channel quality of the multiple PXSCHs is less than or equal to a fourth preset threshold;

[0353] The number of layers of each PXSCH mapping in the multiple PXSCHs is equal;

[0354] The maximum number of transport blocks TB supported by each PXSCH in the multiple PXSCHs is equal;

[0355] The number of TBs actually scheduled by each PXSCH in the multiple PXSCHs is equal.

[0356] Optionally, the first preset condition includes at least one of the following:

[0357] The duration of time domain resources overlaps;

[0358] The interval between the start times of the time domain resources is less than or equal to a fifth preset threshold;

[0359] The interval between the end times of the time domain resources is less than or equal to a sixth preset threshold;

[0360] The time domain resources are located in the same time domain unit.

[0361] Optionally, when each PXSCH in the target PXSCH corresponds to a different HARQ process, the DCI includes any one of the following:

[0362] First information, where the first information is used to indicate the HARQ process corresponding to each PXSCH in the target PXSCH;

[0363] Second information, the second information is used to indicate that the first HARQ process identifier corresponds to the first PXSCH in the target PXSCH.

[0364] Optionally, the first information indicates the HARQ processes corresponding to each PXSCH in the target PXSCH in sequence based on the PXSCH order of the target PXSCH.

[0365] Optionally, the first information includes at least one of the following:

[0366] X first indication fields, where the X first indication fields are used to respectively indicate the HARQ processes corresponding to the respective PXSCHs in the target PXSCH;

[0367] A second indication field, where the second indication field is used to jointly indicate the HARQ processes corresponding to each PXSCH in the target PXSCH;

[0368] A first bitmap, wherein X bits in the first bitmap are set to predetermined values ​​and are used to respectively indicate the HARQ processes corresponding to each PXSCH in the target PXSCH;

[0369] Here, the value of X is equal to the number of PXSCHs included in the target PXSCH.

[0370] Optionally, when each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process, the DCI further includes any one of the following:

[0371] Information used to indicate a second number, where the second number is the number of PXSCHs included in a single PXSCH group;

[0372] PXSCH group division information;

[0373] Information used to indicate the correspondence between the target PXSCH and the HARQ process.

[0374] Optionally, the PXSCH group division information is located in the time domain resource allocation information indicated by the DCI; or,

[0375] The DCI includes a third indication field, and the third indication field is used to indicate the PXSCH group division information.

[0376] Optionally, the PXSCH group division information includes at least one of the following:

[0377] Information used to indicate the boundary of a PXSCH group;

[0378] Information used to indicate the number of PXSCHs contained in each PXSCH group.

[0379] For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiment of Figure 3, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

[0380] The channel determination method provided in the embodiment of the present application may be executed by a channel determination device. In the embodiment of the present application, the channel determination device provided in the embodiment of the present application is described by taking the channel determination method executed by the channel determination device as an example.

[0381] 6, an embodiment of the present application further provides a channel determination device, which can be applied to a terminal. As shown in FIG6, the channel determination device 600 includes:

[0382] A receiving unit 601 is configured to receive downlink control information DCI from a network-side device, where the DCI is used to schedule N physical shared channels PXSCH, where the N PXSCHs are all PUSCHs, or where the N PXSCHs are all PDSCHs, where N is an integer greater than or equal to 1;

[0383] The first processing unit 602 is used to determine the hybrid automatic repeat request HARQ process corresponding to the target PXSCH based on the DCI, and the target PXSCH is the N PXSCHs, or the target PXSCH is a valid PXSCH among the N PXSCHs.

[0384] Optionally, the first processing unit 602 is specifically configured to:

[0385] Determining, based on the DCI and the correspondence between the target physical shared channel and the HARQ process, a HARQ process corresponding to the target physical shared channel;

[0386] The correspondence between the target physical shared channel and the HARQ process includes any one of the following:

[0387] The target PXSCH corresponds to the same HARQ process;

[0388] Each PXSCH in the target PXSCH corresponds to a different HARQ process;

[0389] Each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process.

[0390] Optionally, in the case where multiple PXSCHs correspond to the same HARQ process, the multiple PXSCHs meet a predefined condition; the multiple PXSCHs are the target PXSCHs, or the multiple PXSCHs are PXSCHs located in the same PXSCH group;

[0391] The predefined conditions include at least one of the following:

[0392] Each PXSCH in the plurality of PXSCHs corresponds to the same activated bandwidth part BWP;

[0393] Each of the multiple PXSCHs corresponds to a different activated BWP;

[0394] The subcarrier spacing SCS corresponding to each PXSCH in the multiple PXSCHs is the same;

[0395] The cyclic prefix CP corresponding to each PXSCH in the multiple PXSCHs is the same;

[0396] The time domain resource corresponding to each PXSCH in the multiple PXSCHs meets the first preset condition;

[0397] The number of PRBs occupied by each of the multiple PXSCHs is less than or equal to a first preset threshold;

[0398] The total number of PRBs occupied by the multiple PXSCHs is less than or equal to a second preset threshold;

[0399] The transport block size TBS of the multiple PXSCHs is less than or equal to a third preset threshold;

[0400] The difference in channel quality of the multiple PXSCHs is less than or equal to a fourth preset threshold;

[0401] The number of layers of each PXSCH mapping in the multiple PXSCHs is equal;

[0402] The maximum number of transport blocks TB supported by each PXSCH in the multiple PXSCHs is equal;

[0403] The number of TBs actually scheduled by each PXSCH in the multiple PXSCHs is equal.

[0404] Optionally, the first preset condition includes at least one of the following:

[0405] The duration of time domain resources overlaps;

[0406] The interval between the start times of the time domain resources is less than or equal to a fifth preset threshold;

[0407] The interval between the end times of the time domain resources is less than or equal to a sixth preset threshold;

[0408] The time domain resources are located in the same time domain unit.

[0409] Optionally, when each PXSCH in the target PXSCH corresponds to a different HARQ process, the first processing unit 602 is specifically used for any of the following:

[0410] Determine, according to the first information included in the DCI, the HARQ process corresponding to each PXSCH in the target PXSCH;

[0411] Determine the HARQ process corresponding to each PXSCH in the target PXSCH according to the second information included in the DCI and the first rule;

[0412] The first information is used to indicate the HARQ process corresponding to each PXSCH in the target PXSCH;

[0413] The second information is used to indicate that the first HARQ process identifier corresponds to the first PXSCH in the target PXSCH;

[0414] The first rule is predefined by a protocol, configured by a network, or indicated by the DCI.

[0415] Optionally, the first information indicates the HARQ processes corresponding to each PXSCH in the target PXSCH in sequence based on the PXSCH order of the target PXSCH.

[0416] Optionally, the first information includes at least one of the following:

[0417] X first indication fields, where the X first indication fields are used to respectively indicate the HARQ processes corresponding to the respective PXSCHs in the target PXSCH;

[0418] A second indication field, where the second indication field is used to jointly indicate the HARQ processes corresponding to each PXSCH in the target PXSCH;

[0419] A first bitmap, wherein X bits in the first bitmap are set to predetermined values ​​and are used to respectively indicate the HARQ processes corresponding to each PXSCH in the target PXSCH;

[0420] Here, the value of X is equal to the number of PXSCHs included in the target PXSCH.

[0421] Optionally, the device further comprises:

[0422] The second processing unit is configured to, when each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process, perform any of the following:

[0423] Divide the target PXSCH into at least one PXSCH group based on a second number and a PXSCH order of the target PXSCH, where the second number is the number of PXSCHs contained in a single PXSCH group, and the second number is predefined by a protocol or configured by a network or indicated by the DCI;

[0424] Based on the satisfaction of predefined conditions, the target PXSCH is divided into at least one PXSCH group, wherein each PXSCH in the same PXSCH group satisfies the same predefined conditions;

[0425] Dividing the target PXSCH into at least one PXSCH group based on a predefined number of PXSCH groups and a PXSCH order of the target PXSCH;

[0426] Based on the PXSCH group division information indicated by the DCI, the target PXSCH is divided into at least one PXSCH group;

[0427] Based on the correspondence between the target PXSCH indicated by the DCI and the HARQ process, the PXSCH corresponding to the same HARQ process is divided into the same PXSCH group.

[0428] Optionally, the PXSCH group division information is located in the time domain resource allocation information indicated by the DCI; or,

[0429] The DCI includes a third indication field, and the third indication field is used to indicate the PXSCH group division information.

[0430] Optionally, the PXSCH group division information includes at least one of the following:

[0431] Information used to indicate the boundary of a PXSCH group;

[0432] Information used to indicate the number of PXSCHs contained in each PXSCH group.

[0433] Optionally, the PXSCH order of the target PXSCH is determined based on at least one of the following:

[0434] Resource allocation information of each PXSCH in the target PXSCH, the resource allocation information including at least one of frequency domain resource allocation information and time domain resource allocation information;

[0435] The BWP sequence corresponding to each PXSCH in the target PXSCH;

[0436] The starting time of each PXSCH in the target PXSCH;

[0437] The end time of each PXSCH in the target PXSCH;

[0438] The frequency of the frequency domain resources of each PXSCH in the target PXSCH;

[0439] The HARQ process occupied by each PXSCH in the target PXSCH;

[0440] The effective code rate of each PXSCH in the target PXSCH.

[0441] Optionally, the BWP order is determined based on at least one of the following:

[0442] BWP logo;

[0443] The frequency of the frequency domain resource to which the BWP is configured;

[0444] The order of each BWP in the predefined BWP subset;

[0445] The DCI indicates the order of BWPs.

[0446] Optionally, the device further comprises:

[0447] The third processing unit is used to determine the target reference point of the HARQ-ACK feedback timing based on the reference physical downlink shared channel PDSCH when the target PXSCH corresponds to the same HARQ process, and the target reference point is the reference point for applying the feedback time offset.

[0448] Optionally, the device further comprises:

[0449] a fourth processing unit, configured to perform HARQ-ACK feedback-related operations based on the type of the HARQ-ACK codebook when each PXSCH in the target PXSCH corresponds to a different HARQ process, or when each PXSCH group in the target PXSCH corresponds to a different HARQ process and each PXSCH in the same PXSCH group corresponds to the same HARQ process;

[0450] Wherein, when the type of the HARQ-ACK codebook is type 1, the performing of HARQ-ACK feedback-related operations includes:

[0451] determining a target HARQ-ACK bit sequence in the HARQ-ACK codebook, where the target HARQ-ACK bit sequence is a HARQ-ACK bit sequence corresponding to the target serving cell; or

[0452] When the HARQ-ACK codebook type is type 2, performing HARQ-ACK feedback-related operations includes:

[0453] Determine a mapping relationship between HARQ-ACK feedback and two HARQ-ACK subcodebooks included in the HARQ-ACK codebook, where the two HARQ-ACK subcodebooks include a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook; or,

[0454] When the HARQ-ACK codebook type is type 3, performing HARQ-ACK feedback-related operations includes:

[0455] Determine the number of codewords for each HARQ process of the target serving cell;

[0456] Among them, the target service cell is the service cell where the target PXSCH is located.

[0457] Optionally, when the type of the HARQ-ACK codebook is type 1, the fourth processing unit is specifically configured to:

[0458] Determine, based on a time domain resource allocation TDRA table corresponding to the i-th BWP of the target serving cell, a timing set corresponding to the i-th BWP; wherein i ranges from 1 to M, and M is the number of BWPs configured in the target serving cell;

[0459] Constructing a HARQ-ACK bit sequence corresponding to the i-th BWP based on the opportunity set corresponding to the i-th BWP;

[0460] Perform end-to-end concatenation of the HARQ-ACK bit sequences corresponding to the M BWPs of the target serving cell based on a predefined order to obtain a target HARQ-ACK bit sequence in the HARQ-ACK codebook;

[0461] or,

[0462] The HARQ-ACK feedback corresponding to the first PXSCH group is included in the HARQ-ACK bit sequence corresponding to the first BWP, where the first PXSCH group is a PXSCH group corresponding to at least two BWPs, and the first BWP is the BWP corresponding to the reference PDSCH in the first PXSCH group.

[0463] Optionally, when the type of the HARQ-ACK codebook is type 2, the fourth processing unit is specifically used for at least one of the following:

[0464] When the HARQ-ACK feedback is the first HARQ-ACK feedback, determine the first HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the first HARQ-ACK feedback;

[0465] When the HARQ-ACK feedback is the second HARQ-ACK feedback, determining the second HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the second HARQ-ACK feedback;

[0466] When the HARQ-ACK feedback is the third HARQ-ACK feedback, determine the first HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the third HARQ-ACK feedback;

[0467] When the HARQ-ACK feedback is the fourth HARQ-ACK feedback, determine the second HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the fourth HARQ-ACK feedback;

[0468] The first HARQ-ACK feedback includes any one of the following: HARQ-ACK feedback when the DCI schedules a single PDSCH; HARQ-ACK feedback when the DCI does not schedule a PDSCH; SPS HARQ-ACK feedback;

[0469] The second HARQ-ACK feedback includes: HARQ-ACK feedback when the DCI schedules multiple PDSCHs;

[0470] The third HARQ-ACK feedback includes any one of the following: HARQ-ACK feedback when the DCI schedules a single PDSCH group; HARQ-ACK feedback when the DCI does not schedule PDSCH; SPS HARQ-ACK feedback;

[0471] The fourth HARQ-ACK feedback includes: HARQ-ACK feedback when the DCI schedules multiple PDSCH groups.

[0472] Optionally, when the type of the HARQ-ACK codebook is type 3, the fourth processing unit is specifically used for any of the following:

[0473] uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as a single codeword, or uniformly determining the number of codewords as a double codeword;

[0474] The number of codewords corresponding to the first HARQ process in the HARQ process configured for the target serving cell is determined as a single codeword, and the number of codewords corresponding to the second HARQ process in the HARQ process configured for the target serving cell is determined as a double codeword.

[0475] Optionally, the fourth processing unit is specifically configured to perform at least one of the following:

[0476] In a case where at least one of the BWPs configured for the target serving cell supports dual codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as dual codewords;

[0477] In a case where none of the BWPs configured for the target serving cell supports dual-codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as a single codeword;

[0478] In a case where at least one BWP in the BWP combination that can be scheduled by the DCI supports dual codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as dual codewords;

[0479] In a case where all BWPs in the BWP combination that can be scheduled by the DCI do not support dual-codeword transmission, the number of codewords corresponding to all HARQ processes configured in the target serving cell is uniformly determined to be a single codeword.

[0480] Optionally, when the second PXSCH group in the target PXSCH can use the first HARQ process, the second PXSCH group satisfies the following conditions:

[0481] Corresponding to at least two BWPs, and a reference BWP in the at least two BWPs only supports single codeword transmission;

[0482] or,

[0483] In a case where the third PXSCH group in the target PXSCH can use the second HARQ process, the third PXSCH group satisfies at least one of the following conditions:

[0484] Corresponding to at least two BWPs, and a reference BWP in the at least two BWPs only supports single codeword transmission;

[0485] It corresponds to at least two BWPs, and a reference BWP in the at least two BWPs supports dual-codeword transmission.

[0486] Optionally, the reference BWP includes at least one of the following:

[0487] The BWP corresponding to the reference PDSCH in the PXSCH group;

[0488] Among the BWPs corresponding to the PXSCHs contained in the PXSCH group, the BWP that supports the least number of codewords;

[0489] Among the BWPs corresponding to the PXSCHs contained in the PXSCH group, the BWP that supports the largest number of codewords.

[0490] Optionally, the reference PDSCH includes at least one of the following:

[0491] The first PDSCH among the PDSCHs scheduled by the DCI;

[0492] The last PDSCH in the PDSCH scheduled by the DCI;

[0493] A designated PDSCH in the PDSCH scheduled by the DCI;

[0494] The first PDSCH among the PDSCHs corresponding to the second BWP;

[0495] The last PDSCH in the PDSCH corresponding to the second BWP;

[0496] a designated PDSCH among the PDSCHs corresponding to the second BWP;

[0497] The first PDSCH in the PDSCH corresponding to the first SCS;

[0498] The last PDSCH in the PDSCH corresponding to the first SCS;

[0499] A designated PDSCH in the PDSCH corresponding to the first SCS;

[0500] Wherein, the second BWP is a predefined BWP;

[0501] The first SCS is a predefined SCS.

[0502] In summary, the embodiments of the present application provide a specific and feasible solution for scheduling multiple shared channels that may (or are allowed to) be transmitted in parallel in a given transmission direction within the same serving cell for a single DCI, in key aspects such as HARQ process occupancy and HARQ-ACK feedback. The embodiments of the present application can not only improve the flexibility of physical shared channel scheduling, but also reduce the scheduling overhead of physical shared channels. In addition, these N physical shared channels occupy one or more HARQ processes, which can reduce the HARQ process occupancy overhead and HARQ-ACK feedback overhead.

[0503] The channel determination device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can include servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0504] The channel determination device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0505] The channel scheduling method provided in the embodiment of the present application can be executed by a channel scheduling device. In the embodiment of the present application, the channel scheduling device provided in the embodiment of the present application is described by taking the channel scheduling method executed by the channel scheduling device as an example.

[0506] 7 , an embodiment of the present application further provides a channel scheduling device that can be applied to a network-side device. As shown in FIG7 , the channel scheduling device 700 includes:

[0507] A sending unit 701 is configured to send downlink control information DCI to a terminal, where the DCI is used to schedule N physical shared channels PXSCHs, where the N PXSCHs are all PUSCHs, or where the N PXSCHs are all PDSCHs, and N is an integer greater than 1.

[0508] The DCI is used to determine the hybrid automatic repeat request HARQ process corresponding to the target PXSCH, and the target PXSCH is the N PXSCHs, or the target PXSCH is a valid PXSCH among the N PXSCHs.

[0509] Optionally, the correspondence between the target PXSCH and the HARQ process includes any one of the following:

[0510] The target PXSCH corresponds to the same HARQ process;

[0511] Each PXSCH in the target PXSCH corresponds to a different HARQ process;

[0512] Each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process.

[0513] Optionally, in the case where multiple PXSCHs correspond to the same HARQ process, the multiple PXSCHs meet a predefined condition; the multiple PXSCHs are the target PXSCHs, or the multiple PXSCHs are PXSCHs located in the same PXSCH group;

[0514] The predefined conditions include at least one of the following:

[0515] Each PXSCH in the plurality of PXSCHs corresponds to the same activated bandwidth part BWP;

[0516] Each of the multiple PXSCHs corresponds to a different activated BWP;

[0517] The subcarrier spacing SCS corresponding to each PXSCH in the multiple PXSCHs is the same;

[0518] The cyclic prefix CP corresponding to each PXSCH in the multiple PXSCHs is the same;

[0519] The time domain resource corresponding to each PXSCH in the multiple PXSCHs meets the first preset condition;

[0520] The number of PRBs occupied by each of the multiple PXSCHs is less than or equal to a first preset threshold;

[0521] The total number of PRBs occupied by the multiple PXSCHs is less than or equal to a second preset threshold;

[0522] The transport block size TBS of the multiple PXSCHs is less than or equal to a third preset threshold;

[0523] The difference in channel quality of the multiple PXSCHs is less than or equal to a fourth preset threshold;

[0524] The number of layers of each PXSCH mapping in the multiple PXSCHs is equal;

[0525] The maximum number of transport blocks TB supported by each PXSCH in the multiple PXSCHs is equal;

[0526] The number of TBs actually scheduled by each PXSCH in the multiple PXSCHs is equal.

[0527] Optionally, the first preset condition includes at least one of the following:

[0528] The duration of time domain resources overlaps;

[0529] The interval between the start times of the time domain resources is less than or equal to a fifth preset threshold;

[0530] The interval between the end times of the time domain resources is less than or equal to a sixth preset threshold;

[0531] The time domain resources are located in the same time domain unit.

[0532] Optionally, when each PXSCH in the target PXSCH corresponds to a different HARQ process, the DCI includes any one of the following:

[0533] First information, where the first information is used to indicate the HARQ process corresponding to each PXSCH in the target PXSCH;

[0534] Second information, the second information is used to indicate that the first HARQ process identifier corresponds to the first PXSCH in the target PXSCH.

[0535] Optionally, the first information indicates the HARQ processes corresponding to each PXSCH in the target PXSCH in sequence based on the PXSCH order of the target PXSCH.

[0536] Optionally, the first information includes at least one of the following:

[0537] X first indication fields, where the X first indication fields are used to respectively indicate the HARQ processes corresponding to the respective PXSCHs in the target PXSCH;

[0538] A second indication field, where the second indication field is used to jointly indicate the HARQ processes corresponding to each PXSCH in the target PXSCH;

[0539] A first bitmap, wherein X bits in the first bitmap are set to predetermined values ​​and are used to respectively indicate the HARQ processes corresponding to each PXSCH in the target PXSCH;

[0540] Here, the value of X is equal to the number of PXSCHs included in the target PXSCH.

[0541] Optionally, when each PXSCH group in the target PXSCH corresponds to a different HARQ process, and each PXSCH in the same PXSCH group corresponds to the same HARQ process, the DCI further includes any one of the following:

[0542] Information used to indicate a second number, where the second number is the number of PXSCHs included in a single PXSCH group;

[0543] PXSCH group division information;

[0544] Information used to indicate the correspondence between the target PXSCH and the HARQ process.

[0545] Optionally, the PXSCH group division information is located in the time domain resource allocation information indicated by the DCI; or,

[0546] The DCI includes a third indication field, and the third indication field is used to indicate the PXSCH group division information.

[0547] Optionally, the PXSCH group division information includes at least one of the following:

[0548] Information used to indicate the boundary of a PXSCH group;

[0549] Information used to indicate the number of PXSCHs contained in each PXSCH group.

[0550] In summary, the embodiments of the present application provide a specific and feasible solution for scheduling multiple shared channels that may (or are allowed to) be transmitted in parallel in a given transmission direction within the same serving cell for a single DCI, in key aspects such as HARQ process occupancy and HARQ-ACK feedback. The embodiments of the present application can not only improve the flexibility of physical shared channel scheduling, but also reduce the scheduling overhead of physical shared channels. In addition, these N physical shared channels occupy one or more HARQ processes, which can reduce the HARQ process occupancy overhead and HARQ-ACK feedback overhead.

[0551] The channel scheduling device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0552] The channel scheduling device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0553] As shown in Figure 8, an embodiment of the present application further provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores a program or instruction that can be run on the processor 801. For example, when the communication device 800 is a terminal, the program or instruction, when executed by the processor 801, implements the various steps of the above-mentioned terminal-side method embodiment and can achieve the same technical effect. When the communication device 800 is a network-side device, the program or instruction, when executed by the processor 801, implements the various steps of the above-mentioned network-side method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0554] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

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

[0556] Those skilled in the art will appreciate that the terminal 900 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 910 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG9 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0557] It should be understood that in an embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 907 includes a touch panel 9071 and at least one of other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0558] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 901 may transmit the data to the processor 910 for processing. Furthermore, the RF unit 901 may send uplink data to the network-side device. Typically, the RF unit 901 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0559] The memory 909 can be used to store software programs or instructions and various data. The memory 909 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 909 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. 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 RAM bus random access memory (DRRAM). The memory 909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0560] Processor 910 may include one or more processing units. Optionally, processor 910 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 910.

[0561] The radio frequency unit 901 is used for:

[0562] Receive downlink control information DCI from a network-side device, where the DCI is used to schedule N physical shared channels PXSCH, where the N PXSCHs are all PUSCHs, or where the N PXSCHs are all PDSCHs, where N is an integer greater than or equal to 1;

[0563] The processor 910 is configured to:

[0564] Based on the DCI, the hybrid automatic repeat request HARQ process corresponding to the target PXSCH is determined, and the target PXSCH is the N PXSCHs, or the target PXSCH is a valid PXSCH among the N PXSCHs.

[0565] In the embodiment of the present application, since a single DCI can schedule N PUSCHs or N PDSCHs, the embodiment of the present application can improve the flexibility of physical shared channel scheduling and reduce the scheduling overhead of the physical shared channel. In addition, these N physical shared channels occupy one or more HARQ processes, which can reduce the HARQ process occupation overhead and HARQ-ACK feedback overhead.

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

[0567] The present application 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 configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG5 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0568] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 10, network-side device 1000 includes an antenna 101, a radio frequency device 102, a baseband device 103, a processor 104, and a memory 105. Antenna 101 is connected to radio frequency device 102. In the uplink direction, radio frequency device 102 receives information via antenna 101 and sends the received information to baseband device 103 for processing. In the downlink direction, baseband device 103 processes the information to be transmitted and sends it to radio frequency device 102. Radio frequency device 102 processes the received information and then sends it through antenna 101.

[0569] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 103 , which includes a baseband processor.

[0570] The baseband device 103 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 10, one of which is, for example, a baseband processor, which is connected to the memory 105 through a bus interface to call the program in the memory 105 and execute the network side device operations shown in the above method embodiment.

[0571] The network side device may further include a network interface 106, which is, for example, a Common Public Radio Interface (CPRI).

[0572] Specifically, the network side device 1000 of the embodiment of the present application also includes: instructions or programs stored in the memory 105 and executable on the processor 104. The processor 104 calls the instructions or programs in the memory 105 to execute the method of execution of each module shown in Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0573] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned channel determination method embodiment or the various processes of the above-mentioned channel scheduling method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0574] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0575] An embodiment of the present application further provides a chip, which includes 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 the various processes of the above-mentioned channel determination method embodiment, or to implement the various processes of the above-mentioned channel scheduling method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0576] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0577] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned channel determination method embodiment, or to implement the various processes of the above-mentioned channel scheduling method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0578] An embodiment of the present application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the channel determination method described above, and the network-side device can be used to execute the steps of the channel scheduling method described above.

[0579] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0580] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0581] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A channel determination method, comprising: The terminal receives downlink control information DCI from a network-side device, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels PUSCH, or the N physical shared channels are all downlink physical shared channels PDSCH, where N is an integer greater than or equal to 1; The terminal determines a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel based on the DCI, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

2. The method according to claim 1, wherein The terminal determines, based on the DCI, a HARQ process corresponding to a target physical shared channel, including: The terminal determines, based on the DCI and the correspondence between the target physical shared channel and the HARQ process, the HARQ process corresponding to the target physical shared channel; The correspondence between the target physical shared channel and the HARQ process includes any one of the following: The target physical shared channel corresponds to the same HARQ process; Each physical shared channel in the target physical shared channel corresponds to a different HARQ process; Each physical shared channel group in the target physical shared channel corresponds to a different HARQ process, and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process.

3. The method according to claim 2, wherein: In a case where multiple physical shared channels correspond to the same HARQ process, the multiple physical shared channels meet a predefined condition; the multiple physical shared channels are the target physical shared channels, or the multiple physical shared channels are physical shared channels in the same physical shared channel group; The predefined conditions include at least one of the following: Each physical shared channel in the plurality of physical shared channels corresponds to the same activated bandwidth part BWP; Each physical shared channel in the plurality of physical shared channels corresponds to a different activated BWP; The subcarrier spacing SCS corresponding to each physical shared channel in the multiple physical shared channels is the same; The cyclic prefix CP corresponding to each physical shared channel in the multiple physical shared channels is the same; The time domain resource corresponding to each physical shared channel in the multiple physical shared channels meets a first preset condition; The number of PRBs occupied by each of the multiple physical shared channels is less than or equal to a first preset threshold; The total number of PRBs occupied by the multiple physical shared channels is less than or equal to a second preset threshold; The transport block size TBS of the multiple physical shared channels is less than or equal to a third preset threshold; A difference in channel quality of the multiple physical shared channels is less than or equal to a fourth preset threshold; The number of layers mapped to each physical shared channel in the multiple physical shared channels is equal; The maximum number of transport blocks TB supported by each physical shared channel in the multiple physical shared channels is equal; The number of TBs actually scheduled by each of the multiple physical shared channels is equal.

4. The method according to claim 3, wherein: The first preset condition includes at least one of the following: The duration of time domain resources overlaps; The interval between the start times of the time domain resources is less than or equal to a fifth preset threshold; The interval between the end times of the time domain resources is less than or equal to a sixth preset threshold; The time domain resources are located in the same time domain unit.

5. The method according to claim 2, wherein: In a case where each physical shared channel in the target physical shared channel corresponds to a different HARQ process, determining the HARQ process corresponding to the target physical shared channel includes any one of the following: determining, according to the first information included in the DCI, a HARQ process corresponding to each physical shared channel in the target physical shared channel; Determining, according to the second information included in the DCI and the first rule, a HARQ process corresponding to each physical shared channel in the target physical shared channel; The first information is used to indicate the HARQ process corresponding to each physical shared channel in the target physical shared channel; The second information is used to indicate that the first HARQ process identifier corresponds to the first physical shared channel in the target physical shared channel; The first rule is predefined by a protocol, configured by a network, or indicated by the DCI.

6. The method according to claim 5, wherein: The first information sequentially indicates the HARQ process corresponding to each physical shared channel in the target physical shared channel based on the physical shared channel order of the target physical shared channel.

7. The method according to claim 5 or 6, wherein: The first information includes at least one of the following: X first indication fields, where the X first indication fields are used to respectively indicate a HARQ process corresponding to each physical shared channel in the target physical shared channel; a second indication field, where the second indication field is used to jointly indicate the HARQ processes corresponding to the respective physical shared channels in the target physical shared channel; a first bitmap, wherein X bits in the first bitmap are set to predetermined values and are used to respectively indicate a HARQ process corresponding to each physical shared channel in the target physical shared channel; The value of X is equal to the number of physical shared channels included in the target physical shared channel.

8. The method according to claim 2, wherein: In a case where each physical shared channel group in the target physical shared channel corresponds to a different HARQ process, and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process, the method further includes any one of the following: The terminal divides the target physical shared channel into at least one physical shared channel group based on a second number and a physical shared channel order of the target physical shared channel, where the second number is the number of physical shared channels included in a single physical shared channel group, and the second number is predefined by a protocol, configured by a network, or indicated by the DCI; The terminal divides the target physical shared channel into at least one physical shared channel group based on whether a predefined condition is satisfied, wherein each physical shared channel in the same physical shared channel group satisfies the same predefined condition; The terminal divides the target physical shared channel into at least one physical shared channel group based on a predefined number of physical shared channel groups and a physical shared channel order of the target physical shared channel; The terminal divides the target physical shared channel into at least one physical shared channel group based on the physical shared channel group division information indicated by the DCI; The terminal divides the physical shared channels corresponding to the same HARQ process into the same physical shared channel group based on the correspondence between the target physical shared channels and the HARQ processes indicated by the DCI.

9. The method according to claim 8, wherein The physical shared channel group division information is located in the time domain resource allocation information indicated by the DCI; or, The DCI includes a third indication field, where the third indication field is used to indicate the physical shared channel group division information.

10. The method according to claim 8 or 9, wherein: The physical shared channel group division information includes at least one of the following: Information used to indicate a boundary of a physical shared channel group; Information used to indicate the number of physical shared channels included in each physical shared channel group.

11. The method according to claim 6 or 8, wherein: The physical shared channel order of the target physical shared channel is determined based on at least one of the following: resource allocation information of each physical shared channel in the target physical shared channel, the resource allocation information comprising at least one of frequency domain resource allocation information and time domain resource allocation information; A BWP sequence corresponding to each physical shared channel in the target physical shared channel; a start time of each physical shared channel in the target physical shared channel; an end time of each physical shared channel in the target physical shared channel; The frequency of the frequency domain resources of each physical shared channel in the target physical shared channel; HARQ processes occupied by each physical shared channel in the target physical shared channel; An effective code rate of each physical shared channel in the target physical shared channel.

12. The method according to claim 11, wherein The BWP order is determined based on at least one of the following: BWP logo; The frequency of the frequency domain resource to which the BWP is configured; The order of each BWP in the predefined BWP subset; The DCI indicates the order of BWPs.

13. The method according to any one of claims 1 to 12, wherein The method further comprises: In a case where the target physical shared channel corresponds to the same HARQ process, a target reference point of the HARQ-ACK feedback timing is determined based on a reference physical downlink shared channel PDSCH, where the target reference point is a reference point to which a feedback time offset is applied.

14. The method according to any one of claims 1 to 13, wherein The method further comprises: When each physical shared channel in the target physical shared channel corresponds to a different HARQ process, or when each physical shared channel group in the target physical shared channel corresponds to a different HARQ process and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process, performing HARQ-ACK feedback-related operations based on a type of the HARQ-ACK codebook; Wherein, when the type of the HARQ-ACK codebook is type 1, the performing of HARQ-ACK feedback-related operations includes: determining a target HARQ-ACK bit sequence in the HARQ-ACK codebook, where the target HARQ-ACK bit sequence is a HARQ-ACK bit sequence corresponding to the target serving cell; or When the HARQ-ACK codebook type is type 2, performing HARQ-ACK feedback-related operations includes: Determine a mapping relationship between HARQ-ACK feedback and two HARQ-ACK subcodebooks included in the HARQ-ACK codebook, where the two HARQ-ACK subcodebooks include a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook; or, When the HARQ-ACK codebook type is type 3, performing HARQ-ACK feedback-related operations includes: Determine the number of codewords for each HARQ process of the target serving cell; The target serving cell is the serving cell where the target physical shared channel is located.

15. The method according to claim 14, wherein When the type of the HARQ-ACK codebook is type 1, determining a target HARQ-ACK bit sequence in the HARQ-ACK codebook includes: Determine, based on a time domain resource allocation TDRA table corresponding to the i-th BWP of the target serving cell, a timing set corresponding to the i-th BWP; wherein i ranges from 1 to M, and M is the number of BWPs configured in the target serving cell; Constructing a HARQ-ACK bit sequence corresponding to the i-th BWP based on the opportunity set corresponding to the i-th BWP; Perform end-to-end concatenation of the HARQ-ACK bit sequences corresponding to the M BWPs of the target serving cell based on a predefined order to obtain a target HARQ-ACK bit sequence in the HARQ-ACK codebook; or, The HARQ-ACK feedback corresponding to the first physical shared channel group is included in the HARQ-ACK bit sequence corresponding to the first BWP, where the first physical shared channel group is a physical shared channel group corresponding to at least two BWPs, and the first BWP is the BWP corresponding to the reference PDSCH in the first physical shared channel group.

16. The method according to claim 15, wherein When the type of the HARQ-ACK codebook is type 2, determining a mapping relationship between the HARQ-ACK feedback and two HARQ-ACK subcodebooks included in the HARQ-ACK codebook includes at least one of the following: When the HARQ-ACK feedback is the first HARQ-ACK feedback, determine the first HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the first HARQ-ACK feedback; When the HARQ-ACK feedback is the second HARQ-ACK feedback, determining the second HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the second HARQ-ACK feedback; When the HARQ-ACK feedback is the third HARQ-ACK feedback, determine the first HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the third HARQ-ACK feedback; When the HARQ-ACK feedback is the fourth HARQ-ACK feedback, determine the second HARQ-ACK subcodebook as the HARQ-ACK subcodebook corresponding to the fourth HARQ-ACK feedback; The first HARQ-ACK feedback includes any one of the following: HARQ-ACK feedback when the DCI schedules a single PDSCH; HARQ-ACK feedback when the DCI does not schedule a PDSCH; SPS HARQ-ACK feedback; The second HARQ-ACK feedback includes: HARQ-ACK feedback when the DCI schedules multiple PDSCHs; The third HARQ-ACK feedback includes any one of the following: HARQ-ACK feedback when the DCI schedules a single PDSCH group; HARQ-ACK feedback when the DCI does not schedule PDSCH; SPS HARQ-ACK feedback; The fourth HARQ-ACK feedback includes: HARQ-ACK feedback when the DCI schedules multiple PDSCH groups.

17. The method according to claim 14, wherein: When the type of the HARQ-ACK codebook is type 3, determining the number of codewords for each HARQ process of the target serving cell includes any one of the following: uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as a single codeword, or uniformly determining the number of codewords as a double codeword; The number of codewords corresponding to the first HARQ process in the HARQ process configured for the target serving cell is determined as a single codeword, and the number of codewords corresponding to the second HARQ process in the HARQ process configured for the target serving cell is determined as a double codeword.

18. The method according to claim 17, wherein: The step of uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as a single codeword, or uniformly determining the number of codewords as a double codeword, includes at least one of the following: In a case where at least one of the BWPs configured for the target serving cell supports dual codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as dual codewords; In a case where none of the BWPs configured for the target serving cell supports dual-codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as a single codeword; In a case where at least one BWP in the BWP combination that can be scheduled by the DCI supports dual codeword transmission, uniformly determining the number of codewords corresponding to all HARQ processes configured for the target serving cell as dual codewords; In a case where all BWPs in the BWP combination that can be scheduled by the DCI do not support dual-codeword transmission, the number of codewords corresponding to all HARQ processes configured in the target serving cell is uniformly determined to be a single codeword.

19. The method according to claim 17, wherein When a second physical shared channel group in the target physical shared channel corresponds to at least two BWPs and a reference BWP in the at least two BWPs does not support dual codeword transmission, the second physical shared channel group can use the first HARQ process; or, When a third physical shared channel group in the target physical shared channel corresponds to at least two BWPs and a reference BWP in the at least two BWPs does not support dual codeword transmission, the third physical shared channel group can use the second HARQ process; or, When a fourth physical shared channel group in the target physical shared channel corresponds to at least two BWPs and a reference BWP in the at least two BWPs supports dual codeword transmission, the fourth physical shared channel group can use the second HARQ process.

20. The method according to claim 19, wherein The reference BWP includes at least one of the following: The BWP corresponding to the reference PDSCH in the physical shared channel group; Among the BWPs corresponding to the physical shared channels included in the physical shared channel group, the BWP that supports the least number of codewords; Among the BWPs corresponding to the physical shared channels included in the physical shared channel group, the BWP that supports the largest number of codewords.

21. The method according to any one of claims 13, 15 and 20, wherein The reference PDSCH includes at least one of the following: The first PDSCH among the PDSCHs scheduled by the DCI; The last PDSCH in the PDSCH scheduled by the DCI; A designated PDSCH in the PDSCH scheduled by the DCI; The first PDSCH among the PDSCHs corresponding to the second BWP; The last PDSCH in the PDSCH corresponding to the second BWP; a designated PDSCH among the PDSCHs corresponding to the second BWP; The first PDSCH in the PDSCH corresponding to the first SCS; The last PDSCH in the PDSCH corresponding to the first SCS; A designated PDSCH in the PDSCH corresponding to the first SCS; Wherein, the second BWP is a predefined BWP; The first SCS is a predefined SCS.

22. A channel scheduling method, comprising: The network-side device sends downlink control information DCI to the terminal, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels PUSCH, or the N physical shared channels are all downlink physical shared channels PDSCH, where N is an integer greater than 1; The DCI is used to determine a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

23. The method according to claim 22, wherein The correspondence between the target physical shared channel and the HARQ process includes any one of the following: The target physical shared channel corresponds to the same HARQ process; Each physical shared channel in the target physical shared channel corresponds to a different HARQ process; Each physical shared channel group in the target physical shared channel corresponds to a different HARQ process, and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process.

24. The method according to claim 23, wherein In a case where multiple physical shared channels correspond to the same HARQ process, the multiple physical shared channels meet a predefined condition; the multiple physical shared channels are the target physical shared channels, or the multiple physical shared channels are physical shared channels in the same physical shared channel group; The predefined conditions include at least one of the following: Each physical shared channel in the plurality of physical shared channels corresponds to the same activated bandwidth part BWP; Each physical shared channel in the plurality of physical shared channels corresponds to a different activated BWP; The subcarrier spacing SCS corresponding to each physical shared channel in the multiple physical shared channels is the same; The cyclic prefix CP corresponding to each physical shared channel in the multiple physical shared channels is the same; The time domain resource corresponding to each physical shared channel in the multiple physical shared channels meets a first preset condition; The number of PRBs occupied by each of the multiple physical shared channels is less than or equal to a first preset threshold; The total number of PRBs occupied by the multiple physical shared channels is less than or equal to a second preset threshold; The transport block size TBS of the multiple physical shared channels is less than or equal to a third preset threshold; A difference in channel quality of the multiple physical shared channels is less than or equal to a fourth preset threshold; The number of layers mapped to each physical shared channel in the multiple physical shared channels is equal; The maximum number of transport blocks TB supported by each physical shared channel in the multiple physical shared channels is equal; The number of TBs actually scheduled by each of the multiple physical shared channels is equal.

25. The method according to claim 23, wherein In a case where each physical shared channel in the target physical shared channel corresponds to a different HARQ process, the DCI includes any one of the following: first information, where the first information is used to indicate a HARQ process corresponding to each physical shared channel in the target physical shared channel; Second information, where the second information is used to indicate that the first HARQ process identifier corresponds to a first physical shared channel in the target physical shared channel.

26. The method according to claim 23, wherein In a case where each physical shared channel group in the target physical shared channel corresponds to a different HARQ process, and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process, the DCI further includes any one of the following items: Information used to indicate a second number, where the second number is the number of physical shared channels included in a single physical shared channel group; Physical shared channel group division information; Information used to indicate the correspondence between the target physical shared channel and the HARQ process.

27. A channel determination device, applied to a terminal, the device comprising: a receiving unit, configured to receive downlink control information DCI from a network-side device, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels PUSCH, or the N physical shared channels are all downlink physical shared channels PDSCH, where N is an integer greater than or equal to 1; The first processing unit is configured to determine, based on the DCI, a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

28. The apparatus according to claim 27, wherein The first processing unit is specifically configured to: Determining, based on the DCI and the correspondence between the target physical shared channel and the HARQ process, a HARQ process corresponding to the target physical shared channel; The correspondence between the target physical shared channel and the HARQ process includes any one of the following: The target physical shared channel corresponds to the same HARQ process; Each physical shared channel in the target physical shared channel corresponds to a different HARQ process; Each physical shared channel group in the target physical shared channel corresponds to a different HARQ process, and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process.

29. The apparatus according to claim 27, wherein In a case where each physical shared channel in the target physical shared channel corresponds to a different HARQ process, the first processing unit is specifically configured to perform any of the following: determining, according to the first information included in the DCI, a HARQ process corresponding to each physical shared channel in the target physical shared channel; Determining, according to the second information included in the DCI and the first rule, a HARQ process corresponding to each physical shared channel in the target physical shared channel; The first information is used to indicate the HARQ process corresponding to each physical shared channel in the target physical shared channel; The second information is used to indicate that the first HARQ process identifier corresponds to the first physical shared channel in the target physical shared channel; The first rule is predefined by a protocol, configured by a network, or indicated by the DCI.

30. The apparatus of claim 27, wherein: The device further comprises: The second processing unit is configured to, when each physical shared channel group in the target physical shared channel corresponds to a different HARQ process, and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process, perform any one of the following: Dividing the target physical shared channel into at least one physical shared channel group based on a second number and a physical shared channel order of the target physical shared channel, where the second number is the number of physical shared channels included in a single physical shared channel group, and the second number is predefined by a protocol, configured by a network, or indicated by the DCI; Based on whether a predefined condition is satisfied, dividing the target physical shared channel into at least one physical shared channel group, wherein each physical shared channel in the same physical shared channel group satisfies the same predefined condition; dividing the target physical shared channel into at least one physical shared channel group based on a predefined number of physical shared channel groups and a physical shared channel order of the target physical shared channel; Dividing the target physical shared channel into at least one physical shared channel group based on the physical shared channel group division information indicated by the DCI; Based on the correspondence between the target physical shared channels indicated by the DCI and the HARQ processes, the physical shared channels corresponding to the same HARQ process are divided into the same physical shared channel group.

31. The device according to any one of claims 27 to 30, wherein The device further comprises: The third processing unit is configured to determine, when the target physical shared channel corresponds to the same HARQ process, a target reference point of the HARQ-ACK feedback timing based on the reference physical downlink shared channel PDSCH, where the target reference point is a reference point for applying the feedback time offset.

32. The device according to any one of claims 27 to 31, wherein The device further comprises: a fourth processing unit, configured to perform HARQ-ACK feedback-related operations based on a type of the HARQ-ACK codebook, when each physical shared channel in the target physical shared channel corresponds to a different HARQ process, or when each physical shared channel group in the target physical shared channel corresponds to a different HARQ process and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process; Wherein, when the type of the HARQ-ACK codebook is type 1, the performing of HARQ-ACK feedback-related operations includes: determining a target HARQ-ACK bit sequence in the HARQ-ACK codebook, where the target HARQ-ACK bit sequence is a HARQ-ACK bit sequence corresponding to the target serving cell; or When the HARQ-ACK codebook type is type 2, performing HARQ-ACK feedback-related operations includes: Determine a mapping relationship between HARQ-ACK feedback and two HARQ-ACK subcodebooks included in the HARQ-ACK codebook, where the two HARQ-ACK subcodebooks include a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook; or, When the HARQ-ACK codebook type is type 3, performing HARQ-ACK feedback-related operations includes: Determine the number of codewords for each HARQ process of the target serving cell; The target serving cell is the serving cell where the target physical shared channel is located.

33. A channel scheduling device, applied to a network-side device, comprising: a sending unit, configured to send downlink control information DCI to a terminal, where the DCI is used to schedule N physical shared channels, where the N physical shared channels are all uplink physical shared channels PUSCH, or the N physical shared channels are all downlink physical shared channels PDSCH, where N is an integer greater than 1; The DCI is used to determine a hybrid automatic repeat request HARQ process corresponding to a target physical shared channel, where the target physical shared channel is the N physical shared channels, or the target physical shared channel is a valid physical shared channel among the N physical shared channels.

34. The apparatus according to claim 33, wherein The correspondence between the target physical shared channel and the HARQ process includes any one of the following: The target physical shared channel corresponds to the same HARQ process; Each physical shared channel in the target physical shared channel corresponds to a different HARQ process; Each physical shared channel group in the target physical shared channel corresponds to a different HARQ process, and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process.

35. The apparatus of claim 34, wherein: In a case where each physical shared channel in the target physical shared channel corresponds to a different HARQ process, the DCI includes any one of the following: first information, where the first information is used to indicate a HARQ process corresponding to each physical shared channel in the target physical shared channel; Second information, where the second information is used to indicate that the first HARQ process identifier corresponds to a first physical shared channel in the target physical shared channel.

36. The apparatus of claim 34, wherein: In a case where each physical shared channel group in the target physical shared channel corresponds to a different HARQ process, and each physical shared channel in the same physical shared channel group corresponds to the same HARQ process, the DCI further includes any one of the following items: Information used to indicate a second number, where the second number is the number of physical shared channels included in a single physical shared channel group; Physical shared channel group division information; Information used to indicate the correspondence between the target physical shared channel and the HARQ process.

37. A communication device comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the channel determination method as described in any one of claims 1 to 21 are implemented, or the steps of the channel scheduling method as described in any one of claims 22 to 26 are implemented.

38. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the channel determination method as described in any one of claims 1 to 21, or implements the steps of the channel scheduling method as described in any one of claims 22 to 26.

39. A computer program product comprising computer instructions, which, when executed by a processor, implement the steps of the channel determination method according to any one of claims 1 to 21, or implement the steps of the channel scheduling method according to any one of claims 22 to 26.

Images