New traffic processing method, device and equipment applied to in-cloud network

Abstract

The invention relates to a new traffic processing method and device applied to an intra-cloud network, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: acquiring source address data, destination address data, source port range data and destination port data of each network element node in a cloud network; according to the source address data, the destination address data, the source port range data and the destination port data, constructing an underlying network session table among the network element nodes of the in-cloud network; sending heartbeat messages among different network element nodes to update the underlying network session table; and in response to a new flow instruction, carrying out flow forwarding processing according to the underlying network session table. By adopting the method, the new traffic processing performance can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of cloud computing, and in particular to a new flow processing method and device applied to an intra-cloud network, computer equipment, a computer readable storage medium and a computer program product. BACKGROUND

[0002] The data center network in a cloud computing environment adopts a two-layer Spine-Leaf structure based on a CLOS network topology to carry traffic within a same data center, and separates a control plane from a forwarding plane through an SDN architecture.

[0003] When forwarding traffic of a tenant, a cloud network forwards a user's packet between different network elements. Generally, an overlay method is used to carry service packets between different network elements in an intra-cloud network. A typical encapsulation protocol is VXLAN or NVGRE.

[0004] In a special environment of an intra-cloud network, a source IP and a destination IP of an underlay are fixed. In this forwarding model, the new flow rate of a service packet is initially constrained by the new flow rate of an outer packet. In particular, traffic of multiple network elements converges on a single network element, which limits the performance of new flow of a tenant. When a tenant tests new flow, packet loss occurs, which externally appears as a bottleneck in new flow performance, resulting in a decrease in the performance of new flow processing and failing to meet the requirement of high-performance new flow processing in an intra-cloud network. SUMMARY

[0005] Therefore, it is necessary to provide a new flow processing method, device, computer equipment, computer readable storage medium and computer program product applied to an intra-cloud network, which can improve the performance of new flow processing.

[0006] In a first aspect, the present application provides a new flow processing method applied to an intra-cloud network, comprising:

[0007] obtaining source address data, destination address data, source port range data and destination port data of each network element node in the intra-cloud network;

[0008] constructing an underlying network session table between each of the network element nodes in the intra-cloud network according to the source address data, the destination address data, the source port range data and the destination port data;

[0009] sending heartbeat packets between different network element nodes to update the underlying network session table;

[0010] performing traffic forwarding processing according to the underlying network session table in response to a new traffic instruction.

[0011] In one embodiment, the obtaining of the source address data, the destination address data, the source port range data and the destination port data of each network element node in the intra-cloud network comprises:

[0012] obtaining network topology configuration information and network element node address information of each network element node in the intra-cloud network;

[0013] identifying network element node types of each of the network element nodes and a bearer protocol type of the intra-cloud network according to the network topology configuration information; the network element node types include edge network element nodes and center network element nodes;

[0014] extracting service Internet protocol addresses of the edge network element nodes to obtain the source address data, and extracting service Internet protocol addresses of the center network element nodes to obtain the destination address data according to the network element node address information;

[0015] obtaining the destination port data and the source port range data according to the bearer protocol type.

[0016] In one embodiment, the identifying of the network element node types of each of the network element nodes according to the network topology configuration information comprises:

[0017] parsing network element connection relationships in the network topology configuration information and counting a connection degree value of each of the network element nodes; the connection degree value represents a number of network element nodes directly connected to the network element node;

[0018] determining a network element node with a connection degree value greater than a preset connection degree threshold as a center network element node;

[0019] determining a network element node with a connection degree value less than or equal to the preset connection degree threshold as an edge network element node.

[0020] In one of the embodiments, the sending of the heartbeat message between different network element nodes to update the underlying network session table comprises:

[0021] extracting a session record to be activated from the underlying network session table, and constructing a heartbeat message data packet according to the session record;

[0022] sending the heartbeat message data packet from the corresponding edge network element node to the central network element node;

[0023] monitoring the session table update response of each network element node on the transmission path of the heartbeat message data packet;

[0024] updating the activation state of the corresponding session record in the underlying network session table according to the session table update response.

[0025] In one of the embodiments, the sending of the heartbeat message data packet from the corresponding edge network element node to the central network element node comprises:

[0026] obtaining a current running phase; the current running phase includes an initialization phase, a stable running phase and a low-load running phase;

[0027] in the case that the current running phase is the initialization phase, setting the heartbeat sending time interval as a first preset interval;

[0028] in the case that the current running phase is the stable running phase, setting the heartbeat sending time interval as a second preset interval; the second preset interval is greater than the first preset interval;

[0029] in the case that the current running phase is the low-load running phase, setting the heartbeat sending time interval as a third preset interval; the third preset interval is greater than the second preset interval;

[0030] creating a heartbeat sending timing task according to the heartbeat sending time interval;

[0031] executing the timing task to send the heartbeat message data packet from the corresponding edge network element node to the central network element node.

[0032] In one of the embodiments, the method further comprises:

[0033] obtaining network performance index data of the transmission link between the edge network element node and the central network element node, and calculating a load evaluation value according to the network performance index data;

[0034] comparing the load evaluation value with a load threshold value corresponding to the current running phase to obtain a load evaluation result;

[0035] adjust the heartbeat sending time interval according to the load evaluation result.

[0036] In a second aspect, the present application further provides a new flow processing device applied to an intra-cloud network, comprising:

[0037] a data acquisition module, configured to acquire source address data, destination address data, source port range data and destination port data of each network element node in the intra-cloud network;

[0038] a data processing module, configured to construct an underlying network session table between each network element node in the intra-cloud network according to the source address data, the destination address data, the source port range data and the destination port data;

[0039] a data updating module, configured to send heartbeat messages between different network element nodes to update the underlying network session table;

[0040] a flow forwarding module, configured to perform flow forwarding processing according to the underlying network session table in response to a new flow instruction.

[0041] In a third aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the first aspect when executing the computer program.

[0042] In a fourth aspect, the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the steps of the first aspect.

[0043] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, and the computer program is executed by a processor to implement the steps of the first aspect.

[0044] The new traffic processing method, device, computer equipment, computer readable storage medium and computer program product applied to the intra-cloud network, by obtaining the source address data, destination address data, source port range data and destination port data of each network element node in the intra-cloud network, the network parameters are collected and prepared in advance, avoiding the delay caused by obtaining these information when actually processing the traffic, according to the source address data, destination address data, source port range data and destination port data, the bottom layer network session table is constructed between each network element node in the intra-cloud network, realizing the transition from the traditional passive session establishment to the active session pre-establishment, by constructing the session table in advance, the subsequent new traffic can directly use the existing session record for forwarding, thereby bypassing the processing delay caused by triggering the session establishment of the new traffic in the traditional way, the heartbeat message is sent between different network element nodes to update the bottom layer network session table, keeping the active state of each session record in the pre-established session table, preventing the session from aging and invalidating due to long time of non-use, ensuring that when the real new traffic comes, the corresponding session channel is still available, avoiding the performance loss caused by re-triggering the session establishment process due to the session invalidation. In response to the new traffic instruction, the traffic forwarding processing is performed according to the bottom layer network session table, when the new traffic arrives, the matching session record can be found in the pre-established bottom layer network session table, and the traffic forwarding processing is directly performed without experiencing the session establishment waiting process in the traditional way, thereby improving the processing performance of the new traffic. BRIEF DESCRIPTION OF DRAWINGS

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description only some embodiments of the present application, and for those skilled in the art, other related drawings can be obtained without creative labor on the basis of these drawings.

[0046] Figure 1 The application environment diagram of the new traffic processing method applied to the intra-cloud network in an embodiment;

[0047] Figure 2 The flowchart of the new traffic processing method applied to the intra-cloud network in an embodiment;

[0048] Figure 3 The star topology structure diagram of the intra-cloud network in an embodiment;

[0049] Figure 4 The flowchart of the new traffic processing method applied to the intra-cloud network in another embodiment;

[0050] Figure 5A structural block diagram of a new traffic processing device applied to an intra-cloud network in an embodiment;

[0051] Figure 6 An internal structural diagram of a computer device in an embodiment. DETAILED DESCRIPTION

[0052] For the purpose, technical solutions and advantages of the present application to be clearer, the present application is further described in detail below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0053] It should be noted that the terms "first", "second", etc. used in the present application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "include" and "have" and any variations thereof used in the present application are intended to cover non-exclusive inclusion. The term "multiple" used in the present application refers to two and more than two. The term "and / or" used in the present application refers to one of the options or any combination of multiple options.

[0054] The new traffic processing method applied to an intra-cloud network provided by the embodiments of the present application can be applied to an application environment as shown in Figure 1 . In which, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data required to be processed by the server 104. The data storage system can be integrated on the server 104, or placed on the cloud or other network servers. Among them, the terminal 102 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, unmanned aerial vehicles, low-altitude flying vehicles, Internet of Things devices and portable wearable devices. The Internet of Things device can be a smart speaker, a smart TV, a smart air conditioner, a smart vehicle device, a projection device, etc. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, etc. The head-mounted device can be a virtual reality (VR) device, an augmented reality (AR) device, smart glasses, etc. The server 104 can be a standalone physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0055] In an exemplary embodiment, as shown in Figure 2 , a new traffic processing method applied to an intra-cloud network is provided. Taking the server 104 in Figure 1 as an example, the method includes the following steps S202 to S206. Among them:

[0056] In step S202, source address data, destination address data, source port range data and destination port data of each network element node in the cloud-in network are acquired.

[0057] The cloud-in network refers to a virtual network constructed in a cloud computing environment, and provides communication and data transmission services for virtual machines, containers and other resources in the cloud-in network through software-defined networking and network virtualization technology. The network element node is a basic component unit of the cloud-in network, and can include various network devices and forwarding devices. The source address data refers to the Internet Protocol address information of the sender of a network packet, and the destination address data refers to the Internet Protocol address information of the receiver of the network packet. The source port range data refers to a set of source port numbers that can be used to identify different data flows in the network transmission process, and the destination port data refers to a fixed port number used by a bearing protocol.

[0058] Exemplarily, the server 104 can acquire network topology configuration information and network element node address information of each network element node in the cloud-in network; identify the network element node type of each network element node and the bearing protocol type of the cloud-in network according to the network topology configuration information; the network element node type includes an edge network element node and a center network element node; the service Internet Protocol address of the edge network element node is extracted to obtain the source address data, and the service Internet Protocol address of the center network element node is extracted to obtain the destination address data according to the network element node address information; the destination port data and the source port range data are obtained according to the bearing protocol type.

[0059] The network topology configuration information describes the connection relationship and hierarchical structure between each network element node in the cloud-in network, and the network element node address information contains the network interface configuration and the corresponding Internet Protocol address of each network element node. The bearing protocol type refers to the protocol type used by the cloud-in network to encapsulate and transmit service packets, such as overlay network protocols such as VXLAN (Virtual eXtensible Local Area Network) or NVGRE (Network Virtualization using Generic Routing Encapsulation).

[0060] Exemplarily, the server 104 can obtain the network topology configuration information and the network element node address information of each network element node by accessing the in-cloud network management system or the configuration database, parse the connection relationship data between each network element node recorded in the network topology configuration information, and identify the network element node types by analyzing the connection degrees of each network element node. The server 104 can also count the number of direct connections of each network element node with other network element nodes, identify the network element nodes with higher connection degrees as central network element nodes, and identify the network element nodes with relatively lower connection degrees as edge network element nodes, thereby completing the analysis and classification of the in-cloud network topology structure. The server 104 can also read the type identifier of the currently used bearer protocol of the in-cloud network from the network topology configuration information, and determine whether to use the VXLAN protocol, the NVGRE protocol, or other custom overlay encapsulation protocol.

[0061] Further, the server 104 can extract the service Internet protocol addresses of each network element node based on the network element node address information. For the edge network element node, the server 104 can read the main interface Internet protocol address carrying service traffic from the network interface configuration data thereof, and then organize and form a source address data set. For the central network element node, the server 104 can extract the main interface Internet protocol address thereof, and form a destination address data set. The server 104 can also verify the correctness of the format and network connectivity of the extracted Internet protocol addresses, to ensure that these address data can be correctly used in the subsequent session table construction.

[0062] Further, the server 104 can determine the destination port data according to the identified bearer protocol type. The server 104 can generate the source port range data according to the performance parameters of the network element node and the expected service traffic demand, can calculate the required number of source ports based on the new connection processing capacity and the number of concurrent connection supports of the network element node, and preferentially select the port numbers with higher historical usage frequency to constitute the source port range data.

[0063] Exemplarily, as Figure 3As shown, the server 104 can adopt a processing mode based on a star topology to obtain the source address data, the destination address data, the source port range data and the destination port data, i.e., a configuration mode in which multiple edge network elements are connected to a single center network element. The server 104 can determine, by analyzing the connection relationship in the network topology configuration information, that the network element A, the network element B, the network element D and the network element E are edge network element nodes, and that the network element C is a center network element node. The server 104 can extract the service Internet protocol address of the edge network element node as the source address data, and extract the service Internet protocol address of the center network element node as the destination address data. The server 104 sets the destination port data according to the VXLAN bearer protocol used by the in-cloud network. Considering the performance bottleneck characteristics of the star topology center network element, the server 104 can calculate the required number of source ports according to the new flow processing capacity of the center network element, for example, when the new rate of the center network element is forty thousand connections per second and there are four edge network elements, the server 104 calculates the number of source ports required by each edge network element, and allocates a corresponding source port sub-range to each edge network element within the available port range to form complete source port range data.

[0064] In step S204, a bottom network session table is constructed between the network element nodes in the in-cloud network according to the source address data, the destination address data, the source port range data and the destination port data.

[0065] The bottom network session table is a data structure that records the communication session information between different network element nodes in the in-cloud network, and can include four-tuple information of the source Internet protocol address, the destination Internet protocol address, the source port and the destination port, as well as session management attributes such as session state, creation time and aging time. The session record is a basic data unit in the bottom network session table, and each session record can correspond to a specific network communication path. The session identifier is a numerical value or a string used to uniquely identify each session record, and the session state includes identifiers of different stages such as a to-be-established state, an activated state and a need-refresh state. The four-tuple information is a combination of parameters used to identify a unique data flow in network communication, which can be composed of elements such as the source Internet protocol address, the source port, the destination Internet protocol address and the destination port.

[0066] Exemplarily, the server 104 can create a data structure of the underlying network session table and pre-allocate sufficient storage space for the underlying network session table. According to the number of addresses in the source address data set, the number of addresses in the destination address data set, and the number of ports in the source port range data, the server 104 can calculate the total number of session records to be created, and generate all possible four-tuple combinations through multi-loop traversal. The server 104 can traverse each edge network element node address in the source address data set. For each source address, the server 104 can continue to traverse each central network element node address in the destination address data set to form a paired combination of source address and destination address. For each combination of source address and destination address, the server 104 can traverse each available source port number in the source port range data to form a complete four-tuple record by combining the current source address, source port number, destination address, and destination port data. The server 104 can assign a unique session identifier to each generated four-tuple record, using an incremental sequence number or a hash value based on the four-tuple content as the identifier, to ensure that each session record can be uniquely identified and quickly located.

[0067] Further, the server 104 can set the session state of the newly created session record to a to-be-established state, indicating that the session path has not been activated through actual network message transmission. The server 104 can record the creation timestamp of the session record, marking the generation time of the four-tuple session in the underlying network session table. The server 104 can set an initial aging time for each session record, which is equal to the creation time plus a preset session retention duration. The server 104 can also initialize a statistical information field for each session record, including the number of heartbeat transmissions, the number of successful activations, the number of traffic usage times, and other data for performance monitoring and optimization decision-making. Further, the server 104 can calculate a hash value according to the four-tuple information and distribute the session record to a hash table. For possible hash conflicts, the server 104 can use a chain hash or open addressing conflict resolution method to ensure the integrity of data storage.

[0068] Exemplarily, as Figure 3As shown, the server 104 can employ a batched session table construction manner for the star topology. In this implementation, the server 104 can identify the communication paths to be established between the edge network elements A, B, D, E and the center network element C, and calculate the total number of session records to be created. Considering the processing capability limit of the center network element of the star topology, the server 104 can employ a gradual session table construction strategy to process all the four-tuple records to be created in multiple batches. The server 104 can create session records for high-priority port ranges, which can be port numbers with high historical usage frequency or expected traffic density. During the construction process, the server 104 can monitor the system resource usage, dynamically adjust the batch size and construction speed according to the memory usage and processor load, and ensure that the session table construction process does not adversely affect the normal operation of the system.

[0069] Through the above steps, the server 104 successfully constructs the underlying network session table containing all necessary four-tuple information, establishes a complete session mapping relationship for the communication between the network element nodes in the cloud network, and realizes a fundamental change from the traditional on-demand session establishment mode to the pre-constructed session table mode. By creating session records containing complete four-tuple information in advance, the subsequent new traffic processing can directly utilize the existing session table for fast path lookup and forwarding decision, avoiding the delay overhead caused by real-time session establishment. At the same time, by employing an efficient data structure and index, the session table ensures fast access performance.

[0070] Step S206, sending heartbeat messages between different network element nodes to update the underlying network session table.

[0071] Among them, the heartbeat message refers to a control message periodically sent between network element nodes, which can be used to maintain and update the network session state and keep the activity of the communication path. Illustratively, the server 104 can extract the session records to be activated from the underlying network session table, and construct a heartbeat message data packet according to the session records; send the heartbeat message data packet from the corresponding edge network element node to the center network element node; monitor the session table update response of each network element node on the transmission path of the heartbeat message data packet; and update the activation state of the corresponding session record in the underlying network session table according to the session table update response.

[0072] Among them, the heartbeat message data packet is a complete data packet structure formed after the heartbeat message is encapsulated by the network protocol, which contains outer network encapsulation information and inner heartbeat payload information. The session table update response refers to the state confirmation information returned by the network device after receiving the heartbeat message and creating or updating its local session table.

[0073] Exemplarily, the server 104 can scan and extract session records with a state of to-be-established from the underlying network session table. The server 104 can traverse the entire session table, identify all four-tuple records that need to be activated, sort the records according to the priority rules, and form a queue of session records to be processed. The server 104 determines an upper limit of the number of records in a single heartbeat sending batch according to the current system load and network resource status, to avoid sending too many heartbeat messages at the same time and impacting the network. The server 104 can select an appropriate number of session records from the sorted queue to be processed as the current batch.

[0074] Further, the server 104 can construct corresponding heartbeat message data packets based on the selected session records. For each session record to be activated, the server 104 can extract its four-tuple information, including the source Internet protocol address, the source port, the destination Internet protocol address, and the destination port, to build the inner load information of the heartbeat message. The load can include control information such as a heartbeat sequence number, a heartbeat type identifier, a session keep-alive instruction, and a timestamp. The server 104 can use the carrying protocol of the intranet network to perform outer encapsulation on the inner load. When the carrying protocol is VXLAN, the server 104 can add a corresponding protocol header according to the VXLAN protocol format to form a complete heartbeat message data packet. The server 104 can assign a unique sequence number to each heartbeat message for subsequent response matching and state tracking.

[0075] In the process of sending the heartbeat message packet from the corresponding edge network element node to the center network element node, the server 104 can obtain the current running stage, which includes the initialization stage, the stable running stage, and the low-load running stage. If the current running stage is the initialization stage, the heartbeat sending time interval is set to the first preset interval. If the current running stage is the stable running stage, the heartbeat sending time interval is set to the second preset interval. The second preset interval is greater than the first preset interval. If the current running stage is the low-load running stage, the heartbeat sending time interval is set to the third preset interval. The third preset interval is greater than the second preset interval. According to the heartbeat sending time interval, a heartbeat sending timing task is created. The timing task is executed to send the heartbeat message packet from the corresponding edge network element node to the center network element node. The network performance index data can include link bandwidth utilization, network delay value, packet loss rate statistical information, and other parameters for measuring network transmission quality. The server 104 can determine whether it is in the initialization stage, the stable running stage, or the low-load running stage by analyzing the system startup time, the current load level, and the network traffic pattern. When the system is in the initialization stage, the server 104 can set a shorter heartbeat sending time interval to quickly establish the required network session. When the system is in the stable running stage, the server 104 can set a medium heartbeat sending time interval to balance session maintenance requirements and resource consumption. When the system is in the low-load running stage, the server 104 can set a longer heartbeat sending time interval to reduce unnecessary network overhead. The server 104 can create a timing task according to the determined heartbeat sending time interval. The timing task can periodically trigger the sending operation of the heartbeat message. The server 104 can execute the timing task to send the heartbeat message packet from the corresponding edge network element node to the target center network element node in sequence according to the set time interval, ensuring the ordered transmission of the heartbeat message.

[0076] In the process of sending the heartbeat message, the server 104 can continuously monitor the session table update response of each network device on the transmission path. The server 104 can identify the complete transmission path of the heartbeat message from the source edge network element node to the destination center network element node, and obtain the list of all intermediate network devices on the path. The server 104 can send a session state query request to these network devices to obtain their processing results of the received heartbeat message. The session state response data returned by the server 104 can include the existence state, active state, and last update time of the corresponding four-tuple record in the local session table of the device. The server 104 can parse the session state response data to determine whether the heartbeat message successfully triggers the session record creation or aging time update operation of each network device.

[0077] Further, the server 104 can also implement network load-aware heartbeat sending adjustment. The server 104 can also acquire network performance index data of a transmission link between an edge network element node and a central network element node, and calculate a load evaluation value according to the network performance index data. The server 104 can compare the load evaluation value with a load threshold corresponding to a current running stage to obtain a load evaluation result. The server 104 can adjust the heartbeat sending time interval according to the load evaluation result. The network performance index data can include multiple dimensions of parameters such as link bandwidth utilization, network delay value, packet loss rate statistical information, processor occupancy, memory usage, and network interface queue depth. The server 104 can calculate a comprehensive load evaluation value based on the collected multiple network performance indexes through weighted average or other mathematical models. The server 104 can compare the calculated load evaluation value with a preset load threshold corresponding to the current running stage, which can include a light load threshold, a medium load threshold, and a heavy load threshold, and determine the load level of the current network through the comparison result. The server 104 can dynamically adjust the heartbeat sending time interval according to the load evaluation result. When the load evaluation value exceeds the light load threshold, the server 104 can lengthen the heartbeat sending time interval. When the load evaluation value exceeds the medium load threshold, the server 104 further lengthens the time interval. When the load evaluation value exceeds the heavy load threshold, the server 104 significantly lengthens the time interval and can suspend part of the non-session heartbeat sending to reduce the additional burden on the network. When the network load falls back to the normal range, the server 104 can gradually restore the heartbeat sending time interval to the original setting value to ensure the continuity and effectiveness of session table maintenance.

[0078] Through the above steps, the server 104 can establish actual communication sessions between network element nodes in the cloud network, and effectively activate and continuously maintain the underlying network session table. The pre-constructed session table is converted into an actual available transmission path in the network. The heartbeat message mechanism ensures the timely activation and continuous effectiveness of the session, avoids performance loss caused by session aging failure, and optimizes the frequency of heartbeat message sending through a phased adaptive sending strategy and a network load-aware adjustment mechanism. The network resource occupation is minimized on the premise of ensuring the session maintenance effect.

[0079] Step S208, in response to a new traffic instruction, performing traffic forwarding processing according to the underlying network session table.

[0080] The new traffic instruction refers to a service traffic request in the cloud network that needs to establish a new network connection, representing a new data transmission demand initiated by a tenant.

[0081] Exemplarily, the server 104 can receive and parse the service traffic information contained in the new flow instruction. When a tenant in the cloud network initiates a new data transmission request, the server 104 can obtain the corresponding new flow instruction, extract the service packet information from the new flow instruction, including the source Internet Protocol address, the destination Internet Protocol address, the source port, the destination port, and the protocol type. The server 104 performs an exact match lookup in the underlying network session table using the queried data. The server 104 can calculate a hash value according to the queried four-tuple data, and locate the corresponding hash bucket or index position in the underlying network session table. The server 104 can perform a detailed record comparison at the target position, and check whether there is a session record that completely matches the queried four-tuple data. The server 104 can verify the current state of the found session record, and ensure that the record is in an activated state and has not exceeded the valid period of time.

[0082] When a matching activated session record is successfully found in the underlying network session table, the server 104 can perform a fast traffic forwarding operation based on the session record. The server 104 can extract the transmission path information from the matching session record, including the address of the next-hop network device and the output interface identifier. The server 104 can perform corresponding protocol encapsulation on the service packet according to the encapsulation protocol information in the session record, and add the necessary network layer and data link layer header information. The server 104 can directly send the encapsulated service packet to the specified output interface, realize the fast forwarding of the packet, and the whole process does not need to go through the time-consuming operations such as traditional route lookup and session establishment. The server 104 updates the usage statistical information of the matching session record, including the latest usage time and the cumulative usage times.

[0083] When the server 104 fails to find a matching activated session record in the underlying network session table, the server 104 can start a fast session establishment process and implement a packet protection mechanism. The server 104 can temporarily store the current service packet in a special buffer queue to avoid packet loss during the session establishment process. The server 104 can set a timeout time for the temporarily stored packet to prevent the packet from waiting indefinitely in the queue. The server 104 can analyze the unmatched queried four-tuple data to determine whether it can match other existing session records by adjusting the source port number. If there is an available similar session, the server 104 can redirect the packet to the session for processing. The server 104 can trigger a fast establishment process of a new session, generate corresponding heartbeat packets and send them to the network to create a new session record on the underlying network device.

[0084] In the new traffic processing method applied to the intra-cloud network, the source address data, the destination address data, the source port range data and the destination port data of each network element node in the intra-cloud network are acquired, so that the network parameters are collected and prepared in advance, the delay caused by acquiring the information during actual traffic processing is avoided, the bottom-layer network session table is constructed between each network element node in the intra-cloud network according to the source address data, the destination address data, the source port range data and the destination port data, the change from the traditional passive session establishment to the active session pre-establishment is realized, the subsequent new traffic can be directly forwarded by using the existing session record through the pre-constructed session table, so that the processing delay caused by triggering the session establishment of the new traffic in the traditional way is bypassed, the heartbeat message is sent between different network element nodes to update the bottom-layer network session table and keep the active state of each session record in the pre-established session table, the session is prevented from aging and invalidation due to long-time non-use, and it is ensured that the corresponding session channel is still available when the real new traffic arrives, so that the performance loss caused by triggering the session establishment process again due to the session invalidation is avoided. In response to the new traffic instruction, the traffic forwarding processing is performed according to the bottom-layer network session table, when the new traffic arrives, the matching session record can be found in the pre-established bottom-layer network session table, and the traffic forwarding processing is directly performed without experiencing the session establishment waiting process in the traditional way, so that the processing performance of the new traffic is improved.

[0085] In an exemplary embodiment, as shown in FIG. 3, the step of identifying the network element node type of each network element node according to the network topology configuration information can include steps S302 to S306. Wherein: Figure 4

[0086] In step S302, the network element connection relationship in the network topology configuration information is parsed, and the connection degree value of each network element node is counted.

[0087] The connection degree value represents the number of network element nodes directly connected to the network element node. The network element connection relationship refers to the direct connection state and connection mode between each network element node in the intra-cloud network topology, which describes the physical or logical connection structure of the network. The connection degree value is the total number of other network element nodes directly connected to a specific network element node in network topology analysis, which is an index for measuring the importance of the network element node in the network. The network topology configuration information is configuration data containing the description of the intra-cloud network structure, which can store the connection relationship between network element nodes in graphical representation, adjacency matrix, adjacency list or other data formats. Direct connection means that there is a physical or logical direct connection link between two network element nodes, and data can be transmitted directly between the two nodes without passing through other intermediate nodes.

[0088] ​Exemplarily, the server 104 can acquire and load the topology configuration information of the in-cloud network, which can be stored in a configuration database or a topology description file of a network management system. The server 104 can parse the data format of the topology configuration information, and identify the network element node identifiers and connection relationship descriptions contained therein. The server 104 can extract the unique identifier of each network element node, which can be a device name, an Internet Protocol address, a Media Access Control (MAC) address, or other forms of network device identification. The server 104 can parse the connection relationship data between network element nodes, which describe which network element nodes have direct communication link connections.

[0089] The server 104 can traverse all network element node records in the network topology configuration information, and for each target network element node, the server 104 can search all other network element nodes in the topology configuration information that have direct connection relationships with the node. The server 104 can calculate the number of other network element nodes directly connected to the target network element node, and record this value as the degree value of the target network element node. The server 104 can repeat this statistical process until the degree calculation of all network element nodes in the topology configuration information is completed. The server 104 can organize the calculation results into a network element node degree statistics table, which contains the identifier of each network element node and the corresponding degree value.

[0090] Step S304, determining the network element node with a degree value greater than the preset degree threshold as a center network element node.

[0091] Exemplarily, the server 104 can set the preset degree threshold according to the overall size, design target, and performance requirements of the in-cloud network. The server 104 can check the degree value of each network element node in the network element node degree statistics table one by one, and compare it with the preset degree threshold. The server 104 can set the network element node type identifier of the network element node with a degree value greater than the preset degree threshold to a center network element node.

[0092] Step S306, determining the network element node with a degree value less than or equal to the preset degree threshold as an edge network element node.

[0093] Exemplarily, the server 104 can traverse the node records of the network elements in the connectivity statistics table which have not been classified, and for each node, the server 104 can compare the connectivity value of the node with the preset connectivity threshold. The server 104 determines that the network element node with the connectivity value less than the preset connectivity threshold does not have the condition to undertake the network core forwarding function. The server 104 can classify the nodes with the connectivity value equal to the preset connectivity threshold as the edge network element nodes. The server 104 can establish a list of the edge network element nodes, and record the device identifier, the connectivity value, the Internet protocol address and other related attribute information of each edge network element node. The server 104 can analyze the specific position and connection mode of each edge network element node in the network topology, and identify the network area and the service type mainly served by the edge network element nodes.

[0094] Through the above steps, the server 104 completes the comprehensive classification of all network element nodes in the in-cloud network, clearly identifies the edge network element nodes responsible for the edge access function, establishes a complete network node role system, and through accurate identification of the edge network element nodes, the server 104 can implement a special session table construction scheme for the nodes, optimizes the communication path from the edge node to the center node, reasonably configures the sending strategy of the heartbeat packet, and realizes efficient cooperation between the edge network element nodes and the center network element nodes.

[0095] It should be understood that although each step in the flowchart involved in each embodiment as described above is displayed in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other sequences. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence of these steps or stages is not necessarily sequential, but can be executed in rotation or alternation with at least part of other steps or steps or stages in other steps. It can be understood that the steps in different embodiments can be freely combined as needed, and various non-contradictory schemes formed by the combination are within the scope of protection of the present application.

[0096] Based on the same inventive concept, the embodiments of the present application also provide a new traffic processing device applied to an in-cloud network for implementing the new traffic processing method applied to an in-cloud network as described above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, and therefore the specific limitations in one or more new traffic processing device embodiments applied to an in-cloud network provided below can refer to the limitations of the new traffic processing method applied to an in-cloud network described above, which will not be described here again.

[0097] In one example embodiment, as shown in Figure 5 Fig. 1, a new flow processing device applied to an intra-cloud network is provided, comprising a data acquisition module 502, a data processing module 504, a data updating module 506 and a flow forwarding module 508, wherein:

[0098] The data acquisition module 502 is configured to acquire source address data, destination address data, source port range data and destination port data of each network element node in the intra-cloud network.

[0099] The data processing module 504 is configured to construct an underlying network session table between each network element node in the intra-cloud network according to the source address data, the destination address data, the source port range data and the destination port data.

[0100] The data updating module 506 is configured to send a heartbeat message between different network element nodes to update the underlying network session table.

[0101] The flow forwarding module 508 is configured to perform flow forwarding processing according to the underlying network session table in response to a new flow instruction.

[0102] In one example embodiment, the data acquisition module 502 is specifically configured to acquire network topology configuration information and network element node address information of each network element node in the intra-cloud network; identify a network element node type of each network element node and a bearer protocol type of the intra-cloud network according to the network topology configuration information; the network element node type includes an edge network element node and a center network element node; extract a service Internet Protocol address of the edge network element node to obtain the source address data, and extract a service Internet Protocol address of the center network element node to obtain the destination address data according to the network element node address information; and obtain the destination port data and the source port range data according to the bearer protocol type.

[0103] In one example embodiment, the data acquisition module 502 is specifically configured to parse a network element connection relationship in the network topology configuration information and count a connection degree value of each network element node; the connection degree value represents a number of network element nodes directly connected to the network element node; determine a network element node with a connection degree value greater than a preset connection degree threshold as a center network element node; and determine a network element node with a connection degree value less than or equal to the preset connection degree threshold as an edge network element node.

[0104] In one example embodiment, the data updating module 506 is specifically configured to extract a session record to be activated from the underlying network session table, and construct a heartbeat message data packet according to the session record; send the heartbeat message data packet from a corresponding edge network element node to a center network element node; monitor a session table update response of each network element node on a transmission path of the heartbeat message data packet; and update an activation state of a corresponding session record in the underlying network session table according to the session table update response.

[0105] In one of the embodiments, the data updating module 506 is specifically configured to: acquire a current running stage; the current running stage comprises an initialization stage, a stable running stage and a low-load running stage; in a case where the current running stage is the initialization stage, set the heartbeat sending time interval as a first preset interval; in a case where the current running stage is the stable running stage, set the heartbeat sending time interval as a second preset interval; the second preset interval is greater than the first preset interval; in a case where the current running stage is the low-load running stage, set the heartbeat sending time interval as a third preset interval; the third preset interval is greater than the second preset interval; create a heartbeat sending timing task according to the heartbeat sending time interval; and execute the timing task to send the heartbeat message packet from the corresponding edge network element node to the center network element node.

[0106] In one of the embodiments, the device further comprises a data adjusting unit configured to acquire network performance index data of a transmission link between the edge network element node and the center network element node, and calculate a load evaluation value according to the network performance index data; compare the load evaluation value with a load threshold corresponding to the current running stage to obtain a load evaluation result; and adjust the heartbeat sending time interval according to the load evaluation result.

[0107] The above-mentioned various modules in the new flow processing device applied to the intra-cloud network can be realized by software, hardware and combinations thereof, in whole or in part. The above-mentioned various modules can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a memory in a computer device in software form, so as to be called and executed by a processor to perform the operations corresponding to the above-mentioned various modules.

[0108] In an exemplary embodiment, a computer device, which can be a server, is provided, and an internal structure diagram of the computer device can be as shown in Figure 6 The computer device includes a processor, a memory, an input / output interface (I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operating system and the computer program in the non-volatile storage medium to run. The input / output interface of the computer device is configured to exchange information between the processor and external devices. The communication interface of the computer device is configured to communicate with external terminals through network connection. The computer program is executed by the processor to implement an intra-cloud network new flow processing method.

[0109] Those skilled in the art can understand that Figure 6 The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0110] In one embodiment, a computer device is also provided, including a memory and a processor, the memory storing a computer program, and the processor implementing the steps in the above method embodiments when executing the computer program.

[0111] In one embodiment, a computer readable storage medium is provided, storing a computer program, and the computer program implements the steps in the above method embodiments when executed by a processor.

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

[0113] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations.

[0114] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. In the embodiments provided in the present application, any reference to memory, database or other medium can include at least one of non-volatile memory and volatile memory. The non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. The volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0115] Any technical features in the above embodiments can be combined, and for the sake of brevity, not all possible combinations are described, however, any combination of the technical features is considered to be within the scope of the present application. The above embodiments only express several implementation manners of the present application, and the description is more specific and detailed, but it should not be understood as a limitation on the patent scope of the present application. It should be pointed out that, for those skilled in the art, without departing from the concept of the present application, some modifications and improvements can be made, which are all within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A method for processing new traffic applied to an in-cloud network, characterized in that, The method comprises: Obtaining source address data, destination address data, source port range data and destination port data of each network element node in the cloud network; According to the source address data, the destination address data, the source port range data and the destination port data, constructing an underlying network session table between each network element node in the cloud network; Sending heartbeat messages between different network element nodes to update the underlying network session table; In response to a new traffic instruction, performing traffic forwarding processing according to the underlying network session table.

2. The method of claim 1, wherein, The method comprises: Obtaining network topology configuration information and network element node address information of each network element node in the cloud network; According to the network topology configuration information, identifying the network element node type of each network element node and the bearer protocol type of the cloud network; the network element node type includes edge network element nodes and center network element nodes; According to the network element node address information, extracting the service Internet Protocol address of the edge network element node to obtain source address data, and extracting the service Internet Protocol address of the center network element node to obtain destination address data; According to the bearer protocol type, obtaining destination port data and source port range data.

3. The method of claim 2, wherein, The method comprises: Parsing the network connection relationship in the network topology configuration information and counting the connection degree value of each network element node; the connection degree value represents the number of network element nodes directly connected to the network element node; Determining the network element node with a connection degree value greater than a preset connection degree threshold as a center network element node; Determining the network element node with a connection degree value less than or equal to the preset connection degree threshold as an edge network element node.

4. The method of claim 2, wherein, The method comprises: Extracting the session record to be activated from the underlying network session table, and constructing a heartbeat message data packet according to the session record; Sending the heartbeat message data packet from the corresponding edge network element node to the center network element node; Monitoring the session table update response of each network element node on the transmission path of the heartbeat message data packet; According to the session table update response, updating the activation state of the corresponding session record in the underlying network session table.

5. The method of claim 4, wherein, The method comprises: Obtaining the current running stage; the current running stage includes an initialization stage, a stable running stage and a low load running stage; In the case where the current running stage is the initialization stage, setting the heartbeat sending time interval to a first preset interval; In the case where the current running stage is the stable running stage, setting the heartbeat sending time interval to a second preset interval; the second preset interval is greater than the first preset interval; In a case where the current running phase is a low-load running phase, a heartbeat sending time interval is set as a third preset interval; the third preset interval is greater than the second preset interval; According to the heartbeat sending time interval, a heartbeat sending timing task is created; The timing task is executed to send the heartbeat message data packet from the corresponding edge network element node to the center network element node.

6. The method of claim 5, wherein, The method further comprises: Obtaining network performance index data of a transmission link between the edge network element node and the center network element node, and calculating a load evaluation value according to the network performance index data; Comparing the load evaluation value with a load threshold value corresponding to the current running phase to obtain a load evaluation result; Adjusting the heartbeat sending time interval according to the load evaluation result.

7. A new flow processing device applied to an in-cloud network, characterized in that, The device comprises: A data acquisition module configured to acquire source address data, destination address data, source port range data and destination port data of each network element node in an intra-cloud network; A data processing module configured to construct a bottom-layer network session table between each network element node in the intra-cloud network according to the source address data, the destination address data, the source port range data and the destination port data; A data updating module configured to send heartbeat messages between different network element nodes to update the bottom-layer network session table; A traffic forwarding module configured to perform traffic forwarding processing according to the bottom-layer network session table in response to a new traffic instruction.

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that, The processor executes the computer program to implement the steps of the method of any one of claims 1 to 6.

9. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method of any one of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method of any one of claims 1 to 6.

Images