CN107682208A - A kind of SDN piggy back service quality acquisition method based on LLDP agreements - Google Patents
A kind of SDN piggy back service quality acquisition method based on LLDP agreements Download PDFInfo
- Publication number
- CN107682208A CN107682208A CN201711088788.6A CN201711088788A CN107682208A CN 107682208 A CN107682208 A CN 107682208A CN 201711088788 A CN201711088788 A CN 201711088788A CN 107682208 A CN107682208 A CN 107682208A
- Authority
- CN
- China
- Prior art keywords
- lldp
- interchanger
- controller
- qos
- quality
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
- H04L43/55—Testing of service level quality, e.g. simulating service usage
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
Abstract
The invention discloses a kind of SDN piggy back service quality acquisition method based on LLDP agreements, including step：Periodic QoS over LLDP sampling interval is set；Controller generation QoS TLV；Controller sends Packet_out to interchanger；Interchanger fills in quality of service information to QoS TLV；LLDP carries out multitransmission；Recipient's interchanger sends Packet_in message；Controller finds the link with quality of service information.The advantage of the invention is that：1. causing SDN controllers during Topology Discovery is carried out using LLDP agreements, piggy back collection is carried out to quality of service information.2. effective the characteristics of make use of LLDP Topology Discovery flows, realize that service quality gathers in the case where not introducing specialized protocol, reduce added flow.SDN OpenFlow southbound interface workflows will not be impacted simultaneously, realize non-intrusion type design.3. the characteristics of being directed to SDN is designed, without introducing extra network monitoring system to realize the collection of quality of service information.
Description
Technical field
The present invention relates to technical field of Internet information, more particularly to a kind of SDN piggy back based on LLDP agreements
Service quality acquisition method.
Background technology
Software defined network (Software-Defined Networking, SDN) is proposed by Stanford Univ USA
, it is designed based on OpenFlow agreements for construction network innovation platform.The characteristics of SDN maximums, is there is loose coupling
The control plane of conjunction and the network state of datum plane, support centralization control, realize bottom-layer network facility to upper layer application
It is transparent.Often using OpenFlow agreements as the southbound interface with underlay network device, (that is, controller interacts SDN with the network equipment
Interface), there is flexible software programmability so that the automatic management of network and control ability obtain unprecedented carry
Rise, can efficiently solve the resource extent extension that current network systems are faced is limited, networking flexibility is poor, be difficult to it is quick completely
The problems such as sufficient business demand.
Link discovery technology is the key that SDN controllers obtain the whole network information, is to realize network address learning, VLAN, road
By the necessary basis of the network functions such as forwarding.Find independently to carry out difference, SDN by each network element with legacy network link
In link discovery work completed by controller is unified.SDN controllers have mainly used LLDP (Link Layer Discovery
Protocol, Link Layer Discovery Protocol) link discovery protocols are used as, the agreement is proposed by IEEE, there is provided a kind of chain of standard
Road finds mode, can be organized into the information such as the unique ability of local device, management address, device identification, interface identifier not
Same TLV (Type/Length/Value, type/length/value), and it is encapsulated in LLDPDU (Link Layer Discovery
Protocol Data Unit, Link Layer Discovery Protocol data cell) in be distributed to the neighbours direct-connected with oneself, neighbours receive this
It is saved in the form of standard mib (Management Information Base, management information bank) after a little information,
Judge the communication conditions of link so that NMS Check is inquired about.Because SDN employs the mechanism of control of centralization, LLDP associations
The link and topology information that view operation obtains will focus on controller end.
In existing SDN frameworks, controller is only got in current network by southbound interface by LLDP agreements and handed over
The full mesh topology that quantity, the information of each port of interchanger and each link changed planes are formed, then controller opened up in the whole network
Forwarding strategy, and the switching equipment decentralization forwarding plan by the flow table in OpenFlow agreements to bottom are generated on the basis of flutterring
Slightly, the global management and control of centralization is realized.However, the information that current controller obtains from interchanger is still limited, cause
The forwarding strategy that controller is transferred at present is only some relatively simple forwarding strategies (such as shortest path based on hop count).
The guarantee of network service quality (Quality of Service, QoS) is the basis of good Consumer's Experience, and computer network
And the focus and emphasis of SDN area researches.And during existing link and Topology Discovery based on LLDP, can not be effective
Collection quality of service information so that the guarantee of SDN service quality becomes difficult, such as, it is difficult to for bandwidth intensive business (example
Such as video traffic) find the optimal path for meeting bandwidth demand, it is difficult to found for time delay sensitive type business (such as VoIP) full
Optimal path of sufficient delay requirement, etc., so as to which the forwarding strategy for meeting QoS requirement can not be formulated, realize to Service Quality
The guarantee of amount.
Existing technical scheme：
Discovering network topology of the 1.SDN controllers based on LLDP
SDN controllers often using LLDP carry out network topology structure discovery, Floodlight, OpenDaylight,
The main flow SDN controllers such as ONOS, Ryu, POX/NOX have used similar scheme.The main flow of the program is as follows, utilize with
It is illustrated exemplified by net environment very much：
Step 1：Controller sends Packet_out to interchanger.Controller firstly generates LLDP messages, and destination address is
LLDP multicast address.Hereafter, controller generation Packet_out messages, using the LLDP messages generated before this as Packet_out
The load of message, the interchanger for receiving the message will multitransmission.Controller by Packet_out messages be sent to it is all with
Its interchanger being joined directly together.Controller starts timing 15 seconds.
Step 2：Interchanger multicast LLDP message.The interchanger for receiving Packet_out separates LLDP load, according to
The instruction of action fields, multitransmission is carried out to LLDP, i.e., send LLDP to phase from all of the port in addition to receiving port
Adjacent interchanger.Convenient to illustrate, the interchanger of multitransmission LLDP messages is referred to as sender's interchanger, and title receives LLDP reports
The interchanger of text is recipient's interchanger.
Step 3：Recipient's interchanger sends Packet_in message.According to the workflow of OpenFlow agreements, recipient
Interchanger will match the LLDP messages received in the flow table of oneself.Because interchanger is free of the flow table item of processing LLDP messages,
Interchanger will send Packet_in message to controller, how be handled LLDP messages as its load, inquiry.
Step 4：Controller finds link.Carrying Packet_in Ether frame contains the MAC Address of recipient's interchanger
Etc. information, and the LLDP messages that Packet_in is included contain the information such as the MAC Address of sender's interchanger, therefore can sentence
Link be present between recipient's interchanger in disconnected sender's interchanger.This link information is stored in controller end by controller.
Step 1-4 is performed repeatedly in respective switch so that controller can find global Topological Structure.
Step 5：Controller checks whether timing is overtime 15 seconds, overtime then jump procedure 1, starts next round link and topology
It was found that flow, to tackle the change that topological structure may occur.
It can be seen that in the above-mentioned technical solutions, although circularly having carried out topology discovery, each interchanger
Quality of service information is not gathered effectively by controller.
2. the service quality collection of Based Network Monitoring technology
SFlow softwares are the Typical Representatives of this kind of scheme.SFlow is the network prison by the company such as InMon joint development
Software is surveyed, using data flow random sampling technique, it is possible to provide the complete second layer to the 4th layer, or even the stream in the range of whole network
Information is measured, the flow analysis being adapted under super large network traffics (such as larger than 10Gbit/s) environment, allows user in detail, in real time
The problem of analyzing the performance of network transmission stream, trend and existing.SFlow monitoring tools are by sFlow Agent and sFlow
Collector two parts form.Agent is typically embedded in network forwarding equipment (such as interchanger, router) as client,
By obtaining interface statistic and data message in this equipment, by Information encapsulation into sFlow messages, the message format by
RFC 3176 is defined.When sFlow message buffers are full or after sFlow packet buffer times (cache-time is 1 second) time-out,
SFlow messages can be sent to the Collector specified by sFlow Agent.Collector is responsible for pair as far-end server
SFlow message analysis, collect, generate traffic report.
It is insufficient existing for prior art：
The technical scheme of above-mentioned discovering network topology of the SDN controllers based on LLDP does not include the step of quality of service aware
Suddenly, i.e. Service Quality Metrics that will not be current to interchanger, each port bandwidth of such as interchanger, time delay, packet loss, shake, enter
Row collection.Under the technical program, the collection of quality of service information is if desired carried out, implements quality-of-service based Route Selection
Or network strategy, then need to dispose extra bypath system.That is, discovery and the quality of service information of network topology structure
Collection be relative two stages isolated.
The technical scheme of the service quality collection of above-mentioned Based Network Monitoring technology not specially designs for SDN, is
A kind of general network monitor technology, therefore the technical scheme depends on the collection of network monitor technology service implementation quality, needs
There is the background knowledge of network monitor technology, under SDN backgrounds, especially to the unfamiliar network management of network monitor technology
Member/user, this can cause extra burden, use curve comparable steepness.Network manager/user is it is understood that Collector
With the concept of the specific area such as Agent, and correct configuration is done to it, that is to say, that this kind of scheme is for SDN keepers/use
It is " opaque " for family.Flow detection result is sent to Collector from Agent, it is necessary to special InMon in order to realize
SFlow agreements are used for encapsulation of data, the byte of size 592 of each sFlow packets (possibly rely on configuration and different),
In default situations, sFlow data acquisition intervals are 1 second, generate more added flow, and band is competed with customer flow
It is wide.
The content of the invention
A kind of the defects of present invention is directed to prior art, there is provided SDN piggy back Service Quality based on LLDP agreements
Acquisition method is measured, can effectively solve the problem that the above-mentioned problems of the prior art.
In order to realize above goal of the invention, the technical scheme that the present invention takes is as follows：
A kind of SDN piggy back service quality acquisition method based on LLDP agreements, comprises the following steps：
Step 1, the sampling interval for setting periodic QoS over LLDP, the sampling interval are that controller sends LLDP reports
The time interval of text, if not setting explicitly, give tacit consent to 15 seconds；
Step 2, controller generation QoS TLV, generate customized TLV fields in controller end, be i.e. QoS TLV, be used for
Subsequent step incidentally gathers each Service Quality Metrics of each port of interchanger, including bandwidth, time delay, shake, packet loss；
Step 3, controller send Packet_out and firstly generate LLDP messages to interchanger, controller, and destination address is
LLDP multicast address, and the QoS TLV in step 2 are put into the TLV lists of LLDP messages；Hereafter, controller generates
Packet_out messages, the load using the LLDP messages generated before this as Packet_out messages, receive the exchange of the message
Machine will multitransmission；Packet_out messages are sent to all interchangers being directly connected by controller, and controller is opened
Beginning timing, the sampling interval that timing duration is set by step 1 determine；
Step 4, interchanger fill in quality of service information to QoS TLV, and the interchanger for receiving Packet_out separates
LLDP load, LLDP multitransmissions port is determined, the bandwidth of the port of LLDP multitransmissions to be implemented, time delay, shake, packet loss
The quality of service information such as rate insert QoS TLV；
Step 5, interchanger multicast LLDP message are right according to the instruction of action fields after having filled in QoS TLV
LLDP carries out multitransmission, i.e., LLDP is sent to adjacent interchanger from all of the port in addition to receiving port, for elaboration side
Just, the interchanger of multitransmission LLDP messages is referred to as sender's interchanger, and the interchanger for receiving the LLDP messages is referred to as recipient
Interchanger；
Step 6, recipient's interchanger send Packet_in message, according to the workflow of OpenFlow agreements, recipient
Interchanger will match the LLDP messages received in the flow table of oneself, because interchanger is free of the flow table item of processing LLDP messages,
Interchanger will send Packet_in message to controller, how be handled LLDP messages as its load, inquiry；
Step 7, controller find the link with quality of service information, obtain recipient's interchanger mac address information and
The mac address information of sender's interchanger, judge sender's interchanger with existing link between recipient's interchanger；According to
LLDP QoS TLV fields determination contains the quality of service information of switch ports themselves, and this link is band quality of service information
's；This link information is stored in controller end by controller.
Step 8, controller check whether timer is overtime, overtime then jump procedure 2；Actively whether controller check user
Active QoS over LLDP are called, if any then jump procedure 2.
Further, the value of TLV type field is 127 in step 2, and sub-type field is 0x66.
Further, the specific sub-step of the step 4 is as follows：
Step 41, calculate effective bandwidth：The effective bandwidth of t subtracts ratio of the t by port by port total bandwidth
Special number：bandwidtht=bandwidthtotal-bitst；
Step 42, calculation delay：Unit is us：delayt=1/packetst, wherein packetstIt is to pass through in t
The number of the packet of port, if packetst<packetsthreash, then delay is madetThe packet that=N/A, i.e. t are received
It is few, less than default lower limit packetsthreash, then it is assumed that it can not accurately estimate, be set to Not-a-Number N/A；
Step 43, calculate shake：Shake is the variable quantity of front and rear time delay, and unit is us：jittert=Δ delayt=
delayt-delayt-1；
Step 44, calculate packet loss：The packet loss of each port has record in systems, using tc-s qdisc show
The order of implementor name directly obtains, without manual calculations；
Step 45, the QoS information of itself is filled into the TLV specified, must modification interchanger source code realize itself QoS
Information is filled in LLDP.
Compared with prior art the advantage of the invention is that：
1. SDN controllers during Topology Discovery is carried out using LLDP agreements, are carried out to quality of service information
Piggy back gathers.Because each quasi-controller has widely used the flow that LLDP topology sides find, it is utilized to carry out piggy back clothes
Quality of being engaged in collection, flow is familiar with for SDN administrator/users, is relative " transparent ".
2. effective the characteristics of make use of LLDP Topology Discovery flows, service is realized in the case where not introducing specialized protocol
Quality gathers, and reduces added flow.SDN OpenFlow southbound interface workflows will not be impacted, realized simultaneously
Non-intrusion type designs.
3. the characteristics of being directed to SDN is designed, without introducing extra network monitoring system to realize quality of service information
Collection.
Brief description of the drawings
Fig. 1 is QoS TLV structure charts of the embodiment of the present invention；
Fig. 2 is the script figure that the embodiment of the present invention calculates service quality；
Fig. 3 is the Open vSwicth interchanger code maps that the embodiment of the present invention fills in QoS TLV；
Fig. 4 is that Floodlight controllers of the embodiment of the present invention read QoS information figure from LLDP；
The main flow chart of Fig. 5 embodiment of the present invention；
The schematic diagram of Fig. 6 embodiment of the present invention.
Embodiment
For the objects, technical solutions and advantages of the present invention are more clearly understood, develop simultaneously embodiment referring to the drawings, right
The present invention is described in further details.
Step 1, the sampling interval that periodic QoS over LLDP are set.The sampling interval is that controller sends LLDP reports
The time interval of text, if not setting explicitly, give tacit consent to 15 seconds.When this programme is embodied, it is contemplated that LLDP agreements are former
15 seconds fixed time-count cycles, the flexibility in terms of service quality is gathered was poor, devised corresponding controller northbound interface REST
API is used for the cycle for adjusting the transmission of LLDP messages, i.e. periodic performs, and time-count cycle is adjustable, adjusts the REST API in cycle
For：http://{ip}:8080/wm/qosoverlldp/Lldptoallinterval/ { interval }/json, wherein { ip }
To dispose the IP address of the main frame of Floodlight controllers, { interval } is integer not less than 1, unit：Second.
Step 2, controller generation QoS TLV.Customized TLV fields are generated in controller end, be i.e. QoS TLV, are used for
Subsequent step incidentally gathers each Service Quality Metrics of each port of interchanger, including bandwidth, time delay, shake, packet loss etc..SDN
Web vector graphic LLDP as link discovery protocols, the agreement by the unique ability of local device, management address, device identification, connect
The information such as mouth mark are organized into different TLV (Type/Length/Value, type/length/value).Therefore, this project is intended using
TLV deposits the QoS information of underlying device.In order to save network overhead, several QoS informations are all placed on a TLV by this project
The inside.Wherein, originally there is the TLV that recording interactive postpones in LLDP Central Plains, so not add additionally.Specific QoS TLV designs
As shown in Figure 1.The value of TLV type field is 127, and sub-type field is 0x66, i.e., metric 102, this is this item purpose
Subtype identifies.The reason for type field uses 127：It is Standford types, is a kind of generally acknowledged TLV types, TLV's
Length is Institution Code (0xabcdef, showing a QoS TLV), subtype, the sum of length shared by QoS；Wherein, four QoS
Default initial values be all 0x7fffffffffffffff, why be not configured to 0x0000000000000000, be in order to anti-
Only obscure with actual QoS value for 0 situation.
Step 3, controller send Packet_out to interchanger.Controller firstly generates LLDP messages, and destination address is
LLDP multicast address, and the QoS TLV in step 2 are put into the TLV lists of LLDP messages.Hereafter, controller generates
Packet_out messages, the load using the LLDP messages generated before this as Packet_out messages, receive the exchange of the message
Machine will multitransmission.Packet_out messages are sent to all interchangers being directly connected by controller.Controller is opened
Beginning timing, the sampling interval that timing duration is set by step 1 determine.
Step 4, interchanger fill in quality of service information to QoS TLV.The interchanger for receiving Packet_out separates
LLDP load, determine LLDP multitransmissions port (export), the bandwidth of the port of LLDP multitransmissions to be implemented, time delay,
The quality of service information such as shake, packet loss insert QoS TLV.Under this specific implementation environment, because OVS interchangers are deployed in
On (SuSE) Linux OS, bandwidth, time delay, shake, packet loss can calculate in the following way.It should be noted that it is directed to it
His specific hardware switch, bandwidth, time delay, shake, packet loss need to calculate according to hardware environment, i.e. following sub-step can quilt
Replace.It is further noted that the present invention focuses on service quality acquisition method of the design based on LLDP agreement piggy backs, service
The calculating of quality is not the emphasis of the present invention, therefore its calculating can voluntarily be replaced according to specific environment.
Step 41, computation bandwidth：Here bandwidth refers to effective bandwidth, and unit is bps, inside linux system, often
The flow information for the packet that each interface of individual OVS pbx processes is passed through is recorded in/sys/devices/
In corresponding folder below this catalogue of virtual/net/, can easily it inquire about.The effective bandwidth of t is by the total band in port
Width subtracts bit number of the t by port：bandwidtht=bandwidthtotal-bitst
Step 42, calculation delay：The calculating of time delay employs simplified algorithm and estimated, unit is us：delayt=
1/packetst, wherein packetstIt is in number of the t by the packet of port.If packetst<packetsthreash,
Then make delaytThe packet that=N/A, i.e. t are received is very few, less than default lower limit packetsthreash, then it is assumed that can not
Accurate estimation, is set to Not-a-Number N/A (Not a Number).
Step 43, calculate shake：Shake is the variable quantity of front and rear time delay, and unit is us：jittert=Δ delayt=
delayt-delayt-1
Step 44, calculate packet loss：The packet loss of each port has record in linux system, using tc-s qdisc
The order of show implementor names directly obtains, without manual calculations.
The process that whole service quality calculates above, is realized, specific code is such as particular by Linux Shell scripts
Shown in Fig. 2.
Step 45, the QoS information of itself is filled into inside the TLV specified.Then, it is necessary to change Open vSwicth sources
Code realizes that itself QoS information is filled in LLDP, realizes that code is as shown in Figure 3.
Step 5, interchanger multicast LLDP message.It is right according to the instruction of action fields after having filled in QoS TLV
LLDP carries out multitransmission, i.e., sends LLDP to adjacent interchanger from all of the port in addition to receiving port.For elaboration side
Just, the interchanger of multitransmission LLDP messages is referred to as sender's interchanger, and the interchanger for receiving the LLDP messages is referred to as recipient
Interchanger.
Step 6, recipient's interchanger send Packet_in message.According to the workflow of OpenFlow agreements, recipient
Interchanger will match the LLDP messages received in the flow table of oneself.Because interchanger is free of the flow table item of processing LLDP messages,
Interchanger will send Packet_in message to controller, how be handled LLDP messages as its load, inquiry.
Step 7, controller find the link with quality of service information.Carrying Packet_in Ether frame contains reception
The information such as the MAC Address of square interchanger, and the LLDP messages that Packet_in is included contain the MAC Address of sender's interchanger
Etc. information, therefore it may determine that sender's interchanger has link between recipient's interchanger.Meanwhile LLDP QoS TLV
Field contains the quality of service information of switch ports themselves, therefore this link is with quality of service information.Controller by this
One link information is stored in controller end.Change Floodlight source codes so that Packet_in data of the controller in LLDP
The quality of service information of all interchangers in network is extracted in bag, realizes code such as Fig. 4.Step 2- steps 7 are in each exchange
Machine performs repeatedly so that controller can find the global Topological Structure with quality of service information.
Step 8, controller check whether timer is overtime, overtime then jump procedure 2；Actively whether controller check user
Active QoS over LLDP are called, if any then jump procedure 2, its REST API is：http://{ip}:8080/wm/
Qosoverlldp/proactive/json, wherein { ip } is the IP address of deployment Floodlight main frame.
As shown in figure 5, elaborate that the present invention utilizes the overall procedure of LLDP agreements collection service quality in SDN.
As shown in fig. 6, by taking the simple topology structure of a controller and two interchangers as an example, the core of the present invention is given
Heart operation principle, wherein solid line give the link of collection switch A and the process of service quality, and dotted line gives collection and exchanged
Machine B link and the process of service quality.
One of ordinary skill in the art will be appreciated that embodiment described here is to aid in reader and understands this hair
Bright implementation, it should be understood that protection scope of the present invention is not limited to such especially statement and embodiment.Ability
The those of ordinary skill in domain can be made according to these technical inspirations disclosed by the invention it is various do not depart from essence of the invention its
Its various specific deformations and combination, these deformations and combination are still within the scope of the present invention.
Claims (3)
1. a kind of SDN piggy back service quality acquisition method based on LLDP agreements, it is characterised in that comprise the following steps：
Step 1, the sampling interval for setting periodic QoS over LLDP, the sampling interval are that controller sends LLDP messages
Time interval, if not setting explicitly, give tacit consent to 15 seconds；
Step 2, controller generation QoS TLV, customized TLV fields, i.e. QoS TLV, for follow-up are generated in controller end
Step incidentally gathers each Service Quality Metrics of each port of interchanger, including bandwidth, time delay, shake, packet loss；
Step 3, controller send Packet_out and firstly generate LLDP messages, destination address LLDP to interchanger, controller
Multicast address, and the QoS TLV in step 2 are put into the TLV lists of LLDP messages；Hereafter, controller generation Packet_
Out messages, the load using the LLDP messages generated before this as Packet_out messages, the interchanger for receiving the message will be more
Broadcast forwarding；Packet_out messages are sent to all interchangers being directly connected by controller, and controller starts timing, counts
The sampling interval that Shi Shichang is set by step 1 determines；
Step 4, interchanger fill in quality of service information to QoS TLV, and the interchanger for receiving Packet_out separates LLDP loads
Lotus, LLDP multitransmissions port is determined, the bandwidth of the port of LLDP multitransmissions to be implemented, time delay, shake, packet loss etc. are taken
Business quality information inserts QoS TLV；
Step 5, interchanger multicast LLDP message, after having filled in QoS TLV, according to the instruction of action fields, enter to LLDP
Row multitransmission, i.e., LLDP is sent to adjacent interchanger from all of the port in addition to receiving port, convenient to illustrate, title is more
The interchanger for broadcasting forwarding LLDP messages is sender's interchanger, and the interchanger for receiving the LLDP messages is referred to as recipient's interchanger；
Step 6, recipient's interchanger send Packet_in message, and according to the workflow of OpenFlow agreements, recipient exchanges
Machine will match the LLDP messages received in the flow table of oneself, due to flow table item of the interchanger without processing LLDP messages, exchange
Machine will send Packet_in message to controller, how be handled LLDP messages as its load, inquiry；
Step 7, controller find the link with quality of service information, obtain mac address information and the transmission of recipient's interchanger
The mac address information of square interchanger, judge sender's interchanger with existing link between recipient's interchanger；According to LLDP's
The determination of QoS TLV fields contains the quality of service information of switch ports themselves, and this link is with quality of service information；Control
This link information is stored in controller end by device.
Step 8, controller check whether timer is overtime, overtime then jump procedure 2；Controller checks whether user actively calls
Active QoS over LLDP, if any then jump procedure 2.
2. a kind of SDN piggy back service quality acquisition method based on LLDP agreements according to claim 1, it is special
Sign is：The value of TLV type field is 127 in step 2, and sub-type field is 0x66.
3. a kind of SDN piggy back service quality acquisition method based on LLDP agreements according to claim 1, it is special
Sign is：The specific sub-step of the step 4 is as follows：
Step 41, calculate effective bandwidth：The effective bandwidth of t subtracts bit number of the t by port by port total bandwidth：
bandwidtht=bandwidthtotal-bitst；
Step 42, calculation delay：Unit is us：delayt=1/packetst, wherein packetstIt is by port in t
Packet number, if packetst＜ packetsthreash, then delay is madetThe packet that=N/A, i.e. t are received is very few, few
In default lower limit packetsthreash, then it is assumed that it can not accurately estimate, be set to Not-a-Number N/A；
Step 43, calculate shake：Shake is the variable quantity of front and rear time delay, and unit is us：jittert=Δ delayt=delayt-
delayt-1；
Step 44, calculate packet loss：The packet loss of each port has record in systems, using tc-s qdisc show equipment
The order of name directly obtains, without manual calculations；
Step 45, the QoS information of itself is filled into the TLV specified, must modification interchanger source code realize itself QoS information
LLDP is filled in.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711088788.6A CN107682208A (en) | 2017-11-08 | 2017-11-08 | A kind of SDN piggy back service quality acquisition method based on LLDP agreements |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711088788.6A CN107682208A (en) | 2017-11-08 | 2017-11-08 | A kind of SDN piggy back service quality acquisition method based on LLDP agreements |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107682208A true CN107682208A (en) | 2018-02-09 |
Family
ID=61146776
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711088788.6A Pending CN107682208A (en) | 2017-11-08 | 2017-11-08 | A kind of SDN piggy back service quality acquisition method based on LLDP agreements |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107682208A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110708216A (en) * | 2019-10-12 | 2020-01-17 | 深圳市吉祥腾达科技有限公司 | Switch LLDP protocol test method and test system |
| CN111698122A (en) * | 2020-06-12 | 2020-09-22 | 南京北星极网络科技有限公司 | Network topology discovery method based on SDN |
| CN113630481A (en) * | 2021-08-13 | 2021-11-09 | 上海微波技术研究所（中国电子科技集团公司第五十研究所） | Automatic in-band control plane construction method and system in SDN |
| CN114095508A (en) * | 2020-07-31 | 2022-02-25 | 南京理工大学 | Method for P2P transmission under same switch |
| CN114449049A (en) * | 2022-01-19 | 2022-05-06 | 广东优力普物联科技有限公司 | Communication device and communication system based on light management data interaction |
| CN114553768A (en) * | 2021-12-29 | 2022-05-27 | 航天科工网络信息发展有限公司 | Networking method based on SDN |
| CN114978305A (en) * | 2018-02-13 | 2022-08-30 | 瞻博网络公司 | Method and apparatus for consistency check in a decomposed DWDM system |
| CN115484214A (en) * | 2022-09-13 | 2022-12-16 | 杭州迦尔科技有限公司 | Industrial control network terminal type detection and network service quality optimization method |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101645849A (en) * | 2009-09-09 | 2010-02-10 | 中兴通讯股份有限公司 | QoS realization method in transitional environment and PE router |
| CN102238066A (en) * | 2010-04-27 | 2011-11-09 | 杭州华三通信技术有限公司 | Real-time traffic reporting method, media endpoint and system |
| CN103999404A (en) * | 2011-06-22 | 2014-08-20 | 华为技术有限公司 | Internet group management protocol version three for quality of service support |
| CN104901890A (en) * | 2015-06-24 | 2015-09-09 | 上海斐讯数据通信技术有限公司 | Route generating and coupling method and system of SDN |
| CN104980302A (en) * | 2015-05-12 | 2015-10-14 | 上海斐讯数据通信技术有限公司 | STP-based method for removing redundancy link under SDN framework |
| CN106789709A (en) * | 2016-12-21 | 2017-05-31 | 迈普通信技术股份有限公司 | A kind of method and device of load balancing |
| WO2017123254A1 (en) * | 2016-01-15 | 2017-07-20 | Hewlett Packard Enterprise Development Lp | Storage area network management packets |
-
2017
- 2017-11-08 CN CN201711088788.6A patent/CN107682208A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101645849A (en) * | 2009-09-09 | 2010-02-10 | 中兴通讯股份有限公司 | QoS realization method in transitional environment and PE router |
| CN102238066A (en) * | 2010-04-27 | 2011-11-09 | 杭州华三通信技术有限公司 | Real-time traffic reporting method, media endpoint and system |
| CN103999404A (en) * | 2011-06-22 | 2014-08-20 | 华为技术有限公司 | Internet group management protocol version three for quality of service support |
| CN104980302A (en) * | 2015-05-12 | 2015-10-14 | 上海斐讯数据通信技术有限公司 | STP-based method for removing redundancy link under SDN framework |
| CN104901890A (en) * | 2015-06-24 | 2015-09-09 | 上海斐讯数据通信技术有限公司 | Route generating and coupling method and system of SDN |
| WO2017123254A1 (en) * | 2016-01-15 | 2017-07-20 | Hewlett Packard Enterprise Development Lp | Storage area network management packets |
| CN106789709A (en) * | 2016-12-21 | 2017-05-31 | 迈普通信技术股份有限公司 | A kind of method and device of load balancing |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114978305A (en) * | 2018-02-13 | 2022-08-30 | 瞻博网络公司 | Method and apparatus for consistency check in a decomposed DWDM system |
| CN110708216A (en) * | 2019-10-12 | 2020-01-17 | 深圳市吉祥腾达科技有限公司 | Switch LLDP protocol test method and test system |
| CN111698122A (en) * | 2020-06-12 | 2020-09-22 | 南京北星极网络科技有限公司 | Network topology discovery method based on SDN |
| CN114095508A (en) * | 2020-07-31 | 2022-02-25 | 南京理工大学 | Method for P2P transmission under same switch |
| CN113630481A (en) * | 2021-08-13 | 2021-11-09 | 上海微波技术研究所（中国电子科技集团公司第五十研究所） | Automatic in-band control plane construction method and system in SDN |
| CN113630481B (en) * | 2021-08-13 | 2023-11-28 | 上海微波技术研究所（中国电子科技集团公司第五十研究所） | Automatic in-band control plane construction method and system in SDN |
| CN114553768A (en) * | 2021-12-29 | 2022-05-27 | 航天科工网络信息发展有限公司 | Networking method based on SDN |
| CN114449049A (en) * | 2022-01-19 | 2022-05-06 | 广东优力普物联科技有限公司 | Communication device and communication system based on light management data interaction |
| CN115484214A (en) * | 2022-09-13 | 2022-12-16 | 杭州迦尔科技有限公司 | Industrial control network terminal type detection and network service quality optimization method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107682208A (en) | A kind of SDN piggy back service quality acquisition method based on LLDP agreements | |
| Shaikh et al. | An OSPF topology server: Design and evaluation | |
| CN106209490B (en) | Select and monitor the method and system of multiple service key performance indicators | |
| US8130661B2 (en) | Systems and methods for intelligent probe testing | |
| US9294973B2 (en) | Peer-based handoff performance measurement | |
| CN103959713B (en) | Measurement to the data flow in communication network | |
| Feng et al. | OpenRouteFlow: Enable legacy router as a software-defined routing service for hybrid SDN | |
| Paolucci et al. | Interoperable multi-domain delay-aware provisioning using segment routing monitoring and BGP-LS advertisement | |
| Feamster et al. | Network-wide BGP route prediction for traffic engineering | |
| Chahlaoui et al. | Towards QoS-enabled SDN networks | |
| JP2010193055A (en) | Flow information transmitter, intermediate apparatus, flow information transmission method and program | |
| Raspall | Building Nemo, a system to monitor IP routing and traffic paths in real time | |
| Pitkanen et al. | OSPF flooding process optimization | |
| CN109688062A (en) | A kind of method for routing and routing device | |
| Alberi et al. | Using real-time measurements in support of real-time network management | |
| Andersson et al. | Performance management in software defined networking | |
| Menth | Analysis and Design of Advanced Multiservice Networks Supporting Mobility, Multimedia, and Internetworking COST-279–Midterm Report | |
| Katov | Energy Efficient Mechanism for Next Generation Networks: Adaptive Resource Allocation | |
| Ruotsalainen | L3 Latency in Regional Networks: Preparing 5G launch | |
| Farkas | Resilience and quality of service assurance methods in ethernet and utran networks | |
| Jonglez et al. | A delay-based metric for the Babel routing protocol | |
| EP1683301B1 (en) | Systems and methods for intelligent probe testing | |
| Sapountzis | Traffic monitoring for green networking | |
| Abrahamsson | Internet traffic management | |
| Akonjang | ISP traffic management via flow optimization |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180209 |