CN104717095A - Multiple controllers integrated visualized SDN management method - Google Patents
Multiple controllers integrated visualized SDN management method Download PDFInfo
- Publication number
- CN104717095A CN104717095A CN201510116458.8A CN201510116458A CN104717095A CN 104717095 A CN104717095 A CN 104717095A CN 201510116458 A CN201510116458 A CN 201510116458A CN 104717095 A CN104717095 A CN 104717095A
- Authority
- CN
- China
- Prior art keywords
- controller
- information
- sdn
- stream table
- topology
- 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.)
- Granted
Links
Landscapes
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a multiple controllers integrated visualized SDN management method. The visualized SDN management is achieved, a user can utilize a front-end webpage provided the method to achieve functions as follows: simple and fast generation of an SDN, displaying of a generated network topology, displaying of information of the SDN, management of the flow statement of a switch and the like. The multiple controllers integrated visualized SDN management method enables command lines to be replaced by a graphical interface, further unifies interfaces provided by multiple controllers for us and shields the difference brought by different controllers, a user does not think about the types of the controllers in the SDN and also does not need to be familiar with switch operating commands of the controllers, and accordingly a beginner can simply and conveniently use the relevant functions of the SDN controllers and fast know the SDN.
Description
Technical field
The present invention relates to a kind of visual SDN management method of integrated multi-controller, belong to Computer Applied Technology field.
Background technology
Along with the constantly universal of SDN and development, the research of current SDN has become the important research topic of one, China.Increasing researcher enters this research field at present, but, nowadays great majority are all the assemblies (comprising controller, switch, main frame etc.) being gone out SDN by software virtuals such as Mininet for the research of SDN, then carry out experimental study on this basis.Therefore, this field of researcher's first contacts all thinks that the technology of SDN is very abstract, is difficult to hold, and seriously hinders the understanding of researcher to SDN, has difficulty in taking a step so researcher becomes in the research in this field.Secondly, the time proposed due to the concept of SDN is shorter, therefore also ununified at present standard, particularly for the research and development of SDN controller, many different groups develop the controller of polytype SDN, and the interface name that different controller provides, function may be all inconsistent, therefore researcher needs principle, the API of Learning Studies various controller, then could be applied in an experiment, but the interface that various controller provides is various, title is different, this brings difficulty to undoubtedly the research and development of researcher.
Summary of the invention
In order to overcome above-mentioned deficiency, the invention provides a kind of SDN management method being integrated with multi-controller based on Java, Flex technology.First, the method achieve and manage the visualized operation of SDN, the front end page that user can utilize this method to provide realizes following function: simple and quick generation SDN; Show the network topology generated; Show the information of SDN; The stream table of switch is managed etc.
In addition, the method not only instead of order line with patterned interface, and we have also unified the interface that multi-controller provides, shield the difference that different controller brings, make user need not consider the type of SDN middle controller, also need not be familiar with the order of often kind of controller operate switch, thus enable beginner use SDN controller correlation function simply and easily, be familiar with SDN fast.
The technical scheme that the present invention takes is as follows:
A visual SDN management method for integrated multi-controller, method by front end, server end, database, SDN controller and switch composition; Wherein server end manages by SDN, is responsible for communicating with SDN, is the bridge that front end communicates with SDN; Wherein server end realizes primarily of Java language, and the dependence simultaneously applying spring framework is injected and statement formula transaction management comes initialization and the transaction management of management server end object; Visual (in conjunction with the server end) that realize the operations such as SDN topology creates, the displaying of SDN topology information, the deletion of the interpolation that stream is shown and stream table is mainly responsible in front end; Front end realizes primarily of Flex, ActionScript language, and wherein Flex is responsible for the structure of webpage and beautifies, and ActionScript is responsible for the realization of webpage function, is also responsible for and server end interaction data simultaneously.Database section is the relevant information of SDN that gathers of storage server end mainly, uses for front end inquiry.Wherein front end and server end access remote service Interface realization by Blazeds, wherein Blazeds is a Java far call based on server and Web message transferring technology, and the java application of server end can be intercomed mutually with the Flex application program run on a web browser; And server end carries out accessing operation by MyBatis and Spring technology to database, and integrated by MyBatis-Spring between MyBatis and Spring, use the class in MyBatis-Spring class libraries, Spring will load necessary MyBatis factory class and session class.This class libraries also provides a simple mode to inject MyBatis data mapper and SqlSession to the bean of operation layer, so just achieves the operation of server to database; Server end is then the control by realizing to the RESTAPI transmission HTTP request of SDN controller SDN controller.
A visual SDN management method for integrated multi-controller, comprises the deletion of the establishment of SDN topology, topology information collection, the displaying of SDN topology information, the interpolation of stream table and stream table; Specific as follows:
The method that SDN topology creates is:
(1) user determines required topology;
(2) assembly is created, comprising SDN controller, OpenFlow switch and main frame.This step mainly completes in front end page;
(3) controller created in above-mentioned steps is connected, switch and main frame composition network topology, wherein, controller connects switch, switch also can connect main frame by connection control device, and there is not direct link between controller and main frame, this step is also complete in front end page, after network topology has created, topology can be derived;
Topology information acquisition method is:
(4) determine the topology information needing to gather, need to obtain which topology information mainly by kind and developer's decision of SDN controller in topology, generally comprise the relevant informations such as controller, switch, main frame, link;
(5) judge Control Cooling, because different controllers, the order obtaining same class information is inconsistent;
(6) after determining controller type and needing the information of collection, be exactly the order of splicing Information Monitoring, because server end and controller are realized by HTTP request alternately, the order of therefore splicing Information Monitoring is exactly splice HTTP request in fact, the HTTP request obtaining different topology information is different, therefore obtain different topology informations to need to splice different HTTP request, HTTP request splicing detailed process is: first determine that HTTP request type (comprises POST, GET, DELETE), after determining HTTP request type, to the information content of request be needed to join in HTTP again, such HTTP request completed just splicing completes, carry out next step afterwards,
(7) send HTTP to controller to plead, controller, when receiving the HTTP request that outside is sent, first judges that whether its form is correct, is directly returning mistake if incorrect, no longer carry out other operations, if form correctly then carries out next step; HTTP request resolved by SDN controller, obtains the type of solicited message, then will the Information encapsulation returned be needed to become the character string of JSON word format to return;
(8) after server end receives the return information of self-controller, the form of return information is JSON character string, need to resolve it, resolving is as follows: define at server end the JSON character string that a Map object returns to receive controller, then take out information in JSON stored in corresponding object by Map, finally again the method for call operation database by information updating in database;
(9) in network, topology information is real-time change, being arranged to the task of timing, often crossing obtaining topology information in network one-period and just obtaining a topology information.
The method of the displaying of SDN topology information is:
(10) user selects the topology information that needs to check, carries out next step after determining;
(11) after have selected the topology information needing display user, the method reading database of the acquisition particular topology information that front end is provided by invoking server end obtains the currency of required topology information, front end is back to after being packaged into object, if there is not relevant topology information, then return sky;
(12), after receiving the data that server end returns, the object of encapsulation is taken out in front end, then shows at the page;
(13) if also want to check other information, return (10).
The method of the interpolation of stream table:
(14) start to add stream table, this step mainly completes in front end, and concrete operations are, arranges the relevant parameter needing to add stream table, carries out next step after being provided with;
(15) controller type is determined, because the order that different controller adds stream table is inconsistent;
(16) after determining controller type, be exactly the HTTP request that the order of stream table is added in splicing, its process is consistent with splicing HTTP request in acquisition network topological information;
(17), after HTTP has spliced, server end will send the HTTP request of having spliced to controller;
(18) controller is after receiving the HTTP request from server, first judges that whether its form is correct, if incorrect, directly return error message and restarts stream table and add, if correct, carry out the 6th step;
(19) judge whether to exist in stream table and show stream list item of the same name with the stream that will add, if exist, directly cover, return the JSON character string with entry pushed information, if do not exist, judge whether the stream list item that will add meets dependence, satisfied then add and newly flow table, return the JSON character string with entry pushed information to server, otherwise, adding stream shows unsuccessfully, returns the JSON character string with entry push failed information;
(20) then proceed to (14) if also need to continue to add stream table, otherwise the interpolation of stream table terminates.
The method of the deletion of stream table:
(21) start to delete stream table, this step mainly completes in front end, and concrete operations are, arranges the stream table name needing to delete stream table, carries out next step after being provided with;
(22) controller type is determined, because the order that stream table deleted by different controller is inconsistent;
(23) after determining controller type, be exactly the HTTP request that the order of stream table is deleted in splicing, its process is consistent with splicing HTTP request in acquisition network topological information;
(24), after HTTP has spliced, server end will send the HTTP request of having spliced to controller;
(25) controller is after receiving the HTTP request from server, first judges that whether its form is correct, if incorrect, directly return error message and restarts to flow list deletion, if correct, carrying out next step;
(26) judge whether to exist in stream table and show stream list item of the same name with the stream that will delete, if exist, carry out deletion action, return the JSON character string with " Entry ' stream table name ' deleted " information, why any operation is not carried out if do not exist, return the JSON character string with " Entry ' stream table name ' deleted " information, then proceed to (21) if also need to continue to delete stream table, otherwise the interpolation of stream table terminates.
Beneficial effect of the present invention: the present invention not only achieves the visualized management to SDN, and for the diversity of SDN controller, we add one deck on the control plane of SDN, for the API that unified dissimilar controller provides, thus eliminate different controller the different API troublesome operation brought is provided.
Accompanying drawing explanation
Fig. 1 is overall system architecture schematic diagram of the present invention.
Fig. 2 is the particular flow sheet that this method generates SDN topology.
Fig. 3 is the particular flow sheet that this method obtains SDN topology.
Fig. 4 is the particular flow sheet that this method shows module information in SDN.
Fig. 5 is the particular flow sheet that this method adds stream table.
Fig. 6 is the particular flow sheet that this method deletes stream table.
Embodiment
Carry out further describing to the present invention below in conjunction with accompanying drawing.
As shown in Figure 1, a kind of visual SDN management method of integrated multi-controller, method by front end, server end, database, SDN controller and switch composition; Wherein server end manages SDN, is responsible for communicating with SDN controller and front end, is the bridge that front end communicates with SDN; Wherein server end realizes primarily of Java language, and the dependence simultaneously applying spring framework is injected and statement formula transaction management function comes initialization and the transaction management of management server end object; Visual (in conjunction with the server end) that realize the operations such as SDN topology creates, the displaying of SDN topology information, the deletion of the interpolation that stream is shown and stream table is mainly responsible in front end; Front end realizes primarily of Flex, ActionScript language, and wherein Flex is responsible for the structure of webpage and beautifies, ActionScript be responsible for realizing webpage logic function and and server end between data interaction.Database section is the relevant information of SDN that gathers of storage server end mainly, uses for front end inquiry.The database that this method uses is MySQL.SDN controller mainly manages the switch in network, and function mainly comprises stream table and issues, network flow monitoring, load balancing etc.; Finally, the switch in SDN is responsible for according to stream table forwarding data bag, and adds up the data forwarded; Wherein front end and server end access remote service Interface realization by Blazeds, wherein Blazeds mono-is based on the Java far call of server and Web message transferring technology, and the java application of server end can be intercomed mutually with the Flex application program run on a web browser; And server end carries out accessing operation by MyBatis and Spring technology to database, and integrated by MyBatis-Spring between MyBatis and Spring, use the class in MyBatis-Spring class libraries, Spring will load necessary MyBatis factory class and session class.This class libraries also provides a simple mode to inject MyBatis data mapper and SqlSession to the bean of operation layer, so just achieves the operation of server to database; Server end is then by sending to the RESTAPI of SDN controller the control that HTTP request realizes the controller to SDN.
Fig. 2 describes the process schematic of the self-defined SDN topology of this method.The first step is that user determines required topology, then performs next step; Second step creates assembly exactly, comprising SDN controller, and OpenFlow switch and main frame.This step mainly completes in front end page, the webpage that this method provides pulls required component and puts among the panel of " creating topology ", namely complete the establishment of an assembly.Next step is carried out after all component has created; 3rd step connects the controller created in above-mentioned steps, and switch and main frame composition network topology, wherein, controller connects switch, and switch also can connect main frame by connection control device, there is not direct link between controller and main frame.This step is also complete in front end page, by connecting in panel two different assemblies, namely completing the establishment of a link, just representing that network topology has created, and can derive topology after all link establishments complete; Finally, after derivation topology, if also want to continue to create topology, can add assembly on the basis created before, link continues to create, and also can empty panel and re-create other topologys.
Fig. 3 is the particular flow sheet obtaining SDN topology information, and the whole process obtaining topology information is all perform at server end, does not relate to front-end operations.First, the first step is the topology information determining to need to gather, and needs to obtain which topology information mainly by kind and developer's decision of SDN controller in topology.Generally comprise the relevant informations such as controller, switch, main frame, link; Second step, judges Control Cooling, because different controllers, the order obtaining same class information is inconsistent; 3rd step is exactly the order of splicing Information Monitoring after determining controller type and needing the information of collection.Because server end and controller are realized by HTTP request alternately, the order of therefore splicing Information Monitoring is exactly splice HTTP request in fact, the HTTP request obtaining different topology information is different, and therefore obtaining different topology informations needs to splice different HTTP request.HTTP request splicing detailed process is: first determine that HTTP request type (comprises POST, GET, DELETE), after determining HTTP request type, to the information content of request be needed to join in HTTP again, such HTTP request completed just splicing completes, and carries out next step afterwards; 3rd step, sends HTTP to controller and pleads, and controller, when receiving the HTTP request that outside is sent, first judges that whether its form is correct, directly returning mistake if incorrect, no longer carry out other operations, if form correctly then carries out next step; 4th step, HTTP request resolved by SDN controller, obtains the type of solicited message, then will the Information encapsulation returned be needed to become the form of JSON character string to return.5th step, after server end receives the return information of self-controller, because the form of return information is JSON character string, therefore needs to resolve it.Resolving is as follows: define at server end the JSON character string that a Map object returns to receive controller, then takes out information in JSON stored in corresponding object by Map, finally again the method for call operation database by information updating in database; Finally, because topology information is real-time change in network, therefore we have been arranged to the task of timing by obtaining topology information in network, and we just obtain a topology information often to cross one-period.
Fig. 4 is the particular flow sheet checking SDN topology information.The first step is the topology information that user selects to need to check, carries out next step after determining; Second step is after user have selected the topology information needing display, the method reading database of the acquisition particular topology information that front end is provided by invoking server end obtains the currency of required topology information, front end is back to after being packaged into object, if there is not relevant topology information, then return sky; 3rd step, after receiving the data that server end returns, the object of encapsulation is taken out in front end, then in page display, finally, if also want to check other information, repeats above-mentioned steps.
Fig. 5 is the particular flow sheet that this method realizes adding stream table.The first step, start to add stream table, this step mainly completes in front end, carries out next step after being provided with; Second step, determines controller type, because the order that different controller adds stream table is inconsistent.3rd step is exactly the HTTP request that the order of stream table is added in splicing after determining controller type, and its process is consistent with splicing HTTP request in acquisition network topological information.4th step, after HTTP has spliced, server end will send the HTTP request of having spliced to controller; 5th step, controller, after receiving the HTTP request from server, first judges that whether its form is correct, if incorrect, directly return error message and restarts stream table and add, if correct, carry out next step; 6th step, judge whether to exist in stream table and show stream list item of the same name with the stream that will add, if exist, directly cover, return the JSON character string with entry pushed information, if do not exist, judge whether the stream list item that will add meets dependence, satisfied then add and newly flow table, the JSON character string with entry pushed information is returned to server, otherwise, add stream and show unsuccessfully, return the JSON character string with entry push failed information; Finally, if also need to continue to add stream table then repeat above-mentioned steps, otherwise the interpolation of stream table terminates.
Fig. 6 is the particular flow sheet that this method realizes deleting stream table, the first step, and start to delete stream table, this step mainly completes in front end, carries out next step after being provided with; Second step, determines controller type, because the order that stream table deleted by different controller is inconsistent.3rd step is exactly the HTTP request that the order of stream table is deleted in splicing after determining controller type, and its process is consistent with splicing HTTP request in acquisition network topological information.4th step, after HTTP has spliced, server end will send the HTTP request of having spliced to controller; 5th step, controller, after receiving the HTTP request from server, first judges that whether its form is correct, if incorrect, directly return error message and restarts to flow list deletion, if correct, carrying out next step; 6th step, judge whether to exist in stream table and show stream list item of the same name with the stream that will delete, if exist, carry out deletion action, return the JSON character string with " Entry ' stream table name ' deleted " information, why any operation is not carried out if do not exist, return the JSON character string with " Entry ' stream table name ' deleted " information, if also need to continue to delete stream table then repeat above-mentioned steps, otherwise the interpolation of stream table terminates.
Claims (1)
1. a visual SDN management method for integrated multi-controller, comprises the deletion of the establishment of SDN topology, topology information collection, the displaying of SDN topology information, the interpolation of stream table and stream table; It is characterized in that,
The method that SDN topology creates is:
(1) user determines required topology;
(2) assembly is created, comprising front end, server end, database, SDN controller and OpenFlow switch composition;
Wherein server end manages by SDN, is responsible for communicating with SDN, is the bridge that front end communicates with SDN; Front end primary responsibility realizes the visual of the operations such as SDN topology creates, the displaying of SDN topology information, the deletion of the interpolation that stream is shown and stream table;
Database section is the relevant information of SDN that gathers of storage server end mainly, uses for front end inquiry; Wherein front end and server end access remote service Interface realization by Blazeds, and server end is then the control by realizing to the RESTAPI transmission HTTP request of SDN controller SDN controller;
(3) connect SDN controller, OpenFlow switch and the main frame composition network topology created in above-mentioned steps, wherein, controller connects switch, and switch connection control device or connection main frame, do not exist direct link between controller and main frame; After network topology has created, derive topology;
Topology information acquisition method is:
(4) determine the topology information needing to gather, need to obtain which topology information mainly by kind and developer's decision of SDN controller in topology, generally comprise the relevant informations such as controller, switch, main frame, link;
(5) judge Control Cooling, because different controllers, the order obtaining same class information is inconsistent;
(6) after determining controller type and needing the information of collection, be exactly the order of splicing Information Monitoring, because server end and controller are realized by HTTP request alternately, the order of therefore splicing Information Monitoring is exactly splice HTTP request in fact, the HTTP request obtaining different topology information is different, therefore obtain different topology informations to need to splice different HTTP request, HTTP request splicing detailed process is: first determine HTTP request type, comprise POST, GET, DELETE, after determining HTTP request type, to the information content of request be needed to join in HTTP again, the HTTP request splicing completed completes, carry out next step afterwards,
(7) send HTTP to controller to plead, controller, when receiving the HTTP request that outside is sent, first judges that whether its form is correct, is directly returning mistake if incorrect, no longer carry out other operations, if form correctly then carries out next step; HTTP request resolved by SDN controller, obtains the type of solicited message, then will the Information encapsulation returned be needed to become the character string of JSON word format to return;
(8) after server end receives the return information of self-controller, because the form of return information is JSON character string, therefore need to resolve it, resolving is as follows: define at server end the JSON character string that a Map object returns to receive controller, then take out information in JSON stored in corresponding object by Map, finally again the method for call operation database by information updating in database;
(9) because topology information is real-time change in network, therefore we have been arranged to the task of timing by obtaining topology information in network, and we just obtain a topology information often to cross one-period;
The method of the displaying of SDN topology information is:
(10) user selects the topology information that needs to check, carries out next step after determining;
(11) be after user have selected the topology information needing display, the method reading database of the acquisition particular topology information that front end is provided by invoking server end obtains the currency of required topology information, front end is back to after being packaged into object, if there is not relevant topology information, then return sky;
(12), after receiving the data that server end returns, the object of encapsulation is taken out in front end, then shows at the page;
(13) if also want to check other information, return (10);
The method of the interpolation of stream table:
(14) start to add stream table, this step mainly completes in front end, and concrete operations are, arranges the relevant parameter needing to add stream table, carries out next step after being provided with;
(15) controller type is determined, because the order that different controller adds stream table is inconsistent;
(16) after determining controller type, be exactly the HTTP request that the order of stream table is added in splicing, its process is consistent with splicing HTTP request in acquisition network topological information;
(17), after HTTP has spliced, server end will send the HTTP request of having spliced to controller;
(18) controller is after receiving the HTTP request from server, first judges that whether its form is correct, if incorrect, directly return error message and restarts stream table and add, if correct, carry out the 6th step;
(19) judge whether to exist in stream table and show stream list item of the same name with the stream that will add, if exist, directly cover, return the JSON character string with entry pushed information, if do not exist, judge whether the stream list item that will add meets dependence, satisfied then add and newly flow table, return the JSON character string with entry pushed information to server, otherwise, adding stream shows unsuccessfully, returns the JSON character string with entry push failed information;
(20) then proceed to (14) if also need to continue to add stream table, otherwise the interpolation of stream table terminates;
The method of the deletion of stream table:
(21) start to delete stream table, this step mainly completes in front end, arranges the stream table name needing to delete stream table, carries out next step after being provided with;
(22) controller type is determined, because the order that stream table deleted by different controller is inconsistent;
(23) after determining controller type, be exactly the HTTP request that the order of stream table is deleted in splicing, its process is consistent with splicing HTTP request in acquisition network topological information;
(24), after HTTP has spliced, server end will send the HTTP request of having spliced to controller;
(25) controller is after receiving the HTTP request from server, first judges that whether its form is correct, if incorrect, directly return error message and restarts to flow list deletion, if correct, carrying out next step;
(26) judge whether to exist in stream table and show stream list item of the same name with the stream that will delete, if exist, carry out deletion action, return the JSON character string with " Entry ' stream table name ' deleted " information, why any operation is not carried out if do not exist, return the JSON character string with " Entry ' stream table name ' deleted " information, then proceed to (21) if also need to continue to delete stream table, otherwise the interpolation of stream table terminates.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510116458.8A CN104717095B (en) | 2015-03-17 | 2015-03-17 | A kind of visualization SDN management method of integrated multi-controller |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510116458.8A CN104717095B (en) | 2015-03-17 | 2015-03-17 | A kind of visualization SDN management method of integrated multi-controller |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104717095A true CN104717095A (en) | 2015-06-17 |
| CN104717095B CN104717095B (en) | 2018-04-10 |
Family
ID=53416086
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510116458.8A Active CN104717095B (en) | 2015-03-17 | 2015-03-17 | A kind of visualization SDN management method of integrated multi-controller |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104717095B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105471633A (en) * | 2015-11-18 | 2016-04-06 | 武汉烽火网络有限责任公司 | Graphical programming method applied to SDN |
| CN105809248A (en) * | 2016-03-01 | 2016-07-27 | 中山大学 | Method for configuring DANN onto SDN and an interaction method between them |
| CN106385326A (en) * | 2016-08-29 | 2017-02-08 | 广州西麦科技股份有限公司 | SDN (Software Defined Networking) flow table automatic one-key deployment system |
| CN107040416A (en) * | 2017-04-12 | 2017-08-11 | 大连理工大学 | A kind of virtual data center visual management method based on Cairngorm frameworks |
| CN107133020A (en) * | 2016-02-26 | 2017-09-05 | 中移(苏州)软件技术有限公司 | A kind of data processing method, system, interface end and server |
| CN109327342A (en) * | 2018-11-27 | 2019-02-12 | 哈尔滨理工大学 | A kind of the adaptive SD N analogue system and emulation platform of task based access control driving |
| CN110120962A (en) * | 2018-02-06 | 2019-08-13 | 北京龙腾佳讯科技股份公司 | Visualization real-time interaction method and system for SDN network |
| CN111130952A (en) * | 2019-12-31 | 2020-05-08 | 南京煌和信息技术有限公司 | Integrated multi-client distributed network monitoring system through SDN network architecture |
| CN113162807A (en) * | 2021-04-27 | 2021-07-23 | 银清科技有限公司 | Method and device for realizing linkage of cloud management server and SDN |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140052836A1 (en) * | 2012-08-15 | 2014-02-20 | Dell Products L.P. | Network switching system using software defined networking applications |
| CN103856356A (en) * | 2014-03-19 | 2014-06-11 | 北京工业大学 | Home network implementation method based on user self-control |
| CN104092565A (en) * | 2014-06-24 | 2014-10-08 | 复旦大学 | Multi-tenant policy-driven type software-defined networking method for cloud data center |
| CN104106237A (en) * | 2012-02-10 | 2014-10-15 | 日本电气株式会社 | Computer system and method for visualizing virtual network |
| WO2014188939A1 (en) * | 2013-05-21 | 2014-11-27 | 独立行政法人情報通信研究機構 | Network configuration and operation visualization device |
-
2015
- 2015-03-17 CN CN201510116458.8A patent/CN104717095B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104106237A (en) * | 2012-02-10 | 2014-10-15 | 日本电气株式会社 | Computer system and method for visualizing virtual network |
| US20140052836A1 (en) * | 2012-08-15 | 2014-02-20 | Dell Products L.P. | Network switching system using software defined networking applications |
| WO2014188939A1 (en) * | 2013-05-21 | 2014-11-27 | 独立行政法人情報通信研究機構 | Network configuration and operation visualization device |
| CN103856356A (en) * | 2014-03-19 | 2014-06-11 | 北京工业大学 | Home network implementation method based on user self-control |
| CN104092565A (en) * | 2014-06-24 | 2014-10-08 | 复旦大学 | Multi-tenant policy-driven type software-defined networking method for cloud data center |
Non-Patent Citations (1)
| Title |
|---|
| 袁晓等: "大规模网络仿真软件及其仿真技术", 《计算机技术与发展》 * |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105471633B (en) * | 2015-11-18 | 2019-04-26 | 武汉烽火网络有限责任公司 | A kind of graphic programming method applied to SDN |
| CN105471633A (en) * | 2015-11-18 | 2016-04-06 | 武汉烽火网络有限责任公司 | Graphical programming method applied to SDN |
| CN107133020A (en) * | 2016-02-26 | 2017-09-05 | 中移(苏州)软件技术有限公司 | A kind of data processing method, system, interface end and server |
| CN105809248A (en) * | 2016-03-01 | 2016-07-27 | 中山大学 | Method for configuring DANN onto SDN and an interaction method between them |
| CN105809248B (en) * | 2016-03-01 | 2018-07-24 | 中山大学 | A kind of configuration and exchange method of the distribution artificial neural network on SDN |
| CN106385326B (en) * | 2016-08-29 | 2019-08-23 | 广州西麦科技股份有限公司 | SDN flow table automates a key deployment system |
| CN106385326A (en) * | 2016-08-29 | 2017-02-08 | 广州西麦科技股份有限公司 | SDN (Software Defined Networking) flow table automatic one-key deployment system |
| CN107040416A (en) * | 2017-04-12 | 2017-08-11 | 大连理工大学 | A kind of virtual data center visual management method based on Cairngorm frameworks |
| CN107040416B (en) * | 2017-04-12 | 2019-12-27 | 大连理工大学 | Virtual data center visual management method based on Cairngorm framework |
| CN110120962A (en) * | 2018-02-06 | 2019-08-13 | 北京龙腾佳讯科技股份公司 | Visualization real-time interaction method and system for SDN network |
| WO2019154367A1 (en) * | 2018-02-06 | 2019-08-15 | 北京龙腾佳讯科技股份公司 | Visual real-time interaction method and system for use in sdn |
| CN110120962B (en) * | 2018-02-06 | 2020-09-04 | 北京龙腾佳讯科技股份公司 | Visual real-time interaction method and system for SDN (software defined network) |
| CN109327342A (en) * | 2018-11-27 | 2019-02-12 | 哈尔滨理工大学 | A kind of the adaptive SD N analogue system and emulation platform of task based access control driving |
| CN111130952A (en) * | 2019-12-31 | 2020-05-08 | 南京煌和信息技术有限公司 | Integrated multi-client distributed network monitoring system through SDN network architecture |
| CN113162807A (en) * | 2021-04-27 | 2021-07-23 | 银清科技有限公司 | Method and device for realizing linkage of cloud management server and SDN |
| CN113162807B (en) * | 2021-04-27 | 2022-12-30 | 银清科技有限公司 | Method and device for realizing linkage of cloud management server and SDN |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104717095B (en) | 2018-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104717095A (en) | Multiple controllers integrated visualized SDN management method | |
| CN106326104B (en) | Terminal control testing method and device | |
| EP2508996B1 (en) | Visualizing relationships between a transaction trace graph and a map of logical subsystems | |
| EP2508995B1 (en) | Visualizing transaction traces as flows through a map of logical subsystems | |
| US8001481B2 (en) | Implementation of an interactive progress bar in a test application environment | |
| CN103927253A (en) | Multiple browser compatibility testing method and system | |
| CN109739855B (en) | Method and system for realizing data sheet splicing and automatically training machine learning model | |
| CN102222043B (en) | Testing method and testing device | |
| Rodríguez-Echeverría et al. | Modernization of legacy web applications into rich internet applications | |
| JP2022020541A (en) | Test method and device | |
| CN109388791A (en) | Chart Dynamic Display method, apparatus, computer equipment and storage medium | |
| CN103631719A (en) | Web automated testing method and device | |
| CN103677781A (en) | Graphical user interface and establishing method thereof for automated testing | |
| CN103324755A (en) | Display method, system and device of application program | |
| CN102946334A (en) | Method and system for acquiring valid image verification code | |
| CN105743736A (en) | Automated testing method and system | |
| CN104008041A (en) | Terminal application test method and device | |
| CN106970870B (en) | Webpage test platform, webpage test method and webpage test system | |
| US10728095B2 (en) | Client-configured server class tracing to a configurable threshold | |
| CN104834594B (en) | Web system method of testing and device | |
| CN104461509B (en) | A kind of information interaction system and method | |
| CN105426308A (en) | Offline data construction method and device | |
| CN111125451B (en) | Data production processing method and device, electronic equipment and storage medium | |
| CN106599087B (en) | A kind of Secondary of spatial Information Service | |
| CN105095093A (en) | Intelligent terminal performance test method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |