CN113630799A

CN113630799A - Traffic scheduling method and device and computing equipment

Info

Publication number: CN113630799A
Application number: CN202010382138.8A
Authority: CN
Inventors: 阮一荻
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Group Zhejiang Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Group Zhejiang Co Ltd
Priority date: 2020-05-08
Filing date: 2020-05-08
Publication date: 2021-11-09
Anticipated expiration: 2040-05-08
Also published as: CN113630799B

Abstract

The embodiment of the invention relates to the technical field of network operation and maintenance, and discloses a traffic scheduling method, a traffic scheduling device and computing equipment. The method comprises the following steps: when alarm information appears in a core network element group, acquiring information of each SAE gateway connected with the core network element group; acquiring the capacity of each SAE gateway and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs, and calculating the ratio of the current weight to the capacity of each SAE gateway; taking the minimum value in the ratio of the current weight to the capacity of each SAE gateway as a reference value; calculating the initial adjustment weight of each SAE gateway according to the reference value and the capacity of each SAE gateway; and carrying out traffic scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway. Through the mode, the embodiment of the invention can automatically carry out flow scheduling and improve the accuracy of scheduling.

Description

Traffic scheduling method and device and computing equipment

Technical Field

The embodiment of the invention relates to the technical field of network operation and maintenance, in particular to a traffic scheduling method, a traffic scheduling device and computing equipment.

Background

As the demand on the network increases, the utilization of network devices remains at a high level. In order to maintain network stability, when a network device fails or traffic volume suddenly increases, traffic scheduling is required, so that traffic is reasonably distributed.

Due to the complex network structure, the traffic is shared to some devices with lower utilization rate by generally manually adjusting the weight of a System Architecture Evolution (SAE) gateway, but this scheduling method cannot obtain an accurate result.

Disclosure of Invention

In view of the foregoing problems, embodiments of the present invention provide a traffic scheduling method, a traffic scheduling apparatus, and a computing device, which can automatically perform traffic scheduling and improve the accuracy of the scheduling.

According to a first aspect of the embodiments of the present invention, a traffic scheduling method is provided, including: when alarm information appears in a core network element group, acquiring information of each SAE gateway connected with the core network element group; acquiring the capacity of each SAE gateway and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs, and calculating the ratio of the current weight to the capacity of each SAE gateway; taking the minimum value in the ratio of the current weight to the capacity of each SAE gateway as a reference value; calculating the initial adjustment weight of each SAE gateway according to the reference value and the capacity of each SAE gateway; and carrying out traffic scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway.

In an optional manner, after the performing traffic scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway, the method further includes: judging whether the alarm information appears in the core network element group; if alarm information appears, acquiring a preset weight adjustment step length, and adjusting the initial adjustment weight according to the preset weight adjustment step length; carrying out flow scheduling on each SAE gateway according to the adjusted initial adjustment weight; setting the adjusted initial adjustment weight as an initial adjustment weight; and continuing to execute the step of judging whether the alarm information appears in the core network element group or not, and carrying out flow scheduling on each SAE gateway.

In an optional manner, before the obtaining information of each SAE gateway connected to the core network element group when the core network element group has the alarm information, the method further includes: acquiring total throughput of the whole network; calculating the current flow of each SAE gateway according to the total throughput of the whole network and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs; and generating the alarm information according to the current flow of each SAE gateway and the topological relation of the core network element group.

In an optional manner, the generating the alarm information according to the current traffic of each SAE gateway and the topological relation of the core network element group specifically includes: acquiring the traffic information of each network element in the core network element group according to the current traffic of each SAE gateway and the topological relation of the core network element group; calculating the traffic utilization rate of the network element according to the traffic information; and when the traffic utilization rate of the network element exceeds a preset traffic utilization rate threshold, generating the alarm information.

In an optional manner, the generating the alarm information according to the current traffic of each SAE gateway and the topological relation of the core network element group specifically includes: acquiring bandwidth information of links among network elements in the core network element group according to the current flow of each SAE gateway and the topological relation of the core network element group; calculating the bandwidth utilization rate of the link according to the bandwidth information; and when the bandwidth utilization rate of the link exceeds a preset bandwidth utilization rate threshold value, generating the alarm information.

In an optional manner, the method further comprises: and displaying the topological relation of the core network element group and the alarm information.

In an optional manner, before the obtaining the capacity of each SAE gateway and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs, and calculating the ratio of the capacity of each SAE gateway to the current weight, the method further includes: acquiring a fault network element identifier; determining a core network element group with a fault according to the fault network element identifier; and setting the current weight of the SAE gateway connected with the core network element group with the fault in the SAE gateway pool to zero.

According to a second aspect of the embodiments of the present invention, there is provided a traffic scheduling apparatus, including: an SAE gateway acquisition module, configured to acquire, when an alarm message occurs in a core network element group, information of each SAE gateway connected to the core network element group; an initial adjustment weight calculation module, configured to obtain the capacity of each SAE gateway and the current weight of each SAE gateway in an SAE gateway pool to which the SAE gateway belongs, calculate a ratio between the capacity of each SAE gateway and the current weight, use a minimum value of the ratios between the capacity of each SAE gateway and the current weight as a reference value, and calculate an initial adjustment weight of each SAE gateway according to the reference value and the capacity of each SAE gateway; and the flow scheduling module is used for carrying out flow scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway.

According to a third aspect of embodiments of the present invention, there is provided a computing device comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus; the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation of the traffic scheduling method.

According to a fourth aspect of the embodiments of the present invention, there is provided a computer-readable storage medium, where at least one executable instruction is stored, and when the executable instruction is executed on a computing device, the computing device is caused to execute the traffic scheduling method described above.

In the embodiment of the invention, when alarm information appears in a core network element group, the information of each SAE gateway connected with the core network element group is acquired, the capacity of each SAE gateway and the current weight of each SAE gateway in an SAE gateway pool to which the SAE gateway belongs are acquired, the ratio of the current weight to the capacity of each SAE gateway is calculated, the minimum value of the ratio of the current weight to the capacity of each SAE gateway is taken as a reference value, the initial adjustment weight of each SAE gateway is calculated according to the reference value and the capacity of each SAE gateway, and the traffic scheduling is carried out on each SAE gateway according to the initial adjustment weight of each SAE gateway, so that the weight of the SAE gateway can be automatically calculated, thereby automatically carrying out the traffic scheduling and improving the scheduling accuracy.

The foregoing description is only an overview of the technical solutions of the embodiments of the present invention, and the embodiments of the present invention can be implemented according to the content of the description in order to make the technical means of the embodiments of the present invention more clearly understood, and the detailed description of the present invention is provided below in order to make the foregoing and other objects, features, and advantages of the embodiments of the present invention more clearly understandable.

Drawings

The drawings are only for purposes of illustrating embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a schematic diagram illustrating an application scenario of a traffic scheduling method according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating a traffic scheduling method according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a traffic scheduling method according to another embodiment of the present invention;

fig. 4 is a flowchart illustrating a traffic scheduling method according to another embodiment of the present invention;

fig. 5 is a flowchart illustrating a traffic scheduling method according to another embodiment of the present invention;

fig. 6 is a schematic structural diagram illustrating a traffic scheduling apparatus according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a computing device provided by an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein.

The inventor analyzes the prior art and discovers that, at present, the flow is shared to some devices with lower utilization rate generally by manually adjusting the weight of a System Architecture Evolution (SAE) gateway, but this scheduling method cannot obtain an accurate adjustment value through manual estimation, and there are many paths connected between devices in the network, adjusting the weight of the SAE gateway affects all devices related to the SAE gateway, and the final effect of the whole network after scheduling cannot be known, so that an accurate result cannot be obtained.

Based on this, the embodiment of the invention provides a traffic scheduling method, a traffic scheduling device and a computing device, which can automatically perform traffic scheduling and improve the accuracy of the scheduling.

Fig. 1 is a schematic diagram illustrating an application scenario of a traffic scheduling method according to an embodiment of the present invention. The traffic scheduling method is applied to a Long Term Evolution (LTE) system. As shown in fig. 1, the application scenario includes a base station 11 and an Evolved Packet Core (EPC) 12.

The base station 11 is an Evolved Node B (eNB). The base station 11 is responsible for radio access function and ground interface function of E-UTRAN, including implementing radio bearer control, radio admission control, connection mobility control, etc.; finishing the allocation (scheduling) of uplink and downlink terminal dynamic resources; IP header compression and user data stream encryption; selecting a Mobility Management Entity (MME) when the terminal is attached; scheduling transmission of paging and broadcast messages initiated by the MME; measurements and measurement reports etc. are done regarding mobility configuration and scheduling. User Equipment (UE) can directly access the base station 11 and then connect to the network through the EPC 12 to obtain a corresponding service. Alternatively, the UE may be a smartphone, a multimedia device, a streaming media device, and so on.

The EPC 12 is used to provide a channel to external networks (e.g., CMNET, internet, corporate local area network, etc.) and operator services (e.g., multimedia message, multimedia broadcast and multicast service, etc.), and supports mobile handover between various access technologies (e.g., EDGE, WCDMA, LTE, WLAN, CDMA2000, etc.).

In which, the control plane and the user plane of the EPC 12 are completely separated, and the network architecture tends to be flat. Specifically, EPC 12 includes SAE gateway 121 and core network element group 122. SAE gateway 121 and core network element group 122 are both user plane nodes of EPC 12. The EPC 12 also includes a Mobility Management Entity (MME). The MME is a control plane node of the EPC 12.

Among other things, SAE gateway 121 may communicate with base station 11 over an S1 interface. SAE gateway 121 may also communicate with a core network element group 122. The number of SAE gateways 121 may be multiple, multiple SAE gateways 121 may form an SAE gateway pool, and the traffic borne on each SAE gateway 121 in the SAE gateway pool is controlled by the weight configured in the configuration file in the DNS. A plurality of SAE gateways 121 may be connected to the same core network element group 122 at the same time, and several SAE gateways 121 connected to the same core network element group 122 at the same time may become one SAE gateway group. In particular, SAE Gateway 121 may include a serving Gateway (S-GW) and/or a Packet data network Gateway (P-GW). The S-GW is responsible for the transmission, forwarding, and route switching of UE user plane data, and also serves as a mobility anchor of the user plane during mutual transfer between enodebs, and as a mobility anchor of LTE and other 3GPP technologies, and is also responsible for accessing the base station 11 to provide services for the mobility of LTE access users. The P-GW is used to manage the connection between the UE and the external packet data network. One UE can be synchronously connected with multiple P-GWs of multiple PDNs. In this embodiment, SAE gateway 121 may include an S-GW and a P-GW for example. Of course, in some other embodiments, the SAE gateway 121 may also be composed of only an S-GW, or only a P-GW, and both the SAE gateway 121 composed of only an S-GW and the SAE gateway 121 composed of only a P-GW are connected to the core network element group 122.

The core network element group 122 may include a Switch (Switch, SW) and/or a firewall (Fire Wall, FW) disposed between the SAE gateway 121 and an external network, among others. Specifically, the core network element group 122 may include an access SW 1221, an LTE FW 1222, an LTE SW 1223, a Gn FW 1224, and a convergence SW 1225. Access SW 1221 communicates with LTE FW 1222, LTE FW 1222 communicates with LTE SW 1223, LTE SW 1223 communicates with SW of external networks, LTE SW 1223 also communicates with Gn FW 1224, Gn FW 1224 communicates with aggregation SW 1225, aggregation SW 1225 communicates with access SW 1221. Of course, in some other embodiments, the core network element group 122 may further include more or fewer devices than those in fig. 1, and may be specifically set according to an actual network situation.

Of course, the method provided in the embodiment of the present invention is not limited to be used in the application scenario shown in fig. 1, and may also be used in other possible application scenarios, which is not limited in the embodiment of the present invention. The functions that can be implemented by each device in the application scenario shown in fig. 1 will be described in the following method embodiments, and will not be described in detail herein.

Specifically, the embodiments of the present invention will be further explained below with reference to the drawings.

It should be understood that the following examples are provided by way of illustration and are not intended to limit the invention in any way to the particular embodiment disclosed.

Fig. 2 is a flowchart illustrating a traffic scheduling method according to an embodiment of the present invention. The method may be applied to the application scenario as shown in fig. 1, e.g. may be performed at a base station. As shown in fig. 2, the method includes:

step 210, when the core network element group has alarm information, obtaining each SAE gateway information connected with the core network element group.

In an LTE system, an SAE gateway pool composed of a plurality of SAE gateways is connected with a plurality of core network element groups, alarm information may occur in one or more core network element groups, and when the alarm information occurs in one or more core network element groups, the information of the SAE gateway connected with the core network element groups is acquired for all the core network element groups. Wherein, a plurality of SAE gateways which are simultaneously connected with the same core network element group are marked as an SAE gateway group. For example, as shown in fig. 1, it is assumed that an LTE system includes three core network element groups of a1, a2, and A3 and an SAE gateway pool including four SAE gateways of B1, B2, B3, and B4, B1 and B2 are connected to a1, B3 is connected to a2, and B4 is connected to A3, and when alarm information occurs in a1 and a2, information of B1 and B2 connected to a1 and information of B3 connected to a2 are acquired.

The SAE gateway information may include, among other things, address information of the SAE gateway.

Step 220, obtaining the capacity of each SAE gateway and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs, and calculating the ratio of the current weight and the capacity of each SAE gateway.

The SAE gateway pool is provided with the weight of each SAE gateway, so that the weight of each SAE gateway in the SAE gateway group in the SAE gateway pool to which the SAE gateway belongs can be obtained through the configuration parameters of the SAE gateway pool, and the SAE gateway capacity can be obtained by inputting the configuration parameters of the SAE gateway in advance as the current weight.

Wherein, calculating the ratio of the current weight and the capacity of the SAE gateway may be: the current weight of the SAE gateway is divided by the capacity of the SAE gateway.

And step 230, taking the minimum value of the ratio of the current weight to the capacity of each SAE gateway as a reference value.

The ratio of the current weight and the capacity of all SAE gateways in the same SAE gateway group is compared, the minimum value of the ratio is determined, and the minimum value is used as a reference value. For example, assuming that SAE gateways B1, B2 are connected to core network element group a1 (i.e. SAE gateways B1, B2 are the same SAE gateway group), the current weight and capacity ratios of SAE gateways B1, B2 are 20%/c 1, 50%/c 2, respectively, 20%/c 1 and 50%/c 2 are compared, and if 20%/c 1 is determined to be the smallest, 20%/c 1 is used as the reference value.

And step 240, calculating the initial adjustment weight of each SAE gateway according to the reference value and the capacity of each SAE gateway.

Specifically, the reference value is multiplied by the capacity of other SAE gateways to obtain the initial adjustment weights of other SAE gateways. For example, SAE gateways B1 and B2 are connected to core network element group a1, the current weight and capacity ratios of SAE gateways B1 and B2 are 20%/c 1 and 50%/c 2, respectively, and the reference value is determined to be 20%/c 1, then the initial adjustment weight of B1 is 20%/c 1, and the initial adjustment weight of B2 is c2 × 20%/c 1.

And step 250, carrying out flow scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway.

Wherein, the traffic scheduling is performed on each SAE gateway according to the initial adjustment weight of each SAE gateway, which may specifically be: and in the same SAE gateway group, carrying out flow scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway, and finishing the flow scheduling of the SAE gateway group connected with the core network element group if the alarm information appearing in the core network element group disappears.

The priority of the SAE gateway group traffic scheduling can be determined according to the number of the alarm messages, and if the number of the alarm messages is larger, the priority of the SAE gateway group traffic scheduling is higher. For example, assuming that an LTE system includes three core network element groups of a1, a2, and A3 and an SAE gateway pool including four SAE gateways of B1, B2, B3, and B4, B1 and B2 are connected to a1, B3 is connected to a2, B4 is connected to A3, the number of alarm information appearing in a1 is 3, and the number of alarm information appearing in a2 is 1, an initial adjustment weight is calculated for B1 and B2 connected to a1, and traffic scheduling is performed, and then an initial adjustment weight is calculated for B3 connected to a2, and traffic scheduling is performed. Of course, in some other implementations, the priority of SAE gateway group traffic scheduling may also be determined according to the urgency of the alert message, and if the urgency of the alert message is higher, the priority of SAE gateway group traffic scheduling is higher.

In some embodiments, after performing traffic scheduling on the SAE gateway group connected to the core network element group in which the alarm message appears according to the initial adjustment weight of each SAE gateway, the number of the alarm message may be reduced, but the alarm message does not disappear completely, and then the traffic scheduling still needs to be performed. As shown in fig. 3, after step 250, the method further comprises:

step 261, judging whether the alarm information appears in the core network element group;

step 262, if the alarm information appears, obtaining a preset weight adjustment step length, and adjusting the initial adjustment weight according to the preset weight adjustment step length.

The preset weight adjustment step length may be preset according to an actual situation, for example, if the adjustment time is expected to be short, a larger preset weight adjustment step length may be set. Alternatively, the preset weight adjustment step size may be 2.

The initial adjustment weight is adjusted according to the preset weight adjustment step length, which may specifically be: and subtracting the preset weight adjustment step length from the initial adjustment weight to obtain the adjusted initial adjustment weight. For example, assuming that the preset weight adjustment step size is 2, in one SAE gateway group, the initial adjustment weight of SAE gateway B1 is 20%/B1, and the initial adjustment weight of SAE gateway B2 is B2 × 20%/B1, then the initial adjustment weights after adjustment by SAE gateways B1 and B2 are 20%/B1-2 and B2 × 20%/B1-2, respectively.

And 263, performing traffic scheduling on each SAE gateway according to the adjusted initial adjustment weight.

In the same SAE gateway group, flow scheduling is carried out on each SAE gateway according to the adjusted initial adjustment weight of each SAE gateway, so that the alarm information is reduced.

Step 264, setting the adjusted initial adjustment weight as the initial adjustment weight.

Step 265, continuing to execute the above step of judging whether the alarm information appears in the core network element group, and performing traffic scheduling on each SAE gateway.

Specifically, after the adjusted initial adjustment weight is used as the initial adjustment weight, step 261 is continuously executed to perform traffic scheduling for each SAE gateway. If the alarm information still appears in the network element group of the core network after the step 261 is executed, the steps 262 to 265 are continuously executed circularly.

Wherein, the stop condition of the circulation can be: the core network element group does not have the alarm information any more, and the alarm information added for other core network element groups can be provided, or the emergency degree of the alarm information provided for other core network element groups can be increased, and the like. For example, after step 261 is executed, if the alarm information does not appear in the network element group of the core network, the traffic scheduling is completed.

In some embodiments, prior to step 220, the method further comprises:

step 271, acquiring a fault network element identifier.

The failed network element identifier may be a name or an address of the failed network element, or the like.

And 272, determining the core network element group with the fault according to the fault network element identifier.

And determining a core network element group where the failed network element is located according to the failed network element, namely the core network element group with the failure. For example, as shown in fig. 1, assuming that an access SW in the core network element group a2 fails, a2 is a core network element group in which a failure exists.

Step 273, setting the current weight of the SAE gateway connected to the failed core network element group in the SAE gateway pool to zero.

When a certain network element in the core network element group fails, the whole core network element group cannot be used, the current weight of the SAE gateway connected with the core network element group in the SAE gateway pool to which the SAE gateway belongs is set to be zero, and then the calculation of the initial adjustment weights of other SAE gateways is carried out.

In this embodiment, by setting the current weight of the SAE gateway connected to the core network element group with the failure in the SAE gateway pool to zero, traffic scheduling can be performed in the scenario of the failed network element.

Fig. 4 is a flowchart illustrating a traffic scheduling method according to another embodiment of the present invention. The method may be applied to the application scenario as shown in fig. 1, e.g. may be performed at a base station. The difference from the above embodiment is that before step 210, as shown in fig. 4, the method further includes:

and step 310, acquiring the total throughput of the whole network.

Where the total network throughput refers to the total traffic throughput input to one SAE gateway pool. The throughput of the full network may be input by a user. For example, at present, the peak rate of the total provincial traffic throughput is 3000bps, and a value higher than 3000bps is input as the total throughput of the whole network for traffic scheduling calculation.

And step 320, calculating the current flow of each SAE gateway according to the total throughput of the whole network and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs.

And calculating the current flow of each SAE gateway under the current weight according to the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs and the input total throughput of the whole network by multiplying the current weight by the total throughput of the whole network.

Step 330, generating alarm information according to the current flow of each SAE gateway and the topological relation of the core network element group.

Specifically, step 330 comprises:

step 331, obtaining traffic information of each network element in the core network element group according to the current traffic of each SAE gateway and the topological relation of the core network element group, and obtaining bandwidth information of a link between each network element in the core network element group.

The topological relation of the core network element group comprises the connection relation of each network element in the core network element group. The connections between the various network elements are referred to as links, e.g., as shown in fig. 1, the connections between the access SW and the aggregation SW are referred to as links. The topological relation of the core network element group can be manually uploaded in advance or generated by logging in each network element for query. In step 311, the traffic of each network element in the core network element group and the bandwidth of the link between each network element are sequentially calculated according to the current traffic of each SAE gateway and the topological relation of the core network element group, so as to acquire the traffic information of each network element in the core network element group and the bandwidth information of each link. The traffic information of the network element and the bandwidth information of the link may be collected once every preset time.

And 332, calculating the traffic utilization rate of the network element according to the traffic information, and calculating the bandwidth utilization rate of the link according to the bandwidth information.

The traffic information may include traffic of the network element. Calculating the traffic utilization rate of the network element according to the traffic information, which may specifically be: and acquiring the capacity of the network element, dividing the traffic of the network element by the capacity of the network element, and calculating to obtain the traffic utilization rate of the network element.

The bandwidth information may include a bandwidth of the link, among others. Calculating the bandwidth utilization rate of the link according to the bandwidth information, which may specifically be: and acquiring the capacity of the link, dividing the bandwidth of the link by the capacity of the link, and calculating to obtain the bandwidth utilization rate of the bandwidth.

Step 333, generating an alarm message when the traffic utilization rate of the network element exceeds a preset traffic utilization rate threshold, or generating an alarm message when the bandwidth utilization rate of the link exceeds a preset bandwidth utilization rate threshold.

The preset traffic utilization threshold and the preset bandwidth utilization threshold are preset thresholds. And when the traffic utilization rate of the network element exceeds a preset traffic utilization rate threshold or the bandwidth utilization rate of the link exceeds a preset bandwidth utilization rate threshold, generating alarm information.

In some embodiments, the method further comprises:

and step 334, when the traffic utilization rate of the network element is greater than the preset traffic utilization rate second threshold and less than the preset traffic utilization rate threshold, generating secondary alarm information, or when the bandwidth utilization rate of the link is greater than the preset bandwidth utilization rate second threshold and less than the preset bandwidth utilization rate threshold, generating secondary alarm information.

And the preset second threshold of the traffic utilization rate and the preset second threshold of the bandwidth utilization rate are preset thresholds. The preset traffic utilization rate second threshold is smaller than the preset traffic utilization rate threshold, and the preset bandwidth utilization rate second threshold is smaller than the preset bandwidth utilization rate threshold. By setting two different levels of thresholds, prompts of different degrees can be performed.

In some embodiments, the method may further comprise:

and step 340, displaying the topological relation, the alarm information and the secondary alarm information of the network element group of the core network.

The network elements and links in the core network element group can be drawn into corresponding network element icons and link icons, so that the topological relation of the core network element group is displayed through the topological graph. When the user clicks the network element icon or the link icon, the real-time traffic utilization rate of the network element or the bandwidth utilization rate of the link can be inquired.

The warning information may include red light lighting information, and the warning information may be displayed on the network element icon and the link icon. For example, when the traffic utilization rate of the network element exceeds a preset traffic utilization rate threshold, a red light is lighted on a corresponding network element icon; and when the bandwidth utilization rate of the link exceeds a preset bandwidth utilization rate threshold, a red light is lightened on the corresponding link icon, so that a user can know the traffic load condition of the core network element group by observing red light information. The alarm information may also include time information generated by the alarm information, and the like.

The secondary alarm information may include bright yellow light information, and the secondary alarm information may be displayed on the network element icon and the link icon. For example, when the traffic utilization rate of the network element is greater than a preset traffic utilization rate second threshold and less than a preset traffic utilization rate threshold, a yellow light is turned on a corresponding network element icon; and when the bandwidth utilization rate of the link is greater than a second threshold value of the preset bandwidth utilization rate and less than the threshold value of the preset bandwidth utilization rate, a yellow light is turned on the corresponding link icon, so that a user can know the traffic load condition of the core network element group by observing the yellow light information.

In this embodiment, the traffic of the network topology logic is visualized by displaying the topology relationship of the network element group of the core network, and the scheduling effect is visualized by displaying the alarm information, which is convenient for the subsequent manual intervention on the traffic drop.

Fig. 5 is a flowchart illustrating a traffic scheduling method according to another embodiment of the present invention. The method may be applied to the application scenario as shown in fig. 1, and may be performed at a base station. In fig. 1, the LTE system includes three core network element groups a1, a2, A3 and an SAE gateway pool composed of four SAE gateways B1, B2, B3, B4, B1, B2 are connected to a1, B3 is connected to a2, B4 is connected to A3, and the current weights of B1, B2, B3, B4 in the SAE gateway pool are B1, B2, B3, B4, respectively.

As shown in fig. 5, the method includes:

step 401, obtaining the total throughput of the whole network and the identification of the faulty network element, which are input by the user.

Step 402, according to the identifier of the faulty network element, determining that the network element group of the core network with the fault is A3, and setting the current weight B4 of SAE gateway B4 connected with the network element group A3 of the core network to zero.

And step 403, calculating the current flow of SAE gateways B1, B2, B3 and B4 according to the total throughput of the whole network and the current weights of the SAE gateways B1, B2, B3 and B4 in the SAE gateway pool.

The current weights of B1, B2, B3 and B4 are B1, B2, B3 and 0 respectively, and the total throughput of the whole network is m, then the current flows of B1, B2, B3 and B4 are m B1, m B2, m B3 and 0 respectively.

And step 404, generating alarm information according to the current flow of SAE gateways B1, B2, B3 and B4 and the topological relation of network element groups A1, A2 and A3 of the core network.

For example, if 5 icons in the core network element group a1 are lighted with red light, 3 of the core network element group a2 are lighted with red light, and the core network element group A3 is not lighted with red light, the core network element groups a1 and a2 have alarm information.

Step 405, the core network element groups a1 and a2 generate alarm information, and information of SAE gateways B1, B2 and B3 connected with the core network element groups a1 and a2 is acquired.

Step 406, acquiring the capacity of SAE gateways B1 and B2 connected to network element group a1 of the core network and the current weight of SAE gateways B1 and B2, and calculating the ratio of the current weight and the capacity of SAE gateways B1 and B2.

Wherein, if 5 icons in the core network element group a1 are lighted with red light, and 3 of the core network element group a2 are lighted with red light, the core network element group a1 is firstly subjected to traffic scheduling. Wherein, the obtained capacities of SAE gateways B1 and B2 are c1 and c2 respectively, and the ratios of the current weights and capacities of SAE gateways B1 and B2 are B1/c1 and B2/c2 respectively.

Step 407, taking the minimum value of the ratio of the current weight and the capacity of the SAE gateways B1 and B2 as a reference value, and calculating the initial adjustment weight of the SAE gateways B1 and B2 according to the reference value and the capacities of the SAE gateways B1 and B2.

And if the comparison determines that b1/c1 is minimum, the reference value is b1/c 1. The initial adjustment weights of SAE gateways B1 and B2 are calculated to be B1/c1 and c2 × B1/c1 respectively.

And step 408, carrying out traffic scheduling on SAE gateways B1 and B2 according to the initial adjustment weights of the SAE gateways B1 and B2.

Step 409, if the alarm information still appears in the core network element group a1, obtaining a preset weight adjustment step length, and adjusting the initial adjustment weights of the SAE gateways B1 and B2 according to the preset weight adjustment step length.

And if the preset weight adjustment step is 2, adjusting the initial adjustment weights of the SAE gateways B1 and B2 to B1/c1-2 and c2 × B1/c 1-2.

And step 410, carrying out traffic scheduling on SAE gateways B1 and B2 according to the adjusted initial adjustment weight.

Step 411, if the alarm information of the core network element group a1 still does not disappear, taking the adjusted initial adjustment weight as the initial adjustment weight, and executing step 409 and step 410 in a circulating manner until the alarm information does not appear in the core network element group a 1.

After the adjustment, the red light quantity of the core network element group a1 may be reduced, but the red light quantity does not completely disappear, so that the adjustment needs to be continued until the red light quantity of the core network element group a1 disappears, and the traffic scheduling of the core network element group a1 is completed.

Step 412, performing traffic scheduling on the core network element group a2 according to the method in step 406-411 until the warning information does not appear in the core network element group a2 any more, and then completing the traffic scheduling of the whole system.

Fig. 5 is a schematic structural diagram illustrating a traffic scheduling apparatus according to an embodiment of the present invention. The method may be applied to the application scenario as shown in fig. 1, e.g. may be performed at a base station. As shown in fig. 5, the apparatus includes: SAE gateway acquisition module 510, initial adjustment weight calculation module 520, and traffic scheduling module 530.

The SAE gateway acquiring module 510 is configured to acquire, when an alarm information occurs in a core network element group, information of each SAE gateway connected to the core network element group; the initial adjustment weight calculation module 520 is configured to obtain the capacity of each SAE gateway and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs, calculate a ratio between the capacity of each SAE gateway and the current weight, use a minimum value of the ratio between the capacity of each SAE gateway and the current weight as a reference value, and calculate an initial adjustment weight of each SAE gateway according to the reference value and the capacity of each SAE gateway; the traffic scheduling module 530 is configured to perform traffic scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway.

In an optional manner, the traffic scheduling module 530 is further configured to determine whether an alarm message occurs in the core network element group; if alarm information appears, acquiring a preset weight adjustment step length, and adjusting the initial adjustment weight according to the preset weight adjustment step length; carrying out flow scheduling on each SAE gateway according to the adjusted initial adjustment weight; setting the adjusted initial adjustment weight as an initial adjustment weight; and continuing to execute the step of judging whether the alarm information appears in the core network element group or not, and carrying out flow scheduling on each SAE gateway.

In an optional manner, the apparatus further comprises: the device comprises an input module and an alarm module. The input module is used for acquiring the total throughput of the whole network; the alarm module is used for calculating the current flow of each SAE gateway according to the total throughput of the whole network and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs; and generating the alarm information according to the current flow of each SAE gateway and the topological relation of the core network element group.

In an optional manner, the alarm module is specifically configured to: acquiring the traffic information of each network element in the core network element group according to the current traffic of each SAE gateway and the topological relation of the core network element group; calculating the traffic utilization rate of the network element according to the traffic information; and when the traffic utilization rate of the network element exceeds a preset traffic utilization rate threshold, generating the alarm information.

In an optional manner, the alarm module is specifically configured to: acquiring bandwidth information of links among network elements in the core network element group according to the current flow of each SAE gateway and the topological relation of the core network element group; calculating the bandwidth utilization rate of the link according to the bandwidth information; and when the bandwidth utilization rate of the link exceeds a preset bandwidth utilization rate threshold value, generating the alarm information.

In an optional manner, the apparatus further comprises: and a display module. And the display module is used for displaying the topological relation of the core network element group and the alarm information.

In an optional manner, the input module is further configured to obtain a failed network element identifier; the initial adjustment weight calculation module 520 is further configured to determine, according to the identifier of the faulty network element, a core network element group in which the fault exists; and setting the current weight of the SAE gateway connected with the core network element group with the fault in the SAE gateway pool to zero.

It should be noted that, the traffic scheduling apparatus provided in the embodiments of the present invention is an apparatus capable of executing the traffic scheduling method, and all embodiments of the traffic scheduling method are applicable to the apparatus and can achieve the same or similar beneficial effects.

Fig. 6 shows a schematic structural diagram of a computing device provided by an embodiment of the present invention. The specific embodiments of the present invention are not intended to limit the specific implementations of computing devices.

As shown in fig. 6, the computing device may include: a processor (processor)602, a communication Interface 604, a memory 606, and a communication bus 608.

Wherein: the processor 602, communication interface 604, and memory 606 communicate with one another via a communication bus 608. A communication interface 604 for communicating with other devices, such as network elements or network elements of other servers and the like. The processor 602 is configured to execute the program 610, and may specifically perform the relevant steps in the embodiment of the traffic scheduling method.

In particular, program 610 may include program code comprising computer-executable instructions.

The processor 602 may be a central processing unit CPU or an application Specific Integrated circuit asic or one or more Integrated circuits configured to implement embodiments of the present invention. The computing device includes one or more processors, which may be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.

And a memory 606 for storing a program 610. Memory 606 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The program 610 may specifically be invoked by the processor 602 to enable the computing device to perform the operations in the traffic scheduling method in the foregoing embodiments.

An embodiment of the present invention provides a computer-readable storage medium, where the storage medium stores at least one executable instruction, and when the executable instruction is executed on a computing device, the computing device is enabled to execute a traffic scheduling method in any of the above method embodiments. The executable instructions may be specifically configured to cause the computing device to perform the operations in the traffic scheduling method in the foregoing embodiments.

The embodiment of the invention provides a traffic scheduling device, which is used for executing the traffic scheduling method.

Embodiments of the present invention provide a computer program, where the computer program can be called by a processor to enable a computing device to execute a traffic scheduling method in any of the above method embodiments.

Embodiments of the present invention provide a computer program product, which includes a computer program stored on a computer-readable storage medium, where the computer program includes program instructions, and when the program instructions are run on a computer, the computer is caused to execute the method for scheduling traffic in any of the above-mentioned method embodiments.

The algorithms or displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.

In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the invention and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names. The steps in the above embodiments should not be construed as limiting the order of execution unless specified otherwise.

Claims

1. A traffic scheduling method, comprising:

when alarm information appears in a core network element group, acquiring information of each SAE gateway connected with the core network element group;

acquiring the capacity of each SAE gateway and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs, and calculating the ratio of the current weight to the capacity of each SAE gateway;

taking the minimum value in the ratio of the current weight to the capacity of each SAE gateway as a reference value;

calculating the initial adjustment weight of each SAE gateway according to the reference value and the capacity of each SAE gateway;

and carrying out traffic scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway.

2. The method of claim 1, wherein after the traffic scheduling for each SAE gateway according to its initial adjusted weight, the method further comprises:

judging whether the alarm information appears in the core network element group;

if alarm information appears, acquiring a preset weight adjustment step length, and adjusting the initial adjustment weight according to the preset weight adjustment step length;

carrying out flow scheduling on each SAE gateway according to the adjusted initial adjustment weight;

setting the adjusted initial adjustment weight as an initial adjustment weight;

and continuing to execute the step of judging whether the alarm information appears in the core network element group or not, and carrying out flow scheduling on each SAE gateway.

3. The method of claim 1, wherein before the obtaining of each SAE gateway information connected to a core network element group when the alarm information occurs in the core network element group, the method further comprises:

acquiring total throughput of the whole network;

calculating the current flow of each SAE gateway according to the total throughput of the whole network and the current weight of each SAE gateway in the SAE gateway pool to which the SAE gateway belongs;

and generating the alarm information according to the current flow of each SAE gateway and the topological relation of the core network element group.

4. The method according to claim 3, wherein the generating the alarm information according to the current traffic of each SAE gateway and the topological relation of the core network element group specifically includes:

acquiring the traffic information of each network element in the core network element group according to the current traffic of each SAE gateway and the topological relation of the core network element group;

calculating the traffic utilization rate of the network element according to the traffic information;

and when the traffic utilization rate of the network element exceeds a preset traffic utilization rate threshold, generating the alarm information.

5. The method according to claim 3, wherein the generating the alarm information according to the current traffic of each SAE gateway and the topological relation of the core network element group specifically includes:

acquiring bandwidth information of links among network elements in the core network element group according to the current flow of each SAE gateway and the topological relation of the core network element group;

calculating the bandwidth utilization rate of the link according to the bandwidth information;

and when the bandwidth utilization rate of the link exceeds a preset bandwidth utilization rate threshold value, generating the alarm information.

6. The method of claim 3, further comprising:

and displaying the topological relation of the core network element group and the alarm information.

7. The method of any of claims 1-6, wherein before said obtaining the capacity of each said SAE gateway and the current weight of each said SAE gateway in the SAE gateway pool to which it belongs, and calculating the ratio of the capacity of each said SAE gateway to the current weight, the method further comprises:

acquiring a fault network element identifier;

determining a core network element group with a fault according to the fault network element identifier;

and setting the current weight of the SAE gateway connected with the core network element group with the fault in the SAE gateway pool to zero.

8. A traffic scheduling apparatus, comprising:

an SAE gateway acquisition module, configured to acquire, when an alarm message occurs in a core network element group, information of each SAE gateway connected to the core network element group;

an initial adjustment weight calculation module, configured to obtain the capacity of each SAE gateway and the current weight of each SAE gateway in an SAE gateway pool to which the SAE gateway belongs, calculate a ratio between the capacity of each SAE gateway and the current weight, use a minimum value of the ratios between the capacity of each SAE gateway and the current weight as a reference value, and calculate an initial adjustment weight of each SAE gateway according to the reference value and the capacity of each SAE gateway;

and the flow scheduling module is used for carrying out flow scheduling on each SAE gateway according to the initial adjustment weight of each SAE gateway.

9. A computing device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;

the memory is configured to store at least one executable instruction that causes the processor to perform the operations of the traffic scheduling method according to any of claims 1-7.

10. A computer-readable storage medium having stored therein at least one executable instruction that, when executed on a computing device, causes the computing device to perform operations of the traffic scheduling method according to any one of claims 1 to 7.