Method and device for real-time synchronization of uplink and downlink flow data in asymmetric routing scene

Abstract

The invention provides an asymmetric routing scene uplink and downlink flow data real-time synchronization method and device, and the method comprises the steps: enabling an index value to be equal to a target MAC address through the corresponding relation between an index value and a target MAC address, and enabling the index values of uplink flow information and downlink flow information which correspond to each other to be the same; in this way, the handshake association messages corresponding to the uplink flow information and the downlink flow information can be sent to the same target device so as to ensure that the handshake association messages which should be associated with each other can be identified and associated in the same network device, thereby ensuring that the network devices corresponding to the asymmetric routing scene can be associated with each other. According to the method and the device provided by the invention, the data synchronization is completed without sending each handshake association message to all network devices like the prior art, so that the handshake association messages needing to be associated with each other can be ensured to be sent to the same network device, and the performance occupation of association interaction between the devices is greatly reduced.

Description

Technical Field

[0001] This invention belongs to the field of network communication technology, and more specifically, relates to a method and apparatus for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario. Background Technology

[0002] In current internet data center, cloud computing, and edge computing environments, asymmetric routing has become a prevalent network architecture pattern. This pattern allows data packets to travel from source to destination and back through different network devices, links, or service providers, thereby fully utilizing multipath bandwidth, improving network reliability, and achieving load balancing. However, since the uplink and downlink traffic of the same data stream may flow through different physical or virtual network devices, traditional traffic analysis techniques based on single-point collection cannot obtain a complete session view. Therefore, it is necessary to correlate the network devices through which uplink and downlink traffic flows in order to obtain a complete session view subsequently.

[0003] Associating different network devices requires sending handshake messages to the same network device to match two handshake messages and identify the two network devices that need to be associated. In existing asymmetric routing scenarios, to ensure that two handshake messages are sent to the same network device, each network device typically broadcasts all uplink traffic session information (i.e., handshake messages) it processes to the entire network. Each network device must also receive and process broadcast information from all other network devices. This leads to a non-linear increase in the processing load, storage requirements, and network control plane bandwidth consumption of a single device with the number of devices. As the network scales up, system performance degrades sharply, and processing latency increases significantly. Ultimately, when the number of devices exceeds one hundred, the system often faces the risks of control plane storms, storage overflows, and complete failure of session synchronization, failing to meet the real-time monitoring needs of high-concurrency traffic in modern large-scale data centers or cloud environments.

[0004] Therefore, overcoming the shortcomings of the existing technology is an urgent problem to be solved in this technical field. Summary of the Invention

[0005] The problem this invention aims to solve is how to reduce the performance overhead caused by the association between network devices in asymmetric routing scenarios.

[0006] Firstly, a method for real-time synchronization of uplink and downlink traffic data in asymmetric routing scenarios is provided, including: Configure multiple network devices and collect the MAC addresses corresponding to all network devices to obtain an address list, and synchronize the address list to each network device; When the corresponding network device receives one-way traffic information, it parses the one-way traffic information to obtain the index value corresponding to the one-way traffic information, retrieves the target MAC address from the address list based on the index value, and takes the network device corresponding to the target MAC address as the target device. The corresponding network device sends a handshake association message to the target device; The target device obtains mutually matching handshake association messages and associates the network devices corresponding to the mutually matching handshake association messages with each other. Interconnected network devices communicate and synchronize directly.

[0007] Preferably, the step of parsing the one-way traffic information to obtain the index value corresponding to the one-way traffic information specifically includes: Obtain the quintuple information from the unidirectional traffic information; The quintuple information is hashed to obtain the corresponding hash value; The hash value is processed to obtain the index value.

[0008] Preferably, the process of processing the hash value to obtain the index value specifically includes: Obtain the number of network devices N, and use the remainder of the hash value divided by the number N as the index value.

[0009] Preferably, the corresponding network device sends a handshake association message to the target device, specifically including: The corresponding network device obtains source IP information, destination IP information, source port information, destination port information, and protocol type based on the unidirectional traffic information; Generate a corresponding session identifier based on the source IP information, destination IP information, source port information, destination port information, and protocol type; Generate a handshake-related message based on the session identifier; The corresponding network device sends the handshake association message to the corresponding target device based on the target MAC address.

[0010] Preferably, the target device acquires mutually matching handshake association messages, specifically including: The target device parses all received handshake-related messages and obtains the five-tuple information corresponding to all handshake-related messages; If the five-tuple information of two handshake association messages are symmetrical among all the handshake association messages received by the target device, then the two handshake association messages are matched.

[0011] Preferably, the step of associating the network devices corresponding to the mutually matched handshake association messages specifically includes: Obtain the MAC addresses of the uplink and downlink network devices corresponding to the matching handshake association messages; The target device forwards the handshake association message of the uplink network device to the downlink network device based on the MAC address of the downlink network device; The downlink network device records and associates the information of the uplink network device according to the received handshake association message, and replies with a confirmation association message to the uplink network device; The uplink network device records and associates the information of the downlink network device based on the received confirmation association message, so as to complete the mutual association between the uplink network device and the downlink network device.

[0012] Preferably, the configuration of multiple network devices specifically includes: Each network device is equipped with a synchronization interface; Each of the aforementioned synchronization interfaces is connected to the same switch; Different network devices exchange information through the switch.

[0013] Preferably, the different network devices exchange information through the switch, specifically including: The address list is synchronously stored in the switch; When different network devices exchange information, the sending network device sends the information to the switch. The switch obtains the receiving network device based on the MAC address carried in the information and the address list, and then sends the information to the receiving network device.

[0014] Secondly, a device for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario is provided, comprising 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, the instructions being executed by the processor to perform the aforementioned method for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario.

[0015] Thirdly, the present invention also provides a non-volatile computer storage medium storing computer-executable instructions that are executed by one or more processors to perform the method described in the first aspect.

[0016] Fourthly, a chip is provided, comprising: a processor and an interface for calling and running a computer program stored in memory, performing the method as described in the first aspect.

[0017] Fifthly, a computer program product containing instructions is provided that, when executed on a computer or processor, causes the computer or processor to perform the method as described in the first aspect.

[0018] Sixthly, a real-time synchronization system for uplink and downlink traffic data in an asymmetric routing scenario is provided, including the uplink and downlink traffic data real-time synchronization device for an asymmetric routing scenario as described in the second aspect, and using the uplink and downlink traffic data real-time synchronization method for an asymmetric routing scenario as described in the first aspect.

[0019] Unlike existing technologies, the present invention has at least the following beneficial effects: By establishing a mapping between index values ​​and target MAC addresses and leveraging the fact that the index values ​​of corresponding uplink and downlink traffic information are the same, handshake association messages corresponding to uplink and downlink traffic information can be sent to the same target device. This ensures that handshake association messages that should be associated with each other can be identified and associated in the same network device, thereby ensuring that network devices in asymmetric routing scenarios can be associated with each other and complete data synchronization. Unlike existing technologies, which require sending each handshake association message to all network devices to ensure that handshake association messages that need to be associated with each other are sent to the same network device, this greatly reduces the performance overhead of device association interactions. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments of the present invention will be briefly described below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0021] Figure 1 This is a flowchart of a method for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario provided by an embodiment of the present invention; Figure 2 This is a schematic diagram of an existing asymmetric scenario in an asymmetric routing scenario real-time synchronization method provided by an embodiment of the present invention; Figure 3 This is a flowchart illustrating the process of obtaining the index value in a real-time synchronization method for uplink and downlink traffic data in an asymmetric routing scenario, as provided in an embodiment of the present invention. Figure 4 This is an interactive flowchart of the target device in a real-time synchronization method for uplink and downlink traffic data in an asymmetric routing scenario provided by an embodiment of the present invention. Figure 5This is a schematic diagram illustrating the matching of handshake-related messages in a real-time synchronization method for uplink and downlink traffic data in an asymmetric routing scenario provided by an embodiment of the present invention. Figure 6 This is a schematic diagram illustrating the association between network devices in a real-time synchronization method for uplink and downlink traffic data in an asymmetric routing scenario provided by an embodiment of the present invention. Figure 7 This is a flowchart illustrating a method for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario, as provided in an embodiment of the present invention. Figure 8 This is a flowchart illustrating the interaction between different network devices in a real-time synchronization method for uplink and downlink traffic data in an asymmetric routing scenario, as provided in an embodiment of the present invention. Figure 9 This is a schematic diagram of a device for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario, provided in an embodiment of the present invention. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0023] Unless the context otherwise requires, throughout the specification and claims, the term "comprising" is interpreted as openly inclusive, meaning "including, but not limited to." In the description of the specification, terms such as "one embodiment," "some embodiments," "exemplary embodiment," "example," "specific example," or "some examples" are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this disclosure. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics mentioned may be included in any suitable manner in any one or more embodiments or examples; that is, although they may be incorporated into embodiments or examples using the above terms for reasons such as order and position, it does not limit them to be incorporated in combination by a single embodiment or example.

[0024] In the description of this invention, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of this disclosure, unless otherwise stated, "a plurality of" means two or more. Furthermore, for example, the description may use the prefix "A" or "B" to describe the same type of nouns as two independent entities. In this case, the corresponding features defined with "A" and "B" are used only to distinguish between similar entities and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features.

[0025] In the description of this invention, the expression “A and / or B” (where A and B are used to formally represent specific features) will be used. The corresponding expression includes the following three combinations: only A, only B, and a combination of A and B.

[0026] As used in this invention, “about,” “approximately,” or “approximately” includes the stated value and the average value within an acceptable range of deviation from a particular value, wherein the acceptable range of deviation is determined by a person skilled in the art taking into account the measurement under discussion and the error associated with the measurement of the particular quantity (i.e., the limitations of the measurement system).

[0027] Furthermore, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0028] Example 1: This embodiment provides a method for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario, such as... Figure 1 As shown, the method flow includes the following.

[0029] In step 101, multiple network devices are configured, and the MAC addresses corresponding to all network devices are collected to obtain an address list. The address list is then synchronized to each network device.

[0030] In this embodiment, the network device refers to the routing device through which data is transmitted between the host and the client during data interaction. In asymmetric routing scenarios, the network devices through which the host transmits data to the client and the network devices through which the client transmits data to the host are different. Therefore, traditional traffic analysis techniques based on single-point collection cannot simultaneously obtain complete uplink and downlink traffic information, and thus cannot obtain a complete session view. Therefore, it is necessary to associate the network devices through which uplink traffic passes (referred to as uplink network devices in this embodiment) and the network devices through which downlink traffic passes (referred to as downlink network devices in this embodiment) to enable complete monitoring of data at all times during data transmission. Figure 2 The image shows a partial schematic diagram of an asymmetric routing scenario.

[0031] In this embodiment, configuring the network devices involves defining and associating the interfaces of each network device with the switches used for synchronization, establishing information exchange channels between the network devices. The MAC address is used to represent the location information of each network device; the corresponding network device can be located through the MAC address to facilitate information exchange. All the MAC addresses corresponding to the network devices are included in the address list, which also includes the mapping relationship between the MAC addresses of each network device and their index values. This facilitates finding the MAC address of the corresponding network device based on the index value. The address list is then synchronized to all network devices, enabling each network device to know the location of the others, thus facilitating subsequent information exchange and transmission.

[0032] In step 102, when the corresponding network device receives one-way traffic information, it parses the one-way traffic information to obtain the index value corresponding to the one-way traffic information, obtains the target MAC address from the address list according to the index value, and takes the network device corresponding to the target MAC address as the target device.

[0033] In this embodiment, the corresponding network device can refer to any network device, which can be an uplink network device or a downlink network device. The one-way traffic information is either uplink traffic information or downlink traffic information, sent by the host or the client. When the corresponding network device is an uplink network device, the corresponding one-way traffic information is uplink traffic information; when the corresponding network device is a downlink network device, the corresponding one-way traffic information is downlink traffic information. For example, in the following scenario: host X sends first traffic information to network device A, network device A forwards the first traffic information to client Y, and after receiving the first traffic information, client Y sends second traffic information to network device B, and network device B forwards the second traffic information to host X; in the above scenario, the first traffic information is the uplink traffic information, and the second traffic information is the downlink traffic information. The one-way traffic information includes a five-tuple, which includes: source IP information, destination IP information, source port information, destination port information, and protocol type. Through the five-tuple information in the one-way traffic information, one can know all the device information that the one-way traffic information needs to pass through from output to reception. Furthermore, by parsing the one-way traffic information, an index value can be obtained. The five-tuple information corresponding to the one-way traffic information that is both uplink and downlink is symmetrical to each other. Therefore, the index values ​​obtained by hash calculation are the same, and the corresponding target MAC addresses are also the same, so the corresponding target devices are also the same.

[0034] In step 103, the corresponding network device sends a handshake association message to the target device.

[0035] If two one-way traffic messages are corresponding uplink and downlink traffic messages, the network devices corresponding to the two one-way traffic messages (i.e., the uplink network device and the downlink network device) will send handshake association messages to the same target device. The handshake association message contains the five-tuple information of the one-way traffic messages. The target device is a network device other than the corresponding uplink and downlink network devices. The target device can obtain the network device corresponding to the corresponding one-way traffic message based on the five-tuple information in the one-way traffic message, and determine whether different one-way traffic messages match each other, so as to complete the subsequent association between the corresponding uplink and downlink network devices.

[0036] In step 104, the target device obtains mutually matching handshake association messages and associates the network devices corresponding to the mutually matching handshake association messages.

[0037] In this embodiment, the network devices corresponding to the mutually matching handshake association messages are the uplink and downlink network devices that sent these handshake association messages and correspond to each other. The target device can forward the handshake association message to the corresponding uplink or downlink network device. The corresponding network device obtains the address information of the other network device that needs to be associated and sends a handshake message to the network device to respond and confirm, thus completing the mutual association between the corresponding uplink and downlink network devices.

[0038] In step 105, the interconnected network devices communicate and synchronize directly.

[0039] In existing technologies, to associate uplink and downlink network devices, the handshake association messages sent by the uplink and downlink network devices must be delivered to the same other network device to match the two handshake association messages. If the two handshake association messages are not delivered to the same network device, they cannot be matched. However, before associating, the corresponding uplink and downlink network devices cannot know the address of the network device to which the other's handshake association messages will be delivered. Therefore, to ensure that the two handshake association messages will be delivered to the same network device, existing technologies broadcast their respective handshake association messages to all other network devices to guarantee that the two handshake association messages will be delivered to the same network device, thus enabling the subsequent association between the uplink and downlink network devices.

[0040] In this embodiment, by establishing a correspondence between index values ​​and target MAC addresses, and by ensuring that the index values ​​of the corresponding uplink and downlink traffic information are identical, the handshake association messages corresponding to the uplink and downlink traffic information can be sent to the same target device. This guarantees that handshake association messages that should be associated with each other can be identified and associated in the same network device, thereby ensuring that network devices in asymmetric routing scenarios can be associated with each other and complete data synchronization. Unlike existing technologies, which require sending each handshake association message to all network devices to ensure that handshake association messages that need to be associated with each other can be sent to the same network device, this greatly reduces the performance overhead of device interactions.

[0041] Furthermore, in this embodiment, for one-way traffic information, it is necessary to parse it to obtain an index value, which is used to query the corresponding target MAC address to obtain the target device. Therefore, this embodiment also involves the following design: the parsing process of the one-way traffic information to obtain the index value corresponding to the one-way traffic information, such as... Figure 3 As shown, the method flow includes: In step 201, the quintuple information in the unidirectional flow information is obtained.

[0042] In this embodiment, the five-tuple information includes source IP information, destination IP information, source port information, destination port information, and protocol type. Through the five-tuple information, one can understand the output device, intermediate network devices, and final receiving device of the one-way traffic information during transmission, as well as some information content of the one-way traffic information, which facilitates the matching of handshake association messages and the association between network devices in the future.

[0043] In step 202, the quintuple information is hashed to obtain the corresponding hash value.

[0044] In step 203, the hash value is processed to obtain the index value.

[0045] In this embodiment, the step of processing the hash value to obtain the index value specifically includes: obtaining the number N of network devices, and using the remainder of the hash value divided by the number N as the index value.

[0046] In this embodiment, the index value ranges from [0, N-1]. When two single-line traffic information are each other’s uplink traffic information and downlink traffic information, the corresponding index values ​​are the same, so as to ensure that the handshake association messages sent by the corresponding uplink network devices and downlink network devices can be sent to the same target device.

[0047] Furthermore, in this embodiment, the handshake association message needs to carry relevant information about the one-way traffic information, so that the target device can understand the transmission path and network device corresponding to the one-way traffic information based on the handshake association message, and perform matching between handshake association messages. Therefore, this embodiment also involves the following design: the corresponding network device sends a handshake association message to the target device, such as... Figure 4 As shown, the method flow includes the following.

[0048] In step 301, the corresponding network device obtains the source IP information, destination IP information, source port information, destination port information, and protocol type based on the unidirectional traffic information.

[0049] In step 302, a corresponding session identifier is generated based on the source IP information, destination IP information, source port information, destination port information, and protocol type.

[0050] In step 303, a handshake association message is generated based on the session identifier.

[0051] In this embodiment, the handshake association message contains the session identifier.

[0052] In step 304, the corresponding network device sends the handshake association message to the corresponding target device according to the target MAC address.

[0053] Furthermore, in this embodiment, after the target device receives the handshake association message, it needs to parse the handshake association message to obtain the one-way traffic information and network devices corresponding to the handshake association message for subsequent matching and association. Therefore, this embodiment also involves the following design: the target device obtains mutually matching handshake association messages, such as... Figure 3 As shown, the method flow includes the following.

[0054] In step 401, the target device parses all received handshake-related messages and obtains the five-tuple information corresponding to all handshake-related messages.

[0055] In step 402, among all the handshake association messages received by the target device, if the five-tuple information of two handshake association messages is symmetrical, then the corresponding two handshake association messages are matched.

[0056] In this embodiment, since the five-tuple information of the corresponding uplink traffic information and downlink traffic information is symmetrical, the port device that sends uplink traffic information is also the port device that receives downlink traffic information, and vice versa. When the target device receives multiple handshake association messages, it parses the five-tuple information in each handshake association message to obtain symmetrical five-tuple information. It then matches the handshake association messages with symmetrical five-tuple information and, based on the network device that sent the matching handshake association messages, performs subsequent associations between network devices.

[0057] Furthermore, in this embodiment, after the target device matches the received handshake association messages, it needs to synchronously associate the network devices corresponding to the handshake association messages based on the matching results. The design is as follows: Associating the network devices corresponding to the mutually matched handshake association messages is as follows... Figure 6 As shown, the method flow includes the following.

[0058] In step 501, the MAC addresses of the uplink and downlink network devices corresponding to the mutually matching handshake association messages are obtained.

[0059] In step 502, the target device forwards the handshake association message of the uplink network device to the downlink network device based on the MAC address of the downlink network device.

[0060] In step 503, the downlink network device records and associates the information of the uplink network device according to the received handshake association message, and replies to the uplink network device with an acknowledgment association message.

[0061] In step 504, the uplink network device records and associates the information of the downlink network device according to the received confirmation association message, so as to complete the mutual association between the uplink network device and the downlink network device.

[0062] In this embodiment, after the uplink network device and the downlink network device establish an association, they can communicate directly with each other based on the MAC address of the other device to synchronize traffic information such as application identification results, packet counts and byte counts in real time.

[0063] To illustrate the above solution more clearly, the following example is used: Network device 1 and network device 2 respectively receive the corresponding one-way traffic information. Network device 1 and network device 2 correspond to each other, with network device 1 being the uplink network device and network device 2 being the downlink network device.

[0064] Network device 1 and network device 2 respectively parse the one-way traffic information they receive to obtain the five-tuple information, and obtain the corresponding index value based on the five-tuple information. They then search in the address list based on the index value to obtain the target MAC address of the target device. The target device corresponding to both network device 1 and network device 2 is network device N.

[0065] Network device 1 and network device 2 both send handshake association messages containing their respective five-tuple information to network device N. Network device N detects that the five-tuple information in the handshake association messages sent by network device 1 and network device 2 is symmetrical and matches the handshake association messages sent by network device 1 and network device 2.

[0066] Network device N forwards the handshake association message of network device 1 to network device 2 based on the MAC address of network device 2. Network device 2 records and associates the information of network device 1 based on the received handshake association message and replies to network device 1 with an acknowledgment association message. Network device 1 records and associates the information of network device 2 based on the received acknowledgment association message, thereby completing the mutual association between network device 1 and network device 2.

[0067] like Figure 7The diagram illustrates the association between network devices 1 and 2, and their subsequent communication. Once associated, network devices 1 and 2 synchronize protocol information based on protocol identification results and priorities. They periodically send heartbeat messages to the uplink network device to prevent its flow table from timing out first. Upon timing out, the uplink and downlink packet counts are sent to the uplink network device for generating a complete log.

[0068] It is worth mentioning that if a network device parses and processes the one-way traffic information it receives, and the MAC address found by the index number matches its own MAC address, then the network device does not need to initiate an association and can simply wait for the device receiving the traffic from the other direction to send the association information.

[0069] Furthermore, in this embodiment, the initial configuration of each network device involves the following design: the configuration of multiple network devices, such as... Figure 8 As shown, the method flow includes the following.

[0070] In step 601, each network device is configured with a synchronization interface.

[0071] In step 602, each of the synchronization interfaces is connected to the same switch.

[0072] In step 603, different network devices exchange information through the switch.

[0073] In this embodiment, the different network devices interact with each other through the switch, specifically including: the switch synchronously contains the address list; when different network devices interact with each other, the sending network device sends information to the switch, and the switch obtains the receiving network device based on the MAC address carried in the information and the address list, and sends the information to the receiving network device.

[0074] In summary, this embodiment uses a hash-distribution mechanism to redirect the handshake messages that would otherwise flood the entire network under broadcast methods to specific devices, significantly reducing the processing pressure on a single machine. For example, in a scenario with 60 devices, each creating 200,000 new sessions, and 50% of the traffic being one-way, if broadcast methods are used, each network device would need to process approximately 6 million pps of handshake association messages; while using the hash-direction method in this embodiment, each device only needs to process approximately 100,000 pps of handshake association messages. Including the associated confirmation messages, the total synchronization message volume per device is approximately 400,000 pps. Assuming an average message size of 70 bytes, the required bandwidth is approximately 224 Mbps. This bandwidth requirement is independent of the total number of devices, depending only on the number of new sessions and the proportion of one-way traffic per device, thus decoupling the system processing pressure from network scale and demonstrating good scalability.

[0075] In summary, this embodiment, through the above design, can achieve the following beneficial effects: 1. By using a hash modulo algorithm, the session association pressure across the entire network is evenly distributed to each network device, decoupling the number of synchronization messages processed by a single network device from the total number of network devices. In N network devices, the processing pressure of a single machine is reduced from the O(N) level of broadcast mode to the O(1) level, realizing the horizontal linear scalability of the system scale and perfectly supporting ultra-large-scale network deployment.

[0076] 2. Completely eliminates the control plane storm risk caused by broadcast flooding. Synchronization messages are forwarded through the data plane Layer 2, avoiding the occupation of control plane bandwidth and processing resources. Actual tests show that, in a scenario with 60 devices and 200,000 new sessions per device, the single-device synchronization message processing volume decreased from 6 million pps to 100,000 pps, a reduction of 98.3%.

[0077] 3. The hash-directed mechanism ensures a balanced distribution of processing load across devices, making system performance predictable. Regardless of network expansion, the processing load of a single device depends only on its actual traffic load, not the total number of devices in the network, providing a solid foundation for capacity planning and performance assurance.

[0078] 4. Synchronous communication uses point-to-point transmission with destination MAC addressing, which only occupies the necessary link bandwidth. Compared with the network-wide flooding of broadcast mode, this solution can reduce the synchronous bandwidth consumption to 1 / N of that of broadcast mode (N is the number of devices), significantly improving network resource utilization.

[0079] 5. Point-to-point communication eliminates the systemic risks caused by broadcast storms; faults are isolated at the level of a single session or device, preventing cascading failures. The hash mechanism possesses inherent load balancing capabilities, ensuring that a single point of failure will not cause a synchronized network-wide outage.

[0080] 6. The targeted forwarding path avoids the multi-hop flooding and queuing delays of the broadcast method. Synchronization messages are transmitted through the Layer 2 direct link, reducing the end-to-end synchronization latency from milliseconds to microseconds, which meets the needs of application scenarios with extremely high real-time requirements.

[0081] 7. No complex broadcast domain partitioning or multicast protocol configuration is required. Devices can establish synchronization channels using a pre-configured MAC address list, significantly reducing deployment complexity and maintenance costs. When expanding the system, only the MAC address list needs to be updated; no adjustments to network topology or protocol parameters are necessary.

[0082] 8. The solution in this embodiment is based on standard Layer 2 forwarding and hash calculation, does not depend on specific hardware or proprietary protocols, can be implemented on network equipment from different vendors, and has good heterogeneous network compatibility and deployment flexibility.

[0083] Example 2: Based on the real-time synchronization method for uplink and downlink traffic data in asymmetric routing scenarios provided in the foregoing embodiments, the present invention also provides an apparatus for implementing the real-time synchronization of uplink and downlink traffic data in asymmetric routing scenarios, such as... Figure 9 The diagram shown is a schematic representation of the device architecture according to an embodiment of the present invention. The device for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario of this embodiment includes one or more processors 41 and a memory 42. Figure 9 Take a processor 41 as an example.

[0084] Processor 41 and memory 42 can be connected via a bus or other means. Figure 9 Taking the example of a connection between China and Israel via a bus.

[0085] The memory 42, as a non-volatile computer-readable storage medium for real-time synchronization of uplink and downlink traffic data in asymmetric routing scenarios, can be used to store non-volatile software programs and non-volatile computer-executable programs, such as the real-time synchronization method for uplink and downlink traffic data in asymmetric routing scenarios in the aforementioned embodiments. The processor 41 executes various functional applications and data processing of the real-time synchronization device for uplink and downlink traffic data in asymmetric routing scenarios by running the non-volatile software programs, instructions, and modules stored in the memory 42, thereby realizing the real-time synchronization method for uplink and downlink traffic data in asymmetric routing scenarios in the aforementioned embodiments.

[0086] Memory 42 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 42 may include memory remotely located relative to processor 41, which can be connected to processor 41 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0087] The program instructions / modules are stored in memory 42. When executed by one or more processors 41, they perform the real-time synchronization method for uplink and downlink traffic data in the asymmetric routing scenario described in the foregoing embodiments. For example, they perform the above-described... Figures 1-5 The steps shown.

[0088] This invention also provides a non-volatile computer storage medium storing computer-executable instructions that are executed by one or more processors, for example... Figure 9One of the processors 41 enables the processors to execute the real-time synchronization method for uplink and downlink traffic data in the asymmetric routing scenario described in the foregoing embodiments, for example, to execute the steps shown in the figures above.

[0089] It is worth noting that the information interaction and execution process between the modules and units in the above-mentioned device and system are based on the same concept as the processing method embodiment of the present invention. For details, please refer to the description in the method embodiment of the present invention, and will not be repeated here.

[0090] Those skilled in the art will understand that all or part of the steps in the various methods of the embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0091] Those skilled in the art will readily understand that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for real-time synchronization of uplink and downlink traffic data in asymmetric routing scenarios, characterized in that, include: Configure multiple network devices and collect the MAC addresses corresponding to all network devices to obtain an address list, and synchronize the address list to each network device; When the corresponding network device receives one-way traffic information, it parses the one-way traffic information to obtain the index value corresponding to the one-way traffic information, retrieves the target MAC address from the address list based on the index value, and takes the network device corresponding to the target MAC address as the target device. The corresponding network device sends a handshake association message to the target device; The target device obtains mutually matching handshake association messages and associates the network devices corresponding to the mutually matching handshake association messages with each other. Interconnected network devices communicate and synchronize directly.

2. The asymmetric routing scenario uplink and downlink traffic data real-time synchronization method according to claim 1, characterized in that, The step of parsing the one-way traffic information to obtain the index value corresponding to the one-way traffic information specifically includes: Obtain the quintuple information from the unidirectional traffic information; The quintuple information is hashed to obtain the corresponding hash value; The hash value is processed to obtain the index value.

3. The method of claim 2, wherein the asymmetric routing scenario uplink and downlink traffic data real-time synchronization method is characterized by, The process of processing the hash value to obtain the index value specifically includes: Obtain the number of network devices N, and use the remainder of the hash value divided by the number N as the index value.

4. The asymmetric routing scenario uplink and downlink traffic data real-time synchronization method according to claim 1, characterized in that, The corresponding network device sends a handshake association message to the target device, specifically including: The corresponding network device obtains source IP information, destination IP information, source port information, destination port information, and protocol type based on the unidirectional traffic information; Generate a corresponding session identifier based on the source IP information, destination IP information, source port information, destination port information, and protocol type; Generate a handshake-related message based on the session identifier; The corresponding network device sends the handshake association message to the corresponding target device based on the target MAC address.

5. The method for real-time synchronization of uplink and downlink traffic data in asymmetric routing scenarios according to claim 1, characterized in that, The target device obtains mutually matching handshake association messages, specifically including: The target device parses all received handshake-related messages and obtains the five-tuple information corresponding to all handshake-related messages; If the five-tuple information of two handshake association messages are symmetrical among all the handshake association messages received by the target device, then the two handshake association messages are matched.

6. The method for real-time synchronization of uplink and downlink traffic data in asymmetric routing scenarios according to claim 1, characterized in that, The step of associating the network devices corresponding to the mutually matching handshake association messages specifically includes: Obtain the MAC addresses of the uplink and downlink network devices corresponding to the matching handshake association messages; The target device forwards the handshake association message of the uplink network device to the downlink network device based on the MAC address of the downlink network device; The downlink network device records and associates the information of the uplink network device according to the received handshake association message, and replies with a confirmation association message to the uplink network device; The uplink network device records and associates the information of the downlink network device based on the received confirmation association message, so as to complete the mutual association between the uplink network device and the downlink network device.

7. The method for real-time synchronization of uplink and downlink traffic data in asymmetric routing scenarios according to claim 1, characterized in that, The configuration of multiple network devices specifically includes: Each network device is equipped with a synchronization interface; Each of the aforementioned synchronization interfaces is connected to the same switch; Different network devices exchange information through the switch.

8. The method for real-time synchronization of uplink and downlink traffic data in asymmetric routing scenarios according to claim 7, characterized in that, The different network devices exchange information through the switch, specifically including: The address list is synchronously stored in the switch; When different network devices exchange information, the sending network device sends the information to the switch. The switch obtains the receiving network device based on the MAC address carried in the information and the address list, and then sends the information to the receiving network device.

9. A device for real-time synchronization of uplink and downlink traffic data in an asymmetric routing scenario, characterized in that, The method 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, the instructions being executed by the processor for performing the real-time synchronization method for uplink and downlink traffic data in an asymmetric routing scenario as described in any one of claims 1-8.

10. A non-volatile computer storage medium, characterized in that, The computer storage medium stores computer program instructions, which, when executed by one or more processors, implement the real-time synchronization method for uplink and downlink traffic data in an asymmetric routing scenario as described in any one of claims 1-8.

Images