Resource scheduling method, and terminal and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are a resource scheduling method, and a terminal and a network-side device. The method in the embodiments of the present application comprises: a terminal receiving first information from a network-side device; and the terminal determining the time-domain position of a scheduled data channel on the basis of the first information, wherein the first information is used for indicating or configuring a time-domain resource allocation parameter, and the time-domain resource allocation parameter includes at least one of a resource allocation granularity, a resource allocation range and a resource indication granularity.

Description

Resource scheduling methods, terminals and network-side equipment

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510492486.3, filed on April 18, 2025, entitled “Resource Scheduling Method, Terminal and Network Side Device”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a resource scheduling method, a terminal, and network-side equipment. Background Technology

[0004] In relevant resource scheduling schemes, when scheduling data channels such as Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH), predefined or fixed-length time-domain resource allocation parameters are usually used, such as the minimum time unit for time-domain allocation being one symbol, thereby reducing resource scheduling overhead.

[0005] However, the aforementioned resource scheduling methods provided in related communication technologies cannot flexibly adapt to different application scenarios, such as Ultra-Reliable and Low Latency Communications (URLLC) service scenarios, Enhanced Mobile Broadband (eMBB) service scenarios, and Enhanced Machine-Type Communications (eMTC) service scenarios. Summary of the Invention

[0006] This application provides a resource scheduling method, a terminal, and a network-side device, which can achieve more flexible and efficient resource scheduling and adapt to different application scenarios.

[0007] In a first aspect, a resource scheduling method is provided, comprising: a terminal receiving first information from a network-side device; the terminal determining the time-domain location of a scheduled data channel based on the first information; wherein the first information is used to indicate or configure time-domain resource allocation parameters, the time-domain resource allocation parameters including at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0008] Secondly, a resource scheduling method is provided, comprising: a network-side device sending first information; wherein the first information is used to indicate or configure time-domain resource allocation parameters of the scheduled data channel, the time-domain resource allocation parameters including at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0009] Thirdly, a resource scheduling apparatus is provided, comprising: a receiving module for receiving first information from a network-side device; and a processing module for determining the time-domain location of a scheduled data channel based on the first information; wherein the first information is used to indicate or configure time-domain resource allocation parameters, and the time-domain resource allocation parameters include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0010] Fourthly, a resource scheduling apparatus is provided, comprising: a transmitting module for transmitting first information; wherein the first information is used to indicate or configure time-domain resource allocation parameters of a scheduled data channel, the time-domain resource allocation parameters including at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0011] Fifthly, a resource scheduling apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

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

[0013] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to receive first information from a network-side device; the processor is used to determine the time-domain location of a scheduled data channel based on the first information; wherein the first information is used to indicate or configure time-domain resource allocation parameters, the time-domain resource allocation parameters including at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

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

[0015] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send first information; wherein the first information is used to indicate or configure time-domain resource allocation parameters of a scheduled data channel, the time-domain resource allocation parameters including at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

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

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

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

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

[0020] In this embodiment, the terminal receives first information from a network-side device and determines the temporal location of the scheduled data channel based on this first information. The first information is used to indicate or configure temporal resource allocation parameters, which include at least one of resource allocation granularity, resource allocation range, and resource indication granularity. Therefore, by introducing flexible and configurable temporal resource allocation parameters, such as at least one of resource allocation granularity, resource allocation range, and resource indication granularity, the terminal can determine the temporal location of the scheduled data channel. This enables more flexible and efficient resource scheduling, avoiding the poor resource scheduling flexibility that may exist when configuring temporal resource allocation parameters through protocol conventions in related technologies, and improving the performance of the communication system. Attached Figure Description

[0021] Figure 1 is a schematic diagram of the structure of a wireless communication system provided in an exemplary embodiment of this application.

[0022] Figure 2 is one of the flowcharts of a resource scheduling method provided in an exemplary embodiment of this application.

[0023] Figure 3 is a second flowchart illustrating a resource scheduling method provided in an exemplary embodiment of this application.

[0024] Figure 4 is a flowchart of a resource scheduling method provided in an exemplary embodiment of this application.

[0025] Figure 5a is one of the schematic diagrams of time-domain resources for resource scheduling provided in an exemplary embodiment of this application.

[0026] Figure 5b is a second schematic diagram of time-domain resources for resource scheduling provided in an exemplary embodiment of this application.

[0027] Figure 5c is a second schematic diagram of time-domain resources for resource scheduling provided in an exemplary embodiment of this application.

[0028] Figure 5d is a second schematic diagram of time-domain resources for resource scheduling provided in an exemplary embodiment of this application.

[0029] Figure 6 is a fourth flowchart illustrating a resource scheduling method provided in an exemplary embodiment of this application.

[0030] Figure 7 is a fifth flowchart illustrating a resource scheduling method provided in an exemplary embodiment of this application.

[0031] Figure 8 is a flowchart of a resource scheduling method provided in an exemplary embodiment of this application.

[0032] Figure 9 is a schematic diagram of the structure of a resource scheduling device provided in an exemplary embodiment of this application.

[0033] Figure 10 is a second schematic diagram of the structure of a resource scheduling device provided in an exemplary embodiment of this application.

[0034] Figure 11 is a schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application.

[0035] Figure 12 is a schematic diagram of the structure of a terminal provided in an exemplary embodiment of this application.

[0036] Figure 13 is a schematic diagram of the structure of a network-side device provided in an exemplary embodiment of this application. Detailed Implementation

[0037] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

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

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

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

[0041] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. Furthermore, in addition to the terminals described above, terminal 11 can also be a chip within a terminal, such as a modem chip, a system-on-chip (SoC), etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application.

[0042] Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, wireless local area network (WLAN) access points (APs), or wireless Fidelity (WiFi) nodes, etc. Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0043] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0044] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0045] In addition, for ease of understanding, the relevant features involved in the technical solution of this application are introduced here, as follows.

[0046] 1. Time-domain resource allocation for PDSCH / PUSCH

[0047] The NR system supports different types of services, such as eMBB, URLLC, and eMTC. Among them, compared to eMBB, URLLC has higher latency requirements. Therefore, the protocol defines two different types of PDSCH / PUSCH time domain resource allocation.

[0048] Type A: Time slot-based scheduling, where the time domain allocation length is relatively long.

[0049] Type B: Non-slot-based scheduling, also known as mini-slot-based scheduling, features shorter time-domain allocations and is suitable for latency-sensitive services.

[0050] Regardless of whether it is Type A or Type B time-domain resource allocation, the allocated resources belong to the same time slot, and there will be no cross-time-slot resource allocation.

[0051] To improve uplink coverage, NR supports repetition transmission of PUSCH. Depending on the repetition transmission style, the protocol defines two different PUSCH repetition types.

[0052] PUSCH repetition Type A: The user sends the same transport block (TB) on K consecutive slots, and the symbol positions occupied in the K slots are exactly the same, that is, the starting symbol position and the occupied symbol length are the same in each slot.

[0053] PUSCH repetition Type B: Its corresponding time-domain resource allocation supports cross-slot indication, such as independently indicating the start symbol position (e.g., Start (0~13)), occupied symbol length (e.g., length (1~14)), repetition count, etc. Among them, nominal transmission can cross time slots. When nominal transmission crosses a time slot, it will actually be divided into two actual transmissions. That is to say, the actual transmission still does not cross time slots.

[0054] For transmissions above 52.6 GHz, due to the use of larger subcarrier spacing and shorter symbol lengths, in order to reduce the detection overhead of the Physical Downlink Control Channel (PDCCH), the NR system also supports scheduling multiple consecutive time slots of PDSCH or PUSCH with a single Downlink Control Information (DCI). This method is also based on slot transmission, transmitting different TBs in multiple consecutive time slots, but using the same time domain resource allocation in each time slot. Because the resource allocation is the same, it is indicated by a single DCI.

[0055] To improve uplink coverage, in addition to the repetitive transmission defined above for PUSCH, NR also supports mapping a TB to multiple consecutive time slots (Transport Block processing over multi slots, TBoMS). This method is also based on slot-based repetitive transmission, with each slot using the same symbol-level allocation. TBoMS uses multiple slots to transmit a TB block, and these multiple slots transmit the same Redundancy Version (RV) of the TB. TBoMS and PUSCH repetition Type A can be configured and enabled simultaneously.

[0056] Furthermore, as mentioned earlier, the protocol defines two different types of PDSCH / PUSCH time-domain resource allocation methods (Type A and Type B). Since these two methods are designed for different scenarios, the corresponding demodulation reference signal (DMRS) mapping methods are also different. That is, there are different DMRS determination methods for PDSCH mapping Type A and PDSCH mapping Type B.

[0057] The aforementioned resource scheduling schemes typically employ predefined or fixed-length time-domain resource allocation parameters when scheduling data channels such as PDSCH and PUSCH. For example, the minimum predefined time unit for time-domain allocation is one symbol. This results in a lack of flexibility in adapting to different application scenarios, such as URLLC, eMBB, and eMTC services. To address this, this application provides a resource scheduling scheme that introduces flexible and configurable time-domain resource allocation parameters, enabling more flexible and efficient resource scheduling to adapt to different application scenarios.

[0058] The technical solutions provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0059] Figure 2 shows a flowchart of a resource scheduling method 200 provided in an exemplary embodiment of this application. This method 200 can be executed by, but is not limited to, a terminal, specifically by hardware and / or software installed in the terminal. In this embodiment, the method 200 may include at least the following steps.

[0060] S210, the terminal receives the first information from the network-side device.

[0061] S220, the terminal determines the time domain location of the scheduled data channel based on the first information.

[0062] The first information is used to indicate or configure time-domain resource allocation parameters, which include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0063] The resource allocation granularity can be understood as the smallest unit in resource allocation or the smallest resource block that a network-side device can divide when scheduling resources. In this embodiment, the resource allocation granularity may include at least one sub-time unit. The sub-time unit may be a symbol, slot, subframe, etc.

[0064] The resource allocation range can be understood as the total size of the resource pool that is allowed to be scheduled. In this embodiment, the resource allocation range may include at least one time unit, wherein the time unit may be a time slot, symbol, frame, etc.

[0065] The resource indication granularity can be understood as the smallest unit indicating resource allocation, such as the coding granularity in the Time Domain Resource Allocation (TDRA) field of DCI. In this embodiment, the resource indication granularity may include at least one time unit. The time unit may be a time slot, symbol, frame, etc.

[0066] Optionally, the resource indication granularity may include at least one of the granularity parameter M0 for PDSCH time-domain resource allocation and the granularity parameter M2 for PDSCH time-domain resource allocation. In this embodiment, when indicating or configuring the resource indication granularity through the first information, M0 and M2 can be indicated or configured independently, or M0 and M2 can be indicated or configured simultaneously, without limitation.

[0067] In this embodiment, for the time units involved in the resource allocation granularity, resource allocation range, and resource indication granularity in the aforementioned time-domain resource allocation parameters, a time unit may include multiple sub-time units. For example, if the time unit is a time slot and the sub-time unit is a symbol, then a time slot may include 14 symbols.

[0068] Optionally, the data channel described in this embodiment may include, but is not limited to, PDSCH, PUSCH, etc. The time-domain position of the data channel may include, but is not limited to, the start time unit (such as the start symbol) of the data channel, the number of consecutive time units occupied by the data channel, etc., and is not limited here.

[0069] In this embodiment, the terminal receives first information from the network-side device and determines the temporal location of the scheduled data channel based on the first information. The first information is used to indicate or configure temporal resource allocation parameters, which include at least one of resource allocation granularity, resource allocation range, and resource indication granularity. Therefore, by dynamically indicating or configuring the first information, flexible and configurable temporal resource allocation parameters, such as at least one of resource allocation granularity, resource allocation range, and resource indication granularity, can be introduced for the terminal to determine the temporal location of the scheduled data channel. This achieves more flexible and efficient resource scheduling, avoiding the poor resource scheduling flexibility that may exist when using predefined or fixed-length temporal resource allocation parameters in related technologies, and improving the performance of the communication system.

[0070] Furthermore, the dynamic indication or configuration of time-domain resource allocation parameters based on the first information provided in this embodiment can also be understood as a unified time-domain resource indication or allocation method. That is, in this embodiment, there is no need to define different time-domain resource allocation methods for different application scenarios (such as eMBB service scenarios, URLLC service scenarios, and eMTC service scenarios). Thus, while achieving flexible and efficient resource scheduling, it can also flexibly adapt to different application scenarios. For example, different values ​​of time-domain resource allocation parameters can be indicated or configured for different application scenarios.

[0071] In some embodiments, when the time-domain resource allocation parameters are indicated or configured through the first information, this embodiment can indicate or configure them explicitly or implicitly, thereby further improving the flexibility of indicating or configuring the time-domain resource allocation parameters to adapt to different business scenarios, such as eMBB business scenarios, URLLC business scenarios, and eMTC business scenarios.

[0072] For example, the first information may include (such as direct carrying or implicit indication) but is not limited to at least one of 11)-17) below.

[0073] 11) First parameter, which is a parameter used for flexible time units (such as time slots).

[0074] In the case where the first information includes the first parameter, this can be understood as an implicit indication or configuration method, enabling the terminal to determine the time-domain resource allocation parameters based on the first parameter. For example, if the first parameter is configured according to the reference granularity of the frame structure, then the terminal can determine the first parameter as the time-domain resource allocation parameter, such as one or more of the time-domain resource allocation range, time-domain resource indication granularity, and time-domain resource indication granularity.

[0075] Optionally, the first parameter can be configured per cell group, or per cell, or per bandwidth part (BWP).

[0076] 12) Second parameter, the second parameter is a parameter used for other channel configuration, such as time domain resource allocation parameters (such as resource allocation granularity, resource allocation range, etc.) used for other channel configuration, the other channels are channels other than the data channel, such as PDCCH, Physical Uplink Control Channel (PUCCH), etc.

[0077] In the case where the first information includes the second parameter, it can be understood as an implicit indication or configuration method, so that the terminal can determine the time domain resource allocation parameter according to the second parameter, such as determining the second parameter as the time domain resource allocation parameter, etc., without limitation.

[0078] Optionally, the second parameter can be configured per cell group, or per cell, or per BWP.

[0079] 13) A third parameter, which is a parameter used for the data channel, such as other time-domain parameters different from the time-domain resource allocation parameters. In this embodiment, the third parameter can be understood as a parameter specifically used for the data channel.

[0080] In the case where the first information includes the third parameter, it can be understood as an implicit indication or configuration method, enabling the terminal to determine the time-domain resource allocation parameters, such as resource allocation granularity and resource allocation range, based on the third parameter.

[0081] Optionally, the third parameter is configured per cell group, or per cell, or per BWP.

[0082] 14) First indication information, the first indication information is used to indicate a first time domain allocation item, the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list includes at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

[0083] In the case where the first information includes the first indication information, it can be understood as an implicit indication or configuration method, enabling the terminal to determine the time domain location information of the data channel based on at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity included in the first time domain allocation item.

[0084] In this embodiment, by using the first indication information to indicate, the resource indication overhead can be reduced while indicating or configuring the time-domain resource allocation parameters.

[0085] Optionally, the time-domain allocation list can be configured per cell group, or per cell, or per BWP.

[0086] 15) Configuration period for monitoring occasions. The monitoring occasion can be understood as when the terminal begins monitoring downlink channels, such as PDCCH, DCI, etc.

[0087] In the case where the first information includes the configuration period of the listening timing, it can be understood as an implicit indication or configuration method, so that the terminal can determine the time domain resource allocation parameters according to the configuration period of the listening timing, thereby enabling more flexible and efficient data channel scheduling.

[0088] Optionally, the method by which the terminal determines the time-domain resource allocation parameters based on the configuration period of the listening timing can be agreed upon by the protocol or indicated by the network-side device. For example, if the first information includes the configuration period of the listening timing and the configuration period of the listening timing is X time units, the terminal may determine that the resource allocation granularity is Y1 sub-time units, the resource allocation range is Y2 time units, and the resource indication granularity is Y3 time units. In this case, one time unit (e.g., a time slot) includes multiple sub-time units (e.g., symbols). X, Y1, Y2, and Y3 are all integers not less than 1, and at least one of Y1, Y2, and Y3 is equal to X, such as X = Y1 = Y2 = Y3 = 1, or X = Y1 = 1, and Y2 and Y3 are not equal to 1.

[0089] Optionally, X, Y1, Y2, and Y3 can be determined by protocol agreement, network-side device configuration, or network-side device indication, etc., and there are no restrictions here.

[0090] 16) Configuration period for PDCCH listening time. The PDCCH listening time can be understood as the duration for which the terminal needs to continuously listen during each PDCCH listening session, such as the number of symbols that need to be continuously listened to.

[0091] In the case where the first information includes the configuration period of the PDCCH listening time, it can be understood as an implicit indication or configuration method, so that the terminal can determine the time domain resource allocation parameters according to the configuration period of the PDCCH listening time, thereby enabling more flexible and efficient data channel scheduling.

[0092] For example, the terminal can determine the configuration period of the PDCCH listening time as the time domain resource allocation range, etc.

[0093] 17) At least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity. Wherein, each piece of information included in 17) can be understood as: explicitly indicating the time-domain resource allocation parameters through the first information.

[0094] In some embodiments, if the first information includes the resource allocation range but not the resource indication granularity, then the terminal can also determine that the resource indication granularity is the same as the resource allocation range. In this way, the resource indication granularity can be implicitly indicated by indicating the resource indication range, thereby achieving flexible and efficient resource scheduling.

[0095] In this embodiment, which information from 11)-17) mentioned above is carried in the first information can be determined by means of protocol agreement, thereby ensuring the consistency of the terminal's and the network-side device's understanding of the first information.

[0096] In some embodiments, the first information may be transmitted via at least one of, but not limited to, DCI, Media Access Control Control Element (MAC CE), and Radio Resource Control (RRC) signaling. For example, assuming the first information is transmitted via the DCI, then the first information may be configured or carried in the TDRA within the DCI, but not limited to.

[0097] In some embodiments, for a terminal, the indicative or configurable value of the time-domain resource allocation parameter is associated with at least one of the following 21)-24).

[0098] 21) Subcarrier Spacing (SCS) of the data channel.

[0099] In cases where the indicative or configurable value of the time-domain resource allocation parameter is related to the SCS of the data channel, a larger SCS allows for a larger value for the time-domain resource allocation parameter. For example, assuming the time-domain resource allocation parameter is the resource indication granularity, if the SCS = 15K, the resource indication granularity can be A; if the SCS = 30K, the resource indication granularity can be 2A, and so on.

[0100] 22) The format of the second indication information. The second indication information is used to schedule the data channel. In this embodiment, the second indication information may be, but is not limited to, DCI, etc.

[0101] 23) The second indication information is the Radio Network Temporary Identifier (RNTI). This second indication information is used to schedule the data channel. In this embodiment, the second indication information can be, but is not limited to, DCI, etc.

[0102] 24) The scheduling method of the data channel, wherein the scheduling method is one of unicast, multicast, or broadcast.

[0103] In some embodiments, when the time-domain resource allocation parameters (such as one or more of resource allocation granularity, resource allocation range, resource indication granularity, etc.) are configured per BWP and the data channel is scheduled during BWP switching, the time-domain resource allocation parameters may correspond to at least one of a first BWP and a second BWP. The first BWP is the BWP used before the BWP switching (i.e., the original BWP), and the second BWP is the BWP used after the BWP switching (i.e., the target BWP).

[0104] In the case where the time-domain resource allocation parameters correspond to the first BWP, it can be understood that when data channel scheduling is performed at the same time as the BWP switching occurs, the original BWP can be scheduled first for data channel transmission, and then the BWP switching can be performed.

[0105] The case where the time-domain resource allocation parameters correspond to the second BWP can be understood as follows: when scheduling data channels at the same time as BWP switching occurs, BWP switching can be performed first, and then data channel transmission can be performed based on the new BWP after switching.

[0106] Optionally, if the time-domain resource allocation parameters correspond to the second BWP, then when the network-side device determines the size of the DCI field according to the time-domain resource allocation parameters corresponding to the new BWP after the switch, if the DCI field is larger than the DCI field of the original BWP, it will be padded with 0; otherwise, it will be truncated, thereby ensuring the reliability of the indication or configuration of the time-domain resource allocation parameters.

[0107] In some embodiments, when the network-side device indicates or configures the time-domain resource allocation parameters through the first information, it may also indicate a Start and Length Indicator Value (SLIV) value determined based on the resource allocation granularity and resource allocation range to the terminal, so that the terminal can determine the time-domain location of the scheduled data channel.

[0108] Optionally, in this embodiment, the time-domain resource allocation parameters (such as at least one of resource allocation granularity, resource allocation range, and resource indication granularity) and the SLIV value can satisfy a first correlation relationship (i.e., the first correlation relationship is used to characterize the correlation relationship between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information), so that after receiving the time-domain resource allocation parameters and SLIV value indicated by the first information, the terminal can determine the time-domain location of the scheduled data channel based on the first correlation relationship, the time-domain resource allocation parameters, and the SLIV value. The first correlation relationship can be represented by the following equation (1) or equation (2).

[0109] In equations (1) and (2), R represents the resource allocation range, G represents the resource allocation granularity, S1 represents the first starting sub-time unit in the first time-domain location information, L represents the number of first starting sub-time units in the first time-domain location information, and 0 <L≤14-S。

[0110] Based on this, in some embodiments, if the first information is also used to indicate the SLIV value, then, referring to Figure 3, the implementation process of determining the time domain position of the scheduled data channel based on the first information in S220 may include, but is not limited to, S221-S222, as follows.

[0111] S221, determine the first time-domain location information based on the time-domain resource allocation parameters, the SLIV value and the first association relationship. The first time-domain location information includes the first starting sub-time unit and the number of first sub-time units.

[0112] S222, determine the starting sub-time unit of the data channel based on the first starting sub-time unit, and determine the number of consecutive sub-time units occupied by the data channel based on the number of the first sub-time units.

[0113] One of the time units may include at least one sub-time unit, and the first association relationship is used to characterize the association relationship between the time domain resource allocation parameter, the SLIV value and the first time domain location information.

[0114] Optionally, when the terminal in S222 determines the starting sub-time unit of the data channel based on the first starting sub-time unit and determines the number of the first sub-time units as the number of consecutive sub-time units occupied by the data channel, if the first information indicates or configures multiple SLIV values, then for each SLIV value, the terminal can determine the starting sub-time unit (e.g., the starting symbol) of the data channel based on the first starting sub-time unit (e.g., the starting symbol) in the first time-domain location information determined by the time-domain resource allocation parameters, the SLIV value, and the first association relationship, and determine the number of the first sub-time units (e.g., the number of consecutive symbols) in the first time-domain location information as the number of consecutive sub-time units occupied by the data channel (e.g., the number of consecutive symbols).

[0115] Alternatively, if the first information indicates or configures an SLIV value, then after determining the first time-domain location information based on the time-domain resource allocation parameters, the SLIV value, and the first association relationship, the terminal can determine the starting sub-time unit of the data channel and the number of consecutive sub-time units occupied by the data channel according to the first time-domain location information, the reference sub-time unit, and the resource allocation granularity. For example, assuming the starting sub-time unit in the first time-domain location information is S1, the number of first sub-time units is L1, the resource allocation granularity is G, and the reference sub-time unit is S2, then the starting sub-time unit S of the data channel = S1*G + S2, and the number of consecutive sub-time units occupied by the data channel L = L1*G.

[0116] Optionally, the resource allocation granularity and the resource allocation range may be the same or different, and there is no limitation on this.

[0117] Optionally, if the first information is transmitted via DCI, the first information may be carried in the TDRA field of the DCI.

[0118] In addition to the aforementioned method of determining the time-domain position of the data channel based on S221-S222, in some embodiments, assuming that time unit groups are pre-configured through protocol reservation or other means, then, as shown in Figure 4, the process of determining the time-domain position of the scheduled data channel based on the first information in S220 may include, but is not limited to, S223-S224, as follows.

[0119] S223, determine the time unit group to which the data channel belongs, and determine the starting sub-time unit of the time unit group as the reference sub-time unit.

[0120] The time unit group in which the data channel is located can also be understood as the time unit group corresponding to the data channel, in order to determine the time domain location of the data channel.

[0121] S224, determine the time-domain location information of the data channel based on the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and the first correlation relationship. The time-domain location information includes the starting sub-time unit of the data channel and the number of consecutive sub-time units occupied by the data channel. The first correlation relationship characterizes the association between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

[0122] In other words, this embodiment introduces time unit groups (such as time slot groups, symbol groups, etc.) to improve the efficiency of resource scheduling. For example, when scheduling downlink data channels (such as PDSCH), time units can be grouped and numbered in a way that skips uplink time units.

[0123] Optionally, the time unit group mentioned in this embodiment can be divided into physical time units (such as time slots or symbols) or logical time units (such as time slots or symbols), and there is no limitation on this.

[0124] Based on this, in some embodiments, the method for determining the time unit group to which the data channel belongs in S223 can be varied. For example, suppose the first information is also used to indicate or configure a fifth parameter, which is used to indicate the time unit-level offset between the data channel and the scheduling information, such as the time slot-level offset K0 between PDSCH scheduling and PDCCH, and the time slot-level offset K2 between PUSCH scheduling and PDCCH. The fifth parameter is determined based on the resource indication granularity, such as K0 being determined based on resource indication granularity M0, and K2 being determined based on resource indication granularity M2. Then, the method for determining the time unit group to which the data channel belongs in S223 can include at least one of the following methods 11-13.

[0125] Method 11: Determine the time unit group where the data channel is located based on the first index and the fifth parameter.

[0126] Wherein, the first index is the index of the time unit group in which the first information is located. For example, assuming the first information is transmitted via DCI, then the first index is the index of the time unit group in which the DCI is located.

[0127] The scope of resource allocation is the same as the granularity of resource allocation.

[0128] The number of time units included in each time unit group is the same as the number of time units included in the resource allocation range (or the number of time units included in the resource allocation granularity).

[0129] Optionally, the time unit group can be a fixed time unit group. For example, assuming the time unit is a time slot, the time domain units can be allocated into fixed time slot groups according to the frame structure. For example, starting from the first time slot of the radio frame, every R time slots can form a time slot group, that is, each time slot group includes R time slots, where R is the number of time slots included in the resource allocation range.

[0130] Optionally, in the case of determining the time unit group of the data channel according to the first index and the fifth parameter as described in method 11, the index Ksg of the time unit group of the data channel is n1+K; where n1 represents the first index, K (such as K0, K2) represents the fifth parameter, and M (such as M0, M2) represents the resource allocation granularity.

[0131] For example, assuming the time unit is a time slot, the sub-time unit is a symbol, the first information is carried in the TDRA field of the DCI, and the first information is used to indicate or configure the time domain resource allocation parameters, the fifth parameter and the SLIV value, the parameter value of the fifth parameter is 2, and the data channel is PDSCH, then, as shown in Figure 5a, the index Ksg of the time slot group where the PDSCH is located is Ksg = n1 + K0, that is, Ksg is "#3" shown in Figure 5a, the n1 is the index of the time slot group where the DCI is located (which can be equivalent to floor(n / R) + K, where n is the time slot where the DCI is located), that is, n1 is "#1" shown in Figure 5a, and K0 is the indication based on the resource indication granularity M0.

[0132] Method 12: Determine the first time unit based on the second index, the fifth parameter, and the resource indication granularity, and determine the time unit group where the first time unit is located as the time unit group where the data channel is located.

[0133] Wherein, the second index is the index of the time unit in which the first information is located, or the second index is the index of the start or end time unit of the time unit group in which the first information is located. For example, assuming the first information is transmitted via DCI, then the second index is the index of the time unit in which the DCI is located, or the second index is the index of the start or end time unit of the time unit group in which the DCI is located.

[0134] The scope of resource allocation is different from the granularity of resource allocation.

[0135] The number of time units included in each time unit group is the same as the number of time units included in the resource allocation range. Optionally, the time unit group can be a fixed time unit group or a non-fixed time unit group. For a fixed time unit group, assuming a time unit is a time slot, the time domain resources can be allocated into fixed time slot groups according to the frame structure. For example, starting from the first time slot of the radio frame, every R time slots constitute a fixed time slot group, i.e., each time slot group includes R time slots, where R is the number of time slots included in the resource allocation range.

[0136] Optionally, for the case described in method 12 where the first time unit is determined based on the second index, the fifth parameter, and the resource indication granularity, the index Ks of the first time unit is Ks = n2 + K * M; where n2 represents the second index, K (such as K0, K2) represents the fifth parameter, and M (such as M0, M2) represents the resource allocation granularity.

[0137] For example, assuming the time unit group is a fixed time unit group, and the time unit is a time slot, the sub-time unit is a symbol, the first information is carried in the TDRA field of the DCI, the first information is used to indicate or configure the time domain resource allocation parameter, the fifth parameter and the SLIV value, the parameter value of the fifth parameter is 7, the second index is the index of the time slot where the DCI is located, the resource indication granularity in the time domain resource allocation parameter is predefined as 1 slot, and the data channel is PDSCH, then, as shown in Figure 5b, the index Ks of the first time slot determined based on the second index, the fifth parameter and the resource indication granularity is n2 + K0 * M0, where n2 is the index of the second time slot in time slot group #1 shown in Figure 5b, Ks is the index of the second time slot in time slot group #3 shown in Figure 5b, and the index of the time slot group where the data channel is located is the time slot group where the first time slot is located, that is, time slot group #3 shown in Figure 5a.

[0138] For example, assuming the time unit group is a non-fixed time unit group, and the time unit is a time slot, the sub-time unit is a symbol, the first information is carried in the TDRA field of the DCI, and the first information is used to indicate or configure the time domain resource allocation parameter, the fifth parameter and the SLIV value, the parameter value of the fifth parameter is 8, the second index is the index of the time slot where the DCI is located, the resource indication granularity in the time domain resource allocation parameter is predefined as 1 slot, and the data channel is PDSCH, then, as shown in Figure 5c, the index Ks of the first time slot determined based on the second index, the fifth parameter and the resource indication granularity is Ks = n2 + K0 * M0, where n2 is time slot #2 shown in Figure 5c, Ks is time slot #11 shown in Figure 5c, and the index of the time slot group where the data channel is located is the time slot group where the first time slot is located, that is, time slot group # shown in Figure 5c, where the length of the time slot group is R time slots, and R is the resource indication range.

[0139] Method 13: Determine the time unit group where the data channel belongs based on the start or end sub-time unit of the monitoring timing where the first information is located. The value of the fifth parameter is 0.

[0140] Optionally, the end sub-time unit of the monitoring timing where the first information is located is located in the R*Ath sub-time unit after the start sub-time unit, where R represents the number of time units in the time unit group and A represents the number of sub-time units in each time unit.

[0141] For example, assuming that there are incomplete time slots in the time slots included in the time unit group, and that the time unit is a time slot and the sub-time unit is a symbol, the first information is carried in the TDRA field in the DCI, and the first information is used to indicate or configure the time domain resource allocation parameters, the fifth parameter and the SLIV value, and the parameter value of the fifth parameter (such as K0, K2) is 0, then, as shown in Figure 5d, the time slot group where the data channel is located is the time slot group where the start symbol or the end symbol of the PDCCH MO where the DCI is located is located, as shown in the time slot group # in Figure 5d.

[0142] In some embodiments, if there are incomplete time slots in the time slots included in the time unit group, and the parameter value of the fifth parameter is not equal to 0, then the time unit group in which the SLIV is located can be determined according to the aforementioned method 11 or method 12. Then, a start sub-time unit is indicated in the start time unit in the time unit group. Finally, the time unit group in which the data channel is located is determined with the start sub-time unit of the start time unit as the starting sub-time unit. The end sub-time unit of the time unit group in which the data channel is located is the R*Ath sub-time unit located after the start sub-time unit.

[0143] For example, assuming that the time unit is a time slot, and the time slot group in which the SLIV is located is determined to be group #1 according to the aforementioned method 11 or method 12, then a symbol can be indicated as the start symbol in the start time slot #1 of the group #1, such as symbol #6. Then, symbol #6 is used as the start symbol of the time unit group in which the data channel is located, and the R*Ath symbol after symbol #6 is used as the end symbol of the time unit group in which the data channel is located.

[0144] In this embodiment, by implementing the aforementioned methods 11-13, flexible and configurable or indicative time-domain resource allocation parameters can be introduced during resource scheduling, while achieving more flexible and efficient single PDSCH / PUSCH self-scheduling.

[0145] In some embodiments, in addition to determining the time unit group of the data channel through methods 11-13 as described above, if the first information can also be used to indicate that the data channel is cross-carrier scheduling, such as the Carrier Indicator Field (CIF) indication carried in the DCI, or if the first information is also used to indicate that the data channel is cross-BWP scheduling within the same carrier, such as the BWP indication carried in the DCI. That is, the data channel is cross-carrier, cross-BWP, or cross-cell scheduling. Then, the method for determining the time unit group of the data channel described in S223 can also include S2231 shown in FIG6, the content of which is as follows.

[0146] S2231, determine the time unit group to which the data channel belongs based on at least one of the time domain allocation parameters, the SCS corresponding to the first object, the SCS corresponding to the second object, the third index, and the fifth parameter.

[0147] The first object is the original carrier during cross-carrier scheduling or the original BWP during cross-BWP scheduling. The second object is the target carrier during cross-carrier scheduling or the target BWP during cross-BWP scheduling, and the time-domain resource allocation parameters correspond to the second object. The cross-carrier scheduling can be implemented based on the same cell or BWP, or it can be implemented based on different cells or BWPs; no limitation is imposed here.

[0148] The third index is the index of the time unit group where the first information is located, or the index of the start or end sub-time unit of the time unit group where the first information is located, or the index of the time unit where the first information is located. For example, assuming the first information is transmitted via DCI, then the third index can be the index of the time unit where the DCI is located, or the third index can be the index of the start or end time unit of the time unit group where the DCI is located.

[0149] The fifth parameter indicates the time unit-level offset between the data channel and the scheduling information, such as the time slot-level offset K0 between PDSCH scheduling and PDCCH, and the time slot-level offset K2 between PUSCH scheduling and PDCCH. The fifth parameter is determined based on the resource indication granularity; for example, K0 can be determined based on resource indication granularity M0, and K2 can be determined based on resource indication granularity M2. The SLIV and the fifth parameter are used for scheduling according to the time-domain resource allocation parameters of the scheduled second object.

[0150] In this embodiment, by using the time unit group determination method provided in S2231, flexible and efficient resource scheduling can be achieved by introducing flexible and configurable or indicative time domain resource allocation parameters, while also enabling more flexible and efficient cross-carrier, cross-BWP, or cross-cell scheduling of a single data channel.

[0151] In some embodiments, the method of determining the time unit group of the data channel according to at least one of the time domain allocation parameters, the SCS corresponding to the first object, the SCS corresponding to the second object, the third index, and the fifth parameter as described in S2231 may include, but is not limited to, at least one of the following methods 21-22.

[0152] Method 21: Determine the time unit group where the data channel is located based on the third index, the fifth parameter, the SCS corresponding to the first object, and the SCS corresponding to the second object.

[0153] The third index is the index of the time unit group where the first information is located, and the resource allocation range is the same as the resource allocation granularity.

[0154] The number of time units included in each time unit group is the same as the number of time units included in the resource allocation range. Optionally, the time unit group is a fixed time unit group. For example, assuming that the time unit is a time slot, the second object can allocate the time domain units into fixed time slot groups according to the frame structure. For example, starting from the first time slot of the radio frame, every R time slots constitute a time slot group, that is, each time slot group includes R time slots, where R is the number of time units (such as time slots) included in the resource allocation range.

[0155] Optionally, in the case described in method 21, where the time unit group of the data channel is determined based on the third index, the fifth parameter, the SCS corresponding to the first object, and the SCS corresponding to the second object, the index Ksg of the time unit group of the data channel is floor(n3*(μ1 / μ2) / R)+K, where n3 represents the time unit where the first information is located on the first object, or n3 represents the start or end time unit of the time unit group where the first information is located on the first object, K represents the fifth parameter, μ1 represents the SCS corresponding to the first object, μ2 represents the SCS corresponding to the second object, and M represents the time domain resource granularity corresponding to the second object.

[0156] For example, assuming the time unit is a time slot and the sub-time unit is a symbol, the first information of the DCI of the first object indicates the scheduling of the second object, and the first information carried in the TDRA field of the DCI indicates or configures the time domain resource allocation parameters, the fifth parameter and the SLIV value corresponding to the second object, and the data channel is PDSCH, then the index Ksg of the time slot group where the data channel on the second object is located is Ksg = floor(n3*(μ1 / μ2) / R) + K0, where n3 is the time slot where the DCI is located, and K0 is determined based on the resource indication granularity M0 on the second object.

[0157] Method 22: Determine the second time unit based on at least one of the third index, the fifth parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, and the resource indication granularity, and determine the time unit group to which the second time unit belongs as the time unit group to which the data channel belongs.

[0158] Wherein, the third index is the index of the beginning or end sub-time unit of the time unit group where the first information is located, or the third index is the index of the time unit where the first information is located, and the resource allocation range is different from the resource allocation granularity.

[0159] The number of time units included in each time unit group is the same as the number of time units included in the resource allocation range. Optionally, the time unit group can be a fixed or non-fixed time unit group. For a fixed time unit group, assuming a time unit is a time slot, the time domain resources can be allocated into fixed time slot groups according to the frame structure. For example, starting from the first time slot of the radio frame, every R time slots constitute a fixed time slot group, i.e., each time slot group includes R time slots, where R is the number of time units (e.g., time slots) included in the resource allocation range.

[0160] Optionally, in method 22, when the second time unit is determined based on at least one of the third index, the fifth parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, and the resource indication granularity, the index Ks of the second time unit is n3 + K*M, or the index Ks of the second time unit is floor(n3*(μ1 / μ2)) + K*M; where n3 represents the time unit where the first information is located on the first object, or n3 represents the start or end time unit of the time unit group where the first information is located on the first object, K represents the fifth parameter, μ1 represents the SCS corresponding to the first object, μ2 represents the SCS corresponding to the second object, and M represents the time-domain resource granularity corresponding to the second object.

[0161] For example, assuming the time unit group is a fixed time unit group, and the time unit is a time slot, the sub-time unit is a symbol, the first information of the first object's DCI (such as CIF or BWP indication) indicates the scheduling of the second object, and the first information carried in the TDRA field of the DCI indicates or configures the time domain resource allocation parameters, the fifth parameter and the SLIV value corresponding to the second object, then the index Ks of the second time slot is n3 + K*M, and the index of the time slot group where the data channel is located is the time slot group where the second time slot is located, where n3 represents the time slot where the DCI is located on the first object, or where n3 represents the start time slot or the end time slot of the time slot group where the DCI is located on the first object.

[0162] For example, assuming the time unit group is a non-fixed time unit group, and the time unit is a time slot, the sub-time unit is a symbol, the first information of the first object's DCI (such as CIF or BWP indication) indicates the scheduling of the second object, and the first information carried in the TDRA field of the DCI indicates or configures the time domain resource allocation parameters, the fifth parameter and the SLIV value corresponding to the second object, and the data channel is PDSCH, then the index of the second time slot Ks = floor(n3*(μ1 / μ2)) + K0*M0, and the index of the time slot group where the data channel is located is the time slot group where the second time slot is located, wherein the length of the time slot group is R time slots, and R is the resource indication range corresponding to the second object.

[0163] In this embodiment, by using the time unit group determination method provided in the aforementioned methods 21-22, flexible and configurable or indicative time-domain resource allocation parameters can be introduced during the resource scheduling process to achieve flexible and efficient resource scheduling. At the same time, more flexible and efficient cross-carrier, cross-BWP, or cross-cell scheduling of a single data channel can also be achieved.

[0164] After determining the time unit group where the data channel belongs based on the foregoing embodiments, and determining the starting sub-time unit of the time unit group as the reference sub-time unit, the implementation process of determining the time-domain location information of the data channel according to the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and the first correlation relationship in S224 can be varied. For example, in some embodiments, the implementation process of determining the time-domain location information of the data channel according to the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and the first correlation relationship in S224 can include, but is not limited to, S2241-S2242 shown in FIG7, as follows.

[0165] S2241, determine the first time domain location information according to the time domain resource allocation parameters and the first association relationship, wherein the first time domain location information includes the first start sub-time unit and the number of the first sub-time units.

[0166] S2242, determine the starting sub-time unit of the data channel based on the first starting sub-time unit and the resource allocation granularity, and determine the number of consecutive sub-time units occupied by the data channel based on the length of the first sub-time unit and the resource allocation granularity.

[0167] Optionally, the index S of the starting sub-time unit of the data channel is determined by the formula S = S2 + S1 * G; and / or, the number L of consecutive sub-time units occupied by the data channel is determined by the formula L = L1 * G. Wherein, S2 is the reference sub-time unit, S1 represents the first starting sub-time unit, G represents the resource allocation granularity, and L1 represents the length of the first sub-time unit. The time unit may include multiple sub-time units, such as a time slot or a symbol, etc., without limitation.

[0168] In some embodiments, for the terminal at the time-domain position of the data channel determined based on the foregoing embodiments, the number of time units occupied by the time-domain position of the data channel does not exceed the number of time units corresponding to the resource allocation range, thereby achieving more flexible and efficient scheduling of a single data channel across multiple time units (such as time slots).

[0169] In some embodiments, when the terminal determines the transport block (TB) size based on the time-domain location of the data channel, the transport block size corresponding to the data channel does not exceed a predetermined value (i.e., transport block size limit). In other words, the terminal does not expect the transport block size corresponding to the data channel scheduled by the network-side device to exceed the predetermined value, thereby ensuring the transmission efficiency and reliability of the data channel transmission.

[0170] Based on this, in some embodiments, if the transport block size calculated by the terminal according to the time-domain resource allocation parameters exceeds the predetermined value, the terminal can determine that the scheduled transport block size is the predetermined value, thereby ensuring the transmission efficiency and reliability of the data channel transmission.

[0171] Optionally, the predetermined value can be agreed upon by a protocol or configured by the network-side device, or the terminal can report the predetermined value to the network-side device to ensure that the terminal and the network-side device have a consistent understanding of the predetermined value.

[0172] In some embodiments, the method of determining the time-domain location of the scheduled data channel based on the first information in S220 may include any one of the following methods 31-32.

[0173] Method 31: When there are multiple data channels and the first information is also used to indicate or configure multiple first lists (such as {K, SLIV value}), the terminal determines the time-domain position of each data channel according to each of the first lists. Each of the first lists includes a fifth parameter and an SLIV value. The fifth parameter indicates the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0174] For example, assuming the first information is carried in the TDRA domain of the DCI, and the first information is used to indicate or configure time-domain resource allocation parameters and multiple first lists, then for each of the first lists, the time-domain location of the multiple data channels to be scheduled can be determined according to the time-domain location determination scheme in the aforementioned method embodiment 200 or 300.

[0175] Method 32: When there are multiple data channels and the first information is also used to indicate or configure multiple second lists (e.g., K, SLIV list), for each second list, the terminal determines the time-domain position of each data channel according to each parameter group (e.g.) in the second list. Wherein, the time-domain positions of multiple data channels determined based on the parameter group in the same second list are located within the same time unit group. The parameter group includes a fifth parameter and an SLIV list. The fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0176] For example, assuming the first information is carried in the TDRA domain of the DCI, and the first information is used to indicate or configure time-domain resource allocation parameters and multiple second lists, then for each parameter group in each of the second lists, the time-domain positions of multiple data channels located in the same time unit group can be determined according to the time-domain position determination scheme in the aforementioned method embodiments 200 or 300. That is, the time-domain positions of data channels determined based on the same second list are located in the same time unit group, and the time-domain positions of data channels determined based on different second categories are located in different time unit groups.

[0177] In this embodiment, flexible and efficient scheduling of multiple data channels can be achieved through the implementation of the aforementioned method 31 or method 32.

[0178] In some embodiments, where the first information is also used to indicate or configure the number of repetitions of the data channel, embodiment 200 of this method may further include: the terminal using the determined time-domain position of the data channel as the first repetition occasion of the data channel; and based on the first repetition occasion, the terminal repetitively transmitting the data channel according to the number of repetitions, thereby enabling more flexible or efficient repetition scheduling for a single data channel. Wherein, the interval between each repetition occasion is x time units, where x is a positive integer, or there is no interval between each repetition occasion.

[0179] In some embodiments, it is assumed that the terminal can perform repeated transmission of the data channel based on a repeated transmission mode, wherein the repeated transmission mode includes a first mode or a second mode, the first mode is in which the interval between each repeated transmission opportunity is x time units, and the second mode is in which there is no interval between each repeated transmission opportunity. Therefore, when the terminal performs repeated transmission of the data channel, the actual repeated transmission mode (such as the first mode or the second mode) adopted can be implemented by protocol agreement, terminal determination, network configuration, etc., and is not limited here.

[0180] For example, in the case determined by the terminal, when performing repeated transmission of the data channel, the terminal can determine the repeated transmission mode of the data channel based on the time-domain allocation information of the first repeated timing. For instance, when the time-domain allocation information of the first repeated timing indicates that the first repeated transmission timing is within one time unit (e.g., a time slot), the terminal can determine the repeated transmission mode as a first mode; or, for another example, when the time-domain allocation information of the first repeated timing indicates that the first repeated transmission timing spans at least two time units (e.g., time slots), the terminal can determine the repeated transmission mode as a second mode, and so on, without limitation.

[0181] In some embodiments, the method embodiment 200 may further include: in the event of a resource conflict during the first repeated transmission, the terminal performs at least one of the following processing on the conflicting transmission resources: puncture, rate matching, and postpone. This embodiment provides a solution for handling resource conflicts during repeated transmissions, ensuring both resource flexibility and efficiency while maintaining the reliability of the data channel transmission.

[0182] Optionally, the resources in the event of a resource conflict may include, but are not limited to, one or more of the following: frequency domain resources (such as resource elements (REs), physical resource blocks (PRBs)), time domain resources (such as symbols), and spatial domain resources.

[0183] Optionally, the conflict may include: the first repeated transmission timing of the data channel conflicting with the transmission timing of the semi-static uplink (UL) or the transmission timing of the downlink (DL); and / or, the data channel conflicting with at least one of the Channel State Information Reference Signal (CSI-RS), Sounding Reference Signal (SRS), Random Access Channel (RACH), and PUCCH.

[0184] In this embodiment, by introducing flexible and configurable or indicative time-domain resource allocation parameters, such as resource allocation granularity, resource allocation range, and resource indication granularity, more flexible and efficient resource scheduling can be achieved.

[0185] Figure 8 shows a flowchart of a resource scheduling method 800 provided in an exemplary embodiment of this application. This method 800 can be executed by, but is not limited to, a network-side device, specifically by hardware and / or software installed in the network-side device. In this embodiment, the method 800 may include at least the following steps.

[0186] S810, the network-side device sends the first message.

[0187] The first information is used to indicate or configure the time-domain resource allocation parameters of the scheduled data channel, and the time-domain resource allocation parameters include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0188] In some embodiments, the first information includes at least one of the following: a first parameter, which is a parameter for a flexible time unit; a second parameter, which is a parameter for other channel configurations, wherein the other channels are channels other than the data channel; a third parameter, which is a parameter for the data channel; first indication information, which is used to indicate a first time domain allocation item, wherein the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list including at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity; a configuration period for the listening timing; a configuration period for the physical downlink control channel (PDCCH) listening time; and at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

[0189] In some embodiments, at least one of the first parameter, the second parameter, the third parameter, and the time-domain allocation list is configured per per cell group, or per cell, or per bandwidth portion of the BWP.

[0190] In some embodiments, when the first information includes the configuration period of the listening timing and the configuration period of the listening timing is X time units, the resource allocation granularity is Y1 sub-time units, the resource allocation range is Y2 time units, and the resource indication granularity is Y3 time units, wherein X, Y1, Y2, and Y3 are all integers not less than 1, at least one of Y1, Y2, and Y3 is equal to X, and one time unit includes multiple sub-time units.

[0191] In some embodiments, the indicative or configurable value of the time-domain resource allocation parameter is related to at least one of the following: the subcarrier spacing (SCS) of the data channel; the format of the second indication information; the radio network temporary identifier (RNTI) of the second indication information; and the scheduling mode of the data channel, wherein the scheduling mode is one of unicast, multicast, or broadcast; wherein the second indication information is used to schedule the data channel.

[0192] In some embodiments, when the time-domain resource allocation parameters are configured per BWP and the data channel is scheduled when a BWP handover occurs, the time-domain resource allocation parameters correspond to at least one of a first BWP and a second BWP; wherein the first BWP is the BWP used before the BWP handover occurs, and the second BWP is the BWP used after the BWP handover occurs.

[0193] In some embodiments, the first information is further used to indicate or configure the SLIV value, wherein there is a first correlation between the resource allocation granularity, the resource allocation range, the SLIV value, and the first temporal location information, and the first correlation is represented by any of the following: Where (L1-1)≤7*R / G; Wherein, (L1-1)>7*R / G; where R represents the resource allocation range, G represents the resource allocation granularity, S1 represents the first starting sub-time unit in the first time domain location information, L1 represents the number of first starting sub-time units in the first time domain location information, and 0 <L1≤14-S1。

[0194] In some embodiments, the first information is transmitted via at least one of the following: Downlink Control Information (DCI); Media Resource Control Unit (MAC CE); Radio Resource Control (RRC) signaling.

[0195] It is understood that each implementation in this method embodiment 800 has the same or corresponding technical features as the aforementioned method embodiment 200. Therefore, the implementation of each implementation in this method embodiment 800 can be referred to the relevant description in the aforementioned method embodiment 200 to achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0196] The resource scheduling method provided in this application can be executed by a resource scheduling device. This application uses the example of a resource scheduling device executing the resource scheduling method to illustrate the resource scheduling device provided in this application.

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

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

[0199] Specifically, referring to Figure 9, when the resource scheduling device is a terminal or a component in a terminal, the resource scheduling device 900 includes a receiving module 910 for receiving first information from a network-side device; and a processing module 920 for determining the time-domain location of the scheduled data channel based on the first information; wherein the first information is used to indicate or configure time-domain resource allocation parameters, and the time-domain resource allocation parameters include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0200] In some embodiments, the first information includes at least one of the following: a first parameter, which is a parameter for a flexible time unit; a second parameter, which is a parameter for other channel configurations, wherein the other channels are channels other than the data channel; a third parameter, which is a parameter for the data channel; first indication information, which is used to indicate a first time domain allocation item, wherein the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list including at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity; a configuration period for the listening timing; a configuration period for the physical downlink control channel (PDCCH) listening time; and at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

[0201] In some embodiments, at least one of the first parameter, the second parameter, the third parameter, and the time-domain allocation list is configured per per cell group, or per cell, or per bandwidth portion of the BWP.

[0202] In some embodiments, when the first information includes the configuration period of the listening timing and the configuration period of the listening timing is X time units, the resource allocation granularity is Y1 sub-time units, the resource allocation range is Y2 time units, and the resource indication granularity is Y3 time units, wherein X, Y1, Y2, and Y3 are all integers not less than 1, at least one of Y1, Y2, and Y3 is equal to X, and one time unit includes multiple sub-time units.

[0203] In some embodiments, the indicative or configurable value of the time-domain resource allocation parameter is related to at least one of the following: the subcarrier spacing (SCS) of the data channel; the format of the second indication information; the radio network temporary identifier (RNTI) of the second indication information; and the scheduling mode of the data channel, wherein the scheduling mode is one of unicast, multicast, or broadcast; wherein the second indication information is used to schedule the data channel.

[0204] In some embodiments, when the time-domain resource allocation parameters are configured per BWP and the data channel is scheduled when a BWP handover occurs, the time-domain resource allocation parameters correspond to at least one of a first BWP and a second BWP; wherein the first BWP is the BWP used before the BWP handover occurs, and the second BWP is the BWP used after the BWP handover occurs.

[0205] In some embodiments, the first information is further used to indicate start and length indication values ​​(SLIVs). Determining the time-domain location of the scheduled data channel based on the first information includes: determining first time-domain location information based on the time-domain resource allocation parameters, the SLIV value, and a first correlation, wherein the first time-domain location information includes a first starting sub-time unit and a number of first sub-time units; determining the starting sub-time unit of the data channel based on the first starting sub-time unit; and determining the number of consecutive sub-time units occupied by the data channel based on the number of first sub-time units; wherein the first correlation is used to characterize the correlation between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

[0206] In some embodiments, the first information is further used to indicate or configure the SLIV value. Determining the time-domain location of the scheduled data channel based on the first information includes: determining the time unit group in which the data channel belongs, and determining the starting sub-time unit of the time unit group as a reference sub-time unit; determining the time-domain location information of the data channel based on the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and a first correlation, wherein the time-domain location information includes the starting sub-time unit of the data channel and the number of consecutive sub-time units occupied by the data channel; wherein the first correlation is used to characterize the correlation between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

[0207] In some embodiments, the first information is further used to indicate or configure a fifth parameter. Determining the time unit group to which the data channel belongs includes at least one of the following: determining the time unit group to which the data channel belongs based on a first index and the fifth parameter, wherein the first index is the index of the time unit group to which the first information is located, the resource allocation range is the same as the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range; determining a first time unit based on a second index, the fifth parameter, and the resource indication granularity, and determining the time unit group to which the first time unit belongs as the time unit group to which the data channel belongs, wherein... The second index is the index of the time unit where the first information is located, or the second index is the index of the start or end time unit of the time unit group where the first information is located. The resource allocation range is different from the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range. The time unit group where the data channel is located is determined according to the start or end sub-time unit of the monitoring timing where the first information is located, wherein the parameter value of the fifth parameter is 0. The fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0208] In some embodiments, when the time unit group to which the data channel belongs is determined based on the first index and the fifth parameter, the index Ksg of the time unit group to which the data channel belongs is n1+K; or, when the first time unit is determined based on the second index, the fifth parameter and the resource indication granularity, the index Ks of the first time unit is n2+K*M; wherein, n1 represents the first index, n2 represents the second index, K represents the fifth parameter, and M represents the resource allocation granularity.

[0209] In some embodiments, when the time unit group of the data channel is determined according to the start or end sub-time unit of the monitoring time when the first information is located, the end sub-time unit of the monitoring time when the first information is located is the R*Ath sub-time unit after the start sub-time unit, where R represents the number of time units in the time unit group and A represents the number of sub-time units in each time unit.

[0210] In some embodiments, the first information is further used to indicate that the data channel is cross-carrier scheduling, or the first information is further used to indicate that the data channel is cross-BWP scheduling within the same carrier. Determining the time unit group in which the data channel is located includes: determining the time unit group in which the data channel is located based on at least one of the time domain allocation parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, the third index, and the fifth parameter; wherein, the time domain resource allocation parameter corresponds to the second object, the first object is the source carrier in cross-carrier scheduling or the original BWP in cross-BWP scheduling, the second object is the target carrier in cross-carrier scheduling or the target BWP in cross-BWP scheduling, the third index is the index of the time unit group in which the first information is located or the index of the start sub-time unit or the end sub-time unit of the time unit group in which the first information is located or the index of the time unit group in which the first information is located, and the fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0211] In some embodiments, determining the time unit group to which the data channel belongs based on at least one of the time-domain allocation parameters, the SCS corresponding to the first object, the SCS corresponding to the second object, the third index, and the fifth parameter includes at least one of the following: determining the time unit group to which the data channel belongs based on the third index, the fifth parameter, the SCS corresponding to the first object, and the SCS corresponding to the second object, wherein the third index is the index of the time unit group to which the first information belongs, the resource allocation range is the same as the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range; determining the second time unit based on at least one of the third index, the fifth parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, and the resource indication granularity, and determining the time unit group to which the second time unit belongs as the time unit group to which the data channel belongs, wherein the third index is the index of the start sub-time unit or the end sub-time unit of the time unit group to which the first information belongs, or the third index is the index of the time unit to which the first information belongs, the resource allocation range is different from the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range.

[0212] In some embodiments, when the time unit group to which the data channel belongs is determined according to the third index, the fifth parameter, the SCS corresponding to the first object, and the SCS corresponding to the second object, the index Ksg of the time unit group to which the data channel belongs is floor(n3*(μ1 / μ2) / R)+K; and / or, when the second time unit is determined according to at least one of the third index, the fifth parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, and the resource indication granularity, the index Ks of the second time unit is n3+K*M, or the index Ks of the second time unit is floor(n3*(μ1 / μ2))+K*M; wherein, n3 represents the time unit to which the first information is located on the first object, n3 represents the time unit to which the first information is located on the first object, or n3 represents the start time unit or end time unit of the time unit group to which the first information is located on the first object, K represents the fifth parameter, μ1 represents the SCS corresponding to the first object, μ2 represents the SCS corresponding to the second object, and M represents the time domain resource granularity corresponding to the second object.

[0213] In some embodiments, determining the time-domain location information of the data channel based on the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and the first association relationship includes: determining first time-domain location information based on the time-domain resource allocation parameters and the first association relationship, wherein the first time-domain location information includes a first start sub-time unit and a number of first sub-time units; determining the starting sub-time unit of the data channel based on the first start sub-time unit and the resource allocation granularity; and determining the number of consecutive sub-time units occupied by the data channel based on the length of the first sub-time unit and the resource allocation granularity.

[0214] In some embodiments, the index S of the starting sub-time unit of the data channel is determined by the formula S = S2 + S1 * G; and / or, the number L of consecutive sub-time units occupied by the data channel is determined by the formula L = L1 * G; wherein, S2 is the reference sub-time unit, S1 represents the first starting sub-time unit, G represents the resource allocation granularity, and L1 represents the length of the first sub-time unit.

[0215] In some embodiments, the first association is represented by any of the following: Where (L1-1)≤7*R / G; Wherein, (L1-1)>7*R / G; where R represents the resource allocation range, G represents the resource allocation granularity, S1 represents the first starting sub-time unit in the first time domain location information, L1 represents the number of first starting sub-time units in the first time domain location information, and 0 <L1≤14-S1。

[0216] In some embodiments, where the first information is also used to indicate or configure the number of retransmissions of the data channel, the processing module 920 is further configured to: take the determined time-domain position of the data channel as the first retransmission opportunity of the data channel; and to perform retransmissions of the data channel according to the number of retransmissions based on the first retransmission opportunity; wherein the interval between each retransmission opportunity is x time units, where x is a positive integer, or there is no interval between each retransmission opportunity.

[0217] In some embodiments, the processing module 920 is further configured to: determine the repetition transmission mode of the data channel based on the time-domain allocation information of the first repetition timing; wherein the repetition transmission mode includes a first mode or a second mode, the first mode being that the interval between each repetition timing is x time units, and the second mode being that there is no interval between each repetition timing.

[0218] In some embodiments, the processing module 920 is further configured to: in the event of a resource conflict during the first repeated transmission, perform at least one of the following processing on the conflicting transmission resources: puncture, rate matching, and postponing.

[0219] In some embodiments, the number of time units occupied by the time domain location of the data channel does not exceed the number of time units corresponding to the resource allocation range; and / or, the transport block size corresponding to the data channel does not exceed a predetermined value.

[0220] In some embodiments, determining the time-domain location of the scheduled data channel based on the first information includes any one of the following: when there are multiple data channels and the first information is also used to indicate or configure multiple first lists, the terminal determines the time-domain location of each data channel based on each of the first lists, wherein each of the first lists includes a fifth parameter and an SLIV value; when there are multiple data channels and the first information is also used to indicate or configure multiple second lists, for each of the second lists, the terminal determines the time-domain location of each data channel based on each parameter group in the second list, wherein the time-domain locations of multiple data channels determined based on the parameter group in the same second list are located within the same time unit group, the parameter group including a fifth parameter and an SLIV list; wherein the fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0221] In some embodiments, the first information is transmitted via at least one of the following: Downlink Control Information (DCI); Media Resource Control Unit (MAC CE); Radio Resource Control (RRC) signaling.

[0222] The resource scheduling device 900 provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 2 to 7 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0223] Referring to Figure 10, when the resource scheduling device is a network-side device or a component of a network-side device, the resource scheduling device 1000 includes a sending module 1010 for sending first information; wherein, the first information is used to indicate or configure the time-domain resource allocation parameters of the scheduled data channel, and the time-domain resource allocation parameters include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0224] In some embodiments, as shown in FIG10, the resource scheduling device 1000 further includes a processing module 1020 for determining the first information.

[0225] In some embodiments, the first information includes at least one of the following: a first parameter, which is a parameter for a flexible time unit; a second parameter, which is a parameter for other channel configurations, wherein the other channels are channels other than the data channel; a third parameter, which is a parameter for the data channel; first indication information, which is used to indicate a first time domain allocation item, wherein the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list including at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity; a configuration period for the listening timing; a configuration period for the physical downlink control channel (PDCCH) listening time; and at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

[0226] In some embodiments, at least one of the first parameter, the second parameter, the third parameter, and the time-domain allocation list is configured per per cell group, or per cell, or per bandwidth portion of the BWP.

[0227] In some embodiments, when the first information includes the configuration period of the listening timing and the configuration period of the listening timing is X time units, the resource allocation granularity is Y1 sub-time units, the resource allocation range is Y2 time units, and the resource indication granularity is Y3 time units, wherein X, Y1, Y2, and Y3 are all integers not less than 1, at least one of Y1, Y2, and Y3 is equal to X, and one time unit includes multiple sub-time units.

[0228] In some embodiments, the indicative or configurable value of the time-domain resource allocation parameter is related to at least one of the following: the subcarrier spacing (SCS) of the data channel; the format of the second indication information; the radio network temporary identifier (RNTI) of the second indication information; and the scheduling mode of the data channel, wherein the scheduling mode is one of unicast, multicast, or broadcast; wherein the second indication information is used to schedule the data channel.

[0229] In some embodiments, when the time-domain resource allocation parameters are configured per BWP and the data channel is scheduled when a BWP handover occurs, the time-domain resource allocation parameters correspond to at least one of a first BWP and a second BWP; wherein the first BWP is the BWP used before the BWP handover occurs, and the second BWP is the BWP used after the BWP handover occurs.

[0230] In some embodiments, the first information is further used to indicate or configure the SLIV value, wherein there is a first correlation between the resource allocation granularity, the resource allocation range, the SLIV value, and the first temporal location information, and the first correlation is represented by any of the following: Where (L1-1)≤7*R / G; Wherein, (L1-1)>7*R / G; where R represents the resource allocation range, G represents the resource allocation granularity, S1 represents the first starting sub-time unit in the first time domain location information, L1 represents the number of first starting sub-time units in the first time domain location information, and 0 <L1≤14-S1。

[0231] In some embodiments, the first information is transmitted via at least one of the following: Downlink Control Information (DCI); Media Resource Control Unit (MAC CE); Radio Resource Control (RRC) signaling.

[0232] The resource scheduling device 1000 provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG8 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0233] As shown in Figure 11, this application embodiment also provides a communication device 1100, including a processor 1101 and a memory 1102. The memory 1102 stores programs or instructions that can run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instructions executed by the processor 1101 implement the various steps of the resource scheduling method embodiment 200 described above, and achieve the same technical effect. When the communication device 1100 is a network-side device, the program or instructions executed by the processor 1101 implement the various steps of the resource scheduling method embodiment 800 described above, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0234] This 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 used to run programs or instructions to implement the steps in the method embodiments shown in Figures 2-7. This terminal embodiment corresponds to the above-described terminal-side method embodiments, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal may be the resource scheduling device shown in Figure 9. Specifically, Figure 12 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0235] The terminal 1200 includes, but is not limited to, at least some of the following components: radio frequency unit 1201, network module 1202, audio output unit 1203, input unit 1204, sensor 1205, display unit 1206, user input unit 1207, interface unit 1208, memory 1209, and processor 1210.

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

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

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

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

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

[0241] The radio frequency unit 1201 is used to receive first information from the network-side device; the processor 1210 is used to determine the time domain location of the scheduled data channel based on the first information; wherein the first information is used to indicate or configure time domain resource allocation parameters, and the time domain resource allocation parameters include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0242] In some embodiments, the first information includes at least one of the following: a first parameter, which is a parameter for a flexible time unit; a second parameter, which is a parameter for other channel configurations, wherein the other channels are channels other than the data channel; a third parameter, which is a parameter for the data channel; first indication information, which is used to indicate a first time domain allocation item, wherein the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list including at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity; a configuration period for the listening timing; a configuration period for the physical downlink control channel (PDCCH) listening time; and at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

[0243] In some embodiments, at least one of the first parameter, the second parameter, the third parameter, and the time-domain allocation list is configured per per cell group, or per cell, or per bandwidth portion of the BWP.

[0244] In some embodiments, when the first information includes the configuration period of the listening timing and the configuration period of the listening timing is X time units, the resource allocation granularity is Y1 sub-time units, the resource allocation range is Y2 time units, and the resource indication granularity is Y3 time units, wherein X, Y1, Y2, and Y3 are all integers not less than 1, at least one of Y1, Y2, and Y3 is equal to X, and one time unit includes multiple sub-time units.

[0245] In some embodiments, the indicative or configurable value of the time-domain resource allocation parameter is related to at least one of the following: the subcarrier spacing (SCS) of the data channel; the format of the second indication information; the radio network temporary identifier (RNTI) of the second indication information; and the scheduling mode of the data channel, wherein the scheduling mode is one of unicast, multicast, or broadcast; wherein the second indication information is used to schedule the data channel.

[0246] In some embodiments, when the time-domain resource allocation parameters are configured per BWP and the data channel is scheduled when a BWP handover occurs, the time-domain resource allocation parameters correspond to at least one of a first BWP and a second BWP; wherein the first BWP is the BWP used before the BWP handover occurs, and the second BWP is the BWP used after the BWP handover occurs.

[0247] In some embodiments, the first information is further used to indicate start and length indication values ​​(SLIVs). Determining the time-domain location of the scheduled data channel based on the first information includes: determining first time-domain location information based on the time-domain resource allocation parameters, the SLIV value, and a first correlation, wherein the first time-domain location information includes a first starting sub-time unit and a number of first sub-time units; determining the starting sub-time unit of the data channel based on the first starting sub-time unit; and determining the number of consecutive sub-time units occupied by the data channel based on the number of first sub-time units; wherein the first correlation is used to characterize the correlation between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

[0248] In some embodiments, the first information is further used to indicate or configure a fifth parameter. Determining the time-domain location of the scheduled data channel based on the first information includes: when the parameter value of the fifth parameter is 0, determining the start sub-time unit or end sub-time unit of the monitoring timing where the first information is located as the start sub-time unit of the time unit group where the data channel is located; determining the end sub-time unit of the time unit group where the data channel is located based on the start sub-time unit of the time unit group and the number of sub-time units in each time unit; wherein the fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0249] In some embodiments, the end sub-time unit of the monitoring timing where the first information is located is the R*Ath sub-time unit after the start sub-time unit, where R represents the number of time units in the time unit group and A represents the number of sub-time units in each time unit.

[0250] In some embodiments, the first information is further used to indicate or configure the SLIV value. Determining the time-domain location of the scheduled data channel based on the first information includes: determining the time unit group in which the data channel belongs, and determining the starting sub-time unit of the time unit group as a reference sub-time unit; determining the time-domain location information of the data channel based on the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and a first correlation, wherein the time-domain location information includes the starting sub-time unit of the data channel and the number of consecutive sub-time units occupied by the data channel; wherein the first correlation is used to characterize the correlation between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

[0251] In some embodiments, the first information is further used to indicate or configure a fifth parameter. Determining the time unit group in which the data channel is located includes at least one of the following: determining the time unit group in which the data channel is located based on a first index and the fifth parameter, wherein the first index is the index of the time unit group in which the first information is located, the resource allocation range is the same as the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range; determining a first time unit based on a second index, the fifth parameter, and the resource indication granularity, and determining the time unit group in which the first time unit is located as the time unit group in which the data channel is located, wherein the second index is the index of the time unit in which the first information is located, or the second index is the index of the start time unit or end time unit of the time unit group in which the first information is located, the resource allocation range is different from the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range; wherein the fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0252] In some embodiments, when the time unit group to which the data channel belongs is determined based on the first index and the fifth parameter, the index Ksg of the time unit group to which the data channel belongs is n1+K; or, when the first time unit is determined based on the second index, the fifth parameter and the resource indication granularity, the index Ks of the first time unit is n2+K*M; wherein, n1 represents the first index, n2 represents the second index, K represents the fifth parameter, and M represents the resource allocation granularity.

[0253] In some embodiments, the first information is further used to indicate that the data channel is cross-carrier scheduling, or the first information is further used to indicate that the data channel is cross-BWP scheduling within the same carrier. Determining the time unit group in which the data channel is located includes: determining the time unit group in which the data channel is located based on at least one of the time domain allocation parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, the third index, and the fifth parameter; wherein, the time domain resource allocation parameter corresponds to the second object, the first object is the source carrier in cross-carrier scheduling or the original BWP in cross-BWP scheduling, the second object is the target carrier in cross-carrier scheduling or the target BWP in cross-BWP scheduling, the third index is the index of the time unit group in which the first information is located or the index of the start sub-time unit or the end sub-time unit of the time unit group in which the first information is located or the index of the time unit group in which the first information is located, and the fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0254] In some embodiments, determining the time unit group to which the data channel belongs based on at least one of the time-domain allocation parameters, the SCS corresponding to the first object, the SCS corresponding to the second object, the third index, and the fifth parameter includes at least one of the following: determining the time unit group to which the data channel belongs based on the third index, the fifth parameter, the SCS corresponding to the first object, and the SCS corresponding to the second object, wherein the third index is the index of the time unit group to which the first information belongs, the resource allocation range is the same as the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range; determining the second time unit based on at least one of the third index, the fifth parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, and the resource indication granularity, and determining the time unit group to which the second time unit belongs as the time unit group to which the data channel belongs, wherein the third index is the index of the start sub-time unit or the end sub-time unit of the time unit group to which the first information belongs, or the third index is the index of the time unit to which the first information belongs, the resource allocation range is different from the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range.

[0255] In some embodiments, when the time unit group to which the data channel belongs is determined according to the third index, the fifth parameter, the SCS corresponding to the first object, and the SCS corresponding to the second object, the index Ksg of the time unit group to which the data channel belongs is floor(n3*(μ1 / μ2) / R)+K; and / or, when the second time unit is determined according to at least one of the third index, the fifth parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, and the resource indication granularity, the index Ks of the second time unit is n3+K*M, or the index Ks of the second time unit is floor(n3*(μ1 / μ2))+K*M; wherein, n3 represents the time unit to which the first information is located on the first object, n3 represents the time unit to which the first information is located on the first object, or n3 represents the start time unit or end time unit of the time unit group to which the first information is located on the first object, K represents the fifth parameter, μ1 represents the SCS corresponding to the first object, μ2 represents the SCS corresponding to the second object, and M represents the time domain resource granularity corresponding to the second object.

[0256] In some embodiments, determining the time-domain location information of the data channel based on the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and the first association relationship includes: determining first time-domain location information based on the time-domain resource allocation parameters and the first association relationship, wherein the first time-domain location information includes a first start sub-time unit and a number of first sub-time units; determining the starting sub-time unit of the data channel based on the first start sub-time unit and the resource allocation granularity; and determining the number of consecutive sub-time units occupied by the data channel based on the length of the first sub-time unit and the resource allocation granularity.

[0257] In some embodiments, the index S of the starting sub-time unit of the data channel is determined by the formula S = S2 + S1 * G; and / or, the number L of consecutive sub-time units occupied by the data channel is determined by the formula L = L1 * G; wherein, S2 is the reference sub-time unit, S1 represents the first starting sub-time unit, G represents the resource allocation granularity, and L1 represents the length of the first sub-time unit.

[0258] In some embodiments, the first association is represented by any of the following: Where (L1-1)≤7*R / G; Wherein, (L1-1)>7*R / G; where R represents the resource allocation range, G represents the resource allocation granularity, S1 represents the first starting sub-time unit in the first time domain location information, L1 represents the number of first starting sub-time units in the first time domain location information, and 0 <L1≤14-S1。

[0259] In some embodiments, where the first information is further used to indicate or configure the number of retransmissions of the data channel, the processor 1210 is further used to: take the determined time-domain position of the data channel as the first retransmission opportunity of the data channel; the radio frequency unit 1201 is used to, based on the first retransmission opportunity, have the terminal retransmit the data channel according to the number of retransmissions; wherein the interval between each retransmission opportunity is x time units, where x is a positive integer, or there is no interval between each retransmission opportunity.

[0260] In some embodiments, the processor 1210 is further configured to: the terminal determine the repetition transmission mode of the data channel based on the time-domain allocation information of the first repetition timing; wherein the repetition transmission mode includes a first mode or a second mode, the first mode being that the interval between each repetition timing is x time units, and the second mode being that there is no interval between each repetition timing.

[0261] In some embodiments, the processor 1210 is further configured to: in the event of a resource conflict during the first repeated transmission, perform at least one of the following processes on the conflicting transmission resources: puncture, rate matching, and postponing.

[0262] In some embodiments, the number of time units occupied by the time domain location of the data channel does not exceed the number of time units corresponding to the resource allocation range; and / or, the transport block size corresponding to the data channel does not exceed a predetermined value.

[0263] In some embodiments, determining the time-domain location of the scheduled data channel based on the first information includes any one of the following: when there are multiple data channels and the first information is also used to indicate or configure multiple first lists, the terminal determines the time-domain location of each data channel based on each of the first lists, wherein each of the first lists includes a fifth parameter and an SLIV value; when there are multiple data channels and the first information is also used to indicate or configure multiple second lists, for each of the second lists, the terminal determines the time-domain location of each data channel based on each parameter group in the second list, wherein the time-domain locations of multiple data channels determined based on the parameter group in the same second list are located within the same time unit group, the parameter group including a fifth parameter and an SLIV list; wherein the fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

[0264] In some embodiments, the first information is transmitted via at least one of the following: Downlink Control Information (DCI); Media Resource Control Unit (MAC CE); Radio Resource Control (RRC) signaling.

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

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

[0267] Specifically, this application embodiment also provides a network-side device, which may be the resource scheduling device 1000 shown in FIG10. As shown in FIG13, the network-side device 1300 includes: an antenna 1301, a radio frequency device 1302, a baseband device 1303, a processor 1304, and a memory 1305. The antenna 1301 is connected to the radio frequency device 1302. In the uplink direction, the radio frequency device 1302 receives information through the antenna 1301 and sends the received information to the baseband device 1303 for processing. In the downlink direction, the baseband device 1303 processes the information to be transmitted and sends it to the radio frequency device 1302, which processes the received information and then transmits it through the antenna 1301.

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

[0269] The baseband device 1303 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG13. One of the chips is, for example, a baseband processor, which is connected to the memory 1305 via a bus interface to call the program or instructions in the memory 1305 to execute the network-side device operation shown in the above method embodiment.

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

[0271] The radio frequency device 1302 is used to transmit first information; wherein the first information is used to indicate or configure the time-domain resource allocation parameters of the scheduled data channel, and the time-domain resource allocation parameters include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

[0272] In some embodiments, the first information includes at least one of the following: a first parameter, which is a parameter for a flexible time unit; a second parameter, which is a parameter for other channel configurations, wherein the other channels are channels other than the data channel; a third parameter, which is a parameter for the data channel; first indication information, which is used to indicate a first time domain allocation item, wherein the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list including at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity; a configuration period for the listening timing; a configuration period for the physical downlink control channel (PDCCH) listening time; and at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

[0273] In some embodiments, at least one of the first parameter, the second parameter, the third parameter, and the time-domain allocation list is configured per per cell group, or per cell, or per bandwidth portion of the BWP.

[0274] In some embodiments, when the first information includes the configuration period of the listening timing and the configuration period of the listening timing is X time units, the resource allocation granularity is Y1 sub-time units, the resource allocation range is Y2 time units, and the resource indication granularity is Y3 time units, wherein X, Y1, Y2, and Y3 are all integers not less than 1, at least one of Y1, Y2, and Y3 is equal to X, and one time unit includes multiple sub-time units.

[0275] In some embodiments, the indicative or configurable value of the time-domain resource allocation parameter is related to at least one of the following: the subcarrier spacing (SCS) of the data channel; the format of the second indication information; the radio network temporary identifier (RNTI) of the second indication information; and the scheduling mode of the data channel, wherein the scheduling mode is one of unicast, multicast, or broadcast; wherein the second indication information is used to schedule the data channel.

[0276] In some embodiments, when the time-domain resource allocation parameters are configured per BWP and the data channel is scheduled when a BWP handover occurs, the time-domain resource allocation parameters correspond to at least one of a first BWP and a second BWP; wherein the first BWP is the BWP used before the BWP handover occurs, and the second BWP is the BWP used after the BWP handover occurs.

[0277] In some embodiments, the first information is further used to indicate or configure the SLIV value, wherein there is a first correlation between the resource allocation granularity, the resource allocation range, the SLIV value, and the first temporal location information, and the first correlation is represented by any of the following: Where, (L1-1)≤7*R / G; Wherein, (L1-1)>7*R / G; where R represents the resource allocation range, G represents the resource allocation granularity, S1 represents the first starting sub-time unit in the first time domain location information, L1 represents the number of the first starting sub-time units in the first time domain location information, 0 <L1≤14-S1。

[0278] In some embodiments, the first information is transmitted via at least one of the following: Downlink Control Information (DCI); Media Resource Control Unit (MAC CE); Radio Resource Control (RRC) signaling.

[0279] In addition, the network-side device 1300 of this application embodiment also includes: a program or instructions stored in the memory 1305 and executable on the processor 1304. The processor 1304 calls the program or instructions in the memory 1305 to execute the methods executed by each module shown in FIG10 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

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

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

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

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

[0284] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described resource scheduling method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0285] This application also provides a wireless communication system, including a terminal and a network-side device. The terminal can be used to implement the various processes of the resource scheduling method embodiment 200 described above, and the network-side device can be used to implement the various processes of the resource scheduling method embodiment 800 described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

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

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

Claims

1. A resource scheduling method, comprising: The terminal receives the first information from the network-side device; The terminal determines the time domain location of the scheduled data channel based on the first information; The first information is used to indicate or configure time-domain resource allocation parameters, which include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

2. The method according to claim 1, wherein, The first information includes at least one of the following: The first parameter is a parameter used for flexible time units; The second parameter is a parameter used for configuring other channels, which are channels other than the data channel; The third parameter is a parameter used for the data channel; First indication information, the first indication information is used to indicate a first time domain allocation item, the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list includes at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity; The configuration cycle for monitoring timing; Configuration period for Physical Downlink Control Channel (PDCCH) listening time; At least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

3. The method according to claim 2, wherein, The first parameter, the second parameter, the third parameter, and at least one of the time-domain allocation list are configured per per cell group, or per cell, or per bandwidth portion of the BWP.

4. The method according to claim 2, wherein, When the first information includes the configuration period of the listening timing and the configuration period of the listening timing is X time units, the resource allocation granularity is Y1 sub-time units, the resource allocation range is Y2 time units, and the resource indication granularity is Y3 time units, wherein X, Y1, Y2, and Y3 are all integers not less than 1, at least one of Y1, Y2, and Y3 is equal to X, and one time unit includes multiple sub-time units.

5. The method according to any one of claims 1-4, wherein, The indicative or configurable value of the time-domain resource allocation parameter is related to at least one of the following: The subcarrier spacing (SCS) of the data channel; The format of the second instruction message; The second instruction information includes the Wireless Network Temporary Identifier (RNTI). The data channel scheduling method is one of unicast, multicast, and broadcast. The second indication information is used to schedule the data channel.

6. The method according to any one of claims 1-5, wherein, When the time-domain resource allocation parameters are configured per BWP and the data channel is scheduled during BWP handover, the time-domain resource allocation parameters correspond to at least one of the first BWP and the second BWP. Wherein, the first BWP is the BWP used before the BWP switchover occurs, and the second BWP is the BWP used after the BWP switchover occurs.

7. The method according to any one of claims 1-6, wherein, The first information is also used to indicate the start and length indication value (SLIV). Determining the time-domain location of the scheduled data channel based on the first information includes: The first time-domain location information is determined based on the time-domain resource allocation parameters, the SLIV value, and the first association relationship. The first time-domain location information includes the first starting sub-time unit and the number of first sub-time units. The starting sub-time unit of the data channel is determined based on the first starting sub-time unit, and the number of consecutive sub-time units occupied by the data channel is determined based on the number of the first sub-time units. The first association relationship is used to characterize the association relationship between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

8. The method according to any one of claims 1-6, wherein, The first information is also used to indicate or configure the SLIV value, and the step of determining the time-domain location of the scheduled data channel based on the first information includes: Determine the time unit group to which the data channel belongs, and determine the starting sub-time unit of the time unit group as the reference sub-time unit; The time-domain location information of the data channel is determined based on the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and the first correlation relationship. The time-domain location information includes the starting sub-time unit of the data channel and the number of consecutive sub-time units occupied by the data channel. The first association relationship is used to characterize the association relationship between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

9. The method according to claim 8, wherein, The first information is also used to indicate or configure the fifth parameter, wherein determining the time unit group in which the data channel belongs includes at least one of the following: The time unit group in which the data channel is located is determined according to the first index and the fifth parameter, wherein the first index is the index of the time unit group in which the first information is located, the resource allocation range is the same as the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range; The first time unit is determined according to the second index, the fifth parameter, and the resource indication granularity. The time unit group where the first time unit is located is determined as the time unit group where the data channel is located. The second index is the index of the time unit where the first information is located, or the second index is the index of the start time unit or the end time unit of the time unit group where the first information is located. The resource allocation range is different from the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range. The time unit group where the data channel is located is determined according to the start or end sub-time unit of the monitoring time when the first information is located, wherein the parameter value of the fifth parameter is 0; The fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

10. The method according to claim 9, wherein, When the time unit group to which the data channel belongs is determined based on the first index and the fifth parameter, the index of the time unit group to which the data channel belongs, Ksg = n1 + K; Alternatively, when the first time unit is determined based on the second index, the fifth parameter, and the resource indication granularity, the index Ks of the first time unit is n2 + K*M; Wherein, n1 represents the first index, n2 represents the second index, K represents the fifth parameter, and M represents the resource allocation granularity.

11. The method according to claim 9, wherein, When the time unit group of the data channel is determined based on the start or end sub-time unit of the monitoring time when the first information is located, the end sub-time unit of the monitoring time when the first information is located is the R*Ath sub-time unit after the start sub-time unit, where R represents the number of time units in the time unit group and A represents the number of sub-time units in each time unit.

12. The method according to claim 8, wherein, The first information is further used to indicate that the data channel is cross-carrier scheduling, or the first information is further used to indicate that the data channel is cross-BWP scheduling within the same carrier, wherein determining the time unit group to which the data channel belongs includes: The time unit group to which the data channel belongs is determined based on at least one of the time domain allocation parameters, the SCS corresponding to the first object, the SCS corresponding to the second object, the third index, and the fifth parameter. The time-domain resource allocation parameters correspond to the second object, the first object is the source carrier during cross-carrier scheduling or the source BWP during cross-BWP scheduling, the second object is the target carrier during cross-carrier scheduling or the target BWP during cross-BWP scheduling, the third index is the index of the time unit group where the first information is located or the index of the start sub-time unit or the end sub-time unit of the time unit group where the first information is located or the index of the time unit where the first information is located, and the fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

13. The method according to claim 12, wherein, Determining the time unit group to which the data channel belongs based on at least one of the time-domain allocation parameters, the SCS corresponding to the first object, the SCS corresponding to the second object, the third index, and the fifth parameter includes at least one of the following: Based on the third index, the fifth parameter, the SCS corresponding to the first object, and the SCS corresponding to the second object, the time unit group where the data channel is located is determined. The third index is the index of the time unit group where the first information is located. The resource allocation range is the same as the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range. A second time unit is determined based on at least one of the third index, the fifth parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, and the resource indication granularity. The time unit group to which the second time unit is located is determined as the time unit group to which the data channel is located. The third index is the index of the start sub-time unit or the end sub-time unit of the time unit group to which the first information is located, or the third index is the index of the time unit to which the first information is located. The resource allocation range is different from the resource allocation granularity, and the number of time units included in each time unit group is the same as the number of time units included in the resource allocation range.

14. The method according to claim 13, wherein, When the time unit group to which the data channel belongs is determined based on the third index, the fifth parameter, the SCS corresponding to the first object, and the SCS corresponding to the second object, the index Ksg of the time unit group to which the data channel belongs is floor(n3*(μ1 / μ2) / R)+K; And / or, When the second time unit is determined based on at least one of the third index, the fifth parameter, the SCS corresponding to the first object, the SCS corresponding to the second object, and the resource indication granularity, the index Ks of the second time unit is n3 + K*M, or the index Ks of the second time unit is floor(n3*(μ1 / μ2)) + K*M. Wherein, n3 represents the time unit in which the first information is located on the first object, n3 represents the time unit in which the first information is located on the first object, or n3 represents the start or end time unit of the time unit group in which the first information is located on the first object, K represents the fifth parameter, μ1 represents the SCS corresponding to the first object, μ2 represents the SCS corresponding to the second object, and M represents the temporal resource granularity corresponding to the second object.

15. The method according to any one of claims 8-14, wherein, Determining the time-domain location information of the data channel based on the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and the first correlation includes: The first time-domain location information is determined based on the time-domain resource allocation parameters and the first association relationship. The first time-domain location information includes the first start sub-time unit and the number of first sub-time units. The starting sub-time unit of the data channel is determined based on the first starting sub-time unit and the resource allocation granularity, and the number of consecutive sub-time units occupied by the data channel is determined based on the length of the first sub-time unit and the resource allocation granularity.

16. The method according to claim 15, wherein, The index S of the starting sub-time unit of the data channel is determined by the formula S = S2 + S1 * G. And / or, the number L of consecutive sub-time units occupied by the data channel is determined by the formula L = L1 * G; Wherein, S2 is the reference sub-time unit, S1 represents the first start sub-time unit, G represents the resource allocation granularity, and L1 represents the length of the first sub-time unit.

17. The method according to claim 7, 8, or 15, wherein, The first association is represented by any of the following: Where (L1-1)≤7*R / G; Among them, (L1-1)>7*R / G; Wherein, R represents the resource allocation range, G represents the resource allocation granularity, S1 represents the first starting sub-time unit in the first time-domain location information, L1 represents the number of first starting sub-time units in the first time-domain location information, and 0 <L1≤14-S1。 18. The method according to any one of claims 1-17, wherein, If the first information is also used to indicate or configure the number of retransmissions of the data channel, the method further includes: The terminal uses the determined time-domain position of the data channel as the first retransmission opportunity of the data channel. Based on the first repeated transmission opportunity, the terminal repeatedly transmits data to the data channel according to the number of repeated transmissions; The interval between each repeated transmission opportunity is x time units, where x is a positive integer, or there is no interval between each repeated transmission opportunity.

19. The method according to claim 18, wherein, The method further includes: The terminal determines the repetition transmission mode of the data channel based on the time-domain allocation information of the first repetition timing. The repeated transmission mode includes a first mode or a second mode, wherein the first mode is that the interval between each repeated transmission opportunity is x time units, and the second mode is that there is no interval between each repeated transmission opportunity.

20. The method according to claim 18 or 19, wherein, The method further includes: In the event of a resource conflict during the first repeated transmission, the terminal performs at least one of the following processes on the conflicting transmission resources: puncture, rate matching, and postponing.

21. The method according to any one of claims 1-17, wherein, The number of time units occupied by the time domain position of the data channel does not exceed the number of time units corresponding to the resource allocation range; And / or, The size of the transport block corresponding to the data channel does not exceed a predetermined value.

22. The method according to any one of claims 1-17, wherein, Determining the time-domain location of the scheduled data channel based on the first information includes any one of the following: When there are multiple data channels and the first information is also used to indicate or configure multiple first lists, the terminal determines the time domain position of each data channel according to each of the first lists, wherein each of the first lists includes a fifth parameter and a SLIV value; When there are multiple data channels and the first information is also used to indicate or configure multiple second lists, for each second list, the terminal determines the time domain position of each data channel according to each parameter group in the second list, wherein the time domain positions of multiple data channels determined based on the parameter group in the same second list are located in the same time unit group, and the parameter group includes a fifth parameter and a SLIV list; The fifth parameter is used to indicate the time unit-level offset between the data channel and the scheduling information, and the fifth parameter is determined based on the resource indication granularity.

23. The method according to any one of claims 1-22, wherein, The first information is transmitted via at least one of the following: Downlink Control Information (DCI); Media Resource Control Unit (MAC CE); Radio Resource Control (RRC) signaling.

24. A resource scheduling method, comprising: The network-side device sends the first message; The first information is used to indicate or configure the time-domain resource allocation parameters of the scheduled data channel, and the time-domain resource allocation parameters include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

25. The method according to claim 24, wherein, The first information includes at least one of the following: The first parameter is a parameter used for flexible time units; The second parameter is a parameter used for configuring other channels, which are channels other than the data channel; The third parameter is a parameter used for the data channel; First indication information, the first indication information is used to indicate a first time domain allocation item, the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list includes at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity; The configuration cycle for monitoring timing; Configuration period for Physical Downlink Control Channel (PDCCH) listening time; At least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

26. The method of claim 25, wherein, The first parameter, the second parameter, the third parameter, and at least one of the time-domain allocation list are configured per per cell group, or per cell, or per bandwidth portion of the BWP.

27. The method according to claim 25, wherein, When the first information includes the configuration period of the listening timing and the configuration period of the listening timing is X time units, the resource allocation granularity is Y1 sub-time units, the resource allocation range is Y2 time units, and the resource indication granularity is Y3 time units, wherein X, Y1, Y2, and Y3 are all integers not less than 1, at least one of Y1, Y2, and Y3 is equal to X, and one time unit includes multiple sub-time units.

28. The method according to any one of claims 24-27, wherein, The indicative or configurable value of the time-domain resource allocation parameter is related to at least one of the following: The subcarrier spacing (SCS) of the data channel; The format of the second instruction message; The second instruction information includes the Wireless Network Temporary Identifier (RNTI). The data channel scheduling method is one of unicast, multicast, and broadcast. The second indication information is used to schedule the data channel.

29. The method according to any one of claims 24-28, wherein, When the time-domain resource allocation parameters are configured per BWP and the data channel is scheduled during BWP handover, the time-domain resource allocation parameters correspond to at least one of the first BWP and the second BWP. Wherein, the first BWP is the BWP used before the BWP switchover occurs, and the second BWP is the BWP used after the BWP switchover occurs.

30. The method according to any one of claims 24-29, wherein, The first information is also used to indicate or configure the SLIV value, wherein there is a first correlation between the resource allocation granularity, the resource allocation range, the SLIV value, and the first temporal location information, and the first correlation is represented by any of the following: Where (L1-1)≤7*R / G; Among them, (L1-1)>7*R / G; Wherein, R represents the resource allocation range, G represents the resource allocation granularity, S1 represents the first starting sub-time unit in the first time-domain location information, L1 represents the number of first starting sub-time units in the first time-domain location information, and 0 <L1≤14-S1。 31. The method according to any one of claims 24-30, wherein, The first information is transmitted via at least one of the following: Downlink Control Information (DCI); Media Resource Control Unit (MAC CE); Radio Resource Control (RRC) signaling.

32. A resource scheduling device, comprising: The receiving module is used to receive the first information from the network-side device; The processing module is used to determine the time-domain location of the scheduled data channel based on the first information; The first information is used to indicate or configure time-domain resource allocation parameters, which include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

33. The apparatus according to claim 32, wherein, The first information is also used to indicate the start and length indication value (SLIV). Determining the time-domain location of the scheduled data channel based on the first information includes: The first time-domain location information is determined based on the time-domain resource allocation parameters, the SLIV value, and the first association relationship. The first time-domain location information includes the first starting sub-time unit and the number of first sub-time units. The starting sub-time unit of the data channel is determined based on the first starting sub-time unit, and the number of consecutive sub-time units occupied by the data channel is determined based on the number of the first sub-time units. The first association relationship is used to characterize the association relationship between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

34. The apparatus according to claim 32, wherein, The first information is also used to indicate or configure the SLIV value, and the step of determining the time-domain location of the scheduled data channel based on the first information includes: Determine the time unit group to which the data channel belongs, and determine the starting sub-time unit of the time unit group as the reference sub-time unit; The time-domain location information of the data channel is determined based on the reference sub-time unit, the time-domain resource allocation parameters, the SLIV value, and the first correlation relationship. The time-domain location information includes the starting sub-time unit of the data channel and the number of consecutive sub-time units occupied by the data channel. The first association relationship is used to characterize the association relationship between the time-domain resource allocation parameters, the SLIV value, and the first time-domain location information.

35. A resource scheduling device, comprising: The sending module is used to send the first message; The first information is used to indicate or configure the time-domain resource allocation parameters of the scheduled data channel, and the time-domain resource allocation parameters include at least one of resource allocation granularity, resource allocation range, and resource indication granularity.

36. The apparatus according to claim 35, wherein, The first information includes at least one of the following: The first parameter is a parameter used for flexible time units; The second parameter is a parameter used for configuring other channels, which are channels other than the data channel; The third parameter is a parameter used for the data channel; First indication information, the first indication information is used to indicate a first time domain allocation item, the first time domain allocation item includes at least one item in a pre-configured time domain allocation list, each time domain allocation item in the time domain allocation list includes at least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity; The configuration cycle for monitoring timing; Configuration period for Physical Downlink Control Channel (PDCCH) listening time; At least one of the resource allocation granularity, the resource allocation range, and the resource indication granularity.

37. The apparatus according to claim 36, wherein, The first parameter, the second parameter, the third parameter, and at least one of the time-domain allocation list are configured per per cell group, or per cell, or per bandwidth portion of the BWP.

38. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as claimed in any one of claims 1 to 23.

39. A network-side device comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as claimed in any one of claims 24 to 31.

40. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 23, or implement the steps of the method as claimed in any one of claims 24 to 31.

Images