Scheduling method and apparatus, device, readable storage medium, and computer program product

Abstract

The present application relates to the technical field of communications, and specifically to a scheduling method and apparatus, a device, a readable storage medium, and a computer program product. The method comprises: a terminal sends first auxiliary information to a network side device, and / or, the terminal receives first indication information from the network side device; and the terminal receives scheduling of the network side device on the basis of the first auxiliary information or the first indication information, wherein the first auxiliary information comprises related information of a scheduling constraint expected by the terminal, and / or, the first auxiliary information comprises related information of a power saving operation that the terminal expects to be triggered; and the first indication information comprises related information of a scheduling constraint of the scheduling executed by the network side device, and / or, the first indication information comprises related information used for indicating a power saving operation that can be triggered by the terminal.

Description

Scheduling methods, apparatus, equipment, readable storage media, and computer program products

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410976012.1, filed in China on July 19, 2024, 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 scheduling method, apparatus, device, readable storage medium, and computer program product. Background Technology

[0004] Currently, the implementation of network-side device scheduling algorithms does not consider the energy efficiency of terminals, resulting in scheduling methods that are not the most energy-efficient for terminals. For example, the scheduling result of a terminal may be that the scheduling is distributed across multiple time slots over a period of time, and the number of frequency domain resources scheduled in each time slot is relatively small. This reduces the time and depth at which the terminal can enter sleep mode, which is not conducive to terminal energy saving. Summary of the Invention

[0005] This application provides a scheduling method, apparatus, device, readable storage medium, and computer program product, which can solve the problem that current network-side device scheduling algorithms do not consider the energy efficiency of the terminal, thus hindering terminal energy saving.

[0006] Firstly, a scheduling method is provided, including:

[0007] The terminal sends first auxiliary information to the network-side device, and / or the terminal receives first indication information from the network-side device;

[0008] The terminal receives the scheduling from the network-side device according to the first auxiliary information or the first indication information;

[0009] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0010] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

[0011] Secondly, a scheduling method is provided, including:

[0012] The network-side device receives first auxiliary information from the terminal, and / or the network-side device sends first indication information to the terminal;

[0013] The network-side device performs scheduling based on the first auxiliary information or the first indication information;

[0014] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0015] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

[0016] Thirdly, a scheduling device is provided, comprising:

[0017] The first transceiver module is used for the terminal to send first auxiliary information to the network-side device, and / or for the terminal to receive first indication information from the network-side device;

[0018] The first processing module is used for the terminal to receive the scheduling from the network-side device according to the first auxiliary information or the first indication information;

[0019] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0020] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

[0021] Fourthly, a scheduling device is provided, comprising:

[0022] The second transceiver module is used for the network-side device to receive first auxiliary information from the terminal, and / or for the network-side device to send first indication information to the terminal;

[0023] The third processing module is used by the network-side device to perform scheduling based on the first auxiliary information or the first indication information;

[0024] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0025] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

[0026] Fifthly, a 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.

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

[0028] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used for the terminal to send first auxiliary information to a network-side device, and / or for the terminal to receive first indication information from the network-side device;

[0029] The processor is used by the terminal to receive scheduling from the network-side device according to the first auxiliary information or the first indication information;

[0030] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0031] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

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

[0033] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used for the network-side device to receive first auxiliary information from a terminal, and / or for the network-side device to send first indication information to the terminal;

[0034] The processor is used by the network-side device to perform scheduling based on the first auxiliary information or the first indication information;

[0035] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0036] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

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

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

[0039] 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 programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

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

[0041] In this embodiment, the terminal sends information about the scheduling restrictions it desires and / or information about triggering energy-saving operations to the network-side device via first auxiliary information; and / or, the network-side device sends information about scheduling restrictions it performs and / or information indicating that the terminal can trigger energy-saving operations to the terminal via first indication information. By exchanging information related to high-efficiency scheduling between the terminal and the network-side device, scheduling actions detrimental to the terminal's energy efficiency are avoided. This solves the problem of poor terminal energy efficiency caused by long scheduling times and limited resources in each time period, thus achieving a gain in saving terminal energy consumption. Attached Figure Description

[0042] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0043] Figure 2 is a flowchart of one of the scheduling methods provided in the embodiments of this application;

[0044] Figure 3 is a second schematic flowchart of the scheduling method provided in the embodiments of this application;

[0045] Figure 4 is a second schematic diagram of an application scenario provided in the embodiments of this application;

[0046] Figure 5 is a second schematic diagram of an application scenario provided in the embodiments of this application;

[0047] Figure 6 is a second schematic diagram of an application scenario provided in the embodiments of this application;

[0048] Figure 7 is one of the structural schematic diagrams of the scheduling device provided in the embodiments of this application;

[0049] Figure 8 is a second schematic diagram of the scheduling device provided in an embodiment of this application;

[0050] Figure 9 is a schematic diagram of the structure of the communication device provided in an embodiment of this application;

[0051] Figure 10 is a schematic diagram of the structure of the terminal provided in an embodiment of this application;

[0052] Figure 11 is a schematic diagram of the network-side device provided in an embodiment of this application;

[0053] Figure 12 is a second schematic diagram of the network-side device provided in the embodiments of this application. Detailed Implementation

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

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

[0056] 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 one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

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

[0058] 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 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 headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" 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), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0059] 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. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

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

[0061] To better understand the technical solution of this application, the following will be introduced first:

[0062] Base station scheduling algorithm

[0063] Base station scheduling algorithms are implementation algorithms used in wireless communication networks to manage resource allocation and scheduling among base stations. For mobile communication systems, base station scheduling algorithms are crucial for network optimization and improving user experience. Below are some common base station scheduling algorithms:

[0064] Power control scheduling algorithm: This algorithm dynamically adjusts the base station's transmit power based on the distance between the base station and the user, as well as channel quality, to maximize network coverage and capacity. Coverage and signal quality can be optimized by reducing base station power to decrease interference or increasing power to enhance coverage.

[0065] Resource allocation and scheduling algorithm: Based on user demand, network load and channel status, dynamically allocate frequency, code rate and other wireless resources to achieve efficient use of network resources and meet user communication needs.

[0066] Link quality scheduling algorithm: This algorithm dynamically adjusts the connection and handover strategies between the base station and the user equipment based on the channel quality and mobility of the user equipment, so as to ensure communication quality and realize mobility management.

[0067] Load balancing scheduling algorithm: Based on the load conditions between base stations and the distribution of users, dynamically adjust the base stations connected to users in order to achieve network load balancing and avoid congestion.

[0068] Intelligent Algorithm: Based on technologies such as machine learning, artificial intelligence, and big data analysis, the intelligent scheduling algorithm can analyze and predict based on historical data and real-time environment, thereby optimizing the allocation and scheduling strategies of base station resources.

[0069] The selection and design of these base station scheduling algorithms need to be comprehensively considered based on the specific network architecture, service requirements, and technical conditions. Effective base station scheduling algorithms can optimize network performance, maximize resource utilization, and improve user experience.

[0070] Terminal sleep model

[0071] A terminal sleep model refers to a model in wireless communication networks where mobile terminal devices enter a sleep state when idle to save energy. Terminal sleep models are commonly used in mobile communication systems, such as LTE and 5G wireless communication networks, to optimize power consumption and extend battery life.

[0072] The basic idea of ​​the terminal sleep model is to turn off the wireless interface or switch to a low-power mode when the mobile terminal device does not have a data transmission or reception requirement, in order to reduce energy consumption. When there is a data transmission requirement, the terminal device will be woken up, the wireless interface will be reactivated for communication, and then it will enter sleep mode again.

[0073] Deep Sleep, Light Sleep, and Micro Sleep refer to different sleep modes used by terminal devices to control power consumption and extend battery life. The following are their basic mechanisms:

[0074] Deep Sleep: Deep Sleep is an extremely low-power sleep mode in which the terminal device is almost completely shut down, retaining only a few basic functions, such as a clock or timer. The terminal device cannot communicate or process data in Deep Sleep mode. It is primarily used when there is no need to communicate with the network or perform tasks for extended periods, in order to significantly reduce energy consumption.

[0075] Light Sleep: Light Sleep is a low-power sleep mode that falls between Deep Sleep and Active mode. In Light Sleep mode, some hardware or functional modules of the terminal device will enter a low-power state, but will still maintain network monitoring and a certain degree of responsiveness in order to quickly wake up and enter the Active state. This can save some power consumption and maintain a certain level of communication capability.

[0076] Micro Sleep: Micro Sleep refers to a terminal device entering a sleep state within a very short time to reduce power consumption. It typically occurs when the device is inactive and has not been used for an extended period. In Micro Sleep mode, the device can quickly wake up and return to an active state to respond to user actions or network demands.

[0077] The selection and switching of these sleep modes are typically managed by the terminal device's hardware and operating system. By making proper use of these sleep modes, terminal devices can effectively reduce power consumption, extend battery life, and improve user experience while ensuring communication capabilities.

[0078] Currently, the implementation of base station scheduling algorithms does not consider the energy efficiency of terminals. Therefore, it is highly likely that the scheduling result will not be the most energy-efficient for a terminal. For example, the scheduling result of a terminal may be as follows: the scheduling is distributed across multiple time slots over a period of time, and the number of frequency domain resources scheduled in each time slot is relatively small. This will reduce the time and depth at which the terminal can enter sleep mode, which is not conducive to terminal energy saving.

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

[0080] Referring to Figure 2, this application embodiment provides a scheduling method, the execution subject of which is a terminal, including:

[0081] Step 201: The terminal sends first auxiliary information to the network-side device, and / or the terminal receives first indication information from the network-side device;

[0082] Step 202: The terminal receives the scheduling from the network-side device according to the first auxiliary information or the first instruction information;

[0083] The first auxiliary information includes information related to the scheduling constraints desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations; the first auxiliary information can be summarized as auxiliary information related to high-efficiency scheduling.

[0084] The first indication information includes information related to scheduling restrictions performed by network-side devices, and / or, the first indication information includes information for instructing terminals to trigger energy-saving operations; the first indication information can be summarized as indication information related to high-efficiency scheduling.

[0085] The aforementioned high-efficiency scheduling includes scheduling-related restrictions aimed at improving energy efficiency or saving energy consumption, and / or, operations to improve energy efficiency or save energy consumption after receiving scheduling.

[0086] The aforementioned first auxiliary information can be carried by uplink channel signaling such as Radio Resource Control (RRC) messages, Media Access Control Control Element (MAC CE) messages, or Physical Uplink Control Channel (PUCCH) messages.

[0087] The aforementioned first indication information can be carried by downlink channel signaling such as RRC messages, MAC CE, or Physical Downlink Control Channel (PDCCH) messages.

[0088] It should be noted that step 201 of the above method includes three cases:

[0089] Scenario 1: The terminal sends the first auxiliary information to the network-side device;

[0090] Scenario 2: The terminal receives the first indication information from the network-side device;

[0091] Case 3: The terminal sends the first auxiliary information to the network-side device, and the terminal receives the first indication information from the network-side device;

[0092] Situation 1 above refers to the terminal providing the network-side device with information on the scheduling restrictions the terminal expects, and / or information on the terminal expecting to trigger energy-saving operations. The corresponding network-side device performs scheduling based on the first auxiliary information. Specifically, step 202 of the above method refers to the terminal receiving the scheduling from the network-side device based on the first auxiliary information.

[0093] Situation 2 above refers to the network-side device providing the terminal with relevant information on scheduling restrictions for network-side device to perform scheduling, and / or relevant information for instructing the terminal to trigger energy-saving operations. The corresponding network-side device performs scheduling according to the first instruction information. Specifically, step 202 of the above method refers to the terminal receiving the scheduling from the network-side device according to the first instruction information.

[0094] The above situation 3 refers to the terminal providing the network-side device with information related to the scheduling restrictions the terminal expects, and / or information related to the terminal expecting to trigger energy-saving operations, while the network-side device performs scheduling restrictions related to scheduling, and / or information related to instructing the terminal to trigger energy-saving operations. The corresponding network-side device performs scheduling according to the first instruction information. Specifically, step 202 of the above method refers to the terminal receiving the scheduling from the network-side device according to the first instruction information.

[0095] In this embodiment, the terminal sends information about the scheduling restrictions it desires and / or information about triggering energy-saving operations to the network-side device via first auxiliary information; and / or, the network-side device sends information about scheduling restrictions it performs and / or information indicating that the terminal can trigger energy-saving operations to the terminal via first indication information. By exchanging information related to high-efficiency scheduling between the terminal and the network-side device, scheduling actions detrimental to the terminal's energy efficiency are avoided. This solves the problem of poor terminal energy efficiency caused by long scheduling times and limited resources in each time period, thus achieving a gain in saving terminal energy consumption.

[0096] In one alternative implementation, the first auxiliary information includes at least one of the following:

[0097] (1) Second indication information, used to indicate the scheduling constraints desired by the terminal;

[0098] (2) First capability information, used to indicate that the terminal supports the first scheduling mode;

[0099] (3) First request information, used to request the network-side device to enter the first scheduling mode;

[0100] The first scheduling mode is a scheduling mode related to the scheduling constraints desired by the terminal; that is, the terminal can indicate to the network-side device that it supports the high-energy-efficiency scheduling mode through the first capability information; the terminal can also request the network-side device to enter the high-energy-efficiency scheduling mode through the first request information.

[0101] (4) First type of information, used to indicate that the terminal has a target scheduling requirement;

[0102] The target scheduling requirement refers to the scheduling requirement related to the scheduling constraints desired by the terminal. That is, the terminal can indicate to the network-side equipment that it has a high-energy-efficiency scheduling requirement through the first type of information.

[0103] In one optional implementation, the second indication information includes at least one of the following:

[0104] (a) The terminal expects the minimum time interval between two consecutive scheduling bursts, where a scheduling burst contains multiple scheduling instances;

[0105] In this application, the scheduling instance is defined as at least one of the Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), or Physical Uplink Shared Channel (PUSCH); the scheduling in this application can be replaced by downlink scheduling, uplink scheduling, or all uplink and downlink scheduling.

[0106] The scheduling burst is predefined as one or N consecutive scheduling instances, or as one or more scheduling instances that occur within a certain time threshold between any two consecutive scheduling instances.

[0107] (b) The maximum number of scheduling instances that the terminal expects to schedule within a preset time period;

[0108] (c) The maximum time length that the terminal expects to schedule within a preset time period;

[0109] The aforementioned preset time period can also be called a specific time period, which is a fixed time window of a specific length (the time period is connected end to end), or a sliding time window of a specific length, or the period or activation time period of UE discontinuous reception (DRX), Cell DTX / DRX.

[0110] (d) The minimum number of frequency domain units that the terminal expects to schedule in a time domain unit;

[0111] (e) The minimum Transport Block Size (TBS) that the terminal expects to schedule in a time domain unit;

[0112] (f) The minimum data rate that the terminal expects to schedule in a time-domain unit;

[0113] The aforementioned time-domain unit may include one or more symbols, time slots, radio subframes, and radio frames; the aforementioned frequency-domain unit may include one or more subcarriers, physical resource blocks (PRBs), precoding resource block groups (PRGs), resource block groups (RBGs), resource block sets (RB sets), and subbands.

[0114] (g) The minimum average number of frequency domain units that the terminal expects to schedule for each scheduling instance within a preset time period;

[0115] (h) The minimum average TBS that the terminal expects to schedule on each scheduled instance within a preset time period;

[0116] (i) The minimum average data rate that the terminal expects to be scheduled on each scheduled instance within a preset time period;

[0117] (j) The terminal expects that, within a time period or a scheduling burst, the number of scheduling frequency domain units that are less than or equal to the number threshold accounts for the maximum proportion of the total number of scheduling times.

[0118] For example, if the maximum proportion of scheduled frequency domain units less than or equal to 10 PRBs (10 is the threshold) is 20%, it means that at most 2 out of 10 scheduling operations will have frequency domain units less than or equal to 10 PRBs.

[0119] (k) The terminal expects the maximum proportion of the total number of scheduling times in a time period or a scheduling burst where the scheduling TBS is less than or equal to the TBS threshold.

[0120] (l) The terminal expects the maximum proportion of the total number of scheduling times in a time period or a scheduling burst where the data rate is less than or equal to the data rate threshold.

[0121] (m) The minimum total transmit power of uplink data that the terminal expects to schedule in one time domain unit;

[0122] (n) The minimum average transmit power on the uplink data units that the terminal expects to schedule within a preset time period;

[0123] (o) The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times in which the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold is out of the total number of scheduling times.

[0124] The above (a) to (o) provide an indication of the desired scheduling restrictions for the terminal.

[0125] In one alternative implementation, the first indication information includes at least one of the following:

[0126] (1) The third instruction information is used to instruct network-side devices to perform scheduling restrictions;

[0127] (2) The fourth instruction information is used to instruct the network-side device to enter the second scheduling mode;

[0128] The second scheduling mode is a scheduling mode related to scheduling restrictions performed by network-side devices.

[0129] In one alternative implementation, the third instruction information includes at least one of the following:

[0130] (a) The minimum time interval between two consecutive scheduling bursts of network-side device scheduling, where a scheduling burst contains multiple scheduling instances;

[0131] (b) The maximum number of scheduling instances scheduled by the network-side device within a preset time period;

[0132] (c) The maximum time length for network-side devices to schedule within a preset time period;

[0133] (d) The minimum number of frequency domain units that a network-side device can schedule in a time domain unit;

[0134] (e) The minimum value of TBS scheduled by network-side devices in a time-domain unit;

[0135] (f) The minimum data rate that the network-side device can schedule in a time-domain unit;

[0136] (g) The minimum average number of frequency domain units on each scheduling instance scheduled by the network-side device within a preset time period;

[0137] (h) The minimum average TBS of each scheduling instance scheduled by the network-side device within a preset time period;

[0138] (i) The minimum average data rate on each scheduled instance scheduled by the network-side device within a preset time period;

[0139] (j) The maximum proportion of the total number of scheduling times in which the number of frequency domain units scheduled by the network-side device is less than or equal to the number threshold within a time period or a scheduling burst.

[0140] (k) The maximum proportion of the total number of scheduling times in a time period or a scheduling burst by the network-side device when the scheduling TBS is less than or equal to the TBS threshold.

[0141] (l) The maximum proportion of the total number of times a network-side device schedules a data rate less than or equal to the data rate threshold within a time period or a scheduling burst;

[0142] (m) The minimum total transmit power of uplink data scheduled by network-side devices in one time domain unit;

[0143] (n) The minimum average transmit power of the uplink data units scheduled by the network-side equipment within a preset time period;

[0144] (o) The maximum proportion of the total number of times the network-side device schedules uplink data whose total transmit power is less than or equal to the total transmit power threshold within a time period or a scheduling burst.

[0145] The scheduling restrictions for network-side devices to perform scheduling are achieved through (a) to (o) above.

[0146] In one alternative implementation, the method further includes:

[0147] After receiving the first scheduling from the network-side device, the terminal performs at least one of the following actions during the first time period:

[0148] (1) Skip PDCCH monitoring, or skip PDCCH monitoring for scheduling downlink data, or skip PDCCH monitoring for scheduling uplink data;

[0149] (2) Entering a sleep state;

[0150] (3) Do not start the inactive state timer;

[0151] The first schedule is used to instruct the terminal to trigger energy-saving operations. That is, when the terminal receives the first schedule, it will perform the energy-saving operations (1) to (3) above within the first time period.

[0152] In one alternative implementation, the first indication information further includes at least one of the following:

[0153] (1) Instruction information of the first dispatcher;

[0154] (2) Instructions for the first time period.

[0155] In one alternative implementation, the first scheduling includes at least one of the following:

[0156] (1) Any scheduling instance or the last scheduling instance in a scheduling burst;

[0157] The first scheduler is any scheduling instance, or the first scheduler is the last scheduling instance of the scheduling burst;

[0158] (2) The number of scheduled instances that reaches the maximum value within a preset time period;

[0159] The first scheduling is when the maximum number of scheduling instances is reached within a specific time period;

[0160] (3) Scheduling instances that reach the maximum time length within a preset time period;

[0161] The first scheduling instance is the scheduling instance that reaches the maximum scheduling time within a specific time period;

[0162] (4) Scheduling instances where the number of frequency domain units scheduled is less than or equal to the frequency domain unit number threshold.

[0163] The first scheduling instance is a scheduling instance where the number of frequency domain units scheduled is less than or equal to a certain value;

[0164] (5) Scheduling instances where the scheduled TBS is less than or equal to the TBS threshold;

[0165] The first scheduling instance is a scheduling instance whose TBS is less than or equal to a certain value.

[0166] (6) Scheduling instances where the data rate is less than or equal to the data rate threshold;

[0167] The first scheduling instance is a scheduling instance whose data rate is less than or equal to a certain value.

[0168] (7) Scheduling instances where the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold.

[0169] The first scheduling instance is a scheduling instance where the total transmit power of the uplink data is less than or equal to a certain value.

[0170] In one alternative implementation, the first time period satisfies at least one of the following:

[0171] (1) Starting from the first scheduling or a specific time after the first scheduling, the time length is the minimum time interval between two consecutive scheduling bursts determined according to the first auxiliary information or the first instruction information;

[0172] The first time period is the starting point of the first scheduling or a specific time after the first scheduling. The length of the first time period is the minimum time interval between two consecutive scheduling bursts included in the first auxiliary information or first indication information above.

[0173] (2) The time period is a preset time period, starting from the first scheduling or a specific time after the first scheduling;

[0174] The first time period is the time period that starts at the first scheduling or a specific time after the first scheduling and ends at the end time of the preset time period included in the first auxiliary information or the first indication information above.

[0175] (3) The time is determined by the terminal, indicated by the network side device, or predefined by the protocol, starting from the first scheduling or a specific time after the first scheduling.

[0176] The first time period is defined as starting from the first scheduling or a specific time after the first scheduling, and the duration is determined by the base station indication, terminal reporting, or a value predefined by the protocol.

[0177] Referring to Figure 3, this application embodiment provides a scheduling method, the execution subject of which is a network-side device, such as a base station, including:

[0178] Step 301: The network-side device receives first auxiliary information from the terminal, and / or the network-side device sends first instruction information to the terminal;

[0179] Step 302: The network-side device performs scheduling based on the first auxiliary information or the first instruction information;

[0180] It should be noted that, as the peer device that interacts with the terminal, the network-side device should be understood in the same way as the interactive actions and information involved in the technical solutions of this application, so as to ensure that the terminal side and the network side can work correctly. Therefore, the technical solutions described in the network-side method can be referred to the descriptions in the terminal-side method, and will not be repeated here.

[0181] The first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations.

[0182] The first indication information includes information related to scheduling restrictions performed by network-side devices, and / or, the first indication information includes information for instructing terminals to trigger energy-saving operations.

[0183] In one alternative implementation, the first auxiliary information includes at least one of the following:

[0184] The second indication information is used to indicate the scheduling constraints desired by the terminal;

[0185] First capability information is used to indicate that the terminal supports the first scheduling mode;

[0186] The first request information is used to request the network-side device to enter the first scheduling mode;

[0187] The first type of information is used to indicate that the terminal has a target scheduling requirement;

[0188] The first scheduling mode is a scheduling mode related to the scheduling constraints desired by the terminal;

[0189] The target scheduling requirement is the scheduling requirement related to the scheduling constraints expected by the terminal.

[0190] In one optional implementation, the second indication information includes at least one of the following:

[0191] The terminal expects the minimum time interval between two consecutive scheduling bursts, and a scheduling burst contains multiple scheduling instances.

[0192] The maximum number of scheduling instances that the terminal expects to schedule within a preset time period;

[0193] The maximum time duration that the terminal expects to schedule within a preset time period;

[0194] The minimum number of frequency domain units that the terminal expects to schedule in a time domain unit;

[0195] The terminal expects to schedule the minimum value of TBS within a time domain unit;

[0196] The minimum data rate that the terminal expects to schedule within a time-domain unit;

[0197] The terminal expects to achieve the minimum average number of frequency domain units on each scheduling instance within a preset time period;

[0198] The terminal expects to achieve the minimum average TBS on each scheduled instance within a preset time period;

[0199] The terminal expects the minimum average data rate on each scheduled instance within a preset time period;

[0200] The terminal expects that, within a time period or a scheduling burst, the number of scheduling frequency domain units that are less than or equal to a certain threshold accounts for the maximum proportion of the total number of scheduling times.

[0201] The terminal expects the maximum proportion of the total number of scheduling events in a time period or a scheduling burst where the scheduling TBS is less than or equal to the TBS threshold.

[0202] The terminal expects the maximum proportion of the total number of scheduling operations in a time period or a scheduling burst where the data rate is less than or equal to the data rate threshold.

[0203] The terminal expects to schedule the minimum total transmit power of uplink data within a time domain unit;

[0204] The terminal expects the minimum average transmit power on the uplink data units scheduled within a preset time period;

[0205] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times in which the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold is reached.

[0206] In one alternative implementation, the first indication information includes at least one of the following:

[0207] The third instruction information is used to instruct network-side devices on scheduling restrictions;

[0208] The fourth instruction information is used to instruct network-side devices to enter the second scheduling mode;

[0209] The second scheduling mode is a scheduling mode related to the scheduling restrictions performed by network-side devices.

[0210] In one alternative implementation, the third instruction information includes at least one of the following:

[0211] The minimum time interval between two consecutive scheduling bursts in network-side device scheduling; a scheduling burst contains multiple scheduling instances.

[0212] The maximum number of scheduling instances that a network-side device can schedule within a preset time period;

[0213] The maximum duration for network-side devices to schedule within a preset time period;

[0214] The minimum number of frequency domain units that a network-side device can schedule in a time domain unit;

[0215] The minimum value of TBS scheduled by network-side devices in a time-domain unit;

[0216] The minimum data rate that a network-side device can schedule within a time-domain unit;

[0217] The minimum average number of frequency domain units on each scheduling instance scheduled by the network-side device within a preset time period;

[0218] The minimum average TBS of each scheduling instance scheduled by the network-side device within a preset time period;

[0219] The minimum average data rate on each scheduled instance within a preset time period by the network-side device;

[0220] The maximum proportion of the total number of scheduling times in which the number of frequency domain units scheduled by the network-side device is less than or equal to the number threshold within a time period or a scheduling burst.

[0221] The maximum proportion of the total number of scheduling operations where the TBS is less than or equal to the TBS threshold within a time period or a scheduling burst by the network-side equipment.

[0222] The maximum proportion of the total number of scheduling operations where the data rate is less than or equal to the data rate threshold within a time period or a scheduling burst by the network-side device.

[0223] The minimum total transmit power of uplink data scheduled by network-side devices in a time-domain unit;

[0224] The minimum average transmit power of the uplink data units scheduled by the network-side equipment within a preset time period;

[0225] The maximum proportion of the total number of times a network-side device schedules uplink data with a total transmit power less than or equal to the total transmit power threshold within a given time period or scheduling burst.

[0226] In one alternative implementation, the method further includes:

[0227] The network-side device sends the first schedule to the terminal;

[0228] The first schedule is used to instruct the terminal to trigger energy-saving operations in the first time period.

[0229] In one alternative implementation, the first indication information further includes at least one of the following:

[0230] The first dispatcher's instruction information;

[0231] Instructions for the first time period.

[0232] In one alternative implementation, the first scheduling includes at least one of the following:

[0233] Any scheduling instance or the last scheduling instance in a scheduling burst;

[0234] The number of scheduled instances reaches the maximum value within a preset time period;

[0235] Scheduling instances that reach their maximum duration within a preset time period;

[0236] Scheduling instances where the number of frequency domain units scheduled is less than or equal to a frequency domain unit number threshold;

[0237] Scheduling instances where the TBS is less than or equal to the TBS threshold;

[0238] Scheduling instances where the data rate is less than or equal to the data rate threshold;

[0239] A scheduling instance where the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold.

[0240] In one alternative implementation, the first time period satisfies at least one of the following:

[0241] Starting from the first scheduling or a specific time after the first scheduling, the time length is the minimum time interval between two consecutive scheduling bursts determined according to the first auxiliary information or the first instruction information;

[0242] Starting from the first scheduling or a specific time after the first scheduling, the time length is a preset time period;

[0243] The time period is determined by the terminal, indicated by the network-side device, or predefined by the protocol, starting from the first scheduling or a specific time after the first scheduling.

[0244] The technical solution of this application will be described below with reference to specific application embodiments:

[0245] Example 1:

[0246] The main idea of ​​this embodiment is that the terminal reports the expected scheduling constraints and other auxiliary information, thereby solving the problem of poor terminal energy efficiency caused by long base station scheduling time and limited scheduling resources in each time period, and achieving the gain of improved transmission energy efficiency.

[0247] The corresponding signaling flow is shown in Figure 4.

[0248] In some sub-implementations, the first auxiliary information sent by the terminal is the expected minimum time interval between two consecutive scheduling bursts. For example, if the scheduling burst is a scheduling instance, after the terminal receives a scheduling instance, the next nearest scheduling instance will be after the minimum time interval.

[0249] Optionally, the base station may send confirmation information according to the first auxiliary information sent by the terminal.

[0250] Optionally, the base station schedules according to the restrictions of the first auxiliary information. That is, after the base station schedules a terminal for a scheduling instance, it will not schedule data for the terminal again within the minimum time interval after the scheduling instance. This indirectly restricts the base station from scheduling too few resources in a scheduling instance and requires it to send the data in the buffer as soon as possible. Otherwise, the base station will not have any available scheduling opportunities for a period of time, which will result in the inability to meet the service QoS.

[0251] In some sub-implementations, the first auxiliary information sent by the terminal is the maximum number of scheduling instances or the maximum scheduling length expected to be scheduled within a specific time period. The specific time period is a fixed time window of a specific length (with the beginning and end of the time period connected), or a sliding time window of a specific length, or the period or activation time period of UE DRX, Cell DTX / DRX.

[0252] Optionally, the base station may send confirmation information according to the first auxiliary information sent by the terminal.

[0253] Optionally, the base station performs scheduling according to the restrictions of the first auxiliary information. That is, after the base station schedules the maximum number or the maximum scheduling length of the terminal's scheduling instances within a specific time period, it will no longer schedule the terminal within that specific time period. This indirectly restricts the base station from scheduling too few resources in a scheduling instance. Otherwise, the base station will not have available scheduling opportunities for a period of time, resulting in the inability to meet the service (Quality of Service, QoS).

[0254] In some sub-implementations, the first auxiliary information sent by the terminal is the minimum number of frequency domain units, minimum TB size, or minimum data rate to be scheduled in a time domain unit (or the minimum average number of frequency domain units, minimum average TB size, or minimum average data rate on the scheduling unit within a specific time period).

[0255] Optionally, the base station may send confirmation information according to the first auxiliary information sent by the terminal.

[0256] Optionally, the base station schedules according to the restrictions of the first auxiliary information, that is, the number of frequency domain units, TB size, or data rate scheduled by the base station in each time domain unit (or the minimum average number of frequency domain units, minimum average TB size, or minimum average data rate in the scheduling unit within a specific time period) is greater than or equal to the minimum value, which directly restricts the base station from scheduling fewer resources in a scheduling instance or a scheduling instance over a period of time.

[0257] In some sub-implementations, the first auxiliary information sent by the terminal is the number of frequency domain units expected to be scheduled in a period of time or a set of scheduling instances, the maximum proportion of TB size or data rate that is less than or equal to a certain threshold value;

[0258] Optionally, the base station may send confirmation information according to the first auxiliary information sent by the terminal.

[0259] Optionally, the base station performs scheduling according to the restrictions of the first auxiliary information. That is, after the proportion of the number of frequency domain units, TB size, or data rate scheduled by the base station in a certain period of time or group of scheduling instances that is less than or equal to a certain threshold reaches the maximum proportion, the base station can no longer perform scheduling of the number of frequency domain units, TB size, or data rate that is less than or equal to a certain threshold. This provides the base station with a certain degree of flexibility to schedule fewer resources, while avoiding the base station from always scheduling fewer resources, thus achieving a trade-off between base station scheduling flexibility and terminal energy efficiency.

[0260] In some sub-implementations, the first auxiliary information sent by the terminal is the minimum total transmit power of uplink data to be scheduled in a time domain unit (or the minimum average transmit power of uplink data units to be scheduled within a specific time period);

[0261] Optionally, the base station may send confirmation information according to the first auxiliary information sent by the terminal.

[0262] Optionally, the base station schedules according to the restrictions of the first auxiliary information, that is, the minimum total transmit power of the uplink data scheduled by the base station in each time domain unit (or the minimum average transmit power of the uplink data unit scheduled in a specific time period) is greater than or equal to the minimum value. This directly restricts the base station from scheduling a small amount of uplink data resources in a scheduling instance or a scheduling instance over a period of time.

[0263] In some sub-implementations, the first auxiliary information sent by the terminal is the maximum proportion of the total uplink data transmission power scheduled over a period of time or a set of scheduling instances (or the minimum average transmission power scheduled on uplink data units within a specific time period) that is less than or equal to a certain threshold value.

[0264] Optionally, the base station may send confirmation information according to the first auxiliary information sent by the terminal.

[0265] Optionally, the base station performs scheduling according to the restrictions of the first auxiliary information. That is, after the proportion of the total uplink data transmission power (or the minimum average transmission power of the uplink data unit scheduled within a certain time period or a set of scheduling instances) less than or equal to a certain threshold reaches the maximum proportion, the base station can no longer perform scheduling when the total uplink data transmission power (or the minimum average transmission power of the uplink data unit scheduled within a certain time period) is less than or equal to a certain threshold. This provides the base station with a certain degree of flexibility to schedule fewer resources, while avoiding the base station from always scheduling fewer resources, thus achieving a trade-off between base station scheduling flexibility and terminal energy efficiency.

[0266] Example 2:

[0267] The main idea of ​​this embodiment is that the base station instructs the terminal to perform a high-energy-efficiency scheduling strategy, and the terminal performs energy-saving operations according to the strategy. This solves the problem of poor terminal energy efficiency caused by long base station scheduling time and limited scheduling resources in each time period, and achieves the gain of improved transmission energy efficiency.

[0268] The corresponding signaling flow is shown in Figure 5.

[0269] In some sub-implementations, the terminal receives the first indication information from the network as the minimum time interval between two consecutive scheduling bursts scheduled by the base station. For example, if the scheduling burst is a scheduling instance, after the terminal receives a scheduling instance, the next nearest scheduling instance will be after the minimum time interval.

[0270] The base station schedules according to the restrictions of the first indication information. That is, after the base station schedules a terminal for a scheduling instance, it will not schedule data for the terminal again within the minimum time interval after that scheduling instance. This indirectly restricts the base station from scheduling too few resources in a scheduling instance and requires it to send the data in the buffer as soon as possible. Otherwise, the base station will not have any available scheduling opportunities for a period of time, which will result in the inability to meet the service QoS.

[0271] Optionally, when a terminal receives a schedule, it may refrain from monitoring the schedule PDCCH for at least a minimum time interval, or enter a sleep state, or not start the inactivity timer.

[0272] In some sub-implementations, the terminal receives the first indication information from the network as the maximum number of scheduling instances or the maximum scheduling length scheduled by the base station within a specific time period. The specific time period is a fixed time window of a specific length (with the beginning and end of the time period connected), or a sliding time window of a specific length, or the period or activation time period of UE DRX, Cell DTX / DRX.

[0273] The base station schedules according to the restrictions of the first indication information. That is, after the base station schedules the maximum number or the maximum scheduling length of the terminal's scheduling instances within a specific time period, it will no longer schedule the terminal within that specific time period. This indirectly restricts the base station from scheduling too few resources in a scheduling instance. Otherwise, the base station will not have any available scheduling opportunities for a period of time, which will result in the inability to meet the service QoS.

[0274] Optionally, when the terminal reaches the maximum number of scheduling instances or the maximum scheduling length within a specific time period, the terminal will not monitor the scheduling PDCCH for the remaining specific time period, or will enter a sleep state, or will not start the inactivity timer.

[0275] In some sub-implementations, the terminal receives the first indication information from the network as the minimum number of frequency domain units, minimum TB size, or minimum data rate scheduled by the base station in a time domain unit (or the minimum average number of frequency domain units, minimum average TB size, or minimum average data rate on the scheduling unit within a specific time period).

[0276] The base station schedules according to the restrictions of the first indication information, that is, the number of frequency domain units, TB size, or data rate scheduled by the base station in each time domain unit (or the minimum average number of frequency domain units, minimum average TB size, or minimum average data rate in the scheduling unit within a specific time period) is greater than or equal to the minimum value. This directly restricts the base station from scheduling fewer resources in a scheduling instance or a scheduling instance over a period of time.

[0277] In some sub-implementations, the terminal receives the first indication information from the network, which is the number of frequency domain units scheduled by the base station in a period of time or a group of scheduling instances, the maximum proportion of TB size or data rate that is less than or equal to a certain threshold value.

[0278] The base station performs scheduling according to the restrictions of the first indication information. That is, once the proportion of frequency domain units, TB size, or data rate scheduled by the base station within a certain period of time or group of scheduling instances that is less than or equal to a certain threshold reaches the maximum proportion, the base station can no longer perform scheduling of frequency domain units, TB size, or data rate that is less than or equal to a certain threshold. This provides the base station with a certain degree of flexibility to schedule fewer resources, while avoiding the base station from scheduling fewer resources all the time, thus achieving a trade-off between base station scheduling flexibility and terminal energy efficiency.

[0279] In some sub-implementations, the terminal receives the first indication information from the network as the minimum total transmit power of uplink data scheduled by the base station in a time domain unit (or the minimum average transmit power scheduled on the uplink data unit within a specific time period);

[0280] The base station schedules data according to the restrictions of the first indication information, that is, the minimum total transmit power of the uplink data scheduled by the base station in each time domain unit (or the minimum average transmit power of the uplink data unit scheduled in a specific time period) is greater than or equal to the minimum value. This directly restricts the base station from scheduling a small amount of uplink data resources in a scheduling instance or a scheduling instance over a period of time.

[0281] In some sub-implementations, the terminal receives the first indication information from the network as the maximum proportion of the total uplink data transmission power (or the minimum average transmission power on the uplink data unit scheduled by the base station in a period of time or a set of scheduling instances) that is less than or equal to a certain threshold value.

[0282] The base station performs scheduling according to the restrictions of the first indication information. That is, after the proportion of the total uplink data transmission power (or the minimum average transmission power of the uplink data unit scheduled within a certain period of time or a set of scheduling instances) less than or equal to a certain threshold reaches the maximum proportion, the base station can no longer perform scheduling when the total uplink data transmission power (or the minimum average transmission power of the uplink data unit scheduled within a certain period of time) is less than or equal to a certain threshold. This provides the base station with a certain degree of flexibility to schedule fewer resources, while avoiding the base station from scheduling fewer resources all the time, thus achieving a trade-off between base station scheduling flexibility and terminal energy efficiency.

[0283] Before receiving instructions from the base station, the terminal still reports the first auxiliary information, including the terminal's ability to support high-energy-efficiency scheduling mode, or the terminal's request to enter high-energy-efficiency scheduling mode, or the terminal's type information that has high-energy-efficiency scheduling requirements, or various scheduling restrictions corresponding to the expected requirements.

[0284] Example 3:

[0285] The main idea of ​​this embodiment is that the base station indicates special first scheduling-related information, which enables the terminal to enter energy-saving operation after receiving these schedulings, avoiding the base station from performing scheduling that is detrimental to the terminal's energy efficiency. This solves the problem of poor terminal energy efficiency caused by long base station scheduling time and limited scheduling resources in each time period, and achieves the benefit of saving terminal energy consumption.

[0286] The corresponding signaling flow is shown in Figure 6.

[0287] In some sub-implementations, the first indication information received by the terminal from the network, namely the first scheduling, includes at least one of the following:

[0288] The number of frequency domain units scheduled is less than or equal to a certain value for the scheduling instance;

[0289] The scheduling instance whose TBS is less than or equal to a certain value;

[0290] Scheduling instance where the data rate is less than or equal to a certain value;

[0291] The total transmit power of the scheduled uplink data is less than or equal to a certain value in the scheduling instance.

[0292] When the terminal receives the first schedule, it will not monitor the scheduled PDCCH within the specified time period indicated, or during the running time of the started Timer, or enter a sleep state, or not start the inactivity timer.

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

[0294] This application provides a scheduling device. As an example, the 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.

[0295] The scheduling device may include 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 may include a general-purpose processor, a special-purpose processor, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), an Artificial Intelligence (AI) processor, a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), a Network Processor (NP), a Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules may be implemented by a communication interface, which may include one or more of the following: a transceiver, pins, circuits, a bus, and a radio frequency unit.

[0296] Specifically, referring to Figure 7, when the scheduling device is a terminal or a component within a terminal, the scheduling device 700 includes:

[0297] The first transceiver module 701 is used for the terminal to send first auxiliary information to the network-side device, and / or for the terminal to receive first indication information from the network-side device;

[0298] The first processing module 702 is used for the terminal to receive the scheduling from the network-side device according to the first auxiliary information or the first indication information;

[0299] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0300] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

[0301] In one optional implementation, the first auxiliary information includes at least one of the following:

[0302] The second indication information is used to indicate the scheduling constraints desired by the terminal;

[0303] First capability information is used to indicate that the terminal supports a first scheduling mode;

[0304] The first request information is used to request the network-side device to enter the first scheduling mode;

[0305] The first type of information is used to indicate that the terminal has a target scheduling requirement;

[0306] Wherein, the first scheduling mode is a scheduling mode related to the scheduling constraints desired by the terminal;

[0307] The target scheduling requirement is a scheduling requirement related to the scheduling constraints desired by the terminal.

[0308] In one optional implementation, the second indication information includes at least one of the following:

[0309] The terminal expects the minimum time interval between two consecutive scheduling bursts, and one scheduling burst contains multiple scheduling instances.

[0310] The terminal expects to schedule the maximum number of scheduling instances within a preset time period;

[0311] The terminal expects to schedule the maximum duration within a preset time period;

[0312] The terminal expects to schedule the minimum number of frequency domain units in a time domain unit;

[0313] The terminal expects to schedule the minimum value of TBS within a time domain unit;

[0314] The terminal expects to schedule the minimum data rate within a time-domain unit;

[0315] The terminal expects to achieve the minimum average number of frequency domain units on each scheduling instance within a preset time period.

[0316] The terminal expects to achieve the minimum average TBS on each scheduled instance within a preset time period.

[0317] The terminal expects to achieve the minimum average data rate on each scheduled instance within a preset time period;

[0318] The terminal expects that, within a time period or a scheduling burst, the number of scheduling frequency domain units that are less than or equal to a certain threshold accounts for the maximum proportion of the total number of scheduling times.

[0319] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times in which the scheduled TBS is less than or equal to the TBS threshold is out of the total number of scheduling times.

[0320] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times where the data rate is less than or equal to the data rate threshold is out of the total number of scheduling times.

[0321] The terminal expects to schedule the minimum total transmit power of uplink data within a time-domain unit;

[0322] The terminal expects to achieve the minimum average transmit power on the uplink data units scheduled within a preset time period;

[0323] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times in which the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold is reached.

[0324] In one optional implementation, the first indication information includes at least one of the following:

[0325] The third indication information is used to indicate the scheduling restrictions that the network-side device performs;

[0326] The fourth instruction information is used to instruct the network-side device to enter the second scheduling mode;

[0327] The second scheduling mode is a scheduling mode related to the scheduling restrictions performed by the network-side device.

[0328] In one optional implementation, the third indication information includes at least one of the following:

[0329] The network-side device schedules the minimum time interval between two consecutive scheduling bursts, and one scheduling burst contains multiple scheduling instances.

[0330] The maximum number of scheduling instances that the network-side device can schedule within a preset time period;

[0331] The maximum scheduling time length of the network-side device within a preset time period;

[0332] The minimum number of frequency domain units that the network-side device can schedule in a time domain unit;

[0333] The minimum value of TBS scheduled by the network-side device in one time-domain unit;

[0334] The minimum data rate that the network-side device schedules in a time-domain unit;

[0335] The minimum average number of frequency domain units on each scheduling instance scheduled by the network-side device within a preset time period;

[0336] The minimum average TBS of each scheduling instance scheduled by the network-side device within a preset time period;

[0337] The minimum average data rate on each scheduling instance scheduled by the network-side device within a preset time period;

[0338] The maximum proportion of the total number of scheduling times in which the number of frequency domain units scheduled by the network-side device is less than or equal to a certain threshold within a time period or a scheduling burst.

[0339] The maximum proportion of the total number of scheduling times in a time period or a scheduling burst where the network-side device has a scheduling TBS less than or equal to the TBS threshold.

[0340] The maximum proportion of the total number of scheduling operations in a time period or a scheduling burst by the network-side device where the data rate is less than or equal to the data rate threshold.

[0341] The minimum total transmit power of uplink data scheduled by the network-side device in one time domain unit;

[0342] The minimum average transmit power of the uplink data units scheduled by the network-side device within a preset time period;

[0343] The network-side device, within a time period or a scheduling burst, represents the maximum proportion of scheduling times where the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold, relative to the total number of scheduling times.

[0344] In one alternative embodiment, the device further includes:

[0345] The second processing module is configured to, after the terminal receives the first scheduling from the network-side device, perform at least one of the following during a first time period:

[0346] Skip PDCCH monitoring, or skip PDCCH monitoring for scheduling downlink data, or skip PDCCH monitoring for scheduling uplink data;

[0347] Entering a sleep state;

[0348] Do not start inactive timers;

[0349] The first scheduling is a scheduling method used to instruct the terminal to trigger energy-saving operations.

[0350] In one optional implementation, the first indication information further includes at least one of the following:

[0351] The indication information of the first scheduler;

[0352] Indication information for the first time period.

[0353] In one alternative implementation, the first scheduling includes at least one of the following:

[0354] Any scheduling instance or the last scheduling instance in a scheduling burst;

[0355] The number of scheduled instances reaches the maximum value within a preset time period;

[0356] Scheduling instances that reach their maximum duration within a preset time period;

[0357] Scheduling instances where the number of frequency domain units scheduled is less than or equal to a frequency domain unit number threshold;

[0358] Scheduling instances where the TBS is less than or equal to the TBS threshold;

[0359] Scheduling instances where the data rate is less than or equal to the data rate threshold;

[0360] A scheduling instance where the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold.

[0361] In one alternative implementation, the first time period satisfies at least one of the following:

[0362] Starting from the first scheduling or a specific time after the first scheduling, the time length is the minimum time interval between two consecutive scheduling bursts determined according to the first auxiliary information or the first indication information.

[0363] The time period is a preset time segment, starting from the first scheduling or a specific time after the first scheduling.

[0364] The time duration is determined by the terminal, indicated by the network-side device, or predefined by the protocol, starting from the first scheduling or a specific time after the first scheduling.

[0365] Referring to Figure 8, when the scheduling device is a network-side device or a component within a network-side device, the scheduling device 800 includes:

[0366] The second transceiver module 801 is used for the network-side device to receive first auxiliary information from the terminal, and / or for the network-side device to send first indication information to the terminal;

[0367] The third processing module 802 is used by the network-side device to perform scheduling based on the first auxiliary information or the first indication information;

[0368] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0369] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

[0370] In one optional implementation, the first auxiliary information includes at least one of the following:

[0371] The second indication information is used to indicate the scheduling constraints desired by the terminal;

[0372] First capability information is used to indicate that the terminal supports a first scheduling mode;

[0373] The first request information is used to request the network-side device to enter the first scheduling mode;

[0374] The first type of information is used to indicate that the terminal has a target scheduling requirement;

[0375] Wherein, the first scheduling mode is a scheduling mode related to the scheduling constraints desired by the terminal;

[0376] The target scheduling requirement is a scheduling requirement related to the scheduling constraints desired by the terminal.

[0377] In one optional implementation, the second indication information includes at least one of the following:

[0378] The terminal expects the minimum time interval between two consecutive scheduling bursts, and one scheduling burst contains multiple scheduling instances.

[0379] The terminal expects to schedule the maximum number of scheduling instances within a preset time period;

[0380] The terminal expects to schedule the maximum duration within a preset time period;

[0381] The terminal expects to schedule the minimum number of frequency domain units in a time domain unit;

[0382] The terminal expects to schedule the minimum value of TBS within a time domain unit;

[0383] The terminal expects to schedule the minimum data rate within a time-domain unit;

[0384] The terminal expects to achieve the minimum average number of frequency domain units on each scheduling instance within a preset time period.

[0385] The terminal expects to achieve the minimum average TBS on each scheduled instance within a preset time period.

[0386] The terminal expects to achieve the minimum average data rate on each scheduled instance within a preset time period;

[0387] The terminal expects that, within a time period or a scheduling burst, the number of scheduling frequency domain units that are less than or equal to a certain threshold accounts for the maximum proportion of the total number of scheduling times.

[0388] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times in which the scheduled TBS is less than or equal to the TBS threshold is out of the total number of scheduling times.

[0389] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times where the data rate is less than or equal to the data rate threshold is out of the total number of scheduling times.

[0390] The terminal expects to schedule the minimum total transmit power of uplink data within a time-domain unit;

[0391] The terminal expects to achieve the minimum average transmit power on the uplink data units scheduled within a preset time period;

[0392] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times in which the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold is reached.

[0393] In one optional implementation, the first indication information includes at least one of the following:

[0394] The third indication information is used to indicate the scheduling restrictions that the network-side device performs;

[0395] The fourth instruction information is used to instruct the network-side device to enter the second scheduling mode;

[0396] The second scheduling mode is a scheduling mode related to the scheduling restrictions performed by the network-side device.

[0397] In one optional implementation, the third indication information includes at least one of the following:

[0398] The network-side device schedules the minimum time interval between two consecutive scheduling bursts, and one scheduling burst contains multiple scheduling instances.

[0399] The maximum number of scheduling instances that the network-side device can schedule within a preset time period;

[0400] The maximum scheduling time length of the network-side device within a preset time period;

[0401] The minimum number of frequency domain units that the network-side device can schedule in a time domain unit;

[0402] The minimum value of TBS scheduled by the network-side device in one time-domain unit;

[0403] The minimum data rate that the network-side device schedules in a time-domain unit;

[0404] The minimum average number of frequency domain units on each scheduling instance scheduled by the network-side device within a preset time period;

[0405] The minimum average TBS of each scheduling instance scheduled by the network-side device within a preset time period;

[0406] The minimum average data rate on each scheduling instance scheduled by the network-side device within a preset time period;

[0407] The maximum proportion of the total number of scheduling times in which the number of frequency domain units scheduled by the network-side device is less than or equal to a certain threshold within a time period or a scheduling burst.

[0408] The maximum proportion of the total number of scheduling times in a time period or a scheduling burst where the network-side device has a scheduling TBS less than or equal to the TBS threshold.

[0409] The maximum proportion of the total number of scheduling operations in a time period or a scheduling burst by the network-side device where the data rate is less than or equal to the data rate threshold.

[0410] The minimum total transmit power of uplink data scheduled by the network-side device in one time domain unit;

[0411] The minimum average transmit power of the uplink data units scheduled by the network-side device within a preset time period;

[0412] The network-side device, within a time period or a scheduling burst, represents the maximum proportion of scheduling times where the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold, relative to the total number of scheduling times.

[0413] In one alternative embodiment, the device further includes:

[0414] The fourth processing module is used for the network-side device to send the first schedule to the terminal;

[0415] The first scheduling is used to instruct the terminal to trigger energy-saving operation in a first time period.

[0416] In one optional implementation, the first indication information further includes at least one of the following:

[0417] The indication information of the first scheduler;

[0418] Indication information for the first time period.

[0419] In one alternative implementation, the first scheduling includes at least one of the following:

[0420] Any scheduling instance or the last scheduling instance in a scheduling burst;

[0421] The number of scheduled instances reaches the maximum value within a preset time period;

[0422] Scheduling instances that reach their maximum duration within a preset time period;

[0423] Scheduling instances where the number of frequency domain units scheduled is less than or equal to a frequency domain unit number threshold;

[0424] Scheduling instances where the TBS is less than or equal to the TBS threshold;

[0425] Scheduling instances where the data rate is less than or equal to the data rate threshold;

[0426] A scheduling instance where the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold.

[0427] In one alternative implementation, the first time period satisfies at least one of the following:

[0428] Starting from the first scheduling or a specific time after the first scheduling, the time length is the minimum time interval between two consecutive scheduling bursts determined according to the first auxiliary information or the first indication information.

[0429] The time period is a preset time segment, starting from the first scheduling or a specific time after the first scheduling.

[0430] The time duration is determined by the terminal, indicated by the network-side device, or predefined by the protocol, starting from the first scheduling or a specific time after the first scheduling.

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

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

[0433] 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 embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the scheduling device shown in FIG7. Specifically, FIG10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0434] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0435] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1010 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 10 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.

[0436] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 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 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 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.

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

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

[0439] The processor 1010 may include one or more processing units; optionally, the processor 1010 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 the processor 1010.

[0440] The radio frequency unit 1001 is used for the terminal to send first auxiliary information to the network-side device, and / or for the terminal to receive first indication information from the network-side device.

[0441] The processor 1010 is used for the terminal to receive scheduling from the network-side device according to the first auxiliary information or the first indication information;

[0442] Wherein, the first auxiliary information includes information related to the scheduling restrictions desired by the terminal, and / or, the first auxiliary information includes information related to the terminal's desire to trigger energy-saving operations;

[0443] The first indication information includes information related to scheduling restrictions performed by the network-side device, and / or the first indication information includes information for instructing the terminal to trigger energy-saving operations.

[0444] In one optional implementation, the first auxiliary information includes at least one of the following:

[0445] The second indication information is used to indicate the scheduling constraints desired by the terminal;

[0446] First capability information is used to indicate that the terminal supports a first scheduling mode;

[0447] The first request information is used to request the network-side device to enter the first scheduling mode;

[0448] The first type of information is used to indicate that the terminal has a target scheduling requirement;

[0449] Wherein, the first scheduling mode is a scheduling mode related to the scheduling constraints desired by the terminal;

[0450] The target scheduling requirement is a scheduling requirement related to the scheduling constraints desired by the terminal.

[0451] In one optional implementation, the second indication information includes at least one of the following:

[0452] The terminal expects the minimum time interval between two consecutive scheduling bursts, and one scheduling burst contains multiple scheduling instances.

[0453] The terminal expects to schedule the maximum number of scheduling instances within a preset time period;

[0454] The terminal expects to schedule the maximum duration within a preset time period;

[0455] The terminal expects to schedule the minimum number of frequency domain units in a time domain unit;

[0456] The terminal expects to schedule the minimum value of TBS within a time domain unit;

[0457] The terminal expects to schedule the minimum data rate within a time-domain unit;

[0458] The terminal expects to achieve the minimum average number of frequency domain units on each scheduling instance within a preset time period.

[0459] The terminal expects to achieve the minimum average TBS on each scheduled instance within a preset time period.

[0460] The terminal expects to achieve the minimum average data rate on each scheduled instance within a preset time period;

[0461] The terminal expects that, within a time period or a scheduling burst, the number of scheduling frequency domain units that are less than or equal to a certain threshold accounts for the maximum proportion of the total number of scheduling times.

[0462] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times in which the scheduled TBS is less than or equal to the TBS threshold is out of the total number of scheduling times.

[0463] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times where the data rate is less than or equal to the data rate threshold is out of the total number of scheduling times.

[0464] The terminal expects to schedule the minimum total transmit power of uplink data within a time-domain unit;

[0465] The terminal expects to achieve the minimum average transmit power on the uplink data units scheduled within a preset time period;

[0466] The terminal expects that, within a time period or a scheduling burst, the maximum proportion of scheduling times in which the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold is reached.

[0467] In one optional implementation, the first indication information includes at least one of the following:

[0468] The third indication information is used to indicate the scheduling restrictions that the network-side device performs;

[0469] The fourth instruction information is used to instruct the network-side device to enter the second scheduling mode;

[0470] The second scheduling mode is a scheduling mode related to the scheduling restrictions performed by the network-side device.

[0471] In one optional implementation, the third indication information includes at least one of the following:

[0472] The network-side device schedules the minimum time interval between two consecutive scheduling bursts, and one scheduling burst contains multiple scheduling instances.

[0473] The maximum number of scheduling instances that the network-side device can schedule within a preset time period;

[0474] The maximum scheduling time length of the network-side device within a preset time period;

[0475] The minimum number of frequency domain units that the network-side device can schedule in a time domain unit;

[0476] The minimum value of TBS scheduled by the network-side device in one time-domain unit;

[0477] The minimum data rate that the network-side device schedules in a time-domain unit;

[0478] The minimum average number of frequency domain units on each scheduling instance scheduled by the network-side device within a preset time period;

[0479] The minimum average TBS of each scheduling instance scheduled by the network-side device within a preset time period;

[0480] The minimum average data rate on each scheduling instance scheduled by the network-side device within a preset time period;

[0481] The maximum proportion of the total number of scheduling times in which the number of frequency domain units scheduled by the network-side device is less than or equal to a certain threshold within a time period or a scheduling burst.

[0482] The maximum proportion of the total number of scheduling times in a time period or a scheduling burst where the network-side device has a scheduling TBS less than or equal to the TBS threshold.

[0483] The maximum proportion of the total number of scheduling operations in a time period or a scheduling burst by the network-side device where the data rate is less than or equal to the data rate threshold.

[0484] The minimum total transmit power of uplink data scheduled by the network-side device in one time domain unit;

[0485] The minimum average transmit power of the uplink data units scheduled by the network-side device within a preset time period;

[0486] The network-side device, within a time period or a scheduling burst, represents the maximum proportion of scheduling times where the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold, relative to the total number of scheduling times.

[0487] In one optional implementation, the processor 1010 is configured to, after the terminal receives the first scheduling from the network-side device, execute at least one of the following during a first time period:

[0488] Skip PDCCH monitoring, or skip PDCCH monitoring for scheduling downlink data, or skip PDCCH monitoring for scheduling uplink data;

[0489] Entering a sleep state;

[0490] Do not start inactive timers;

[0491] The first scheduling is a scheduling method used to instruct the terminal to trigger energy-saving operations.

[0492] In one optional implementation, the first indication information further includes at least one of the following:

[0493] The indication information of the first scheduler;

[0494] Indication information for the first time period.

[0495] In one alternative implementation, the first scheduling includes at least one of the following:

[0496] Any scheduling instance or the last scheduling instance in a scheduling burst;

[0497] The number of scheduled instances reaches the maximum value within a preset time period;

[0498] Scheduling instances that reach their maximum duration within a preset time period;

[0499] Scheduling instances where the number of frequency domain units scheduled is less than or equal to a frequency domain unit number threshold;

[0500] Scheduling instances where the TBS is less than or equal to the TBS threshold;

[0501] Scheduling instances where the data rate is less than or equal to the data rate threshold;

[0502] A scheduling instance where the total transmit power of the scheduled uplink data is less than or equal to the total transmit power threshold.

[0503] In one alternative implementation, the first time period satisfies at least one of the following:

[0504] Starting from the first scheduling or a specific time after the first scheduling, the time length is the minimum time interval between two consecutive scheduling bursts determined according to the first auxiliary information or the first indication information.

[0505] The time period is a preset time segment, starting from the first scheduling or a specific time after the first scheduling.

[0506] The time duration is determined by the terminal, indicated by the network-side device, or predefined by the protocol, starting from the first scheduling or a specific time after the first scheduling.

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

[0508] 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 FIG3. 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.

[0509] Specifically, this application embodiment also provides a network-side device, which may be the scheduling device shown in FIG9. As shown in FIG11, the network-side device 1100 includes: an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114, and a memory 115. The antenna 111 is connected to the radio frequency device 112. In the uplink direction, the radio frequency device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and sends it to the radio frequency device 112. The radio frequency device 112 processes the received information and transmits it through the antenna 111.

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

[0511] The baseband device 113 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG11. One of the chips is, for example, a baseband processor, which is connected to the memory 115 via a bus interface to call the program in the memory 115 and execute the network device operation shown in the above method embodiment.

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

[0513] Specifically, the network-side device 1100 in this application embodiment further includes: instructions or programs stored in memory 115 and executable on processor 114. Processor 114 calls the instructions or programs in memory 115 to execute the methods executed by each module shown in FIG9 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0514] Specifically, this application also provides a network-side device. As shown in FIG12, the network-side device 1200 includes a processor 1201, a network interface 1202, and a memory 1203. The network-side device may be the scheduling device shown in FIG9. The network interface 1202 is, for example, a Common Public Radio Interface (CPRI).

[0515] Specifically, the network-side device 1200 in this application embodiment further includes: instructions or programs stored in memory 1203 and executable on processor 1201. Processor 1201 calls the instructions or programs in memory 1203 to execute the methods executed by each module shown in FIG9 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

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

[0517] The processor mentioned above is the processor in the terminal described in the above embodiments. 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.

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

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

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

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

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

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

[0524] 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 scheduling method, comprising: a terminal sending first assistance information to a network side device, and / or the terminal receiving first indication information from the network side device; the terminal receiving scheduling of the network side device according to the first assistance information or the first indication information; wherein the first assistance information comprises information related to a scheduling limit expected by the terminal, and / or the first assistance information comprises information related to triggering energy saving operation expected by the terminal; the first indication information comprises information related to a scheduling limit of the network side device performing scheduling, and / or the first indication information comprises information for indicating that the terminal can trigger energy saving operation.

2. The method of claim 1, wherein, the first assistance information comprises at least one of the following: second indication information for indicating a scheduling limit expected by the terminal; first capability information for indicating that the terminal supports a first scheduling mode; first request information for requesting the network side device to enter the first scheduling mode; first type information for indicating that the terminal has a target scheduling demand; wherein the first scheduling mode is a scheduling mode related to the scheduling limit expected by the terminal; the target scheduling demand is a scheduling demand related to the scheduling limit expected by the terminal.

3. The method of claim 2, wherein, the second indication information comprises at least one of the following: the terminal expects a minimum time interval between two consecutive scheduling bursts, one of the scheduling bursts comprising a plurality of scheduling instances; the terminal expects a maximum value of a number of scheduling instances scheduled within a preset time period; the terminal expects a maximum time length of scheduling within a preset time period; the terminal expects a minimum value of a number of frequency domain units scheduled in one time domain unit; the terminal expects a minimum value of a transport block size (TBS) scheduled in one time domain unit; the terminal expects a minimum value of a data rate scheduled in one time domain unit; the terminal expects a minimum value of an average number of frequency domain units on each scheduling instance scheduled within a preset time period; the terminal expects a minimum value of an average TBS on each scheduling instance scheduled within a preset time period; the terminal expects a minimum value of an average data rate on each scheduling instance scheduled within a preset time period; the terminal expects a maximum proportion of a number of times of scheduling in which a number of frequency domain units scheduled in a time period or a scheduling burst is less than or equal to a number threshold, to a total number of times of scheduling in the time period or the scheduling burst; the terminal expects a maximum proportion of a number of times of scheduling in which a TBS scheduled in a time period or a scheduling burst is less than or equal to a TBS threshold, to a total number of times of scheduling in the time period or the scheduling burst; the terminal expects a maximum proportion of a number of times of scheduling in which a data rate scheduled in a time period or a scheduling burst is less than or equal to a data rate threshold, to a total number of times of scheduling in the time period or the scheduling burst; the terminal expects a minimum value of a total transmit power of uplink data scheduled in one time domain unit; the terminal expects a minimum value of an average transmit power on an uplink data unit scheduled within a preset time period; the terminal expects a maximum proportion of a number of times of scheduling in which a total transmit power of uplink data scheduled in a time period or a scheduling burst is less than or equal to a total transmit power threshold, to a total number of times of scheduling in the time period or the scheduling burst.

4. The method of claim 1, wherein, The first indication information comprises at least one of: Third indication information for indicating scheduling restriction of the network side device performing scheduling; Fourth indication information for indicating the network side device entering a second scheduling mode; The second scheduling mode is a scheduling mode related to the scheduling restriction of the network side device performing scheduling.

5. The method of claim 4, wherein, The third indication information comprises at least one of: The minimum time interval between two continuous scheduling bursts scheduled by the network side device, wherein one of the scheduling bursts comprises a plurality of scheduling instances; The maximum number of scheduling instances scheduled by the network side device within a preset time period; The maximum time length scheduled by the network side device within a preset time period; The minimum number of frequency domain units scheduled by the network side device in one time domain unit; The minimum TBS scheduled by the network side device in one time domain unit; The minimum data rate scheduled by the network side device in one time domain unit; The minimum average number of frequency domain units on each scheduling instance scheduled by the network side device within a preset time period; The minimum average TBS on each scheduling instance scheduled by the network side device within a preset time period; The minimum average data rate on each scheduling instance scheduled by the network side device within a preset time period; The maximum proportion of the scheduling times in which the number of frequency domain units scheduled by the network side device in a time period or a scheduling burst is less than or equal to a number threshold, to the total scheduling times; The maximum proportion of the scheduling times in which the TBS scheduled by the network side device in a time period or a scheduling burst is less than or equal to a TBS threshold, to the total scheduling times; The maximum proportion of the scheduling times in which the data rate scheduled by the network side device in a time period or a scheduling burst is less than or equal to a data rate threshold, to the total scheduling times; The minimum total transmit power of uplink data scheduled by the network side device in one time domain unit; The minimum average transmit power on uplink data units scheduled by the network side device within a preset time period; The maximum proportion of the scheduling times in which the total transmit power of uplink data scheduled by the network side device in a time period or a scheduling burst is less than or equal to a total transmit power threshold, to the total scheduling times.

6. The method of claim 1, further comprising: After the terminal receives the first scheduling of the network side device, performing at least one of the following in a first time period: Skipping physical downlink control channel (PDCCH) monitoring, or skipping PDCCH monitoring for scheduling downlink data, or skipping PDCCH monitoring for scheduling uplink data; Entering a sleep state; Not starting a non-active state timer; The first scheduling is a scheduling for indicating the terminal triggering energy saving operation.

7. The method of claim 6, wherein, The first indication information further comprises at least one of: Indication information of the first scheduling; Indication information of the first time period.

8. The method of claim 6, wherein, The first scheduling comprises at least one of: The last scheduling instance in any scheduling instance or scheduling burst; The scheduling instance in which the number of instances scheduled in a preset time period reaches a maximum value; a scheduling instance with a maximum time length is scheduled within a preset time period; a scheduling instance with a number of scheduled frequency domain units less than or equal to a threshold of the number of frequency domain units; a scheduling instance with a scheduled TBS less than or equal to a TBS threshold; a scheduling instance with a scheduled data rate less than or equal to a data rate threshold; a scheduling instance with a total transmit power of scheduled uplink data less than or equal to a total transmit power threshold.

9. The method of claim 6, wherein, The first time period satisfies at least one of the following conditions: a time length is a minimum time interval between two consecutive scheduling bursts determined according to the first auxiliary information or the first indication information, starting from the first scheduling or a specific time after the first scheduling; a time length is a preset time period, starting from the first scheduling or a specific time after the first scheduling; a time length is determined by the terminal, or indicated by the network side device, or predefined by a protocol, starting from the first scheduling or a specific time after the first scheduling.

10. A scheduling method, comprising: a network side device receiving first auxiliary information from a terminal, and / or the network side device sending first indication information to the terminal; the network side device performing scheduling according to the first auxiliary information or the first indication information; wherein the first auxiliary information comprises relevant information of scheduling restrictions expected by the terminal, and / or the first auxiliary information comprises relevant information of triggering energy saving operations expected by the terminal; the first indication information comprises relevant information of scheduling restrictions of the network side device performing scheduling, and / or the first indication information comprises relevant information for indicating that the terminal can trigger energy saving operations.

11. The method of claim 10, wherein, The first auxiliary information comprises at least one of the following: second indication information for indicating scheduling restrictions expected by the terminal; first capability information for indicating that the terminal supports a first scheduling mode; first request information for requesting the network side device to enter the first scheduling mode; first type information for indicating that the terminal has a target scheduling requirement; wherein the first scheduling mode is a scheduling mode related to the scheduling restrictions expected by the terminal; the target scheduling requirement is a scheduling requirement related to the scheduling restrictions expected by the terminal.

12. The method of claim 11, wherein, The second indication information comprises at least one of the following: the terminal expects a minimum time interval between two consecutive scheduling bursts, and each of the scheduling bursts contains multiple scheduling instances; the terminal expects a maximum value of the number of scheduling instances scheduled within a preset time period; the terminal expects a maximum time length scheduled within a preset time period; the terminal expects a minimum value of the number of frequency domain units scheduled in a time domain unit; the terminal expects a minimum value of TBS scheduled in a time domain unit; the terminal expects a minimum value of data rate scheduled in a time domain unit; the terminal expects a minimum value of average frequency domain units on each scheduling instance scheduled within a preset time period; the terminal expects a minimum value of average TBS on each scheduling instance scheduled within a preset time period; the terminal expects a minimum value of average data rate on each scheduling instance scheduled within a preset time period; The terminal expects that the maximum proportion of the scheduling times in which the number of scheduled frequency domain units is less than or equal to a number threshold in a time period or a scheduling burst to the total scheduling times is less than or equal to a proportion threshold; The terminal expects that the maximum proportion of the scheduling times in which the TBS of scheduled data is less than or equal to a TBS threshold in a time period or a scheduling burst to the total scheduling times is less than or equal to a proportion threshold; The terminal expects that the maximum proportion of the scheduling times in which the data rate of scheduled data is less than or equal to a data rate threshold in a time period or a scheduling burst to the total scheduling times is less than or equal to a proportion threshold; The terminal expects a minimum value of the total transmission power of uplink data scheduled in a time domain unit; The terminal expects a minimum value of the average transmission power on uplink data units scheduled in a preset time period; The terminal expects that the maximum proportion of the scheduling times in which the total transmission power of scheduled uplink data is less than or equal to a total transmission power threshold in a time period or a scheduling burst to the total scheduling times is less than or equal to a proportion threshold.

13. The method of claim 10, wherein, The first indication information includes at least one of: Third indication information for indicating a scheduling limit of the network side device performing scheduling; Fourth indication information for indicating the network side device entering a second scheduling mode; The second scheduling mode is a scheduling mode related to the scheduling limit of the network side device performing scheduling.

14. The method of claim 13, wherein, The third indication information includes at least one of: A minimum time interval between two consecutive scheduling bursts scheduled by the network side device, and each of the scheduling bursts includes multiple scheduling instances; A maximum value of the number of scheduling instances scheduled by the network side device in a preset time period; A maximum time length scheduled by the network side device in a preset time period; A minimum value of the number of frequency domain units scheduled by the network side device in a time domain unit; A minimum value of the TBS scheduled by the network side device in a time domain unit; A minimum value of the data rate scheduled by the network side device in a time domain unit; A minimum value of the average number of frequency domain units on each scheduling instance scheduled by the network side device in a preset time period; A minimum value of the average TBS on each scheduling instance scheduled by the network side device in a preset time period; A minimum value of the average data rate on each scheduling instance scheduled by the network side device in a preset time period; The network side device expects that the maximum proportion of the scheduling times in which the number of scheduled frequency domain units is less than or equal to a number threshold in a time period or a scheduling burst to the total scheduling times is less than or equal to a proportion threshold; The network side device expects that the maximum proportion of the scheduling times in which the TBS of scheduled data is less than or equal to a TBS threshold in a time period or a scheduling burst to the total scheduling times is less than or equal to a proportion threshold; The network side device expects that the maximum proportion of the scheduling times in which the data rate of scheduled data is less than or equal to a data rate threshold in a time period or a scheduling burst to the total scheduling times is less than or equal to a proportion threshold; The network side device expects a minimum value of the total transmission power of uplink data scheduled in a time domain unit; The network side device expects a minimum value of the average transmission power on uplink data units scheduled in a preset time period; The network-side device schedules the uplink data in a time period or a scheduling burst, and the number of scheduling instances in which the total transmission power of the scheduled uplink data is less than or equal to the total transmission power threshold accounts for the maximum proportion of the total scheduling instances.

15. The method of claim 10, further comprising: The network-side device sends the terminal the first scheduling; The first scheduling is a scheduling for instructing the terminal to trigger the power saving operation in a first time period.

16. The method of claim 15, wherein, The first indication information further includes at least one of the following: The indication information of the first scheduling; The indication information of the first time period.

17. The method of claim 15, wherein, The first scheduling includes at least one of the following: The last scheduling instance in any scheduling instance or scheduling burst; The scheduling instance in which the number of instances scheduled in a preset time period reaches a maximum value; The scheduling instance in which the scheduling in a preset time period reaches a maximum time length; The scheduling instance in which the number of scheduled frequency domain units is less than or equal to a frequency domain unit threshold; The scheduling instance in which the TBS of the scheduled data is less than or equal to a TBS threshold; The scheduling instance in which the data rate of the scheduled data is less than or equal to a data rate threshold; The scheduling instance in which the total transmission power of the scheduled uplink data is less than or equal to a total transmission power threshold.

18. The method of claim 15, wherein, The first time period satisfies at least one of the following: The time length is a minimum time interval between two consecutive scheduling bursts determined according to the first auxiliary information or the first indication information, starting from the first scheduling or a specific time after the first scheduling; The time length is a preset time period, starting from the first scheduling or a specific time after the first scheduling; The time length is determined by the terminal, or indicated by the network-side device, or predefined by a protocol, starting from the first scheduling or a specific time after the first scheduling.

19. A scheduling apparatus, comprising: A first transceiving module, configured to send, by a terminal, first auxiliary information to a network-side device, and / or receive, by the terminal, first indication information from the network-side device; A first processing module, configured to receive, by the terminal, scheduling of the network-side device according to the first auxiliary information or the first indication information; The first auxiliary information includes related information of a scheduling limit expected by the terminal, and / or the first auxiliary information includes related information of a power saving operation expected to be triggered by the terminal; The first indication information includes related information of a scheduling limit of the network-side device performing scheduling, and / or the first indication information includes related information for instructing the terminal to be able to trigger a power saving operation.

20. The apparatus of claim 19, wherein, The first auxiliary information includes at least one of the following: Second indication information for indicating a scheduling limit expected by the terminal; First capability information for indicating that the terminal supports a first scheduling mode; First request information for requesting the network-side device to enter the first scheduling mode; First type information for indicating that the terminal has a target scheduling requirement; The first scheduling mode is a scheduling mode related to the scheduling limit expected by the terminal; The target scheduling requirement is a scheduling requirement related to the scheduling limit expected by the terminal.

21. The apparatus of claim 20, wherein, The second indication information includes at least one of the following: the terminal expects a minimum time interval between two consecutive scheduling bursts, each of which contains multiple scheduling instances; the terminal expects a maximum value of the number of scheduling instances scheduled within a preset time period; the terminal expects a maximum time length of scheduling within a preset time period; the terminal expects a minimum value of the number of frequency domain units scheduled in a time domain unit; the terminal expects a minimum value of TBS scheduled in a time domain unit; the terminal expects a minimum value of data rate scheduled in a time domain unit; the terminal expects a minimum value of the average number of frequency domain units on each scheduling instance scheduled within a preset time period; the terminal expects a minimum value of the average TBS on each scheduling instance scheduled within a preset time period; the terminal expects a minimum value of the average data rate on each scheduling instance scheduled within a preset time period; the terminal expects a maximum proportion of the total scheduling times in a time period or a scheduling burst, in which the number of frequency domain units scheduled is less than or equal to a number threshold; the terminal expects a maximum proportion of the total scheduling times in a time period or a scheduling burst, in which the TBS scheduled is less than or equal to a TBS threshold; the terminal expects a maximum proportion of the total scheduling times in a time period or a scheduling burst, in which the data rate scheduled is less than or equal to a data rate threshold; the terminal expects a minimum value of the total transmission power of uplink data scheduled in a time domain unit; the terminal expects a minimum value of the average transmission power on uplink data units scheduled within a preset time period; the terminal expects a maximum proportion of the total scheduling times in a time period or a scheduling burst, in which the total transmission power of uplink data scheduled is less than or equal to a total transmission power threshold.

22. The apparatus of claim 19, wherein, The first indication information includes at least one of: third indication information for indicating scheduling restrictions of the network side device performing scheduling; fourth indication information for indicating the network side device entering a second scheduling mode; wherein the second scheduling mode is a scheduling mode related to the scheduling restrictions of the network side device performing scheduling.

23. The apparatus of claim 22, wherein, The third indication information includes at least one of: the network side device schedules a minimum time interval between two consecutive scheduling bursts, each of which contains multiple scheduling instances; the network side device schedules a maximum value of the number of scheduling instances within a preset time period; the network side device schedules a maximum time length within a preset time period; the network side device schedules a minimum value of the number of frequency domain units in a time domain unit; the network side device schedules a minimum value of TBS in a time domain unit; the network side device schedules a minimum value of data rate in a time domain unit; the network side device schedules a minimum value of the average number of frequency domain units on each scheduling instance within a preset time period; the network side device schedules a minimum value of the average TBS on each scheduling instance within a preset time period; the network side device schedules a minimum value of the average data rate on each scheduling instance within a preset time period; The network-side device schedules a maximum proportion of scheduling times in a time period or a scheduling burst, in which the number of scheduled frequency domain units is less than or equal to a number threshold. The network-side device schedules a maximum proportion of scheduling times in a time period or a scheduling burst, in which the TBS is less than or equal to a TBS threshold. The network-side device schedules a maximum proportion of scheduling times in a time period or a scheduling burst, in which the data rate is less than or equal to a data rate threshold. The network-side device schedules a minimum value of total transmission power of uplink data in a time domain unit. The network-side device schedules a minimum value of average transmission power of uplink data units in a preset time period. The network-side device schedules a maximum proportion of scheduling times in a time period or a scheduling burst, in which the total transmission power of uplink data is less than or equal to a total transmission power threshold.

24. The apparatus of claim 19, further comprising: a second processing module configured to, after the terminal receives the first scheduling of the network-side device, perform at least one of the following in a first time period: skip PDCCH monitoring, or skip PDCCH monitoring for scheduling downlink data, or skip PDCCH monitoring for scheduling uplink data; enter a sleep state; not start a non-active timer; wherein the first scheduling is a scheduling for instructing the terminal to trigger energy saving operation.

25. The apparatus of claim 24, wherein, The first indication information further comprises at least one of the following: indication information of the first scheduling; indication information of the first time period.

26. The apparatus of claim 24, wherein, The first scheduling comprises at least one of the following: a last scheduling instance in an arbitrary scheduling instance or scheduling burst; a scheduling instance in which a number of instances scheduled in a preset time period reaches a maximum value; a scheduling instance in which scheduling in a preset time period reaches a maximum time length; a scheduling instance in which a number of scheduled frequency domain units is less than or equal to a frequency domain unit number threshold; a scheduling instance in which a TBS is less than or equal to a TBS threshold; a scheduling instance in which a data rate is less than or equal to a data rate threshold; a scheduling instance in which total transmission power of scheduled uplink data is less than or equal to a total transmission power threshold.

27. The apparatus of claim 24, wherein, The first time period satisfies at least one of the following: a time length from the first scheduling or a specific time after the first scheduling to a minimum time interval between two consecutive scheduling bursts determined according to the first assistance information or the first indication information; a time length from the first scheduling or a specific time after the first scheduling to a preset time period; a time length from the first scheduling or a specific time after the first scheduling, which is determined by the terminal, or indicated by the network-side device, or predefined by a protocol.

28. A scheduling apparatus, comprising: a second transceiving module configured to receive, by a network-side device, first assistance information from a terminal, and / or transmit, by the network-side device, first indication information to the terminal; a third processing module configured to perform, by the network-side device, scheduling according to the first assistance information or the first indication information. The first auxiliary information includes information related to a scheduling limit expected by the terminal, and / or the first auxiliary information includes information related to triggering of energy saving operation expected by the terminal. The first indication information includes information related to a scheduling limit of scheduling performed by the network side device, and / or the first indication information includes information for indicating that the terminal can trigger energy saving operation.

29. The apparatus of claim 28, wherein, The first auxiliary information includes at least one of the following: Second indication information for indicating a scheduling limit expected by the terminal; First capability information for indicating that the terminal supports a first scheduling mode; First request information for requesting the network side device to enter the first scheduling mode; First type information for indicating that the terminal has a target scheduling demand; The first scheduling mode is a scheduling mode related to the scheduling limit expected by the terminal; The target scheduling demand is a scheduling demand related to the scheduling limit expected by the terminal.

30. The apparatus of claim 29, wherein, The second indication information includes at least one of the following: The terminal expects a minimum time interval between two consecutive scheduling bursts, and each of the scheduling bursts includes a plurality of scheduling instances; The terminal expects a maximum value of a number of scheduling instances scheduled within a preset time period; The terminal expects a maximum time length of scheduling within a preset time period; The terminal expects a minimum value of a number of frequency domain units scheduled in a time domain unit; The terminal expects a minimum value of TBS scheduled in a time domain unit; The terminal expects a minimum value of a data rate scheduled in a time domain unit; The terminal expects a minimum value of an average number of frequency domain units on each scheduling instance scheduled within a preset time period; The terminal expects a minimum value of an average TBS on each scheduling instance scheduled within a preset time period; The terminal expects a minimum value of an average data rate on each scheduling instance scheduled within a preset time period; The terminal expects a maximum proportion of a number of times of scheduling, in which a number of frequency domain units scheduled in a time period or a scheduling burst is less than or equal to a number threshold, to a total number of times of scheduling in the time period or the scheduling burst; The terminal expects a maximum proportion of a number of times of scheduling, in which TBS scheduled in a time period or a scheduling burst is less than or equal to a TBS threshold, to a total number of times of scheduling in the time period or the scheduling burst; The terminal expects a maximum proportion of a number of times of scheduling, in which a data rate scheduled in a time period or a scheduling burst is less than or equal to a data rate threshold, to a total number of times of scheduling in the time period or the scheduling burst; The terminal expects a minimum value of a total transmit power of uplink data scheduled in a time domain unit; The terminal expects a minimum value of an average transmit power on an uplink data unit scheduled within a preset time period; The terminal expects a maximum proportion of a number of times of scheduling, in which a total transmit power of uplink data scheduled in a time period or a scheduling burst is less than or equal to a total transmit power threshold, to a total number of times of scheduling in the time period or the scheduling burst.

31. The apparatus of claim 28, wherein, The first indication information includes at least one of the following: Third indication information for indicating a scheduling limit of scheduling performed by the network side device; Fourth indication information for indicating that the network side device enters a second scheduling mode; The second scheduling mode is a scheduling mode related to scheduling restriction of scheduling performed by the network side device.

32. The apparatus of claim 31, wherein, The third indication information includes at least one of the following: The network side device schedules a minimum time interval between two continuous scheduling bursts, and each of the scheduling bursts includes multiple scheduling instances; A maximum value of a number of scheduling instances scheduled by the network side device within a preset time period; A maximum time length scheduled by the network side device within a preset time period; A minimum value of a number of frequency domain units scheduled by the network side device in a time domain unit; A minimum value of TBS scheduled by the network side device in a time domain unit; A minimum value of a data rate scheduled by the network side device in a time domain unit; A minimum value of an average number of frequency domain units on each scheduling instance scheduled by the network side device within a preset time period; A minimum value of an average TBS on each scheduling instance scheduled by the network side device within a preset time period; A minimum value of an average data rate on each scheduling instance scheduled by the network side device within a preset time period; A maximum proportion of a number of scheduling times in which a number of frequency domain units scheduled by the network side device in a time period or a scheduling burst is less than or equal to a number threshold, to a total number of scheduling times; A maximum proportion of a number of scheduling times in which TBS scheduled by the network side device in a time period or a scheduling burst is less than or equal to a TBS threshold, to a total number of scheduling times; A maximum proportion of a number of scheduling times in which a data rate scheduled by the network side device in a time period or a scheduling burst is less than or equal to a data rate threshold, to a total number of scheduling times; A minimum value of a total transmission power of uplink data scheduled by the network side device in a time domain unit; A minimum value of an average transmission power on an uplink data unit scheduled by the network side device within a preset time period; A maximum proportion of a number of scheduling times in which a total transmission power of uplink data scheduled by the network side device in a time period or a scheduling burst is less than or equal to a total transmission power threshold, to a total number of scheduling times.

33. The apparatus of claim 28, further comprising: a fourth processing module configured to cause the network side device to send a first scheduling to the terminal; The first scheduling is a scheduling for instructing the terminal to trigger a power saving operation in a first time period.

34. The apparatus of claim 33, wherein, The first indication information further includes at least one of the following: indication information of the first scheduling; indication information of the first time period.

35. The apparatus of claim 33, wherein, The first scheduling includes at least one of the following: a last scheduling instance in an arbitrary scheduling instance or scheduling burst; a scheduling instance in which a number of instances scheduled in a preset time period reaches a maximum value; a scheduling instance in which a maximum time length is scheduled in a preset time period; a scheduling instance in which a number of frequency domain units scheduled is less than or equal to a number threshold of frequency domain units; a scheduling instance in which TBS scheduled is less than or equal to a TBS threshold; a scheduling instance in which a data rate scheduled is less than or equal to a data rate threshold; a scheduling instance in which a total transmission power of uplink data scheduled is less than or equal to a total transmission power threshold.

36. The apparatus of claim 33, wherein, The first time period satisfies at least one of the following: a time length is a minimum time interval between two continuous scheduling bursts determined according to the first assistance information or the first indication information, starting from the first scheduling or a certain time after the first scheduling; a time length is a preset time period, starting from the first scheduling or a certain time after the first scheduling; a time length is determined by the terminal, or indicated by the network side device, or predefined by a protocol, starting from the first scheduling or a certain time after the first scheduling. 37.A terminal comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement steps of the scheduling method according to any one of claims 1 to 9. 38.A network side device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement steps of the scheduling method according to any one of claims 10 to 18. 39.A readable storage medium, the readable storage medium storing programs or instructions, the programs or instructions, when executed by a processor, implement steps of the scheduling method according to any one of claims 1 to 9, or implement steps of the scheduling method according to any one of claims 10 to 18. 40.A computer program product comprising computer instructions, the computer instructions, when executed by a processor, implement steps of the scheduling method according to any one of claims 1 to 9, or implement steps of the scheduling method according to any one of claims 10 to 18.

Images