CN103236945A - OpenFlow-based FlowVisor network system - Google Patents
OpenFlow-based FlowVisor network system Download PDFInfo
- Publication number
- CN103236945A CN103236945A CN2013101202434A CN201310120243A CN103236945A CN 103236945 A CN103236945 A CN 103236945A CN 2013101202434 A CN2013101202434 A CN 2013101202434A CN 201310120243 A CN201310120243 A CN 201310120243A CN 103236945 A CN103236945 A CN 103236945A
- Authority
- CN
- China
- Prior art keywords
- openflow
- controller
- flowvisor
- network
- switch
- 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
Images
Abstract
The invention discloses a QoS (quality of service) integrated management system based on an OpenFlow network, and belongs to the technical field of OpenFlow network design. The QoS integrated management system comprises an OpenFlow switch and an OpenFlow controller. An OpenFlow proxy server is arranged between the OpenFlow switch and the OpenFlow controller, is connected with the OpenFlow switch and the OpenFlow controller respectively, and is used for communicating with the OpenFlow controller through the OpenFlow protocol and the OpenFlow switch. By the network system, a FlowVisor abstractive layer is adopted to split the physical network; and the network system is located between a group of switches and a software-defined network or among a plurality of networks, similar to a management program located between server hardware and software, to allow multiple virtual operating systems to run.
Description
Technical field
The invention belongs to OpenFlow network design technical field, relate in particular to a kind of FlowVisor network system based on OpenFlow.
Background technology
OpenFlow is the same with its structure piece, and FlowVisor can help researcher's fast and flexible ground in large-scale production environment new SDN theory and instrument to be experimentized.FlowVisor is deployed in the production environment of U.S. various places particularly in large-scale campus (for example Stamford) at present.In addition, the participant of two catenets of attaching most importance to research--GENI (GENI) and Internet2 is also using FlowVisor.Yet this does not also mean that FlowVisor is about to appear near your business network.The developer of Stanford University represents, though this platform is highly stable, but still has a long way to go.
FlowVisor is the network virtualization platform that is based upon on the OpenFlow, and it can be divided into physical network a plurality of logical network, thereby realizes open software defined network (SDN).It comes supervising the network for the keeper provides extensive definition rule, rather than comes supervising the network by adjusting router and switch.
Summary of the invention
The objective of the invention is to, the platform of the FlowVisor network virtualization on a kind of OpenFlow of being based upon is provided, be used for physical network is divided into a plurality of logical network, thereby realize open software defined network (SDN).
To achieve these goals, the technical scheme that the present invention proposes is, a kind of FlowVisor network system based on OpenFlow, comprise OpenFlow switch and OpenFlow controller, it is characterized in that between OpenFlow switch and the OpenFlow controller FlowVisor acting server being set, described FlowVisor acting server links to each other with the OpenFlow controller with the OpenFlow switch respectively, and communicates by OpenFlow agreement and OpenFlow switch and OpenFlow controller;
Described FlowVisor acting server is used for the message that the OpenFlow switch sends is tackled, revised and transmits, specifically comprise: when the message of OpenFlow switch transmission need not to revise, directly the message that the OpenFlow switch is sent was transmitted the OpenFlow controller; When the message that sends when the OpenFlow switch need be revised, revise the message that described OpenFlow switch sends according to preset rule after, be forwarded to the OpenFlow controller; When the message of OpenFlow switch transmission is error message, the message that described OpenFlow switch sends is returned the OpenFlow switch.
Described network system also comprises the FlowChecker controller, and described FlowChecker controller links to each other with the OpenFlow controller, is used for obtaining the stream table of OpenFlow controller.
Network system provided by the invention is cut apart physical network by the FlowVisor level of abstraction, it is between one group of switch and software defined network or a plurality of network, managing bandwidth, cpu busy percentage and flowmeter, this is similar to hypervisor between server hardware and software, to allow a plurality of virtual opetrating system operations.
Description of drawings
Fig. 1 is virtual level schematic diagram figure;
Fig. 2 is the connection layout of FlowVisor and FlowChecker;
Fig. 3 is the FlowChecker interaction figure.
Embodiment
Below in conjunction with accompanying drawing, preferred embodiment is elaborated.Should be emphasized that following explanation only is exemplary, rather than in order to limit the scope of the invention and to use.
1、FlowVisor
FlowVisor is cut apart physical network by level of abstraction, it is between one group of switch and software defined network or a plurality of network, managing bandwidth, cpu busy percentage and flowmeter, this is similar to hypervisor between server hardware and software, to allow a plurality of virtual opetrating system operations.
Depending on standard x86 as hypervisor instructs the virtualized server, FlowVisor uses standard OpenFlow instruction set to manage the OpenFlow switch, these instructions are provided with the low level rule, such as how to transmit packet based on the characteristics in the packet gauge outfit.Because all these rules all define by flowmeter, therefore, no matter be from bandwidth or CPU usage, network virtualization does not all increase a lot of expenses or does not almost increase expense, but needs to arrange and revise the outer physics controller of independent band of flowmeter rule in addition.
The fundamental of FlowVisor network is the network section, and the network section is defined by one group of text configuration file.The text configuration file comprises the rule of control diverse network activity, for example permission, read-only and refusal, and its scope comprises source IP addresses, port numbers or the packet gauge outfit information of flow.
It is the virtualized important component part of FlowVisor that section is isolated, but it is still in being in development.In deliver recently the one piece academic article of describing FlowVisor vision and deployment, the author appeals to carry out tight switch and isolates with CPU, but owing to carrying out indirect control by the switch CPU of OpenFlow at present, causes this function to be limited.In view of these restrictions and function, FlowVisor carries out virtual according to following five specifications (coming from this OpenFlow technical report) and isolates:
(1) bandwidth: each section should have special total available bandwidth percentage.
(2) topological structure: each section should have (comprising physics and virtual switch and router) " view " of oneself for network node.The part of section should not know to cut into slices: for controller, FlowVisor seems to be exactly common switch; From the angle of OpenFlow switch, FlowVisor is exactly a controller.
(3) flow: arrange according to above-mentioned rule, flow should be isolated a particular slice or a plurality of section closely consistently.
(4) equipment CPU: heavily loaded physical switches can be lost the packet in slow path.The network manager can upgrade OpenFlow statistical counter and rule, so when the intensive order of evaluation speed limit, FlowVisor should consider cpu resource.
(5) transmit: often be limited on the physical equipment owing to transmit, the network manager should guarantee that a section can not influence transmitting of any particular device, forces it to abandon the rule of another section.
2, the content of network virtualization
Network virtualization is carried out in the groundwork of FlowVisor exactly.By network virtualization, a plurality of separate networks in logic can be shared same physical basis framework, and these networks may have different addressing methods or operative mechanism.
At first can see the virtual of computer.Computer virtualized success clear abstract inseparable with to bottom hardware, like this, computer virtualized layer just can use hardware abstraction, and its allows upper strata Guest operating system cutting apart and share hardware resource.
Similar with it, network virtualization needs network itself to have the hardware abstraction layer of oneself.Hardware abstraction layer needs easily by burst, so that multiple different network can operate on a series of different hardware simultaneously.On hardware abstraction layer, allow new agreement and addressing mode to run on independently separately independently in the burst, in fact they are in the same physical network, and make network have the ability that network application is optimized, or provide self-defining ability to using the owner.Below hardware abstraction layer, can be different hardware.Fig. 1 is virtual level schematic diagram.
3, the realization of network virtualization
Needing to carry out virtualized resource in the network comprises: bandwidth, topology, flow, equipment CPU, transmit.
(1) implementation procedure:
In FlowVisor realized, OpenFlow was used as hardware abstraction layer.Be similar to the level of abstraction on the computer, FlowVisor is arranged between bottom hardware and the upper strata control software; Be similar to operating system and use instruction set control lower floor hardware, FlowVisor uses OpenFlow agreement control layer physical network down.
(2) main feature is as follows:
1) FlowVisor definition burst is: operate in the structural one group of stream of certain switch logic;
2) FlowVisor is placed in OpenFlow controller and inter-exchange, guarantees that each controller all can only see and control the switch that those arrange in advance;
3) FlowVisor arranges a minimum data rate and divides bandwidth by the adfluxion of forming subregion is closed;
4) FlowVisor divides stream table in each switch by following the tracks of the controller of each stream under list item.
(3) FlowVisor realizes target:
1) transparent: the network virtual layer must be transparent to the network hardware and controller;
2) isolate: the network virtual layer must make high degree of isolation between burst;
3) extendible burst definition.
(3) system is described:
FlowVisor is a special OpenFlow controller, is playing the part of the role of Transparent Proxy between OpenFlow switch and OpenFlow controller.All OpenFlow message all will transmit through FlowVisor.FlowVisor uses OpenFlow agreement and controller and switch to communicate mutually.Need not controller is carried out any modification, and they think directly own and switch communicates.
FlowVisor can be according to interior configured strategy when serving as proxy role, to OpenFlow message tackle, revise, operation such as forwarding.Like this, the OpenFlow controller is just only controlled the stream that it is allowed to control, and does not know that its network of controlling was carried out Fragmentation by FlowVisor.Similar, the message process FlowVisor from switch sends also only can be sent to corresponding controller.
FlowVisor has guaranteed transparent and isolation by checking, overriding and supervise from its OpenFlow message of passing through.According to resource allocation policy, type of message, purpose and content, FlowVisor can carry out following several operation: a) do not revise, directly transmit; B) being revised as suitable message transmits then; C) the form bounce-back message with error message arrives the sender.
It seems that from controller FlowVisor is exactly a switch; It seems that from switch FlowVisor becomes a controller again.
4、FlowChecker
(1) effect of FlowChecker
1) the different switches of different basis instrument combinations and the consistency of controller are crossed in checking;
2) correctness of the comprehensive setting that produces with New Deal of checking;
3) debugging accessibility and safety problem.
For the OpenFlow management of combination, FlowChecker has adopted master controller, and (Master Controller MC) moves FlowChecker and communicate to verify with the OF controller and conciliate never consistency or any error configurations.
Generally speaking, the result of this project is exactly a configuration verification instrument, and the application program by keeper or main operation controller is used for checking, analyzes and forces the end-to-end configuration of OpenFlow when operation to cross over a plurality of combinations in other words conj.or perhaps.
(2) FlowChecker operation
1) first kind of situation is used as independently service.The connection of FlowChecker is as above shown in Figure 2.In this case, the OpenFlow controller can be communicated by letter with FlowChecker by the SSL escape way.FlowChecker inquires about switch by transmitting token to the OpenFlow switch, and query contents comprises topology, user, controller ID and name binding.Controller sends request by the SSL escape way to FlowChecker and accepts answer.
2) another kind of situation, the stream table can be existed in the database.Clearly, this is the trade-off between a simplicity and the fail safe.
At present, FlowChecker has adopted first kind of situation.The mutual example of FlowChecker as shown in Figure 3.
1) FlowChecker is to controller request stream table information;
2) controller sends a piece of news to switch, and message has been passed through FlowVisor;
3) 3a represents: FlowVisor has tackled that message, sends the burst rule to FlowChecker;
4) 3b represents: the OpenFlow switch sends to controller with the stream table;
5) controller sends to FlowChecker with the stream table.
Now, FlowChecker can verify whether stripping strategy guarantees correctly in this stream table.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (2)
1. FlowVisor network system based on OpenFlow, comprise OpenFlow switch and OpenFlow controller, it is characterized in that between OpenFlow switch and the OpenFlow controller FlowVisor acting server being set, described FlowVisor acting server links to each other with the OpenFlow controller with the OpenFlow switch respectively, and communicates by OpenFlow agreement and OpenFlow switch and OpenFlow controller;
Described FlowVisor acting server is used for the message that the OpenFlow switch sends is tackled, revised and transmits, specifically comprise: when the message of OpenFlow switch transmission need not to revise, directly the message that the OpenFlow switch is sent was transmitted the OpenFlow controller; When the message that sends when the OpenFlow switch need be revised, revise the message that described OpenFlow switch sends according to preset rule after, be forwarded to the OpenFlow controller; When the message of OpenFlow switch transmission is error message, the message that described OpenFlow switch sends is returned the OpenFlow switch.
2. network system according to claim 1 is characterized in that described network system also comprises the FlowChecker controller, and described FlowChecker controller links to each other with the OpenFlow controller, is used for obtaining the stream table of OpenFlow controller.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2013101202434A CN103236945A (en) | 2013-04-08 | 2013-04-08 | OpenFlow-based FlowVisor network system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2013101202434A CN103236945A (en) | 2013-04-08 | 2013-04-08 | OpenFlow-based FlowVisor network system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103236945A true CN103236945A (en) | 2013-08-07 |
Family
ID=48884963
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2013101202434A Pending CN103236945A (en) | 2013-04-08 | 2013-04-08 | OpenFlow-based FlowVisor network system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103236945A (en) |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103607348A (en) * | 2013-11-27 | 2014-02-26 | 北京邮电大学 | Virtual network flow classifying method based on OpenFlow protocol |
| CN103905523A (en) * | 2013-12-23 | 2014-07-02 | 浪潮(北京)电子信息产业有限公司 | Cloud computing network virtualization method and system based on SDN |
| CN104298543A (en) * | 2014-11-07 | 2015-01-21 | 陈桂芳 | Implementation method for one-to-multiple virtualization of OPENFlOW switch |
| CN104468633A (en) * | 2014-12-31 | 2015-03-25 | 蓝盾信息安全技术股份有限公司 | SDN southing security proxy product |
| WO2015039574A1 (en) * | 2013-09-18 | 2015-03-26 | 华为技术有限公司 | Network failure recovery method, controller and switch |
| CN104486290A (en) * | 2014-11-18 | 2015-04-01 | 中国科学技术大学 | Stream media cloud transparent service device based on open flow |
| CN104702512A (en) * | 2013-12-06 | 2015-06-10 | 智梵网络科技有限公司 | Hierarchical control in software-defined network (sdn) |
| CN104811382A (en) * | 2014-01-28 | 2015-07-29 | 华为技术有限公司 | Data packet processing method and device |
| WO2015149505A1 (en) * | 2014-04-04 | 2015-10-08 | 中兴通讯股份有限公司 | Sdn application integration, management and control method, system and device |
| CN105024990A (en) * | 2015-03-30 | 2015-11-04 | 清华大学 | Deployment method and device for network security attack and defense exercise environment |
| CN105450525A (en) * | 2014-05-28 | 2016-03-30 | 国际商业机器公司 | Method and equipment for using route switching equipment |
| CN105706074A (en) * | 2013-09-30 | 2016-06-22 | 慧与发展有限责任合伙企业 | Software-defined network application deployment |
| WO2017032280A1 (en) * | 2015-08-21 | 2017-03-02 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
| CN106537839A (en) * | 2013-09-13 | 2017-03-22 | 瑞典爱立信有限公司 | Service placement for inline services chaining with multiple instances |
| US9762508B2 (en) | 2014-10-02 | 2017-09-12 | Microsoft Technology Licensing, Llc | Relay optimization using software defined networking |
| CN107318113A (en) * | 2016-04-27 | 2017-11-03 | 华为技术有限公司 | Network sliced sheet processing method and device |
| WO2018045990A1 (en) * | 2016-09-09 | 2018-03-15 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
| WO2018049583A1 (en) * | 2016-09-14 | 2018-03-22 | 华为技术有限公司 | User plane sharing method, device and supervising management device based on network slicing |
| CN108418847A (en) * | 2017-02-09 | 2018-08-17 | ***通信集团甘肃有限公司 | A kind of network traffic cache system, method and device |
| CN109417572A (en) * | 2016-10-31 | 2019-03-01 | 华为技术有限公司 | The system and method that chain of command function carries out tactful configuration to control plane function |
| CN114338119A (en) * | 2021-12-23 | 2022-04-12 | 中国电信股份有限公司 | Network isolation method and system and proxy equipment |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102959910A (en) * | 2010-06-25 | 2013-03-06 | 瑞典爱立信有限公司 | Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel |
-
2013
- 2013-04-08 CN CN2013101202434A patent/CN103236945A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102959910A (en) * | 2010-06-25 | 2013-03-06 | 瑞典爱立信有限公司 | Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel |
Non-Patent Citations (5)
| Title |
|---|
| E AL-SHAER,S AL-HAJ: "FlowChecker: Configuration analysis and verification of federated OpenFlow", 《PROCEEDINGS OF THE 3RD ACM WORKSHOP ON ASSURABLE AND USABLE SECURITY CONFIGURATION》 * |
| MICHAEL MORISY: "基于OpenFlow的FlowVisor开辟了开放网络虚拟化之路（一）", 《TECHTARGET》 * |
| R SHERWOOD,G GIBB,KK YAP, G APPENZELLER: "FlowVisor：A Network Virtualization Layer", 《OPENFLOW》 * |
| R SHERWOOD,G GIBB,KK YAP, G APPENZELLER: "FlowVisor：A Network Virtualization Layer", 《OPENFLOW》, 14 October 2009 (2009-10-14) * |
| 董青（DONGSWEET）: "《FlowVisor、Checker笔记》", 《百度文库》 * |
Cited By (35)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106537839B (en) * | 2013-09-13 | 2020-01-10 | 瑞典爱立信有限公司 | Service placement for online service chains with multiple instances |
| CN106537839A (en) * | 2013-09-13 | 2017-03-22 | 瑞典爱立信有限公司 | Service placement for inline services chaining with multiple instances |
| WO2015039574A1 (en) * | 2013-09-18 | 2015-03-26 | 华为技术有限公司 | Network failure recovery method, controller and switch |
| CN105706074A (en) * | 2013-09-30 | 2016-06-22 | 慧与发展有限责任合伙企业 | Software-defined network application deployment |
| CN103607348A (en) * | 2013-11-27 | 2014-02-26 | 北京邮电大学 | Virtual network flow classifying method based on OpenFlow protocol |
| CN104702512A (en) * | 2013-12-06 | 2015-06-10 | 智梵网络科技有限公司 | Hierarchical control in software-defined network (sdn) |
| CN104702512B (en) * | 2013-12-06 | 2017-10-24 | 智梵网络科技有限公司 | The multi-level control system and computer implemented method of network management are provided for software defined network |
| CN103905523A (en) * | 2013-12-23 | 2014-07-02 | 浪潮(北京)电子信息产业有限公司 | Cloud computing network virtualization method and system based on SDN |
| CN104811382B (en) * | 2014-01-28 | 2018-05-29 | 华为技术有限公司 | The processing method and device of data packet |
| CN104811382A (en) * | 2014-01-28 | 2015-07-29 | 华为技术有限公司 | Data packet processing method and device |
| WO2015113410A1 (en) * | 2014-01-28 | 2015-08-06 | 华为技术有限公司 | Data packet processing method and apparatus |
| WO2015149505A1 (en) * | 2014-04-04 | 2015-10-08 | 中兴通讯股份有限公司 | Sdn application integration, management and control method, system and device |
| CN105450525B (en) * | 2014-05-28 | 2018-05-01 | 国际商业机器公司 | The method and apparatus used for route exchange device |
| CN105450525A (en) * | 2014-05-28 | 2016-03-30 | 国际商业机器公司 | Method and equipment for using route switching equipment |
| US9762508B2 (en) | 2014-10-02 | 2017-09-12 | Microsoft Technology Licensing, Llc | Relay optimization using software defined networking |
| CN104298543A (en) * | 2014-11-07 | 2015-01-21 | 陈桂芳 | Implementation method for one-to-multiple virtualization of OPENFlOW switch |
| CN104486290B (en) * | 2014-11-18 | 2017-10-03 | 中国科学技术大学 | A kind of Streaming Media cloud transparent service device based on OpenFlow |
| CN104486290A (en) * | 2014-11-18 | 2015-04-01 | 中国科学技术大学 | Stream media cloud transparent service device based on open flow |
| CN104468633B (en) * | 2014-12-31 | 2017-10-10 | 蓝盾信息安全技术股份有限公司 | A kind of SDN south orientations TSM Security Agent product |
| CN104468633A (en) * | 2014-12-31 | 2015-03-25 | 蓝盾信息安全技术股份有限公司 | SDN southing security proxy product |
| CN105024990A (en) * | 2015-03-30 | 2015-11-04 | 清华大学 | Deployment method and device for network security attack and defense exercise environment |
| WO2017032280A1 (en) * | 2015-08-21 | 2017-03-02 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
| US10644955B2 (en) | 2015-08-21 | 2020-05-05 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
| CN107318113A (en) * | 2016-04-27 | 2017-11-03 | 华为技术有限公司 | Network sliced sheet processing method and device |
| CN107318113B (en) * | 2016-04-27 | 2021-09-21 | 华为技术有限公司 | Network slice processing method and device |
| US10880176B2 (en) | 2016-09-09 | 2020-12-29 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
| WO2018045990A1 (en) * | 2016-09-09 | 2018-03-15 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
| US10411964B2 (en) | 2016-09-09 | 2019-09-10 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
| WO2018049583A1 (en) * | 2016-09-14 | 2018-03-22 | 华为技术有限公司 | User plane sharing method, device and supervising management device based on network slicing |
| CN109417572A (en) * | 2016-10-31 | 2019-03-01 | 华为技术有限公司 | The system and method that chain of command function carries out tactful configuration to control plane function |
| CN109417572B (en) * | 2016-10-31 | 2020-10-27 | 华为技术有限公司 | System and method for policy configuration of control plane functions by management plane functions |
| US10812395B2 (en) | 2016-10-31 | 2020-10-20 | Huawei Technologies Co., Ltd. | System and method for policy configuration of control plane functions by management plane functions |
| CN108418847B (en) * | 2017-02-09 | 2021-04-16 | ***通信集团甘肃有限公司 | Network traffic caching system, method and device |
| CN108418847A (en) * | 2017-02-09 | 2018-08-17 | ***通信集团甘肃有限公司 | A kind of network traffic cache system, method and device |
| CN114338119A (en) * | 2021-12-23 | 2022-04-12 | 中国电信股份有限公司 | Network isolation method and system and proxy equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103236945A (en) | OpenFlow-based FlowVisor network system | |
| US10649798B2 (en) | Virtual switching method, related apparatus, and computer system | |
| CN108989091B (en) | Tenant network isolation method based on Kubernetes network, storage medium and electronic equipment | |
| US8639783B1 (en) | Policy based configuration of interfaces in a virtual machine environment | |
| EP2930884B1 (en) | Object-oriented network virtualization | |
| US9203645B2 (en) | Virtual input-output connections for machine virtualization | |
| EP2776925B1 (en) | Dynamic policy based interface configuration for virtualized environments | |
| TWI521437B (en) | Method and system for network configuration and/or provisioning based on open virtualization format (ovf) metadata | |
| CN103026660B (en) | Network policy configuration method, management equipment and network management centre device | |
| US20150350102A1 (en) | Method and System for Integrated Management of Converged Heterogeneous Resources in Software-Defined Infrastructure | |
| CN103905523A (en) | Cloud computing network virtualization method and system based on SDN | |
| US9485187B2 (en) | Intelligent software-defined networking based service paths | |
| TWI477110B (en) | Method and system for nic-centric hyper-channel distributed network management | |
| CN109479029B (en) | Data packet forwarding unit in software defined network | |
| EP3338406B1 (en) | Communication framework for a federation of network controllers | |
| US20140115126A1 (en) | System for controlling and verifying open programmable network and method thereof | |
| CN108512779A (en) | Control information transmitting methods, server and system | |
| WO2018049583A1 (en) | User plane sharing method, device and supervising management device based on network slicing | |
| Gerola et al. | Demonstrating inter-testbed network virtualization in OFELIA SDN experimental facility | |
| WO2014064976A1 (en) | Network device, control method, and program | |
| KR101543735B1 (en) | System and method for processing packets for nfv | |
| KR20190066743A (en) | Software defined networking based network virtualization system, apparatus, and method supporting multiple protocols | |
| Taher | Testing of floodlight controller with mininet in sdn topology | |
| CN106506238A (en) | A kind of network element management method and system | |
| TWI668973B (en) | Schedulable security protection system based on software-defined network and method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20130807 |
|
| RJ01 | Rejection of invention patent application after publication |