Resource scheduling method and device, access network equipment and storage medium

Abstract

The invention relates to a resource scheduling method and device, access network equipment and a storage medium. The method comprises: according to a resource allocation proportion of each contract type service, determining a standardized data transmission amount of each contract type service, the contract type service comprising at least one NGBR bearer type service; according to the standardized data sending amount of a target contract type service and the standardized data sending amount of each contract type service, a target priority corresponding to the target contract type service is determined, and the target contract type service is one of the contract type services; and performing resource scheduling on the target contract type service based on the target priority. According to the method, the priority of the target contract type service can be dynamically determined, and the purpose of differential resources of different user levels is achieved according to the contract type.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a resource scheduling method, apparatus, access network equipment, and storage medium. Background Technology

[0002] In today's communications field, with the continuous expansion of overseas Customer Premise Equipment (CPE) user distribution and the strong demand for low cost and high flexibility, Fixed Wireless Access (FWA) technology has emerged. FWA primarily provides broadband Internet access. As a low-cost wireless broadband solution, it leverages the high bandwidth capabilities of 5G New Radio (5G NR) to replace traditional last-mile fiber-to-the-home (FTTH) with 5G wireless access. This approach not only saves the cost and hassle of fiber optic installation but also provides flexible broadband access services to businesses and homes, delivering a service experience equivalent to fiber broadband.

[0003] Currently, base stations primarily employ a priority-based round-robin scheduling method. For example, 5G Quality of Service Identifier (5QI) bearers numbered 1-9 represent different services, with priorities decreasing sequentially. The base station maintains a priority queue. When a user's bearer updates service data, the bearer is either inserted into or removed from the corresponding priority queue based on the service type. Scheduling proceeds by traversing all priority queues downwards from the highest priority, queuing users for subsequent resource allocation. In this method, user bearer priorities are fixed, and resources are allocated on a first-come, first-served basis. If a user has a high-priority bearer, services on their lower-priority bearers will also be scheduled. However, this round-robin scheduling method may result in users with only low-priority service bearers or users with high-priority service bearers but far back in the queue not receiving scheduling for extended periods. Summary of the Invention

[0004] Therefore, it is necessary to provide a resource scheduling method, apparatus, access network equipment, and storage medium to address the aforementioned technical problems.

[0005] Firstly, this application provides a resource scheduling method, which includes:

[0006] Based on the resource allocation ratio of each type of contracted service, the standardized data transmission volume of each type of contracted service is determined, wherein the contracted service includes at least one NGBR bearer type service.

[0007] Based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service, the target priority corresponding to the target subscription type service is determined, and the target subscription type service is one of the various subscription type services;

[0008] Resource scheduling is performed on the target contract type services based on the target priority.

[0009] Secondly, this application also provides an access network device, characterized in that it includes: a memory, a transceiver, and a processor.

[0010] The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

[0011] Based on the resource allocation ratio of each type of contracted service, the standardized data transmission volume of each type of contracted service is determined, wherein the contracted service includes at least one NGBR bearer type service.

[0012] Based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service, the target priority corresponding to the target subscription type service is determined, and the target subscription type service is one of the various subscription type services;

[0013] Resource scheduling is performed on the target contract type services based on the target priority.

[0014] Thirdly, this application also provides a resource scheduling apparatus, which includes:

[0015] The transmission volume determination module is used to determine the standardized data transmission volume of each subscription type service based on the resource allocation ratio of each subscription type service, wherein the subscription type service includes at least one NGBR bearer type service.

[0016] The priority determination module is used to determine the target priority corresponding to the target subscription type service based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service, wherein the target subscription type service is one of the various subscription type services;

[0017] The resource scheduling module is used to schedule resources for the target subscription type service based on the target priority.

[0018] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect or any embodiment thereof.

[0019] Fifthly, this application also provides a computer program product comprising a computer program that, when executed by a processor, implements the method described in the first aspect or any embodiment thereof.

[0020] The above resource scheduling method determines the standardized data transmission volume of each subscription type service based on the resource allocation ratio of each subscription type service. The subscription type services include at least one NGBR bearer type service. Based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volumes of each subscription type service, a target priority corresponding to the target subscription type service is determined. The target subscription type service is one of the various subscription type services. Resource scheduling is performed on the target subscription type service based on the target priority. This scheme standardizes the data transmission volume by using the resource allocation ratio of each subscription type service. Based on the standardized data transmission volume of each subscription type service and the standardized data transmission volume of the target subscription type service, the priority of the target subscription type service can be determined. Resource scheduling is then performed on the target subscription type service according to this priority. This achieves resource scheduling based on resource allocation ratio, dynamically determining the priority of the target subscription type service and achieving differentiated resource allocation according to subscription type for different user levels. This avoids users with only low-priority services or users with high-priority services but at the back of the queue being unable to receive scheduling for extended periods. Attached Figure Description

[0021] Figure 1 A flowchart illustrating a resource scheduling method. Figure 1 ;

[0022] Figure 2 A flowchart illustrating a resource scheduling method. Figure 2 ;

[0023] Figure 3 A flowchart illustrating a resource scheduling method. Figure 3 ;

[0024] Figure 4 A schematic diagram of the structure of an access network device provided in one embodiment;

[0025] Figure 5 This is a structural block diagram of a resource scheduling device. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0027] In this embodiment of the invention, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0028] FWA primarily focuses on providing broadband internet access services. As a low-cost wireless broadband solution, it delivers a service experience comparable to fiber optic broadband. Leveraging the high bandwidth capabilities of 5G NR, it replaces the last-mile fiber-to-the-home (FTTH) approach with 5G wireless access, eliminating the need for fiber optic cabling. This allows for low-cost and flexible broadband access for businesses and homes. Given the current distribution of CPE users overseas and the urgent need for low-cost, high-flexibility solutions, building an FWA wireless network and implementing corresponding FWA wireless network strategies is particularly important.

[0029] Currently, base stations primarily employ a priority-based round-robin scheduling method. Taking 5QI bearers 1-9 as an example, they represent different services, with priorities decreasing sequentially. The base station maintains a priority queue. When a user's bearer updates service data, the bearer is either inserted into the corresponding priority queue (from no service to service) or removed from the queue (from service to no service). Bearers with the same priority are queued in a first-in, first-out (FIFO) order. During scheduling, all priority queues are traversed downwards from the highest priority, queuing users for subsequent resource allocation. For example, the priority queue corresponding to the 5QI1 bearer is higher than that of the 5QI9 bearer; users with the 5QI1 bearer will queue before users with only the 5QI9 bearer, and will ultimately receive resources first.

[0030] User load balancing has a fixed priority, following a first-come, first-served resource allocation principle. Queuing is based on load balancing, while resource allocation is based on user load balancing. If a user has high-priority loads and other low-priority loads, the high-priority load will be prioritized, causing services on the lower-priority loads to be scheduled as well. If a user's load is very heavy, consuming all physical resources, other queued users in the current time slot will have no resources available and cannot be scheduled. The round-robin scheduling method moves already scheduled users in the same priority queue to the end of the queue each time slot, preventing the continuous scheduling of the first few users of the same priority.

[0031] When the base station's flow control function is enabled, if a user's rate does not meet the minimum non-guaranteed bit rate (NGBR) configured by the base station, the base station will temporarily elevate its priority, thereby increasing the user's scheduling chances. This means the user will be placed earlier in the queue and given priority resource allocation to meet the minimum guaranteed rate. At this time, all NGBR bearers that do not meet the minimum NGBR bit rate will be elevated to the same guaranteed priority layer, which is very high, higher than all normal service bearers. After one successful scheduling, the priority will fall back to the previous bearer priority, awaiting the next flow control function to determine whether another temporary priority increase is needed.

[0032] There are some problems with using priority-based round-robin scheduling algorithms. If there are too many users carrying high-priority services within a base station, and these users have multiple bearers and large traffic volumes, it can lead to insufficient base station resources. In this situation, many users with only low-priority service bearers, or those with high-priority service bearers but far back in the queue, will not be scheduled for a long time, severely impacting the user experience, especially for users with high-priority service bearers but far back in the queue.

[0033] While flow control can temporarily boost the priority of user NGBR services to ensure their rate (at the bearer level, different NGBR bearers can be configured with different minimum guaranteed rates), thus avoiding prolonged starvation, the temporary priority boost is always the same. Furthermore, the minimum guaranteed rate does not differentiate between base station load conditions; that is, the guaranteed rate remains unchanged regardless of whether base station resources are abundant or scarce. This leads to a situation where, if the guaranteed rate is set too high, when base station resources are scarce and there are many users, a large number of low-priority service bearers will occupy base station resources, affecting the rate of high-priority service bearers. Conversely, if the guaranteed rate is set too low, when base station resources are abundant, high-priority services may occupy base station resources, causing low-priority service bearers to starve. The only solution is to temporarily boost the priority to ensure the minimum bit rate, thus impacting user experience.

[0034] To address the aforementioned issues, in this embodiment, the access network device can divide the NGBR bearer into multiple priorities based on the various subscribed service types. Furthermore, to achieve the goal of allocating base station resources according to resource allocation ratios for different services, the priorities of the various service types will dynamically increase or decrease based on the data transmission volume of the service.

[0035] For example, the various service types mentioned above can include: Gold, Silver, and Bronze services under the 5QI contract. Gold services have a higher priority than Silver services, and Silver services have a higher priority than Bronze services. To achieve the goal of allocating base station resources according to the resource allocation ratio for Gold, Silver, and Bronze services, the priority of each service will dynamically increase or decrease based on the data transmission volume.

[0036] In this embodiment, the access network device (which can be a base station) adds an overload state. When the Physical Resource Block (PRB) utilization rate (which can be understood as the percentage of base station resource usage) is greater than or equal to the set overload threshold, the base station is determined to enter the overload state. In the overload state, a new bearer-level NGBR minimum guaranteed rate is provided. That is, gold, silver, and bronze service types can each configure their own minimum guaranteed rate under overload conditions. The same service type (such as all bronze services) can also be configured with different minimum guaranteed rates through different 5QI bearers. This works in conjunction with the NGBR minimum guaranteed rate under non-overload conditions to more flexibly ensure user experience.

[0037] Minimum guaranteed rate is a means of base station flow control. The purpose of flow control is to balance user fairness and system capacity while ensuring the quality of service. Fairness means guaranteeing the minimum throughput of a resource block (RB) or user scheduling to prevent low-priority services from being starved while high-priority services continue to transmit data. Some services have their own guaranteed rates, and the minimum throughput of these services must be guaranteed. System capacity means limiting the maximum throughput of a RB or user scheduling, that is, limiting the actual resources available to a user based on their subscribed rate.

[0038] Flow control is typically implemented using token buckets. For NGBR (Next Generation Batch Flow) and Guaranteed Bit Rate (GBR) services, there are separate sets of variables limiting the lower and upper limits of the rate. This article only discusses NGBR services. NGBR services have Minbr (Minimum Guaranteed Rate for Bearers) and Ambr (Maximum Rate for All Bearers). The base station converts these rate parameters into bits and generates corresponding token buckets. The token bucket size is equal to the number of bits per second represented by the rate. Token counts are updated every millisecond by an amount equal to the token bucket size divided by 1000, and the number of tokens in a token bucket does not exceed the token bucket size. When bearer scheduling is successful, the token count for the corresponding data amount is subtracted from the token bucket of the corresponding bearer. The number of tokens in the token bucket can be negative.

[0039] When queuing users for resource allocation (using a for loop through all priority queues), the token count in the corresponding token bucket is checked. If the Minbr token bucket count is greater than 0, it indicates that the data volume scheduled for this bearer has not yet met the minimum guaranteed rate. The priority is temporarily increased to improve the order of resource allocation for this bearer and meet the minimum guaranteed rate. If the Minbr token bucket count is less than 0 (negative) and Ambr is greater than 0, it indicates that the bearer has been successfully scheduled and the minimum guaranteed rate has been met. Furthermore, the total data volume of all bearers scheduled for this user has not exceeded the maximum rate limit. In this case, the bearer is scheduled normally and no priority increase is performed. If Ambr is less than 0, it indicates that the total data volume of all bearers scheduled for this user has exceeded the maximum rate limit. In this case, the user is removed from the queue and no longer scheduled until the token count in the Ambr token bucket of this user is updated to a positive value.

[0040] The resource scheduling method in this application embodiment can be applied to a resource scheduling device or an access network device. The resource scheduling device can be a functional module or entity within the access network device used to implement the resource scheduling method. For example, the access network device can be a base station.

[0041] For example, such as Figure 1 The diagram shown illustrates the process of a resource scheduling method. Figure 1 The method includes, but is not limited to, the following steps:

[0042] 101. Determine the standardized data transmission volume for each type of contracted business based on the resource allocation ratio for each type of contracted business.

[0043] The contracted service type includes at least one NGBR bearer type service. NGBR bearer type typically refers to a network where a specific bit rate is not guaranteed for data transmission, and the transmission rate may vary depending on network resource availability and other factors.

[0044] For example, in mobile communication networks, certain services may be classified as NGBR bearer types, such as some non-real-time data downloads and social media browsing. Contractual services can be the types of services covered in the service contract signed between the user and the service provider; these services may have different quality of service requirements and characteristics.

[0045] The resource allocation ratio for each of the above-mentioned contracted service types can be configured by the access network equipment (such as base stations). For example, the various contracted service types mentioned above may include: 5QI contracted gold, silver, and bronze services. The resource allocation ratio for gold, silver, and bronze services can be 40:20:10.

[0046] In some embodiments, determining the standardized data transmission volume of each subscription type service based on the resource allocation ratio of each subscription type service may include, but is not limited to: obtaining the broadband spectrum efficiency of the client terminal device corresponding to each subscription type service under the current number of streams; and determining the standardized data transmission volume of each subscription type service based on the broadband spectrum efficiency, the resource allocation ratio of each subscription type service, and the first scheduled data volume within a preset time period.

[0047] The aforementioned broadband spectrum efficiency reflects the channel quality of the terminal (i.e., the client terminal equipment). Different terminals will have different spectrum efficiencies due to differences in their location relative to the base station, or due to differences in the terminal's own hardware.

[0048] In the above embodiments, the standardized data transmission volume for each type of subscription service is determined based on the obtained broadband spectrum efficiency, the resource allocation ratio for each subscription service type, and the first scheduled data volume within a preset time period. The resource allocation ratio determines the share of different subscription service types in the total resources, and the first scheduled data volume represents the amount of data already scheduled within the preset time period. By comprehensively considering these factors, the standardized data transmission volume for each subscription service type under specific conditions can be determined more accurately, thereby enabling better resource allocation and service management.

[0049] For example, the process of determining the above-mentioned standardized data transmission volume can be shown in the following formula (1):

[0050] k = (DRC * scale1 * QciScale[qci]) / V (1)

[0051] Where k represents the standardized data transmission volume, DRC represents the broadband spectrum efficiency of the customer terminal device corresponding to the subscription type service under the current number of streams, V represents the first scheduled data volume within the preset time period, QciScale[qci] represents the resource allocation ratio of the subscription type service, and scale1 can be an amplification factor configured by the access network device (such as a base station), which can be called the numerator amplification factor in this application embodiment.

[0052] For each type of contracted business, the standardized data transmission volume can be calculated using the above formula (1).

[0053] In some embodiments, the first scheduling data volume within the preset time period can be the actual scheduling data volume within the preset time period.

[0054] In some embodiments, before determining the standardized data transmission volume of each type of subscription service based on the resource allocation ratio, broadband spectrum efficiency, and current bearer scheduling rate, the current bearer scheduling rate can also be determined based on the second scheduling data volume in the previous preset time period, the scheduling smoothing constant, and the actual scheduling data volume in the preset time period.

[0055] The aforementioned preset time period refers to a time period of preset duration.

[0056] The aforementioned scheduling smoothing constant can be configured by the access network equipment (such as a base station).

[0057] The aforementioned second scheduling data volume within the preset time period reflects the data scheduling situation over a past period. The aforementioned scheduling smoothing constant may be used to adjust the smoothness of data changes and avoid excessive data fluctuations. The actual scheduling data volume within the preset time period represents the specific actual scheduling situation.

[0058] In the above embodiments, by using a scheduling smoothing constant to combine the data scheduling situation over a period of time with the actual amount of scheduled data within a preset time period, the current bearer scheduling rate can be determined more accurately, providing an important basis for subsequently determining the standardized data transmission volume for each type of contracted service.

[0059] For example, the process of determining the current bearer scheduling rate described above can be represented by the following formula (2):

[0060] V = (1- 1 / T)V0 + TBS * scale2 / T (2)

[0061] Wherein, V represents the current bearer scheduling rate, V0 represents the second scheduling data volume in the previous preset time period, T is a scheduling time constant, which can be configured by the base station and can characterize the window size of data statistics, TBS represents the actual scheduling data volume of the resource block in the statistical window, and scale2 can be an amplification factor configured by the access network device (such as the base station), which can be called the denominator amplification factor in this application embodiment.

[0062] 102. Determine the target priority of the target contract type business based on the standardized data transmission volume of the target contract type business and the standardized data transmission volume of each contract type business.

[0063] Among them, the target contract type business is one of the various contract type businesses.

[0064] In some embodiments, the target priority corresponding to the target subscription type service is determined based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service. This may include, but is not limited to: determining the maximum standardized transmission volume and the minimum standardized transmission volume based on the standardized data transmission volume of each subscription type service; and determining the target priority corresponding to the target subscription type service based on the standardized data transmission volume, the maximum standardized transmission volume, and the minimum standardized transmission volume of the target subscription type service.

[0065] First, determine the maximum and minimum standardized data transmission volumes based on the standardized data transmission volumes for each type of contracted service. This step involves identifying the maximum and minimum values ​​among the standardized data transmission volumes for all contracted service types, as they represent the extreme cases of data transmission volume.

[0066] Then, the target priority for the target subscription type service is determined based on its standardized data transmission volume, the determined maximum standardized transmission volume, and the minimum standardized transmission volume. The specific determination method can be based on certain algorithms or rules. For example, the priority can be determined based on the relative position of the target subscription type service's data transmission volume between the maximum and minimum data transmission volumes; the closer the data transmission volume is to the maximum standardized transmission volume, the higher the priority is likely; conversely, the closer it is to the minimum standardized transmission volume, the lower the priority is likely. This operation makes the priority determination of the target subscription type service more scientific and reasonable, taking into account the overall situation of all subscription type services, so as to better allocate and schedule resources.

[0067] In some embodiments, determining the target priority corresponding to the target subscription type service based on the standardized data transmission volume, maximum standardized transmission volume, and minimum standardized transmission volume of the target subscription type service may include, but is not limited to: determining the transmission volume difference range based on the maximum standardized transmission volume and the minimum standardized transmission volume; determining the transmission volume difference based on the standardized data transmission volume and the minimum standardized transmission volume of the target subscription type service; and determining the target priority corresponding to the target subscription type service based on the transmission volume difference and the transmission volume difference range.

[0068] In this embodiment of the application, the standardized transmission volume and the actual transmission volume are inversely correlated.

[0069] First, the range of differences in transmission volume is determined based on the maximum and minimum standardized transmission volumes. This range reflects the variation in standardized data transmission volume for all contracted service types. Since standardized transmission volume and actual transmission volume are inversely correlated, this means that the maximum standardized transmission volume corresponds to the minimum actual transmission volume, and the minimum standardized transmission volume corresponds to the maximum actual transmission volume.

[0070] Then, the difference in transmission volume is determined based on the standardized data transmission volume of the target subscription type service and the minimum standardized transmission volume. This difference reflects the degree of deviation of the target subscription type service from the maximum actual transmission volume, since the minimum standardized transmission volume corresponds to the maximum actual transmission volume.

[0071] Finally, the target priority for the target subscription type service is determined based on the difference in transmission volume and the range of transmission volume differences. For example, the difference in transmission volume can be compared with the range of transmission volume differences. Given the inverse correlation between standardized transmission volume and actual transmission volume, a larger difference indicates that the standardized data transmission volume of the target subscription type service is smaller, while the corresponding actual transmission volume is larger, and it may be assigned a lower priority. Conversely, a smaller difference indicates that the standardized data transmission volume of the target subscription type service is larger, while the corresponding actual transmission volume is smaller, and its priority may be correspondingly higher. This operation, considering the inverse correlation between standardized and actual transmission volume, allows for a more refined and accurate determination of the priority of the target subscription type service, fully reflecting its actual position in the overall data transmission volume distribution.

[0072] For example, the process of determining the target priority corresponding to the target contract type business can be shown in the following formulas (3) and (4):

[0073] PriIndex = 64 – 1 – (k – MinK) / D (3)

[0074] D = (MaxK – MinK) / 64 (4)

[0075] For example, priority data can be maintained. The above formula uses an array size of 64 as an example. The values ​​in the array are priority levels. The priority value of the data content decreases one by one starting from the data index 0. That is, the first value of the array represents the highest priority and the last value of the array represents the lowest priority.

[0076] Here, PriIndex represents the index of the priority array, used to dynamically determine the bearer priority, k represents the standardized data transmission volume of the target subscription type service, MinK represents the minimum standardized transmission volume, and MaxK represents the maximum standardized transmission volume.

[0077] Combining the above formulas (1) to (4), the data transmission volume of the bearer can be standardized according to the weight (i.e., the resource allocation ratio of the contracted service type), which is the k value obtained. After standardization, bearers of different service types or bearers of the same service type from different users can perceive whether their scheduling should be increased or decreased by comparing the k values. For example, when the rate is the same, due to the influence of weight, the k value calculated by the high-weight bearer will be larger than the k value calculated by the low-weight bearer. The D value is calculated based on the highest and lowest k values ​​of all users, so the D value is the same for all users and all bearers. The larger the k value, the smaller the priority index of the final calculation, and the higher the dynamic priority. The final result is that if the rate of the high-weight bearer and the low-weight bearer is the same, the high-weight bearer will dynamically increase the priority, thereby increasing the data transmission volume of the corresponding bearer. When its k value reaches a certain value, a dynamic balance will be reached, ultimately satisfying the purpose of proportional allocation of base station resources.

[0078] 103. Perform resource scheduling for target contract type services based on target priority.

[0079] In this embodiment, after the priority of the bearer is finally calculated, the bearer can be deleted from the original priority queue and inserted into a new priority queue. When base station resources are sufficient, i.e., when there are few users or low traffic, all users can have their services fully scheduled, eliminating the need for priority or proportional allocation issues. This approach can be applied to scenarios where base station resources are insufficient.

[0080] The resource scheduling method described above can standardize the data transmission volume by allocating resources according to the resource allocation ratio of each subscription type service. Based on the standardized data transmission volume of each subscription type service and the standardized data transmission volume of the target subscription type service, the priority of the target subscription type service can be determined. Resource scheduling is then performed on the target subscription type service according to this priority. This achieves resource scheduling based on resource allocation ratio, thereby dynamically determining the priority of the target subscription type service and achieving the purpose of differential resource allocation according to subscription type for different user levels. This avoids users who are only served by low-priority services or users who are served by high-priority services but are at the back of the queue from being unable to receive scheduling for a long time.

[0081] In some embodiments, when flow control is enabled, the priority of a service can be adjusted based on the number of tokens in the token bucket.

[0082] For example, such as Figure 2 The diagram shown illustrates the process of a resource scheduling method. Figure 2 The method includes, but is not limited to, the following steps:

[0083] 201. Obtain the number of tokens in the token bucket corresponding to the target service.

[0084] The target services include: target subscription type services, or GBR bearer type services. The target subscription type services include at least one NGBR bearer type service.

[0085] In this embodiment of the application, different minimum guaranteed rates can be set for heavy load and non-heavy load states.

[0086] In some embodiments, obtaining the number of tokens in the token bucket of the bearer corresponding to the target service includes: obtaining the physical resource block utilization rate; when the physical resource block utilization rate is greater than or equal to the overload threshold, obtaining the minimum guaranteed rate of the bearer corresponding to the target service under overload conditions; and determining the number of tokens in the token bucket of the bearer corresponding to the target service based on the minimum guaranteed rate under overload conditions.

[0087] In some embodiments, under non-overload conditions, the minimum guaranteed rate of the bearer corresponding to the target service under non-overload conditions can be obtained, and the number of tokens in the token bucket of the bearer corresponding to the target service can be determined based on the minimum guaranteed rate under non-overload conditions.

[0088] 202. Determine if the number of tokens is greater than 0.

[0089] 203. When the number of tokens is greater than 0, adjust the first priority of the target business to the second priority;

[0090] Among them, the second priority is higher than the first priority.

[0091] In some embodiments, when the access network device determines that the terminal has the following target conditions, the bearer priority is temporarily raised to the Quality of Service (QoS) layer (a priority higher than all service bearers), and the new user with the temporarily raised priority is inserted at the end of the queue according to the first-in-first-out rule.

[0092] The target situation can include any of the following:

[0093] (1) There is a GBR service and the number of tokens in the GBR token bucket is greater than zero (the minimum guaranteed rate of GBR is not met).

[0094] (2) When the downlink FWA gold, silver and copper features are turned off, there is an NGBR service in the target service and the number of tokens in the MinBR token bucket is greater than zero (the minimum guaranteed rate of NGBR is not met).

[0095] For example, taking the above-mentioned contract types of services, including Gold, Silver and Bronze services, as an example, the above-mentioned downlink FWA Gold, Silver and Bronze feature shutdown means that the function related to the features of each contract type of service is not enabled. When this function is not enabled, the priority of Gold service is not considered to be higher than that of Silver service, and the priority of Silver service is not considered to be higher than that of Bronze service.

[0096] (3) When the downlink FWA gold, silver and copper features are enabled, there is an NGBR service in the target service, and the service type is gold service, and the number of MinBR tokens is greater than zero (the minimum guaranteed rate of NGBR is not met).

[0097] The aforementioned enabling of FWA Gold, Silver, and Bronze features refers to activating functions related to the features of various contract types. When this function is enabled, the priority of Gold services is considered to be higher than that of Silver services, and the priority of Silver services is higher than that of Bronze services.

[0098] In some embodiments, when the downlink FWA gold, silver and bronze features are enabled, there is an NGBR service, and the service type is silver, and the number of MinBR tokens is greater than zero (not meeting the minimum guaranteed rate of NGBR), then the bearer priority is temporarily raised to the next layer below the QoS layer, and according to the first-in-first-out rule, the new user with the temporarily increased priority is inserted at the end of the queue.

[0099] Among them, the next layer below the QoS layer is a priority that is higher than all service bearers but lower than the QoS layer, that is, lower than the priority temporarily increased by the gold service.

[0100] In some embodiments, when the downlink FWA gold, silver and bronze features are enabled, there is an NGBR service, and the service type is bronze, and the number of MinBR tokens is greater than zero (not meeting the minimum guaranteed rate of NGBR), then the bearer priority is temporarily raised to the two layers below the QoS layer, and according to the first-in-first-out rule, the new user with the temporarily increased priority is inserted at the end of the queue.

[0101] Among them, the two layers below the QoS layer have a priority that is higher than all service bearers but lower than the QoS layer itself, that is, lower than the temporary priority increase for gold and silver services.

[0102] According to the above embodiments, based on the original temporary priority increase, when the base station enables the FWA gold, silver and bronze features, the temporary priority increase of NGBR services is subdivided into three layers, which can better guarantee the scheduling frequency of high-subscription level users.

[0103] In this embodiment of the application, for NGBR services, when the FWA gold-silver-copper feature is enabled, the minimum bit rate of NGBR under FWA overload configuration is not invalid, and the cell enters the overload state, the token count is dynamically replaced with the token count corresponding to the minimum bit rate of Minbr under FWA overload when updating the token count of the token bucket corresponding to the bearer every millisecond. When the cell exits the overload state, the token count is restored to the previous minimum bit rate of Minbr when updating the token count of the token bucket every millisecond.

[0104] The cell downlink PRB utilization rate used to determine the overload state is calculated using the second-level cell downlink physical PRB utilization rate, which is expressed as the total downlink first-layer PRB occupancy within one second divided by the total downlink full-bandwidth PRB resources within one second. For multi-user (MU) scenarios, only the total first-layer PRB occupancy is included in the statistics. In communication systems, multi-user scenarios may involve resource sharing and allocation. For these users, when calculating the cell downlink PRB utilization rate, only the first-layer PRB occupancy is included in the numerator to evaluate and handle resource usage in a specific way.

[0105] For example, such as Figure 3 The diagram shown illustrates the process of a resource scheduling method. Figure 2 This method can be applied to base stations, including but not limited to the following steps:

[0106] 301. Messages are received cyclically through the downlink scheduling process.

[0107] In a base station, the downlink scheduling process is constantly receiving various messages in preparation for subsequent scheduling operations. It may receive information from different modules or devices to understand the current status and requirements of the system.

[0108] 302. Confirm that a timer interrupt has been received from the driver.

[0109] The type of received messages can be determined. When a timed scheduling interrupt is received from the driver, it indicates that the scheduling opportunity has arrived. Timed scheduling interrupts ensure that scheduling operations are performed at regular time intervals, thereby guaranteeing the timeliness of system resource allocation and data transmission.

[0110] 303. Process the data from RLC and update the priority list.

[0111] This process involves handling data transmitted from the Radio Link Control (RLC) layer. When data arrives on a bearer from zero, the bearer is inserted into a priority queue for subsequent resource allocation; when data disappears from a bearer, the bearer is removed from the priority queue to maintain its accuracy and effectiveness.

[0112] 304. Use a for loop to sort the priority queue from high to low to determine the order of user resource allocation.

[0113] Specifically, the priority queue is traversed in descending order of priority to arrange users in the order of resource allocation. This ensures that high-priority users receive resource allocation first, improving the system's resource utilization efficiency and service quality.

[0114] 305. Allocate resources according to the queuing order and notify the RLC to assemble the package.

[0115] This allows for resource allocation to users based on their queuing order, while simultaneously notifying the RLC layer to perform data packet assembly operations, enabling efficient data transmission and processing.

[0116] 306. Update the harq information, temporarily reduce the priority, and use the round-robin scheduling algorithm to update the priority queue to carry the queuing order.

[0117] Update the Hybrid Automatic Repeat Request (HAQ) information to ensure reliable data transmission. Simultaneously, revert any temporarily increased priority to its original state and update the queuing order in the priority queue using a round-robin scheduling algorithm to guarantee fairness and rational resource allocation.

[0118] 307. Determine if the time interval is 1ms.

[0119] Determine if the current time interval has reached 1 ms. If the time interval is 1 ms, update the token count in the token bucket, i.e., execute step 308 below; if the time interval is less than 1 ms, return to execute step 301 above.

[0120] 308. Update the token count in the token bucket.

[0121] The token count in the token bucket is updated based on the system's resource allocation and business needs. The token bucket is used to control resource allocation and business scheduling; updating the token count ensures the rational utilization of resources and fair scheduling of services. For example, the token count in the token bucket can be determined based on the method described in step 201 above.

[0122] 309. Dynamically update the carrying priority.

[0123] The priority of the service bearer is dynamically updated based on the system's status and business needs. This can be determined based on factors such as the resource allocation ratio for each type of contracted service and the standardized data transmission volume, to achieve optimized resource allocation and efficient service scheduling. For example, it can be based on the above... Figure 1 The method shown dynamically updates the bearer priority.

[0124] 310. Determine whether to temporarily prioritize the bearer.

[0125] Based on the system's status and business requirements, determine whether to temporarily increase the bearer's priority. For example, in certain situations, when a service fails to meet the minimum guaranteed rate, the bearer's priority can be temporarily increased to ensure smooth service operation. For example, this can be done according to the above... Figure 2 Steps 202 and 203 in the method shown correspond to the method in the description, determining whether to temporarily elevate the priority of the bearer.

[0126] 311. Calculate PRB utilization rate.

[0127] The above calculation of Physical Resource Block (PRB) utilization provides insight into base station resource usage. PRB utilization can be calculated by dividing the total downlink Layer 1 PRB occupancy within 1 second by the total downlink full-bandwidth PRB resources within 1 second. For multi-user (MU) scenarios, only the total Layer 1 PRB occupancy is included in the statistics, allowing for a specific method of evaluating and processing resource usage.

[0128] After completing step 311 above, you can return to step 301 above and continue to execute the method in a loop.

[0129] Table 1 is a schematic table of bearer priorities provided in one embodiment of this application. The bearer priorities involved in the embodiments of this application can be as shown in Table 1.

[0130] Table 1

[0131]

[0132] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0133] Based on the same technical concept, this application also provides an access network device. This access network device can implement the functions of the base station or access network device described in the foregoing embodiments.

[0134] For example, Figure 4This is a schematic diagram of the structure of an access network device according to one embodiment. The access network device includes: a memory 401, a transceiver 402, and a processor 403, wherein the memory 401, transceiver 402, and processor 403 are connected via a bus interface.

[0135] The memory 401 is used to store computer programs; the transceiver 402 is used to send and receive data under the control of the processor 403.

[0136] The processor 403 described above is used to read the computer program in the memory 401 and perform the following operations:

[0137] In some embodiments, the standardized data transmission volume of each subscription type service is determined according to the resource allocation ratio of each subscription type service, wherein the subscription type service includes at least one NGBR bearer type service;

[0138] Based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service, the target priority corresponding to the target subscription type service is determined, and the target subscription type service is one of the various subscription type services;

[0139] Resource scheduling is performed on the target contract type services based on the target priority.

[0140] In some embodiments, determining the standardized data transmission volume for each subscription type service based on the resource allocation ratio for each subscription type service includes:

[0141] Obtain the broadband spectrum efficiency of the customer terminal device corresponding to each of the contracted service types under the current number of streams;

[0142] Based on the broadband spectrum efficiency, the resource allocation ratio of each type of subscription service, and the first scheduled data volume within a preset time period, the standardized data transmission volume of each type of subscription service is determined.

[0143] In some embodiments, before determining the standardized data transmission volume of each subscription type service based on the resource allocation ratio of each subscription type service, the broadband spectrum efficiency, and the current bearer scheduling rate, the method further includes:

[0144] The current load scheduling rate is determined based on the second scheduling data volume in the previous preset time period, the scheduling smoothing constant, and the actual scheduling data volume in the preset time period.

[0145] In some embodiments, determining the target priority corresponding to the target subscription type service based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service includes:

[0146] Based on the standardized data transmission volume of each contracted business type, determine the maximum and minimum standardized transmission volumes;

[0147] The target priority corresponding to the target subscription type service is determined based on the standardized data transmission volume of the target subscription type service, the maximum standardized transmission volume, and the minimum standardized transmission volume.

[0148] In some embodiments, determining the target priority corresponding to the target subscription type service based on the standardized data transmission volume of the target subscription type service, the maximum standardized transmission volume, and the minimum standardized transmission volume includes:

[0149] The range of transmission volume difference is determined based on the maximum standardized transmission volume and the minimum standardized transmission volume;

[0150] The difference in transmission volume is determined based on the standardized data transmission volume and the minimum standardized transmission volume of the target contract type business;

[0151] Based on the difference in transmission volume and the range of transmission volume differences, the target priority corresponding to the target subscription type service is determined.

[0152] In some embodiments, the method further includes: obtaining the number of tokens in the token bucket of the bearer corresponding to the target service, wherein the target service includes: the target subscription type service, or, a GBR bearer type service;

[0153] When the number of tokens is greater than 0, the first priority corresponding to the target service is adjusted to the second priority;

[0154] The second priority is higher than the first priority.

[0155] In some embodiments, obtaining the number of tokens in the token bucket corresponding to the target service includes:

[0156] Obtain physical resource block utilization;

[0157] When the utilization rate of the physical resource block is greater than or equal to the overload threshold, obtain the minimum guaranteed rate of the bearer corresponding to the target service under the overload state;

[0158] Based on the minimum guaranteed rate under the heavy load state, the number of tokens in the token bucket corresponding to the target service is determined.

[0159] In one exemplary embodiment, such as Figure 5 As shown, a structural block diagram of a resource scheduling device is provided, including:

[0160] The transmission volume determination module 501 is used to determine the standardized data transmission volume of each subscription type service according to the resource allocation ratio of each subscription type service, wherein the subscription type service includes at least one NGBR bearer type service.

[0161] The priority determination module 502 is used to determine the target priority corresponding to the target subscription type service based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service, wherein the target subscription type service is one of the various subscription type services;

[0162] The resource scheduling module 503 is used to perform resource scheduling for the target subscription type service based on the target priority.

[0163] In some embodiments, the transmission volume determination module 501 is specifically used for:

[0164] Obtain the broadband spectrum efficiency of the customer terminal device corresponding to each of the contracted service types under the current number of streams;

[0165] Based on the broadband spectrum efficiency, the resource allocation ratio of each type of subscription service, and the first scheduled data volume within a preset time period, the standardized data transmission volume of each type of subscription service is determined.

[0166] In some embodiments, the resource scheduling device further includes: a rate determination module 504, configured to:

[0167] Before the transmission volume determination module 501 determines the standardized data transmission volume of each subscription type service based on the resource allocation ratio of each subscription type service, the broadband spectrum efficiency, and the current bearer scheduling rate, the current bearer scheduling rate is determined based on the second scheduling data volume in the previous preset time period, the scheduling smoothing constant, and the actual scheduling data volume in the preset time period.

[0168] In some embodiments, the priority determination module 502 is specifically used for:

[0169] Based on the standardized data transmission volume of each contracted business type, determine the maximum and minimum standardized transmission volumes;

[0170] The target priority corresponding to the target subscription type service is determined based on the standardized data transmission volume of the target subscription type service, the maximum standardized transmission volume, and the minimum standardized transmission volume.

[0171] In some embodiments, the priority determination module 502 is specifically used to: determine the range of transmission volume difference based on the maximum standardized transmission volume and the minimum standardized transmission volume;

[0172] The difference in transmission volume is determined based on the standardized data transmission volume and the minimum standardized transmission volume of the target contract type business;

[0173] Based on the difference in transmission volume and the range of transmission volume differences, the target priority corresponding to the target subscription type service is determined.

[0174] In some embodiments, the resource scheduling device further includes: a priority adjustment module 505, configured to:

[0175] Obtain the number of tokens in the token bucket corresponding to the target service, wherein the target service includes: the target subscription type service, or, a GBR bearer type service;

[0176] When the number of tokens is greater than 0, the first priority corresponding to the target service is adjusted to the second priority;

[0177] The second priority is higher than the first priority.

[0178] In some embodiments, the priority adjustment module 505 is specifically used for:

[0179] Obtain physical resource block utilization;

[0180] When the utilization rate of the physical resource block is greater than or equal to the overload threshold, obtain the minimum guaranteed rate of the bearer corresponding to the target service under the overload state;

[0181] Based on the minimum guaranteed rate under the heavy load state, the number of tokens in the token bucket corresponding to the target service is determined.

[0182] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0183] If the integrated modules described above are implemented as software functional modules and sold or used as independent products, they can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application.

[0184] It should be noted that the apparatus provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0185] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements all the method steps implemented in the above method embodiments.

[0186] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements all the method steps implemented in the above method embodiments.

[0187] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0188] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0189] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A resource scheduling method, characterized in that, The method includes: Based on the resource allocation ratio of each type of contracted service, the standardized data transmission volume of each type of contracted service is determined, wherein the contracted service includes at least one NGBR bearer type service. Based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service, the target priority corresponding to the target subscription type service is determined, and the target subscription type service is one of the various subscription type services; Resource scheduling is performed on the target contract type services based on the target priority.

2. The method according to claim 1, characterized in that, The step of determining the standardized data transmission volume for each contract type service based on the resource allocation ratio for each contract type service includes: Obtain the broadband spectrum efficiency of the customer terminal device corresponding to each of the contracted service types under the current number of streams; Based on the broadband spectrum efficiency, the resource allocation ratio of each type of subscription service, and the first scheduled data volume within a preset time period, the standardized data transmission volume of each type of subscription service is determined.

3. The method according to claim 2, characterized in that, Before determining the standardized data transmission volume of each subscription type service based on the resource allocation ratio of each subscription type service, the broadband spectrum efficiency, and the current bearer scheduling rate, the method further includes: The current load scheduling rate is determined based on the second scheduling data volume in the previous preset time period, the scheduling smoothing constant, and the actual scheduling data volume in the preset time period.

4. The method according to claim 2, characterized in that, The step of determining the target priority corresponding to the target subscription type service based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service includes: Based on the standardized data transmission volume of each contracted business type, determine the maximum and minimum standardized transmission volumes; The target priority corresponding to the target subscription type service is determined based on the standardized data transmission volume of the target subscription type service, the maximum standardized transmission volume, and the minimum standardized transmission volume.

5. The method according to claim 4, characterized in that, The step of determining the target priority corresponding to the target subscription type service based on the standardized data transmission volume of the target subscription type service, the maximum standardized transmission volume, and the minimum standardized transmission volume includes: The range of transmission volume difference is determined based on the maximum standardized transmission volume and the minimum standardized transmission volume; The difference in transmission volume is determined based on the standardized data transmission volume and the minimum standardized transmission volume of the target contract type business; Based on the difference in transmission volume and the range of transmission volume differences, the target priority corresponding to the target subscription type service is determined.

6. The method according to claim 1, characterized in that, The method further includes: Obtain the number of tokens in the token bucket corresponding to the target service, wherein the target service includes: the target subscription type service, or, a GBR bearer type service; When the number of tokens is greater than 0, the first priority corresponding to the target service is adjusted to the second priority; The second priority is higher than the first priority.

7. The method according to claim 6, characterized in that, The step of obtaining the number of tokens in the token bucket corresponding to the target service includes: Obtain physical resource block utilization; When the utilization rate of the physical resource block is greater than or equal to the overload threshold, obtain the minimum guaranteed rate of the bearer corresponding to the target service under the overload state; Based on the minimum guaranteed rate under the heavy load state, the number of tokens in the token bucket corresponding to the target service is determined.

8. An access network device, characterized in that, include: Memory, transceiver, processor: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Based on the resource allocation ratio of each type of contracted service, the standardized data transmission volume of each type of contracted service is determined, wherein the contracted service includes at least one NGBR bearer type service. Based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service, the target priority corresponding to the target subscription type service is determined, and the target subscription type service is one of the various subscription type services; Resource scheduling is performed on the target contract type services based on the target priority.

9. A resource scheduling device, characterized in that, include: The transmission volume determination module is used to determine the standardized data transmission volume of each subscription type service based on the resource allocation ratio of each subscription type service, wherein the subscription type service includes at least one NGBR bearer type service. The priority determination module is used to determine the target priority corresponding to the target subscription type service based on the standardized data transmission volume of the target subscription type service and the standardized data transmission volume of each subscription type service, wherein the target subscription type service is one of the various subscription type services; The resource scheduling module is used to schedule resources for the target subscription type service based on the target priority.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 7.

Images