CN114844808A - Software-defined stacked network data transmission system - Google Patents
Software-defined stacked network data transmission system Download PDFInfo
- Publication number
- CN114844808A CN114844808A CN202210379742.4A CN202210379742A CN114844808A CN 114844808 A CN114844808 A CN 114844808A CN 202210379742 A CN202210379742 A CN 202210379742A CN 114844808 A CN114844808 A CN 114844808A
- Authority
- CN
- China
- Prior art keywords
- data
- node
- message
- controller
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 29
- 238000012790 confirmation Methods 0.000 claims description 15
- 230000000694 effects Effects 0.000 claims description 9
- 230000009471 action Effects 0.000 claims description 3
- 230000006855 networking Effects 0.000 claims description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000010485 coping Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000000034 method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/42—Centralised routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a data transmission system of a software-defined overlay network, belonging to the technical field of network data transmission, aiming at solving the technical problems of how to overcome the difficulty in deploying the traditional software-defined network and how to overcome the instability of the data forwarding performance of the application, the technical scheme is as follows: the system is characterized in that a plurality of proxy servers and one or more controllers are deployed in a network, the proxy servers are used as relay nodes to forward data, and ports of the relay nodes used for forwarding the data are automatically designated and informed to the controllers; the controller is used for managing and maintaining the software-defined overlay network and calculating a data forwarding path; wherein, a link exists between any two different relay nodes; the software-defined overlay network utilizes leased logical links of fixed network bandwidth.
Description
Technical Field
The invention relates to the technical field of network data transmission, in particular to a software-defined stacked network data transmission system.
Background
The current internet runs on a core architecture designed years ago, which presents more and more problems with the rapid expansion of network size and the increasing abundance of application types. The functions carried by the network are continuously expanded, so that a router serving as a network core becomes overstaffed; due to lack of global scheduling, the utilization rate of network resources is not high, the capacity expansion pressure of the network is increased, and the network resources are seriously wasted; the continuous complication of the structure and the function of the internet enables the network management and control capability to be weakened continuously; the traditional network is difficult to effectively deal with network attacks such as distributed denial of service attacks (DDoS) which are continuously developed and evolved.
A Software Defined Network (SDN) is a novel network model, which separates forwarding and control functions, thereby simplifying network management, providing a new space for network optimization, quality of service improvement, and security enhancement through network programmable characteristics, and effectively coping with security problems in a conventional network, such as denial of service attacks. In recent years, software defined networking has received much attention and interest from both academic and industrial circles and has been rapidly developed. Google announces that the backbone network of google runs on OpenFlow (software defined network southward interface) completely, and links 12 data centers distributed in various parts of the world through a 10G network, so that the utilization rate of a wide area line is improved from 30% to nearly saturation; major network operators such as china mobile have developed research on SDN technology and started to deploy gradually. The high-efficiency management and scheduling of network resources and the system safety are two key basic problems in a software defined network, the former directly influences the utilization capability of the software defined network resources and the network service quality, and the latter is related to the protection of a system and a system user.
Although software-defined networks have significant advantages over traditional networks, they have not yet been deployed on a large scale, mainly because: the software defined network uses different network devices, and replacing the existing network devices involves many factors such as commercial benefits, etc., so that large-scale network device updating is difficult to complete in a short time.
Therefore, how to overcome the difficulty in deploying the conventional software-defined network and how to overcome the instability of the data forwarding performance of the application is a technical problem to be solved at present.
Disclosure of Invention
The technical task of the invention is to provide a software-defined overlay network data transmission system, which solves the problems of difficult deployment of the traditional software-defined network and unstable forwarding performance of the application data.
The technical task of the invention is realized in the following way, a software-defined overlay network data transmission system is characterized in that a plurality of proxy servers and one or more controllers are deployed in a network, the proxy servers are used as relay nodes to forward data, and ports of the relay nodes used for forwarding the data are automatically designated and informed to the controllers; the controller is used for managing and maintaining the software-defined overlay network and calculating a data forwarding path;
wherein, a link exists between any two different relay nodes; the software-defined overlay network utilizes leased logical links of fixed network bandwidth.
Preferably, in the software defined overlay network, the message sent by the controller to the relay node to indicate the data forwarding action is called a control message, and the control message is actually a message indicated by a data part (application data unit, ADU) in a data packet; the control message uses a preset port, and after the port receives the message, the relevant message is extracted according to the set convention.
More preferably, the control message takes the form of: control message type | control content data;
wherein, the control message is in a form that IP and TCP or UDP headers are not displayed and only a data part (namely a data ADU part) in the data packet is seen; the type of the control message is 8 bits or the number of bits is customized according to the requirement;
preferably, the data portion (i.e., the data ADU portion) of the data packet is preceded by a forwarding message that includes a source address and a destination address.
Preferably, the data forwarding includes that the common user node a sends data to the serving node B, specifically as follows:
s1, the ordinary user node A sends a route request message to the controller to inform itself to send data to the service node B;
s2, the controller calculates the data transmission path and sends a control message to the relay node to deploy the route;
s3, sending the address information of the first relay node of the path calculated by the controller to the common user node A;
s4, the common user node A sends a data transmission request message to the target service node B to inform the target node of the own IP address and the port number used for sending data;
s5, after receiving the data transmission request message sent by the ordinary user node a, the serving node B determines whether to approve receiving the data:
if the node A agrees to receive the data, sending a receiving confirmation message to the common user node A, and executing a step S6; wherein, the receiving confirmation message comprises a port for receiving data;
if the data is not accepted, sending a receiving refusing message to the common user node A;
s6, after receiving the receiving confirmation message sent by the serving node B, the normal user node a sends data to the serving node B.
More preferably, the address information of the relay node in step S3 includes an IP address and a port.
Preferably, the sending of the data from the ordinary user node a to the serving node B in step S6 is as follows:
s601, adding IP addresses of the common user node A and the service node B, ports of the common user node A and the service node B and other defined additional information at the head part of the data packet;
s602, when the ordinary user node a sends data to the serving node B, the data is first sent to the first relay node obtained from the controller in step S2;
and S603, after receiving the data sent by the common user node A, the relay node sequentially forwards the data to the target node according to the path specified by the controller.
More preferably, the management of the relay node is specifically as follows:
(1) each relay node sends heartbeat messages to the controller at intervals (the parameters are specified in the configuration file);
(2) after receiving the heartbeat message, the controller updates the latest activity time of the corresponding relay node and sends a confirmation message to the proxy server;
(3) judging whether the proxy server receives the confirmation message:
reporting that the controller cannot connect to the alarm if the proxy server cannot receive the message for three or more consecutive times (specified in the configuration file);
(4) judging whether the relay node in control updates the latest activity time within the set time:
if A in the controller does not update the latest activity time within the set time (specified in the configuration file), executing the step (5);
(5) and setting the proxy server to be in an inactive state, and not considering the associated logical link of the inactive state when calculating the route.
The software-defined overlay network data transmission system has the following advantages:
the logic link of the laminated network adopts a bandwidth renting mode, so that the data transmission capability of the logic link is ensured, and the problem of unstable data forwarding performance of an application layer is solved;
the invention realizes a high-practicability data transmission tunnel capable of being controlled in a centralized way through a specially designed application layer data format and a data transmission mechanism; meanwhile, effective management of the data transmission proxy server of the laminated network is realized;
thirdly, the invention forwards data in the application layer through the proxy server, the deployment is flexible, and the deployment problem of the traditional software defined network is overcome;
and fourthly, the invention calculates the forwarding path through the controller, so that the performance of the stacked network can be optimized on the whole, and particularly, the network congestion can be avoided.
Drawings
The invention is further described below with reference to the accompanying drawings.
Figure 1 is an architecture diagram of a software defined web stack.
Detailed Description
A software defined overlay network data transmission system of the present invention is described in detail below with reference to the drawings and specific embodiments.
Example 1:
the embodiment provides a data transmission system of a software-defined layer network, which is characterized in that a plurality of proxy servers and one or more controllers are deployed in a network, the proxy servers are used as relay nodes to forward data, and ports of the relay nodes, which are used for forwarding the data, are automatically specified and inform the controllers; the controller is used for managing and maintaining the software-defined overlay network and calculating a data forwarding path;
wherein, a link exists between any two different relay nodes; in order to save cost and guarantee data transmission quality and controllability, the software-defined overlay network utilizes a logical link of a leased fixed network bandwidth. The specific logical link selection may be selected by an optimized plan in the context of specific requirements.
In this embodiment, in the software-defined overlay network, a message sent by the controller to the relay node to indicate a data forwarding action is referred to as a control message, and the control message is actually a message indicated by a data portion (application data unit, ADU) in a data packet; the control message uses a preset port, and after the port receives the message, the relevant message is extracted according to the set convention.
As shown in fig. 1, the software-defined overlay network nodes are divided into four categories, namely, a common user node, a service node, a relay node and a controller node. The common user node refers to a network access node which does not provide service, and is usually a user desktop computer or a notebook computer; the service node is a server for providing services, such as a cloud computing service platform; the relay node refers to a server for data forwarding; controller node means a controller node where a server implementing a control function is similar to a mainstream software defined network. The relay node performs data forwarding at an application layer and does not depend on specific layer network equipment.
The logical link refers to a virtual link between different nodes in the software-defined overlay network, and the main access logical link refers to a logical link between the relay node and a common user node (or a service node).
The control message in this embodiment takes the form: control message type | control content data;
wherein, the control message is in a form that IP and TCP or UDP headers are not displayed and only a data part (namely a data ADU part) in the data packet is seen; the type of the control message is 8 bits or the number of bits is customized according to the requirement;
in the present embodiment, a forwarding message including a source address and a destination address is appended to the beginning of a data portion (i.e., data ADU portion) in a data packet. Other information may be added if desired, provided that it specifies a number of bits and meanings to process according to a uniform rule.
The data forwarding in this embodiment includes that the common user node a sends data to the serving node B, which is specifically as follows:
s1, the ordinary user node A sends a route request message to the controller to inform itself to send data to the service node B;
s2, the controller calculates the data transmission path and sends a control message to the relay node to deploy the route;
s3, sending the address information of the first relay node of the path calculated by the controller to the common user node A;
s4, the common user node A sends a data transmission request message to the target service node B to inform the target node of the own IP address and the port number used for sending data;
s5, after receiving the data transmission request message sent by the ordinary user node a, the serving node B determines whether to approve receiving the data:
if the data reception is agreed, sending a reception confirmation message to the common user node A, and executing a step S6; wherein, the receiving confirmation message comprises a port for receiving data;
if the data is not accepted, sending a receiving refusing message to the common user node A;
s6, after receiving the receiving confirmation message sent by the serving node B, the normal user node a sends data to the serving node B.
The address information of the relay node in step S3 in this embodiment includes an IP address and a port.
In this embodiment, the specific steps for the ordinary user node a in step S6 to send data to the serving node B are as follows:
s601, adding IP addresses of the common user node A and the service node B, ports of the common user node A and the service node B and other defined additional information at the head part of the data packet;
s602, when the ordinary user node a sends data to the serving node B, the data is first sent to the first relay node obtained from the controller in step S2;
and S603, after receiving the data sent by the common user node A, the relay node sequentially forwards the data to the target node according to the path specified by the controller.
The management of the relay node in this embodiment is specifically as follows:
(1) each relay node sends heartbeat messages to the controller at intervals (the parameters are specified in the configuration file);
(2) after receiving the heartbeat message, the controller updates the latest activity time of the corresponding relay node and sends a confirmation message to the proxy server;
(3) judging whether the proxy server receives the confirmation message:
reporting that the controller cannot connect to the alarm if the proxy server cannot receive the message for three or more consecutive times (specified in the configuration file);
(4) judging whether the relay node in control updates the latest activity time within the set time:
if A in the controller does not update the latest activity time within the set time (specified in the configuration file), executing the step (5);
(5) and setting the proxy server to be in an inactive state, and not considering the associated logical link of the inactive state when calculating the route.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (8)
1. A software-defined overlay network data transmission system is characterized in that a plurality of proxy servers and one or more controllers are deployed in a network, the proxy servers serve as relay nodes to forward data, and ports of the relay nodes, which are used for forwarding the data, are automatically designated and inform the controllers; the controller is used for managing and maintaining the software-defined overlay network and calculating a data forwarding path;
wherein, a link exists between any two different relay nodes; the software-defined overlay network utilizes leased logical links of fixed network bandwidth.
2. The system according to claim 1, wherein in the network, the message sent by the controller to the relay node to indicate the data forwarding action is called a control message, and the control message is actually a message indicated by a data part in a data packet; the control message uses a preset port, and after the port receives the message, the relevant message is extracted according to the set convention.
3. The system of claim 2, wherein the control message is in the form of: control message type | control content data;
wherein, the control message adopts a form that IP and TCP or UDP headers are not displayed and only the data part in the data packet is seen; the control message type is 8 bits or self-defined bits according to requirements.
4. The software-defined networking data transmission system of claim 3, wherein the data portion of the data packet is preceded by a forwarding message comprising a source address and a destination address.
5. The system of claim 1, wherein the data forwarding comprises the regular user node a sending data to the serving node B, specifically as follows:
s1, the ordinary user node A sends a route request message to the controller to inform itself to send data to the service node B;
s2, the controller calculates the data transmission path and sends a control message to the relay node to deploy the route;
s3, sending the address information of the first relay node of the path calculated by the controller to the common user node A;
s4, the ordinary user node A sends a data transmission request message to the target service node B to inform the target node of the IP address and the port number used for sending data;
s5, after receiving the data transmission request message sent by the ordinary user node a, the serving node B determines whether to approve receiving the data:
if the node A agrees to receive the data, sending a receiving confirmation message to the common user node A, and executing a step S6; wherein, the receiving confirmation message comprises a port for receiving data;
if the data is not accepted, sending a receiving refusing message to the common user node A;
s6, after receiving the receiving confirmation message sent by the serving node B, the normal user node a sends data to the serving node B.
6. The software-defined networking data transmission system of claim 5, wherein the address information of the relay node in step S3 comprises an IP address and a port.
7. The data transmission system of claim 5 or 6, wherein the general user node a in step S6 sends data to the service node B specifically as follows:
s601, adding IP addresses of a common user node A and a service node B and ports of the common user node A and the service node B at the head part of the data packet;
s602, when the ordinary user node a sends data to the serving node B, the data is first sent to the first relay node obtained from the controller in step S2;
and S603, after receiving the data sent by the common user node A, the relay node sequentially forwards the data to the target node according to the path specified by the controller.
8. The system of claim 7, wherein the relay node is specifically managed as follows:
(1) each relay node sends heartbeat messages to the controller at intervals;
(2) after receiving the heartbeat message, the controller updates the latest activity time of the corresponding relay node and sends a confirmation message to the proxy server;
(3) judging whether the proxy server receives the confirmation message:
if the proxy server can not receive the message for three or more times continuously, reporting that the controller can not be connected with an alarm;
(4) judging whether the relay node in control updates the latest activity time within the set time:
if the A in the controller does not update the latest activity time within the set time, executing the step (5);
(5) and setting the proxy server to be in an inactive state, and not considering the associated logical link of the inactive state when calculating the route.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210379742.4A CN114844808A (en) | 2022-04-12 | 2022-04-12 | Software-defined stacked network data transmission system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210379742.4A CN114844808A (en) | 2022-04-12 | 2022-04-12 | Software-defined stacked network data transmission system |
Publications (1)
Publication Number | Publication Date |
---|---|
CN114844808A true CN114844808A (en) | 2022-08-02 |
Family
ID=82563340
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210379742.4A Pending CN114844808A (en) | 2022-04-12 | 2022-04-12 | Software-defined stacked network data transmission system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114844808A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115514651A (en) * | 2022-09-16 | 2022-12-23 | 山东省计算中心(国家超级计算济南中心) | Cloud-edge data transmission path planning method and system based on software-defined stacked network |
-
2022
- 2022-04-12 CN CN202210379742.4A patent/CN114844808A/en active Pending
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115514651A (en) * | 2022-09-16 | 2022-12-23 | 山东省计算中心(国家超级计算济南中心) | Cloud-edge data transmission path planning method and system based on software-defined stacked network |
CN115514651B (en) * | 2022-09-16 | 2023-08-15 | 山东省计算中心(国家超级计算济南中心) | Cloud edge data transmission path planning method and system based on software-defined stacked network |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
RU2651149C2 (en) | Sdn-controller, data processing center system and the routed connection method | |
EP2157746B1 (en) | Routing control system for L3VPN service network | |
EP3993328A1 (en) | Route distribution method and controller, information routing method and network node device | |
EP3399703B1 (en) | Method for implementing load balancing, apparatus, and network system | |
EP2985952B1 (en) | Method and device for protecting service reliability, and network virtualization system | |
US20200059412A1 (en) | SDN Network System, Controller, and Controlling Method | |
WO2021018155A1 (en) | Routing information monitoring method and apparatus | |
US9743367B2 (en) | Link layer discovery protocol (LLDP) on multiple nodes of a distributed fabric | |
JP5488979B2 (en) | Computer system, controller, switch, and communication method | |
WO2022121080A1 (en) | Network configuration method, controller, and traffic guide system | |
EP2911346B1 (en) | Method and network device for establishing virtual cluster | |
EP2918049B1 (en) | Virtual chassis system control protocols | |
EP3562107A1 (en) | Broadcast packet processing method and processing apparatus, controller, and switch | |
CN115152192B (en) | PCE controlled network reliability | |
CN112910704B (en) | Local area network system, method and device supporting dynamic self-adaptive network configuration | |
CN101562576B (en) | Route distribution method and equipment thereof | |
US20230010837A1 (en) | Fault diagnosis method and apparatus thereof | |
US11894978B1 (en) | Computing power scheduling methods, apparatus, electronic devices and storage media | |
WO2018219103A1 (en) | Method and device for determining link state | |
CN114844808A (en) | Software-defined stacked network data transmission system | |
CN106169982B (en) | Method, device and system for processing expansion port | |
CN112217680A (en) | Controller capability benchmark test method and device based on software-defined wide area network | |
US20210105204A1 (en) | Cloud network transmission routing method and system | |
EP4213460A1 (en) | Session state synchronization and failover using session-based routing | |
JP3844215B2 (en) | Network configuration management system, node device, network configuration management method, node device control method, and node device control program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
CB02 | Change of applicant information |
Country or region after: China Address after: 250353 Qilu Industrial University, 3501 University Road, Changqing District, Ji'nan, Shandong Applicant after: Qilu University of Technology (Shandong Academy of Sciences) Address before: 250353 Qilu Industrial University, 3501 University Road, Changqing District, Ji'nan, Shandong Applicant before: Qilu University of Technology Country or region before: China |