CN103236945A - OpenFlow-based FlowVisor network system - Google Patents

OpenFlow-based FlowVisor network system Download PDF

Info

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
switch
controller
network
flowvisor
Prior art date
Application number
CN2013101202434A
Other languages
Chinese (zh)
Inventor
程远
冯刚
常宁
Original Assignee
北京天地互连信息技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 北京天地互连信息技术有限公司 filed Critical 北京天地互连信息技术有限公司
Priority to CN2013101202434A priority Critical patent/CN103236945A/en
Publication of CN103236945A publication Critical patent/CN103236945A/en

Links

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

基于OpenF I ow的F1wVisor网络系统 Based OpenF I ow of F1wVisor network system

技术领域 FIELD

[0001 ] 本发明属于OpenFlow网络设计技术领域,尤其涉及一种基于OpenFlow的FlowVisor网络系统。 [0001] The present invention belongs to the technical field OpenFlow network design, particularly to a network system based on OpenFlow-FlowVisor.

背景技术 Background technique

[0002] 与其构建块OpenFlow —样,FlowVisor能够帮助研究人员快速灵活地在大型生产环境对新的SDN理念和工具进行实验。 [0002] and its building blocks OpenFlow - like, FlowVisor can help researchers quickly and flexibly to experiment with new concepts and tools in SDN large-scale production environment. 目前FlowVisor被部署在美国各地的生产环境中,特别是在大型校园(例如斯坦福)。 FlowVisor currently being deployed in a production environment across the United States, especially in large campus (eg Stanford). 此外,两个以研究为重点的大型网络一全球网络创新环境(GENI)和Internet2的参与者也在使用FlowVisor。 In addition, a global network of innovation environment (GENI) and Internet2 participants to two studies focusing on large networks also use FlowVisor. 然而,这并不意味着FlowVisor即将出现在你附近的业务网络中。 However, this does not mean FlowVisor will appear in the vicinity of your business network. 斯坦福大学开发人员表示,虽然该平台非常稳定,但仍然有很长的路要走。 Stanford developer said that although the platform is very stable, but still have a long way to go.

[0003] FlowVisor是建立在OpenFlow之上的网络虚拟化平台,它可以将物理网络分成多个逻辑网络,从而实现开放软件定义网络(SDN)。 [0003] FlowVisor network is built on top of OpenFlow virtualization platform, which can be a physical network into multiple logical networks, in order to achieve an open software-defined network (SDN). 它为管理员提供了广泛定义规则来管理网络,而不是通过调整路由器和交换机来管理网络。 It provides administrators with a broad definition of rules to manage the network, rather than to manage the network by adjusting the routers and switches.

发明内容 SUMMARY

[0004] 本发明的目的在于,提供一种建立在OpenFlow之上的FlowVisor网络虚拟化平台,用于将物理网络分成多个逻辑网络,从而实现开放软件定义网络(SDN)。 [0004] The object of the present invention is to provide a built on the FlowVisor OpenFlow network virtualization platform for the physical network into multiple logical networks, in order to achieve an open software-defined network (SDN).

[0005] 为了实现上述目的,本发明提出的技术方案是,一种基于OpenFlow的FlowVisor网络系统,包括OpenFlow交换机和OpenFlow控制器,其特征在于OpenFlow交换机和OpenFlow控制器之间设置FlowVisor代理服务器,所述FlowVisor代理服务器分别与OpenFlow交换机和OpenFl ow控制器相连,并通过OpenFlow协议与OpenFlow交换机和OpenFlow控制器进行通信; [0005] To achieve the above object, the technical solution proposed by the invention is based on the FlowVisor OpenFlow network system comprising OpenFlow OpenFlow switch and a controller, wherein the proxy server is provided between FlowVisor OpenFlow OpenFlow controller and switch, the FlowVisor said proxy server, respectively OpenFl ow OpenFlow switch and connected to the controller, and the communication protocol via OpenFlow OpenFlow OpenFlow controller and switch;

[0006] 所述Fl owV isor代理服务器用于对OpenF I ow交换机发送的消息进行拦截、修改和转发,具体包括:当OpenFlow交换机发送的消息无需修改时,直接将OpenFlow交换机发送的消息转发OpenFlow控制器;当OpenFlow交换机发送的消息需要修改时,根据预先设定的规则修改所述OpenFlow交换机发送的消息后,转发至OpenFlow控制器;当OpenFlow交换机发送的消息是错误消息时,将所述OpenFlow交换机发送的消息返回OpenFlow交换机。 [0006] Fl owV isor the proxy server for a message sent by the switch OpenF I ow to intercept, modify and forwarding comprises: when the message is sent without modification OpenFlow switch, the switch transmits the message directly OpenFlow OpenFlow forwarding control ; a OpenFlow switch after the message is transmitted when the need to modify, the modification messages sent OpenFlow switch according to a predetermined rule, OpenFlow forwarded to the controller; OpenFlow switch when the message is sent when an error message, the OpenFlow switch sending a return message OpenFlow switch.

[0007] 所述网络系统还包括FlowChecker控制器,所述FlowChecker控制器与OpenFlow控制器相连,用于获取OpenFlow控制器中的流表。 The [0007] system further comprises a network FlowChecker a controller, coupled to said controller FlowChecker OpenFlow controller, configured to obtain a flow table OpenFlow controller.

[0008] 本发明提供的网络系统通过FlowVisor抽象层来分割物理网络,它位于一组交换机和软件定义网络或多个网络之间,管理带宽、CPU利用率和流量表,这类似于管理程序位于服务器硬件和软件之间,以允许多个虚拟操作系统运行。 [0008] The network system according to the present invention is provided to divide by FlowVisor physical network abstraction layer, which is located between a group of switches and a plurality of software-defined network or networks, the bandwidth management, CPU utilization, and flow meters, which is similar to hypervisor sits between the server hardware and software to allow multiple virtual operating systems to run.

附图说明 BRIEF DESCRIPTION

[0009] 图1是是虚拟化层次示意图图;[0010]图 2 是FlowVisor 和FlowChecker 的连接图; [0009] FIG. 1 is a schematic diagram of a hierarchical virtualization; [0010] FIG 2 is a connection diagram of FlowVisor and FlowChecker;

[0011]图 3 是FlowChecker 交互图。 [0011] FIG. 3 is FlowChecker interaction FIG.

具体实施方式 Detailed ways

[0012] 下面结合附图,对优选实施例作详细说明。 [0012] below with reference to the accompanying drawings, preferred embodiments described in detail. 应该强调的是,下述说明仅仅是示例性的,而不是为了限制本发明的范围及其应用。 It should be emphasized that the following description is merely exemplary in nature and is not intended to limit the scope and application of the invention.

[0013] 1> FlowVisor [0013] 1> FlowVisor

[0014] FlowVisor通过抽象层来分割物理网络,它位于一组交换机和软件定义网络或多个网络之间,管理带宽、CPU利用率和流量表,这类似于管理程序位于服务器硬件和软件之间,以允许多个虚拟操作系统运行。 [0014] FlowVisor be divided between hardware and software server through a physical network abstraction layer, which is located between a group of switches and a plurality of software-defined network or networks, the bandwidth management, CPU utilization, and flow meters, which is similar to hypervisor sits to allow multiple virtual operating systems to run.

[0015] 正如管理程序依赖于标准x86指令来虚拟化服务器一样,FlowVisor使用标准OpenFlow指令集来管理OpenFlow交换机,这些指令设置了低级别规则,比如如何基于数据包表头中的特点来转发数据包。 [0015] As the management program relies on standard x86 instructions virtualization server as, FlowVisor using standard OpenFlow instruction set management OpenFlow switch, these instructions set the low-level rules, such as how based on the characteristics of the packet header to forward packets . 由于所有这些规则都是通过流量表定义的,因此,无论是从带宽还是CPU使用率来看,网络虚拟化都没有增加很多开销或者几乎没有增加开销,不过另外需要设置和修改流量表规则的单独的带外物理控制器。 Since all of these rules are defined by a flow meter, therefore, whether it is from the point of view of bandwidth or CPU usage, network virtualization did not add a lot of overhead or almost no increase in cost, but in addition you need to set and modify the flow meter rule alone with an outer physical controller.

[0016] FlowVisor网络的基本要素是网络切片,网络切片是由一组文本配置文件来定义的。 [0016] FlowVisor basic elements of a network is a network slices, slice is a network composed of a set of text to define the profile. 文本配置文件包含控制各种网络活动的规则,例如允许、只读和拒绝,其范围包括流量的来源IP地址、端口号或者数据包表头信息。 Text profile contains control various network activity rules, such as allowing, read-only, and reject, which include traffic source IP address, port number or packet header information.

[0017] 切片隔离是FlowVisor虚拟化的重要组成部分,但它仍然在处于发展中。 [0017] FlowVisor slice isolation is an important part of virtualization, but it is still under development. 在近日发表的一篇描述FlowVisor愿景和部署的学术文章中,作者呼吁进行严密的交换机与CPU隔离,但由于目前只能通过OpenFlow对交换机CPU进行间接管理,导致该功能被限制。 In the recently published an article describing FlowVisor vision and deployment of scholarly articles, the authors called for strict isolation switch with the CPU, but only indirectly, due to the current management of the switch CPU by OpenFlow, causing the function is limited. 鉴于这些限制和功能,FlowVisor按照以下五个规格(出自该OpenFlow技术报告)来进行虚拟化和隔离: Given these limitations and capabilities, FlowVisor the following five specifications (technical report from the OpenFlow) to virtualization and isolation:

[0018] (I)带宽:每个切片应该具有专门的总可用带宽百分比。 [0018] (I) Bandwidth: each section should have a specific percentage of the total available bandwidth.

[0019] (2)拓扑结构:每个切片对于网络节点(包括物理和虚拟交换机及路由器)应该有自己的“看法”。 [0019] (2) topology: each slice for network nodes (including physical and virtual switches and routers) should have their own "views." 切片的组成部分应该是不知道切片的:对于控制器而言,FlowVisor看起来就是普通的交换机;从OpenFlow交换机的角度来看,FlowVisor就是一个控制器。 Part of the sections should not know the slice: For control purposes, FlowVisor seems, is an ordinary switch; OpenFlow switch from the point of view, FlowVisor is a controller.

[0020] (3)流量:根据上述规则设置,流量应该严密地始终如一地隔离到一个特定切片或者多个切片。 [0020] (3) Flow rate: the above rule set, it should flow consistently isolated closely to a particular slice or multiple slices.

[0021] (4)设备CPU:重载物理交换机可以丢掉缓慢路径的数据包。 [0021] (4) apparatus CPU: Overloaded physical switch may discard the packets slow path. 网络管理员会更新OpenFlow统计计数器和规则,所以在评定限速密集命令时,FlowVisor应该考虑CPU资源。 OpenFlow network administrator can update statistics counters and rules, so dense in assessing the speed limit command, FlowVisor should consider CPU resources.

[0022] (5)转发表:由于转发表往往被限定在物理设备上,网络管理员应确保一个切片不会影响任何特定设备的转发表,迫使它放弃另一切片的规则。 [0022] (5) forwarding: Due to forwarding is often limited on the physical device, network administrators should ensure that a slice will not affect any particular device forwarding, forcing it to abandon the rules of another slice.

[0023] 2、网络虚拟化的内容 [0023] 2, the content of network virtualization

[0024] FlowVisor的主要工作就是进行网络虚拟化。 [0024] The main FlowVisor is network virtualization. 通过网络虚拟化,多个逻辑上相互独立的网络可以共享同一个物理基础架构,这些网络可能具有不同的编址方法或运转机制。 Through network virtualization, multiple logically independent network can share the same physical infrastructure, these networks may have a different method of addressing or operating mechanisms.

[0025] 首先可以看计算机的虚拟化。 [0025] First of all you can see virtual machine. 计算机虚拟化的成功与对底层硬件的清晰抽象密不可分,这样,计算机虚拟化层便可以使用硬件抽象,它允许上层Guest操作系统对硬件资源的分割与共享。 Computer virtualization success and clear abstract closely to the underlying hardware, so the computer can use virtualization hardware abstraction layer, which allows the upper division and sharing of Guest operating system on hardware resources. [0026] 与之类似的,网络虚拟化需要网络本身带有自己的硬件抽象层。 [0026] Similarly, the network requires virtual network itself with its own hardware abstraction layer. 硬件抽象层需要容易被分片,以使得多种不同的网络可以同时运行在一系列不同的硬件之上。 Hardware Abstraction Layer needed to be fragmented easily, so that the plurality of different networks can run simultaneously on a number of different hardware. 在硬件抽象层之上,允许有新的协议和编址方式独立地运行于在各自独立的分片中,实际上他们都处于同一个物理网络中,并使得网络具有对网络应用进行优化的能力,或对应用所有者提供自定义的能力。 On the hardware abstraction layer, allowing new protocols and addressing mode to run independently in separate slice, in fact they are in the same physical network, and that the network has the ability to optimize the network application , or application owners the ability to provide custom. 在硬件抽象层以下,可以是不同的硬件。 In the following hardware abstraction layer, it may be different hardware. 图1为虚拟化层次示意图。 Figure 1 is a schematic diagram of the virtualization level.

[0027] 3、网络虚拟化的实现 [0027] 3, network virtualization implementation

[0028] 网络中需要进行虚拟化的资源包括:带宽、拓扑、流量、设备CPU、转发表。 [0028] network that need to be virtualized resources include: bandwidth and topology, traffic, equipment CPU, forwarding.

[0029] (I)实现过程: [0029] (I) implementation:

[0030] 在FlowVisor实现中,OpenFlow被作为硬件抽象层。 [0030] In FlowVisor implementations, OpenFlow is used as the hardware abstraction layer. 类似于计算机上的抽象层,FlowVisor被设置于底层硬件和上层控制软件之间;类似于操作系统使用指令集控制下层硬件,FlowVisor使用OpenFlow协议控制下层物理网络。 Similar abstraction layer on the computer, FlowVisor is disposed between the upper layer and the underlying hardware control software; instruction set similar to the operation control system using the underlying hardware, FlowVisor OpenFlow protocol used to control the underlying physical network.

[0031] (2)主要特点如下: [0031] (2) The main features are as follows:

[0032] DFlowVisor定义分片为:运行在某个交换机逻辑结构上的一组流; [0032] DFlowVisor slice is defined as: a set of flow running in a logical structure of the switch;

[0033] 2)FlowVisor安置于OpenFlow控制器与交换机间,保证每一个控制器都只能看到和控制那些事先设置的交换机; [0033] 2) FlowVisor OpenFlow disposed between the controller and the switch, to ensure that each controller can only see and control those switches set in advance;

[0034] 3) FlowVisor通过对组成分区的流集合设置一个最小数据速率来划分带宽; [0034] 3) FlowVisor provided by a set of flows consisting of a partition dividing a minimum data rate to the bandwidth;

[0035] 4) FlowVisor通过跟踪每个流表项所属的控制器来划分每个交换机中的流表。 [0035] 4) FlowVisor table to divide the flow through each switch tracking controller for each flow entry belongs.

[0036] (3) FlowVisor 实现目标: [0036] (3) FlowVisor objectives:

[0037] I)透明:网络虚拟层须对网络硬件和控制器透明; [0037] I) Transparent: Network virtualization layer must be transparent to the network hardware, and a controller;

[0038] 2)隔离:网络虚拟层必须使得分片间高度隔离; [0038] 2) Isolation: virtual network must be such that high isolation layer slice;

[0039] 3)可扩展的分片定义。 [0039] 3) may be extended slice definition.

[0040] (3)系统描述: [0040] (3) System Description:

[0041] FlowVisor是一个特殊的OpenFlow控制器,扮演着OpenFlow交换机和OpenFlow控制器间透明代理的角色。 [0041] FlowVisor is a special OpenFlow controller, playing the role of OpenFlow controller and OpenFlow switch between transparent proxy. 所有OpenFlow消息都将透过FlowVisor进行传送。 All OpenFlow messages will be sent through FlowVisor. FlowVisor使用OpenFlow协议与控制器与交换机相互进行通信。 FlowVisor OpenFlow protocol used with the switch and the controller communicate with each other. 无需对控制器进行任何修改,并且它们认为自己直接与交换机进行通信。 The controller does not need to make any changes, and they consider themselves to communicate directly with the switch.

[0042] FlowVisor在充当代理角色时,会根据内配置的策略,对OpenFlow消息进行拦截、修改、转发等操作。 [0042] FlowVisor when acting as a proxy role, according to the policy in the configuration of the OpenFlow message interception, modification, forwarding and other operations. 这样,OpenFlow控制器就只控制其被允许控制的流,并不知道其所控制的网络被FlowVisor进行过分片操作。 Thus, only the OpenFlow controller which controls flow of control is permitted, it does not know the network control sheet is subjected to excessive operation FlowVisor. 相似的,从交换机发出的消息经过FlowVisor,也只会被发送到相应的控制器。 Similarly, the message sent from the switch through FlowVisor, will only be transmitted to the respective controllers.

[0043] FlowVisor通过检查、覆写和监管从其通过的OpenFlow消息来保证了透明和隔离。 [0043] FlowVisor by checking, overwrite and supervision message via its OpenFlow to ensure transparency and isolation. 根据资源分配策略、消息类型、目的和内容,FlowVisor会进行下列几种操作:a)不修改,直接转发山)修改为合适的消息然后转发;c)以错误信息的形式反弹消息到发送者。 The resource allocation policy, message type, content and purpose, FlowVisor will perform the following types of operations: a) not to modify, and forwards Hill) to an appropriate message and forwards; c) bounce message to the sender in the form of error messages.

[0044] 从控制器看来,FlowVisor就是一个交换机;从交换机看来,FlowVisor又成为了一台控制器。 [0044] From the controller seems, FlowVisor is a switch; the switch opinion, FlowVisor has become one controller.

[0045] 4> FlowChecker [0045] 4> FlowChecker

[0046] (I) FlowChecker 的作用 [0046] (I) FlowChecker action

[0047] I)验证跨越不同的基础设置组合的不同交换机和控制器的一致性; [0047] I) to verify consistency across different switches and controllers of different settings of the base;

[0048] 2)验证用新协议产生的综合设置的正确性;[0049] 3)调试可达性和安全问题。 [0048] 2) verify the correctness of a comprehensive agreement with a new set of generated; [0049] 3) debug accessibility and security issues.

[0050]对于组合的 OpenFlow 管理,FlowChecker 米用了主控制器(Master Controller,MC)来运行FlowChecker并与OF控制器进行通信来验证和解决不一致性或任何错误配置。 [0050] For OpenFlow management portfolio, FlowChecker rice with the master controller (Master Controller, MC) and run FlowChecker OF communicate with the controller to verify and resolve any inconsistencies or errors configuration.

[0051] 总的来说,这个项目的结果就是一个配置验证工具,或者说是一个由管理员或主控制器运行的应用程序,用于验证、分析和迫使OpenFlow在运行时的端到端配置跨越多个组合。 [0051] In summary, the results of this project is to validate a configuration tool, or is an application run by an administrator or master controller for validation, analysis and forcing the end OpenFlow at run-time configuration span multiple combination.

[0052] (2) FlowChecker 操作 [0052] (2) FlowChecker operation

[0053] I)第一种情况,当作独立的服务。 [0053] I) the first case, as a separate service. FlowChecker的连接如上图2所示。 FlowChecker connector 2 as shown above. 这种情况下,OpenFlow控制器会通过SSL安全通道同FlowChecker通信。 In this case, OpenFlow controller communicate with FlowChecker SSL secure channel. FlowChecker通过传递令牌到OpenFlow交换机,对交换机进行查询,查询内容包含拓扑、用户、控制器ID和名字绑定。 FlowChecker by passing the token to the OpenFlow switch, the switch query, the query comprising the content of the topology, the user, the controller ID and name bindings. 控制器通过SSL安全通道向FlowChecker发送请求接受回复。 Controller sends a request to the SSL secure channel FlowChecker accept replies.

[0054] 2)另一种情况,流表可以被存在数据库中。 [0054] 2) the other case, the stream table may be present in the database. 很明显,这是一个简单性与安全性之间的trade-off。 Obviously, this is a trade-off between simplicity and security.

[0055] 目前,FlowChecker米用了第一种情况。 [0055] Currently, FlowChecker meters with the first case. 一个FlowChecker交互的例子如图3所 An example of FIG. 3 interaction FlowChecker

/Jn o / Jn o

[0056] I) FlowChecker向控制器请求流表信息; [0056] I) FlowChecker request flow table information to the controller;

[0057] 2)控制器向交换机发送一条消息,消息通过了FlowVisor ; [0057] 2) a message to the switch controller sends a message through the FlowVisor;

[0058] 3) 3a表示:Fl owVisor拦截下了那条消息,向FlowChecker发送分片规则; [0058] 3) 3a represents: Fl owVisor intercepted under a piece of message transmission rules to fragmentation FlowChecker;

[0059] 4) 3b表示:0penFlow交换机将流表发送给控制器; [0059] 4) 3b represents: 0penFlow switch the flow table to the controller;

[0060] 5)控制器将流表发送给FlowChecker。 [0060] 5) a flow controller to send table FlowChecker.

[0061] 现在,FlowChecker可以验证分片策略在这个流表中是否保证正确。 [0061] Now, FlowChecker can verify this fragmentation strategy to ensure the flow table if correct.

[0062] 以上所述,仅为本发明较佳的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到的变化或替换,都应涵盖在本发明的保护范围之内。 [0062] The above are only the preferred specific embodiments of the invention, but the scope of the present invention is not limited thereto, any skilled in the art in the art within the scope of the invention disclosed can be easily thought variations or replacements shall fall within the protection scope of the present invention. 因此,本发明的保护范围应该以权利要求的保护范围为准。 Accordingly, the scope of the present invention should be defined by the scope of the claims.

Claims (2)

1.一种基于OpenFlow的FlowVisor网络系统,包括OpenFlow交换机和OpenFlow控制器,其特征在于OpenFlow交换机和OpenFlow控制器之间设置FlowVisor代理服务器,所述FlowVisor代理服务器分别与OpenFlow交换机和OpenFlow控制器相连,并通过OpenFlow协议与OpenFlow交换机和OpenFlow控制器进行通信; 所述FlowVisor代理服务器用于对OpenFlow交换机发送的消息进行拦截、修改和转发,具体包括:当OpenFlow交换机发送的消息无需修改时,直接将OpenFlow交换机发送的消息转发OpenFlow控制器;当OpenFlow交换机发送的消息需要修改时,根据预先设定的规则修改所述OpenFlow交换机发送的消息后,转发至OpenFlow控制器;当OpenFlow交换机发送的消息是错误消息时,将所述OpenFlow交换机发送的消息返回OpenFlow交换机。 A network-based system of OpenFlow FlowVisor, including OpenFlow OpenFlow switch and a controller, wherein the proxy server is provided between FlowVisor OpenFlow OpenFlow switch and a controller connected to the proxy server FlowVisor OpenFlow OpenFlow controller and switch, respectively, and by agreement with OpenFlow OpenFlow OpenFlow switch and a controller in communication; FlowVisor the proxy server to a message sent by the switch OpenFlow intercept, modify and forwarding comprises: when the message is sent without modification OpenFlow switch directly OpenFlow forwarding the message sent by the switch controller OpenFlow; OpenFlow switch when sending messages need to be modified, based on a preset rule modifying the OpenFlow message sent by the switch, the OpenFlow forwarded to the controller; OpenFlow switch when the message is sent an error message when the message sent by the switch to return the OpenFlow OpenFlow switch.
2.根据权利要求1所述的网络系统,其特征在于所述网络系统还包括FlowChecker控制器,所述FlowChecker控制器与OpenFlow控制器相连,用于获取OpenFlow控制器中的流表。 2. The network system according to claim 1, wherein said system further comprises a network connected FlowChecker controller, said controller FlowChecker OpenFlow controller, configured to obtain a flow table OpenFlow controller.
CN2013101202434A 2013-04-08 2013-04-08 OpenFlow-based FlowVisor network system CN103236945A (en)

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 CN103236945A (en) 2013-04-08 2013-04-08 OpenFlow-based FlowVisor network system

Country Status (1)

Country Link
CN (1) CN103236945A (en)

Cited By (17)

* Cited by examiner, † Cited by third party
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
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

Citations (1)

* Cited by examiner, † Cited by third party
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

Patent Citations (1)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
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 (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
CN104702512B (en) * 2013-12-06 2017-10-24 智梵网络科技有限公司 It provides network management for software-defined network hierarchical control systems and computer-implemented method
CN104702512A (en) * 2013-12-06 2015-06-10 智梵网络科技有限公司 Hierarchical control in software-defined network (sdn)
CN103905523A (en) * 2013-12-23 2014-07-02 浪潮(北京)电子信息产业有限公司 Cloud computing network virtualization method and system based on SDN
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
CN104811382B (en) * 2014-01-28 2018-05-29 华为技术有限公司 A packet processing method and apparatus
WO2015149505A1 (en) * 2014-04-04 2015-10-08 中兴通讯股份有限公司 Sdn application integration, management and control method, system and device
CN105450525A (en) * 2014-05-28 2016-03-30 国际商业机器公司 Method and equipment for using route switching equipment
CN105450525B (en) * 2014-05-28 2018-05-01 国际商业机器公司 A method and apparatus for use in routing and 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
CN104486290A (en) * 2014-11-18 2015-04-01 中国科学技术大学 Stream media cloud transparent service device based on open flow
CN104486290B (en) * 2014-11-18 2017-10-03 中国科学技术大学 OpenFlow-based streaming service cloud transparent means
CN104468633B (en) * 2014-12-31 2017-10-10 蓝盾信息安全技术股份有限公司 One kind sdn south to the Security Products
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
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

Similar Documents

Publication Publication Date Title
Stephens et al. PAST: Scalable Ethernet for data centers
AU2012340387B2 (en) Network control system for configuring middleboxes
Nunes et al. A survey of software-defined networking: Past, present, and future of programmable networks
Fernandes et al. Virtual networks: Isolation, performance, and trends
US9094308B2 (en) Finding latency through a physical network in a virtualized network
US9935851B2 (en) Technologies for determining sensor placement and topology
US9319337B2 (en) Universal physical control plane
CN104780096B (en) A method of controlling the virtual network system and the virtual network controller node
Jin et al. Covisor: A compositional hypervisor for software-defined networks
US20160094420A1 (en) Network embedded framework for distributed network analytics
Drutskoy et al. Scalable network virtualization in software-defined networks
KR101528213B1 (en) Software defined network-based data processing method, node, and system
US9413649B2 (en) Virtual network device architecture
EP3072263B1 (en) Multi-tenant isolation in a cloud environment using software defined networking
US9288162B2 (en) Adaptive infrastructure for distributed virtual switch
US9577845B2 (en) Multiple active L3 gateways for logical networks
US9294351B2 (en) Dynamic policy based interface configuration for virtualized environments
US9898317B2 (en) Physical path determination for virtual network packet flows
US9503371B2 (en) High availability L3 gateways for logical networks
EP2086178B1 (en) Link aggregation method and device, mac frame receiving/sending method and system
Blenk et al. Survey on network virtualization hypervisors for software defined networking
Hu et al. A survey on software-defined network and openflow: From concept to implementation
US9338097B2 (en) Method and system for load balancing at a data network
US8879396B2 (en) System and method for using dynamic allocation of virtual lanes to alleviate congestion in a fat-tree topology
US9996371B2 (en) Virtual switching method, related apparatus, and computer system

Legal Events

Date Code Title Description
C06 Publication
C10 Entry into substantive examination
RJ01 Rejection of invention patent application after publication