CN103095565B - A kind of software defined network operating system and its implementation - Google Patents
A kind of software defined network operating system and its implementation Download PDFInfo
- Publication number
- CN103095565B CN103095565B CN201210397349.4A CN201210397349A CN103095565B CN 103095565 B CN103095565 B CN 103095565B CN 201210397349 A CN201210397349 A CN 201210397349A CN 103095565 B CN103095565 B CN 103095565B
- Authority
- CN
- China
- Prior art keywords
- forwarding
- driver module
- nos
- abstraction
- interface
- 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.)
- Active
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a kind of SDN operating system, comprising: NOS kernel, control interface, application; This system also comprises: forward level of abstraction, the driver module of more than one corresponding forwarding face equipment; Described forwarding level of abstraction, is arranged at NOS kernel and forwards between face device driver module, for managing driver module, by that operation requests converts unified standard to functional interface that is hardware independent for transmitting of application or NOS kernel; Call the driver module of corresponding forwarding face equipment; Described driver module, for the connection between NOS kernel with corresponding forwarding face equipment; According to calling of described forwarding level of abstraction, convert described standard operation to hardware pipeline and specifically transmit operation.The present invention also also discloses a kind of implementation method of SDN operating system, adopts system and method for the present invention, makes NOS when not knowing forwarding face hardware pipeline design details, also can realize the optimized control to the face of forwarding equipment.
Description
Technical field
The present invention relates to software defined network (SDN, SoftwareDefinedNetwork) field, particularly relate to a kind of SDN operating system (NOS, NetworkOperatingSystem) and its implementation.
Background technology
SDN is a kind of emerging control and forward separating and the direct programmable network architecture, SDN mainly contains four features: one is control and forward separating, namely supports that third party's chain of command equipment controls the exchange/routing function of common hardware by open protocol remote such as OpenFlow; Two is control plane centralization; Three is Forwarding plane generalizations; Four is meet customization demand by software programming mode.
SDN is as a kind of control and forward separating, the central controlled network architecture, the challenge that its of facing is very large be exactly SDN control plane NOS how by network route, policy mappings on the multiple forwarding face equipment of different manufacturers, realize real Network Programmable.Owing to there being the existence of multiple hardwares and repeating optimizing method, NOS is difficult to go to describe bottom hardware with unified model, also adopts standardized instrument effectively to programme to forwarding face with regard to being difficult to.In addition, part forward face equipment provide manufacturer also may not be willing to completely purpose NOS manufacturer discloses the hardware pipeline model of oneself, it is more unrealistic that this makes NOS directly carry out other programming of pipeline stages to hardware.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of SDN operating system and its implementation, makes NOS when not knowing forwarding face hardware pipeline design details, also can realize the optimized control to the face of forwarding equipment.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention provides a kind of software defined network SDN operating system, comprising: NOS kernel, control interface, application; Described system also comprises: the driver module forwarding level of abstraction, more than one corresponding forwarding face equipment; Wherein,
Described forwarding level of abstraction, is arranged between NOS kernel and the driver module forwarding face equipment, for managing driver module; By that operation requests converts unified standard to functional interface that is hardware independent for transmitting of application or NOS kernel; The interface that the driver module calling corresponding forwarding face equipment provides;
Described driver module, for the connection between NOS kernel with corresponding forwarding face equipment; According to calling of described forwarding level of abstraction, convert described standard operation to hardware pipeline and specifically transmit operation.
In such scheme, described forwarding face equipment is switch or is router; Described forwarding face equipment has unique device type identifier.
In such scheme, described forwarding level of abstraction, also for according to the forwarding face device type identifier collected, loads corresponding driver module, and concrete forwarding face example and driver module is set up corresponding relation.
In such scheme, described driver module, also for recording instance number and the device type identifier of described forwarding face equipment, initiating hardware performance data.
In such scheme, described control interface is forwarding face device management protocol interface, control protocol interface;
Described control protocol comprises OpenFlow agreement;
Described management agreement comprises order line, Simple Network Management Protocol, network configuration protocol.
In such scheme, the interface between described forwarding level of abstraction and driver module is NOS Standard Interface.
Present invention also offers a kind of SDN operating system implementation method, forwarding level of abstraction is set between NOS kernel and the driver module of the face of forwarding equipment; Described method also comprises:
Forward level of abstraction by that operation requests converts unified standard to interface that is hardware independent for transmitting of application or NOS kernel;
The interface that the driver module that forwarding level of abstraction calls corresponding forwarding face equipment provides;
Described driver module calls according to described forwarding level of abstraction, converts described standard operation to hardware pipeline and specifically transmits operation.
In such scheme, described forwarding face equipment is switch or is router; Described forwarding face equipment has unique device type identifier;
The interface that the driver module that described forwarding level of abstraction calls corresponding forwarding face equipment provides is: forward level of abstraction and find corresponding forwarding face to drive according to the device type identifier forwarding face equipment, and calls the interface that described driver module provides.
In such scheme, described method also comprises: described forwarding level of abstraction, according to the forwarding face device type identifier collected, loads corresponding driver module, and concrete forwarding face example and driver module are set up corresponding relation.
In such scheme, described method also comprises: when forwarding face device first and SDNNOS establish a connection, the device type identifier of active reporting self, SDNNOS finds corresponding driver module example according to described device type identifier, by the instance number and the device type identifier that forward face equipment described in described driver module record, and initiating hardware performance data.
In such scheme, described driver module is any driver corresponding with the face of forwarding equipment; When described driver is installed on NOS, register the binding relationship between self and one or more device type identifier.
In such scheme, the interface between described forwarding level of abstraction and driver module is NOS Standard Interface.
SDN operating system provided by the present invention and its implementation, level of abstraction and driver module is forwarded by introducing, make NOS can control the forwarding face device hardware of various producer easily, and the specific driver module of manufacturer can be relied on to generate optimized transmitting; For the new forwarding face device hardware may introduced in the future, only need install the new driver module for new forwarding face equipment on NOS, without the need to requiring that NOS provider upgrades whole NOS, this makes the new network hardware, the deployment cycle of function shortens greatly.In addition, the invention enables forwarding face hardware vendors just can dock with the NOS of other producer without the need to disclosing self detailed hardware interior details, improving the feasibility of SDN intercommunication.
Accompanying drawing explanation
Fig. 1 is the schematic diagram that NOS controls different forwarding faces hardware;
Fig. 2 is the composition structural representation of embodiment of the present invention NOS framework;
Fig. 3 is the realization flow schematic diagram that NOS of the present invention controls forwarding face device, method;
Fig. 4 is the realization flow schematic diagram that the present invention forwards that face device drives loads embodiment;
Fig. 5 is the realization flow schematic diagram that the present invention transmits management process embodiment.
Embodiment
Basic thought of the present invention is: independently forward level of abstraction (FAL for NOS introduces, ForwardingAbstractionLayer), when the forwarding face equipment of various SDN and NOS docking, corresponding driver module is installed, all driver modules are managed by the FAL of NOS, FAL is by that operation requests converts unified standard to functional interface that is hardware independent for transmitting of application or NOS kernel, then call the driver module of corresponding forwarding face equipment, convert standard operation to hardware pipeline by correspondence forwarding face device drives and specifically transmit operation.
Wherein, described forwarding face equipment is switch or is router.
In the present invention, the prerequisite realizing the present invention program comprises:
1) the forwarding face equipment of often kind of SDN system has unique device type identifier, such as, and the specification of equipment descriptor of a character string forms: name equipment brand specifications and models version number of manufacturer;
2) interface specification of NOS manufacturer, the interface specification namely between FAL and driver module are followed in the realization forwarding the driving of face manufacturer;
3) when forwarding face drives and installs on NOS, need to register the binding relationship between self and a certain or certain several device type identifier, so that when corresponding forwarding face equipment connection is to NOS, NOS can find corresponding driver entrance according to device type identifier.
Fig. 1 is the schematic diagram that NOS controls different forwarding faces hardware, and as shown in Figure 1, in FIG, a NOS controls two and forwards face equipment, and obviously, in Fig. 1, these two forwarding face equipment have different pipeline series, and also have different streamline redirect relations.Wherein, Packet_in represents the message of arrival equipment, the message forwarded after the process of Packet_out indication equipment; Tablek indicates k pipeline series, and Tablen indicates n pipeline series, and the arrow points between streamline link shows different redirect relations.
In practical application, forward face hardware differences than larger shown in Fig. 1, each manufacturer also may not be ready to announce to NOS the details that self forwards surface model completely simultaneously, and such NOS wants that regarding the face of forwarding equipment as white box goes the difficulty of control very large intuitively.So the present invention will solve when NOS does not know forwarding face hardware pipeline design details, how to realize the problem that the face of forwarding equipment optimization is controlled.
Usual one forwards face equipment, as conventional switch and router, all comprise at least one local cpu and a forwarding face Message processing device, CPU is for the treatment of each quasi-protocol and network management interface, under SDN framework, forwarding the control interface agreement in face is also by the local cpu process of the face of forwarding equipment.And forward face Message processing device and be usually all made up of many streamlines, every bar streamline is made up of multiple processing links again, and each processing links can think a concurrent hardware thread; First a message is assigned on certain Message processing streamline when arriving forwarding face entrance, and from first processing links of streamline, to the last a processing links is disposed, and is then sent by certain port of forwarding face Message processing device.
Here, the groundwork of each streamline link Message processing is: the value of taking out header is tabled look-up as keyword, processes after hitting certain table record according to the result in table to message.The present invention is follow-up to be expressed for simplifying, and usually represent a link in streamline with a table, and be isomorphism between many streamlines, identical streamline link all inquires about identical transmitting.
Fig. 2 is the composition structural representation of embodiment of the present invention NOS framework, as shown in Figure 2, this NOS system architecture is made up of the most basic NOS kernel, control interface, application, and key is, invention introduces the driver module forwarding level of abstraction and more than one corresponding forwarding face equipment; Wherein,
Described forwarding level of abstraction, is arranged between NOS kernel and the driver module forwarding face equipment, for managing driver module, by that operation requests converts unified standard to functional interface that is hardware independent for transmitting of application or NOS kernel; The interface that the driver module calling corresponding forwarding face equipment provides;
Concrete, the interface that the driver module that described forwarding level of abstraction calls corresponding forwarding face equipment provides is: described forwarding level of abstraction finds corresponding forwarding face to drive according to the face of forwarding device identifier, and calls the interface that described driver module provides;
Further, described forwarding level of abstraction, also for according to the forwarding face device type identifier collected, loads corresponding driver module, and concrete forwarding face example and driver module is set up corresponding relation, control so that follow-up to described forwarding face example.
Concrete, described that operation requests converts unified standard to functional interface that is hardware independent by transmitting, only need to define standard interface between forwarding level of abstraction and driver module.Such as: definition two-layer retransmitting table interface, Layer 3 router interface, ACL interface etc.; Described driver module knows details and the configuration of the hardware corresponding to oneself, can directly generate transmitting of optimization.
Give an example, usual computer can be installed/read multiple different memory device, such as: hard disk, USB flash disk, SD card etc.; From the angle of hardware operation, for distinct device, the instruction of practical operation and method are different, but, operating system shields this otherness, no matter is USB flash disk or hard disk, the subregion that what user saw in windows is all one by one, directly file operation can be carried out on these subregions, as: create, delete, copy etc.Wherein, the file system in operating system just act as the role of this conversion, that is: by abstract file manipulation command such as open, close, convert the operational order of distinct device to, and corresponding functional interface is supplied to upper layer application.
In the present invention, forward level of abstraction and provide abstract functional interface to upper layer application, such as above-mentioned two layers, three layer function interfaces, call corresponding driver module downwards and operate concrete forwarding face equipment, as switch/router.Such as: the switch had supports openflow agreement, then these functional interface operation transformation are become openflow order by driver module; Some switches only support snmp agreement, and so these operations are just expressed by snmp by driver module.
Wherein, described forwarding face equipment is switch or router;
Here, described forwarding level of abstraction shields the streamline detailed information of forwarding face equipment to NOS kernel or upper layer application, the driver module that can call only is provided to NOS kernel or upper layer application, make NOS can control the forwarding face device hardware of various producer easily, and the specific driving of each manufacturer can be relied on to generate optimized transmitting.
Concrete, each driver module knows details and the configuration of the hardware corresponding to oneself, can directly generate transmitting of optimization, and the video driver like certain manufacturer can adopt the video card of oneself producer of optimum way management the same.
Described driver module, for the connection between NOS kernel with corresponding forwarding face equipment; According to calling of described forwarding level of abstraction, convert standard operation to hardware pipeline and specifically transmit operation;
Described driver module, also for recording instance number and the device type identifier of described forwarding face equipment, initiating hardware performance data.
Two kinds of driver modules are given: driver module 1, driver module 2 shown in Fig. 2; Driver module 1, driver module 2 provide by forwarding face hardware vendor accordingly, that is: driver module 1 corresponding forwarding face equipment 1, driver module 2 corresponding forwarding face equipment 2.
Concrete, driver module can be any driver corresponding with the face of forwarding equipment; When the driver of forwarding face equipment is installed on NOS, need to register the binding relationship between self and a certain or certain several device type identifier, so that when corresponding forwarding face equipment connection is to NOS, NOS can find corresponding driver entrance according to device type identifier.
In addition, the NOS of SDN also comprises virtualization layer, api interface layer etc., but owing to not having direct relation with the present invention, is not described in detail in this.
Fig. 3 is the realization flow schematic diagram that NOS of the present invention controls forwarding face device, method, and as shown in Figure 3, the method comprises the following steps:
Step 301: forward level of abstraction by application or NOS kernel transmit operation requests convert to unified standard, with the interface of hardware independent;
Here, the forwarding face equipment of often kind of SDN system has unique device type identifier, and described specification of equipment descriptor can adopt character string forms, as: name equipment brand specifications and models version number of manufacturer;
And the driving forwarding face manufacturer realizes the interface specification following NOS manufacturer, the interface specification namely between FAL and driving.
Concrete, that operation requests converts unified standard to functional interface that is hardware independent by transmitting, described conversion demand is converted to the unified interface that FAL provides; Accordingly, only need to define standard interface between forwarding level of abstraction and driver module, such as: definition two-layer retransmitting table interface, Layer 3 router interface, ACL interface etc.
Step 302: the interface that the driver module that forwarding level of abstraction calls corresponding forwarding face equipment provides;
Concrete, described forwarding level of abstraction finds corresponding forwarding face to drive according to the face of forwarding device identifier, and calls the interface that described driver module provides;
Further, described forwarding level of abstraction, according to the forwarding face device type identifier collected, loads corresponding driver module, and concrete forwarding face example and driver module is set up corresponding relation, control so that follow-up to described forwarding face example.
Here, driver module can be any driver corresponding with the face of forwarding equipment; When the driver of forwarding face equipment is installed on NOS, need to register the binding relationship between self and a certain or certain several device type identifier, so that when corresponding forwarding face equipment connection is to NOS, NOS can find corresponding driver entrance according to device type identifier.
Further, when forwarding face device first and SDNNOS establishes a connection, the device type identifier of active reporting self, SDNNOS finds corresponding driver module example according to described device type identifier, by the instance number and the device type identifier that forward face equipment described in described driver module record, and initiating hardware performance data.
Step 303: described driver module calls according to described forwarding level of abstraction, converts described standard operation to hardware pipeline and specifically transmits operation.
Here, described conversion is a kind of decomposition in fact, that is: in driver module, operation is decomposed different streamlines and perform.
Give an example, the request forwarding level of abstraction is AddL3Route (IPSubnet, Mask, NextHopList), the hardware of driver management itself may have six level production lines, the wherein corresponding table 3 of IP route, and this IP route can not complete final forwarding decision, the outlet of L3 route also needs to replace target MAC (Media Access Control) address, and the MAC Address processing list of this equipment is table 6 to only have driver to know, therefore issues and go back Compass 6 after IP route table elemental motion is disposed and carry out MAC Address process.
In the above example, described standard operation refers to request Add_L3Route, described in convert to and specificly transmit operation and refer to: the IP routing operations first performing table 3, table 3 executes rear Compass 6 and carries out MAC Address process; Wherein, described IP route be NOS kernel according to topology calculate decision-making, be handed down to forwarding face level of abstraction by Add_L3Route standard interface afterwards.Because a level production line may comprise multiple tables, allow corresponding redirect relation between these tables, table 3 mentioned here, table 6 refer to two tables in streamline, and the progression shown shows the quantity shown in this streamline, such as, six level production lines illustrate that this streamline has six tables.
Here, driver module directly calls control interface and described forwarding face equipment carries out ardware feature negotiation as required; Described control interface is forwarding face device management protocol interface, control protocol interface; Described control protocol comprises OpenFlow agreement; Described management agreement comprises order line, Simple Network Management Protocol (SNMP), network configuration protocol (NetConf).
Fig. 4 is the realization flow schematic diagram that the present invention forwards that face device drives loads embodiment, and as shown in Figure 4, this flow process comprises the following steps:
Step 401 ~ 402: forward face equipment and send network join request to NOS kernel, this network join request arrives NOS kernel by control interface;
Here, described control interface can be any mainstream switches/router administration protocol interface, control protocol interface; Described control protocol can be the agreements such as OpenFlow, and management agreement can be order line, Simple Network Management Protocol, network configuration protocol etc.
After step 403:NOS kernel receives network join request, send bind request to forwarding level of abstraction;
Here, in described bind request containing the information such as device type identifier of forwarding face equipment sending network join request.
Step 404: forward level of abstraction and find corresponding driver entrance according to the device type identifier of bind request transfer fermentation equipment, and driver module corresponding for concrete driver is tied to corresponding forwarding face device instance, the binding entrance of calling driver module;
Here, described forwarding face device instance belongs to the different forwarding face equipment of same forwarding face device type.
Step 405: forward the binding entrance that level of abstraction calls the driver module found, send bind request to driver module;
Step 406: the driver module of described forwarding face equipment records this device type identifier and device instance number, initiating hardware performance data;
Step 407 ~ 410: driver module returns response, response, through forwarding level of abstraction, NOS kernel, sends external message eventually through control interface and returns to forwarding face equipment;
Step 411 ~ 414: driver module directly calls control interface as required and described forwarding face equipment carries out ardware feature negotiation.
Fig. 5 is the realization flow schematic diagram that the present invention transmits management process embodiment, and as shown in Figure 5, this flow process comprises the following steps:
Step 501: apply and send increase route requests to NOS kernel;
Step 502:NOS kernel searches local topology information according to routing table information after receiving this increase route requests, and determines to forward face equipment issues at which to transmit;
Step 503:NOS kernel sends route sending-down request to forwarding level of abstraction, and described route sending-down request comprises the instance number of routing iinformation itself and the face of forwarding equipment;
Step 504: forward level of abstraction and find corresponding driver module route sending-down connection inlet according to forwarding face device instance number;
Step 505: forward level of abstraction and call the connection inlet found, send route sending-down request to driver module;
Step 506: driver module according to the forwarding face ardware feature of self-management and the hardware parameter collected, by routing list decomposition on corresponding hardware pipeline;
Give an example, the request forwarding level of abstraction is Add_L3Route (IP_Subnet, Mask, NextHopList), the hardware of driver management itself may have six level production lines, the wherein corresponding table 3 of IP route, and this IP route can not complete final forwarding decision, the outlet of L3 route also needs to replace target MAC (Media Access Control) address, and the MAC Address processing list of this equipment is table 6 to only have driver to know, therefore issues and go back Compass 6 after IP route table elemental motion is disposed and carry out MAC Address process.
In the above example, described standard operation refers to request Add_L3Route, described in convert to and specificly transmit operation and refer to: the IP routing operations first performing table 3, table 3 executes rear Compass 6 and carries out MAC Address process; Wherein, described IP route be NOS kernel according to topology calculate decision-making, be handed down to forwarding face level of abstraction by Add_L3Route standard interface afterwards.Because a level production line may comprise multiple tables, allow corresponding redirect relation between these tables, table 3 mentioned here, table 6 refer to two tables in streamline, and the progression shown shows the quantity shown in this streamline, such as, six level production lines illustrate that this streamline has six tables.
Step 507 ~ 508: the ardware feature of driver module known to oneself generates transmitting of hardware specific, send amendment to control interface and transmit order, control interface receives after this amendment transmits order, order is transmitted in this amendment and sends to forwarding face equipment;
Step 509 ~ 513: forward face equipment and return successfully modified response;
Here, may there be different selections described step 509 ~ 513 in different realizations, and under partial picture, some step can be default, such as: in OpenFlow agreement, do not have the response of step 509, upper strata depends on error reporting to determine to transmit and revises unsuccessfully.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.
Claims (11)
1. a software defined network SDN operating system, comprising: NOS kernel, control interface, application; It is characterized in that, described system also comprises: the driver module forwarding level of abstraction, more than one corresponding forwarding face equipment; Wherein,
Described forwarding level of abstraction, is arranged between NOS kernel and the driver module forwarding face equipment, for managing driver module; By that operation requests converts unified standard to functional interface that is hardware independent for transmitting of application or NOS kernel; The interface that the driver module calling corresponding forwarding face equipment provides;
Described driver module, for the connection between NOS kernel with corresponding forwarding face equipment; According to calling of described forwarding level of abstraction, convert described standard operation to hardware pipeline and specifically transmit operation;
Described forwarding face equipment is switch or is router; Described forwarding face equipment has unique device type identifier.
2. system according to claim 1, is characterized in that, described forwarding level of abstraction, also for according to the forwarding face device type identifier collected, loads corresponding driver module, and concrete forwarding face example and driver module are set up corresponding relation.
3. system according to claim 1, is characterized in that, described driver module, also for recording instance number and the device type identifier of described forwarding face equipment, initiating hardware performance data.
4. the system according to claim 1,2 or 3, is characterized in that, described control interface is forwarding face device management protocol interface, control protocol interface;
Described control protocol comprises OpenFlow agreement;
Described management agreement comprises order line, Simple Network Management Protocol, network configuration protocol.
5. the system according to claim 1,2 or 3, is characterized in that, the interface between described forwarding level of abstraction and driver module is NOS Standard Interface.
6. a SDN operating system implementation method, is characterized in that, between NOS kernel and the driver module of the face of forwarding equipment, arrange forwarding level of abstraction; Described method also comprises:
Forward level of abstraction by that operation requests converts unified standard to interface that is hardware independent for transmitting of application or NOS kernel;
The interface that the driver module that forwarding level of abstraction calls corresponding forwarding face equipment provides;
Described driver module calls according to described forwarding level of abstraction, converts described standard operation to hardware pipeline and specifically transmits operation;
Described forwarding face equipment is switch or is router; Described forwarding face equipment has unique device type identifier.
7. method according to claim 6, it is characterized in that, the interface that the driver module that described forwarding level of abstraction calls corresponding forwarding face equipment provides is: forward level of abstraction and find corresponding forwarding face to drive according to the device type identifier forwarding face equipment, and calls the interface that described driver module provides.
8. method according to claim 7, it is characterized in that, described method also comprises: described forwarding level of abstraction, according to the forwarding face device type identifier collected, loads corresponding driver module, and concrete forwarding face example and driver module are set up corresponding relation.
9. method according to claim 7, it is characterized in that, described method also comprises: when forwarding face device first and SDNNOS establish a connection, the device type identifier of active reporting self, SDNNOS finds corresponding driver module example according to described device type identifier, by the instance number and the device type identifier that forward face equipment described in described driver module record, and initiating hardware performance data.
10. the method according to claim 7,8 or 9, is characterized in that, described driver module is any driver corresponding with the face of forwarding equipment; When described driver is installed on NOS, register the binding relationship between self and one or more device type identifier.
11. methods according to any one of claim 6 to 9, it is characterized in that, the interface between described forwarding level of abstraction and driver module is NOS Standard 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 CN103095565A (en) | 2013-05-08 |
| CN103095565B true 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) |
Families Citing this family (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8817625B1 (en) * | 2013-09-13 | 2014-08-26 | Telefonaktiebolaget L M Ericsson (Publ) | Service placement for inline services chaining with multiple instances |
| CN104468415A (en) * | 2013-09-16 | 2015-03-25 | 中兴通讯股份有限公司 | Method and device for reporting switch type |
| CN105339899B (en) * | 2013-11-27 | 2019-11-29 | 华为技术有限公司 | For making the method and controller of application program cluster in software defined network |
| CN103647658B (en) * | 2013-11-27 | 2016-12-07 | 华为技术有限公司 | The management method of the network equipment and controller in a kind of software defined network system |
| WO2015082016A1 (en) * | 2013-12-06 | 2015-06-11 | Huawei Technologies Co., Ltd. | Method and controller for chaining applications in a software defined network |
| CN103763121B (en) * | 2013-12-24 | 2018-01-09 | 新华三技术有限公司 | The method and device that a kind of network configuration information quickly issues |
| WO2015100542A1 (en) | 2013-12-30 | 2015-07-09 | 华为技术有限公司 | Software-defined networking event distribution method, control device, and processor |
| CN103701649B (en) * | 2013-12-31 | 2017-10-24 | 曙光云计算集团有限公司 | The collocation method of network |
| EP3094051B1 (en) | 2014-01-29 | 2018-08-15 | Huawei Technologies Co., Ltd. | Data transmission method, transmission control method and device |
| CN104978172A (en) * | 2014-04-04 | 2015-10-14 | 中兴通讯股份有限公司 | Integrated management and control method, system and equipment of SDN (Software Defined Networking) applications |
| WO2015188331A1 (en) * | 2014-06-11 | 2015-12-17 | 华为技术有限公司 | 转发控制方法、驱动器及sdn网络 forwarding control method, driver and sdn network |
| CN106664235B (en) * | 2014-08-19 | 2019-12-06 | 华为技术有限公司 | Method and device for fusing software defined network and traditional network |
| 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 operation system loading method based on SDN mode |
| CN111654923A (en) * | 2016-05-26 | 2020-09-11 | 华为技术有限公司 | Communication control method and related network element |
| 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 |
| CN109309711B (en) * | 2018-08-30 | 2020-06-16 | 中国科学院声学研究所 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103095565A (en) | 2013-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103095565B (en) | A kind of software defined network operating system and its implementation | |
| CN107147509B (en) | Virtual private network service implementation method, device and communication system | |
| CN104170334B (en) | A kind of method and apparatus for the configuration trustship element for being used to manage network-based control device | |
| CN103546451B (en) | System and method for managing the flow in overlay network | |
| Hu et al. | A survey on software-defined network and openflow: From concept to implementation | |
| Azodolmolky et al. | Cloud computing networking: Challenges and opportunities for innovations | |
| JP5792894B2 (en) | Port expansion topology information acquisition method, system, control bridge, and uplink port processing method and system | |
| KR101692890B1 (en) | Chassis controllers for converting universal flows | |
| TW202026896A (en) | Asynchronous object manager in a network routing environment | |
| CN102959910A (en) | Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel | |
| CN105681191A (en) | SDN (Software Defined Network) platform based on router virtualization and implementation method | |
| CN103763367A (en) | Method and system for designing distributed virtual network in cloud calculating data center | |
| US10050859B2 (en) | Apparatus for processing network packet using service function chaining and method for controlling the same | |
| CN107733795B (en) | Ethernet virtual private network EVPN and public network intercommunication method and device | |
| CN107005471A (en) | Universal Subscriber premises equipment | |
| CN111064649B (en) | Method and device for realizing binding of layered ports, control equipment and storage medium | |
| US20210329004A1 (en) | Network verification method and apparatus | |
| CN110430114B (en) | Virtual router and method for realizing interconnection between SDN network and traditional IP network | |
| CN105052113A (en) | Common agent framework for network devices | |
| CN105450525A (en) | Method and equipment for using route switching equipment | |
| CN104243299A (en) | Tunnel processing method and system, control surface equipment and forwarding surface equipment | |
| Huang et al. | Automatical end to end topology discovery and flow viewer on SDN | |
| KR20180104377A (en) | Method for inter-cloud virtual networking over packet optical transport network | |
| Yamanaka et al. | AutoVFlow: Autonomous virtualization for wide-area OpenFlow networks | |
| Olimjonovich | Software Defined Networking: Management of network resources and data flow |
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 |