Resource scheduling method and device, equipment, storage medium and program product

Abstract

Disclosed are a resource scheduling method, apparatus and device, a storage medium and a program product, the method being applied to a base station, the specific technical scheme comprising: receiving a first resource scheduling request sent by a first user type terminal and a second resource scheduling request sent by a second user type terminal; obtaining scheduling priorities corresponding to the first user type terminal and the second user type terminal and a preset scheduling frequency domain range corresponding to the first user type terminal; determining a processing sequence of the first resource scheduling request and the second resource scheduling request according to the scheduling priority; and performing resource scheduling according to the processing sequence and a preset scheduling frequency domain range. Therefore, the data transmission time delay of the RedCap terminal can be reduced, and the service performance of the RedCap terminal is improved.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a method, apparatus, device, storage medium, and program product for resource scheduling. Background Art

[0002] The 5G-Advanced Reduced Capability (5G-ARedCap) user equipment reduces the cost of the terminal by simplifying the number of terminal antennas and reducing the transceiver bandwidth. Currently, RedCap is mainly applied to fields such as in-vehicle telematics boxes (T-Boxes), industrial control, smart wearable devices, and video surveillance, as well as scenarios with low-cost communication requirements in the power, petrochemical, and other industries.

[0003] However, when RedCap terminals and Enhanced Mobile Broadband (embb) terminals access a base station simultaneously, in the case of a large number of embb terminals, the bandwidth resources of the base station will be preempted by the embb terminals, resulting in limited transmission rates for RedCap terminals. Moreover, in commercial and industrial scenarios, RedCap terminals have high requirements for data transmission latency. As the number of embb terminals increases, the data transmission latency of RedCap terminals will increase, thereby reducing the service performance of RedCap terminals. Summary of the Invention

[0004] Embodiments of this application provide a method, apparatus, device, storage medium, and program product for resource scheduling, which can reduce the data transmission latency of RedCap terminals, thereby improving the service performance of RedCap terminals.

[0005] In a first aspect, embodiments of this application provide a method for resource scheduling, which is applied to a base station. The method includes:

[0006] Receiving a first resource scheduling request sent by a first user type terminal and a second resource scheduling request sent by a second user type terminal;

[0007] Obtaining the scheduling priorities corresponding to the first user type terminal and the second user type terminal, and the preset scheduling frequency domain range corresponding to the first user type terminal;

[0008] Determining the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priorities;

[0009] Performing resource scheduling according to the processing order and the preset scheduling frequency domain range.

[0010] In a possible implementation, determining the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priority includes:

[0011] When the scheduling priorities of the first user type terminal and the second user type terminal are the same priority, the time order of receiving the first resource scheduling request and the second resource scheduling request is used as the processing order.

[0012] In a possible implementation, performing resource scheduling according to the processing order and the preset scheduling frequency domain range includes:

[0013] According to the processing order, when the resource scheduling request to be processed is the first resource scheduling request, resource scheduling is performed at each partial bandwidth BWP position;

[0014] According to the processing order, when the resource scheduling request to be processed is the second resource scheduling request, resource scheduling is performed at other partial bandwidth BWP positions except the preset scheduling frequency domain range in each partial bandwidth BWP position.

[0015] In a possible implementation, before obtaining the scheduling priorities corresponding to the first user type terminal and the second user type terminal and the preset scheduling frequency domain range, the method further includes:

[0016] Obtaining the resource scheduling data corresponding to each terminal within a preset duration, where the resource scheduling data includes the total number of scheduling times corresponding to different user type terminals, the number of scheduling failures, and the average scheduling data volume of the first user type terminal at each partial bandwidth BWP position;

[0017] Calculating the ratio of the number of scheduling failures to the total number of scheduling times to obtain the first scheduling failure ratio corresponding to the first user type terminal;

[0018] When the first scheduling failure ratio is greater than a preset threshold, setting the scheduling priority of the first user type terminal to the high priority and setting the scheduling priority of the second user type terminal to the low priority;

[0019] For the average scheduled data volume corresponding to the first user type terminal at each partial bandwidth BWP position, when the maximum average scheduled data volume is greater than or equal to a preset multiple of the secondary average scheduled data volume, determine the target partial bandwidth BWP position corresponding to the maximum average scheduled data volume, where the maximum average scheduled data volume is the maximum value among the scheduled data volumes corresponding to each partial bandwidth BWP position, and the secondary average scheduled data volume is the maximum value among the scheduled data volumes corresponding to each partial bandwidth BWP position except the maximum average data volume;

[0020] Set the preset scheduling frequency domain range to the frequency domain range corresponding to the target partial bandwidth BWP position.

[0021] In a possible implementation, it further includes:

[0022] When the first scheduling failure ratio is less than or equal to the preset threshold, set the scheduling priorities of the first user type terminal and the second user type terminal to the same priority.

[0023] In a possible implementation, after setting the scheduling priority of the first user type terminal to a high priority and setting the scheduling priority of the second user type terminal to a low priority, the method further includes:

[0024] For the average scheduled data volume corresponding to the first user type terminal at each partial bandwidth BWP position, when the maximum average scheduled data volume is less than the preset multiple of the secondary average scheduled data volume, set the preset scheduling frequency domain range to a null value.

[0025] In a second aspect, an embodiment of the present application provides a resource scheduling device, which is applied to a base station, and the device includes:

[0026] A receiving module, configured to receive a first resource scheduling request sent by a first user type terminal and a second resource scheduling request sent by a second user type terminal;

[0027] An obtaining module, configured to obtain the scheduling priorities corresponding to the first user type terminal and the second user type terminal and the preset scheduling frequency domain range corresponding to the first user type terminal;

[0028] A determining module, configured to determine the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priorities;

[0029] A scheduling module, configured to perform resource scheduling according to the processing order and the preset scheduling frequency domain range.

[0030] In a third aspect, an embodiment of the present application provides a terminal device, which includes: a processor and a memory storing computer program instructions;

[0031] When the processor executes the computer program instructions, the method for resource scheduling as described in the first aspect is implemented.

[0032] In a fourth aspect, an embodiment of the present application provides a computer storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the method for resource scheduling as described in the first aspect is implemented.

[0033] In a fifth aspect, an embodiment of the present application provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device is caused to execute the method for resource scheduling as described in the first aspect.

[0034] For a method, device, equipment, storage medium, and program product for resource scheduling according to an embodiment of the present application, after a base station receives a first resource scheduling request sent by a first user type terminal and a second resource scheduling request sent by a second user type terminal, it respectively obtains the scheduling priorities corresponding to the first user type terminal and the second user type terminal and the corresponding preset scheduling frequency domain ranges. In this way, the base station can process the first resource scheduling request and the second resource scheduling request in the order of the scheduling priorities, and perform resource scheduling within the corresponding preset scheduling frequency domain ranges by specifying the preset scheduling frequency domain ranges corresponding to different user type terminals, reducing the transmission delays of different user type terminals, and thus ensuring the service performance of different user type terminals. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings required to be used in the embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative efforts.

[0036] Figure 1 is a flowchart of a method for resource scheduling provided by an embodiment of the present application;

[0037] Figure 2 is an exemplary diagram of a method for setting a preset scheduling frequency domain range and a scheduling priority provided by an embodiment of the present application;

[0038] Figure 3 is an exemplary diagram of the position of a partial bandwidth BWP provided by an embodiment of the present application;

[0039] Figure 4 is an exemplary diagram of a method for resource scheduling provided by an embodiment of the present application;

[0040] Figure 5 It is a schematic structural diagram of a resource scheduling device provided by an embodiment of the present application;

[0041] Figure 6 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Specific Embodiments

[0042] The features and exemplary embodiments of various aspects of the present application will be described in detail below. To make the objectives, technical solutions, and advantages of the present application clearer and more understandable, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application and not to limit the present application. For those skilled in the art, the present application can be implemented without some of these specific details. The following description of the embodiments is only intended to provide a better understanding of the present application by showing examples of the present application.

[0043] It should be noted that, in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variation thereof is intended to cover a non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.

[0044] To solve the problems of the prior art, embodiments of the present application provide a resource scheduling method, device, equipment, storage medium, and program product. The resource scheduling method provided by the embodiments of the present application will be described first below.

[0045] As Figure 1 shown, this method is applied to a base station, and this method includes:

[0046] S101. Receive a first resource scheduling request sent by a first user type terminal and a second resource scheduling request sent by a second user type terminal.

[0047] Among them, the first user type terminal is a RedCap terminal, and the second user type terminal is an embb terminal.

[0048] S102. Obtain the scheduling priorities corresponding to the terminals of the first user type and the terminals of the second user type, and the preset scheduling frequency domain range corresponding to the terminals of the first user type.

[0049] The preset scheduling frequency domain range is the frequency domain range reserved in advance for the terminals of the first user type, which is used to ensure that the terminals of the first user type have sufficient frequency domain resources.

[0050] S103. Determine the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priority.

[0051] It can be understood that according to the scheduling priorities corresponding to the terminals of the first user type and the terminals of the second user type, the priority order of the terminals of the first user type and the terminals of the second user type can be determined, so as to determine the processing order of the first resource scheduling request and the second resource scheduling request according to the priority order of the terminals of the first user type and the terminals of the second user type.

[0052] S104. Perform resource scheduling according to the processing order and the preset scheduling frequency domain range.

[0053] By using the above method, after the base station receives the first resource scheduling request sent by the terminals of the first user type and the second resource scheduling request sent by the terminals of the second user type, it obtains the scheduling priorities corresponding to the terminals of the first user type and the terminals of the second user type and the corresponding preset scheduling frequency domain range respectively. In this way, the base station can process the first resource scheduling request and the second resource scheduling request according to the scheduling priority order, and perform resource scheduling within the corresponding preset scheduling frequency domain range by specifying the preset scheduling frequency domain range corresponding to different user type terminals, reducing the transmission delay of different user type terminals, and thus ensuring the service performance of different user type terminals.

[0054] Among them, the above processing order includes the following two situations:

[0055] Situation 1: When the scheduling priorities of the terminals of the first user type and the terminals of the second user type are the same priority, take the time order of receiving the first resource scheduling request and the second resource scheduling request as the processing order.

[0056] Among them, when the base station receives a resource scheduling request, it generates a time stamp corresponding to the resource scheduling request. When the scheduling priorities of the terminals of the first user type and the terminals of the second user type are the same priority, determine the processing order according to the time stamp corresponding to each resource scheduling request.

[0057] Case 2: When the scheduling priorities of the first user type terminal and the second user type terminal are different priorities, determine the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priorities of the first user type terminal and the second user type terminal. That is, preferentially process the resource scheduling request corresponding to the terminal with the higher priority.

[0058] In this way, when the scheduling priorities of the first user type terminal and the second user type terminal are the same priority, it means that the position of a part of the bandwidth (bandwidth part, BWP) of the current base station is sufficient to support the data transmission requirements of the first user type terminal and the second user type terminal. Therefore, the base station can process them one by one according to the reception time.

[0059] After determining the above processing order, perform resource scheduling according to the preset scheduling frequency domain range. The above S104, perform resource scheduling according to the processing order and the preset scheduling frequency domain range, can be specifically implemented as follows:

[0060] According to the processing order, when the resource scheduling request to be processed is the first resource scheduling request, perform resource scheduling at each part of the bandwidth BWP position.

[0061] According to the processing order, when the resource scheduling request to be processed is the second resource scheduling request, perform resource scheduling at other part of the bandwidth BWP positions except the preset scheduling frequency domain range in each part of the bandwidth BWP position.

[0062] It should be noted that when the first user type terminal is a RedCap terminal, since each RedCap terminal uses a part of the bandwidth and the part of the bandwidth used by each RedCap terminal is fixed and unchanged, the RedCap terminal can perform resource scheduling at the corresponding part of the bandwidth BWP position.

[0063] It can be understood that when the second user type terminal is an embb terminal, since the embb terminal uses all the bandwidth of the base station, the base station can perform resource scheduling for the embb terminal at all BWP positions. Among them, the preset scheduling frequency domain range is the frequency domain range reserved by the base station for the RedCap terminal in advance. To ensure the service performance of the RedCap terminal, the base station performs resource scheduling at other part of the bandwidth BWP positions except the preset scheduling frequency domain range.

[0064] The method provided by the embodiment of the present application is adopted, wherein the preset scheduling frequency domain range is the frequency domain range reserved for the first user type terminal. In this way, when there are many first user type terminals, when the resource scheduling request to be processed is the second resource scheduling request, that is, the resource scheduling request corresponding to the second user type terminal, in order to avoid the second resource scheduling request occupying the frequency domain resources corresponding to the first user type terminal, resulting in a decrease in the service performance of the first user type terminal, the base station performs resource scheduling at other bandwidth BWP positions except the preset scheduling frequency domain range. By reserving the frequency domain range for the first user type terminal, the service performance of the first user type terminal is guaranteed.

[0065] The following combination Figure 2 Introduce the scheduling priorities corresponding to different user type terminals and the method for determining the preset frequency domain range, such as Figure 2 As shown, the method includes:

[0066] S201: Obtain resource scheduling data corresponding to each terminal within a preset time period.

[0067] The resource scheduling data includes the total scheduling times, scheduling failure times and average scheduling data volume of the first user type terminal at each partial bandwidth BWP position corresponding to different user type terminals.

[0068] The preset duration is pre-set based on experience. The total scheduling times refers to the number of times each first user type terminal and the second user type terminal initiates a resource scheduling request within the preset duration. The scheduling failure times refers to the number of times each first user type terminal and the second user type terminal fails to obtain resources. The average scheduled data volume of the first user type terminal at each partial bandwidth BWP position refers to the amount of data obtained from the partial bandwidth BWP position by the first user type terminal in each data scheduling.

[0069] As shown in Table 1, Table 1 exemplarily shows resource scheduling data, as shown in Table 1:

[0070] Table 1

[0071]

[0072]

[0073] The base station may distinguish different users according to the user identifier carried in the resource scheduling request initiated by the terminal, for example, different users may be distinguished according to temporary identifiers such as CALLID or C-RNTI;

[0074] The base station can identify the user type based on the Message Type 1 (msg1) or Message Type 3 (msg3) sent by the terminal, or the SupportOfRedcap-r17 field in the User Equipment (UE) capability message of the Uu Interface (uu). The embodiments of the present application do not limit the method for determining the user type.

[0075] For a RedCap terminal, the base station can determine the partial bandwidth BWP position where the RedCap terminal is located according to the locationandbandwidth cell.

[0076] For an embb terminal, the base station can perform resource scheduling for the embb terminal within the frequency domain range of the entire bandwidth, that is, perform resource scheduling within the entire bandwidth of BWP1. For example, if the base station provides 100M bandwidth, then the entire 100M bandwidth is the BWP1 bandwidth. For a RedCap terminal, the base station performs resource scheduling at the BWP position corresponding to each RedCap. Continuing with the above example, the base station can divide the 100M total bandwidth into 5 parts, namely BWP1-1, BWP1-2, BWP1-3, BWP1-4, BWP1-5, and the specific position situation is as Figure 3 shown. Among them, the cell bandwidth provided by the base station is 100MHz, that is, the entire BWP1 bandwidth is 100MHz, and the base station can perform resource scheduling for the embb terminal on the entire BWP1 bandwidth. For a RedCap terminal, the base station divides the 100M total bandwidth into 5 parts, namely BWP1-1, BWP1-2, BWP1-3, BWP1-4, BWP1-5, and BWP1-1, BWP1-2, BWP1-3, BWP1-4, BWP1-5 respectively correspond to different RedCap terminals.

[0077] For the total number of scheduling times, the base station can determine the user terminals with data scheduling according to CALLID or C-RNTI, and then determine the number of scheduling times within a preset duration. The more the total number of scheduling times, the busier the UE service.

[0078] For the average scheduling data volume, the base station can determine the average value of the data volume scheduled each time for the users with data scheduling according to CALLID or C-RNTI within a preset duration. The larger the value, the more data to be sent by the UE, and the base station should give priority to ensuring the bandwidth and service performance of this type of terminal.

[0079] S202. Calculate the ratio of the number of scheduling failures to the total number of scheduling times to obtain the first scheduling failure ratio corresponding to the first user type terminal.

[0080] Among them, the scheduling failure ratio calculated according to Table 1 above is shown in Table 2 as follows:

[0081] Table 2

[0082]

[0083] Among them, by calculating the ratio of the number of scheduling failures to the total number of schedulings, the second scheduling failure ratio corresponding to the eMBB terminal can be obtained as 1.02%, and the first scheduling failure ratio corresponding to the RedCap terminal is 1.29%.

[0084] S203. When the first scheduling failure ratio is greater than the preset threshold, set the scheduling priority of the first user type terminal to a high priority, and set the scheduling priority of the second user type terminal to a low priority.

[0085] Among them, the preset threshold can be a preset multiple of the second scheduling failure ratio. In one example, the preset threshold can be twice the second scheduling failure ratio. Since the first scheduling failure ratio of the RedCap terminal is greater than twice the second scheduling failure ratio of the eMBB terminal, the base station sets the scheduling priority corresponding to the RedCap terminal to "RedCap terminal first".

[0086] S204. For the average scheduling data volume corresponding to the first user type terminal at each partial bandwidth BWP position, when the maximum average scheduling data volume is greater than or equal to a preset multiple of the secondary average scheduling data volume, determine the target partial bandwidth BWP position corresponding to the maximum average scheduling data volume.

[0087] Among them, the maximum average scheduling data volume is the maximum value among the scheduling data volumes corresponding to each partial bandwidth BWP position, and the secondary average scheduling data volume is the maximum value among the scheduling data volumes corresponding to each partial bandwidth BWP position except the maximum average data volume.

[0088] Specifically, as shown in Table 3, Table 3 exemplarily shows the average scheduling data volume of different RedCap terminals at each partial bandwidth BWP position:

[0089] Table 3

[0090] BWP Location of RedCap Terminal Summation Term: Average Scheduled Data Volume (Bytes) BWP1-1 7235 BWP1-2 13856 BWP1-3 5039 BWP1-4 2941 BWP1-5 3962

[0091] By calculating the preset multiple of the maximum average scheduling data volume and the secondary average scheduling quantity in each BWP position, it can be determined whether there is a frequency domain range where the RedCap terminal service is busy among the above BWP positions. When it is determined that there is a frequency domain range with busy service, adjust the preset scheduling frequency domain range to this frequency domain range with busy service.

[0092] In one example, the preset multiple can be 2 times, where the maximum average scheduled data volume is 13,856 and the secondary average scheduling quantity is 7,235. Since 13,856 is less than 2 times of 7,235, there is no frequency domain range with busy RedCap terminal services in the BWP positions in Table 3 above. Therefore, the preset scheduling frequency domain range can be set to a null value.

[0093] S205. Set the preset scheduling frequency domain range to the frequency domain range corresponding to the target partial bandwidth BWP position.

[0094] By using the method provided in the embodiment of the present application, through the resource scheduling data within the preset duration, the first scheduling failure ratio of the first user type terminal can be calculated. When the first scheduling failure ratio is greater than the preset threshold, it indicates that the service quality of the first user type terminal is relatively low. To improve the service performance of the first user type terminal, the scheduling priority of the first user type terminal is set to a high priority. Thus, after the base station receives the resource scheduling requests of the first user type terminal and the second user type terminal simultaneously, it preferentially processes the resource scheduling request of the first user type terminal to ensure the transmission delay and service performance of the first user type terminal. When the maximum average scheduled data volume is greater than or equal to the preset multiple of the secondary average scheduled data volume, it indicates that there are frequent resource mobilizations in the target partial bandwidth BWP position corresponding to the maximum average scheduled data volume, that is, the target partial bandwidth BWP position bears more services of the first user type terminal. Therefore, to ensure the service performance of the first user type terminal, the preset frequency domain scheduling range is set to the frequency domain range of the target partial bandwidth BWP position. In this way, when the base station processes the resource scheduling request of the second user type terminal subsequently, it can avoid occupying the bandwidth positions within the preset frequency domain range, thereby ensuring the service performance of the first user type terminal.

[0095] It should be noted that when the first scheduling failure ratio is less than or equal to the preset threshold, the scheduling priorities of the first user type terminal and the second user type terminal are set to the same priority.

[0096] In one example, the scheduling failure ratio of the first RedCap terminal is less than or equal to 2 times the second scheduling failure ratio of the eMBB terminal, and the base station sets the scheduling priority to "the same for RedCap terminal and eMBB terminal".

[0097] It can be understood that when the first scheduling failure ratio is less than or equal to the preset threshold, it indicates that within the above preset duration, the data transmission service quality of the first user type terminal is good, that is, the frequency domain resources of the current base station are sufficient to support the resource scheduling of the first user type terminal and the second user type terminal, and there is no need to set a high-priority terminal.

[0098] In some embodiments of the present application, after setting the scheduling priorities of the first user type terminal and the second user type terminal as described above, a preset frequency domain range is further set according to the secondary average scheduling data volume and the maximum average scheduling data volume. Specifically:

[0099] For the average scheduling data volume corresponding to the first user type terminal at each partial bandwidth BWP position, when the maximum average scheduling data volume is less than a preset multiple of the secondary average scheduling data volume, the preset scheduling frequency domain range is set to a null value.

[0100] Combined with Table 3 above, specifically, the preset multiple can be 2 times. Among them, the maximum average scheduling data volume is 13856, and the secondary average scheduling quantity is 7235. Since 13856 is less than 2 times of 7235, there is no frequency domain range where the RedCap terminal service is busy among the BWP positions in Table 3 above. Therefore, the preset scheduling frequency domain range can be set to a null value.

[0101] In this way, when the maximum average scheduling data volume is less than a preset multiple of the secondary average scheduling data volume, it means that the resources required by the first user type terminal are not concentrated in a certain partial bandwidth BWP position. Therefore, the preset scheduling frequency domain range can be set to a null value. In this way, the subsequent base station can implement resource scheduling for the first user type terminal and resource scheduling for the second user type terminal at each partial bandwidth BWP position.

[0102] The following combines Figure 4 to introduce the complete process of the resource scheduling method provided by the embodiments of the present application. As Figure 4 shown, the method includes:

[0103] S401. Obtain the scheduling priority and the preset scheduling frequency domain range.

[0104] Among them, the above scheduling priority and preset scheduling frequency domain range are the scheduling priority and preset scheduling frequency domain range calculated by the base station in the previous preset period.

[0105] S402. Obtain the resource scheduling data at time T.

[0106] Among them, time T is set according to the preset period, that is, the base station updates the scheduling priority and the preset scheduling frequency domain range every preset period.

[0107] S403. Extract information such as the total number of scheduling times, the number of scheduling failures, and the user type.

[0108] S404. Determine the scheduling priority.

[0109] Specifically, for the method of determining the scheduling priority, refer to the relevant description in the above embodiments, which will not be elaborated here.

[0110] S405, RedCap has priority.

[0111] S406, RedCap is the same as embb.

[0112] S407, Set the preset scheduling frequency domain range.

[0113] S408, Adjust the parameters.

[0114] S409, Return to execute S403 at time T + 1.

[0115] Using the method provided by the embodiments of the present application, after receiving a resource scheduling request, the base station performs resource scheduling according to the corresponding scheduling priority and the preset scheduling frequency domain range. Then, the resource scheduling data within the preset duration of the resources is obtained every preset period, that is, the resource scheduling data at time T mentioned above. Every preset period, the scheduling priority of different user types and the corresponding preset scheduling frequency domain range are determined using information such as the total number of scheduling times, the number of scheduling failures, and the user type in the resource scheduling data. In this way, the scheduling priority and the preset scheduling frequency domain range can be dynamically updated according to the resource scheduling data within the preset duration of each preset period. By adjusting the scheduling priority and the preset scheduling frequency domain range, flexible resource allocation for terminals of different user types can be achieved.

[0116] Based on the same concept, the embodiments of the present application also provide a resource scheduling device applied to a base station, as Figure 5 shown. The device includes:

[0117] A receiving module 501, configured to receive a first resource scheduling request sent by a first user type terminal and a second resource scheduling request sent by a second user type terminal;

[0118] An obtaining module 502, configured to obtain the scheduling priorities corresponding to the first user type terminal and the second user type terminal and the preset scheduling frequency domain range corresponding to the first user type terminal;

[0119] A determining module 503, configured to determine the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priority;

[0120] A scheduling module 504, configured to perform resource scheduling according to the processing order and the preset scheduling frequency domain range.

[0121] In a possible implementation, the determining module 503 is specifically configured to:

[0122] When the scheduling priorities of the first user type terminal and the second user type terminal are the same priority, the time sequence of receiving the first resource scheduling request and the second resource scheduling request is used as the processing sequence.

[0123] In a possible implementation manner, the scheduling module 504 is specifically configured to:

[0124] According to the processing sequence, when the resource scheduling request to be processed is the first resource scheduling request, resource scheduling is performed at each partial bandwidth BWP position;

[0125] According to the processing sequence, when the resource scheduling request to be processed is the second resource scheduling request, resource scheduling is performed at other partial bandwidth BWP positions except the preset scheduling frequency domain range in each partial bandwidth BWP position.

[0126] In a possible implementation manner, the device further includes:

[0127] The obtaining module 502 is further configured to obtain the resource scheduling data corresponding to each terminal within a preset duration before obtaining the scheduling priorities corresponding to the first user type terminal and the second user type terminal and the preset scheduling frequency domain range. The resource scheduling data includes the total scheduling times corresponding to different user type terminals, the scheduling failure times, and the average scheduling data volume of the first user type terminal at each partial bandwidth BWP position;

[0128] The calculating module is configured to calculate the ratio of the scheduling failure times to the total scheduling times to obtain the first scheduling failure ratio corresponding to the first user type terminal;

[0129] The setting module is configured to, when the first scheduling failure ratio is greater than a preset threshold, set the scheduling priority of the first user type terminal to the high priority and set the scheduling priority of the second user type terminal to the low priority;

[0130] The determining module 503 is further configured to, for the average scheduling data volume corresponding to the first user type terminal at each partial bandwidth BWP position, when the maximum average scheduling data volume is greater than or equal to a preset multiple of the secondary average scheduling data volume, determine the target partial bandwidth BWP position corresponding to the maximum average scheduling data volume. The maximum average scheduling data volume is the maximum value among the scheduling data volumes corresponding to each partial bandwidth BWP position, and the secondary average scheduling data volume is the maximum value among the scheduling data volumes corresponding to each partial bandwidth BWP position except the maximum average data volume;

[0131] The setting module is further configured to set the preset scheduling frequency domain range as the frequency domain range corresponding to the target partial bandwidth BWP position.

[0132] In a possible implementation manner, the setting module is further configured to:

[0133] In the case where the first scheduling failure ratio is less than or equal to the preset threshold, set the scheduling priorities of the first user type terminal and the second user type terminal to the same priority.

[0134] In a possible implementation manner, the setting module is further configured to:

[0135] After setting the scheduling priority of the first user type terminal to a high priority and setting the scheduling priority of the second user type terminal to a low priority, for the average scheduling data volume corresponding to each partial bandwidth BWP position of the first user type terminal, in the case where the maximum average scheduling data volume is less than a preset multiple of the secondary average scheduling data volume, set the preset scheduling frequency domain range to a null value.

[0136] It should be noted that the resource scheduling device corresponds to the above resource scheduling method. All implementation manners in the above method embodiments are applicable to the embodiments of this device and can achieve the same technical effects.

[0137] Figure 6 The hardware structure diagram of the electronic device provided by the embodiment of the present application is shown.

[0138] The electronic device may include a processor 601 and a memory 602 storing computer program instructions.

[0139] Specifically, the above processor 601 may include a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0140] The memory 602 may include a mass storage for data or instructions. By way of example and not limitation, the memory 602 may include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory 602 may include removable or non-removable (or fixed) media. Where appropriate, the memory 602 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, the memory 602 is a non-volatile solid-state memory.

[0141] In a particular embodiment, the memory 602 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage media device, an optical storage media device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.

[0142] The processor 601 reads and executes the computer program instructions stored in the memory 602 to implement any one of the resource scheduling methods in the above embodiments.

[0143] In one example, the electronic device may further include a communication interface 603 and a bus 604. Among them, as Figure 6 shown, the processor 601, the memory 1302, and the communication interface 603 are connected through the bus 604 to complete communication with each other.

[0144] The communication interface 603 is mainly used to implement communication between each module, device, unit, and / or device in the embodiments of the present application.

[0145] The bus 604 includes hardware, software, or both, and couples components of the electronic device to each other. By way of example and not limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Super Transmission (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low PinCount (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable bus or a combination of two or more of these. Where appropriate, the bus 604 may include one or more buses. Although the embodiments of the present application describe and illustrate specific buses, the present application contemplates any suitable bus or interconnect.

[0146] In addition, in combination with the resource scheduling method in the above embodiments, an embodiment of the present application can be implemented by providing a computer storage medium. Computer program instructions are stored on the computer storage medium; when the computer program instructions are executed by a processor, any one of the resource scheduling methods in the above embodiments is implemented.

[0147] An embodiment of the present application also provides a computer program product, including a computer program, and when the computer program is executed by a processor, any one of the resource scheduling methods in the above embodiments is implemented.

[0148] It should be clear that the present application is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and illustrated as examples. However, the method process of the present application is not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications, and additions, or change the order between steps after understanding the spirit of the present application.

[0149] The functional blocks shown in the above structural block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, and so on. When implemented in software, the elements of the present application are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium or transmitted via a data signal carried in a carrier wave over a transmission medium or a communication link. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable read-only memory (EROM), floppy disks, Compact Disc Read-Only Memory (CD-ROM), optical discs, hard disks, fiber optic media, Radio Frequency (RF) links, and so on. The code segment can be downloaded via a computer network such as the Internet, intranet, and so on.

[0150] It should also be noted that the exemplary embodiments mentioned in the present application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above steps, that is, the steps can be executed in the order mentioned in the embodiments, can be different from the order in the embodiments, or several steps can be executed simultaneously.

[0151] Aspects of the present disclosure have been described above with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each block in the flowcharts and / or block diagrams, and the combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the functions / actions specified in one or more blocks of the flowcharts and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and the combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or by a combination of dedicated hardware and computer instructions.

[0152] The above are only specific embodiments of the present application. Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, modules, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein. It should be understood that the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should all be covered within the protection scope of the present application.

Claims

1. A method for resource scheduling, characterized in that, Applied to a base station, the method includes: Receiving a first resource scheduling request sent by a first user type terminal and a second resource scheduling request sent by a second user type terminal; Obtaining the scheduling priorities corresponding to the first user type terminal and the second user type terminal, and the preset scheduling frequency domain range corresponding to the first user type terminal; Determining the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priorities; Performing resource scheduling according to the processing order and the preset scheduling frequency domain range.

2. The method according to claim 1, characterized in that The determining the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priorities includes: When the scheduling priorities of the first user type terminal and the second user type terminal are the same priority, taking the time order of receiving the first resource scheduling request and the second resource scheduling request as the processing order.

3. The method according to claim 2, wherein The performing resource scheduling according to the processing order and the preset scheduling frequency domain range includes: According to the processing order, when the resource scheduling request to be processed is the first resource scheduling request, performing resource scheduling at each partial bandwidth BWP position; According to the processing order, when the resource scheduling request to be processed is the second resource scheduling request, performing resource scheduling at other partial bandwidth BWP positions except the preset scheduling frequency domain range in each partial bandwidth BWP position.

4. The method according to claim 1, wherein Before obtaining the scheduling priorities corresponding to the first user type terminal and the second user type terminal and the preset scheduling frequency domain range, the method further includes: Obtaining the resource scheduling data corresponding to each terminal within a preset duration, where the resource scheduling data includes the total scheduling times, the scheduling failure times corresponding to different user type terminals, and the average scheduling data volume of the first user type terminal at each partial bandwidth BWP position; Calculating the ratio of the scheduling failure times to the total scheduling times to obtain the first scheduling failure ratio corresponding to the first user type terminal; When the first scheduling failure ratio is greater than a preset threshold, setting the scheduling priority of the first user type terminal to a high priority, and setting the scheduling priority of the second user type terminal to a low priority; For the average scheduling data volume corresponding to the first user type terminal at each partial bandwidth BWP position, when the maximum average scheduling data volume is greater than or equal to a preset multiple of the secondary average scheduling data volume, determining the target partial bandwidth BWP position corresponding to the maximum average scheduling data volume, where the maximum average scheduling data volume is the maximum value among the scheduling data volumes corresponding to each partial bandwidth BWP position, and the secondary average scheduling data volume is the maximum value among the scheduling data volumes corresponding to each partial bandwidth BWP position except the maximum average scheduling data volume; Setting the preset scheduling frequency domain range to the frequency domain range corresponding to the target partial bandwidth BWP position.

5. The method according to claim 4, wherein It further includes: When the first scheduling failure ratio is less than or equal to the preset threshold, set the scheduling priorities of the terminals of the first user type and the terminals of the second user type to the same priority.

6. The method according to claim 4, characterized in that After setting the scheduling priority of the terminals of the first user type to a high priority and setting the scheduling priority of the terminals of the second user type to a low priority, the method further includes: For the average scheduling data volume corresponding to each partial bandwidth BWP position of the terminals of the first user type, when the maximum average scheduling data volume is less than a preset multiple of the secondary average scheduling data volume, set the preset scheduling frequency domain range to a null value.

7. An apparatus for resource scheduling, characterized in that, Applied to a base station, the device includes: a receiving module, configured to receive a first resource scheduling request sent by a terminal of a first user type and a second resource scheduling request sent by a terminal of a second user type; an obtaining module, configured to obtain the scheduling priorities corresponding to the terminals of the first user type and the terminals of the second user type, and the preset scheduling frequency domain range corresponding to the terminals of the first user type; a determining module, configured to determine the processing order of the first resource scheduling request and the second resource scheduling request according to the scheduling priorities; a scheduling module, configured to perform resource scheduling according to the processing order and the preset scheduling frequency domain range.

8. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the method for resource scheduling according to any one of claims 1-6 is implemented.

9. A computer-readable storage medium, characterized in that, Computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by the processor, the method for resource scheduling according to any one of claims 1-6 is implemented.

10. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device is caused to execute the method for resource scheduling according to any one of claims 1-6.

Images