CN103095565A - Software definition network operating system and implement method thereof - Google Patents
Software definition network operating system and implement method thereof Download PDFInfo
- Publication number
- CN103095565A CN103095565A CN2012103973494A CN201210397349A CN103095565A CN 103095565 A CN103095565 A CN 103095565A CN 2012103973494 A CN2012103973494 A CN 2012103973494A CN 201210397349 A CN201210397349 A CN 201210397349A CN 103095565 A CN103095565 A CN 103095565A
- Authority
- CN
- China
- Prior art keywords
- forwarding
- nos
- forwarding plane
- interface
- abstraction layer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000012512 characterization method Methods 0.000 claims 1
- 238000013461 design Methods 0.000 abstract description 3
- 238000012545 processing Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000005192 partition Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a self-defending network (SDN) operating system which comprises a network operating system (NOS) kernel, a control interface and application. The system further comprises a forwarding abstraction layer, and more than one drive modules of corresponding forwarding face equipment. The forwarding abstraction layer is arranged between the NOS kernel and the drive modules of the forwarding face equipment and used for managing the drive modules and converting forwarding list operating requests of the application or the NOS kernel into function interfaces which are of unified standards and not related to hardware. The drive modules of the corresponding forwarding face equipment are called. The drive modules are used for connecting the NOS kernel with the corresponding forwarding face equipment. According to call of the forwarding abstraction layer, standard operation is converted into specific forwarding list operation of a hardware production line. The invention further discloses an achieving method of the SDN operating system. According to the system and the method, under the circumstance that design details of the forwarding face hardware production line are unknown to the NOS, optimum control of the forwarding face equipment can be achieved.
Description
Technical Field
The present invention relates to the field of Software Defined Networking (SDN), and in particular, to a SDN Operating System (NOS) and a method for implementing the same.
Background
The SDN is an emerging network architecture with separated control and forwarding and direct programming, and has four main characteristics: the method comprises the steps that control and forwarding are separated, namely, the switching/routing function of universal hardware is remotely controlled by third-party control surface equipment through open protocols such as OpenFlow and the like; secondly, control plane centralization; thirdly, the forwarding plane is generalized; fourthly, the customized requirements can be met in a software programming mode.
As a network architecture with separate and centralized control of control and forwarding, SDN faces a great challenge in how SDN control plane NOS maps network routes and policies to multiple forwarding plane devices of different manufacturers, so as to implement true network programmability. Because of the existence of various hardware and forwarding optimization methods, NOS is difficult to describe the underlying hardware with a unified model, and it is also difficult to effectively program the forwarding plane with a standardized approach. In addition, partial forwarding plane device providers may not be completely willing to disclose their own hardware pipeline model to the NOS vendor, making it even more impractical for the NOS to directly program the hardware at pipeline level.
Disclosure of Invention
In view of the above, the main object of the present invention is to provide an SDN operating system and an implementation method thereof, which enable NOS to optimally control a forwarding plane device without knowing details of the hardware pipeline design of the forwarding plane.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a Software Defined Network (SDN) operating system, which comprises: NOS kernel, control interface, application; the system further comprises: the device comprises a forwarding abstraction layer and more than one driving module corresponding to forwarding surface equipment; wherein,
the forwarding abstraction layer is arranged between the NOS kernel and a driving module of the forwarding surface equipment and is used for managing the driving module; converting the forwarding table operation request of an application or an NOS kernel into a unified standard functional interface irrelevant to hardware; calling an interface provided by a driving module corresponding to the forwarding plane equipment;
the driving module is used for connecting the NOS kernel with the corresponding forwarding surface equipment; and converting the standard operation into a forwarding table operation specific to a hardware pipeline according to the call of the forwarding abstraction layer.
In the above scheme, the forwarding plane device is a switch or a router; the forwarding plane device has a unique device type identifier.
In the above scheme, the forwarding abstraction layer is further configured to load a corresponding driver module according to the collected forwarding plane device type identifier, and establish a corresponding relationship between a specific forwarding plane instance and the driver module.
In the above scheme, the driver module is further configured to record an instance number and a device type identifier of the forwarding plane device, and initialize hardware characteristic data.
In the above scheme, the control interface is a forwarding plane device management protocol interface and a control protocol interface;
the control protocol comprises an OpenFlow protocol;
the management protocol comprises a command line, a simple network management protocol and a network configuration protocol.
In the above scheme, the interface between the forwarding abstraction layer and the driver module is an NOS specification interface.
The invention also provides a SDN operating system implementation method, wherein a forwarding abstract layer is arranged between the NOS kernel and a driving module of forwarding plane equipment; the method further comprises the following steps:
the forwarding abstract layer converts the forwarding table operation request of the application or the NOS kernel into a uniform standard interface which is irrelevant to hardware;
the forwarding abstraction layer calls an interface provided by a driving module corresponding to the forwarding plane equipment;
and the driving module converts the standard operation into a forwarding table operation specific to a hardware pipeline according to the call of the forwarding abstraction layer.
In the above scheme, the forwarding plane device is a switch or a router; the forwarding plane device has a unique device type identifier;
the forwarding abstraction layer calls an interface provided by a driving module corresponding to the forwarding plane equipment, and the interface is as follows: and the forwarding abstraction layer finds the corresponding forwarding surface driver according to the device type identifier of the forwarding surface device and calls an interface provided by the driver module.
In the above scheme, the method further comprises: and the forwarding abstraction layer loads a corresponding driving module according to the collected forwarding plane equipment type identifier and establishes a corresponding relation between a concrete forwarding plane instance and the driving module.
In the above scheme, the method further comprises: when the forwarding plane equipment establishes a connection relation with the SDN NOS for the first time, the SDN NOS actively reports the equipment type identifiers of the forwarding plane equipment, searches the corresponding driving module examples according to the equipment type identifiers, records the example numbers and the equipment type identifiers of the forwarding plane equipment by the driving modules, and initializes hardware characteristic data.
In the above scheme, the driving module is any driving program corresponding to the forwarding plane device; when the driver is installed in the NOS, the binding relationship between the driver and one or more device type identifiers is registered.
In the above scheme, the interface between the forwarding abstraction layer and the driver module is an NOS specification interface.
The SDN operating system and the implementation method thereof provided by the invention have the advantages that by introducing the forwarding abstraction layer and the driver module, the NOS can easily control forwarding plane equipment hardware of various manufacturers and can generate an optimized forwarding table by depending on a specific driver module of the manufacturers; for new forwarding plane equipment hardware which may be introduced in the future, only a new drive module aiming at the new forwarding plane equipment needs to be installed on the NOS, and the NOS provider does not need to be required to upgrade the whole NOS, so that the deployment period of new network hardware and functions is greatly shortened. In addition, the invention enables the forwarding plane hardware manufacturer to be in butt joint with NOS of other manufacturers without disclosing the detailed internal details of the hardware, thereby improving the feasibility of SDN intercommunication.
Drawings
FIG. 1 is a diagram of NOS controlling different forwarding plane hardware;
FIG. 2 is a schematic diagram of a NOS framework according to an embodiment of the present invention;
fig. 3 is a schematic flow chart illustrating an implementation of a method for controlling a forwarding plane device by NOS according to the present invention;
fig. 4 is a schematic diagram illustrating an implementation flow of the forwarding plane device driver loading embodiment of the present invention;
fig. 5 is a schematic diagram of an implementation process of the forwarding table management process embodiment of the present invention.
Detailed Description
The basic idea of the invention is as follows: an independent Forwarding Abstraction Layer (FAL) is introduced for the NOS, when forwarding plane devices of various SDNs are in butt joint with the NOS, corresponding driving modules are installed, all the driving modules are managed by the FAL of the NOS, the FAL converts forwarding table operation requests of applications or NOS kernels into a unified standard functional interface irrelevant to hardware, then the driving modules of corresponding forwarding plane devices are called, and the standard operations are converted into hardware pipeline specific forwarding table operations by corresponding forwarding plane device drivers.
Wherein, the forwarding plane device is a switch or a router.
In the invention, the premise for realizing the scheme of the invention comprises the following steps:
1) forwarding plane devices of each SDN system have a unique device type identifier, such as a device specification descriptor in the form of a string: the brand, specification, model and version number of the factory name equipment;
2) the implementation of the driver of the forwarding plane manufacturer follows the interface specification of the NOS manufacturer, namely the interface specification between the FAL and the driver module;
3) when the forwarding plane driver is installed in the NOS, the binding relationship between the forwarding plane driver and one or more device type identifiers needs to be registered, so that when the corresponding forwarding plane device is connected to the NOS, the NOS can search the corresponding driver entry according to the device type identifier.
Fig. 1 is a schematic diagram of NOS controlling different forwarding plane hardware, and as shown in fig. 1, one NOS controls two forwarding plane devices, and obviously, the two forwarding plane devices in fig. 1 have different pipeline stages and also have different pipeline jump relationships. Wherein, Packet _ in represents a message arriving at the device, and Packet _ out represents a message forwarded after being processed by the device; table k indicates that there are k pipeline stages, Table n indicates that there are n pipeline stages, and the arrow directions between the pipeline stages indicate different jump relationships.
In practical application, the hardware difference of the forwarding plane is larger than that shown in fig. 1, and meanwhile, each manufacturer does not necessarily want to completely publish the details of the forwarding plane model of itself to NOS, so that it is difficult for NOS to visually control forwarding plane devices as white boxes. Therefore, the present invention is to solve the problem of how to realize the optimal control of the forwarding plane device without the NOS knowing the design details of the forwarding plane hardware pipeline.
Generally, a forwarding plane device, such as a common switch and a common router, includes at least one local CPU and a forwarding plane message processor, where the CPU is configured to process various protocols and network interface, and in an SDN framework, a control interface protocol of the forwarding plane is also processed by the local CPU of the forwarding plane device. The forwarding plane message processor generally comprises a plurality of pipelines, each pipeline comprises a plurality of processing links, and each processing link can be regarded as a concurrent hardware thread; when a message reaches the entrance of the forwarding plane, the message is firstly distributed to a certain message processing pipeline, from the first processing link of the pipeline to the last processing link, and then the message is sent out through a certain port of the message processor of the forwarding plane.
Here, the main work of each pipeline link message processing is: and taking the value of the head of the message as a keyword table look-up, and processing the message according to the result in the table after hitting a certain table record. The invention is followed by simplified expression, usually one table is used to represent one link in the pipeline, and a plurality of pipelines are isomorphic, and the same pipeline link queries the same forwarding table.
Fig. 2 is a schematic diagram of a configuration structure of an NOS architecture according to an embodiment of the present invention, and as shown in fig. 2, the NOS system architecture is composed of a most basic NOS kernel, a control interface, and an application, and it is critical that a forwarding abstraction layer and one or more driver modules corresponding to forwarding plane devices are introduced in the present invention; wherein,
the forwarding abstraction layer is arranged between the NOS kernel and a driving module of the forwarding plane equipment and is used for managing the driving module and converting the forwarding table operation request of the application or the NOS kernel into a unified standard functional interface irrelevant to hardware; calling an interface provided by a driving module corresponding to the forwarding plane equipment;
specifically, the interface provided by the forwarding abstraction layer calling the driver module corresponding to the forwarding plane device is: the forwarding abstraction layer finds a corresponding forwarding surface driver according to the forwarding surface equipment identifier and calls an interface provided by the driver module;
further, the forwarding abstraction layer is further configured to load a corresponding driver module according to the collected forwarding plane device type identifier, and establish a corresponding relationship between a specific forwarding plane instance and the driver module, so as to subsequently control the forwarding plane instance.
Specifically, the forwarding table operation request is converted into a uniform standard hardware-independent functional interface, and only a standard interface needs to be defined between the forwarding abstraction layer and the driver module. Such as: defining a two-layer forwarding table interface, a three-layer routing interface, an ACL interface and the like; the driving module knows the details and the configuration of the hardware corresponding to the driving module, and can directly generate an optimized forwarding table.
For example, a computer may be equipped with/read a variety of different storage devices, such as: hard disk, U disk, SD card, etc.; from the viewpoint of hardware operation, the actual operation instructions and methods are different for different devices, but the operating system shields the difference, and whether the operating system is a U disk or a hard disk, a user only sees one partition in windows, and file operations can be directly performed on the partitions, such as: create, delete, copy, etc. The file system in the operating system plays the role of the conversion, namely: and converting abstract file operation commands such as open and close into operation instructions of different devices, and providing corresponding functional interfaces to the upper-layer application.
In the present invention, the forwarding abstraction layer provides an abstract functional interface to the upper layer application, such as the aforementioned two-layer or three-layer functional interface, and calls the corresponding driver module to operate a specific forwarding plane device, such as a switch/router, downward. For example: if some switches support the openflow protocol, the driving module converts the functional interface operations into openflow commands; some switches only support the snmp protocol, and the driving module expresses the operations through the snmp.
The forwarding plane equipment is a switch or a router;
here, the forwarding abstraction layer shields the pipeline detail information of the forwarding plane device from the NOS kernel or upper layer application, and only provides the NOS kernel or upper layer application with a callable driver module, so that the NOS can easily control the forwarding plane device hardware of various manufacturers, and can generate an optimized forwarding table depending on each vendor specific driver.
Specifically, each driver module knows details and configuration of hardware corresponding to the driver module, and can directly generate an optimized forwarding table, as if the driver module can manage the display card of the manufacturer in an optimal manner as compared with the driver module of the display card of the manufacturer.
The driving module is used for connecting the NOS kernel with the corresponding forwarding surface equipment; according to the call of the forwarding abstraction layer, converting standard operation into specific forwarding table operation of a hardware pipeline;
the driving module is further configured to record an instance number and a device type identifier of the forwarding plane device, and initialize hardware characteristic data.
Fig. 2 shows two drive modules: a driving module 1 and a driving module 2; the driver modules 1 and 2 are provided by corresponding forwarding plane hardware manufacturers, namely: the driving module 1 corresponds to the forwarding plane device 1, and the driving module 2 corresponds to the forwarding plane device 2.
Specifically, the driving module may be any driving program corresponding to the forwarding plane device; when a driver of a forwarding plane device is installed in an NOS, it is necessary to register a binding relationship between itself and one or more device type identifiers, so that when the corresponding forwarding plane device is connected to the NOS, the NOS can search for a corresponding driver entry according to the device type identifier.
In addition, the NOS of SDN includes a virtualization layer, an API interface layer, and the like, but is not described in detail herein since it has no direct relation to the present invention.
Fig. 3 is a schematic flow chart of an implementation of the NOS controlling forwarding plane device method of the present invention, and as shown in fig. 3, the method includes the following steps:
step 301: the forwarding abstract layer converts the forwarding table operation request of the application or the NOS kernel into a uniform and standard interface irrelevant to hardware;
here, forwarding plane devices of each SDN system have unique device type identifiers, and the device specification descriptors may be in the form of strings, such as: the brand, specification, model and version number of the factory name equipment;
and the driver implementation of the forwarding plane manufacturer follows the interface specification of the NOS manufacturer, i.e., the interface specification between the FAL and the driver.
Specifically, the forwarding table operation request is converted into a unified standard functional interface irrelevant to hardware, and the conversion is to convert the requirement into a unified interface provided by the FAL; accordingly, only a standard interface needs to be defined between the forwarding abstraction layer and the driver module, such as: a two-layer forwarding table interface, a three-layer routing interface, an ACL interface, etc. are defined.
Step 302: the forwarding abstraction layer calls an interface provided by a driving module corresponding to the forwarding plane equipment;
specifically, the forwarding abstraction layer finds a corresponding forwarding plane driver according to a forwarding plane device identifier, and calls an interface provided by the driver module;
further, the forwarding abstraction layer loads a corresponding driver module according to the collected forwarding plane device type identifier, and establishes a corresponding relationship between a specific forwarding plane instance and the driver module, so as to control the forwarding plane instance in the following.
Here, the driver module may be any driver corresponding to the forwarding plane device; when a driver of a forwarding plane device is installed in an NOS, it is necessary to register a binding relationship between itself and one or more device type identifiers, so that when the corresponding forwarding plane device is connected to the NOS, the NOS can search for a corresponding driver entry according to the device type identifier.
Further, when the forwarding plane device establishes a connection relationship with the SDN NOS for the first time, the device type identifier of the forwarding plane device is actively reported, the SDN NOS finds a corresponding drive module instance according to the device type identifier, and the drive module records an instance number and the device type identifier of the forwarding plane device and initializes hardware characteristic data.
Step 303: and the driving module converts the standard operation into a forwarding table operation specific to a hardware pipeline according to the call of the forwarding abstraction layer.
Here, the transformation is actually a decomposition, i.e.: operations are broken down into different pipelined executions within the driver module.
For example, the request of the forwarding abstraction layer is Add L3Route (IP Subnet, Mask, NextHopList), the hardware managed by the driver itself may have six-stage pipelines, where the IP Route corresponds to table 3, and the IP Route cannot complete the final forwarding decision, the L3Route outlet also needs to replace the destination MAC address, and only the driver knows that the MAC address processing table of the device is table 6, so that the driver also points to table 6 to perform MAC address processing after the basic action processing of the issued IP Route table is completed.
In the above example, the standard operation is a request Add _ L3Route, and the operation of converting into a specific forwarding table is: the IP routing operation of the table 3 is executed firstly, and the table 3 is pointed to the table 6 to carry out MAC address processing after the execution; and the IP Route is decided by the NOS kernel according to topology calculation and then is issued to a forwarding plane abstract layer through an Add _ L3Route standard interface. Since a pipeline may contain multiple tables, and the tables allow corresponding jump relationships, the tables 3 and 6 as mentioned herein refer to two tables in the pipeline, and the number of the tables indicates the number of the tables in the pipeline, for example, a six-stage pipeline indicates that the pipeline has six tables in total.
Here, the driving module directly calls a control interface and the forwarding plane equipment to carry out hardware characteristic negotiation according to the requirement; the control interface is a forwarding plane equipment management protocol interface and a control protocol interface; the control protocol comprises an OpenFlow protocol; the management protocols include command line, Simple Network Management Protocol (SNMP), network configuration protocol (NetConf).
Fig. 4 is a schematic diagram of an implementation flow of the forwarding plane device driver loading embodiment of the present invention, and as shown in fig. 4, the flow includes the following steps:
step 401-402: the forwarding plane equipment sends a network joining request to the NOS kernel, and the network joining request reaches the NOS kernel through the control interface;
here, the control interface may be any mainstream switch/router management protocol interface, control protocol interface; the control protocol may be an OpenFlow protocol, and the like, and the management protocol may be a command line, a simple network management protocol, a network configuration protocol, and the like.
Step 403: after receiving the network joining request, the NOS inner core sends a binding request to a forwarding abstraction layer;
here, the binding request includes information such as a device type identifier of the forwarding plane device that issued the network join request.
Step 404: the forwarding abstraction layer finds a corresponding driver entry according to the device type identifier of the forwarding plane device in the binding request, binds a driver module corresponding to the specific driver to a corresponding forwarding plane device example, and calls the binding entry of the driver module;
here, the forwarding plane device instances belong to different forwarding plane devices of the same forwarding plane device type.
Step 405: the forwarding abstraction layer calls the found binding inlet of the drive module and sends a binding request to the drive module;
step 406: the driving module of the forwarding plane equipment records the equipment type identifier and the equipment instance number and initializes hardware characteristic data;
step 407-410: the driving module returns a response, the response passes through the forwarding abstraction layer and the NOS kernel, and finally, an external message is sent through the control interface and returned to the forwarding plane equipment;
step 411 to 414: and the driving module directly calls a control interface and the forwarding plane equipment to carry out hardware characteristic negotiation according to the requirement.
Fig. 5 is a schematic diagram of an implementation process of an embodiment of a forwarding table management process of the present invention, and as shown in fig. 5, the process includes the following steps:
step 501: the application sends a routing adding request to the NOS kernel;
step 502: after receiving the routing request, the NOS kernel searches local topology information according to the routing table information and determines which forwarding plane equipment to send and receive a forwarding table;
step 503: the NOS inner core sends a route issuing request to a forwarding abstraction layer, wherein the route issuing request comprises route information and an instance number of forwarding plane equipment;
step 504: the forwarding abstraction layer finds a corresponding driving module route issuing interface inlet according to the forwarding surface equipment instance number;
step 505: the forwarding abstraction layer calls the found interface entry and sends a route issuing request to the driving module;
step 506: the driving module decomposes the routing table to a corresponding hardware pipeline according to the hardware characteristics of the forwarding plane managed by the driving module and the collected hardware parameters;
for example, the request of the forwarding abstraction layer is Add _ L3Route (IP _ Subnet, Mask, NextHopList), the hardware managed by the driver itself may have six-stage pipelines, where the IP Route corresponds to table 3, and the IP Route cannot complete the final forwarding decision, the L3Route exit also needs to replace the destination MAC address, and only the driver knows that the MAC address processing table of the device is table 6, so that the driver also points to table 6 to perform MAC address processing after issuing the basic action processing of the IP Route table.
In the above example, the standard operation is a request Add _ L3Route, and the operation of converting into a specific forwarding table is: the IP routing operation of the table 3 is executed firstly, and the table 3 is pointed to the table 6 to carry out MAC address processing after the execution; and the IP Route is decided by the NOS kernel according to topology calculation and then is issued to a forwarding plane abstract layer through an Add _ L3Route standard interface. Since a pipeline may contain multiple tables, and the tables allow corresponding jump relationships, the tables 3 and 6 as mentioned herein refer to two tables in the pipeline, and the number of the tables indicates the number of the tables in the pipeline, for example, a six-stage pipeline indicates that the pipeline has six tables in total.
Step 507-508: the driving module generates a forwarding table specific to hardware according to the known hardware characteristic, sends a forwarding table modifying command to the control interface, and sends the forwarding table modifying command to forwarding plane equipment after the control interface receives the forwarding table modifying command;
step 509-513: the forwarding plane equipment returns a modification success response;
here, the steps 509 to 513 may have different options in different implementations, and some steps may be defaulted in some cases, such as: in the OpenFlow protocol, there is no response from step 509, and the upper layers rely on error reports to determine that the forwarding table modification failed.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (12)
1. A software defined network, SDN, operating system comprising: NOS kernel, control interface, application; characterized in that the system further comprises: the device comprises a forwarding abstraction layer and more than one driving module corresponding to forwarding surface equipment; wherein,
the forwarding abstraction layer is arranged between the NOS kernel and a driving module of the forwarding surface equipment and is used for managing the driving module; converting the forwarding table operation request of an application or an NOS kernel into a unified standard functional interface irrelevant to hardware; calling an interface provided by a driving module corresponding to the forwarding plane equipment;
the driving module is used for connecting the NOS kernel with the corresponding forwarding surface equipment; and converting the standard operation into a forwarding table operation specific to a hardware pipeline according to the call of the forwarding abstraction layer.
2. The system of claim 1, wherein the forwarding plane device is a switch or a router; the forwarding plane device has a unique device type identifier.
3. The system according to claim 2, wherein the forwarding abstraction layer is further configured to load a corresponding driver module according to the collected forwarding plane device type identifier, and establish a correspondence between a specific forwarding plane instance and the driver module.
4. The system of claim 2, wherein the driver module is further configured to record an instance number and a device type identifier of the forwarding plane device, and initialize the hardware characterization data.
5. The system of claim 1, 2, 3 or 4, wherein the control interface is a forwarding plane device management protocol interface, a control protocol interface;
the control protocol comprises an OpenFlow protocol;
the management protocol comprises a command line, a simple network management protocol and a network configuration protocol.
6. The system of claim 1, 2, 3 or 4, wherein the interface between the forwarding abstraction layer and the driver module is a NOS specification interface.
7. A SDN operating system implementation method is characterized in that a forwarding abstraction layer is arranged between an NOS kernel and a driver module of forwarding plane equipment; the method further comprises the following steps:
the forwarding abstract layer converts the forwarding table operation request of the application or the NOS kernel into a uniform standard interface which is irrelevant to hardware;
the forwarding abstraction layer calls an interface provided by a driving module corresponding to the forwarding plane equipment;
and the driving module converts the standard operation into a forwarding table operation specific to a hardware pipeline according to the call of the forwarding abstraction layer.
8. The method of claim 7, wherein the forwarding plane device is a switch or a router; the forwarding plane device has a unique device type identifier;
the forwarding abstraction layer calls an interface provided by a driving module corresponding to the forwarding plane equipment, and the interface is as follows: and the forwarding abstraction layer finds the corresponding forwarding surface driver according to the device type identifier of the forwarding surface device and calls an interface provided by the driver module.
9. The method of claim 8, further comprising: and the forwarding abstraction layer loads a corresponding driving module according to the collected forwarding plane equipment type identifier and establishes a corresponding relation between a concrete forwarding plane instance and the driving module.
10. The method of claim 8, further comprising: when the forwarding plane equipment establishes a connection relation with the SDN NOS for the first time, the SDNNOS actively reports the equipment type identifier of the forwarding plane equipment, searches the corresponding drive module instance according to the equipment type identifier, records the instance number and the equipment type identifier of the forwarding plane equipment by the drive module, and initializes hardware characteristic data.
11. The method of claim 8, 9 or 10, wherein the driver module is any driver corresponding to a forwarding plane device; when the driver is installed in the NOS, the binding relationship between the driver and one or more device type identifiers is registered.
12. The method according to any of claims 7 to 10, wherein the interface between the forwarding abstraction layer and the driver module is a NOS specification interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210397349.4A CN103095565B (en) | 2012-10-18 | 2012-10-18 | A kind of software defined network operating system and its implementation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210397349.4A CN103095565B (en) | 2012-10-18 | 2012-10-18 | A kind of software defined network operating system and its implementation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103095565A true CN103095565A (en) | 2013-05-08 |
| CN103095565B CN103095565B (en) | 2015-12-16 |
Family
ID=48207719
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210397349.4A Active CN103095565B (en) | 2012-10-18 | 2012-10-18 | A kind of software defined network operating system and its implementation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103095565B (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103647658A (en) * | 2013-11-27 | 2014-03-19 | 华为技术有限公司 | Management method of network equipment in software-defined network system and controller |
| CN103701649A (en) * | 2013-12-31 | 2014-04-02 | 曙光云计算技术有限公司 | Network configuration method |
| CN103763121A (en) * | 2013-12-24 | 2014-04-30 | 杭州华三通信技术有限公司 | Method and device for quickly issuing network configuration information |
| CN104468415A (en) * | 2013-09-16 | 2015-03-25 | 中兴通讯股份有限公司 | Method and device for reporting switch type |
| WO2015100542A1 (en) * | 2013-12-30 | 2015-07-09 | 华为技术有限公司 | Software-defined networking event distribution method, control device, and processor |
| WO2015113297A1 (en) * | 2014-01-29 | 2015-08-06 | 华为技术有限公司 | Data transmission method, transmission control method and device |
| CN104950839A (en) * | 2015-04-30 | 2015-09-30 | 张陵 | Switchboard control method and device |
| WO2015149505A1 (en) * | 2014-04-04 | 2015-10-08 | 中兴通讯股份有限公司 | Sdn application integration, management and control method, system and device |
| WO2015188331A1 (en) * | 2014-06-11 | 2015-12-17 | 华为技术有限公司 | 转发控制方法、驱动器及sdn网络 forwarding control method, driver and sdn network |
| CN105339899A (en) * | 2013-11-27 | 2016-02-17 | 华为技术有限公司 | Method and controller for clustering applications in a software-defined network |
| WO2016026089A1 (en) * | 2014-08-19 | 2016-02-25 | 华为技术有限公司 | Converging method and apparatus for software defined network and traditional network |
| CN105429785A (en) * | 2015-11-02 | 2016-03-23 | 浪潮集团有限公司 | Switch operating system loading method based on SDN mode |
| WO2016082750A1 (en) * | 2014-11-26 | 2016-06-02 | Huawei Technologies Co., Ltd. | Network abstractor for advanced interactive sdn optimization |
| CN105793823A (en) * | 2013-12-06 | 2016-07-20 | 华为技术有限公司 | Method and controller for linking applications in a software-defined network |
| CN106537839A (en) * | 2013-09-13 | 2017-03-22 | 瑞典爱立信有限公司 | Service placement for inline services chaining with multiple instances |
| CN109156040A (en) * | 2016-05-26 | 2019-01-04 | 华为技术有限公司 | A kind of communication control method and related network element |
| CN109144540A (en) * | 2018-07-27 | 2019-01-04 | 同济大学 | A kind of distributed software defined network update method |
| CN109257280A (en) * | 2017-07-14 | 2019-01-22 | 深圳市中兴微电子技术有限公司 | A kind of micro engine and its method for handling message |
| CN109309711A (en) * | 2018-08-30 | 2019-02-05 | 中国科学院声学研究所 | A virtual cache sharing method and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5889846A (en) * | 1997-02-10 | 1999-03-30 | At&T Corp | Method and system for initiating a software defined network call via a network adjunct platform |
| CN1933425A (en) * | 2006-10-10 | 2007-03-21 | 华为技术有限公司 | Module and method for realizing equipment access interface, equipment access system and method |
| CN101566923A (en) * | 2008-04-25 | 2009-10-28 | 中兴通讯股份有限公司 | Unified driving module of target end SCSI equipment and method thereof |
| US20100014431A1 (en) * | 2008-07-17 | 2010-01-21 | Paritosh Bajpay | Method and apparatus for providing automated processing of a network service alarm |
| CN101895669A (en) * | 2010-07-20 | 2010-11-24 | 深圳市茁壮网络股份有限公司 | General middleware adaptation layer system for digital television |
-
2012
- 2012-10-18 CN CN201210397349.4A patent/CN103095565B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5889846A (en) * | 1997-02-10 | 1999-03-30 | At&T Corp | Method and system for initiating a software defined network call via a network adjunct platform |
| CN1933425A (en) * | 2006-10-10 | 2007-03-21 | 华为技术有限公司 | Module and method for realizing equipment access interface, equipment access system and method |
| CN101566923A (en) * | 2008-04-25 | 2009-10-28 | 中兴通讯股份有限公司 | Unified driving module of target end SCSI equipment and method thereof |
| US20100014431A1 (en) * | 2008-07-17 | 2010-01-21 | Paritosh Bajpay | Method and apparatus for providing automated processing of a network service alarm |
| CN101895669A (en) * | 2010-07-20 | 2010-11-24 | 深圳市茁壮网络股份有限公司 | General middleware adaptation layer system for digital television |
Non-Patent Citations (1)
| Title |
|---|
| 吕高锋等: "LabelCast：一种普适的SDN转发平面抽象", 《计算机学报》 * |
Cited By (33)
| 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 |
| CN104468415A (en) * | 2013-09-16 | 2015-03-25 | 中兴通讯股份有限公司 | Method and device for reporting switch type |
| CN105339899A (en) * | 2013-11-27 | 2016-02-17 | 华为技术有限公司 | Method and controller for clustering applications in a software-defined network |
| US10498854B2 (en) | 2013-11-27 | 2019-12-03 | Huawei Technologies Co., Ltd. | Method and controller for clustering applications in a software-defined network |
| CN105339899B (en) * | 2013-11-27 | 2019-11-29 | 华为技术有限公司 | For making the method and controller of application program cluster in software defined network |
| CN103647658A (en) * | 2013-11-27 | 2014-03-19 | 华为技术有限公司 | Management method of network equipment in software-defined network system and controller |
| US10255120B2 (en) | 2013-12-06 | 2019-04-09 | Huawei Technologies Co., Ltd. | Method and controller for chaining applications in a software defined network |
| CN105793823B (en) * | 2013-12-06 | 2019-03-26 | 华为技术有限公司 | The method and controller of connectivity application in software defined network |
| CN105793823A (en) * | 2013-12-06 | 2016-07-20 | 华为技术有限公司 | Method and controller for linking applications in a software-defined network |
| CN103763121A (en) * | 2013-12-24 | 2014-04-30 | 杭州华三通信技术有限公司 | Method and device for quickly issuing network configuration information |
| WO2015100542A1 (en) * | 2013-12-30 | 2015-07-09 | 华为技术有限公司 | Software-defined networking event distribution method, control device, and processor |
| US9832255B2 (en) | 2013-12-30 | 2017-11-28 | Huawei Technologies Co., Ltd. | Event distribution method, control device, and processor on software-defined network |
| CN103701649B (en) * | 2013-12-31 | 2017-10-24 | 曙光云计算集团有限公司 | The collocation method of network |
| CN103701649A (en) * | 2013-12-31 | 2014-04-02 | 曙光云计算技术有限公司 | Network configuration method |
| WO2015113297A1 (en) * | 2014-01-29 | 2015-08-06 | 华为技术有限公司 | Data transmission method, transmission control method and device |
| US10548074B2 (en) | 2014-01-29 | 2020-01-28 | Huawei Technologies Co., Ltd. | Rule-based routing within a software-defined core network |
| CN104978172A (en) * | 2014-04-04 | 2015-10-14 | 中兴通讯股份有限公司 | Integrated management and control method, system and equipment of SDN (Software Defined Networking) applications |
| WO2015149505A1 (en) * | 2014-04-04 | 2015-10-08 | 中兴通讯股份有限公司 | Sdn application integration, management and control method, system and device |
| CN105379198A (en) * | 2014-06-11 | 2016-03-02 | 华为技术有限公司 | Forwarding control method, driver and SDN |
| WO2015188331A1 (en) * | 2014-06-11 | 2015-12-17 | 华为技术有限公司 | 转发控制方法、驱动器及sdn网络 forwarding control method, driver and sdn network |
| WO2016026089A1 (en) * | 2014-08-19 | 2016-02-25 | 华为技术有限公司 | Converging method and apparatus for software defined network and traditional network |
| WO2016082750A1 (en) * | 2014-11-26 | 2016-06-02 | Huawei Technologies Co., Ltd. | Network abstractor for advanced interactive sdn optimization |
| US10757630B2 (en) | 2014-11-26 | 2020-08-25 | Huawei Technologies Co., Ltd. | Network abstractor for advanced interactive SDN optimization |
| CN104950839A (en) * | 2015-04-30 | 2015-09-30 | 张陵 | Switchboard control method and device |
| CN105429785A (en) * | 2015-11-02 | 2016-03-23 | 浪潮集团有限公司 | Switch operating system loading method based on SDN mode |
| CN109156040A (en) * | 2016-05-26 | 2019-01-04 | 华为技术有限公司 | A kind of communication control method and related network element |
| CN109156040B (en) * | 2016-05-26 | 2020-04-28 | 华为技术有限公司 | A kind of communication control method and related network element |
| CN109257280A (en) * | 2017-07-14 | 2019-01-22 | 深圳市中兴微电子技术有限公司 | A kind of micro engine and its method for handling message |
| CN109257280B (en) * | 2017-07-14 | 2022-05-27 | 深圳市中兴微电子技术有限公司 | Micro-engine and message processing method thereof |
| CN109144540A (en) * | 2018-07-27 | 2019-01-04 | 同济大学 | A kind of distributed software defined network update method |
| CN109309711A (en) * | 2018-08-30 | 2019-02-05 | 中国科学院声学研究所 | A virtual cache sharing method and system |
| CN109309711B (en) * | 2018-08-30 | 2020-06-16 | 中国科学院声学研究所 | A virtual cache sharing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103095565B (en) | 2015-12-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103095565B (en) | A kind of software defined network operating system and its implementation | |
| KR101143648B1 (en) | Virtual network topology generation | |
| CN112187517B (en) | Configuration method, platform and controller for SDN virtual routing of data center | |
| US7941539B2 (en) | Method and system for creating a virtual router in a blade chassis to maintain connectivity | |
| US7945647B2 (en) | Method and system for creating a virtual network path | |
| US9674038B2 (en) | Method for automatically deploying a network device configuration | |
| US8782210B2 (en) | Network management control program, network management control device, and network management control method | |
| US8305934B2 (en) | Computer program, apparatus, and method for managing network | |
| US20110188373A1 (en) | Interface control system and interface control method | |
| US10050859B2 (en) | Apparatus for processing network packet using service function chaining and method for controlling the same | |
| JP2014519249A (en) | Port expansion topology information acquisition method, system, control bridge, and uplink port processing method and system | |
| US7020145B1 (en) | Network topology manager | |
| US20190199622A1 (en) | Data packet forwarding unit in a data transmission network | |
| EP3819728A1 (en) | Automatic device naming for fast device replacement | |
| CN109743259A (en) | A kind of network traffic scheduling method and device | |
| CN104852840A (en) | Method and device for controlling mutual access between virtual machines | |
| CN107003860A (en) | A kind of software defined network controller and its creation method | |
| US20180227170A1 (en) | Virtual local area network configuration system and method, and computer program product thereof | |
| CN108494607A (en) | The design method and system of big double layer network framework based on container | |
| CN106161603B (en) | A method, device and architecture for networking | |
| CN113285816B (en) | Control request sending method, device and system based on key value configuration | |
| WO2010125749A1 (en) | Network configuration device, information communication network, and network automatic construction method used for same | |
| CN114553707B (en) | Method and device for generating topology information of network and delimiting network faults | |
| WO2016173196A1 (en) | Method and apparatus for learning address mapping relationship | |
| JP6162831B2 (en) | Packet communication system, SDN control device, packet communication method, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |