CN104243319A - Neighbor discovering method and device thereof - Google Patents
Neighbor discovering method and device thereof Download PDFInfo
- Publication number
- CN104243319A CN104243319A CN201310227239.8A CN201310227239A CN104243319A CN 104243319 A CN104243319 A CN 104243319A CN 201310227239 A CN201310227239 A CN 201310227239A CN 104243319 A CN104243319 A CN 104243319A
- Authority
- CN
- China
- Prior art keywords
- port
- message
- neighbours
- openflow
- openflow switch
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Abstract
The invention provides a neighbor discovering method and a device thereof, which are applied in an OpenFlow network environment in which physical ports and logical ports coexist. The neighbor discovering method comprises the following steps: identifying physical ports on all OpenFlow switches, and transmitting a neighbor message to an opposite-end OpenFlow switch based on the physical ports; receiving the message by a message processing unit, wherein the message is reported by the physical port of the OpenFlow switch, thereby computing out a network topology structure. The neighbor discovering method and the device of the invention can effectively prevent effect of the logical port in the OpenFlow network environment for OpenFlow network topology computing.
Description
Technical field
The present invention relates to data communication field, particularly relate to a kind of method and device of neighbor uni-cast under OpenFlow network environment.
Background technology
Along with the development of Internet technology, client is shorter and shorter for the time requirement disposing business on the internet.Such as service deployment often needs the time of some months several years ago, but also needs to spend a large amount of manpowers; A present Internet service may require, when dropping into a small amount of manpower, to complete deployment in several days.How rapid deployment Internet service, this relates to some new technology, such as SDN(Software Defined Network, software defined network), under the network model of SDN definition, the rapid deployment that can realize business by the mode of software, thus the input, the reduction of erection time that reduce manpower.Wherein, in numerous SDN technology, OpenFlow is the wherein representational a kind of technology of most.
A typical OpenFlow ad-hoc network as shown in Figure 1, OpenFlow switch (OpenFlow Switch) is except existing except data channel each other, and independently management channels and OpenFlow controller (Openflow Controller) connect also to pass through one.After OpenFlow switch receives message, first inquire about stream table (FlowTable) of equipment of itself internal maintenance, if a hit list item, then forward according to the outgoing interface in list item; If not hit, then message can be reported OpenFlow controller, request OpenFlow controller issues a new list item and forwards to instruct it, OpenFlow controller is through certain calculating, can tell how OpenFlow switch processes message, abandons, current limliting or go out from which port repeat.
In above-mentioned processing procedure, OpenFlow controller needs to tell OpenFlow switch sends message from which port, the result that this port obtains after being actually and calculating based on whole network topology structure, instead of arbitrary port.Such as, in the network environment shown in Fig. 1, if OpenFlow Switch1 receives the message that is issued Server1, if the stream table (FlowTable) of OpenFlow Switch1 inside there is no corresponding forwarding rule, then need this message to send to OpenFlow controller.After OpenFlow controller receives message, if other safety certification of message is all passed through, then calculate based on whole network topology, under can knowing that Server1 is connected on OpenFlow Switch4, OpenFlow Switch1 can arrive OpenFlow Switch4 by port eth2, so OpenFlow controller forwards the packet give OpenFlow Switch1, require that this message sends from port eth2, and (this rule is used for telling OpenFlow Switch1 to issue corresponding message repeating rule, follow-up similar message directly sends from port eth2), after OpenFlow Switch1 receives this message repeating rule, upgrade the stream table FlowTable that therein is safeguarded.
As can be seen from message repeating process above, OpenFlow controller knows that network topology structure is most important for whole OpenFlow message repeating system.OpenFlow controller can know network topology by the mode of keeper's manual drawing, also can know network topology by process some neighbor protocol (such as LLDP, CDP etc.) message.If when whole OpenFlow network is very large, keeper's manual drawing network topology workload will be very huge, therefore find that network topology seems necessary by neighbor protocol.Find that in fact network topology is exactly the process finding neighbours OpenFlow switch, namely for any OpenFlow switch, which OpenFlow switch its neighbours have, and are connected each other by what port.
Summary of the invention
In view of this, the invention provides a kind of method and device of neighbor uni-cast, to solve the disappearance and deficiency that exist in prior art.
The present invention is achieved through the following technical solutions:
A kind of neighbor uni-cast device, is applied in the OpenFlow network environment that physical port and logic port coexist, includes port identification unit and message process unit, wherein:
Port identification unit, for identifying the physical port on all OpenFlow switches, and physically based deformation port sends neighbours' message to opposite end OpenFlow switch;
Message process unit, for receiving neighbours' message that OpenFlow switch physical port reports, and calculates network topology structure accordingly.
The present invention also provides a kind of method of neighbor uni-cast simultaneously, and be applied in the OpenFlow network environment that physical port and logic port coexist, wherein said method comprises the steps:
Step 1, the physical port identified on all OpenFlow switches, and physically based deformation port sends neighbours' message to opposite end OpenFlow switch;
Neighbours' message that step 2, reception OpenFlow switch physical port report, and calculate network topology structure accordingly.
Compared with prior art, under the OpenFlow network environment that the present invention coexists at physical port and logic port, logic port effectively can be avoided to calculate OpenFlow network topology impact, and then greatly improve the accuracy of neighbor uni-cast under OpenFlow network environment.
Accompanying drawing explanation
Fig. 1 is existing one typical OpenFlow ad-hoc network schematic diagram;
Fig. 2 sends neighbours' message based on all of the port in OpenFlow network environment and finds the schematic diagram of neighbours;
Fig. 3 is network environment middle port polymerization schematic diagram described in Fig. 2;
Fig. 4 is neighbor uni-cast apparatus structure schematic diagram of the present invention;
Fig. 5 is the process chart of neighbor discovering method of the present invention.
Embodiment
As stated in the Background Art, in SDN, OpenFlow controller finds network topology structure, generally by constructing based on OpenFlow switch all of the port and sending neighbours' message and then find neighbours OpenFlow switch.By this scientific discovery network topology structure, OpenFlow controller needs the process carrying out following two aspects usually: based on OpenFlow switch port configuration and indicate this port to send neighbours message to the port of opposite end OpenFlow switch; The neighbours' message requiring OpenFlow switch to report opposite end to send also calculates the neighborhood of OpenFlow inter-exchange according to this.
Concrete processing procedure is as follows:
Step a, travel through all OpenFlow switches, to every platform OpenFlow switch, indicate this port to send neighbours' message to the port that opposite end OpenFlow switch is corresponding based on its port configuration.
For current OpenFlow switch, OpenFlow controller obtains ports all on it, for each port, OpenFlow controller constructs neighbours' message, and indicates this OpenFlow switch ports themselves that this neighbours' message is sent to the port that opposite end OpenFlow switch is corresponding.The field that wherein neighbours' message comprises comprises: current OpenFlow switch identification (IP, MAC etc.), present port mark (Port IP, port mac, port id etc.).
The neighbours' message from opposite end that step b, reception OpenFlow switch ports themselves report.
In order to successfully receive the neighbours' message from opposite end that OpenFlow switch reports, OpenFlow controller also needs to create on all OpenFlow switch ports themselves to forward rule, requires to receive neighbours' message repeating of opposite end transmission to OpenFlow controller.Like this, OpenFlow controller can know the neighborhood between neighbours' message sender and recipient after receiving neighbours' message that opposite end that OpenFlow switch ports themselves reports sends (this neighbours' message also can incidentally from the neighbours' message which port receives).After OpenFlow controller receives all neighbours' messages, the neighborhood between all OpenFlow switches can be known, that is find the OpenFlow switch-layer topology structure in SDN.
Further as shown in Figure 2, when OpenFlow controller is based on the eth2 transmission neighbours message of OFS1, this neighbours' message is finally transmitted to OpenFlow controller by OFS2.OpenFlow controller is according to the message received, the receiving port eth1 of ID and OFS2 of the transmit port eth2 of ID, OFS1 of OFS1 can be extracted, thus can know that OFS1 and OFS2 is neighborhood, and the eth1 direct port connection of the eth2 port of OFS1 and OFS2.When OpenFlow controller is based on all of the port transmission neighbours message of all OpenFlow switches, and after receiving all neighbours' messages, just can calculate whole topology of networks.
But; according to OpenFlow agreement; in above-mentioned OpenFlow network environment; directly cannot distinguish which port is physical port; which port is logic port, and logic port carries on the physical port often, than aggregation port as shown in Figure 3; in the network environment shown in this figure, suppose to there are two direct connected link (OFS1:eth2-OFS2:eth1 between OFS1 and OFS2; And these two direct connected links are aggregated into a logical links (OFS1:Aggregation1-OFS2:Aggregation1) OFS1:eth3-OFS2:eth2).Like this, in this network environment, at least there are three ports in OFS1: eth2, eth3 and Aggregaton1, and equally, OFS2 also at least exists three ports: eth1, eth2 and Aggregaton1.If OpenFlow controller sends neighbours' message by the eth2 of OFS1 to OFS2, eth1 and Aggregation1 of OFS2 can receive neighbours' message, and all can report OpenFlow controller.And as previously mentioned, OpenFlow agreement directly cannot distinguish which port is physical port, which port is logic port, this will cause its neighbours' message received of OpenFlow controller None-identified which be effective, which is invalid, thus causes the calculating failure of whole network topology structure.
The present invention solves the problems referred to above by the method improving OpenFlow controller neighbor uni-cast in SDN.For software simulating, the invention provides a kind of method and device of neighbor uni-cast, wherein this neighbor uni-cast device operates on OpenFlow controller as logic device, and OpenFlow switch matches with it, has assisted the discovery of OpenFlow environment lower network topological structure.As the carrier that this logic device runs, the hardware environment of OpenFlow controller at least all comprises CPU, internal memory and nonvolatile memory usually to support the operation of above-mentioned logic device.Certainly, OpenFlow controller also may comprise the business hardware of other controller network topology discoveries of the present invention, because these are not the required assembly for realizing the object of the invention, is not repeated herein.
Please refer to Fig. 4, in the OpenFlow network environment that described neighbor uni-cast application of installation coexists at the physical port shown in Fig. 3 and logic port, include port identification unit and message process unit.Wherein, described neighbor uni-cast device in running with the interaction flow of OpenFlow inter-exchange as shown in Figure 5, comprise the following steps.
Physical port on step 1, all OpenFlow switches of port identification unit identification, and physically based deformation port sends neighbours' message to opposite end OpenFlow switch.
Concrete, the process of the physical port on port identification unit identification all OpenFlow switch is as follows:
Step 1-1, travel through all OpenFlow switches, obtain all ports on every platform OpenFlow switch.
Step 1-2, according to obtain OpenFlow switch on port, based on port configuration neighbours message (being specifically as follows LLDP message or CDP message), and it is sent to OpenFlow switch, require that neighbours' message is sent to the corresponding ports of opposite end OpenFlow switch by this OpenFlow switch, the field that wherein neighbours' message comprises comprises: current OpenFlow switch identification (IP, MAC etc.), present port mark (Port IP, port mac, port id etc.).
Neighbours' message that step 1-3, reception OpenFlow switch report also identifies whether the port receiving neighbours' message is physical port.
In order to identify that OpenFlow switch reports the port of neighbours' message whether to be physical port, in the present invention, also need to create on all OpenFlow switches in advance to forward rule, require that neighbours' message that the opposite end of its port accepts sends by OpenFlow switch reports port identification unit.
According to OpenFlow agreement regulation, for neighbours' message that OpenFlow switch reports, all need the port numbers (OFPXMT_OFB_IN_PORT) of subsidiary reception message and the physical port number (OFPXMT_OFB_IN_PHY_PORT) of correspondence thereof.If OFPXMT_OFB_IN_PORT equals OFPXMT_OFB_IN_PHY_PORT, then illustrate that this receiving port is physical port, then this physical port information of port identification unit record; If OFPXMT_OFB_IN_PORT is not equal to OFPXMT_OFB_IN_PHY_PORT, illustrate that receiving port is logic port, then port identification unit does not do any process.Like this, after port identification unit receives neighbours' message that OpenFlow switch reports, just can identify that whether port that this OpenFlow receives neighbours' message is the physical port on OpenFlow switch.
Further, port identification unit is as follows to the processing procedure of opposite end OpenFlow switch ports themselves by physical port transmission neighbours message:
According to the physical port on the OpenFlow switch identified, physically based deformation port constructs neighbours' message again, and described neighbours' message is sent these physical ports, then indicate these physical ports that neighbours' message is sent to the port that opposite end OpenFlow switch is corresponding, wherein the field that comprises of neighbours' message is identical with the field in neighbours' message in abovementioned steps 1.Comprise: current OpenFlow switch identification (IP, MAC etc.), present port mark (Port IP, port mac, port id etc.).
Step 2, message process unit receive neighbours' message that OpenFlow switch physical port reports, and calculate network topology structure accordingly.
After neighbours' message that the port of OpenFlow switch reports opposite end to send, message process unit receives only neighbours' message that physical port reports, and calculates topology based on received neighbours' message.Like this, after waiting all neighbours' messages to receive, the network topology of OpenFlow can correctly be calculated.For neighbours' message that non-physical port on OpenFlow switch reports, then directly make discard processing.
In order to make those skilled in the art clearly with clear, the OpenFlow networking application scene below still shown in composition graphs 3 describes implementation procedure of the present invention in detail.
According to the inventive method, first port identification unit needs to find the physical port on all OpenFlow.Particularly, port identification unit constructs neighbours' message respectively based on OFS1 port eth2, eth3 and Aggregation1, and indicates these ports that this neighbours' message is sent to the corresponding ports of OFS2.After neighbours' message that each port accepts of OFS2 sends to OFS1 port, these messages are reported port identification unit.For the message that eth1 port on OFS2 receives, report the OFPXMT_OFB_IN_PORT field of message to be the port numbers that eth1 is corresponding, OFPXMT_OFB_IN_PHY_PORT field is also the port numbers that eth1 is corresponding; For the message that eth2 on OFS2 receives, report the OFPXMT_OFB_IN_PORT field of message to be the port numbers that eth2 is corresponding, OFPXMT_OFB_IN_PHY_PORT field is also the port numbers that eth2 is corresponding; For the message that the Aggregation1 port on OFS2 receives, report the OFPXMT_OFB_IN_PORT field of message to be the port numbers that Aggregation1 is corresponding, OFPXMT_OFB_IN_PHY_PORT field is the port numbers that eth1 or eth2 is corresponding; Obviously, port identification unit can identify the physical port that eth1 and eth2 is OFS2, and Aggregation1 is not.In like manner, port identification unit sends neighbours' message respectively based on OFS2 port eth1, eth2 and Aggregation1; After receiving neighbours' message by OFS1 corresponding ports, can know that eth2 and eth3 is the physical port of OFS1.Like this, according to neighbor discovering method of the present invention, described port identification unit just can complete and obtain physical port { { OFS2, eth1}, { OFS2, eth2}, { OFS1, eth2}, { OFS1, eth3}} all on OFS1 and OFS2 switch.
Then, port identification unit is based on the physical port structure neighbours message on OpenFlow switch, and indicate these physical ports to send neighbours' message to the port of opposite end OpenFlow switch, particularly: described port identification unit is based on { OFS2, eth1} port configuration also indicates transmission neighbours message, neighbours' message carries device identification (IP, MAC etc.), the eth1 port-mark (Port IP, port mac, port id etc.) of OFS2, and by { OFS2, eth1} send; Based on OFS2, eth2} port configuration also indicates transmission neighbours message, and neighbours' message carries device identification (IP, MAC etc.), the eth2 port-mark (Port IP, port mac, port id etc.) of OFS2, and by { OFS2, eth2} send.In like manner, port identification unit is based on { OFS1, eth2} port configuration also indicates transmission neighbours message, and neighbours' message carries device identification (IP, MAC etc.), the eth2 port-mark (Port IP, port mac, port id etc.) of OFS1, and by { OFS1, eth2} send; Based on OFS1, eth3} port configuration also indicates transmission neighbours message, and neighbours' message carries device identification (IP, MAC etc.), the eth3 port-mark (Port IP, port mac, port id etc.) of OFS1, and by { OFS2, eth3} send.
Finally, described message process unit only processes the neighbours' message sent from opposite end that OpenFlow switch physical port reports, and calculates OpenFlow network topology according to the annexation that this neighbours' message is preserved.Particularly, described message process unit is by { OFS2, eth1} port accepts is to neighbours' message { OFS1, eth2}, due to { OFS2, eth1} is with { OFS1, eth2} are physical ports, therefore report this Packet by Packet processing unit so that described message process unit preserves the annexation (OFS1:eth2-OFS2:eth1) of OpenFlow inter-exchange according to this neighbours' message; In like manner, message process unit is by { OFS2, eth2} port accepts is to neighbours' message { OFS1; eth3}, due to { OFS2, eth2} and { OFS1; eth3} is physical port, therefore after message process unit process, preserves annexation (OFS1:eth2-OFS2:eth1; OFS1:eth3-OFS2:eth2); When message receiving element is by { { OFS1, eth2} are with { OFS1, eth3}, because { OFS2, Aggregation1} are not physical ports, therefore directly abandon related neighbor information to neighbours' message for OFS2, Aggregation1} port accepts; When message process unit is by { OFS1, eth2} receive neighbours' message { OFS2, eth1}, because { OFS2, eth1} are with { OFS1, eth2} are physical ports, need to preserve annexation, but exist due to (OFS1:eth2-OFS2:eth1), therefore no longer perform and preserve operation; Message process unit is by { OFS1, eth3} port accepts is to neighbours' message { OFS2, eth2}, because { OFS1, eth3} are with { OFS2, eth2} are physical ports, need to preserve annexation, but exist due to (OFS1:eth3-OFS2:eth2), therefore no longer perform and preserve operation; When the message process unit on neighbor uni-cast device is by { { OFS2, eth1} are with { OFS2, eth2}, because { OFS1, Aggregation1} are not physical ports, therefore abandon related neighbor information to neighbours' message for OFS1, Aggregation1} port accepts; Finally, according to the annexation (OFS1:eth2-OFS2:eth1 that OpenFlow controller is preserved; OFS1:eth3-OFS2:eth2), described neighbor uni-cast device can obtain correct OpenFlow network topology.
The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, within the spirit and principles in the present invention all, any amendment made, equivalent replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (10)
1. a neighbor uni-cast device, is applied in the OpenFlow network environment that physical port and logic port coexist, includes port identification unit and message process unit, it is characterized in that:
Port identification unit, for identifying the physical port on all OpenFlow switches, and physically based deformation port configuration send neighbours' message to opposite end OpenFlow switch;
Message process unit, for receiving neighbours' message that OpenFlow switch physical port reports, and calculates network topology structure accordingly.
2. device as claimed in claim 1, it is characterized in that, the process of the physical port on port identification unit identification OpenFlow switch is as follows:
Travel through all OpenFlow switches, obtain the port on every platform OpenFlow switch;
Based on the port configuration neighbours message on the OpenFlow switch obtained, and require that it is sent to opposite end OpenFlow switch by the port of this OpenFlow switch after receiving neighbours' message;
Neighbours' message that reception OpenFlow switch reports also identifies whether the port receiving neighbours' message is physical port.
3. device as claimed in claim 2, it is characterized in that, when the port numbers of the reception message carried in neighbours' message that OpenFlow switch reports is equal with physical port number, then this receiving port of port identification unit identification is physical port.
4. device as claimed in claim 3, it is characterized in that, message process unit is used for neighbours' message of computing network topological structure, after port identification unit identifies the physical port on all OpenFlow switches according to neighbours' message of structure, neighbours' message that physically based deformation port constructs again.
5. device as claimed in claim 4, is characterized in that, carries out discard processing after neighbours' message that message process unit reports at the non-physical port receiving OpenFlow switch.
6. a neighbor discovering method, be applied in the OpenFlow network environment that physical port and logic port coexist, it is characterized in that, described method comprises the steps:
Step 1, the physical port identified on all OpenFlow switches, and physically based deformation port configuration send neighbours' message to opposite end OpenFlow switch;
Neighbours' message that step 2, reception OpenFlow switch physical port report, and calculate network topology structure accordingly.
7. method as claimed in claim 6, is characterized in that, the port that described step 1 identifies on OpenFlow switch is that the process of physical port is as follows:
Travel through all OpenFlow switches, obtain the port on every platform OpenFlow switch;
Based on the port configuration neighbours message on the OpenFlow switch obtained, and require that it is sent to opposite end OpenFlow switch by the port of this OpenFlow switch after receiving neighbours' message;
Neighbours' message that reception OpenFlow switch reports also identifies whether the port receiving neighbours' message is physical port.
8. method as claimed in claim 7, is characterized in that, when the port numbers of the reception message carried in neighbours' message that OpenFlow switch reports is equal with physical port number, then identify that this receiving port is physical port.
9. method as claimed in claim 8, it is characterized in that, described step 2, for neighbours' message of computing network topological structure, is after described step 1 identifies the physical port on all OpenFlow switches according to neighbours' message of structure, neighbours' message that physically based deformation port constructs again.
10. method as claimed in claim 9, is characterized in that, carries out discard processing after neighbours' message that described step 2 reports at the non-physical port receiving OpenFlow switch.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310227239.8A CN104243319B (en) | 2013-06-06 | 2013-06-06 | The method and device that a kind of neighbours have found |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310227239.8A CN104243319B (en) | 2013-06-06 | 2013-06-06 | The method and device that a kind of neighbours have found |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104243319A true CN104243319A (en) | 2014-12-24 |
| CN104243319B CN104243319B (en) | 2018-01-09 |
Family
ID=52230701
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310227239.8A Active CN104243319B (en) | 2013-06-06 | 2013-06-06 | The method and device that a kind of neighbours have found |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104243319B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105429875A (en) * | 2015-10-29 | 2016-03-23 | 上海斐讯数据通信技术有限公司 | Link automatic discovery method and system based on software defined network |
| WO2016206555A1 (en) * | 2015-06-26 | 2016-12-29 | 中兴通讯股份有限公司 | Method, apparatus and switch for separating stack system protocol control and forwarding links |
| CN107113322A (en) * | 2015-01-14 | 2017-08-29 | 华为技术有限公司 | Create and manage the hardware and software method of transportable formula logic business chain |
| US20230099263A1 (en) * | 2020-09-30 | 2023-03-30 | Fortinet, Inc. | Secure link aggregation |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110188373A1 (en) * | 2010-02-01 | 2011-08-04 | Shuichi Saito | Interface control system and interface control method |
| WO2012096131A1 (en) * | 2011-01-13 | 2012-07-19 | 日本電気株式会社 | Network system and method of controlling path |
| CN102792645A (en) * | 2010-03-24 | 2012-11-21 | 日本电气株式会社 | Information system, control apparatus, method of controlling virtual network, and program |
| CN102938722A (en) * | 2012-10-30 | 2013-02-20 | 中兴通讯股份有限公司 | Method and device for sending network equipment protocol packages periodically |
| CN103001887A (en) * | 2012-11-22 | 2013-03-27 | 中兴通讯股份有限公司 | Link keeping alive method, controller and switchboard |
| JP2013074362A (en) * | 2011-09-27 | 2013-04-22 | Nec Corp | Virtual machine management device, method for managing virtual machine, and program |
| CN103067277A (en) * | 2013-01-06 | 2013-04-24 | 华为技术有限公司 | Method of building control channel, forwarding point (FP) and controller |
| CN103119901A (en) * | 2010-10-19 | 2013-05-22 | 日本电气株式会社 | Communication system, control apparatus, configuration method for processing rules, and program |
-
2013
- 2013-06-06 CN CN201310227239.8A patent/CN104243319B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110188373A1 (en) * | 2010-02-01 | 2011-08-04 | Shuichi Saito | Interface control system and interface control method |
| CN102792645A (en) * | 2010-03-24 | 2012-11-21 | 日本电气株式会社 | Information system, control apparatus, method of controlling virtual network, and program |
| CN103119901A (en) * | 2010-10-19 | 2013-05-22 | 日本电气株式会社 | Communication system, control apparatus, configuration method for processing rules, and program |
| WO2012096131A1 (en) * | 2011-01-13 | 2012-07-19 | 日本電気株式会社 | Network system and method of controlling path |
| JP2013074362A (en) * | 2011-09-27 | 2013-04-22 | Nec Corp | Virtual machine management device, method for managing virtual machine, and program |
| CN102938722A (en) * | 2012-10-30 | 2013-02-20 | 中兴通讯股份有限公司 | Method and device for sending network equipment protocol packages periodically |
| CN103001887A (en) * | 2012-11-22 | 2013-03-27 | 中兴通讯股份有限公司 | Link keeping alive method, controller and switchboard |
| CN103067277A (en) * | 2013-01-06 | 2013-04-24 | 华为技术有限公司 | Method of building control channel, forwarding point (FP) and controller |
Non-Patent Citations (2)
| Title |
|---|
| OPENFLOW: "Openflow switch specification v1.0.0 (1)", 《HTTP://WWW.OPENFLOWSWITCH.ORG/DOCUMENTS/OPENFLOW-SPEC-VL.0.0 .PDF》 * |
| PAUL CONGDON: "LLDP Overview", 《HTTP://WWW.IEEE802.ORG/1/FILES/PUBLIC/DOCS2002/LLDP%20OVERVIEW .PDF》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107113322A (en) * | 2015-01-14 | 2017-08-29 | 华为技术有限公司 | Create and manage the hardware and software method of transportable formula logic business chain |
| CN107113322B (en) * | 2015-01-14 | 2020-02-14 | 华为技术有限公司 | Hardware and software method for creating and managing migratable logical service chains |
| WO2016206555A1 (en) * | 2015-06-26 | 2016-12-29 | 中兴通讯股份有限公司 | Method, apparatus and switch for separating stack system protocol control and forwarding links |
| CN105429875A (en) * | 2015-10-29 | 2016-03-23 | 上海斐讯数据通信技术有限公司 | Link automatic discovery method and system based on software defined network |
| CN105429875B (en) * | 2015-10-29 | 2018-10-12 | 上海斐讯数据通信技术有限公司 | Chain-link automatic finding method based on software defined network and system |
| US20230099263A1 (en) * | 2020-09-30 | 2023-03-30 | Fortinet, Inc. | Secure link aggregation |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104243319B (en) | 2018-01-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103259728B (en) | A kind of OFS in-band communications method and OFS | |
| EP3082309B1 (en) | Sdn controller, data centre system and router connection method | |
| US9467363B2 (en) | Network system and method of managing topology | |
| CN104506408A (en) | Data transmission method and device based on SDN | |
| US10044830B2 (en) | Information system, control apparatus, method of providing virtual network, and program | |
| CN101247353B (en) | Stream aging method and network appliance | |
| EP2814213A1 (en) | Control device, communication system, communication method and program | |
| CN104394080A (en) | Method and device for achieving function of security group | |
| EP2553870B1 (en) | An operations, administrations and management proxy and a method for handling operations, administrations and management messages | |
| US11100020B2 (en) | Hybrid control plane data link agent and protocol | |
| CN107404441B (en) | Method and equipment for data stream splitting in slicing network | |
| CN104320345A (en) | Method and device for collecting topological information in SDN network | |
| CN110351388B (en) | Application method based on Internet of things architecture system | |
| CN104243319A (en) | Neighbor discovering method and device thereof | |
| CN105471742A (en) | Message processing method and message processing equipment | |
| KR101598775B1 (en) | Method, apparatus and computer program for controlling multi-path transmission of packet in software defined network | |
| CN104796340A (en) | Multicast data transmission method and device | |
| CN104320322A (en) | Message control method and equipment | |
| WO2016119269A1 (en) | Service data stream data packet processing method and device | |
| KR101610031B1 (en) | Method for controlling openflow switch embedded controller in software defined network and apparatus thereof | |
| CN104935581A (en) | Ethernet OAM and BFD dual-stack processing engine realization method and device | |
| CN104486226A (en) | Message processing method and device | |
| TWI575909B (en) | Network grouping system and the network grouping method thereof | |
| WO2016070617A1 (en) | Method and device for updating flow table | |
| US8015290B2 (en) | Group driver |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Applicant before: Huasan Communication Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |