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

Abstract

The present application relates to the technical field of communications, and discloses a channel determination method and apparatus, a channel scheduling method and apparatus, and a communication device. The channel determination method of embodiments of the present application comprises: a terminal receives downlink control information (DCI) from a network side device, the DCI being used for scheduling N physical shared channels that are all PUSCHs or are all PDSCHs, and N being an integer greater than or equal to 1; and the terminal executes a target operation on the basis of the DCI, wherein the target operation comprises at least one of the following items: determining a bandwidth part (BWP) corresponding to the N physical shared channels; and determining resource allocation information corresponding to the N physical shared channels, the resource allocation information comprising at least one of frequency domain resource allocation information and time domain resource allocation information.

Description

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

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202410171138.1 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 via downlink control information (DCI). In related technologies, a single DCI can usually only schedule one physical shared channel in the same transmission direction (uplink or downlink). This shows that the scheduling of the physical shared channel lacks flexibility. 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 problem of lack of flexibility in scheduling of physical shared channels in related technologies.

[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 performs a target operation based on the DCI;

[0009] The target operation includes at least one of the following:

[0010] Determine a bandwidth part BWP corresponding to the N physical shared channels;

[0011] Resource allocation information corresponding to the N physical shared channels is determined, where the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

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

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

[0014] The DCI is used to determine at least one of the following:

[0015] The bandwidth part BWP corresponding to the N physical shared channels;

[0016] The resource allocation information corresponding to the N physical shared channels includes at least one of frequency domain resource allocation information and time domain resource allocation information.

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

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

[0019] A first processing unit, configured to perform a target operation based on the DCI;

[0020] The target operation includes at least one of the following:

[0021] Determine a bandwidth part BWP corresponding to the N physical shared channels;

[0022] Resource allocation information corresponding to the N physical shared channels is determined, where the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

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

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

[0025] The DCI is used to determine at least one of the following:

[0026] The bandwidth part BWP corresponding to the N physical shared channels;

[0027] The resource allocation information corresponding to the N physical shared channels includes at least one of frequency domain resource allocation information and time domain resource allocation information.

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

[0029] 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, wherein the DCI is used to schedule N physical shared channels, wherein 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, and N is an integer greater than or equal to 1; the processor is used to: perform a target operation based on the DCI; wherein the target operation includes at least one of the following: determining a bandwidth part BWP corresponding to the N physical shared channels; determining resource allocation information corresponding to the N physical shared channels, wherein the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

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

[0031] In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is used to: send downlink control information DCI to a terminal, wherein the DCI is used to schedule N physical shared channels, wherein 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; wherein the DCI is used to determine at least one of the following: a bandwidth part BWP corresponding to the N physical shared channels; resource allocation information corresponding to the N physical shared channels, wherein the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

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

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

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

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

[0036] 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 physical shared channels, wherein the N physical shared channels are all PUSCHs, or the N physical shared channels are all PDSCHs, and N is an integer greater than or equal to 1; the terminal performs a target operation based on the DCI; the target operation includes at least one of the following: determining the BWP corresponding to the N physical shared channels; determining the resource allocation information corresponding to the N physical shared channels. Since a single DCI can schedule N PUSCHs or N PDSCHs, the embodiment of the present application supports DCI scheduling of multiple physical shared channels, which can improve the flexibility of physical shared channel scheduling and reduce the scheduling overhead of physical shared channels. In addition, the terminal can also determine the BWP or resource allocation information corresponding to the N physical shared channels based on the DCI, so that data can be transmitted through the N physical shared channels, which can fully utilize the frequency domain resources of the cell, improve data throughput, and reduce transmission delay. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0064] The channel determination method and channel scheduling method provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

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

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

[0067] Step 302: The terminal performs a target operation based on the DCI.

[0068] The target operation includes at least one of the following:

[0069] Determine the BWP corresponding to the N physical shared channels;

[0070] Resource allocation information corresponding to the N physical shared channels is determined, where the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

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

[0072] In the 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. Accordingly, here we mainly consider that a single DCI schedules N PXSCHs in a single service cell, and these N PXSCHs are located in at least one BWP of this service cell, that is, they are located in a single or multiple BWPs. 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. FIG4 shows a schematic diagram of a single DCI scheduling multiple PXSCHs for parallel transmission.

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

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

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

[0076] CG PUSCH with Type 2;

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

[0078] Dynamically Granted (DG) PUSCH;

[0079] DG PDSCH.

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

[0081] In the embodiment of the present application, determining the BWP corresponding to the N PXSCHs can be replaced by determining the correspondence between the N PXSCHs and the BWPs. Determining the BWP corresponding to the N PXSCHs can be achieved by determining the PXSCH corresponding to each BWP scheduled with the PXSCH.

[0082] Determining the resource allocation information corresponding to the N PXSCHs can be replaced by determining the correspondence between the N PXSCHs and the resource allocation information.

[0083] 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 performs a target operation based on the DCI; the target operation includes at least one of the following: determining the BWP corresponding to the N PXSCHs; determining the resource allocation information corresponding to 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 PXSCH scheduling and, in addition, reduce the scheduling overhead of the physical shared channel. Furthermore, the terminal can also determine the BWP or resource allocation information corresponding to the N physical shared channels based on the DCI, thereby enabling data transmission through the N physical shared channels, thereby fully utilizing the frequency domain resources of the cell, improving data throughput, and reducing transmission delay.

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

[0085] In the embodiment of the present application, determining the BWP corresponding to the N PXSCHs can be understood as determining the BWP to which the N PXSCHs belong. The following first describes an implementation method for determining the BWP to which the N PXSCHs belong.

[0086] In some embodiments, the DCI is used to schedule N PXSCHs, including any of the following:

[0087] The DCI is used to schedule N PXSCHs within a single BWP;

[0088] The DCI is used to schedule N PXSCHs within N BWPs;

[0089] The DCI is used to schedule N PXSCHs within M BWPs, where M is an integer less than N.

[0090] That is, N PXSCHs can be scheduled based on any of the following situations:

[0091] Case 1: One DCI schedules only a single PXSCH within a single BWP;

[0092] Case 2: One DCI can schedule one or more PXSCHs within a single BWP;

[0093] Case 3: One DCI can schedule multiple PXSCHs in multiple BWPs, and each BWP contains only a single PXSCH;

[0094] Case 4: One DCI can schedule multiple PXSCHs in multiple BWPs, and each BWP may contain one or more PXSCHs.

[0095] Since any of the above four PXSCH scheduling methods can be adopted, the flexibility of PXSCH scheduling can be improved.

[0096] When case 1 or case 2 is allowed, the BWP corresponding to each of the N PXSCHs may be determined as any one of the following:

[0097] The BWP where the DCI is located;

[0098] The BWP indicated by the DCI.

[0099] That is to say, the BWP where the DCI is located can be determined as the BWP corresponding to all scheduled PXSCHs, or the ID / index corresponding to a single BWP can be indicated in the DCI, and this single BWP can be used as the BWP corresponding to all scheduled PXSCHs.

[0100] When situation 3 is allowed, the embodiment of the present application provides the following implementation method:

[0101] In some embodiments, when the DCI is used to schedule N PXSCHs within N BWPs, the DCI includes first information, where the first information is used to indicate a first BWP subset, or used to indicate a first BWP in a first BWP subset, where the first BWP subset is a BWP subset including N BWPs;

[0102] The determining of the BWP corresponding to the N PXSCHs includes any one of the following:

[0103] Determine the N BWPs included in the first BWP subset indicated by the first information as the BWPs of the N PXSCHs;

[0104] Based on the first BWP indicated by the first information and the first rule, a first BWP subset is determined, and the N BWPs included in the determined first BWP subset are determined as the BWPs of the N PXSCHs; wherein the first rule is predefined by the protocol or configured by the network or indicated by the DCI.

[0105] That is, when case 3 is allowed, the DCI may indicate a BWP subset, or in other words, the DCI may indicate the BWP subset it schedules, and schedules a single PXSCH for each BWP in this BWP subset.

[0106] In this implementation, the DCI includes first information, and the BWP subset is directly indicated or indirectly indicated through the first information.

[0107] In this implementation, by indicating the BWP subset, it can be more simply achieved that a single DCI schedules N PXSCHs on one or more BWPs in the same serving cell.

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

[0109] a first bitmap, where the first bitmap is used to indicate the first BWP subset;

[0110] a first subset identifier, where the first subset identifier is used to indicate the first BWP subset, and the first BWP subset is a BWP subset in a predefined BWP subset list;

[0111] N BWP identifiers, the first BWP subset includes N BWPs corresponding to the N BWP identifiers;

[0112] A first BWP identifier is used to indicate the first BWP.

[0113] Each bit of the first bitmap may correspond to each BWP in a BWP order.

[0114] The number of bits of the first bitmap may be equal to a first number or a second number, wherein the first number is the number of BWPs configured in the current serving cell, and the second number is the number of activated BWPs in the BWPs configured in the current serving cell.

[0115] Optionally, the first BWP identifier is an identifier of a predefined BWP in the first BWP subset, and the first rule includes at least one of the number of BWPs, an increasing step, and a decreasing step;

[0116] The predefined BWP includes any of the following:

[0117] BWP identifies the smallest BWP;

[0118] BWP identifies the largest BWP;

[0119] The BWP corresponding to the PXSCH at the predefined position among the N PXSCHs.

[0120] The PXSCH at a predefined position among N PXSCHs can be understood as a PXSCH at a specific position determined according to the order between PXSCHs (which can be referred to as PXSCH order) (see the corresponding description below for details), for example, the first PXSCH among N PXSCHs.

[0121] The number of BWPs may be specified by the protocol or configured by higher-layer signaling, or directly indicated by the DCI, or indicated by the DCI as a value in a predefined number list, or equal to the number of PXSCHs. Here, the number of PXSCHs may be determined based on frequency domain resource allocation and / or time domain resource allocation.

[0122] As can be seen from the above optional implementations, there are multiple ways for DCI to indicate a BWP subset. When indicating the BWP subset it schedules, DCI can use any of the following BWP subset indication modes 1 to 4:

[0123] BWP subset indication mode (or scheduling BWP subset indication mode, the same below) 1: Use bitmap to indicate each BWP configured in the current serving cell, or whether each BWP currently activated belongs to this BWP subset

[0124] For example, the number of bits in the Bitmap (i.e., the number of bits in the DCI indication field) is the number of BWPs configured for the current serving cell or the number of BWPs currently in Active state. Each bit in the Bitmap corresponds to each BWP based on the order between BWPs (referred to as BWP order) (see the corresponding description below for details). When the value of a certain bit is 1, it indicates that the corresponding BWP belongs to this BWP subset, that is, a single PXSCH is scheduled. Optionally, each bit in the Bitmap can also correspond to a group of BWPs, for example, the BWPs configured for the current serving cell or the Active BWPs are grouped based on a method similar to the PXSCH grouping method (see the corresponding description below for details).

[0125] BWP subset indication method 2: Indicates a BWP subset in the predefined BWP subset list

[0126] The predefined BWP subset list may be specified by the protocol or configured by higher layer signaling.

[0127] BWP subset indication method 3: directly indicate the ID / index of each BWP contained in the BWP subset

[0128] For example, each BWP ID / index in the BWP subset is indicated by a single corresponding BWP ID / index indication field in the DCI, and the number of BWP ID / index indication fields in the DCI may be specified by the protocol or configured by higher layer signaling.

[0129] BWP subset indication mode 4: only indicate the predefined BWP (or specific BWP) in the BWP subset, and other BWPs are determined based on this indication and predefined rules

[0130] For example, the ID / index of a predefined BWP is directly indicated. The ID / index of the BWP following the predefined BWP is: the ID / index corresponding to the predefined BWP + / - the step size (which can be further modulo the maximum number of IDs / indexes, the number of BWPs configured in the current serving cell, or the number of currently active BWPs); the ID / index of the next BWP is: the ID / index corresponding to the previous BWP + / - the step size (which can be further modulo the maximum number of IDs / indexes, the number of BWPs configured in the current serving cell, or the number of currently active BWPs); and so on. The step size here is >= 1, and typically can be 1. The ID / index of a BWP can be understood as the ID / index configured for that BWP, or, based on the order of BWPs, the local index / subscript of that BWP within the BWPs configured in the current serving cell (or the currently active BWP).

[0131] For another example, first determine the order between PXSCHs and directly indicate the BWP ID corresponding to the first PXSCH scheduled; the BWP corresponding to the next PXSCH is: (BWP ID corresponding to the previous PXSCH + / - step size) mod the number of BWPs, where mod represents the modulo operation.

[0132] In some embodiments, determining the BWP corresponding to the N PXSCHs further includes:

[0133] Based on the BWP order of the first BWP subset, the correspondence between each PXSCH in the N PXSCHs and each BWP in the first BWP subset is determined.

[0134] Exemplarily, the order between the frequency domain resource allocation information corresponding to at least one PXSCH scheduled by this DCI (when frequency domain resource allocation mode 1-1 or time domain resource allocation mode 1-1 is adopted) can be determined based on the order between the BWPs in the BWP subset (see the corresponding description below for details), or the order between the time domain resource allocation information corresponding to at least one PXSCH (when frequency domain resource allocation mode 1-2 and / or time domain resource allocation mode 1-2 is adopted). At this time, each BWP in the BWP subset corresponds one by one to each PXSCH scheduled by the DCI based on this order.

[0135] Optionally, the UE expects (or the network-side device ensures) that each BWP in the indicated BWP subset is in the Active state.

[0136] When situation 4 is allowed, the embodiment of the present application provides the following implementation method:

[0137] In some embodiments, when the DCI is used to schedule N PXSCHs within M BWPs, determining the BWPs corresponding to the N PXSCHs includes any one of the following:

[0138] Determine, according to the second information included in the DCI, a BWP corresponding to each PXSCH of the N PXSCHs;

[0139] Determine, according to the third information and the fourth information included in the DCI, a BWP corresponding to each PXSCH in the N PXSCHs;

[0140] Determine, according to the third information and the fifth information included in the DCI, a BWP corresponding to each PXSCH in the N PXSCHs;

[0141] Determine, according to the third information included in the DCI and S PXSCH groups, a BWP corresponding to each PXSCH group of the S PXSCH groups, where the S PXSCH groups are obtained by grouping the N PXSCHs, and S is an integer greater than or equal to 1 and less than or equal to N;

[0142] The second information is used to indicate the BWP corresponding to each PXSCH in the N PXSCHs;

[0143] The third information is used to indicate the second BWP subset, or is used to indicate the second BWP in the second BWP subset, where the second BWP subset is a BWP subset including M BWPs;

[0144] The fourth information is used to indicate the PXSCH corresponding to each BWP in the second BWP subset;

[0145] The fifth information is used to indicate the correspondence between each PXSCH in the N PXSCHs and each BWP in the second BWP subset.

[0146] Optionally, the second information includes at least one of the following:

[0147] N first indication fields, where the N first indication fields are used to respectively indicate the BWP corresponding to each of the N PXSCHs;

[0148] The second indication field is used to jointly indicate the BWP corresponding to each PXSCH in the N PXSCHs.

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

[0150] Optionally, the fourth information includes:

[0151] M second bitmaps, where the M second bitmaps are used to respectively indicate the PXSCH corresponding to each BWP in the second BWP subset.

[0152] The order of the M second bitmaps may be consistent with the BWP order of the second BWP subset (for details, see the corresponding description below).

[0153] Each bit of each second bit map in the M second bit maps may correspond to each PXSCH according to the PXSCH order of the N PXSCHs (for details, please refer to the corresponding description below).

[0154] Optionally, the fifth information includes:

[0155] The third bit map, each K bits of the third bit map are used to respectively indicate the BWP corresponding to each PXSCH in the N PXSCHs, and K is an integer greater than or equal to 1.

[0156] Optionally, the fifth information includes N independent indication fields, each indication field being used to indicate the index of the BWP corresponding to the corresponding PXSCH in the second BWP subset. The index here can be understood as the index in the subset, as distinguished from the method of directly indicating the BWP ID / index within the current serving cell range in scheduling BWP indication mode 1.

[0157] In some embodiments, determining the BWP corresponding to each of the S PXSCH groups according to the third information included in the DCI and the S PXSCH groups includes:

[0158] Based on the BWP order of the second BWP subset and the order of each PXSCH group, the BWP corresponding to each PXSCH group is determined.

[0159] In this embodiment, by determining the BWP corresponding to the PXSCH group, the BWP corresponding to each PXSCH group can be determined more efficiently.

[0160] In some embodiments, when determining the BWP corresponding to each of the S PXSCH groups based on the third information included in the DCI and the S PXSCH groups, the method further includes:

[0161] Based on the second rule, the N PXSCHs are grouped to obtain the S PXSCH groups;

[0162] The second rule includes at least one of the following:

[0163] The number of PXSCHs in a preset single PXSCH group;

[0164] Predefined conditions;

[0165] Grouping information indicated by DCI;

[0166] The preset number of PXSCH groups.

[0167] Among them, the preset PXSCH number of a single PXSCH group can be, for example, the maximum number of PXSCHs of a preset single PXSCH group.

[0168] As can be seen from the above optional implementation manner, when case 4 is allowed, the DCI may use any of the following BWP indication modes 1 to 2 to indicate the scheduled BWP:

[0169] BWP indication mode (or scheduling BWP indication mode, the same below) 1: Indicates the BWP ID / index corresponding to each PXSCH respectively

[0170] When indicating, an independent indication field / indication bit in the DCI can be used to indicate the BWP ID / index corresponding to each scheduled PXSCH respectively, or, a joint coding method can be used to use the same indication field / indication bit to simultaneously indicate the BWP ID / index corresponding to each scheduled PXSCH, for example, to indicate a BWP ID / index combination configured by a higher layer. The order between the BWP ID / index indication field / indication bit corresponding to each scheduled PXSCH can be the order between multiple PXSCHs scheduled by a single DCI (see the corresponding description below); or, when receiving DCI, the UE knows in advance that there are N BWP IDs / index indication fields / indication bits corresponding to PXSCHs in each DCI (N can be specified by the protocol or configured by high-level signaling; the number of bits occupied by the BWP ID / index indication field / indication bit corresponding to each PXSCH is also known in advance, for example, the number of bits occupied by the BWP ID / index indication field / indication bit corresponding to each PXSCH is equal, and is M, M can be specified by the protocol, or configured by high-level signaling, or determined based on the number of Configured / Active BWPs, for example, M=ceiling(log2(number of Configured / Active BWPs)), where ceiling() means rounding up), based on the BWP ID / index indication field / indication bit corresponding to these N PXSCHs (or the BWP corresponding to N1 Valid PXSCHs in the N PXSCHs The order between Scheduled / Valid PXSCHs can be determined by the order between the ID / index indication field / indication bit) (that is, the order of arrangement in the DCI).

[0171] It can be understood that, among the at least one PXSCH allowed to be scheduled at this time, the BWP ID / index corresponding to more than one PXSCH is the same.

[0172] BWP indication mode 2: Based on the indication of the scheduling BWP subset, further indicate the correspondence between each scheduling BWP and PXSCH

[0173] For the indication of scheduling BWP subsets, please refer to the corresponding description above.

[0174] When indicating the correspondence between each scheduling BWP and PXSCH, any of the following BWP indication methods 2-1 to scheduling BWP indication method 2-2 may be used:

[0175] BWP indication method 2-1: Use Bitmap to indicate the correspondence between each scheduling BWP and PXSCH

[0176] Specifically, any of the following scheduling BWP indication modes 2-1-1 to 2-1-2 may be used:

[0177] Scheduling BWP indication method 2-1-1: Indicates the PXSCH corresponding to each scheduling BWP

[0178] At this time, a bitmap can be set for each scheduling BWP, and each bit in the bitmap corresponds to the scheduled PXSCH based on the order between the PXSCHs (see the corresponding description below; for example, the PXSCH order determined in the frequency domain resource allocation and / or time domain resource allocation). For example, a bit value of 1 in the bitmap indicates that the corresponding PXSCH corresponds to the scheduling BWP corresponding to this bitmap.

[0179] The order between the Bitmaps corresponding to each scheduled BWP is consistent with the order between the BWPs in the indicated scheduled BWP subset (see the corresponding description below for details).

[0180] Scheduling BWP indication method 2-1-2: Indicates the scheduling BWP corresponding to each PXSCH

[0181] At this time, a single Bitmap can be indicated in the DCI, and N bits can be set for a single PXSCH in this Bitmap (N>=1, for example, N=ceiling(log2(actual number of scheduled BWPs or maximum number of allowed scheduled BWPs)), where ceiling() is rounded up), and the bits in the Bitmap are mapped one by one to the scheduled PXSCH based on the order between PXSCHs (see the corresponding description below; for example, the PXSCH order determined in the frequency domain resource allocation and / or time domain resource allocation). The N bits corresponding to a certain PXSCH indicate the index of the scheduled BWP corresponding to this PXSCH in the scheduled BWP subset. For example, the scheduled BWP subset indication method 3 is adopted and the protocol specifies or the high-level signaling configures that two BWP IDs / indexes are indicated in the DCI; assuming that a single DCI can schedule up to M PXSCHs, an M-bit Bitmap is introduced in the DCI, and each bit in this Bitmap corresponds one by one to the PXSCH actually scheduled by the DCI based on the (starting) frequency domain resources allocated by the PXSCH in ascending order. For a certain bit in this Bitmap corresponding to a certain PXSCH, when its value is 0, it indicates the first BWP ID / index indicated by the DCI corresponding to this PXSCH, and when its value is 1, it indicates the second BWP ID / index indicated by the DCI corresponding to this PXSCH.

[0182] Scheduling BWP indication mode 2-2: Group the scheduled PXSCHs, and each PXSCH group corresponds to a single scheduling BWP

[0183] When grouping the scheduled PXSCHs, at least one of the following may be used:

[0184] Divide the PXSCH groups based on the number of PXSCHs contained in a single PXSCH group (such as the maximum number);

[0185] Divide PXSCH groups based on the satisfaction of predefined conditions;

[0186] The PXSCH group division information is indicated by DCI;

[0187] PXSCH groups are divided based on the number of PXSCH groups.

[0188] For details on the PXSCH grouping method, please refer to the corresponding description below.

[0189] Afterwards, based on the order between BWPs in the indicated scheduling BWP subset (see the corresponding description below for details), each PXSCH group is matched one by one with each scheduling BWP (before the one-to-one correspondence, the order between each PXSCH group can be determined based on the PXSCH contained in each PXSCH group; afterward, for the sorted scheduling BWP queue and PXSCH group queue, the scheduling BWP and PXSCH group with the same number / index in the two queues are matched one by one).

[0190] The following describes an implementation method for determining the resource allocation information corresponding to the N PXSCHs.

[0191] In some embodiments, the DCI is used to respectively indicate resource allocation information corresponding to each of the N PXSCHs;

[0192] or,

[0193] The DCI is used to jointly indicate resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0194] or,

[0195] The DCI is used to indicate the same resource allocation information for each of the N PXSCHs.

[0196] This implementation improves the flexibility of DCI indicating resource allocation information corresponding to each PXSCH.

[0197] Optionally, the DCI includes at least one of the following:

[0198] N third indication fields, where the N third indication fields are used to respectively indicate frequency domain resource allocation information corresponding to each of the N PXSCHs;

[0199] A fourth indication field, where the fourth indication field is used to jointly indicate frequency domain resource allocation information corresponding to each of the N PXSCHs;

[0200] N fifth indication fields, where the N fifth indication fields are used to respectively indicate time domain resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0201] The sixth indication field is used to jointly indicate the time domain resource allocation information corresponding to each PXSCH in the N PXSCHs.

[0202] Optionally, when each BWP corresponding to the N physical shared channels meets a predefined condition, the DCI is used to indicate the same resource allocation information for each PXSCH in the N PXSCHs;

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

[0204] The resource allocation type is the same;

[0205] SCS is the same;

[0206] CP is the same;

[0207] Indicator particle size is the same;

[0208] The number of physical resource blocks (PRBs) is equal;

[0209] The number of target frequency domain indicator objects is equal, and the number of target frequency domain indicator objects is determined based on the indication granularity and the number of PRBs in the activated BWP;

[0210] The number of rows contained in the corresponding Time Domain Resource Allocation (TDRA) table is equal;

[0211] Use the same TDRA form.

[0212] When the resource allocation type is resourceAllocationType0, the target frequency domain indication object can be a resource block group (RBG) (the indication granularity at this time can be understood as the RBG size); when the resource allocation type is resourceAllocationType1, the target frequency domain indication object can be a resource indicator value (RIV) (the indication granularity at this time can be understood as the indication step size of RIV).

[0213] Optionally, the DCI includes at least one of the following:

[0214] A seventh indication field, where the seventh indication field is used to indicate the same frequency domain resource allocation information for each of the N PXSCHs;

[0215] The eighth indication field is used to indicate the same time domain resource allocation information for each PXSCH in the N PXSCHs.

[0216] In the case where the N PXSCHs correspond to multiple activated BWPs, the number of bits in the seventh indication field is equal to the third number or the fourth number. Here, the third number is the maximum number of frequency domain resource allocation bits corresponding to the activated BWP that may schedule PXSCHs, and the fourth number is the maximum number of frequency domain resource allocation bits corresponding to the activated BWP that actually schedules PXSCHs.

[0217] In the case where the N PXSCHs correspond to multiple activated BWPs, the number of bits in the eighth indication field is equal to the fifth number or the sixth number. Here, the fifth number is the maximum number of time domain resource allocation bits corresponding to the activated BWP that may schedule PXSCHs, and the sixth number is the maximum number of time domain resource allocation bits corresponding to the activated BWP that actually schedules PXSCHs.

[0218] In some embodiments, when the DCI is used to indicate the same frequency domain resource allocation information for each of the N PXSCHs, and the terminal determines that the first target condition is met, the method further includes any one of the following:

[0219] The terminal selects, from the PRB numbers corresponding to the frequency domain resource allocation information, a PRB number within a first PRB number range, where the first PRB number range is a PRB number range corresponding to a first activated BWP;

[0220] The terminal performs modulo processing on the number of PRBs included in the first activated BWP by the PRB number corresponding to the frequency domain resource allocation information to obtain an available PRB number;

[0221] The terminal ignores the PXSCH corresponding to the first activated BWP;

[0222] The terminal ignores the DCI;

[0223] The first activated BWP is an activated BWP corresponding to at least one PXSCH among the N PXSCHs;

[0224] The first target condition includes:

[0225] Among the PRBs corresponding to the frequency domain resource allocation information, a PRB number of at least one PRB exceeds a maximum value of a PRB number of the first activated BWP.

[0226] When the above-mentioned first target condition is met, the frequency domain resource allocation information indicated by the DCI can be considered incompatible with the frequency domain resources corresponding to the first activated BWP. In addition to the above-mentioned incompatibility situations, other incompatibility situations may also exist. For example, when the BWP corresponding to at least one PXSCH among the N PXSCHs scheduled by the DCI (assuming it is called the target BWP) is configured or applied with different parameter values ​​from the BWPs corresponding to other PXSCHs (assuming it is called the remaining BWP) (assuming that for a given parameter, the target BWP is configured or applied with a value V1, and the other BWPs are configured or applied with a value V2, and V1 is different from or unequal to V2), and the DCI indicates the frequency domain resource allocation information based on the value V2 of the given parameter, the frequency domain resource allocation information indicated by the DCI can also be considered incompatible with the frequency domain resources corresponding to the target BWP. The given parameters here may include at least one of the following parameters: resource allocation type, SCS, CP, indication granularity, number of PRBs, and number of target frequency domain indication objects. Other incompatibility situations can be handled using solutions similar to this embodiment, and this embodiment of the present application is not limited to this.

[0227] Optionally, the terminal expects that the frequency domain resource allocation information indicated by the DCI is compatible with the frequency domain resources corresponding to any activated BWP corresponding to the N physical shared channels, that is, the terminal expects that there will be no incompatibility between the frequency domain resource allocation information indicated by the DCI and the frequency domain resources corresponding to any activated BWP corresponding to the N physical shared channels.

[0228] In some embodiments, when the DCI is used to indicate the same time domain resource allocation information for each of the N PXSCHs, and the terminal determines that the second target condition is met, the method further includes any one of the following:

[0229] The terminal performs a modulo process on the row index included in the time domain resource allocation information and the number of rows included in the first TDRA table to obtain an available row index; the first TDRA table is the TDRA table corresponding to the second activated BWP;

[0230] The terminal ignores the PXSCH corresponding to the second activated BWP;

[0231] The terminal ignores the DCI;

[0232] The second activated BWP is an activated BWP corresponding to at least one PXSCH among the N PXSCHs;

[0233] The second target condition includes:

[0234] The row index indicated by the time domain resource allocation information exceeds the maximum value of the row index of the first TDRA table.

[0235] When the above-mentioned second target condition is met, it can be considered that the time domain resource allocation information indicated by the DCI is incompatible with the time domain resources corresponding to the second activated BWP. In addition to the above-mentioned incompatibility situations, other incompatibility situations may also exist. For example, when the BWP corresponding to at least one PXSCH among the N PXSCHs scheduled by the DCI (assuming it is called the target BWP) is configured or applied with different parameter values ​​from the BWP corresponding to other PXSCHs (assuming it is called the remaining BWP) (assuming that for a given parameter, the target BWP is configured or applied with a value of V3, and the other BWPs are configured or applied with a value of V4, and V3 is different from or unequal to V4), and the DCI indicates the time domain resource allocation information based on the value V4 of the given parameter, it can also be considered that the time domain resource allocation information indicated by the DCI is incompatible with the time domain resources corresponding to the target BWP. The given parameters here may include at least one of the following parameters: SCS, CP, corresponding TDRA table, and the number of rows contained in the corresponding TDRA table. Other incompatibility situations can be handled using a scheme similar to this embodiment, and the embodiments of the present application are not limited to this.

[0236] Optionally, the terminal expects that the time domain resource allocation information indicated by the DCI is compatible with the time domain resources corresponding to any activated BWP corresponding to the N physical shared channels, that is, the terminal expects that there will be no incompatibility between the time domain resource allocation information indicated by the DCI and the time domain resources corresponding to any activated BWP corresponding to the N physical shared channels.

[0237] The following describes frequency domain resource allocation and time domain resource allocation respectively.

[0238] 1. Frequency Domain Resource Allocation

[0239] The terminal can determine whether each scheduled PXSCH is allocated valid frequency domain resources, and which valid frequency domain resources are actually allocated, based on the indication field / indication bit in the DCI and in combination with predefined rules and high-level signaling as needed. Specifically, the frequency domain resources can be allocated in any of the following frequency domain resource allocation methods 1 to 2:

[0240] Frequency domain resource allocation method 1: Indicate frequency domain resource allocation information for each scheduled PXSCH

[0241] Specifically, any of the following frequency domain resource allocation modes 1-1 to 1-2 may be used:

[0242] Frequency domain resource allocation mode 1-1: Use independent indication fields / indication bits to indicate the frequency domain resource allocation information corresponding to each scheduled PXSCH

[0243] The order between the indication fields / indication bits corresponding to the frequency domain resource allocation information corresponding to each scheduled PXSCH may be the order between multiple PXSCHs scheduled by a single DCI (see the corresponding description below); or, when receiving the DCI, the UE may know in advance that there are N indication fields / indication bits corresponding to frequency domain resource allocation information in each DCI (N may be specified by the protocol or configured by high-level signaling; the number of bits occupied by the indication field / indication bit corresponding to each frequency domain resource allocation information is also known in advance, for example, the number of bits occupied by the indication field / indication bit corresponding to each item of frequency domain resource allocation information is equal, which is M, and M may be specified by the protocol, or configured by high-level signaling, or based on at least one BWP (for example, Configured / Active The order of the scheduling PXSCHs corresponding to each item of frequency domain resource allocation information (or each item of valid frequency domain resource allocation information) can be determined based on the order of the indication fields / indication bits corresponding to the N items of frequency domain resource allocation information (or the indication fields / indication bits corresponding to the N1 items of valid frequency domain resource allocation information) in the DCI.

[0244] For example, assuming that the order of the indication domains / indication bits corresponding to the frequency domain resource allocation information corresponding to each scheduled PXSCH is the order between multiple PXSCHs scheduled by a single DCI (see the corresponding description below): when only case 2 is allowed, it can be arranged in ascending / descending order based on the frequency of the first / last / designated RB / RE occupied by the PXSCH, or the lowest / highest frequency corresponding to the occupied frequency domain resources; when only case 3 is allowed, it can be based on the order between the BWPs corresponding to the PXSCHs (see the corresponding description below for details); when case 4 is allowed, it can be based on the order between the BWPs corresponding to the PXSCHs (see the corresponding description below for details), and the PXSCHs corresponding to the same BWP can be arranged in ascending / descending order based on the frequency of the first / last / designated RB / RE occupied by the PXSCH, or the lowest / highest frequency corresponding to the occupied frequency domain resources.

[0245] The frequency domain resource allocation information corresponding to each scheduled PXSCH is determined based on the corresponding configuration parameters of the BWP corresponding to the corresponding scheduled PXSCH and the corresponding mechanism in NR, including the indication method (for example, Bitmap method or RIV method), the number of occupied bits (depending on the indication method, indication granularity, and the number of frequency domain resources in BWP), etc.

[0246] Frequency domain resource allocation mode 1-2: Using joint coding, the same indication field / indication bit is used to simultaneously indicate the frequency domain resource allocation information corresponding to each scheduled PXSCH.

[0247] For example, some frequency domain resource allocation combinations that are desired to be scheduled or preferred can be pre-defined or configured. A certain frequency domain resource allocation combination can indicate frequency domain resource allocation information on at least one BWP (including whether frequency domain resources are allocated on a given BWP, and when allocated, the actual allocated frequency domain resources, and / or the corresponding number of PXSCHs, etc.); the ID / index of the selected frequency domain resource allocation combination is then indicated using an indication field / indication bit in the scheduling DCI. The order between the frequency domain resource allocation information corresponding to each PXSCH in a certain frequency domain resource allocation combination can be the order between multiple PXSCHs scheduled by a single DCI (see the corresponding description below). For related examples, see the description of frequency domain resource allocation method 1-1; alternatively, for a certain frequency domain resource allocation combination indicated by the DCI, the order between the scheduled PXSCHs corresponding to each piece of frequency domain resource allocation information (or each piece of valid frequency domain resource allocation information) can be determined based on the configuration order between each piece of frequency domain resource allocation information (or each piece of valid frequency domain resource allocation information) in this frequency domain resource allocation combination.

[0248] For another example, only when multiple scheduled PXSCHs are located in a single BWP and the frequency domain resource allocation information is indicated in a Bitmap manner (for example, this BWP adopts resource allocation type 0), all adjacent RBGs indicated in the Bitmap correspond to the same PXSCH (that is, the number of scheduled PXSCHs is determined based on the number of RBG clusters indicated in the Bitmap, each RBG cluster corresponds one-to-one to a single scheduled PXSCH, and the frequency domain resource allocation of the corresponding scheduled PXSCH is determined by one or more RBGs corresponding to the RBG cluster; all RBGs whose corresponding bits have a value of 1 (or indicate that they need to be occupied) and whose bits are continuous constitute an RBG cluster).

[0249] Frequency domain resource allocation method 2: The same frequency domain resource allocation information is indicated for each scheduled PXSCH

[0250] It can be understood that the same frequency domain resource allocation information indicated by the indicator field / indication bit in the DCI is applied to each scheduled PXSCH respectively. When the scheduled PXSCH can correspond to multiple Active BWPs, the number of bits of the indicator field / indication bit here can be taken from each possible scheduling (that is, the range of the maximum value is the set of schedulable Active BWPs, which can be specified by the protocol or configured by high-level signaling) or actual scheduling (that is, the range of the maximum value is the set of actually scheduled Active BWPs, which is determined by the Active BWP corresponding to a certain DCI-scheduled PXSCH) The maximum value of the number of frequency domain resource allocation bits corresponding to the Active BWP of the corresponding PXSCH.

[0251] When the same frequency domain resource allocation information is incompatible with the frequency domain resources corresponding to a certain Active BWP actually scheduled (for example, based on the same frequency domain resource allocation information, at least one PRB number that needs to be occupied exceeds the maximum PRB number in this Active BWP), one of the following (a) to (e) can be used:

[0252] (a) Only PRBs whose PRB numbers are within the PRB number range of this Active BWP are used, that is, truncation is performed.

[0253] (b) The numbers of the PRBs to be occupied are modulo the number of PRBs included in the Active BWP to determine the PRB numbers to be used. Optionally, the UE assumes that the PRBs to be used do not conflict with each other (i.e., they do not need to be occupied more than once).

[0254] (c) The UE ignores the PXSCH scheduled on this Active BWP and only considers the PXSCH scheduled on the remaining Active BWPs.

[0255] (d) The UE ignores this DCI (i.e., ignores all PXSCHs scheduled by this DCI).

[0256] (e) The UE does not expect this situation to occur.

[0257] Optionally, frequency domain resource allocation mode 2 is allowed only when each of the potentially scheduled or actually scheduled Active BWPs meets predefined requirements. The predefined requirements here may include at least one of the following (a) to (d):

[0258] (a) The resource allocation types are the same, for example, resource allocation type 0 (resourceAllocationType0) / resource allocation type 1 (resourceAllocationType1) / dynamic switch (dynamicSwitch);

[0259] (b) SCS and / or CP are the same;

[0260] (c) The indication granularity is the same, for example, when the resource allocation type is resourceAllocationType0, the RBG size is equal, or when the resource allocation type is resourceAllocationType1, the RIV indication step size is equal;

[0261] (d) The number of PRBs in the Active BWP is equal, or the number of PRBs that can be indicated based on the indication granularity (which can also be understood as the total number that needs to be indicated, or the total number of candidate indications; for examples, see the corresponding description in the previous text) is equal.

[0262] 2. Time Domain Resource Allocation

[0263] The terminal can determine the time domain resources actually allocated to each scheduled PXSCH based on the indication field / indication bit in the DCI and in combination with predefined rules and high-level signaling as needed. Specifically, the time domain resources can be allocated in any of the following time domain resource allocation methods 1 to 2:

[0264] Time domain resource allocation method 1: Indicate time domain resource allocation information for each scheduled PXSCH

[0265] Specifically, any of the following time domain resource allocation modes 1-1 to 1-2 may be used:

[0266] Time domain resource allocation mode 1-1: Use independent indication fields / indication bits to indicate the time domain resource allocation information corresponding to each scheduled PXSCH

[0267] The order between the indication fields / indication bits corresponding to the time domain resource allocation information corresponding to each scheduled PXSCH may be the order between multiple PXSCHs scheduled by a single DCI (see the corresponding description below); or, when receiving the DCI, the UE may know in advance that there are N indication fields / indication bits corresponding to time domain resource allocation information in each DCI (N may be specified by the protocol or configured by high-level signaling; the number of bits occupied by the indication field / indication bit corresponding to each time domain resource allocation information is also known in advance, for example, the number of bits occupied by the indication field / indication bit corresponding to each item of time domain resource allocation information is equal, which is M, and M may be specified by the protocol, or configured by high-level signaling, or based on at least one BWP (for example, Reference in Configured / Active BWP). Based on the order of the indication fields / indication bits corresponding to the N items of time domain resource allocation information (or the indication fields / indication bits corresponding to the N1 items of valid time domain resource allocation information among the N items) (i.e. the front-to-back arrangement order in the DCI), the order of the scheduling PXSCHs corresponding to each item of time domain resource allocation information (or each item of valid time domain resource allocation information) can be determined.

[0268] For example, assuming that the order of the indication fields / indication bits corresponding to the time domain resource allocation information corresponding to each scheduled PXSCH is the order between multiple PXSCHs scheduled by a single DCI (see the corresponding description below): when only case 2 is allowed, it can be arranged in ascending / descending order based on the frequency of the first / last / designated RB / RE occupied by the PXSCH, or the lowest / highest frequency corresponding to the occupied frequency domain resources; when only case 3 is allowed, it can be based on the order between the BWPs corresponding to the PXSCHs (see the corresponding description below for details); when case 4 is allowed, it can be based on the order between the BWPs corresponding to the PXSCHs (see the corresponding description below for details), and the PXSCHs corresponding to the same BWP can be arranged in ascending / descending order based on the frequency of the first / last / designated RB / RE occupied by the PXSCH, or the lowest / highest frequency corresponding to the occupied frequency domain resources.

[0269] The time domain resource allocation information corresponding to each scheduled PXSCH is determined based on the corresponding configuration parameters of the BWP corresponding to the corresponding scheduled PXSCH and the corresponding mechanism in NR, including the indication method (for example, the row index in the TDRA table corresponding to the BWP), the number of occupied bits (depending on the number of rows configured in the TDRA table corresponding to the BWP, or explicitly configured by high-level signaling), etc.

[0270] Time domain resource allocation mode 1-2: Using joint coding, the same indication field / indication bit is used to indicate the time domain resource allocation information corresponding to each scheduled PXSCH at the same time.

[0271] For example, some time domain resource allocation combinations that are desired to be scheduled or preferred can be pre-defined or configured. A certain time domain resource allocation combination can indicate time domain resource allocation information on at least one BWP (including whether time domain resources are allocated on a given BWP, and when allocated, the actual allocated time domain resources, and / or the corresponding number of PXSCHs, etc.); the ID / index of the selected time domain resource allocation combination is then indicated using an indication field / indication bit in the scheduling DCI. The order between the time domain resource allocation information corresponding to each PXSCH in a certain time domain resource allocation combination can be the order between multiple PXSCHs scheduled by a single DCI (see the corresponding description below). For related examples, see the description of time domain resource allocation method 1-1; alternatively, for a certain time domain resource allocation combination indicated by the DCI, the order between the scheduled PXSCHs corresponding to each time domain resource allocation information (or each valid time domain resource allocation information) can be determined based on the configuration order between each time domain resource allocation information (or each valid time domain resource allocation information) in this time domain resource allocation combination.

[0272] Time domain resource allocation mode 2: Indicate the same time domain resource allocation information for each scheduled PXSCH

[0273] It can be understood that the same time domain resource allocation information indicated by the indicator field / indication bit in the DCI is applied to each scheduled PXSCH respectively. When the scheduled PXSCH can correspond to multiple Active BWPs, the number of bits of the indicator field / indication bit here can be taken from each possible scheduling (that is, the range of the maximum value is the set of schedulable Active BWPs, which can be specified by the protocol or configured by high-level signaling) or actual scheduling (that is, the range of the maximum value is the set of actually scheduled Active BWPs, which is determined by the Active BWP corresponding to a certain DCI-scheduled PXSCH) The maximum value of the number of time domain resource allocation bits corresponding to the Active BWP of the corresponding PXSCH.

[0274] When the same time domain resource allocation information is incompatible with the time domain resource configuration corresponding to a certain Active BWP actually scheduled (for example, the Row Index indicated by the same time domain resource allocation information exceeds the maximum Row Index in the TDRA table corresponding to the Active BWP), one of the following options (a) to (d) may be used:

[0275] (a) Modulo the indicated row index with the number of rows in the TDRA table corresponding to this Active BWP to determine the final row index to be used.

[0276] (b) The UE ignores the PXSCH scheduled on this Active BWP and only considers the PXSCH scheduled on the remaining Active BWPs.

[0277] (c) The UE ignores this DCI (i.e., ignores all PXSCHs scheduled by this DCI).

[0278] (d) The UE does not expect this situation to occur.

[0279] Optionally, time domain resource allocation mode 2 is allowed only when each of the potentially schedulable or actually scheduled Active BWPs meets predefined requirements. The predefined requirements here may include at least one of the following (a) to (c):

[0280] (a) The SCS and / or CP are the same;

[0281] (b) The number of rows contained in the corresponding TDRA table is equal;

[0282] (c) Use the same TDRA table.

[0283] The PXSCH grouping method is explained below.

[0284] When grouping multiple PXSCHs scheduled by a single DCI, at least one of the following PXSCH grouping methods 1 to 4 may be used:

[0285] PXSCH grouping method 1: PXSCH groups are divided based on the (maximum) number of PXSCHs contained in a single PXSCH group

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

[0287] PXSCH grouping method 2: PXSCH groups are divided based on the satisfaction of predefined conditions

[0288] Based on the different predefined conditions met, one or more PXSCHs that meet a certain predefined condition or a combination of predefined conditions are divided into the same PXSCH group.

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

[0290] For another example, when the predefined condition is "located in time slot (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).

[0291] Other predefined conditions are not given as examples one by one.

[0292] When determining the order between the divided PXSCH groups, one of the following (a) to (b) may be used:

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

[0294] (b) The order between these 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 PXSCH groups correspond to the predefined conditions "SCS is 15kHz" and "SCS is 30kHz" respectively, the PXSCH group corresponding to the predefined condition "SCS is 15kHz" can be arranged before the PXSCH group corresponding to the predefined condition "SCS is 30kHz" in ascending order of SCS values. When grouping based on a combination of predefined conditions, only a single or part of the predefined conditions in this combination can be used, or all the predefined conditions can be used to determine the order between the PXSCH groups. When multiple predefined conditions are involved, each of the multiple predefined conditions can be used in sequence according to the predefined order; the predefined order here can be the traversal order of all predefined conditions that may be involved and uniformly stipulated or configured, or the order in which each predefined condition appears in the combination, etc.

[0295] PXSCH grouping mode 3: PXSCH group division information is indicated by DCI

[0296] Specifically, one of the following PXSCH grouping modes 3-1 to 3-3 may be used:

[0297] PXSCH grouping mode 3-1: There is 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 PXSCH group division.

[0298] For example, when time domain resource allocation method 1-2 is adopted, there is PXSCH group division information in each pre-defined or configured time domain resource allocation combination, and the group division of PXSCH corresponding to this time domain resource allocation combination can be determined based on this information.

[0299] PXSCH grouping mode 3-2: The HARQ process corresponding to each PXSCH is indicated in the DCI separately. At least one PXSCH corresponding to the same HARQ process is classified into the same PXSCH group and uses this HARQ process.

[0300] PXSCH grouping mode 3-3: Independently indicate PXSCH group division information in DCI

[0301] A new indication field may be introduced, or the reserved indication field / padding bit in the existing indication field / DCI may be reinterpreted. The indicated PXSCH group division information may be one of the following PXSCH grouping modes 3-3-1 to 3-3-2:

[0302] PXSCH grouping method 3-3-1: indicating the boundaries of adjacent PXSCH groups in DCI

[0303] Assuming that each PXSCH group corresponds to a PXSCH with a continuous number / index (the determination of the order between PXSCHs can be found in the previous description and will not be repeated here; based on the determined order, the number / index corresponding to each PXSCH can be determined), then the number / index of the first / last PXSCH in each PXSCH group can be indicated in sequence (for example, in order of the PXSCH group number / index from small to large). Optionally, the information of the last PXSCH group can be omitted and derived based on all PXSCHs scheduled by this DCI and the indication information of other previous PXSCH groups.

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

[0305] PXSCH grouping method 3-3-2: Indicate the number of PXSCHs contained in each PXSCH group in the DCI

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

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

[0308] PXSCH grouping method 4: PXSCH group division based on the number of PXSCH groups

[0309] This assumes that the number of PXSCH groups is known, for example, as specified by the protocol, configured by higher-layer signaling, or explicitly indicated by the DCI. In this case, all PXSCHs scheduled by a single DCI can be evenly (or as evenly as possible) divided into N PXSCH groups. For example, assuming a DCI schedules M PXSCHs, then for the first N1 = M mod N PXSCH groups, each PXSCH group contains ceiling(M / N) PDSCHs, and for the next N2 = N – N1 PXSCH groups, each PXSCH group contains floor(M / N) PXSCHs (or, the first N2 groups each contain floor(M / N) PXSCHs, and the next N1 groups each contain ceiling(M / N) PXSCHs), where floor() indicates rounding down. When M is divisible by N, each PXSCH group contains M / N PXSCHs. This requires that M > 0 and N > 0.

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

[0311] The following describes the method for determining the order between multiple PXSCHs scheduled by a single DCI (referred to as PXSCH order) and the method for determining the order between BWPs (referred to as BWP order).

[0312] In some embodiments, the PXSCH order of the N PXSCHs is determined based on at least one of the following:

[0313] The second information included in the DCI is used to indicate the BWP corresponding to each PXSCH in the N PXSCHs;

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

[0315] The BWP sequence corresponding to each PXSCH in the N PXSCHs;

[0316] The starting time of each PXSCH in the N PXSCHs;

[0317] The end time of each PXSCH in the N PXSCHs;

[0318] The frequency of the frequency domain resources of each PXSCH in the N PXSCHs;

[0319] The HARQ process occupied by each PXSCH in the N PXSCHs;

[0320] The effective code rate of each PXSCH among the N PXSCHs.

[0321] Specifically, the order between multiple PXSCHs scheduled by a single DCI may be determined based on at least one of the following (a) to (g):

[0322] (a) PXSCH order determined in the scheduling BWP indication. For example, when the scheduling BWP indication method 1 is used, the order of the corresponding PXSCH can be determined based on the order of each BWP ID / index indication field / indication bit in the DCI.

[0323] (b) The order of PXSCHs determined in the frequency domain resource allocation and / or time domain resource allocation. For example, when frequency domain resource allocation mode 1-1 and / or time domain resource allocation mode 1-1 is adopted, the order of the corresponding PXSCHs can be determined based on the order of the indication fields / indication bits in the DCI; when frequency domain resource allocation mode 1-2 and / or time domain resource allocation mode 1-2 is adopted, the order of the corresponding PXSCHs can be determined based on the order of the allocation information in the frequency domain resource allocation combination and / or time domain resource allocation combination indicated in the DCI.

[0324] (c) Based on the order of the BWPs corresponding to the PXSCHs (see the corresponding description above for details). It is assumed here that at least one PXSCH corresponds to a different BWP than the remaining PXSCHs.

[0325] (d) Arrange in ascending / descending order based on the start / end time of PXSCH.

[0326] (e) Arrange in ascending / descending order based on the frequency of the first / last / designated RB / RE occupied by PXSCH, or the lowest / highest frequency corresponding to the occupied frequency domain resources.

[0327] (f) Arrange the HARQ processes in ascending / descending order based on the PXSCH occupation.

[0328] (g) Arrange in ascending / descending order based on the effective code rate of PXSCH.

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

[0330] BWP logo;

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

[0332] The order of the BWPs in the predefined BWP subset;

[0333] The DCI indicates the order of BWPs.

[0334] Specifically, the order between BWPs may be determined based on at least one of the following (a) to (d):

[0335] (a) Sort in ascending / descending order based on the BWP index / ID corresponding to the BWP.

[0336] (b) 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 PRB with the lowest / highest frequency configured for the BWP in the CRB grid of the serving cell.

[0337] (c) When all BWPs to be sorted are in the same predefined BWP subset, based on the prescribed / configured order of the BWPs contained in this predefined BWP subset; see the corresponding description in BWP subset indication method 2.

[0338] (d) When all BWPs to be sorted are directly indicated by the same DCI, based on the indication order in the DCI (i.e., the order of arrangement of the BWP ID / index indication fields in the DCI); see the corresponding description in BWP subset indication method 3.

[0339] The embodiments of the present application provide specific and feasible solutions for the scenario where a single DCI schedules multiple physical shared channels that may (or are allowed to) be transmitted in parallel in a given transmission direction within the same serving cell, in key aspects such as home BWP determination, frequency domain resource allocation, and time domain resource allocation, thereby making full use of the cell's frequency domain resources, improving data throughput, and reducing transmission latency.

[0340] In summary, the embodiments of the present application can improve the flexibility of physical shared channel scheduling and reduce the scheduling overhead of physical shared channels. Furthermore, the terminal can determine the BWP or resource allocation information corresponding to N physical shared channels based on the DCI, thereby enabling data transmission through the N physical shared channels. This can fully utilize the frequency domain resources of the cell, improve data throughput, and reduce transmission latency.

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

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

[0343] Step 501: A network-side device sends a DCI to a terminal, where the DCI is used to schedule N physical shared channels, where all of the N physical shared channels are PUSCHs, or all of the N physical shared channels are PDSCHs, where N is an integer greater than 1.

[0344] The DCI is used to determine at least one of the following:

[0345] The bandwidth part BWP corresponding to the N PXSCHs;

[0346] The resource allocation information corresponding to the N PXSCHs includes at least one of frequency domain resource allocation information and time domain resource allocation information.

[0347] Optionally, the DCI is used to schedule N PXSCHs, including any of the following:

[0348] The DCI is used to schedule N PXSCHs within a single BWP;

[0349] The DCI is used to schedule N PXSCHs within N BWPs;

[0350] The DCI is used to schedule N PXSCHs within M BWPs, where M is an integer less than N.

[0351] Optionally, in the case where the DCI is used to schedule N PXSCHs within N BWPs, the DCI includes first information, where the first information is used to indicate a first BWP subset, or to indicate a first BWP in a first BWP subset, where the first BWP subset is a BWP subset including N BWPs.

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

[0353] a first bitmap, where the first bitmap is used to indicate the first BWP subset;

[0354] a first subset identifier, where the first subset identifier is used to indicate the first BWP subset, and the first BWP subset is a BWP subset in a predefined BWP subset list;

[0355] N BWP identifiers, the first BWP subset includes N BWPs corresponding to the N BWP identifiers;

[0356] A first BWP identifier is used to indicate the first BWP.

[0357] Optionally, the first BWP identifier is an identifier of a predefined BWP in the first BWP subset, and the predefined BWP includes any one of the following:

[0358] BWP identifies the smallest BWP;

[0359] BWP identifies the largest BWP;

[0360] The BWP corresponding to the PXSCH at the predefined position among the N PXSCHs.

[0361] Optionally, when the DCI is used to schedule N PXSCHs within M BWPs, the DCI includes any one of the following:

[0362] Second information, where the second information is used to indicate a BWP corresponding to each of the N PXSCHs;

[0363] Third and fourth information;

[0364] Third and fifth information;

[0365] The third information and the grouping information of the N PXSCHs;

[0366] The third information is used to indicate the second BWP subset, or is used to indicate the second BWP in the second BWP subset, where the second BWP subset is a BWP subset including M BWPs;

[0367] The fourth information is used to indicate the PXSCH corresponding to each BWP in the second BWP subset;

[0368] The fifth information is used to indicate the correspondence between each PXSCH in the N PXSCHs and each BWP in the second BWP subset.

[0369] Optionally, the second information includes at least one of the following:

[0370] N first indication fields, where the N first indication fields are used to respectively indicate the BWP corresponding to each of the N PXSCHs;

[0371] The second indication field is used to jointly indicate the BWP corresponding to each PXSCH in the N PXSCHs.

[0372] Optionally, the fourth information includes:

[0373] M second bitmaps, where the M second bitmaps are used to respectively indicate the PXSCH corresponding to each BWP in the second BWP subset;

[0374] or,

[0375] The fifth information includes:

[0376] The third bit map, each K bits of the third bit map are used to respectively indicate the BWP corresponding to each PXSCH in the N PXSCHs, and K is an integer greater than or equal to 1.

[0377] Optionally, the DCI is used to respectively indicate resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0378] or,

[0379] The DCI is used to jointly indicate resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0380] or,

[0381] The DCI is used to indicate the same resource allocation information for each of the N PXSCHs.

[0382] Optionally, the DCI includes at least one of the following:

[0383] N third indication fields, where the N third indication fields are used to respectively indicate frequency domain resource allocation information corresponding to each of the N PXSCHs;

[0384] A fourth indication field, where the fourth indication field is used to jointly indicate frequency domain resource allocation information corresponding to each of the N PXSCHs;

[0385] N fifth indication fields, where the N fifth indication fields are used to respectively indicate time domain resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0386] The sixth indication field is used to jointly indicate the time domain resource allocation information corresponding to each PXSCH in the N PXSCHs.

[0387] Optionally, the DCI includes at least one of the following:

[0388] A seventh indication field, where the seventh indication field is used to indicate the same frequency domain resource allocation information for each of the N PXSCHs;

[0389] The eighth indication field is used to indicate the same time domain resource allocation information for each PXSCH in the N PXSCHs.

[0390] Optionally, the frequency domain resource allocation information indicated by the DCI is compatible with the frequency domain resources corresponding to any activated BWP corresponding to the N physical shared channels.

[0391] Optionally, the time domain resource allocation information indicated by the DCI is compatible with the time domain resources corresponding to any activated BWP corresponding to the N physical shared channels.

[0392] Optionally, when each BWP corresponding to the N physical shared channels meets a predefined condition, the DCI is used to indicate the same resource allocation information for each PXSCH in the N PXSCHs;

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

[0394] The resource allocation type is the same;

[0395] The subcarrier spacing SCS is the same;

[0396] The cyclic prefix CP is the same;

[0397] Indicator particle size is the same;

[0398] The number of physical resource blocks (PRBs) is equal;

[0399] The number of target frequency domain indicator objects is equal, and the number of target frequency domain indicator objects is determined based on the indication granularity and the number of PRBs in the activated BWP;

[0400] The number of rows contained in the corresponding TDRA tables is equal;

[0401] Use the same TDRA form.

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

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

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

[0405] 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, where the N physical shared channels are all PUSCHs, or where the N physical shared channels are all PDSCHs, where N is an integer greater than or equal to 1.

[0406] A first processing unit 602 is configured to perform a target operation based on the DCI;

[0407] The target operation includes at least one of the following:

[0408] Determine the bandwidth part BWP corresponding to the N PXSCHs;

[0409] Determine resource allocation information corresponding to the N PXSCHs, where the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

[0410] Optionally, the DCI is used to schedule N PXSCHs, including any of the following:

[0411] The DCI is used to schedule N PXSCHs within a single BWP;

[0412] The DCI is used to schedule N PXSCHs within N BWPs;

[0413] The DCI is used to schedule N PXSCHs within M BWPs, where M is an integer less than N.

[0414] Optionally, in a case where the DCI is used to schedule N PXSCHs within N BWPs, the DCI includes first information, where the first information is used to indicate a first BWP subset, or used to indicate a first BWP in a first BWP subset, where the first BWP subset is a BWP subset including N BWPs;

[0415] The first processing unit 602 is specifically configured to:

[0416] Determine the N BWPs included in the first BWP subset indicated by the first information as the BWPs of the N PXSCHs;

[0417] Based on the first BWP indicated by the first information and the first rule, a first BWP subset is determined, and the N BWPs included in the determined first BWP subset are determined as the BWPs of the N PXSCHs; wherein the first rule is predefined by the protocol or configured by the network or indicated by the DCI.

[0418] Optionally, the first processing unit 602 is further configured to:

[0419] Based on the BWP order of the first BWP subset, the correspondence between each PXSCH in the N PXSCHs and each BWP in the first BWP subset is determined.

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

[0421] a first bitmap, where the first bitmap is used to indicate the first BWP subset;

[0422] a first subset identifier, where the first subset identifier is used to indicate the first BWP subset, and the first BWP subset is a BWP subset in a predefined BWP subset list;

[0423] N BWP identifiers, the first BWP subset includes N BWPs corresponding to the N BWP identifiers;

[0424] A first BWP identifier is used to indicate the first BWP.

[0425] Optionally, the first BWP identifier is an identifier of a predefined BWP in the first BWP subset, and the first rule includes at least one of the number of BWPs, an increasing step, and a decreasing step;

[0426] The predefined BWP includes any of the following:

[0427] BWP identifies the smallest BWP;

[0428] BWP identifies the largest BWP;

[0429] The BWP corresponding to the PXSCH at the predefined position among the N PXSCHs.

[0430] Optionally, when the DCI is used to schedule N PXSCHs within M BWPs, the first processing unit 602 is specifically configured to perform any of the following:

[0431] Determine, according to the second information included in the DCI, a BWP corresponding to each PXSCH of the N PXSCHs;

[0432] Determine, according to the third information and the fourth information included in the DCI, a BWP corresponding to each PXSCH in the N PXSCHs;

[0433] Determine, according to the third information and the fifth information included in the DCI, a BWP corresponding to each PXSCH in the N PXSCHs;

[0434] Determine, according to the third information included in the DCI and S PXSCH groups, a BWP corresponding to each PXSCH group of the S PXSCH groups, where the S PXSCH groups are obtained by grouping the N PXSCHs, and S is an integer greater than or equal to 1 and less than or equal to N;

[0435] The second information is used to indicate the BWP corresponding to each PXSCH in the N PXSCHs;

[0436] The third information is used to indicate the second BWP subset, or is used to indicate the second BWP in the second BWP subset, where the second BWP subset is a BWP subset including M BWPs;

[0437] The fourth information is used to indicate the PXSCH corresponding to each BWP in the second BWP subset;

[0438] The fifth information is used to indicate the correspondence between each PXSCH in the N PXSCHs and each BWP in the second BWP subset.

[0439] Optionally, the second information includes at least one of the following:

[0440] N first indication fields, where the N first indication fields are used to respectively indicate the BWP corresponding to each of the N PXSCHs;

[0441] The second indication field is used to jointly indicate the BWP corresponding to each PXSCH in the N PXSCHs.

[0442] Optionally, the fourth information includes:

[0443] M second bitmaps, where the M second bitmaps are used to respectively indicate the PXSCH corresponding to each BWP in the second BWP subset.

[0444] Optionally, the fifth information includes:

[0445] The third bit map, each K bits of the third bit map are used to respectively indicate the BWP corresponding to each PXSCH in the N PXSCHs, and K is an integer greater than or equal to 1.

[0446] Optionally, determining the BWP corresponding to each of the S PXSCH groups according to the third information included in the DCI and the S PXSCH groups includes:

[0447] Based on the BWP order of the second BWP subset and the order of each PXSCH group, the BWP corresponding to each PXSCH group is determined.

[0448] Optionally, the device further comprises:

[0449] A second processing unit is configured to group the N PXSCHs based on a second rule to obtain the S physical shared channel groups;

[0450] The second rule includes at least one of the following:

[0451] The number of PXSCHs in a preset single PXSCH group;

[0452] Predefined conditions;

[0453] Grouping information indicated by DCI;

[0454] The preset number of PXSCH groups.

[0455] Optionally, the DCI is used to respectively indicate resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0456] or,

[0457] The DCI is used to jointly indicate resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0458] or,

[0459] The DCI is used to indicate the same resource allocation information for each of the N PXSCHs.

[0460] Optionally, the DCI includes at least one of the following:

[0461] N third indication fields, where the N third indication fields are used to respectively indicate frequency domain resource allocation information corresponding to each of the N PXSCHs;

[0462] A fourth indication field, where the fourth indication field is used to jointly indicate frequency domain resource allocation information corresponding to each of the N PXSCHs;

[0463] N fifth indication fields, where the N fifth indication fields are used to respectively indicate time domain resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0464] The sixth indication field is used to jointly indicate the time domain resource allocation information corresponding to each PXSCH in the N PXSCHs.

[0465] Optionally, the DCI includes at least one of the following:

[0466] A seventh indication field, where the seventh indication field is used to indicate the same frequency domain resource allocation information for each of the N PXSCHs;

[0467] The eighth indication field is used to indicate the same time domain resource allocation information for each PXSCH in the N PXSCHs.

[0468] Optionally, the device further comprises:

[0469] The third processing unit is configured to, when the DCI is used to indicate the same frequency domain resource allocation information for each of the N PXSCHs and the terminal determines that the first target condition is met, perform any one of the following:

[0470] Selecting, from the physical resource block PRB numbers corresponding to the frequency domain resource allocation information, a PRB number within a first PRB number range, where the first PRB number range is a PRB number range corresponding to a first activated BWP;

[0471] Performing a modulo process on the number of PRBs included in the first activated BWP by the PRB number corresponding to the frequency domain resource allocation information to obtain an available PRB number;

[0472] Ignore the PXSCH corresponding to the first activated BWP;

[0473] Ignore the DCI;

[0474] The first activated BWP is an activated BWP corresponding to at least one PXSCH among the N PXSCHs;

[0475] The first target condition includes:

[0476] Among the PRBs corresponding to the frequency domain resource allocation information, a PRB number of at least one PRB exceeds a maximum value of a PRB number of the first activated BWP.

[0477] Optionally, the terminal expects that the frequency domain resource allocation information indicated by the DCI is compatible with the frequency domain resources corresponding to any activated BWP corresponding to the N physical shared channels.

[0478] Optionally, the device further comprises:

[0479] The fourth processing unit is configured to, when the DCI is used to indicate the same time domain resource allocation information for each PXSCH in the N PXSCHs, and the terminal determines that the second target condition is met, perform any one of the following:

[0480] Performing a modulo process on the row index included in the time domain resource allocation information and the number of rows included in the first time domain resource allocation TDRA table to obtain an available row index; the first TDRA table is the TDRA table corresponding to the second activated BWP;

[0481] Ignore the PXSCH corresponding to the second activated BWP;

[0482] Ignore the DCI;

[0483] The second activated BWP is an activated BWP corresponding to at least one PXSCH among the N PXSCHs;

[0484] The second target condition includes:

[0485] The row index indicated by the time domain resource allocation information exceeds the maximum value of the row index of the first TDRA table.

[0486] Optionally, the terminal expects that the time domain resource allocation information indicated by the DCI is compatible with the time domain resources corresponding to any activated BWP corresponding to the N physical shared channels.

[0487] Optionally, when each BWP corresponding to the N physical shared channels meets a predefined condition, the DCI is used to indicate the same resource allocation information for each PXSCH in the N PXSCHs;

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

[0489] The resource allocation type is the same;

[0490] The subcarrier spacing SCS is the same;

[0491] The cyclic prefix CP is the same;

[0492] Indicator particle size is the same;

[0493] The number of PRBs is equal;

[0494] The number of target frequency domain indicator objects is equal, and the number of target frequency domain indicator objects is determined based on the indication granularity and the number of PRBs in the activated BWP;

[0495] The number of rows contained in the corresponding TDRA tables is equal;

[0496] Use the same TDRA form.

[0497] Optionally, the PXSCH order of the N PXSCHs is determined based on at least one of the following:

[0498] The second information included in the DCI is used to indicate the BWP corresponding to each PXSCH in the N PXSCHs;

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

[0500] The BWP sequence corresponding to each PXSCH in the N PXSCHs;

[0501] The starting time of each PXSCH in the N PXSCHs;

[0502] The end time of each PXSCH in the N PXSCHs;

[0503] The frequency of the frequency domain resources of each PXSCH in the N PXSCHs;

[0504] The HARQ process occupied by each PXSCH in the N PXSCHs;

[0505] The effective code rate of each PXSCH among the N PXSCHs.

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

[0507] BWP logo;

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

[0509] The order of the BWPs in the predefined BWP subset;

[0510] The DCI indicates the order of BWPs.

[0511] In summary, the embodiments of the present application can improve the flexibility of physical shared channel scheduling and reduce the scheduling overhead of physical shared channels. Furthermore, the terminal can determine the BWP or resource allocation information corresponding to N physical shared channels based on the DCI, thereby enabling data transmission through the N physical shared channels. This can fully utilize the frequency domain resources of the cell, improve data throughput, and reduce transmission latency.

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

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

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

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

[0516] 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, where the N physical shared channels are all PUSCHs, or where the N physical shared channels are all PDSCHs, where N is an integer greater than 1;

[0517] The DCI is used to determine at least one of the following:

[0518] The bandwidth part BWP corresponding to the N PXSCHs;

[0519] The resource allocation information corresponding to the N PXSCHs includes at least one of frequency domain resource allocation information and time domain resource allocation information.

[0520] Optionally, the DCI is used to schedule N PXSCHs, including any of the following:

[0521] The DCI is used to schedule N PXSCHs within a single BWP;

[0522] The DCI is used to schedule N PXSCHs within N BWPs;

[0523] The DCI is used to schedule N PXSCHs within M BWPs, where M is an integer less than N.

[0524] Optionally, in the case where the DCI is used to schedule N PXSCHs within N BWPs, the DCI includes first information, where the first information is used to indicate a first BWP subset, or to indicate a first BWP in a first BWP subset, where the first BWP subset is a BWP subset including N BWPs.

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

[0526] a first bitmap, where the first bitmap is used to indicate the first BWP subset;

[0527] a first subset identifier, where the first subset identifier is used to indicate the first BWP subset, and the first BWP subset is a BWP subset in a predefined BWP subset list;

[0528] N BWP identifiers, the first BWP subset includes N BWPs corresponding to the N BWP identifiers;

[0529] A first BWP identifier is used to indicate the first BWP.

[0530] Optionally, the first BWP identifier is an identifier of a predefined BWP in the first BWP subset, and the predefined BWP includes any one of the following:

[0531] BWP identifies the smallest BWP;

[0532] BWP identifies the largest BWP;

[0533] The BWP corresponding to the PXSCH at the predefined position among the N PXSCHs.

[0534] Optionally, when the DCI is used to schedule N PXSCHs within M BWPs, the DCI includes any one of the following:

[0535] Second information, where the second information is used to indicate a BWP corresponding to each of the N PXSCHs;

[0536] Third and fourth information;

[0537] Third and fifth information;

[0538] The third information and the grouping information of the N PXSCHs;

[0539] The third information is used to indicate the second BWP subset, or is used to indicate the second BWP in the second BWP subset, where the second BWP subset is a BWP subset including M BWPs;

[0540] The fourth information is used to indicate the PXSCH corresponding to each BWP in the second BWP subset;

[0541] The fifth information is used to indicate the correspondence between each PXSCH in the N PXSCHs and each BWP in the second BWP subset.

[0542] Optionally, the second information includes at least one of the following:

[0543] N first indication fields, where the N first indication fields are used to respectively indicate the BWP corresponding to each of the N PXSCHs;

[0544] The second indication field is used to jointly indicate the BWP corresponding to each PXSCH in the N PXSCHs.

[0545] Optionally, the fourth information includes:

[0546] M second bitmaps, where the M second bitmaps are used to respectively indicate the PXSCH corresponding to each BWP in the second BWP subset.

[0547] Optionally, the fifth information includes:

[0548] The third bit map, each K bits of the third bit map are used to respectively indicate the BWP corresponding to each PXSCH in the N PXSCHs, and K is an integer greater than or equal to 1.

[0549] Optionally, the DCI is used to respectively indicate resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0550] or,

[0551] The DCI is used to jointly indicate resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0552] or,

[0553] The DCI is used to indicate the same resource allocation information for each of the N PXSCHs.

[0554] Optionally, the DCI includes at least one of the following:

[0555] N third indication fields, where the N third indication fields are used to respectively indicate frequency domain resource allocation information corresponding to each of the N PXSCHs;

[0556] A fourth indication field, where the fourth indication field is used to jointly indicate frequency domain resource allocation information corresponding to each of the N PXSCHs;

[0557] N fifth indication fields, where the N fifth indication fields are used to respectively indicate time domain resource allocation information corresponding to each PXSCH in the N PXSCHs;

[0558] The sixth indication field is used to jointly indicate the time domain resource allocation information corresponding to each PXSCH in the N PXSCHs.

[0559] Optionally, the DCI includes at least one of the following:

[0560] A seventh indication field, where the seventh indication field is used to indicate the same frequency domain resource allocation information for each of the N PXSCHs;

[0561] The eighth indication field is used to indicate the same time domain resource allocation information for each PXSCH in the N PXSCHs.

[0562] Optionally, the frequency domain resource allocation information indicated by the DCI is compatible with the frequency domain resources corresponding to any activated BWP corresponding to the N physical shared channels.

[0563] Optionally, the time domain resource allocation information indicated by the DCI is compatible with the time domain resources corresponding to any activated BWP corresponding to the N physical shared channels.

[0564] Optionally, when each BWP corresponding to the N physical shared channels meets a predefined condition, the DCI is used to indicate the same resource allocation information for each PXSCH in the N PXSCHs;

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

[0566] The resource allocation type is the same;

[0567] The subcarrier spacing SCS is the same;

[0568] The cyclic prefix CP is the same;

[0569] Indicator particle size is the same;

[0570] The number of physical resource blocks (PRBs) is equal;

[0571] The number of target frequency domain indicator objects is equal, and the number of target frequency domain indicator objects is determined based on the indication granularity and the number of PRBs in the activated BWP;

[0572] The number of rows contained in the corresponding TDRA tables is equal;

[0573] Use the same TDRA form.

[0574] In summary, the embodiments of the present application can improve the flexibility of physical shared channel scheduling and reduce the scheduling overhead of physical shared channels. Furthermore, the terminal can determine the BWP or resource allocation information corresponding to N physical shared channels based on the DCI, thereby enabling data transmission through the N physical shared channels. This can fully utilize the frequency domain resources of the cell, improve data throughput, and reduce transmission latency.

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

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

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

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

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

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

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

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

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

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

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

[0586] receiving 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 PUSCHs, or where the N physical shared channels are all PDSCHs, where N is an integer greater than or equal to 1;

[0587] The processor 910 is configured to:

[0588] Based on the DCI, performing a target operation;

[0589] The target operation includes at least one of the following:

[0590] Determine the bandwidth part BWP corresponding to the N PXSCHs;

[0591] Determine resource allocation information corresponding to the N PXSCHs, where the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

[0592] In an embodiment of the present application, for a single cell formed by the aggregation of multiple discrete spectrums, N PXSCHs can be scheduled by a single DCI, so as to fully utilize the frequency domain resources of the cell, improve data throughput, and reduce transmission delay; and the terminal can determine the BWP or resource allocation information corresponding to the N PXSCHs based on the DCI, so that the terminal can transmit data.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0608] 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 performs a target operation based on the DCI; The target operation includes at least one of the following: Determine a bandwidth part BWP corresponding to the N physical shared channels; Resource allocation information corresponding to the N physical shared channels is determined, where the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

2. The method according to claim 1, wherein The DCI is used to schedule N physical shared channels, including any of the following: The DCI is used to schedule N physical shared channels within a single BWP; The DCI is used to schedule N physical shared channels within N BWPs; The DCI is used to schedule N physical shared channels within M BWPs, where M is an integer less than N.

3. The method according to claim 2, wherein: In a case where the DCI is used to schedule N physical shared channels within N BWPs, the DCI includes first information, where the first information is used to indicate a first BWP subset, or the first information is used to indicate a first BWP in a first BWP subset, where the first BWP subset is a BWP subset including N BWPs; The determining the BWP corresponding to the N physical shared channels includes any one of the following: Determine the N BWPs included in the first BWP subset indicated by the first information as BWPs of the N physical shared channels; Based on the first BWP indicated by the first information and a first rule, a first BWP subset is determined, and the N BWPs included in the determined first BWP subset are determined as the BWPs of the N physical shared channels; wherein the first rule is predefined by a protocol or configured by a network or indicated by the DCI.

4. The method according to claim 3, wherein determining the BWPs corresponding to the N physical shared channels further comprises: Based on the BWP sequence of the first BWP subset, a correspondence between each physical shared channel in the N physical shared channels and each BWP in the first BWP subset is determined.

5. The method according to claim 3 or 4, wherein: The first information includes at least one of the following: a first bitmap, where the first bitmap is used to indicate the first BWP subset; a first subset identifier, where the first subset identifier is used to indicate the first BWP subset, and the first BWP subset is a BWP subset in a predefined BWP subset list; N BWP identifiers, the first BWP subset includes N BWPs corresponding to the N BWP identifiers; A first BWP identifier is used to indicate the first BWP.

6. The method according to claim 5, wherein: The first BWP identifier is an identifier of a predefined BWP in the first BWP subset, and the first rule includes at least one of a number of BWPs, an incrementing step, and a decrementing step; The predefined BWP includes any of the following: BWP identifies the smallest BWP; BWP identifies the largest BWP; The BWP corresponding to the physical shared channel at a predefined position among the N physical shared channels.

7. The method according to claim 2, wherein: In a case where the DCI is used to schedule N physical shared channels within M BWPs, determining the BWPs corresponding to the N physical shared channels includes any one of the following: determining, according to the second information included in the DCI, a BWP corresponding to each physical shared channel of the N physical shared channels; Determining, according to the third information and the fourth information included in the DCI, a BWP corresponding to each physical shared channel of the N physical shared channels; Determining, according to the third information and the fifth information included in the DCI, a BWP corresponding to each physical shared channel of the N physical shared channels; determining, according to the third information included in the DCI and S physical shared channel groups, a BWP corresponding to each of the S physical shared channel groups, where the S physical shared channel groups are obtained by grouping the N physical shared channels, where S is an integer greater than or equal to 1 and less than or equal to N; The second information is used to indicate the BWP corresponding to each physical shared channel of the N physical shared channels; The third information is used to indicate the second BWP subset, or is used to indicate the second BWP in the second BWP subset, where the second BWP subset is a BWP subset including M BWPs; The fourth information is used to indicate the physical shared channel corresponding to each BWP in the second BWP subset; The fifth information is used to indicate a correspondence between each physical shared channel in the N physical shared channels and each BWP in the second BWP subset.

8. The method according to claim 7, wherein: The second information includes at least one of the following: N first indication fields, where the N first indication fields are used to respectively indicate a BWP corresponding to each physical shared channel in the N physical shared channels; A second indication field, where the second indication field is used to jointly indicate a BWP corresponding to each physical shared channel in the N physical shared channels.

9. The method according to claim 7, wherein: The fourth information includes: M second bitmaps, where the M second bitmaps are used to respectively indicate a physical shared channel corresponding to each BWP in the second BWP subset; or, The fifth information includes: A third bitmap, where each K bits of the third bitmap are used to respectively indicate a BWP corresponding to each physical shared channel in the N physical shared channels, where K is an integer greater than or equal to 1.

10. The method according to claim 7, wherein: The determining, according to the third information included in the DCI and the grouping of the N physical shared channels, a BWP corresponding to each physical shared channel group includes: Based on the BWP sequence of the second BWP subset and the sequence of each physical shared channel group, a BWP corresponding to each physical shared channel group is determined.

11. The method according to claim 7, wherein determining a BWP corresponding to each of the S physical shared channel groups based on the third information included in the DCI and the S physical shared channel groups, the method further comprises: Grouping the N physical shared channels based on a second rule to obtain the S physical shared channel groups; The second rule includes at least one of the following: The number of physical shared channels of a preset single physical shared channel group; Predefined conditions; Grouping information indicated by DCI; The number of preset physical shared channel groups.

12. The method according to any one of claims 1 to 11, wherein The DCI is used to indicate resource allocation information corresponding to each physical shared channel in the N physical shared channels; or, The DCI is used to jointly indicate resource allocation information corresponding to each physical shared channel in the N physical shared channels; or, The DCI is used to indicate the same resource allocation information for each physical shared channel in the N physical shared channels.

13. The method according to claim 12, wherein, when the DCI is used to indicate the same frequency domain resource allocation information for each of the N physical shared channels, and the terminal determines that the first target condition is met, the method further comprises any one of the following: The terminal selects, from the physical resource block PRB numbers corresponding to the frequency domain resource allocation information, a PRB number within a first PRB number range, where the first PRB number range is a PRB number range corresponding to a first activated BWP; The terminal performs modulo processing on the number of PRBs included in the first activated BWP by the PRB number corresponding to the frequency domain resource allocation information to obtain an available PRB number; The terminal ignores the physical shared channel corresponding to the first activated BWP; The terminal ignores the DCI; The first activated BWP is an activated BWP corresponding to at least one physical shared channel among the N physical shared channels; The first target condition includes: Among the PRBs corresponding to the frequency domain resource allocation information, a PRB number of at least one PRB exceeds a maximum value of a PRB number of the first activated BWP.

14. The method according to claim 12, wherein, when the DCI is used to indicate the same time domain resource allocation information for each of the N physical shared channels, and the terminal determines that the second target condition is met, the method further comprises any one of the following: The terminal performs a modulo process on the row index included in the time domain resource allocation information and the number of rows included in the first time domain resource allocation TDRA table to obtain an available row index; the first TDRA table is the TDRA table corresponding to the second activated BWP; The terminal ignores the physical shared channel corresponding to the second activated BWP; The terminal ignores the DCI; in, The second activated BWP is an activated BWP corresponding to at least one physical shared channel among the N physical shared channels; The second target condition includes: The row index indicated by the time domain resource allocation information exceeds the maximum value of the row index of the first TDRA table.

15. The method according to any one of claims 12 to 14, wherein When each BWP corresponding to the N physical shared channels meets a predefined condition, the DCI is used to indicate the same resource allocation information for each physical shared channel in the N physical shared channels; The predefined conditions include at least one of the following: The resource allocation type is the same; The subcarrier spacing SCS is the same; The cyclic prefix CP is the same; Indicator particle size is the same; The number of PRBs is equal; The number of target frequency domain indicator objects is equal, and the number of target frequency domain indicator objects is determined based on the indication granularity and the number of PRBs in the activated BWP; The number of rows contained in the corresponding TDRA tables is equal; Use the same TDRA form.

16. The method according to any one of claims 1 to 15, wherein The physical shared channel order of the N physical shared channels is determined based on at least one of the following: Second information included in the DCI, where the second information is used to indicate a BWP corresponding to each of the N physical shared channels; resource allocation information of each of the N physical shared channels, 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 N physical shared channels; a starting time of each physical shared channel among the N physical shared channels; an end time of each physical shared channel among the N physical shared channels; a frequency of a frequency domain resource of each physical shared channel among the N physical shared channels; a HARQ process occupied by each of the N physical shared channels; An effective code rate of each physical shared channel among the N physical shared channels.

17. The method according to any one of claims 4, 10 and 16, 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 the BWPs in the predefined BWP subset; The DCI indicates the order of BWPs.

18. 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 at least one of the following: The bandwidth part BWP corresponding to the N physical shared channels; The resource allocation information corresponding to the N physical shared channels includes at least one of frequency domain resource allocation information and time domain resource allocation information.

19. The method according to claim 18, wherein The DCI is used to schedule N physical shared channels, including any of the following: The DCI is used to schedule N physical shared channels within a single BWP; The DCI is used to schedule N physical shared channels within N BWPs; The DCI is used to schedule N physical shared channels within M BWPs, where M is an integer less than N.

20. The method according to claim 19, wherein In the case where the DCI is used to schedule N physical shared channels within N BWPs, the DCI includes first information, where the first information is used to indicate a first BWP subset, or used to indicate a first BWP in a first BWP subset, where the first BWP subset is a BWP subset including N BWPs.

21. The method according to claim 19, wherein In the case where the DCI is used to schedule N physical shared channels within M BWPs, the DCI includes any one of the following: second information, where the second information is used to indicate a BWP corresponding to each of the N physical shared channels; Third and fourth information; Third and fifth information; third information and grouping information of the N physical shared channels; The third information is used to indicate the second BWP subset, or is used to indicate the second BWP in the second BWP subset, where the second BWP subset is a BWP subset including M BWPs; The fourth information is used to indicate the physical shared channel corresponding to each BWP in the second BWP subset; The fifth information is used to indicate a correspondence between each physical shared channel in the N physical shared channels and each BWP in the second BWP subset.

22. The method according to any one of claims 18 to 21, wherein The DCI is used to indicate resource allocation information corresponding to each physical shared channel in the N physical shared channels; or, The DCI is used to jointly indicate resource allocation information corresponding to each physical shared channel in the N physical shared channels; or, The DCI is used to indicate the same resource allocation information for each physical shared channel in the N physical shared channels.

23. The method according to claim 22, wherein When each BWP corresponding to the N physical shared channels meets a predefined condition, the DCI is used to indicate the same resource allocation information for each physical shared channel in the N physical shared channels; The predefined conditions include at least one of the following: The resource allocation type is the same; The subcarrier spacing SCS is the same; The cyclic prefix CP is the same; Indicator particle size is the same; The number of physical resource blocks (PRBs) is equal; The number of target frequency domain indicator objects is equal, and the number of target frequency domain indicator objects is determined based on the indication granularity and the number of PRBs in the activated BWP; The number of rows contained in the corresponding TDRA tables is equal; Use the same TDRA form.

24. A channel determination device, applied to a terminal, 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; A first processing unit, configured to perform a target operation based on the DCI; The target operation includes at least one of the following: Determine a bandwidth part BWP corresponding to the N physical shared channels; Resource allocation information corresponding to the N physical shared channels is determined, where the resource allocation information includes at least one of frequency domain resource allocation information and time domain resource allocation information.

25. The apparatus according to claim 24, wherein The DCI is used to schedule N physical shared channels, including any of the following: The DCI is used to schedule N physical shared channels within a single BWP; The DCI is used to schedule N physical shared channels within N BWPs; The DCI is used to schedule N physical shared channels within M BWPs, where M is an integer less than N.

26. The device according to claim 25, wherein In a case where the DCI is used to schedule N physical shared channels within N BWPs, the DCI includes first information, where the first information is used to indicate a first BWP subset, or is used to indicate a first BWP in a first BWP subset, where the first BWP subset is a BWP subset including N BWPs; The determining the BWP corresponding to the N physical shared channels includes any one of the following: Determine the N BWPs included in the first BWP subset indicated by the first information as BWPs of the N physical shared channels; Based on the first BWP indicated by the first information and a first rule, a first BWP subset is determined, and the N BWPs included in the determined first BWP subset are determined as the BWPs of the N physical shared channels; wherein the first rule is predefined by a protocol or configured by a network or indicated by the DCI.

27. The apparatus according to claim 25, wherein In a case where the DCI is used to schedule N physical shared channels within M BWPs, determining the BWPs corresponding to the N physical shared channels includes any one of the following: determining, according to the second information included in the DCI, a BWP corresponding to each physical shared channel of the N physical shared channels; Determining, according to the third information and the fourth information included in the DCI, a BWP corresponding to each physical shared channel of the N physical shared channels; Determining, according to the third information and the fifth information included in the DCI, a BWP corresponding to each physical shared channel of the N physical shared channels; determining, according to the third information included in the DCI and S physical shared channel groups, a BWP corresponding to each of the S physical shared channel groups, where the S physical shared channel groups are obtained by grouping the N physical shared channels, where S is an integer greater than or equal to 1 and less than or equal to N; The second information is used to indicate the BWP corresponding to each physical shared channel of the N physical shared channels; The third information is used to indicate the second BWP subset, or is used to indicate the second BWP in the second BWP subset, where the second BWP subset is a BWP subset including M BWPs; The fourth information is used to indicate the physical shared channel corresponding to each BWP in the second BWP subset; The fifth information is used to indicate a correspondence between each physical shared channel in the N physical shared channels and each BWP in the second BWP subset.

28. The device according to any one of claims 24 to 27, wherein The DCI is used to indicate resource allocation information corresponding to each physical shared channel in the N physical shared channels; or, The DCI is used to jointly indicate resource allocation information corresponding to each physical shared channel in the N physical shared channels; or, The DCI is used to indicate the same resource allocation information for each physical shared channel in the N physical shared channels.

29. 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 at least one of the following: The bandwidth part BWP corresponding to the N physical shared channels; The resource allocation information corresponding to the N physical shared channels includes at least one of frequency domain resource allocation information and time domain resource allocation information.

30. The apparatus according to claim 29, wherein The DCI is used to schedule N physical shared channels, including any of the following: The DCI is used to schedule N physical shared channels within a single BWP; The DCI is used to schedule N physical shared channels within N BWPs; The DCI is used to schedule N physical shared channels within M BWPs, where M is an integer less than N.

31. The device according to claim 30, wherein In the case where the DCI is used to schedule N physical shared channels within N BWPs, the DCI includes first information, where the first information is used to indicate a first BWP subset, or used to indicate a first BWP in a first BWP subset, where the first BWP subset is a BWP subset including N BWPs.

32. The apparatus according to claim 30, wherein In the case where the DCI is used to schedule N physical shared channels within M BWPs, the DCI includes any one of the following: second information, where the second information is used to indicate a BWP corresponding to each of the N physical shared channels; Third and fourth information; Third and fifth information; third information and grouping information of the N physical shared channels; The third information is used to indicate the second BWP subset, or is used to indicate the second BWP in the second BWP subset, where the second BWP subset is a BWP subset including M BWPs; The fourth information is used to indicate the physical shared channel corresponding to each BWP in the second BWP subset; The fifth information is used to indicate a correspondence between each physical shared channel in the N physical shared channels and each BWP in the second BWP subset.

33. The device according to any one of claims 29 to 32, wherein The DCI is used to indicate resource allocation information corresponding to each physical shared channel in the N physical shared channels; or, The DCI is used to jointly indicate resource allocation information corresponding to each physical shared channel in the N physical shared channels; or, The DCI is used to indicate the same resource allocation information for each physical shared channel in the N physical shared channels.

34. 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 17 are implemented, or the steps of the channel scheduling method as described in any one of claims 18 to 23 are implemented.

35. 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 17, or implements the steps of the channel scheduling method as described in any one of claims 18 to 23.

36. 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 17, or implement the steps of the channel scheduling method according to any one of claims 18 to 23.

Images