WO2016034217A1 - Contrôleur de réseautage défini par logiciel pour éléments de réseau hybride et procédé de commande de réseau défini par logiciel - Google Patents

Contrôleur de réseautage défini par logiciel pour éléments de réseau hybride et procédé de commande de réseau défini par logiciel Download PDF

Info

Publication number
WO2016034217A1
WO2016034217A1 PCT/EP2014/068710 EP2014068710W WO2016034217A1 WO 2016034217 A1 WO2016034217 A1 WO 2016034217A1 EP 2014068710 W EP2014068710 W EP 2014068710W WO 2016034217 A1 WO2016034217 A1 WO 2016034217A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
software defined
defined networking
resource
controller
Prior art date
Application number
PCT/EP2014/068710
Other languages
English (en)
Inventor
Israel ZIV
Original Assignee
Huawei Technologies Co.,Ltd.
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 Huawei Technologies Co.,Ltd. filed Critical Huawei Technologies Co.,Ltd.
Priority to CN201480037241.1A priority Critical patent/CN105580315A/zh
Priority to PCT/EP2014/068710 priority patent/WO2016034217A1/fr
Publication of WO2016034217A1 publication Critical patent/WO2016034217A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/022—Multivendor or multi-standard integration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • Software defined networking controller for hybrid network components and method for controlling a software defined network
  • the invention relates to a software defined networking controller for controlling network components, especially hybrid network components in a software defined network and an according method.
  • the object of the present invention is to provide a software defined networking controller and method for controlling a software defined network, which are able to control a wide variety of network components while incurring a low hardware and labor cost for implementation.
  • the object is solved by the features of claim 1 for the device and by the features of claim 14 for the method. Further it is solved by the features of claim 15 for the associated computer program.
  • the dependent claims contain further developments.
  • a first aspect of the present invention provides a software defined networking controller comprising a communication unit configured to communicate with network components and a control unit.
  • the network components comprise at least one hybrid network component comprising at least one software defined networking compliant network resource (SDN compliant network resource), and at least one non-software defined networking compliant network resource (non-SDN compliant network resource).
  • the control unit is configured to control the at least one software defined networking compliant network resource and the at least one non-software defined networking compliant resource. It is therefore possible to control individual network resources of a hybrid network component no matter, if they are SDN compliant or non- SDN compliant by a single software defined networking controller. Very low hardware and implementation manpower costs are therefore incurred.
  • the communication unit is configured to receive information regarding said network resources of said hybrid network component.
  • the software defining networking controller then further comprises a databank for storing said received information.
  • the control unit is then furthermore configured to control said network resources of said hybrid network component based upon said stored information.
  • a very flexible configuration of the software defined network is thereby possible.
  • said information indicates, whether a respective network resource of said hybrid network component is an SDN compliant network resource or a non-SDN compliant network resource.
  • the SDN controller can thereby easily judge how to control the individual network resource. This furthermore reduces the implementation effort.
  • said at least one SDN compliant network resource is a software defined networking queue or a software defined networking flow.
  • the at least one SDN compliant network resource is an SDN compliant network port.
  • the at least one non-SDN compliant network resource is a non-SDN compliant network port.
  • the control unit is configured to control the at least one SDN compliant network port and the at least one non-SDN compliant network port to route incoming packets at these network ports to further network ports of said hybrid network component. A very flexible use of the network resources is thereby possible.
  • the at least one SDN compliant network port is an openflow controlled port.
  • the openflow standard By using the openflow standard, a very easy implementation can be achieved.
  • the control unit is configured to control the SDN compliant network resources and non-SDN compliant network resources of the network components based on a data model including an abstract device entity for each network component controlled by the control unit.
  • the abstract device entities each contain a number of abstract resource entities which in turn comprise abstract network ports or abstract network queues or abstract network flows.
  • the resource entities each point to a specific implementation of a resource.
  • the specific implementations of resources comprise network ports, network queues and network flows.
  • the communication unit is configured to, upon connection with a given network component, receive information from the given network component, the information regarding the network resources available at the given network component.
  • the control unit is then configured to, based on the received information, create an abstract device entity for the given network component in the data model. Parts of the implementation can therefore be automated, further reducing the implementation effort.
  • the hybrid network components are hybrid network switches or hybrid network routers comprising at least one SDN compliant port and at least one non-SDN compliant port. Especially by use of hybrid network switches and hybrid network routers as hybrid network components, a large part of the overall hybrid network components are covered. For this large part of the available hybrid network components, the reduced implementation effort can be achieved.
  • a software defined networking system comprises a software defined networking controller as described above, a management controller, and at least two network components.
  • the management controller is configured to control the software defined networking controller by issuing route request to the software defined network controller. A high efficiency of implementation can thereby be reached.
  • said route requests each comprise two of said network components, a dataflow is to be initiated or terminated between.
  • the managing controller therefore does not have to comprise detailed knowledge about the setup of the software defined network. This further increases efficiency.
  • the software defined networking controller comprises at least an SDN compliant network port and a non- SDN compliant network port.
  • the software defined network controller is then configured to initiate or terminate connections between said network ports of said at least one hybrid network component and network ports of said network components to initiate or terminate the above-mentioned data flow specified by the route request.
  • a very efficient management of the software defined network is thereby achieved.
  • a method for controlling a software defined network using a software defined networking controller comprises the software defined networking controller and network components comprising at least one hybrid network component.
  • the at least one hybrid network component comprises at least one SDN compliant network resource and at least one non-SDN compliant network resource.
  • the software defined networking controller controls the at least one SDN compliant network resource and the at least one non-SDN compliant network resource.
  • a low implementation effort and high management efficiency can thereby be achieved.
  • information regarding said network resources of said hybrid network component are received and stored in a databank of the software defined networking controller. For controlling the network resources of said hybrid network component, the stored information is used. A very flexible control of the resources is thereby possible.
  • said at least one SDN compliant network resource is a software defined networking queue or software defined networking flow.
  • said at least one SDN compliant network resource is an SDN compliant network port and said at least one non-SDN compliant network resource is a non-SDN compliant network port.
  • a very wide variety of different network resources can thereby be controlled by the software defined networking controller.
  • the at least one SDN compliant network port and the at least non-SDN compliant network port are controlled to route incoming packets at these network ports to further network ports of said hybrid network component. A very flexible use of the network resources is thereby possible.
  • the at least one SDN compliant network port is an openflow-controlled port.
  • the SDN compliant network resources and non-SDN compliant network resources of the network components are controlled based on a data model including an abstract device entity for each network component.
  • the abstract device entities each contain a number of abstract resource entities.
  • the abstract resource entities each comprise abstract network ports or abstract network queues or abstract network flows.
  • the resource entities each point to a specific implementation of a resource.
  • the specific implementations of resources comprise network ports, network queues and network flows.
  • an eighth implementation form of the second aspect upon connection with a given network component, information from the given network component is received.
  • the information regards the network resources available at the given network component.
  • An abstract device entity for the given network component is created in the data model based upon the received information. Parts of the implementation can therefore be automated, further reducing the implementation effort.
  • the hybrid network components are hybrid network switches or hybrid network routers comprising at least one SDN-compliant port and at least one non-SDN compliant port.
  • a management controller controls the software defined networking controller by issuing route requests to the software defined networking controller. A high efficiency of implementation can thereby be reached.
  • said route requests each comprise two of said network components, a data flow is to be initiated or terminated between.
  • the managing controller therefore does not have to comprise detailed knowledge about the setup of the software defined network. This further increases efficiency.
  • the at least one SDN compliant network resource is an SDN compliant network port and the at least one non-SDN compliant network resource is a non-SDN compliant network port.
  • the software defined networking controller initiates or terminates connections between said network ports of said at least one hybrid network component and network ports of said network components to initiate or terminate the data flow specified by the route request. A very efficient management of the software defined network is thereby achieved.
  • a computer program with program codes for performing the earlier-described method when the computer program runs on a computer is provided.
  • an attribute of each device level indicates which technology is associated with a specific device.
  • the type of a resource e.g. openflow type port vs. legacy type port
  • the type of a resource is derived from the device type. Therefore, there are no degrees of freedom in the resource level.
  • the type of a specific resource is a property of the resource allowing the device containing several resources each of a different technology (e.g. one openflow and the other legacy).
  • the abstraction of devices within the SDN controller is done on the level of a sub-device, which corresponds to the resources of the device.
  • the SDN controller is capable of dealing not only with devices porting multiple technologies in a mutually exclusive manner but actually using multiple technologies in tandem.
  • SDN controllers provide a so-called "North-Bound Interface" for external applications to interact with the SDN controller, the present invention allows for more sophisticated applications - L2 and L3 types - to interact with the SDN controller.
  • Fig. 1 shows a block diagram of a first embodiment of the invention
  • Fig. 2 shows a block diagram of a more detailed second embodiment of the invention
  • Fig. 3 shows an exemplary topology of a software defined network comprising hybrid switches
  • Fig. 4 shows an exemplary routing table
  • Fig. 5 shows exemplary software defined networking system
  • Fig. 6 shows a more detailed view of an exemplary software defined networking system
  • Fig. 7 shows an implementation of a first embodiment of the inventive software defined networking system
  • Fig. 8 shows a representation of a data model used by a third embodiment of the inventive software defined networking controller
  • Fig. 9 shows a second view of the data model shown in Fig. 8;
  • Fig. 10 shows a third view of the data model shown in Fig. 8 and Fig. 9, and Fig. 11 shows a method for controlling a software defined network according to an embodiment of the present invention in a flow diagram.
  • a software defined networking controller 2 according to an embodiment of the present invention is shown.
  • the software defined networking controller 2 comprises a communication unit 3 (COM), which is connected with a control unit 4 (CTRL).
  • CTRL control unit 4
  • the software defined networking controller 2 is shown as part of a software defined networking system 1, which furthermore comprises network components, out of which one network component 5 - a hybrid network component (HNC) - is depicted here.
  • the hybrid network component 5 comprises a software defined networking compliant network resource 6 (SDN NR) and a non- software defined networking compliant network resource 7 (NON-SDN NR), which each are connected to the communication unit 3 of the software defined networking
  • SDN NR software defined networking compliant network resource 6
  • NON-SDN NR non- software defined networking compliant network resource 7
  • the communication unit 3 is connected to the control unit 4.
  • the communication unit 3 serves the purpose of communicating with the network components 5 of the software defined networking system 1.
  • the control unit is configured to control the at least one SDN compliant network resource 6 and the at least one non-SDN compliant network resource 7 of the hybrid network component 5.
  • the software defined networking controller 2 is shown as part of a software defined networking system 1.
  • the software defined networking controller 2 additionally (when compared to Fig. 1) comprises a database 8 (DB), which is connected to the control unit 4.
  • DB database 8
  • an additional network component 10 which is a non-SDN compliant network component (NC)
  • the network component 10 comprises only non-SDN compliant network resources, out of which a non-SDN compliant network resource 11 is depicted here.
  • the communication unit 3 is also connected to this non-SDN compliant network resource 11 of the additional network component 10.
  • the control unit 4 is furthermore configured to also control the non- SDN compliant network resource 11 by use of the communication unit 3.
  • a management controller 9 MAN CTRL
  • MAN CTRL management controller 9
  • the management controller 9 sends a route request to the software defined networking controller 2. In order to do so, the management controller 9 sends the route request to the communication unit 3 of the software defined networking controller 2, which forwards the route request to the control unit 4.
  • the route request comprises identifications (e.g. ports, IP-addresses, MAC addresses or similar) of at least two network components between which a connection shall be established. As an example, identifications of the network components 5, 10 can be comprised in the route request, between which a connection is to be formed.
  • the software defined network controller 2 then initiates or terminates connections between said network ports of said at least one hybrid network component and network ports of said network components in order to initiate or terminate the data flow specified by the route request.
  • the control unit 4 determines, to which network resources packets have to be routed to establish a data flow between the respective network components 5, 10. In this case, the control unit 4 determines that packets have to be routed to the software defined networking compliant network resource 6 and to the non-software defined networking compliant network resource 11 in order to establish a data flow between the network component 5 and the network components 10.
  • the network components 5, 10 are switches or routers.
  • the hybrid network component 5 is for example a hybrid network switch or a hybrid network router
  • the network component 10 is a non-SDN compliant network switch or network router.
  • the SDN-compliant network resources and non-SDN compliant network resources are SDN compliant network ports and non-SDN compliant network ports.
  • queues or flows or other resource types can be employed.
  • the communication unit When setting up the software defined networking system 1, the communication unit is configured to receive information regarding the network resources 6, 7, 11 of the hybrid network component 5 and advantageously any other network component 10 of the software defined networking system 1. This received information is stored in the databank 8. The network components are controlled based upon said stored information in the databank 8.
  • said information may indicate, whether a respective network resource of said hybrid network component is an SDN compliant network resource or a non-SDN compliant network resource.
  • SDN compliant network resource 6 being an SDN compliant network port, advantageously, it is an openflow-controlled port.
  • the software defined networking controller 2 When controlling the SDN compliant network resources and non-SDN compliant network resources, the software defined networking controller 2 performs this control based upon a data model including an abstract device entity for each network component 5, 10 controlled by the control unit 4.
  • the abstract device entities each contain a number of abstract resource entities, the abstract resource entities comprising abstract network ports or abstract network queues or abstract network flows.
  • the resource entity each point to a specific implementation of a resource, which comprise network ports, network queues and network flows.
  • Fig. 8 - Fig. 10 Regarding the data model, it is referred to the elaborations regarding Fig. 8 - Fig. 10.
  • the communication unit 3 furthermore receives information, when being connected to a specific network component regarding which network resources, the component comprises.
  • the control unit 4 is configured to create an abstract device entity for the given network component in the data model based upon the received information.
  • a software defined networking compliant network resource (such as the SDN compliant network resource 6) should be understood as a network resource, which is configurable using a software defined networking protocol, such as openflow.
  • a non-SDN compliant network resource should be understood as a network resource which is configurable only using a legacy protocol, such as an Ethernet protocol.
  • a non-SDN compliant network resource can also be designated as a legacy network resource.
  • a number of network components, especially network switches 30 - 36, which may be part of a software defined networking system 1 as shown in Fig. 1 and 2 is shown.
  • the switches 30, 31, 33, 34 and 36 comprise only software defined networking compliant network ports A 1 -A 4 , B 1 -B4, D 1 -D4, E 1 -E4, G 1 -G4 as network resources.
  • the switches 32 and 35 are hybrid network switches, since they comprise software defined networking compliant network ports Ci, C 2 , Fi, F 2 and non-SDN compliant network ports C 3 , C 4 , F 3 , F 4 , which are labeled as legacy ports here.
  • Connections between individual ports of the switches 30-36 are depicted by lines and respective arrows.
  • the arrows indicate the direction of traffic.
  • the connection of the respective ports of the switches is indicated in the routing table 40 of Fig. 4.
  • the highlighted section of the routing table 40 indicates connections of non-SDN compliant network ports i.e. legacy ports in this example. It can be seen that a connection between non-SDN compliant network ports and SDN compliant network ports is also supported.
  • Fig. 5 an example of a software defined networking system is shown.
  • the system shown here comprises a management controller 59, which is connected to a software defined networking controller 52, which again is connected to a number of network components 30-36 which correspond to the switches 30 - 36 of Fig. 3. Regarding the switches it is referred to the elaborations regarding Fig. 3.
  • the software defined networking controller 52 is for example implemented through the openflow protocol.
  • the controller 52 enables intelligent traffic flow within the network of switches.
  • the software defined networking controller 52 has access to the topology of the network of switches and is capable of configuring the traffic flow in the openflow components of the switches. Therefore, only traffic flow between openflow ports of the switches 30 - 36 can be controlled by the software defined networking controller 52.
  • the management controller 59 which runs a management application, provides a management interface of switches via the software defined networking controller 52. Moreover, it provides a direct control of legacy ports of the switches. This aspect though is not depicted in Fig. 5. A use case relating to the setup shown in Fig.
  • the 5 comprises a route request for a path configuration in which the management application run by the management controller 59 defines only the end points of the path of the route request.
  • the software defined networking controller 52 determines the path of individual packets between ports of the network components - the switches 30 - 36.
  • the software defined networking controller 52 then configures software defined networking compliant network ports - openflow ports of the switches 30 - 36. Since these ports may not suffice for performing the entire path according to the route request, the management application run by the management controller 59 has to configure the non-SDN compliant network ports - i.e. the non-openflow ports in this example. This is depicted in greater detail in Fig. 6.
  • the setup in Fig. 6 corresponds to the setup in Fig. 5.
  • the management application run by the management controller 59 requests from the software defined networking controller 52 to set the port A 3 as a termination point and to set the port E 2 as a termination port. Therefore, the route request comprises the ports A3 and E 2 .
  • the controller receives the respective route request and determines which possible paths could connect these two destination ports. Two alternative paths are discovered:
  • the software defined networking controller 52 decides for one of the possible paths. In this case, it decides for the shorter second path.
  • the exemplary software defined networking controller 52 as depicted here is capable of configuring the ports A 3 , B 2 , B 4 , F 2 and E 2 , but is not capable of configuring the port F 3 , since the switch 35, which comprises the port F 3 is a hybrid switch and the port F 3 is a non-SDN compliant network port - a legacy port. In order to set the path, the respective switches between A 3 and E 2 need to be configured.
  • the software defined networking controller 52 configures the ports A 3 , B 2 , B 4 , F 2 and E 2 .
  • the management application run by the management controller 59 configures the port F 3 via a legacy interface, for example SNMP.
  • a software defined networking system 71 according to an embodiment of the invention is shown.
  • the software defined networking system 71 comprises a management controller 79, a software defined networking controller 72 according to an embodiment of the present invention and a network of switches 30 - 36, which correspond to network components.
  • the switches 32, 35 are hybrid switches, while the remaining switches 30, 31, 33, 34 and 36 are software defined networking compliant network switches.
  • the implementation of the embodiment of the present invention represents a straight forward approach of managing and controlling a software defined network, which corresponds to a mixture of openflow supporting switches and hybrid switches.
  • the switches 30 - 36 used here can be the same switches as used in the example shown in Fig. 6.
  • the main difference lays in the software defined networking controller 72 and the management controller 79.
  • the management controller sends a route request to the software defined networking controller 72.
  • the route request indicates the ports A 3 and E 2 as termination points, defining ports which are to be connected by a data flow.
  • the software defined networking controller 72 receives the route request and finds two alternative paths:
  • the software defined networking controller 72 decides for one of the paths, in this case the shorter second path. After this, the software defined networking controller 72 configures the ports A 3 , B 2 , B 4 , F 2 , E 2 as well as F 3 . All switch-related management commands regardless of their protocol are propagated from the software defined networking controller 72. There is no direct connection and communications channel between the management controller 79 and the individual network components - the switches 30 - 36 needed anymore. The entire management logic is removed from the management controller 79. The management controller 79 therefore can be a very low processing power system such as a thin client. Moreover, a more accurate management of hybrid switches is thereby possible.
  • a data model 80 used for controlling the network resources is shown. Depicted here is an UML diagram depicting a data model supporting hybrid network components, such as the hybrid network component 5 of Fig. 1 and Fig. 2 and the hybrid network component 32, 35 of Fig. 3, and Fig. 5 - 7.
  • the general concept behind this data model is an abstract device entity for each network component, for example for each switch or router.
  • the abstract device entity 81 contains a number of abstract resource entities 83 - 86, which are concatenated by the block 82.
  • the different types of RESOURCE objects, which correspond to the abstract resource entities, have some common features as well as unique attributes which can differ depending upon the technology used.
  • the abstract resource entities 83 - 86 comprise abstract network ports 87 or abstract network queues 88 or abstract network flows 89.
  • an abstract resource element 86 containing non-defined abstract network resources 90 is shown for implementing future resources.
  • the specific technology context is provided by a series of additional objects, which correspond to the abstract network ports 87 or abstract network queues 88 or abstract network flows 89.
  • LAYER2_PORT represents a legacy type resource.
  • the Network Element NE which corresponds to the abstract device entity 81, remains abstract and may indirectly contain resources of various objects, such as OPENFLOW_PORT in tandem with L A YER2_PORT .
  • the abstract resource entities 83 - 86 each point to a specific implementation of a resource 87 - 90.
  • the specific implementations of resources 87 - 90 comprise network ports, network queues and network flows indicated by the individual logs in the area labeled concrete resources.
  • a method for controlling a software defined network comprising at least one hybrid network component, which comprises at least one SDN-compliant network resource and at least one non-SDN compliant network resource.
  • a management controller controls a software defined networking controller by sending a route request to the software defined networking controller.
  • the software defined networking controller controls the at least one SDN compliant network resource and the at least one non-SDN compliant network resource of the hybrid network component.
  • Embodiments of the present invention are not limited to the examples and especially not to the openflow and Open Daylight standards.
  • the concept discussed above can be applied to any software defined network system, comprising hybrid network components.
  • the characteristics of the exemplary embodiments can be used in any advantageous combination.
  • a suitable medium such as an optical storage medium or a solid- state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the internet or other wired or wireless telecommunication systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un contrôleur de réseautage défini par logiciel (2) comprenant une unité de communication (3) configurée pour communiquer avec des éléments de réseau (5), et une unité de commande (4). Les éléments de réseau (5) comprennent au moins un élément de réseau hybride (5) comprenant au moins une ressource (6) de réseau conforme à un réseautage défini par logiciel et au moins une ressource (7) de réseau conforme à un réseautage autre que défini par logiciel. L'unité de commande (4) est configurée pour commander ladite ressource (6) de réseau conforme à un réseautage défini par logiciel et ladite ressource (7) conforme à un réseautage autre que défini par logiciel.
PCT/EP2014/068710 2014-09-03 2014-09-03 Contrôleur de réseautage défini par logiciel pour éléments de réseau hybride et procédé de commande de réseau défini par logiciel WO2016034217A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201480037241.1A CN105580315A (zh) 2014-09-03 2014-09-03 用于混合网络组件的软件定义网络控制器和用于控制软件定义网络的方法
PCT/EP2014/068710 WO2016034217A1 (fr) 2014-09-03 2014-09-03 Contrôleur de réseautage défini par logiciel pour éléments de réseau hybride et procédé de commande de réseau défini par logiciel

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/068710 WO2016034217A1 (fr) 2014-09-03 2014-09-03 Contrôleur de réseautage défini par logiciel pour éléments de réseau hybride et procédé de commande de réseau défini par logiciel

Publications (1)

Publication Number Publication Date
WO2016034217A1 true WO2016034217A1 (fr) 2016-03-10

Family

ID=51492309

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2014/068710 WO2016034217A1 (fr) 2014-09-03 2014-09-03 Contrôleur de réseautage défini par logiciel pour éléments de réseau hybride et procédé de commande de réseau défini par logiciel

Country Status (2)

Country Link
CN (1) CN105580315A (fr)
WO (1) WO2016034217A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018065764A1 (fr) * 2016-10-03 2018-04-12 Global Invacom Ltd Appareil et procédé se rapportant à un système de distribution de données vidéo et/ou audio comportant une fonction d'orchestration activée par mise en réseau sdn

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106375112A (zh) * 2016-08-25 2017-02-01 浪潮(北京)电子信息产业有限公司 一种专用的软件定义网络系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130272135A1 (en) * 2012-04-11 2013-10-17 Gigamon Llc Traffic visibility in an open networking environment
US20130318243A1 (en) * 2012-05-23 2013-11-28 Brocade Communications Systems, Inc. Integrated heterogeneous software-defined network
US20140149542A1 (en) * 2012-11-29 2014-05-29 Futurewei Technologies, Inc. Transformation and Unified Control of Hybrid Networks Composed of OpenFlow Switches and Other Programmable Switches

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130272135A1 (en) * 2012-04-11 2013-10-17 Gigamon Llc Traffic visibility in an open networking environment
US20130318243A1 (en) * 2012-05-23 2013-11-28 Brocade Communications Systems, Inc. Integrated heterogeneous software-defined network
US20140149542A1 (en) * 2012-11-29 2014-05-29 Futurewei Technologies, Inc. Transformation and Unified Control of Hybrid Networks Composed of OpenFlow Switches and Other Programmable Switches

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Migration Use Cases and Methods Migration Working Group", 6 February 2014 (2014-02-06), XP055184486, Retrieved from the Internet <URL:https://www.opennetworking.org/images/stories/downloads/sdn-resources/use-cases/Migration-WG-Use-Cases.pdf> [retrieved on 20150421] *
"OpenFlow Switch Specification Version 1.3.4 (Protocol version (=x04)", 27 March 2014 (2014-03-27), XP055184110, Retrieved from the Internet <URL:https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-switch-v1.3.4.pdf> [retrieved on 20150420] *
"SDN: Software Defined Networks", 22 August 2013, O'REILLY MEDIA, INC., ISBN: 978-1-44-934230-2, article THOMAS D. NADEAU ET AL: "SDN: Software Defined Networks", pages: 1 - 384, XP055172068 *
"Use Cases and Migration Methods - Document properties", 20 April 2015 (2015-04-20), XP055184492, Retrieved from the Internet <URL:https://www.opennetworking.org/images/stories/downloads/sdn-resources/use-cases/Migration-WG-Use-Cases.pdf> [retrieved on 20150421] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018065764A1 (fr) * 2016-10-03 2018-04-12 Global Invacom Ltd Appareil et procédé se rapportant à un système de distribution de données vidéo et/ou audio comportant une fonction d'orchestration activée par mise en réseau sdn

Also Published As

Publication number Publication date
CN105580315A (zh) 2016-05-11

Similar Documents

Publication Publication Date Title
US11563602B2 (en) Method and apparatus for providing a point-to-point connection over a network
US9553770B2 (en) Method for controlling software defined network and apparatus for the same
US9722922B2 (en) Switch routing table utilizing software defined network (SDN) controller programmed route segregation and prioritization
CN107624240B (zh) 用于自动的基于策略的路由的网络元件的配置
US9866408B2 (en) Methods, systems, and computer readable media for configuring a flow interface on a network routing element
EP3637687B1 (fr) Procédé d&#39;orchestration de réseau défini par logiciel et contrôleur sdn
EP3917096A1 (fr) Isolation du réseau locataire d&#39;un centre de données à l&#39;aide des interconnexions de routeur logique pour la fuite de route de réseau virtuel
CN106789637B (zh) 一种跨域业务互通的路径建立方法、控制器及系统
US9432260B2 (en) Automated configuration for network devices
KR102045556B1 (ko) 통신 시스템에서 네트워크 서비스에 기초하여 네트워크 디바이스를 제어하기 위한 장치 및 방법
US10439961B2 (en) Network fabric control
US11425028B2 (en) Priority based automated network selection for micro-services in service mesh
Sonkoly et al. OpenFlow virtualization framework with advanced capabilities
EP3101854A1 (fr) Procédé et dispositif de traitement de tables de groupes basé sur openflow, et unité de configuration de tables de groupes
CN108512737B (zh) 一种数据中心ip层互联的方法和sdn控制器
WO2016034217A1 (fr) Contrôleur de réseautage défini par logiciel pour éléments de réseau hybride et procédé de commande de réseau défini par logiciel
Matias et al. The EHU-OEF: an OpenFlow-based layer-2 experimental facility
US9838218B2 (en) Method for providing overlay network interworking with underlay network and system performing same
CN108737277A (zh) 一种报文转发方法及装置
CN109644158B (zh) 区分报文进入消息的软件定义网络系统
CN115776441B (zh) 基于sdn的虚拟专线业务下发方法、装置、介质及电子设备
KR102023901B1 (ko) 소프트웨어 정의 네트워크에서 패킷의 경로를 설정하는 방법, 장치 및 컴퓨터 프로그램
EP3110092B1 (fr) Procédé pour déterminer un emplacement de stockage de tables, dispositif de transfert et dispositif de commande
US9467356B2 (en) Integrated data plane for heterogeneous network services
CN113965464A (zh) 虚拟化网络功能网元互通的方法及网络设备

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201480037241.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14759154

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14759154

Country of ref document: EP

Kind code of ref document: A1