Traffic management method and device, equipment and storage medium

Abstract

The invention discloses a traffic management method, device and equipment and a storage medium, and relates to the technical field of computer network traffic management and optimization, and the method comprises the steps: obtaining a switch configuration address, a switch configuration path and a to-be-sent data packet; locking a mapping relation between each switch port and corresponding target equipment based on the switch configuration address, and determining a static address table; setting a routing path and a priority corresponding to each data flow based on the switch configuration path, and determining a static routing table; switching a network label corresponding to the to-be-sent data packet based on the static address table and the static routing table, and determining label switching information; and forwarding the to-be-sent data packet along the forwarding path identified by the label switching information to complete routing flow management. According to the invention, the static address table and the static routing table are utilized to accurately control the data flow and select the optimization path, network label switching is carried out to realize rapid and efficient forwarding, and the flow optimization efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computer network traffic management and optimization technology, and in particular to traffic management methods, devices, equipment and storage media. Background Technology

[0002] With the continuous development of network technology, enterprises and operators are increasingly demanding network traffic management. Efficient traffic management can not only improve network performance and stability, but also optimize bandwidth utilization and meet the needs of different services. In the modern network environment, the rapid growth of data traffic and the complexity of network topology require network management systems to have higher flexibility and reliability to cope with dynamically changing network environments and business needs.

[0003] Currently, the existing practice is to use the Multiprotocol Label Switching (MPLS) protocol for efficient data traffic forwarding, and to apply static routing and static MAC address configuration in network management. Static routing controls the transmission path of data packets by manually setting the routing table, which is suitable for scenarios with little network topology change. Static MAC address configuration, on the other hand, prevents table overflow problems caused by dynamic learning by locking the MAC address of the switch port.

[0004] However, while the MPLS protocol can effectively forward traffic, existing practices often fail to fully utilize bandwidth in complex network environments, or the traffic forwarding paths are not flexible enough. Switches with statically configured MAC addresses may experience MAC address table overflow or delayed updates when facing dynamically changing network topologies, impacting network stability and performance. Static routing lacks flexibility; manually updating static routes when the network topology changes increases maintenance complexity and can lead to network communication interruptions or instability. Therefore, optimizing network traffic management in a more flexible and stable manner has become an urgent problem to be solved.

[0005] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0006] The main purpose of this application is to provide a traffic management method, apparatus, device, and storage medium, which aims to solve the technical problem of how to optimize network traffic management more flexibly and stably.

[0007] To achieve the above objectives, this application proposes a traffic management method, which includes:

[0008] Obtain the switch configuration address, switch configuration path, and data packets to be sent;

[0009] Based on the switch configuration address, the mapping relationship between each switch port and the corresponding target device is locked, and a static address table is determined;

[0010] Based on the switch configuration path settings, the routing path and priority corresponding to each data flow are set, and the static routing table is determined;

[0011] Based on the static address table and the static routing table, the network labels corresponding to the data packets to be sent are exchanged to determine the label exchange information;

[0012] The data packets to be sent are forwarded along the forwarding path identified by the tag exchange information to complete the routing traffic management.

[0013] In one embodiment, the step of determining the static address table by locking the mapping relationship between each switch port and the corresponding target device based on the switch configuration address includes:

[0014] Based on the switch configuration address, a corresponding static address is configured for each switch port to determine the static address information;

[0015] The static address information is mapped to the corresponding target device to lock the mapping relationship between each switch port and the corresponding target device, thus obtaining a static address table.

[0016] In one embodiment, the step of determining the static routing table based on the routing path and priority of each data flow configured by the switch includes:

[0017] Configure the static routes corresponding to the configuration paths of the switches according to the network topology, and determine the destination address, subnet mask and next-hop address;

[0018] Based on the destination address, the subnet mask, and the next-hop address, the routing path and priority corresponding to each data flow are set to obtain a static routing table.

[0019] In one embodiment, the step of exchanging the network labels corresponding to the data packets to be sent based on the static address table and the static routing table, and determining the label exchange information, includes:

[0020] Based on the network label assigned to the data packet to be sent, the label information is determined, including static label information and dynamic label information;

[0021] Based on the static address table and the static routing table, the data stream in the data packet to be sent is divided to determine the forwarding equivalence class division information;

[0022] The tag exchange information is obtained by exchanging the tag information and the forwarding equivalence class partitioning information.

[0023] In one embodiment, the step of dividing the data stream in the data packet to be sent based on the static address table and the static routing table to determine the forwarding equivalence class partitioning information includes:

[0024] Based on the addresses bound in the static address table and the ports divided by address, the first forwarding equivalence class division information and division result are determined;

[0025] Based on the partitioning results, the destination address or subnet mask configured in the static routing table is partitioned according to the destination address prefix to determine the second forwarding equivalence class partitioning information;

[0026] Forwarding equivalence class partitioning information is obtained based on the first forwarding equivalence class partitioning information and the second forwarding equivalence class partitioning information.

[0027] In one embodiment, the step of exchanging label exchange information based on the label information and the forwarding equivalence class partitioning information includes:

[0028] Obtain rule hit information and tag forwarding table;

[0029] Based on the rule hit information, the tag information is pushed into the forwarding equivalence class partitioning information to determine the integrated information;

[0030] The network tags in the integrated information are exchanged using the tag forwarding table to obtain tag exchange information.

[0031] In one embodiment, the step of forwarding the data packet to be sent along the forwarding path identified by the label switching information to complete the routing traffic management further includes:

[0032] Based on the forwarding path identified by the tag exchange information, the ports of the switch are mapped to the corresponding static address table to determine the mapped forwarding path information;

[0033] Based on the mapped forwarding path information, the next hop of the data packet is identified and the data packet to be sent is forwarded to determine the forwarding information;

[0034] Based on the forwarding information, a corresponding performance report is generated to complete the routing traffic management.

[0035] Furthermore, to achieve the above objectives, this application also proposes a flow management device, the flow management device comprising:

[0036] The acquisition module is used to acquire the switch configuration address, switch configuration path, and data packets to be sent.

[0037] The processing module is used to lock the mapping relationship between each switch port and the corresponding target device based on the switch configuration address, and determine the static address table;

[0038] The processing module is also used to set the routing path and priority of each data flow based on the switch configuration path, and to determine the static routing table;

[0039] The execution module is used to exchange the network labels corresponding to the data packets to be sent based on the static address table and the static routing table, and determine the label exchange information;

[0040] The execution module is also used to forward the data packet to be sent along the forwarding path identified by the tag exchange information, thereby completing the routing traffic management.

[0041] In addition, to achieve the above objectives, this application also proposes a traffic management device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the traffic management method as described above.

[0042] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the traffic management method described above.

[0043] One or more technical solutions proposed in this application have at least the following technical effects:

[0044] This embodiment proposes a traffic management method that obtains the switch configuration address, switch configuration path, and data packets to be sent; based on the switch configuration address, it locks the mapping relationship between each switch port and the corresponding target device to determine a static address table; based on the switch configuration path, it sets the routing path and priority corresponding to each data flow to determine a static routing table; based on the static address table and the static routing table, it exchanges the network labels corresponding to the data packets to be sent to determine label exchange information; and it forwards the data packets to be sent along the forwarding path identified by the label exchange information to complete the routing traffic management. This application determines the static address table by locking the mapping relationship between each switch port and the target device, avoiding dynamic learning to ensure that data packets can be accurately forwarded to the target device. It also sets the routing path and priority of each data flow to determine the static routing table, thereby achieving precise control and optimized path selection of data flows. Simultaneously, it exchanges the network labels of data packets and determines the label exchange information, forwarding data packets along the path identified by the label exchange information to complete the routing traffic management, achieving fast and efficient traffic forwarding, effectively reducing operation and maintenance costs, improving network stability and traffic optimization efficiency, and enhancing network scalability. Attached Figure Description

[0045] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0046] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1 This is a flowchart illustrating an embodiment of the traffic management method of this application.

[0048] Figure 2 This is a flowchart illustrating Embodiment 2 of the traffic management method of this application;

[0049] Figure 3 This is a schematic diagram of the module structure of the traffic management device according to an embodiment of this application;

[0050] Figure 4 This is a schematic diagram of the device structure of the hardware operating environment involved in the traffic management method in the embodiments of this application.

[0051] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0052] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0053] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0054] The main solution of this application embodiment is as follows: obtain the switch configuration address, switch configuration path, and data packet to be sent; based on the switch configuration address, lock the mapping relationship between each switch port and the corresponding target device, and determine a static address table; based on the switch configuration path, set the routing path and priority corresponding to each data flow, and determine a static routing table; based on the static address table and the static routing table, exchange the network label corresponding to the data packet to be sent, and determine the label exchange information; forward the data packet to be sent along the forwarding path identified by the label exchange information, and complete the routing traffic management.

[0055] In this embodiment, for ease of description, the following description will focus on identifying the traffic management device as the execution subject.

[0056] While the MPLS protocol can effectively forward traffic in existing technologies, it cannot fully utilize bandwidth or has insufficient traffic forwarding paths in complex network environments. Switches with static MAC address configurations may experience MAC address table overflow or delayed updates when facing dynamically changing network topologies, affecting network stability and performance. Static routing lacks flexibility, and manually updating static routes when the network topology changes increases maintenance difficulty and can lead to network communication interruptions or instability.

[0057] This application provides a solution that obtains the switch configuration address, switch configuration path, and data packets to be sent; based on the switch configuration address, it locks the mapping relationship between each switch port and the corresponding target device to determine a static address table; based on the switch configuration path, it sets the routing path and priority corresponding to each data flow to determine a static routing table; based on the static address table and the static routing table, it exchanges the network labels corresponding to the data packets to be sent to determine label exchange information; and it forwards the data packets to be sent along the forwarding path identified by the label exchange information to complete routing traffic management.

[0058] As can be seen from the above embodiments, this application determines a static address table by locking the mapping relationship between each switch port and the target device, avoiding dynamic learning to ensure that data packets can be accurately forwarded to the target device, and sets the routing path and priority of each data flow to determine a static routing table, so as to achieve precise control of data flow and optimized path selection. At the same time, the network labels of data packets are exchanged and the label exchange information is determined. Data packets are forwarded along the path identified by the label exchange information to complete routing traffic management, realize fast and efficient traffic forwarding, effectively reduce operation and maintenance costs, improve network stability and traffic optimization efficiency, and enhance network scalability.

[0059] Based on this, embodiments of this application provide a traffic management method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the traffic management method of this application.

[0060] In this embodiment, the traffic management method includes steps S10 to S50:

[0061] Step S10: Obtain the switch configuration address, switch configuration path, and data packet to be sent;

[0062] It should be noted that the switch configuration address is the unique identifier address of each switch in the network, used to determine the location and identity of the switch in the network. The switch configuration path is the switch path that a data packet takes from the source device to the destination device in the network, including each switch on the path and its port connection relationship. The data packet to be sent is the data that needs to be transmitted in the network, including information such as source address, destination address and data content.

[0063] It is understood that the switch configuration address can be used to accurately identify and locate specific switch devices, thereby enabling the management and configuration of the switch and ensuring that data can be correctly transmitted between switches. The switch configuration path describes the specific switch nodes and port order that data packets pass through during network transmission, similar to route planning on a map. It is used to transmit data packets in the network according to a predetermined path to ensure that the data can reach its destination efficiently and accurately. The data packet to be sent is the basic unit of network communication, carrying various data that users need to transmit, such as text, images, and videos. During data transmission, the switch will process and forward the data packets according to the configured path and rules to realize information interaction and communication between different devices.

[0064] In a specific embodiment, the network administrator can manually assign a static MAC address to each switch port through the network management interface or configuration script to obtain the switch configuration address. The obtained switch configuration address is then bound to a specific network device or host, and dynamic learning of new MAC addresses is no longer allowed to avoid MAC address table overflow. The administrator manually configures the switch path according to the network topology and stores it in the network device to obtain the switch configuration path. Data packets can be automatically obtained by the network device when receiving data, such as a switch or router. The network device receives data packets from the source device through its interface to obtain the data packet to be sent.

[0065] Step S20: Based on the switch configuration address, lock the mapping relationship between each switch port and the corresponding target device, and determine the static address table;

[0066] It should be noted that the static address table is a data structure used to lock the mapping relationship between each switch port and the corresponding target device. It is generated through static configuration to ensure that data packets can be accurately transmitted from the source device to the target device.

[0067] It is understood that by using the static address table, a fixed static MAC address can be assigned to each port and bound to a specific target device. These static MAC addresses are locked, and dynamic learning of new MAC addresses is no longer allowed, effectively avoiding MAC address table overflow. Furthermore, storing the static address table in the network device ensures that data packets can be accurately forwarded to the correct port based on the target MAC address, thereby improving network stability and data transmission reliability.

[0068] In a specific embodiment, a static MAC address configuration module can be used to configure and manage the static MAC address table in the switch. In scenarios with relatively fixed network topologies, such as enterprise internal networks or data centers, static MAC address configuration can be used to prevent overflow problems caused by dynamic learning of the MAC address table. Based on the switch configuration address, a corresponding static address is configured for each switch port, and the static address information is determined. That is, the administrator assigns a static MAC address to each port of the switch and locks it, prohibiting it from learning new MAC addresses. This avoids MAC address learning chaos or table overflow under high load conditions. The static address information is mapped to the corresponding target device, locking the mapping relationship between each switch port and the corresponding target device, thus obtaining the static address table. In other words, the static MAC address of each port is mapped to a specified network device or host. The network interface card of the device or host maintains the static MAC address at the network layer, ensuring that data traffic is always stably forwarded along a preset path. The preset path is a fixed forwarding path formed by mapping the MAC address of each port to the specified network device or host, which needs to be manually configured.

[0069] In one feasible implementation, step S20 may include steps A11 to A12:

[0070] Step A11: Configure a corresponding static address for each switch port based on the switch configuration address to determine the static address information;

[0071] It should be noted that the static address information refers to the MAC address assigned and locked to each port of the switch through static configuration.

[0072] It is understood that the static address information may include port identifier, static MAC address assigned to the port, and mapping relationship between the address and a specific network device or host, to ensure that data packets can be accurately forwarded from the source device to the target device through the specified switch port, avoid MAC address table overflow during dynamic learning, and improve network stability and data transmission reliability.

[0073] Step A12: Map the static address information to the corresponding target device, lock the mapping relationship between each switch port and the corresponding target device, and obtain the static address table.

[0074] It is understandable that the mapping relationship between each switch port and the corresponding target device is established by static configuration, which establishes a fixed association between a certain port of the switch and a specific target device, ensuring that data packets can be accurately forwarded from the source device to the intended target device through the specified port of the switch.

[0075] Step S30: Based on the switch configuration path, set the routing path and priority corresponding to each data flow, and determine the static routing table;

[0076] It should be noted that the static routing table is a data structure manually configured by the network administrator based on the network topology.

[0077] It is understood that the static routing table may include information such as destination IP address, subnet mask, next-hop address and priority, which is used to clarify the transmission path and priority of each data flow in the network, ensure that data packets are transmitted according to the preset path, avoid the instability of path selection in dynamic routing protocols, and improve network stability and data transmission reliability.

[0078] Additionally, it should be noted that since the static MAC address remains unchanged, data traffic can always be forwarded through the preset path, and the forwarding path will not be uncertain due to the dynamic change of the MAC address. Therefore, the static routing table needs to be manually configured to include this information, and the switch selects the next hop according to the static routing table when the data flow passes through.

[0079] In specific embodiments, the transmission path of data packets can be controlled by manually configuring the routing table. The static routing module manages the coordination between the MPLS protocol and static MAC configuration. The static routing table clearly defines the routing path and priority of each data flow. When the network topology is relatively fixed, it can provide more stable and predictable path control. Administrators manually configure static routes according to the network topology. The static routing table contains information such as destination IP address, subnet mask, and next-hop address. This routing information helps the switch select the best path when data flows through. Each static route is assigned a certain priority. When multiple feasible paths exist, the switch will select the most suitable path according to the priority to ensure the priority transmission of important data. At the same time, by combining the static routing table with the MPLS protocol label switching module, dynamic path selection can be performed during traffic forwarding to determine how data traffic enters the MPLS network and how MPLS forwards it efficiently and quickly based on labels, thereby optimizing the traffic management of the entire network and improving network performance and reliability.

[0080] In one feasible implementation, step S30 may include steps B11 to B12:

[0081] Step B11: Configure the static route corresponding to the switch configuration path according to the network topology, and determine the destination address, subnet mask and next hop address;

[0082] It should be noted that the destination address is the IP address of the target device that the data packet needs to reach. It is a key field in the static routing table used to identify the final destination of the data packet. The subnet mask is a 32-bit number used to determine which parts of the IP address belong to the network address and which parts belong to the host address. The next-hop address is the IP address of the next network device that the data packet needs to pass through before reaching its final destination.

[0083] It is understood that when a switch or router receives a data packet, it checks the destination IP address of the packet and matches it with the destination address in the static routing table to determine the transmission path of the data packet, ensuring that the data can accurately reach the specified target device. In the static routing table, the subnet mask is used in conjunction with the destination address to help network devices determine whether the data packet belongs to the same subnet. If the destination address of the data packet matches the subnet mask, it means that the data packet belongs to the same subnet and can be forwarded directly. If they do not match, the data packet needs to be forwarded to another network through the next-hop address, thereby achieving effective network segmentation and routing decisions. The next-hop address is an important field in the static routing table, used to control the forwarding of data packets. When the destination address of the data packet does not belong to the local subnet, the switch or router will forward the data packet to the device specified by the next-hop address. This device will continue to forward the data packet according to its routing table until the data packet finally reaches its destination, ensuring that the data packet can gradually approach and eventually reach the target device.

[0084] Step B12: Based on the destination address, the subnet mask, and the next-hop address, set the routing path and priority for each data flow to obtain a static routing table.

[0085] As we can understand, a routing path is the specific path a data packet takes when it is transmitted from a source device to a destination device in a network. It consists of a series of network devices and their port connections, ensuring that data packets can be transmitted from the source device to the destination device in a predetermined order, achieving efficient and stable traffic transmission. Priority is a value assigned to each routing path in a static routing table, used to select the optimal path when multiple feasible paths exist in the network. Setting priorities allows network administrators to optimize the transmission path of data packets according to different business needs and network conditions. When a data packet arrives at a network node, the node will select the path with the highest priority according to the priority information in the static routing table for forwarding, thereby ensuring that important data packets can be transmitted first, improving the overall performance and reliability of the network.

[0086] Step S40: Based on the static address table and the static routing table, exchange the network labels corresponding to the data packets to be sent, and determine the label exchange information;

[0087] It should be noted that the label exchange information mentioned above is information used in MPLS networks to identify and manage data flows through labels.

[0088] It is understandable that, based on the static address table and the static routing table, the network labels corresponding to the data packets to be sent are exchanged to determine the label exchange information. That is, through the cooperation of static MAC addresses and static routes, combined with the flexible forwarding of MPLS protocol labels, network traffic can be managed efficiently. Static MAC addresses and static routing tables reduce the dynamic learning process of network devices for data packets, greatly improving the processing speed of switches. The MPLS protocol optimizes path selection through label switching, improving network bandwidth utilization. In the implementation process, network traffic can avoid congested network areas and choose the best path for transmission. Through the MPLS traffic label control mechanism, different traffic in the network can be accurately allocated to different bandwidth resources, avoiding bandwidth waste. In the event of a link failure, the MPLS protocol can restore network connectivity by quickly reallocating labels, reducing the impact of network failures. For example, when LER detects a primary path interruption, it will immediately activate backup label 300 and forward it through LSR3 to ensure service continuity.

[0089] In a specific embodiment, an MPLS label switching module can be used, combined with static MAC addresses and static route configuration, to optimize the forwarding path of data flows. Based on the data packets to be sent, corresponding network labels are assigned, and label information is determined. This label information includes static label information and dynamic label information. That is, by assigning labels to each data packet entering the network, its forwarding path is identified, enabling the switch to quickly forward data packets based on labels without performing complex IP route lookups each time, thus significantly improving forwarding efficiency. Based on the static address table and the static routing table, the data flow in the data packets to be sent is divided, and forwarding equivalence class partitioning information is determined. That is, under the guidance of static routing, MPLS protocol labels can be reasonably allocated and applied. Through the network path indicated by the static route, MPLS labels will directly guide data packets to the correct switch port and path, thereby achieving more efficient traffic management. Based on the label information and the forwarding equivalence class partitioning information, label switching information is obtained. That is, by setting label priorities, the bandwidth allocation of different traffic flows can be flexibly controlled, effectively avoiding network congestion and ensuring that the bandwidth requirements of critical services are prioritized, thereby guaranteeing the overall performance and stability of the network.

[0090] Step S50: Forward the data packet to be sent along the forwarding path identified by the tag exchange information to complete the routing traffic management.

[0091] Understandably, after forwarding, network administrators can use a centralized control platform to manage routing traffic, that is, to uniformly manage static MAC addresses, static routes, and MPLS labels in the network, while monitoring network traffic and performance in real time and making corresponding adjustments quickly. Specifically, the centralized management platform can intuitively display LSP paths, label allocation status, and traffic statistics through a software interface, such as the real-time bandwidth utilization of label 200, making it convenient for administrators to view static MAC address tables, static routing tables, and MPLS label configuration details, achieving efficient centralized monitoring and management. The system will also automatically generate performance reports, provide network optimization suggestions, and assist administrators in adjusting static routing or label switching policies to ensure efficient and stable network operation. For example, when the traffic of a certain label exceeds 80% of the configured bandwidth, an SNMP alarm will be triggered. The system can automatically detect whether there is an overlay conflict between the static MAC address and the routing table, effectively avoiding forwarding loop problems.

[0092] In a specific embodiment, all hardware devices and functional modules are closely connected and coordinated to ensure that data flows can be efficiently transferred between modules. The hardware devices can be switches, routers, and MPLS label switches, and the functional modules can be static MAC address tables, static routing tables, and MPLS label switches. Specifically, when terminal A (MAC = 00:1A:2B:3C:4D:5E) sends data to terminal B, switch A directly forwards the data to port Gig1 / 0 / 1 according to the static MAC table and pushes label 100 onto it. When the data packet enters the MPLS network, LSR1 replaces label 100 with 200 and forwards it to LSR2. During the outgoing LER processing, LSR2 pops label 200 and forwards it according to the static routing table. The data is forwarded from the table to port Gig2 / 0 / 3 of switch B. Terminal B receives the data, and switch B's static MAC table matches the terminal B's MAC address to complete the data forwarding. This involves connecting the switch port to the static MAC address table and mapping the switch port to the static MAC address table to ensure that the data packet can be accurately forwarded according to the destination MAC address. Connecting the router to the static routing table allows the router to determine the next hop of the data packet based on the information in the static routing table, ensuring that the data is taken along the best path from the source device to the destination device. Connecting the MPLS switch to the MPLS label switching table allows the MPLS switch to quickly forward data packets from one node to another based on the label information in the MPLS label table, achieving fast data packet forwarding between nodes.

[0093] In one feasible implementation, step S50 may include steps C11 to C13:

[0094] Step C11: Based on the forwarding path identified by the tag switching information, map the port of the switch to the corresponding static address table to determine the mapped forwarding path information;

[0095] It should be noted that the mapping forwarding path information is generated by mapping the switch ports to the corresponding static address tables based on the forwarding path identified by the label switching information.

[0096] It is understood that the mapping and forwarding path information describes in detail the complete transmission path of the data packet from the source device to the target device in the network, including the switch ports, static MAC addresses and related tag information, to ensure that the data packet can be transmitted efficiently and accurately along the preset path.

[0097] Step C12: Based on the mapped forwarding path information, identify the next hop of the data packet and forward the data packet to be sent to determine the forwarding information;

[0098] It should be noted that the forwarding information is the specific forwarding information generated by the switch or router based on the tag exchange information and static address table during the transmission of data packets along the mapped forwarding path.

[0099] It is understood that the forwarding information is used to accurately forward data packets from one device to the next until they reach the target device. This includes the MAC address of the target device, the IP address of the next-hop device, tag information, and port information, thereby enabling network traffic management and optimization.

[0100] Step C13: Generate a corresponding performance report based on the forwarding information to complete routing traffic management.

[0101] It should be noted that the performance report is a detailed report generated based on forwarding information, used to evaluate network performance and the effectiveness of traffic management.

[0102] It is understood that the performance report may include corresponding performance indicators, traffic analysis, device performance, optimization suggestions, and problem diagnosis content. Among them, performance indicators may include transmission latency, packet loss rate, and throughput; traffic analysis may include the number of data packets and bandwidth usage; and device performance may include CPU and memory usage. This allows for the rapid location and resolution of problems, ensuring the efficient and stable operation of the network.

[0103] This embodiment proposes a traffic management method that obtains the switch configuration address, switch configuration path, and data packets to be sent; based on the switch configuration address, it locks the mapping relationship between each switch port and the corresponding target device to determine a static address table; based on the switch configuration path, it sets the routing path and priority corresponding to each data flow to determine a static routing table; based on the static address table and the static routing table, it exchanges the network labels corresponding to the data packets to be sent to determine label exchange information; and it forwards the data packets to be sent along the forwarding path identified by the label exchange information to complete the routing traffic management. This application addresses the technical challenge of optimizing network traffic management more flexibly and stably. Compared to existing technologies, it determines a static address table by locking the mapping relationship between ports and target devices, sets data flow routing paths and priorities to determine a static routing table, and then exchanges network labels on data packets to determine label exchange information. Finally, it forwards data packets to complete routing traffic management, effectively preventing MAC address table overflow, reducing maintenance costs, and improving network stability, flexibility, and bandwidth utilization. Through the effective collaboration between static routing and MPLS label switching, it significantly improves network traffic management efficiency and bandwidth utilization. The improved MAC address table management method, through optimized configuration of static MAC addresses, enhances network scalability, making traffic management more efficient and flexible, and adaptable to dynamic network environments and business needs.

[0104] Based on the first embodiment of this application, in the second embodiment of this application, the same or similar content as the first embodiment can be referred to the above description, and will not be repeated hereafter.

[0105] In this embodiment, refer to Figure 2 , Figure 2 This is a flowchart illustrating Embodiment 2 of the traffic management method of this application. Step S40 specifically includes steps S41 to S43:

[0106] Step S41: Assign a corresponding network label based on the data packet to be sent, and determine the label information, which includes static label information and dynamic label information;

[0107] It should be noted that the label information refers to the label and its related attributes assigned to each data flow in the MPLS network, which are used to identify and manage the transmission path of the data flow in the network.

[0108] It is understood that the tag information can be static tags, which are fixed in the network, avoiding the overhead of dynamic tag distribution protocols, such as static tags manually configured and assigned to specific data flows by the administrator, and the mapping relationship between tags and forwarding equivalence classes. It can also be dynamic tags, such as dynamically assigned tags and their priorities, used to optimize network performance and realize bandwidth allocation and priority control for different traffic. The tags are encapsulated according to a fixed encapsulation format, which represents the position and structure of the tag in the network data packet, thereby ensuring that the data packet can be forwarded quickly without performing complex IP routing lookups every time, thus achieving efficient traffic management and network optimization.

[0109] In a specific embodiment, based on the network topology and service requirements, the network administrator manually assigns static labels to specific data flows and establishes a mapping relationship between these static labels and Forwarding Equivalence Classes (FECs). This ensures that these labels remain fixed in the network, avoiding the uncertainty caused by dynamic changes. Furthermore, the system can automatically assign dynamic labels to data flows through the Dynamic Label Distribution Protocol (LDP) based on the real-time network status and traffic requirements. These dynamic labels can be adjusted according to network changes to optimize traffic paths.

[0110] Step S42: Based on the static address table and the static routing table, the data flow in the data packet to be sent is divided to determine the forwarding equivalence class division information;

[0111] It should be noted that the forwarding equivalence class partitioning information is obtained in the MPLS network by grouping data flows with the same forwarding characteristics into one class based on information in the static address table and static routing table.

[0112] It is understandable that when only a static address table exists, forwarding equivalence class partitioning is based on MAC address, defining the MAC address and port mapping relationship bound in the static MAC table as FEC. When only a static routing table exists, it is also based on MAC address, defining the MAC address and port mapping relationship bound in the static MAC table as FEC. When both static address table and static routing table are identified, it is a mixed mode: static MAC address is matched first, and if no match is found, it falls back to matching the IP prefix of the static route.

[0113] In a specific embodiment, the first forwarding equivalence class partitioning information and partitioning result are determined based on the addresses and ports bound in the static address table in the form of address partitioning; based on the partitioning result, the destination address or subnet mask configured in the static routing table is partitioned in the form of destination address prefix to determine the second forwarding equivalence class partitioning information; and forwarding equivalence class partitioning information is obtained based on the first forwarding equivalence class partitioning information and the second forwarding equivalence class partitioning information. In the ingress label edge router (LER), data flows are divided into forwarding equivalence classes (FECs) based on static routing tables and static MAC address tables. FECs can be divided by destination IP prefix, by MAC address, or in a hybrid mode. For example, by destination IP prefix, the destination IP / subnet mask configured in the static routing table directly corresponds to the FEC; by MAC address, the FEC is defined by the MAC address and port mapping relationship bound in the static MAC table; in hybrid mode, static MAC addresses are matched first, and if a match is not found, the system falls back to matching the IP prefix of the static route. Administrators manually configure the mapping relationship between labels and FECs through a centralized management platform to avoid the overhead of the dynamic label distribution protocol. Labels are inserted between the Layer 2 frame header and the Layer 3 packet header, with the following format: |Layer 2 frame header (MAC DA / SA)|Label (20 bits)|Exp (3 bits)|S (1 bit)|TTL (8 bits)|Layer 3 packet header|.

[0114] In one feasible implementation, step S42 may include steps D11 to D13:

[0115] Step D11: Based on the addresses bound in the static address table and the ports divided by address, determine the first forwarding equivalence class division information and division result;

[0116] It should be noted that the first forwarding equivalence class partitioning information is obtained by partitioning the data stream according to the address and port information bound in the static address table. The partitioning result is the specific FEC classification result obtained after partitioning.

[0117] It is understood that the first forwarding equivalence class (FEC) partitioning information is a process of grouping data flows with the same characteristics into one class by checking the source or destination MAC address of the data packets and combining it with the configuration of the switch port. For example, all data flows with the same destination MAC address and entering the same switch port can be partitioned into the same forwarding equivalence class (FEC). The partitioning result is that the corresponding data flows belong to the same FEC. For example, the partitioning result is that all data flows entering from port 1 with a destination MAC address of 00:1A:2B:3C:4D:5E are partitioned into FEC1, while data flows entering from port 2 with a destination MAC address of 00:1A:2B:3C:4D:5F are partitioned into FEC2, thereby selecting an appropriate forwarding path.

[0118] Step D12: Based on the partitioning result, the destination address or subnet mask configured in the static routing table is partitioned according to the destination address prefix to determine the second forwarding equivalence class partitioning information;

[0119] It should be noted that the second forwarding equivalence class partitioning information is obtained by partitioning the data flow according to the destination address prefix based on the destination address or subnet mask configured in the static routing table.

[0120] Understandably, based on the destination IP address and subnet mask in the static routing table, data flows with the same destination IP address prefix can be grouped into the same Forwarding Equivalence Class (FEC). For example, if a route with a destination IP address of 192.168.1.0 / 24 is configured in the static routing table, then all data flows with destination IP addresses belonging to that subnet will be grouped into the same FEC, ensuring that data flows are transmitted in the network according to the preset path, thereby improving network stability and data transmission reliability.

[0121] Step D13: Obtain forwarding equivalence class partitioning information based on the first forwarding equivalence class partitioning information and the second forwarding equivalence class partitioning information.

[0122] Understandably, the obtained forwarding equivalence class (FEC) partitioning information can ensure that each data flow is accurately classified into the corresponding forwarding equivalence class. During integration, features such as the MAC address and destination IP address prefix of the data flow are considered, and its final FEC affiliation is determined according to preset priority rules or network policies. The partitioning results are recorded in the network device's configuration file or database so that label allocation and packet forwarding operations can quickly and accurately reference them, thereby achieving efficient and stable traffic management and network performance optimization.

[0123] Step S43: Exchange the tag information and the forwarding equivalence class partitioning information to obtain tag exchange information.

[0124] It is understood that the label exchange information may include labels, forwarding equivalence classes (FECs), label forwarding tables, and label operations. A label is a short, fixed-length identifier, typically a 20-digit number, used to identify the FEC to which a data packet belongs. Labels are inserted between the Layer 2 and Layer 3 headers of the data packet, enabling the packet to be quickly identified and forwarded in the network. A FEC is a set of data packets with the same forwarding processing method. FECs are partitioned based on static routing tables and static MAC address tables, and can be partitioned by destination IP prefix, MAC address, or a combination of both. The label forwarding table is stored in the MPLS network device. One of the tables in the label forwarding table records the mapping relationship between labels and FECs, as well as label switching operations. When a data packet arrives at an MPLS device, the device will decide how to process and forward the data packet based on the information in the label forwarding table. Label operations include label pushing, switching, and popping operations. In the ingress label edge router (LER), after matching the FEC according to the static routing table and static MAC address table, the corresponding label is pushed onto the data packet. In the intermediate label switching router (LSR), label switching operations are performed according to the label forwarding table. In the egress LER, the label is popped and the data packet is forwarded to the target device according to the static MAC address table or static routing table.

[0125] In a specific embodiment, rule hit information and label forwarding table are obtained; based on the rule hit information, the label information is pushed into the forwarding equivalence class partitioning information to determine the integration information; the network labels in the integration information are exchanged using the label forwarding table to obtain label exchange information, that is, the ingress LER matches the FEC according to the static MAC / routing table and pushes the corresponding label. If the data flow does not hit the static rule, an alarm is triggered and the data is dropped. The intermediate LSR replaces the label according to the label forwarding table LIB, quickly forwards the data packet, and supports the last hop label popping PHP. The egress LER pops the label and forwards it to the target port according to the static MAC address table.

[0126] In one feasible implementation, step S43 may include steps E11 to E13:

[0127] Step E11: Obtain rule hit information and tag forwarding table;

[0128] It should be noted that the rule hit information is generated when the characteristics of a data packet match a preset rule. The characteristics of the data packet can be source / destination MAC address, source / destination IP address, etc. The preset rule can be a static address table, a static routing table, or an FEC partitioning rule. The label forwarding table is a data structure in the MPLS network that stores the mapping relationship between labels and forwarding paths.

[0129] It is understood that the rule hit information is used to determine the processing method of data packets, such as determining which FEC the data packet belongs to, or whether label switching is required. The rule hit information can ensure that network devices can accurately identify the forwarding path and processing strategy of data packets, thereby achieving efficient and stable traffic management. The label forwarding table can be used to process labeled data packets in the intermediate label switching router LSR. The label forwarding table contains information such as inbound label, outbound label, next-hop address and outbound interface.

[0130] Step E12: Based on the rule hit information, the tag information is pushed into the forwarding equivalence class partitioning information to determine the integrated information;

[0131] It should be noted that the integrated information is a data structure formed by integrating label information, forwarding equivalence class (FEC) partitioning information, and rule hit information.

[0132] It is understood that the integrated information set includes the label attributes of the data stream, the characteristics of the FEC to which it belongs, and the specific rules matched. The label attributes can be label values, priorities, TTL, etc., and the characteristics of the FEC to which it belongs can be destination MAC address, destination IP address prefix, etc., thereby ensuring that data packets can be transmitted efficiently and stably according to the preset path and strategy.

[0133] Step E13: Use the tag forwarding table to exchange the network tags in the integrated information to obtain tag exchange information.

[0134] Understandably, by referencing the label forwarding table, the network labels in the integrated information are exchanged. When a data packet arrives at the intermediate label switching router (LSR), the LSR checks the incoming label carried by the data packet and looks up the corresponding entry in the label forwarding table. After finding a matching entry, the LSR replaces the incoming label of the data packet with the outgoing label and forwards the data packet to the next LSR according to the next hop information and outgoing interface information in the table. This achieves fast label replacement and ensures that the data packet can be transmitted efficiently and stably along the preset path.

[0135] This embodiment proposes a traffic management method that assigns corresponding network labels to the data packets to be sent, determines label information including static and dynamic label information, divides the data flow in the data packets to be sent based on the static address table and the static routing table, and determines forwarding equivalence class partitioning information, and exchanges the label information and the forwarding equivalence class partitioning information to obtain label exchange information. This solves the technical problem of how to optimize network traffic management more flexibly and stably. Compared with existing technologies, this application assigns network labels containing static and dynamic label information to the data packets to be sent, divides the data flow based on the static address table and the static routing table to determine forwarding equivalence class partitioning information, and then exchanges labels to obtain label exchange information. This achieves flexible classification and efficient forwarding of data flows, improves traffic management efficiency and bandwidth utilization, reduces network congestion, ensures priority processing of important service traffic, and significantly improves the overall performance and stability of the network.

[0136] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the traffic management method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0137] This application also provides a flow management device, please refer to... Figure 3 The flow management device includes:

[0138] Module 10 is used to obtain the switch configuration address, switch configuration path, and data packet to be sent;

[0139] Processing module 20 is used to lock the mapping relationship between each switch port and the corresponding target device based on the switch configuration address, and determine the static address table;

[0140] The processing module 20 is also used to set the routing path and priority of each data flow based on the switch configuration path, and to determine the static routing table;

[0141] Execution module 30 is used to exchange the network labels corresponding to the data packets to be sent based on the static address table and the static routing table, and determine the label exchange information;

[0142] The execution module 30 is also used to forward the data packet to be sent along the forwarding path identified by the tag exchange information, thereby completing the routing traffic management.

[0143] The processing module 20 is also used to configure a corresponding static address for each switch port based on the switch configuration address, and to determine the static address information;

[0144] The static address information is mapped to the corresponding target device to lock the mapping relationship between each switch port and the corresponding target device, thus obtaining a static address table.

[0145] The processing module 20 is also used to configure the static route corresponding to the switch configuration path according to the network topology, and determine the destination address, subnet mask and next hop address;

[0146] Based on the destination address, the subnet mask, and the next-hop address, the routing path and priority corresponding to each data flow are set to obtain a static routing table.

[0147] The execution module 30 is further configured to allocate a corresponding network tag based on the data packet to be sent and determine tag information, wherein the tag information includes static tag information and dynamic tag information;

[0148] Based on the static address table and the static routing table, the data stream in the data packet to be sent is divided to determine the forwarding equivalence class division information;

[0149] The tag exchange information is obtained by exchanging the tag information and the forwarding equivalence class partitioning information.

[0150] The execution module 30 is also used to divide the addresses and ports bound in the static address table in the form of address division, and determine the first forwarding equivalence class division information and division result;

[0151] Based on the partitioning results, the destination address or subnet mask configured in the static routing table is partitioned according to the destination address prefix to determine the second forwarding equivalence class partitioning information;

[0152] Forwarding equivalence class partitioning information is obtained based on the first forwarding equivalence class partitioning information and the second forwarding equivalence class partitioning information.

[0153] The execution module 30 is also used to obtain rule hit information and tag forwarding table;

[0154] Based on the rule hit information, the tag information is pushed into the forwarding equivalence class partitioning information to determine the integrated information;

[0155] The network tags in the integrated information are exchanged using the tag forwarding table to obtain tag exchange information.

[0156] The execution module 30 is further configured to map the port of the switch to the corresponding static address table based on the forwarding path identified by the tag switching information, and determine the mapping forwarding path information;

[0157] Based on the mapped forwarding path information, the next hop of the data packet is identified and the data packet to be sent is forwarded to determine the forwarding information;

[0158] Based on the forwarding information, a corresponding performance report is generated to complete the routing traffic management.

[0159] The traffic management device provided in this application, employing the traffic management method described in the above embodiments, can solve the technical problem of how to optimize network traffic management more flexibly and stably. Compared with the prior art, the beneficial effects of the traffic management device provided in this application are the same as those of the traffic management method provided in the above embodiments, and other technical features in the traffic management device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0160] This application provides a traffic management device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the traffic management method in Embodiment 1 above.

[0161] The following is for reference. Figure 4 The diagram illustrates a structural schematic of a traffic management device suitable for implementing embodiments of this application. The traffic management device in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 4 The traffic management device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0162] like Figure 4As shown, the flow management device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.) that can perform various appropriate actions and processes according to a program stored in ROM (Read Only Memory) 1002 or a program loaded from storage device 1003 into RAM (Random Access Memory) 1004. RAM 1004 also stores various programs and data required for the operation of the flow management device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via bus 1005. Input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the flow management device to communicate wirelessly or wiredly with other devices to exchange data. While the figure shows flow management devices with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0163] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0164] The traffic management device provided in this application, employing the traffic management method described in the above embodiments, can solve the technical problem of how to optimize network traffic management more flexibly and stably. Compared with the prior art, the beneficial effects of the traffic management device provided in this application are the same as those of the traffic management method provided in the above embodiments, and other technical features of this traffic management device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0165] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0166] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0167] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the traffic management method in the above embodiments.

[0168] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0169] The aforementioned computer-readable storage medium may be included in the flow management device; or it may exist independently and not be assembled into the flow management device.

[0170] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by the traffic management device, the traffic management device: obtains the switch configuration address, the switch configuration path, and the data packet to be sent; based on the switch configuration address, it locks the mapping relationship between each switch port and the corresponding target device, and determines a static address table; based on the switch configuration path, it sets the routing path and priority corresponding to each data flow, and determines a static routing table; based on the static address table and the static routing table, it exchanges the network labels corresponding to the data packet to be sent, and determines label exchange information; and it forwards the data packet to be sent along the forwarding path identified by the label exchange information, thereby completing the routing traffic management.

[0171] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0172] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0173] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0174] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described traffic management method, thereby solving the technical problem of how to optimize network traffic management more flexibly and stably. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the traffic management method provided in the above embodiments, and will not be repeated here.

[0175] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A traffic management method, characterized in that, The method includes: Obtain the switch configuration address, switch configuration path, and data packet to be sent; Based on the switch configuration address, the mapping relationship between each switch port and the corresponding target device is locked, and a static address table is determined; Based on the switch configuration path settings, the routing path and priority corresponding to each data flow are set, and the static routing table is determined; Based on the static address table and the static routing table, the network labels corresponding to the data packets to be sent are exchanged to determine the label exchange information; The data packets to be sent are forwarded along the forwarding path identified by the tag exchange information to complete the routing traffic management.

2. The method as described in claim 1, characterized in that, The step of determining the static address table by locking the mapping relationship between each switch port and the corresponding target device based on the switch configuration address includes: Based on the switch configuration address, a corresponding static address is configured for each switch port to determine the static address information; The static address information is mapped to the corresponding target device to lock the mapping relationship between each switch port and the corresponding target device, thus obtaining a static address table.

3. The method as described in claim 1, characterized in that, The step of determining the static routing table based on the routing path and priority of each data flow configured by the switch includes: Configure the static routes corresponding to the configuration paths of the switches according to the network topology, and determine the destination address, subnet mask and next-hop address; Based on the destination address, the subnet mask, and the next-hop address, the routing path and priority corresponding to each data flow are set to obtain a static routing table.

4. The method as described in claim 1, characterized in that, The step of exchanging the network labels corresponding to the data packets to be sent based on the static address table and the static routing table, and determining the label exchange information, includes: Based on the network label assigned to the data packet to be sent, the label information is determined, including static label information and dynamic label information; Based on the static address table and the static routing table, the data stream in the data packet to be sent is divided to determine the forwarding equivalence class division information; The tag exchange information is obtained by exchanging the tag information and the forwarding equivalence class partitioning information.

5. The method as described in claim 4, characterized in that, The step of dividing the data stream in the data packet to be sent based on the static address table and the static routing table, and determining the forwarding equivalence class partitioning information includes: Based on the addresses bound in the static address table and the ports divided by address, the first forwarding equivalence class division information and division result are determined; Based on the partitioning results, the destination address or subnet mask configured in the static routing table is partitioned according to the destination address prefix to determine the second forwarding equivalence class partitioning information; Forwarding equivalence class partitioning information is obtained based on the first forwarding equivalence class partitioning information and the second forwarding equivalence class partitioning information.

6. The method as described in claim 4, characterized in that, The step of exchanging label information based on the label information and the forwarding equivalence class partitioning information to obtain label exchange information includes: Obtain rule hit information and tag forwarding table; Based on the rule hit information, the tag information is pushed into the forwarding equivalence class partitioning information to determine the integrated information; The network tags in the integrated information are exchanged using the tag forwarding table to obtain tag exchange information.

7. The method as described in claim 1, characterized in that, The step of forwarding the data packet to be sent along the forwarding path identified by the label switching information to complete the routing traffic management further includes: Based on the forwarding path identified by the tag exchange information, the ports of the switch are mapped to the corresponding static address table to determine the mapped forwarding path information; Based on the mapped forwarding path information, the next hop of the data packet is identified and the data packet to be sent is forwarded to determine the forwarding information; Based on the forwarding information, a corresponding performance report is generated to complete the routing traffic management.

8. A flow management device, characterized in that, The device includes: The acquisition module is used to acquire the switch configuration address, switch configuration path, and data packets to be sent. The processing module is used to lock the mapping relationship between each switch port and the corresponding target device based on the switch configuration address, and determine the static address table; The processing module is also used to set the routing path and priority of each data flow based on the switch configuration path, and to determine the static routing table; The execution module is used to exchange the network labels corresponding to the data packets to be sent based on the static address table and the static routing table, and determine the label exchange information; The execution module is also used to forward the data packet to be sent along the forwarding path identified by the tag exchange information, thereby completing the routing traffic management.

9. A flow management device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the traffic management method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the traffic management method as described in any one of claims 1 to 7.

Images