A method and device for adjusting equipment flow

Abstract

The present invention discloses a method and apparatus for device traffic adjustment operations, wherein the method comprises: calling a circuit query interface to query specific circuit information based on device port information or circuit information inputted from a scene entry; judging whether the circuit is a resource within the adjustment processing range based on the configured circuit attributes or device attributes; if so, judging whether the circuit adopts a traffic adjustment method of adjusting the cost / metric value or a traffic adjustment method of adjusting the static routing entry; judging whether there is a processing record for the circuit to be adjusted, and if so, giving a prompt; if not, judging whether there is an unrecovered adjustment record for the circuit to be adjusted, and if so, performing a recovery operation; if not, performing an adjustment operation. When a port on the device fails, resulting in abnormal traffic, the method and apparatus can quickly perform real-time detection and dynamic judgment, thereby automatically performing a traffic switching operation.

Description

Technical Field

[0001] The present invention relates to the field of flow switching operations, and in particular to a method and apparatus for equipment flow adjustment operations. Background Art

[0002] In the era of large-scale network deployment, network traffic is a key monitoring metric for network maintenance. When a device card or port failure or other causes traffic congestion, existing alarm systems can quickly detect the fault and issue an alert. However, after the alarm occurs, how to quickly respond and switch traffic to minimize the impact of the fault is a daily priority for network maintenance personnel. Traditional traffic switching operations require extensive manual intervention, lack real-time performance, and, if misjudged and improperly switched, can cause even greater network congestion. Summary of the Invention

[0003] In order to solve the above-mentioned problems existing in traditional traffic switching operations, the present invention provides a method and device for device traffic adjustment operations. When a port on the device fails, resulting in abnormal traffic, real-time detection and dynamic judgment can be quickly performed, thereby automatically performing traffic switching operations.

[0004] To achieve the above object, the present invention adopts the following technical solutions:

[0005] In one embodiment of the present invention, a method for adjusting device traffic flow is provided, the method comprising:

[0006] Based on the device port information or circuit information passed into the scene entrance, call the circuit query interface to query the specific circuit information;

[0007] Based on the configured circuit attributes or device attributes, the system determines whether the circuit is within the resource adjustment range. If so, the system determines whether to use traffic shaping methods such as adjusting the cost / metric value or static route entries for the circuit.

[0008] Determine whether there is a processing record for the circuit to be adjusted. If so, give a prompt. If not, determine whether there is an unrestored adjustment record for the circuit to be adjusted. If so, perform a recovery operation. If not, perform an adjustment operation.

[0009] Furthermore, the recovery operation is as follows:

[0010] Displays the cost / metric value of the port before adjustment or the original static route entry;

[0011] After user confirmation or automatic system identification, the operation delivery interface is called to restore the cost / metric values ​​or static route entries at the local and remote ends of the trunk circuit to their original values.

[0012] After the delivery is successful, the traffic adjustment recovery record is recorded.

[0013] Furthermore, the adjustment operation is as follows:

[0014] Query the current cost / metric value or static route entry on the device in real time;

[0015] Call the same-direction port detection interface to query the same-direction port bandwidth usage of the port to be adjusted;

[0016] Determine whether the same-direction port supports bandwidth adjustment. If not, a prompt is given. If yes, the user confirms or the system automatically identifies it and calls the operation delivery interface to adjust the cost / metric value: adjust the cost / metric value of the local and remote ends of the trunk circuit to 10,000 times the original value, or adjust the static route entry: delete the static route of the local and remote ends of the trunk circuit.

[0017] After successful delivery, record the traffic adjustment record, the cost / metric value before the port adjustment or the original static route entry.

[0018] Furthermore, the process for querying the bandwidth usage of the same-direction port to be adjusted is as follows:

[0019] The port to be adjusted is: the port for traffic to be allocated;

[0020] Query the trunk circuit where the adjustment port is located and record: the devices at both ends of the trunk circuit, the circuit property cirprop, and the direction of the circuit where the adjustment port is located, which is recorded as X;

[0021] Query all circuits between the two end devices of the relay circuit whose circuit property is equal to cirprop, which are recorded as: same-direction circuits;

[0022] For the ports in the X direction of the same-direction circuit, after removing the ports to be shared, the remaining ports are recorded as: same-direction ports;

[0023] Query the status of the same-direction ports. If the port status is down, record the port status and exclude it from subsequent calculations. If the port status is up, retain it. Query the traffic data of each port in the system es within 10 minutes. If there is no data, record the port status and traffic data and exclude it from subsequent calculations. If there is data, retain it. Query the real-time cost / metric value of the port on the device and determine whether the cost / metric value is greater than 10000. If so, record it as a blocked port and exclude it from subsequent calculations. Otherwise, retain it and record the port as a list of ports that can share traffic. Calculate whether the traffic can be shared. If so, return: bandwidth can be adjusted. If not, return: bandwidth cannot be adjusted.

[0024] Furthermore, the algorithm for calculating whether traffic can be shared is as follows:

[0025] Query the traffic peaks of the ports to be allocated and the list of ports that can be allocated from the system es on the previous day;

[0026] Query the circuit bandwidth of the circuit corresponding to the list of ports that can share traffic;

[0027] Calculate the apportioned traffic of each circuit: F = the peak traffic volume of the port to be apportioned the previous day / N, where N = the number of circuits to be apportioned.

[0028] Calculate the peak traffic utilization rate of each sharable circuit after allocation: R = (peak traffic of each sharable circuit on the previous day + F) / bandwidth of the circuit * 100%;

[0029] Determine whether R of a port is greater than the port peak utilization threshold Limit set by the system. If so, the traffic cannot be shared; otherwise, it can be shared.

[0030] In one embodiment of the present invention, a device for adjusting device flow is also provided, the device comprising:

[0031] The circuit query module is used to call the circuit query interface to query the information of a specific circuit based on the device port information or circuit information input by the scene entrance;

[0032] The traffic shaping module is used to determine whether the circuit is a resource within the adjustment processing range based on the configured circuit attributes or device attributes. If so, it determines whether the circuit is to be shaped by adjusting the cost / metric value or the static route entry. It also determines whether there is a processing record for the circuit to be adjusted. If so, a prompt is given. If not, it determines whether there is an unrecovered adjustment record for the circuit to be adjusted. If so, a recovery operation is performed. If not, an adjustment operation is performed.

[0033] Furthermore, the recovery operation is as follows:

[0034] Displays the cost / metric value of the port before adjustment or the original static route entry;

[0035] After user confirmation or automatic system identification, the operation delivery interface is called to restore the cost / metric values ​​or static route entries at the local and remote ends of the trunk circuit to their original values.

[0036] After the delivery is successful, the traffic adjustment recovery record is recorded.

[0037] Furthermore, the adjustment operation is as follows:

[0038] Query the current cost / metric value or static route entry on the device in real time;

[0039] Call the same-direction port detection interface to query the same-direction port bandwidth usage of the port to be adjusted;

[0040] Determine whether the same-direction port supports bandwidth adjustment. If not, a prompt is given. If yes, the user confirms or the system automatically identifies it and calls the operation delivery interface to adjust the cost / metric value: adjust the cost / metric value of the local and remote ends of the trunk circuit to 10,000 times the original value, or adjust the static route entry: delete the static route of the local and remote ends of the trunk circuit.

[0041] After successful delivery, record the traffic adjustment record, the cost / metric value before the port adjustment or the original static route entry.

[0042] Furthermore, the process for querying the bandwidth usage of the same-direction port to be adjusted is as follows:

[0043] The port to be adjusted is: the port for traffic to be allocated;

[0044] Query the trunk circuit where the adjustment port is located and record: the devices at both ends of the trunk circuit, the circuit property cirprop, and the direction of the circuit where the adjustment port is located, which is recorded as X;

[0045] Query all circuits between the two end devices of the relay circuit whose circuit property is equal to cirprop, which are recorded as: same-direction circuits;

[0046] For the ports in the X direction of the same-direction circuit, after removing the ports to be shared, the remaining ports are recorded as: same-direction ports;

[0047] Query the status of the same-direction ports. If the port status is down, record the port status and exclude it from subsequent calculations. If the port status is up, retain it. Query the traffic data of each port in the system es within 10 minutes. If there is no data, record the port status and traffic data and exclude it from subsequent calculations. If there is data, retain it. Query the real-time cost / metric value of the port on the device and determine whether the cost / metric value is greater than 10000. If so, record it as a blocked port and exclude it from subsequent calculations. Otherwise, retain it and record the port as a list of ports that can share traffic. Calculate whether the traffic can be shared. If so, return: bandwidth can be adjusted. If not, return: bandwidth cannot be adjusted.

[0048] Furthermore, the algorithm for calculating whether traffic can be shared is as follows:

[0049] Query the traffic peaks of the ports to be allocated and the list of ports that can be allocated from the system es on the previous day;

[0050] Query the circuit bandwidth of the circuit corresponding to the list of ports that can share traffic;

[0051] Calculate the apportioned traffic of each circuit: F = the peak traffic volume of the port to be apportioned the previous day / N, where N = the number of circuits to be apportioned.

[0052] Calculate the peak traffic utilization rate of each sharable circuit after allocation: R = (peak traffic of each sharable circuit on the previous day + F) / bandwidth of the circuit * 100%;

[0053] Determine whether R of a port is greater than the port peak utilization threshold Limit set by the system. If so, the traffic cannot be shared; otherwise, it can be shared.

[0054] In one embodiment of the present invention, a computer device is also proposed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method for the aforementioned device traffic adjustment operation is implemented.

[0055] In one embodiment of the present invention, a computer-readable storage medium is further provided. The computer-readable storage medium stores a computer program for executing a method for adjusting device traffic.

[0056] Beneficial effects:

[0057] 1. The present invention encapsulates various capabilities (circuit query, same-direction port detection and operation issuance, etc.) into an API, so that the solution can be quickly reused in multiple entrances or different scenarios, such as fault port alarms on the alarm board, congested circuit alarms on the alarm board, operation entrances for a port in the port list on the device view, operation entrances for a circuit in the circuit view, and peripheral system calls.

[0058] 2. The present invention is scalable, and the range of processing resource adjustment is configurable. At the same time, it can automatically determine whether the traffic adjustment method is to adjust the cost / isis value (ie, metric value) or adjust the static routing entry based on circuit properties or device properties.

[0059] 3. The present invention adopts a strict flow adjustment pre-judgment process, that is, a process for querying the bandwidth usage of the same-direction ports that need to be adjusted, and the conclusion is accurate.

[0060] 4. After the fault is restored, the user can restore the traffic through the page or directly call the API, which is simple and fast and can be restored with one click. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 It is a flow chart of the method for flow adjustment operation of the device of the present invention;

[0062] Figure 2 This is a schematic diagram of a flow chart showing the query process for bandwidth usage of a port in the same direction that needs to be adjusted;

[0063] Figure 3 It is a flow chart of the algorithm for calculating whether the flow can be apportioned according to the present invention;

[0064] Figure 4 It is a schematic diagram of the structure of the device for flow adjustment operation of the device of the present invention;

[0065] Figure 5 It is a schematic diagram of the computer device structure of the present invention. DETAILED DESCRIPTION

[0066] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided solely to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. Rather, these embodiments are provided to make this disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0067] Those skilled in the art will appreciate that the embodiments of the present invention may be implemented as a system, apparatus, device, method, or computer program product. Therefore, the present disclosure may be implemented in the following forms: entirely in hardware, entirely in software (including firmware, resident software, microcode, etc.), or in a combination of hardware and software.

[0068] According to an embodiment of the present invention, a method and apparatus for device flow adjustment operation are proposed. When a port on a device fails, resulting in flow abnormality, real-time detection and dynamic judgment can be quickly performed, thereby automatically performing flow switching operations.

[0069] The principles and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.

[0070] Figure 1 This is a flow chart of the method for adjusting the flow rate of the device of the present invention. Figure 1 As shown, the method includes:

[0071] 1. Based on the device port information or circuit information passed in at the scene entrance, call the circuit query interface (encapsulate the circuit query capability into an API, supporting querying specific circuit information by specifying device + port input parameters or specifying circuit input parameters) to query specific circuit information, including: local device, port, port bandwidth, device attributes; remote device, port, port bandwidth, device attributes; traffic adjustment records, circuit attributes, etc.

[0072] 2. Based on the configured circuit attributes or device attributes, determine whether the circuit is a resource within the adjustment range. If it is, determine whether to use traffic shaping methods such as adjusting the cost / ISI value (metric value) or adjusting the static route entry for the circuit.

[0073] Determine whether there is a processing record for the circuit to be adjusted. If so, give a prompt, end, and do not repeat the operation. Otherwise, determine whether there is an unrestored adjustment record for the circuit to be adjusted. If so, perform the recovery operation, display the cost / metric value of the port before adjustment or the original static route entry, and after user confirmation or system automatic identification (according to system configuration parameters, skip user confirmation and automatically perform configuration operations), call the operation delivery interface (encapsulate the operation delivery capability into an API, support adjustment of the specified port or the configuration of the ports at both ends of the circuit according to device + port input parameters or circuit input parameters), restore the cost / metric value or static route entry of the local and remote ends of the relay circuit to the original value. After successful delivery, record the traffic adjustment recovery record. Otherwise, perform the adjustment operation, and query the current cost / metric value on the device in real time. The system uses the same-direction port detection interface (which encapsulates the same-direction port detection capability into an API, supporting querying of same-direction port information and traffic shaping capabilities by device and port) to query the bandwidth usage of the port to be adjusted and determine whether the same-direction port supports bandwidth adjustment. If not, a prompt is given. If yes, the system automatically identifies the cost / metric value and calls the operation delivery interface to adjust the cost / metric value of the local and remote ends of the trunk circuit to 10,000 times the original value. Alternatively, the system adjusts the static route entry by deleting the static route of the local and remote ends of the trunk circuit to achieve the effect of traffic diversion. After successful delivery, the system records the traffic adjustment record, the cost / metric value of the port before adjustment, or the original static route entry.

[0074] The above recovery operation can be designed as a page or encapsulated into an API for direct call to perform one-click recovery.

[0075] Figure 2 This is a flow chart of querying the bandwidth usage of the same-direction port that needs to be adjusted. Figure 2 As shown in the figure, the process of querying the bandwidth usage of the same-direction port to be adjusted is as follows:

[0076] The port to be adjusted is: the port for traffic to be allocated;

[0077] Query the trunk circuit where the adjustment port is located, and record: the devices at both ends of the trunk circuit (recorded as devices A and B), the circuit properties (cirprop), and the direction of the circuit where the adjustment port is located, recorded as X;

[0078] Query all circuits between the two end devices of the relay circuit whose circuit property is equal to cirprop, which are recorded as: same-direction circuits;

[0079] For the ports in the X direction of the same-direction circuit, after removing the ports to be shared, the remaining ports are recorded as: same-direction ports;

[0080] Query the status of the same-direction ports. If the port status is down, record the port status and exclude it from subsequent calculations. If the port status is up, retain it. Query the traffic data of each port in the system es within 10 minutes. If there is no data, record the port status and traffic data and exclude it from subsequent calculations. If there is data, retain it. Query the real-time cost / metric value of the port on the device and determine whether the cost / metric value is greater than 10000. If so, record it as a blocked port and exclude it from subsequent calculations. Otherwise, retain it and record the port as a list of ports that can share traffic. Calculate whether the traffic can be shared. If so, return: bandwidth can be adjusted. If not, return: bandwidth cannot be adjusted.

[0081] The above process of querying the bandwidth usage of the same-direction port of the port that needs to be adjusted can be encapsulated into an API and directly called by the peripheral system.

[0082] Figure 3 This is a flow chart of the algorithm for calculating whether the traffic can be shared. Figure 3 As shown, the algorithm for calculating whether traffic can be shared is as follows:

[0083] Query the traffic peaks of the ports to be allocated and the list of ports that can be allocated from the system es on the previous day;

[0084] Query the circuit bandwidth of the circuit corresponding to the list of ports that can share traffic;

[0085] Calculate the apportioned traffic of each circuit: F = the peak traffic volume of the port to be apportioned the previous day / N, where N = the number of circuits to be apportioned.

[0086] Calculate the peak traffic utilization rate of each sharable circuit after allocation: R = (peak traffic of each sharable circuit on the previous day + F) / bandwidth of the circuit * 100%;

[0087] Determine whether R of a port is greater than the port peak utilization threshold Limit set by the system. If so, the traffic cannot be shared; otherwise, it can be shared.

[0088] The system stores historical data such as real-time data collected in the es. The port peak utilization threshold is set in the system parameter table.

[0089] It should be noted that although the operations of the method of the present invention are described in a specific order in the above embodiments and drawings, this does not require or imply that these operations must be performed in this specific order, or that all illustrated operations must be performed to achieve the desired results. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0090] In order to more clearly explain the method of the flow adjustment operation of the above-mentioned device, a specific embodiment is used for illustration below. However, it should be noted that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation to the present invention.

[0091] The following example uses the solution from Guangdong Telecom:

[0092] Guangdong Telecom requires the operation entry to be on the physical port operation list in the device view and the specific circuit link in the adjacent topology diagram;

[0093] (1) Add the "Relay Traffic Adjustment" operation to the physical port operation list in the device view;

[0094] (2) Provide right-click operation on specific circuit links on adjacent topology diagrams;

[0095] (3) Call the encapsulated "circuit query API" to query the specific circuit. Guangdong requires that the circuit attribute be limited to a relay circuit. Therefore, if the circuit is not a relay circuit, a prompt will be given; if the circuit is a relay circuit, continue to determine which traffic adjustment method to use;

[0096] (4) Guangdong requires that the circuit attributes be used to determine whether it is a CR circuit. If it is a CR uplink circuit, the cost value should be adjusted; otherwise, the isis or metric value should be adjusted.

[0097] (5) Guangdong requires that information be displayed to the user in the form of a page for confirmation. Therefore, a "Relay Port Traffic Adjustment" page is designed to display all the information returned by the API interface to the user, including the local device name, local device IP, local device adjustment port, local port bandwidth, peer device name, peer device IP, peer device adjustment port, local port bandwidth, cost / metric value (adjustable and recoverable) and whether the bandwidth is supported;

[0098] Click the "Details" button next to "Whether Bandwidth Supports" to open a modal dialog box, displaying the port bandwidth support cutover verification status, including the same-direction port, port status, port bandwidth (Mbps), the previous day's traffic peak (Mbps), whether the port blocks traffic, whether the bandwidth supports traffic adjustment, and the reason. For example: Whether Bandwidth Supports Traffic Adjustment: Not Supported, Reason: After cutover, the bandwidth utilization of the remaining port running traffic is 95%, which will exceed 90%.

[0099] (6) If the circuit has an unrestored adjustment record, select "Restore" on the "Trunk Port Traffic Adjustment" page. Otherwise, select "Adjust" and it cannot be changed.

[0100] (7) The basic information of the local port and the opposite port, the status of the same-direction port, bandwidth and traffic peak of the previous day, whether the port has been blocked, etc. are displayed to the user for confirmation

[0101] (8) If traffic adjustment is supported and the user confirms, the interface is called to log in to the device to perform traffic adjustment operations.

[0102] Based on the same inventive concept, the present invention also provides a device for adjusting device flow. The implementation of this device can refer to the implementation of the above-mentioned method, and any repetitions will not be repeated. The term "module" used below may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0103] Figure 4 This is a schematic diagram of the structure of the device for flow adjustment operation of the present invention. Figure 5 As shown, the device includes:

[0104] The circuit query module 101 is used to call the circuit query interface to query the information of a specific circuit according to the device port information or circuit information input by the scene entrance;

[0105] The traffic shaping module 102 is configured to determine whether the circuit is a resource within the adjustment processing range based on the configured circuit attributes or device attributes. If so, determine whether the circuit is to be shaped by adjusting the cost / metric value or the static route entry. The module also determines whether there is a processing record for the circuit to be shaped, and if so, provides a prompt. If not, it determines whether there is an unrecovered adjustment record for the circuit to be shaped, and if so, performs a recovery operation. If not, performs an adjustment operation.

[0106] The recovery operation is as follows:

[0107] Displays the cost / metric value of the port before adjustment or the original static route entry;

[0108] After user confirmation or automatic system identification, the operation delivery interface is called to restore the cost / metric values ​​or static route entries at the local and remote ends of the trunk circuit to their original values.

[0109] After the delivery is successful, the traffic adjustment recovery record is recorded.

[0110] The adjustment operations are as follows:

[0111] Query the current cost / metric value or static route entry on the device in real time;

[0112] Call the same-direction port detection interface to query the same-direction port bandwidth usage of the port to be adjusted;

[0113] Determine whether the same-direction port supports bandwidth adjustment. If not, a prompt is given. If yes, the user confirms or the system automatically identifies it and calls the operation delivery interface to adjust the cost / metric value: adjust the cost / metric value of the local and remote ends of the trunk circuit to 10,000 times the original value, or adjust the static route entry: delete the static route of the local and remote ends of the trunk circuit.

[0114] After successful delivery, record the traffic adjustment record, the cost / metric value before the port adjustment or the original static route entry.

[0115] The process for querying the bandwidth usage of the same-direction port to be adjusted is as follows:

[0116] The port to be adjusted is: the port for traffic to be allocated;

[0117] Query the trunk circuit where the adjustment port is located and record: the devices at both ends of the trunk circuit, the circuit property cirprop, and the direction of the circuit where the adjustment port is located, which is recorded as X;

[0118] Query all circuits between the two end devices of the relay circuit whose circuit property is equal to cirprop, which are recorded as: same-direction circuits;

[0119] For the ports in the X direction of the same-direction circuit, after removing the ports to be shared, the remaining ports are recorded as: same-direction ports;

[0120] Query the status of the same-direction ports. If the port status is down, record the port status and exclude it from subsequent calculations. If the port status is up, retain it. Query the traffic data of each port in the system es within 10 minutes. If there is no data, record the port status and traffic data and exclude it from subsequent calculations. If there is data, retain it. Query the real-time cost / metric value of the port on the device and determine whether the cost / metric value is greater than 10000. If so, record it as a blocked port and exclude it from subsequent calculations. Otherwise, retain it and record the port as a list of ports that can share traffic. Calculate whether the traffic can be shared. If so, return: bandwidth can be adjusted. If not, return: bandwidth cannot be adjusted.

[0121] The algorithm for calculating whether traffic can be shared is as follows:

[0122] Query the traffic peaks of the ports to be allocated and the list of ports that can be allocated from the system es on the previous day;

[0123] Query the circuit bandwidth of the circuit corresponding to the list of ports that can share traffic;

[0124] Calculate the apportioned traffic of each circuit: F = the peak traffic volume of the port to be apportioned the previous day / N, where N = the number of circuits to be apportioned.

[0125] Calculate the peak traffic utilization rate of each sharable circuit after allocation: R = (peak traffic of each sharable circuit on the previous day + F) / bandwidth of the circuit * 100%;

[0126] Determine whether R of a port is greater than the port peak utilization threshold Limit set by the system. If so, the traffic cannot be shared; otherwise, it can be shared.

[0127] It should be noted that although the above detailed description mentions several modules of the apparatus for device flow regulation, this division is merely exemplary and not mandatory. In practice, according to embodiments of the present invention, the features and functions of two or more modules described above may be embodied in a single module. Conversely, the features and functions of a single module described above may be further divided and embodied by multiple modules.

[0128] Based on the above invention concept, Figure 5 As shown, the present invention also proposes a computer device 200, including a memory 210, a processor 220 and a computer program 230 stored in the memory 210 and executable on the processor 220, and the processor 220 implements the aforementioned device traffic adjustment operation method when executing the computer program 230.

[0129] Based on the aforementioned inventive concept, the present invention further proposes a computer-readable storage medium, which stores a computer program for executing the aforementioned method for device traffic adjustment operation.

[0130] The method and apparatus for device traffic adjustment operations proposed in the present invention encapsulate various capabilities (circuit query, same-direction port detection and operation dispatch, etc.) into an API, so that the solution can be quickly reused in multiple entries or different scenarios, such as fault port alarms on an alarm panel, congested circuit alarms on an alarm panel, operation entries for a port in a port list on a device view, operation entries for a circuit in a circuit view, and peripheral system calls. The method and apparatus are scalable, and the adjustment processing resource range is configurable. At the same time, the method for traffic adjustment, whether to adjust the cost / ISI value (i.e., metric value) or static routing entries, can be automatically determined based on circuit properties or device properties. A strict traffic adjustment pre-judgment process, i.e., a process for querying the bandwidth usage of the same-direction ports of the ports to be adjusted, is adopted, and the conclusion is accurate. After the fault is recovered, the user can restore the traffic through a web page or by directly calling the API, which is simple and fast, and can achieve one-click recovery.

[0131] Although the spirit and principles of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the specific embodiments disclosed, and the division into various aspects does not mean that the features of these aspects cannot be combined to benefit. Such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

[0132] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.

Claims

1. A method for adjusting device flow rate, characterized in that: The method includes: Based on the device port information or circuit information passed into the scene entrance, call the circuit query interface to query the specific circuit information; Based on the configured circuit attributes or device attributes, the system determines whether the circuit is within the resource adjustment range. If so, the system determines whether to use traffic shaping methods such as adjusting the cost / metric value or static route entries for the circuit. Determine whether there is a processing record for the circuit to be adjusted. If so, give a prompt. If not, determine whether there is an unrestored adjustment record for the circuit to be adjusted. If so, perform a restore operation. If not, perform an adjustment operation. The adjustment operations are as follows: Query the current cost / metric value or static route entry on the device in real time; Call the same-direction port detection interface to query the same-direction port bandwidth usage of the port to be adjusted; Determine whether the same-direction port supports bandwidth adjustment. If not, a prompt is given. If yes, the user confirms or the system automatically identifies it and calls the operation delivery interface to adjust the cost / metric value: adjust the cost / metric value of the local and remote ends of the trunk circuit to 10,000 times the original value, or adjust the static route entry: delete the static route of the local and remote ends of the trunk circuit. After successful delivery, record the traffic adjustment record, the cost / metric value before the port adjustment or the original static route entry; The process for querying the bandwidth usage of the same-direction port to be adjusted is as follows: The port to be adjusted is: the port for traffic to be allocated; Query the trunk circuit where the adjustment port is located and record: the devices at both ends of the trunk circuit, the circuit property cirprop, and the direction of the circuit where the adjustment port is located, which is recorded as X; Query all circuits between the two end devices of the relay circuit whose circuit property is equal to cirprop, which are recorded as: same-direction circuits; For the ports in the X direction of the same-direction circuit, after removing the ports to be shared, the remaining ports are recorded as: same-direction ports; Query the status of the same-direction ports. If the port status is down, record the port status and exclude it from subsequent calculations. If the port status is up, retain it. Query the traffic data of each port in the system es within 10 minutes. If there is no data, record the port status and traffic data and exclude it from subsequent calculations. If there is data, retain it. Query the real-time cost / metric value of the port on the device and determine whether the cost / metric value is greater than 10000. If so, record it as a blocked port and exclude it from subsequent calculations. Otherwise, retain it and record the port as a list of ports that can share traffic. Calculate whether the traffic can be shared. If so, return: bandwidth can be adjusted. If not, return: bandwidth cannot be adjusted.

2. The method for adjusting device flow according to claim 1, characterized in that: The recovery operation is as follows: Displays the cost / metric value of the port before adjustment or the original static route entry; After user confirmation or automatic system identification, the operation delivery interface is called to restore the cost / metric values ​​or static route entries at the local and remote ends of the trunk circuit to their original values. After the delivery is successful, the traffic adjustment recovery record is recorded.

3. The method for adjusting device flow according to claim 1, characterized in that: The algorithm for calculating whether traffic can be shared is as follows: Query the traffic peaks of the ports to be allocated and the list of ports that can be allocated from the system es on the previous day; Query the circuit bandwidth of the circuit corresponding to the list of ports that can share traffic; Calculate the apportioned traffic of each circuit: F = the peak traffic volume of the port to be apportioned the previous day / N, where N = the number of circuits to be apportioned. Calculate the peak traffic utilization rate of each sharable circuit after allocation: R = (peak traffic of each sharable circuit on the previous day + F) / bandwidth of the circuit * 100%; Determine whether R of a port is greater than the port peak utilization threshold Limit set by the system. If so, the traffic cannot be shared; otherwise, it can be shared.

4. A device for adjusting the flow rate of equipment, characterized in that: The device includes: The circuit query module is used to call the circuit query interface to query the information of a specific circuit based on the device port information or circuit information input by the scene entrance; The traffic shaping module is used to determine whether the circuit is a resource within the adjustment processing range based on the configured circuit attributes or device attributes. If it is within the adjustment processing range, it determines whether the circuit is to be shaped by adjusting the cost / metric value or the static route entry. It also determines whether there is a processing record for the circuit to be adjusted. If so, a prompt is given. If not, it determines whether there is an unrecovered adjustment record for the circuit to be adjusted. If so, a recovery operation is performed. If not, an adjustment operation is performed. The adjustment operations are as follows: Query the current cost / metric value or static route entry on the device in real time; Call the same-direction port detection interface to query the same-direction port bandwidth usage of the port to be adjusted; Determine whether the same-direction port supports bandwidth adjustment. If not, a prompt is given. If yes, the user confirms or the system automatically identifies it and calls the operation delivery interface to adjust the cost / metric value: adjust the cost / metric value of the local and remote ends of the trunk circuit to 10,000 times the original value, or adjust the static route entry: delete the static route of the local and remote ends of the trunk circuit. After successful delivery, record the traffic adjustment record, the cost / metric value before the port adjustment or the original static route entry; The process for querying the bandwidth usage of the same-direction port to be adjusted is as follows: The port to be adjusted is: the port for traffic to be allocated; Query the trunk circuit where the adjustment port is located and record: the devices at both ends of the trunk circuit, the circuit property cirprop, and the direction of the circuit where the adjustment port is located, which is recorded as X; Query all circuits between the two end devices of the relay circuit whose circuit property is equal to cirprop, which are recorded as: same-direction circuits; For the ports in the X direction of the same-direction circuit, after removing the ports to be shared, the remaining ports are recorded as: same-direction ports; Query the status of the same-direction ports. If the port status is down, record the port status and exclude it from subsequent calculations. If the port status is up, retain it. Query the traffic data of each port in the system es within 10 minutes. If there is no data, record the port status and traffic data and exclude it from subsequent calculations. If there is data, retain it. Query the real-time cost / metric value of the port on the device and determine whether the cost / metric value is greater than 10000. If so, record it as a blocked port and exclude it from subsequent calculations. Otherwise, retain it and record the port as a list of ports that can share traffic. Calculate whether the traffic can be shared. If so, return: bandwidth can be adjusted. If not, return: bandwidth cannot be adjusted.

5. The device for adjusting the flow rate of equipment according to claim 4, characterized in that: The recovery operation is as follows: Displays the cost / metric value of the port before adjustment or the original static route entry; After user confirmation or automatic system identification, the operation delivery interface is called to restore the cost / metric values ​​or static route entries at the local and remote ends of the trunk circuit to their original values. After the delivery is successful, the traffic adjustment recovery record is recorded.

6. The device for adjusting the flow rate of equipment according to claim 4, characterized in that: The algorithm for calculating whether traffic can be shared is as follows: Query the traffic peaks of the ports to be allocated and the list of ports that can be allocated from the system es on the previous day; Query the circuit bandwidth of the circuit corresponding to the list of ports that can share traffic; Calculate the apportioned traffic of each circuit: F = the peak traffic volume of the port to be apportioned the previous day / N, where N = the number of circuits to be apportioned. Calculate the peak traffic utilization rate of each sharable circuit after allocation: R = (peak traffic of each sharable circuit on the previous day + F) / bandwidth of the circuit * 100%; Determine whether R of a port is greater than the port peak utilization threshold Limit set by the system. If so, the traffic cannot be shared; otherwise, it can be shared.

7. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 3 is implemented.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 3.

Images