CN104243319B - The method and device that a kind of neighbours have found - Google Patents
The method and device that a kind of neighbours have found Download PDFInfo
- Publication number
- CN104243319B CN104243319B CN201310227239.8A CN201310227239A CN104243319B CN 104243319 B CN104243319 B CN 104243319B CN 201310227239 A CN201310227239 A CN 201310227239A CN 104243319 B CN104243319 B CN 104243319B
- Authority
- CN
- China
- Prior art keywords
- port
- message
- neighbours
- openflow
- openflow interchangers
- 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 provides the method and apparatus that a kind of neighbours have found, apply in the OpenFlow network environments that physical port and logic port coexist.Comprise the following steps：Port identification unit identifies the physical port on all OpenFlow interchangers, and sends neighbours' message based on physical port and give opposite end OpenFlow interchangers；Message process unit receives the message that OpenFlow interchanger physical ports report, and calculates network topology structure accordingly.Impacted by the invention it is possible to which the logic port being effectively prevented from OpenFlow network environments is calculated OpenFlow network topologies.
Description
Technical field
The present invention relates to data communication field, more particularly to a kind of method that neighbours under OpenFlow network environments have found
And device.
Background technology
With the continuous development of Internet technology, client for disposing the time requirement of business more and more on the internet
It is short.For example a service deployment generally requires the time of some months several years ago, and also need to spend substantial amounts of manpower；Present one
Individual Internet service may be may require that in the case where putting into a small amount of manpower, and deployment is completed in several days.How rapid deployment one
Internet service, this is related to some new technologies, such as SDN（Software Defined Network, software defined network
Network）, under the network model that SDN is defined, the rapid deployment to business can be realized by way of software, so as to reduce manpower
Input, shorten the duration.Wherein, in numerous SDN technologies, OpenFlow is a kind of wherein most representational technology.
One typical OpenFlow ad-hoc network is as shown in figure 1, OpenFlow interchangers（OpenFlow Switch）Remove
Exist each other outside data channel, also pass through an independent management passage and OpenFlow controllers（Openflow
Controller）Establish connection.After OpenFlow interchangers receive message, one of equipment of itself internal maintenance is first inquired about
Flow table（FlowTable）If hitting a list item, forwarded according to the outgoing interface in list item；If do not hit,
Message can be reported to OpenFlow controllers, request OpenFlow controllers issue a new list item to instruct its forwarding,
OpenFlow controllers pass through certain calculating, can tell how OpenFlow interchangers handle message, are discarding, current limliting, go back
It is to be forwarded from which port.
In above-mentioned processing procedure, OpenFlow controllers need to tell OpenFlow interchangers send report from which port
Text, this port are actually based on the result obtained after whole network topological structure is calculated, rather than arbitrary port.Example
Such as, in the network environment shown in Fig. 1, if OpenFlow Switch1 receive a message for issuing Server1, if
Flow table inside OpenFlow Switch1（FlowTable）It is upper regular without corresponding forwarding, then need to send the message
Give OpenFlow controllers.After OpenFlow controllers receive message, if the other safety certifications of message are all by based on whole
Individual network topology is calculated, it is known that Server1 is connected under OpenFlow Switch4, OpenFlow Switch1 pass through
Port eth2 can reach OpenFlow Switch4, and then OpenFlow controllers, which forward the packet, gives OpenFlow
Switch1, it is desirable to which the message is sent from port eth2, and issues corresponding message forwarding rule（The rule is used to tell
OpenFlow Switch1, directly from port, eth2 is sent follow-up similar message）, OpenFlow Switch1 receive the report
After text forwarding rule, the flow table FlowTable of renewal therein maintenance.
Can be seen that OpenFlow controllers from message repeating process above knows network topology structure for whole
OpenFlow messages forwarding system is most important.OpenFlow controllers can know net by way of keeper's manual drawing
Network topology, can also be by handling some neighbor protocols（Such as LLDP, CDP etc.）Message knows network topology.It is if whole
In the case that OpenFlow networks are very big, keeper's manual drawing network topology workload will be very huge, therefore pass through neighbours
Protocol discovery network topology seems necessary.It was found that network topology is actually to find the mistake of neighbours' OpenFlow interchangers
Journey, i.e., for any one OpenFlow interchanger, which OpenFlow interchanger its neighbour has, and is by assorted between each other
Port connection.
The content of the invention
In view of this, the present invention provides the method and device that a kind of neighbours have found, to solve to lack present in prior art
Become estranged deficiency.
The present invention is achieved through the following technical solutions：
A kind of neighbours have found device, apply in the OpenFlow network environments that physical port and logic port coexist, and wrap
Port identification unit and message process unit have been included, wherein：
Port identification unit, for identifying the physical port on all OpenFlow interchangers, and it is based on physical port
Send neighbours' message and give opposite end OpenFlow interchangers；
Message process unit, the neighbours' message reported for receiving OpenFlow interchanger physical ports, and calculate accordingly
Go out network topology structure.
The present invention also provides a kind of neighbours method found simultaneously, applies what is coexisted in physical port and logic port
In OpenFlow network environments, wherein methods described comprises the following steps：
Step 1, physical port on all OpenFlow interchangers is identified, and neighbours' message is sent based on physical port
Give opposite end OpenFlow interchangers；
Step 2, neighbours' message that OpenFlow interchanger physical ports report is received, and calculate network topology knot accordingly
Structure.
It is compared with prior art, of the invention under the OpenFlow network environments that physical port and logic port coexist,
Logic port can be effectively prevented to impact the calculating of OpenFlow network topologies, and then be greatly enhanced OpenFlow nets
The accuracy that neighbours have found under network environment.
Brief description of the drawings
Fig. 1 is a kind of existing typical OpenFlow ad-hoc network schematic diagrames；
Fig. 2 is to send neighbours' message based on all of the port in OpenFlow network environments and find the schematic diagram of neighbours；
Fig. 3 is that network environment middle port described in Fig. 2 polymerize schematic diagram；
Fig. 4 is that neighbours of the present invention have found apparatus structure schematic diagram；
Fig. 5 is the process chart of neighbor discovering method of the present invention.
Embodiment
As stated in the Background Art, in SDN, OpenFlow controllers find network topology structure, generally by
Constructed based on OpenFlow interchanger all of the ports and send neighbours' message and then find neighbours' OpenFlow interchangers.Pass through
The scientific discovery network topology structure, OpenFlow controllers usually require to carry out following both sides processing：It is based on
The port configuration of OpenFlow interchangers simultaneously indicates that the port sends neighbours' message to the port of opposite end OpenFlow interchangers；Will
Ask OpenFlow interchangers to report neighbours' message of opposite end transmission and calculate the neighborhood of OpenFlow inter-exchanges according to this.
Specific processing procedure is as follows：
Step a, all OpenFlow interchangers are traveled through, to every OpenFlow interchanger, based on its port configuration simultaneously
Indicate that the port sends neighbours' message to port corresponding to the OpenFlow interchangers of opposite end.
For current OpenFlow interchangers, OpenFlow controllers obtain all port thereon, for each port,
OpenFlow controllers construct neighbours' message, and indicate that neighbours' message is sent to pair by the OpenFlow switch ports themselves
Hold port corresponding to OpenFlow interchangers.The field that wherein neighbours' message includes includes：Current OpenFlow switch identifications
（IP, MAC etc.）, present port mark（Port IP, port mac, port id etc.）.
Step b, neighbours' message from opposite end that OpenFlow switch ports themselves report is received.
In order to successfully receive neighbours' message from opposite end that OpenFlow interchangers report, OpenFlow controllers are also
Need to create forwarding rule on all OpenFlow switch ports themselves, it is desirable to forward the neighbours' message for receiving opposite end transmission
Give OpenFlow controllers.So, OpenFlow controllers receive what the opposite end that OpenFlow switch ports themselves report was sent
Neighbours' message（Neighbours' message can also attach the neighbours' message received from which port）Afterwards, you can know neighbours message sender
Neighborhood between recipient.After OpenFlow controllers receive all neighbours' messages, you can know all
Neighborhood between OpenFlow interchangers, that is, find the OpenFlow switch-layer topology structures in SDN.
Further as shown in Fig. 2 when eth2 of the OpenFlow controllers based on OFS1 sends neighbours' message, neighbours' message
OpenFlow controllers are finally transmitted to by OFS2.OpenFlow controllers can extract OFS1's according to the message of reception
ID, OFS1 sending port eth2 ID and OFS2 receiving port eth1, so as to know that OFS1 and OFS2 is neighbours
Relation, and OFS1 eth2 ports and OFS2 eth1 direct port connections.When OpenFlow controllers are handed over based on all OpenFlow
The all of the port changed planes sends neighbours' message, and after having received all neighbours' messages, it is possible to calculate the topology of whole network
Structure.
However, according to OpenFlow agreements, in above-mentioned OpenFlow network environments, it can not directly distinguish which port is
Physical port, which port are logic ports, and logic port is often to carry on the physical port, than as shown in Figure 3
Aggregation port, in the network environment shown in the figure, it is assumed that two direct connected links between OFS1 and OFS2 be present（OFS1:eth2-
OFS2:eth1;OFS1:eth3-OFS2:eth2）, and this two direct connected links are aggregated into a logical links（OFS1:
Aggregation1-OFS2:Aggregation1）.So, in this network environment, at least there are three ports in OFS1：
Also three ports at least be present in eth2, eth3 and Aggregaton1, equally, OFS2：Eth1, eth2 and Aggregaton1.Such as
Fruit OpenFlow controllers send neighbours' message by OFS1 eth2 to OFS2, and OFS2 eth1 and Aggregation1 can
Neighbours' message is received, and can all report OpenFlow controllers.And as it was previously stated, which OpenFlow agreements can not directly distinguish
A little ports are that physical port, which port are logic ports, and this may result in OpenFlow controllers None- identified, and it is received
Neighbours' message which be it is effective, which be invalid, so as to cause the calculating of whole network topological structure to fail.
The present invention is solved the above problems by improving the method for OpenFlow controllers neighbours discovery in SDN.With
Exemplified by software is realized, the present invention provides the method and device that a kind of neighbours have found, the wherein neighbours have found that device fills as logic
Put and operate on OpenFlow controllers, OpenFlow interchangers are cooperating therewith, assist to complete OpenFlow environment lower networks
The discovery of topological structure.As the carrier of logic device operation, the hardware environment of OpenFlow controllers is typically at least all wrapped
CPU, internal memory and nonvolatile memory are included to support the operation of above-mentioned logic device.Certainly, OpenFlow controllers may
Also include the business hardware of other controller network topology discoveries of the present invention, because these are not to realize the object of the invention
Required component, will not be described here.
Fig. 4 is refer to, the neighbours have found that device applies what is coexisted in the physical port shown in Fig. 3 and logic port
In OpenFlow network environments, include port identification unit and message process unit.Wherein, the neighbours have found that device exists
Interaction flow in running with OpenFlow inter-exchanges is as shown in figure 5, comprise the following steps.
Step 1, port identification unit identify the physical port on all OpenFlow interchangers, and are sent out based on physical port
Neighbours' message is sent to give opposite end OpenFlow interchangers.
Specifically, port identification unit identifies that the process of the physical port on all OpenFlow interchangers is as follows：
Step 1-1, all OpenFlow interchangers are traveled through, obtain all ends on every OpenFlow interchanger
Mouthful.
Step 1-2, according to the port on the OpenFlow interchangers of acquisition, based on port configuration neighbours' message（Specifically may be used
Think LLDP messages or CDP messages）, and send it to OpenFlow interchangers, it is desirable to which the OpenFlow interchangers are by neighbour
The corresponding ports that message is sent to opposite end OpenFlow interchangers are occupied, the field that wherein neighbours' message includes includes：Currently
OpenFlow switch identifications（IP, MAC etc.）, present port mark（Port IP, port mac, port id etc.）.
Step 1-3, receive neighbours' message for reporting of OpenFlow interchangers and identifying receive neighbours' message port whether
For physical port.
In order to identify that OpenFlow interchangers report whether the port of neighbours' message is physical port, in the present invention
In, it is also necessary to forwarding rule is created on all OpenFlow interchangers in advance, it is desirable to which OpenFlow interchangers connect its port
Neighbours' message that the opposite end of receipts is sent reports port identification unit.
Provided according to OpenFlow agreements, the neighbours' message reported for OpenFlow interchangers, be required to subsidiary reception
The port numbers of message（OFPXMT_OFB_IN_PORT）And its corresponding physical port number（OFPXMT_OFB_IN_PHY_PORT）.
If OFPXMT_OFB_IN_PORT is equal to OFPXMT_OFB_IN_PHY_PORT, it is physical port to illustrate the receiving port,
Then port identification unit record physical port information；If OFPXMT_OFB_IN_PORT is not equal to OFPXMT_OFB_IN_
PHY_PORT, it is logic port to illustrate receiving port, then port identification unit does not make any processing.So, port identification unit
After receiving neighbours' message that OpenFlow interchangers report, it is possible to identify that the port that the OpenFlow receives neighbours' message is
The no physical port on OpenFlow interchangers.
Further, port identification unit sends neighbours' message by physical port and gives opposite end OpenFlow switch ports themselves
Processing procedure it is as follows：
According to the physical port on the OpenFlow interchangers identified, neighbours' message is constructed again based on physical port,
And neighbours' message is sent into these physical ports, then indicate that neighbours' message is sent to opposite end by these physical ports
Port corresponding to OpenFlow interchangers, the field that wherein neighbours' message includes and the field in neighbours' message in abovementioned steps 1
It is identical.Including：Current OpenFlow switch identifications（IP, MAC etc.）, present port mark（Port IP, port mac, port id
Deng）.
Step 2, message process unit receive neighbours' message that OpenFlow interchanger physical ports report, and calculate accordingly
Go out network topology structure.
After neighbours' message that opposite end is sent is reported in the port of OpenFlow interchangers, message process unit only receives physics
Neighbours' message that port reports, and topology is calculated based on the neighbours' message received.So, all neighbours' messages are waited to receive
Bi Hou, OpenFlow network topology can be computed correctly out.Reported for non-physical port on OpenFlow interchangers
Neighbours' message, then directly make discard processing.
In order that those skilled in the art are more clear and clear, below should still with the OpenFlow networkings shown in Fig. 3
Implementation process of the present invention is described in detail with scene.
According to the inventive method, port identification unit is firstly the need of the physical port found on all OpenFlow.Specifically
Ground, port identification unit constructs neighbours' message respectively based on OFS1 ports eth2, eth3 and Aggregation1, and indicates these
Neighbours' message is sent to OFS2 corresponding ports by port.OFS2 each port receives neighbours' message of OFS1 ports transmission
Afterwards, these messages are reported into port identification unit.For the message that eth1 ports receive on OFS2, message is reported
OFPXMT_OFB_IN_PORT fields are port numbers corresponding to eth1, and OFPXMT_OFB_IN_PHY_PORT fields are also eth1 pairs
The port numbers answered；The message received for eth2 on OFS2, the OFPXMT_OFB_IN_PORT fields for reporting message are eth2 pairs
The port numbers answered, OFPXMT_OFB_IN_PHY_PORT fields are also port numbers corresponding to eth2；For on OFS2
The message that Aggregation1 ports receive, report the OFPXMT_OFB_IN_PORT fields of message corresponding for Aggregation1
Port numbers, OFPXMT_OFB_IN_PHY_PORT fields are port numbers corresponding to eth1 or eth2；It will be apparent that port identification list
Member can identify that eth1 and eth2 is OFS2 physical port, and Aggregation1 is not.Similarly, port identification unit base
In OFS2 ports, eth1, eth2 and Aggregation1 send neighbours' message respectively；Neighbour is being received by OFS1 corresponding ports
After occupying message, it is known that eth2 and eth3 are OFS1 physical ports.So, it is described according to neighbor discovering method of the present invention
Port identification unit can complete to obtain all physical port on OFS1 and OFS2 interchangers { OFS2, eth1 }, OFS2,
eth2},{OFS1,eth2},{OFS1,eth3}}。
Then, port identification unit constructs neighbours' message based on the physical port on OpenFlow interchangers, and indicates this
A little physical ports send neighbours' message to the port of opposite end OpenFlow interchangers, specifically：The port identification unit is based on
{ OFS2, eth1 } port configuration simultaneously indicates to send neighbours' message, neighbours' message carrying OFS2 device identification（IP, MAC etc.）、
Eth1 port-marks（Port IP, port mac, port id etc.）, and sent by { OFS2, eth1 }；Based on OFS2,
Eth2 } port configuration and indicate send neighbours' message, neighbours' message carry OFS2 device identification（IP, MAC etc.）, eth2 ports
Mark（Port IP, port mac, port id etc.）, and sent by { OFS2, eth2 }.Similarly, port identification unit is based on
{ OFS1, eth2 } port configuration simultaneously indicates to send neighbours' message, neighbours' message carrying OFS1 device identification（IP, MAC etc.）、
Eth2 port-marks（Port IP, port mac, port id etc.）, and sent by { OFS1, eth2 }；Based on OFS1,
Eth3 } port configuration and indicate send neighbours' message, neighbours' message carry OFS1 device identification（IP, MAC etc.）, eth3 ports
Mark（Port IP, port mac, port id etc.）, and sent by { OFS2, eth3 }.
Finally, what what the message process unit only handled that OpenFlow interchanger physical ports report sent from opposite end
Neighbours' message, and the annexation preserved according to neighbours' message calculates OpenFlow network topologies.Specifically, at the message
Reason unit neighbours' message { OFS1, eth2 } is received by { OFS2, eth1 } port, due to { OFS2, eth1 } and OFS1,
Eth2 } all it is physical port, therefore the Packet by Packet processing unit is reported so that the message process unit is according to the neighbours
Message preserves the annexation of OpenFlow inter-exchanges（OFS1:eth2-OFS2:eth1）；Similarly, message process unit is led to
Cross { OFS2, eth2 } port and receive neighbours' message { OFS1, eth3 }, because { OFS2, eth2 } and { OFS1, eth3 } is all thing
Port is managed, therefore annexation is preserved after message process unit is handled（OFS1:eth2-OFS2:eth1;OFS1:eth3-
OFS2:eth2）；When message receiving unit receives neighbours' message { OFS1, eth2 } by { OFS2, Aggregation1 } port
{ OFS1, eth3 }, because { OFS2, Aggregation1 } is not physical port, therefore directly abandon related neighbor information；When
Message process unit receives neighbours' message { OFS2, eth1 } by { OFS1, eth2 }, due to { OFS2, eth1 } and OFS1,
Eth2 } all it is physical port, it is necessary to preserve annexation, but due to（OFS1:eth2-OFS2:eth1）It has been existed that, therefore not
Preservation operation is performed again；Message process unit receives neighbours' message { OFS2, eth2 } by { OFS1, eth3 } port, due to
{ OFS1, eth3 } and { OFS2, eth2 } is all physical port, it is necessary to preserve annexation, but due to（OFS1:eth3-OFS2:
eth2）It has been existed that, therefore no longer perform and preserve operation；When neighbours find device on message process unit by OFS1,
Aggregation1 } port receives neighbours' message { OFS2, eth1 } and { OFS2, eth2 }, due to OFS1,
Aggregation1 } it is not physical port, therefore abandon related neighbor information；Finally, preserved according on OpenFlow controllers
Annexation（OFS1:eth2-OFS2:eth1;OFS1:eth3-OFS2:eth2）, neighbours' discovery device is available
Correct OpenFlow network topologies.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the invention, all essences in the present invention
God any modification, equivalent substitution and improvements done etc., should be included within the scope of protection of the invention with principle.
Claims (10)
1. a kind of neighbours have found device, apply in the OpenFlow network environments that physical port and logic port coexist, including
There are port identification unit and message process unit, it is characterised in that：
Port identification unit, constructed for identifying the physical port on all OpenFlow interchangers, and based on physical port
And send neighbours' message and give opposite end OpenFlow interchangers；
Message process unit, the neighbours' message reported for receiving OpenFlow interchanger physical ports, and net is calculated accordingly
Network topological structure.
2. device as claimed in claim 1, it is characterised in that the physics on port identification unit identification OpenFlow interchangers
The process of port is as follows：
All OpenFlow interchangers are traveled through, obtain the port on every OpenFlow interchanger；
Port configuration neighbours' message on OpenFlow interchangers based on acquisition, and require the port of the OpenFlow interchangers
Opposite end OpenFlow interchangers are sent it to after neighbours' message is received；
Receive neighbours' message that OpenFlow interchangers report and identify whether the port for receiving neighbours' message is physical port.
3. device as claimed in claim 2, it is characterised in that when what is carried in neighbours' message that OpenFlow interchangers report
The port numbers of reception message are equal with physical port number, then port identification unit identifies that the receiving port is physical port.
4. device as claimed in claim 3, it is characterised in that message process unit is used for the neighbours of calculating network topological structure
Message, after being the physical port that port identification unit is identified according to neighbours' message of construction on all OpenFlow interchangers,
The neighbours' message constructed again based on physical port.
5. device as claimed in claim 4, it is characterised in that message process unit is receiving the non-of OpenFlow interchangers
Discard processing is carried out after neighbours' message that physical port reports.
6. a kind of neighbor discovering method, applying in the OpenFlow network environments that physical port and logic port coexist, it is special
Sign is that methods described comprises the following steps：
Step 1, physical port on all OpenFlow interchangers is identified, and constructed based on physical port and send neighbours' report
Text gives opposite end OpenFlow interchangers；
Step 2, neighbours' message that OpenFlow interchanger physical ports report is received, and calculate network topology structure accordingly.
7. method as claimed in claim 6, it is characterised in that the port on the step 1 identification OpenFlow interchangers is
The process of physical port is as follows：
All OpenFlow interchangers are traveled through, obtain the port on every OpenFlow interchanger；
Port configuration neighbours' message on OpenFlow interchangers based on acquisition, and require the port of the OpenFlow interchangers
Opposite end OpenFlow interchangers are sent it to after neighbours' message is received；
Receive neighbours' message that OpenFlow interchangers report and identify whether the port for receiving neighbours' message is physical port.
8. method as claimed in claim 7, it is characterised in that when what is carried in neighbours' message that OpenFlow interchangers report
The port numbers of reception message are equal with physical port number, then it is physical port to identify the receiving port.
9. method as claimed in claim 8, it is characterised in that the neighbours that the step 2 is used for calculating network topological structure report
Text, after being the physical port that the step 1 is identified according to neighbours' message of construction on all OpenFlow interchangers, based on thing
Neighbours' message that reason port constructs again.
10. method as claimed in claim 9, it is characterised in that the step 2 is receiving the non-thing of OpenFlow interchangers
Discard processing is carried out after neighbours' message that reason port reports.
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 CN104243319A (en) | 2014-12-24 |
| CN104243319B true 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) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9979645B2 (en) * | 2015-01-14 | 2018-05-22 | Futurewei Technologies, Inc. | Hardware and software methodologies for creating and managing portable service function chains |
| CN106330781B (en) * | 2015-06-26 | 2020-02-07 | 中兴通讯股份有限公司 | Method, device and switch for separating protocol control and forwarding link of stacking system |
| CN105429875B (en) * | 2015-10-29 | 2018-10-12 | 上海斐讯数据通信技术有限公司 | Chain-link automatic finding method based on software defined network and system |
| US11533617B2 (en) * | 2020-09-30 | 2022-12-20 | Fortinet, Inc. | Secure link aggregation |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5493926B2 (en) * | 2010-02-01 | 2014-05-14 | 日本電気株式会社 | Interface control method, interface control method, and interface control program |
| CN102938722B (en) * | 2012-10-30 | 2017-11-10 | 中兴通讯股份有限公司 | The method and device that a kind of network equipment periodic protocol is given out a contract for a project |
-
2013
- 2013-06-06 CN CN201310227239.8A patent/CN104243319B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
|---|
| LLDP Overview;Paul Congdon;《http://www.ieee802.org/1/files/public/docs2002/LLDP%20Overview .pdf》;20030331;全文 * |
| Openflow switch specification v1.0.0 (1);OpenFlow;《http://www.openflowswitch.org/documents/openflow-spec-vl.0.0 .pdf》;20091231;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104243319A (en) | 2014-12-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105553880B (en) | Data processing method and device in a kind of software defined network | |
| CN105337857B (en) | A kind of multi-path transmission method based on software defined network | |
| CN105591912B (en) | A kind of selection method and device of forward-path | |
| CN104579894B (en) | The IGMP Snooping implementation methods and device of the distributed virtual switch system | |
| CN107968751B (en) | Information processing method and device | |
| CN104243319B (en) | The method and device that a kind of neighbours have found | |
| CN105227393B (en) | A kind of bidirectional forwarding detection (BFD) method | |
| CN105207950B (en) | A kind of communication data guard method based on SDN technology | |
| CN106341330A (en) | Topology discovery method and system of SDN controller | |
| CN105591754B (en) | A kind of verification head verification method and system based on SDN | |
| CN107404441B (en) | Method and equipment for data stream splitting in slicing network | |
| CN110351286A (en) | Link flood attack detects response mechanism in a kind of software defined network | |
| CN105009529B (en) | A kind of method and transponder handling message | |
| CN107317707A (en) | A kind of SDN topological management method based on vertex covering set | |
| CN104852855B (en) | Jamming control method, device and equipment | |
| CN107465622A (en) | A kind of method and system that discovering network topology is realized using LLDP | |
| CN105743687B (en) | Method and device for judging node fault | |
| CN102326370B (en) | Message processing method, apparatus and system | |
| CN107820262A (en) | Method for parameter configuration, apparatus and system | |
| CN105391690B (en) | A kind of network interception defence method and system based on POF | |
| CN105284083A (en) | OpenFlow device and IP network device communication method, device and system | |
| CN107547425A (en) | A kind of convergence-level data transmission method and system | |
| CN107465621A (en) | A kind of router finds method, SDN controllers, router and network system | |
| WO2016101600A1 (en) | Line card determination, determination processing method and device, and line card determination system | |
| CN107645391A (en) | A kind of port configuration method and device of Interface Expanding equipment |
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 |
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. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |