CN104683243B - A kind of data processing method, apparatus and system - Google Patents
A kind of data processing method, apparatus and system Download PDFInfo
- Publication number
- CN104683243B CN104683243B CN201310611749.5A CN201310611749A CN104683243B CN 104683243 B CN104683243 B CN 104683243B CN 201310611749 A CN201310611749 A CN 201310611749A CN 104683243 B CN104683243 B CN 104683243B
- Authority
- CN
- China
- Prior art keywords
- flow entry
- interchanger
- controller
- message
- synchronous
- 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 embodiment of the invention discloses a kind of data processing methods, apparatus and system, wherein method includes: that controller receives synchronization request message, the synchronization request message is that interchanger requests for the first flow entry on the controller to be synchronized to the message on the interchanger, and first flow entry is the flow entry that the controller is sent before receiving the synchronization request message to the interchanger;The controller obtains first flow entry according to the synchronization request message;First flow entry is sent to the interchanger by the controller.Using this method and system, the flow entry that can be achieved between controller and interchanger is synchronous, it avoids causing the nonsynchronous phenomenon of the flow entry between controller and interchanger because interchanger loses flow entry, the automatic error correction function in data transmission procedure is increased, the safety of network equipment information interaction is improved.
Description
Technical field
The present invention relates to field of communication technology more particularly to a kind of data processing methods, apparatus and system.
Background technique
As the fast development of internet and the demand of internet new business constantly increase, OpenFlow network is as a kind of
Novel network exchange model keeps it more and more concerned the huge impetus that the innovation and development of network plays and props up
It holds.
OpenFlow network includes interchanger, controller Controller and network virtual layer FlowVisor.Wherein, it hands over
Changing planes is the core component of entire OpenFlow network, the main forwarding for managing data Layer, by flow table, exit passageway and
OpenFlow agreement three parts composition, interchanger include dedicated OpenFlow interchanger and the interchanger for supporting OpenFlow.
Controller realizes the function of control layer, and by OpenFlow consultative management and control OpenFlow interchanger, exit passageway is to connect
Connect OpenFlow interchanger to controller interface.FlowVisor is that the network between hardware configuration element and software is empty
Quasi- layer.
After controller issues flow entry to interchanger by existing OpenFlow agreement, in processing stream inside interchanger
When list item, due to interchanger inter-process OpenFlow protocol massages process and processing flow entry process be not it is same into
Journey, and interprocess communication is possible to the phenomenon that data packetloss occur, and flow entry is caused to be lost, so that the flow entry of interchanger
It is asynchronous with the flow entry of controller.
Summary of the invention
The technical problem to be solved by the embodiment of the invention is that a kind of data processing method, apparatus and system are provided, it can
It realizes that the flow entry between controller and interchanger is synchronous, increases the automatic error correction function after flow entry is lost.
In order to solve the above-mentioned technical problem, first aspect present invention provides a kind of data processing method, it may include:
Controller receives synchronization request message, and the synchronization request message is that interchanger is requested the on the controller
One flow entry is synchronized to the message on the interchanger, and first flow entry, which is the controller, asks receiving the synchronization
Seek the flow entry sent before message to the interchanger;
The controller obtains first flow entry according to the synchronization request message;
First flow entry is sent to the interchanger by the controller.
Based in a first aspect, being taken in the synchronization request message in the first feasible embodiment of first aspect
Band first time point;Correspondingly, the controller obtains first flow entry according to the synchronization request message, comprising:
The controller parses the synchronization request message, obtains the first time point;
The controller before the first time point is determined as by the controller to the flow entry that the interchanger is sent
First flow entry;
The controller obtains first flow entry.
Based on the feasible embodiment of the first of first aspect or first aspect, second in first aspect is feasible
In embodiment, before first flow entry is sent to the interchanger by the controller, further includes:
The controller sends synchronous beginning message to the interchanger, and the synchronous message that starts is for notifying the friendship
The controller of changing planes starts to send first flow entry;
After first flow entry is sent to interchanger by the controller, further includes:
The controller sends synchronous end message to the interchanger, and the synchronous end message is for notifying the friendship
The controller of changing planes terminates to send first flow entry.
Second of feasible reality based on the feasible embodiment first aspect of the first of first aspect or first aspect
Mode is applied, in the third feasible embodiment of first aspect, is sent to the flow entry in the controller described
Before interchanger, further includes:
The controller is used to indicate first flow entry to the first flow entry setting flag, the label as institute
It states interchanger and requests synchronous flow entry.
Second aspect of the present invention provides a kind of data processing method, it may include:
Interchanger sends synchronization request message to controller, and the synchronization request message is that interchanger request will be described
The first flow entry on controller is synchronized to the message on the interchanger, and first flow entry is that the controller is receiving
The flow entry sent before to the synchronization request message to the interchanger;
The interchanger receives first flow entry that the controller is sent.
It is taken in the synchronization request message in the first feasible embodiment of second aspect based on second aspect
Band first time point, the first time point are used to indicate the controller for the controller before the first time point to institute
The flow entry for stating interchanger transmission is determined as first flow entry.
Based on the feasible embodiment of the first of second aspect or second aspect, second in second aspect is feasible
In embodiment, the interchanger sends synchronization request message to controller, comprising:
Interchanger tests to stored flow entry;
The synchronization request message is sent to the controller according to inspection result.
Second of feasible embodiment based on second aspect, in the third feasible embodiment of second aspect
In, it is described that the synchronization request message is sent to the controller according to inspection result, comprising:
When examining the sequence number for arriving the stored flow entry discontinuous or the stored flow entry is lost,
The synchronization request message is sent to the controller.
Second based on the feasible embodiment of the first of second aspect or second aspect or second aspect feasible
The feasible embodiment of the third of embodiment or second aspect, in the 4th kind of feasible embodiment of second aspect,
After the interchanger sends synchronization request message to the controller and the interchanger receives the controller and sends
First flow entry before, further includes:
The interchanger receives the synchronous beginning message that the controller is sent, and the synchronous message that starts is for notifying institute
Controller described in interchanger is stated to start to send first flow entry;
After first flow entry that the interchanger receives that the controller is sent, further includes:
The interchanger receives the synchronization end message that the controller is sent, and the synchronous end message is for notifying institute
Stating controller described in interchanger terminates to send first flow entry;
The interchanger is arranged first flow entry with the synchronous end message according to the synchronous beginning message
Label, the label, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.
Second based on the feasible embodiment of the first of second aspect or second aspect or second aspect feasible
4th kind of feasible embodiment of the feasible embodiment of the third of embodiment or second aspect or second aspect,
In 5th kind of feasible embodiment of two aspects, first flow entry carries label, and the label is used to indicate described the
One flow entry is requested synchronous flow entry by the interchanger.
Third aspect present invention provides a kind of controller, it may include:
Message reception module, for receiving synchronization request message, the synchronization request message is that interchanger request will be described
The first flow entry on controller is synchronized to the message on the interchanger, and first flow entry is that the controller is receiving
The flow entry sent before to the synchronization request message to the interchanger;
Flow entry obtains module, for obtaining first flow entry according to the synchronization request message;
Flow entry sending module, for first flow entry to be sent to the interchanger.
It is taken in the synchronization request message in the first feasible embodiment of the third aspect based on the third aspect
Band first time point;The flow entry obtains module
Resolution unit obtains the first time point for parsing the synchronization request message;
Flow entry determines subelement, and the flow entry for the controller before the first time point to be transmitted across determines
For first flow entry;
Flow entry acquiring unit, for obtaining first flow entry.
Based on the feasible embodiment of the first of the third aspect or the third aspect, second in the third aspect is feasible
In embodiment, further includes:
It is synchronous to start message transmission module, for first flow entry to be sent to institute in the flow entry sending module
Before stating interchanger, synchronous beginning message is sent to the interchanger, the synchronous message that starts is for notifying the interchanger
The controller starts to send first flow entry;
Synchronous end message sending module, for first flow entry to be sent to institute in the flow entry sending module
After stating interchanger, synchronous end message is sent to the interchanger, the synchronous end message is for notifying the interchanger
The controller terminates to send first flow entry.
Second based on the feasible embodiment of the first of the third aspect or the third aspect or the third aspect feasible
Embodiment, in the third feasible embodiment of the third aspect, further includes:
First mark module, for first flow entry to be sent to the interchanger in the flow entry sending module
Before, to the first flow entry setting flag, the label is used to indicate first flow entry is asked by the interchanger
The flow entry for step of seeking common ground.
Fourth aspect present invention provides a kind of interchanger, it may include:
Message transmission module, for sending synchronization request message to controller, the synchronization request message is the exchange
The first flow entry on the controller is synchronized to the message on the interchanger by machine request, and first flow entry is described
The flow entry that controller is sent before receiving the synchronization request message to the interchanger;
Flow entry receiving module, first flow entry sent for receiving the controller.
It is taken in the synchronization request message in the first feasible embodiment of fourth aspect based on fourth aspect
Band first time point, the first time point are used to indicate the controller for the controller before the first time point to institute
The flow entry for stating interchanger transmission is determined as first flow entry.
Based on the feasible embodiment of the first of fourth aspect or fourth aspect, second in fourth aspect is feasible
In embodiment, the message transmission module includes:
Flow entry verification unit, for testing to stored flow entry;
Message sending unit, for sending the synchronization request message to the controller according to inspection result.
Second of feasible embodiment based on fourth aspect, in the third feasible embodiment of fourth aspect
In, the message sending unit includes:
Message transmission sub-unit, for when examine to the stored flow entry sequence number it is discontinuous or it is described
When the flow entry of storage is lost, the synchronization request message is sent to the controller.
Second based on the feasible embodiment of the first of fourth aspect or fourth aspect or fourth aspect feasible
The feasible embodiment of the third of embodiment or fourth aspect, in the 4th kind of feasible embodiment of fourth aspect,
The interchanger further include:
It is synchronous to start message reception module, disappear for sending synchronization request to the controller in the message transmission module
After breath and before the flow entry receiving module receives first flow entry that the controller issues, receives and synchronize
Start message, the synchronous message that starts is for notifying controller described in the interchanger to start to send first flow entry;
Synchronous end message receiving module, for being received described in the controller issues in the flow entry receiving module
After first flow entry, synchronous end message is received, the synchronous end message is for notifying controller described in the interchanger
Terminate to send first flow entry;
Second mark module, for starting message with the synchronous end message to first flow table according to the synchronization
Item setting flag, the label, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.
Second based on the feasible embodiment of the first of fourth aspect or fourth aspect or fourth aspect feasible
4th kind of feasible embodiment of the feasible embodiment of the third of embodiment or fourth aspect or fourth aspect,
In 5th kind of feasible embodiment of four aspects, first flow entry carries label, and the label is used to indicate described the
One flow entry is requested synchronous flow entry by the interchanger.
Fifth aspect present invention provides a kind of data processing system, including controller as described in the third aspect of the present invention
With interchanger described in fourth aspect present invention.
The implementation of the embodiments of the present invention has the following beneficial effects: controller requests synchronous flow entry by desampler
Synchronization request message, the flow entry requested is retransmitted to interchanger, to realize between controller and interchanger
Flow entry it is synchronous, avoid causing the flow entry between controller and interchanger nonsynchronous existing because interchanger loses flow entry
As increasing the automatic error correction function in data transmission procedure, improving the safety of network equipment information interaction.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of invention for those of ordinary skill in the art without creative efforts, can be with
It obtains other drawings based on these drawings.
Fig. 1 is a kind of flow diagram of data processing method provided in an embodiment of the present invention;
Fig. 2 is the flow diagram of another data processing method provided in an embodiment of the present invention;
Fig. 3 is the flow diagram of another data processing method provided in an embodiment of the present invention;
Fig. 4 is the flow diagram of another data processing method provided in an embodiment of the present invention;
Fig. 5 is a kind of structural schematic diagram of controller provided in an embodiment of the present invention;
Fig. 6 is that the flow entry of the embodiment of the present invention obtains the structural schematic diagram of module;
Fig. 7 is a kind of structural schematic diagram of interchanger provided in an embodiment of the present invention;
Fig. 8 is the structural schematic diagram of the message transmission module of the embodiment of the present invention;
Fig. 9 is the structural schematic diagram of the message sending unit of the embodiment of the present invention;
Figure 10 is a kind of structural schematic diagram of data processing equipment provided in an embodiment of the present invention;
Figure 11 is the structural schematic diagram of another data processing equipment provided in an embodiment of the present invention.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, it is obtained by those of ordinary skill in the art without making creative efforts every other
Embodiment shall fall within the protection scope of the present invention.
Data processing method provided in an embodiment of the present invention is mainly used in OpenFlow network environment, OpenFlow net
Network is mainly made of interchanger, controller and network virtual layer FlowVisor.Wherein, after interchanger receives data packet, first
In the port that local flow stream searching can forward, if data packet is transmitted to controller, is determined by controller without appropriate ports
Surely port is forwarded.Controller issues flow entry to interchanger by OpenFlow agreement, and interchanger is to OpenFlow protocol massages
After carrying out dissection process, the forward-path of data packet is obtained by the flow entry received, thereby determines that target port.
It referring to Figure 1, is a kind of flow diagram of data processing method provided in an embodiment of the present invention.The present embodiment from
The detailed process of controller side elaboration data processing method;The method may include following steps S101- step S103.
S101, controller receive synchronization request message, and the synchronization request message is that interchanger is requested the controller
On the first flow entry be synchronized to the message on the interchanger, first flow entry be the controller receive it is described
The flow entry sent before synchronization request message to the interchanger.
It should be noted that interchanger includes flow table, exit passageway and OpenFlow agreement, wherein exit passageway is to connect
The interface of interchanger and controller is connect, controller passes through this Interface Controller and management interchanger.Controller passes through exit passageway
Receive the synchronization request message from interchanger.OpenFlow agreement is for describing between controller and interchanger used in interaction
The standard and controller of information and the interface standard of interchanger.Synchronization request message is that interchanger detects the synchronous stream of needs
The request message sent when list item to controller, OpenFlow agreement need to be expanded by sending and receiving synchronization request message
Exhibition, for example the structure of synchronization request message is as follows:
Wherein, the ofp_header.ofp_type on OpenFlow protocol message head indicates that the type of message, value are
OFPT_FLOW_SMOOTH_REQUEST receives exchange when controller receives OFPT_FLOW_SMOOTH_REQUEST message
The request of the synchronous flow entry of machine.Specific title involved in the above citing is merely illustrative.
For example, controller can will receive the flow entry received before synchronization request message and be determined as interchanger institute
Request the first synchronous flow entry, it is therefore intended that: interchanger is received to synchronize and be asked after sending synchronization request message to controller
It asks in this period before message, if other occurs again in interchanger one end needs synchronous flow entry, without sending out again
Synchronization request message is sent, because the first flow entry that controller retransmits has contained controller and received synchronization request message
All (including newest) historical datas stored before.Again for example, controller will be before receiving synchronization request message
A part of flow entry in all flow entrys sent to interchanger, which is determined as interchanger, requests the first synchronous flow entry.
S102, controller obtain the first flow entry according to synchronization request message;
Controller determines that the flow entry before receiving synchronization request message is that interchanger request is handed over according to synchronization request message
The first flow entry changed obtains the first flow entry, and according to OpenFlow agreement carries out packing processing (there may be multiple data
Packet).
First flow entry is sent to interchanger by S103, controller.
The first flow entry after controller will acquire and be packaged by exit passageway is sent to interchanger, and interchanger connects again
Flow entry is received, realizes that controller is synchronous with the flow entry of interchanger with this.
Through the embodiment of the present invention, controller requests the synchronization request message of synchronous flow entry by desampler, will
Its flow entry requested is retransmitted to interchanger, so that the flow entry realized between controller and interchanger is synchronous, is avoided
The nonsynchronous phenomenon of the flow entry between controller and interchanger is caused because interchanger loses flow entry, increases data transmission
Automatic error correction function in the process improves the safety of network equipment information interaction.
Fig. 2 is referred to, for the embodiment of the invention provides the flow diagrams of another data processing method.The present embodiment
The detailed process of data processing method is illustrated from controller side;The method may include following steps S201- step S208.
S201, controller receive synchronization request message, and the synchronization request message is that interchanger is requested the controller
On the first flow entry be synchronized to the message on the interchanger, first flow entry be the controller receive it is described
The flow entry sent before synchronization request message to the interchanger.
It is specific to execute method, it please refers to and is described in the step S101 in embodiment shown in FIG. 1, details are not described herein.
After controller receives synchronization request message, controller obtains the first flow entry according to synchronization request message, specifically,
It may include step S202- step S203.
S202, controller parse synchronization request message, obtain the first time point.
It should be noted that first time point is carried in synchronization request message, when controller is received from interchanger
When synchronization request message, dissection process is carried out to the message for carrying the synchronization request message, obtains the first time entrained by it
Point.For example, when the time point that first time point can be defined as interchanger sending synchronization request message elapses forward some
Between section time point.
Controller before first time point is determined as the first flow table to the flow entry that the interchanger is sent by S203, controller
?.
After controller obtains first time point, the flow entry that controller before first time point has been transmitted across is determined as first
Flow entry.
In the embodiment shown in Figure 2, by obtaining first time point in synchronization request message, be equivalent to provided with when
Between dimension filter condition.For example, in addition to carrying first time point in synchronization request message, when can also carry another
Between point, to indicate that the filter condition of time dimension, i.e., will be another for " after another time point to first time point before "
Controller is determined as the first flow entry to the flow entry that the interchanger is sent after a time point and before first time point.It illustrates again
For, the filter condition of the time dimension in synchronization request message can also include multiple discontinuous time intervals.In addition to when
Between dimension filter out condition, the filter condition of other dimensions can also be carried in the synchronization request message that interchanger is sent, such as
Need synchronous flow entry is specifically identified (such as flow entry sequence number), and controller determines corresponding flow entry according to the mark
For the first flow entry.
In the present embodiment, it by the way that filter condition is arranged in synchronization request message, thus can avoid sending without synchronizing
Flow entry, save to the resource occupation of exit passageway and reduce the data processing load of controller, interchanger.
S204, controller obtain the first flow entry.
Specifically, controller obtains the first flow entry determined according to first time point, i.e., controlled before acquisition first time point
The flow entry that device processed has been transmitted across, and all flow entrys are packaged, preparation is sent to interchanger again.
S205, controller send synchronous beginning message to interchanger, and the synchronous message that starts is for notifying exchange control unit
Start to send the first flow entry.
Before flow entry is sent to interchanger by controller, synchronous beginning message also is sent to interchanger, synchronizes and starts to disappear
Breath is for notifying exchange control unit to start to send the first flow entry.Specifically, to realize the synchronous transmission for starting message with
It receives, OpenFlow agreement need to be equally extended, specifically, the synchronous structure for starting message is as follows:
Wherein, the ofp_header.ofp_type on OpenFlow protocol message head indicates that the type of message, value are
OFPT_FLOW_SMOOTH_START is indicated when controller sends OFPT_FLOW_SMOOTH_START message to interchanger
Start to send the requested flow entry of interchanger.
S206, for controller to the first flow entry setting flag, it is the interchanger which, which is used to indicate the first flow entry,
Request synchronous flow entry.
It should be noted that controller, to flow entry setting flag, which is used to indicate labeled flow entry to hand over
It changes planes and requests synchronous flow entry, that is, indicate that these flow entrys are that controller is newest and issue, and for no same in interchanger
The flow entry of step mark, interchanger then can be deleted preferentially.In other embodiments, it is had sent due to controller to interchanger
Synchronization starts message, therefore in interchanger side, can also be by interchanger to the stream received after message receiving synchronization
List item setting flag is issued with indicating that these flow entrys are that controller is newest, without marking flow entry by controller, that is, is controlled
Device processed does not need to execute S206, and for not having the flow entry of sync mark in interchanger, interchanger then can be deleted preferentially.
First flow entry is sent to the interchanger by S207, controller.
Specifically, the first flow entry after controller will acquire and be packaged by exit passageway is sent to interchanger, exchange
Machine receives flow entry again, realizes that controller is synchronous with the flow entry of interchanger with this.
S208, controller send synchronous end message to interchanger, and the synchronous end message is for notifying the exchange
Controller described in machine terminates to send the synchronous flow entry of request.
After flow entry is sent by controller, synchronous end message is sent to interchanger, synchronous end message is for leading to
Bosom friend's exchange controller terminates to send the synchronous flow entry of request.To realize sending and receiving for synchronous end message, equally
OpenFlow agreement need to be extended, specifically, the structure of synchronous end message is as follows:
Wherein, the ofp_header.ofp_type on OpenFlow protocol message head indicates that the type of message, value are
OFPT_FLOW_SMOOTH_FINISH, when controller sends OFPT_FLOW_SMOOTH_FINISH message to interchanger, table
Show that the requested flow entry of interchanger has been sent.
Through the embodiment of the present invention, controller requests the synchronization request message of synchronous flow entry by desampler, will
Its flow entry requested is retransmitted to interchanger, so that the flow entry realized between controller and interchanger is synchronous, is avoided
The nonsynchronous phenomenon of the flow entry between controller and interchanger is caused because interchanger loses flow entry, increases data transmission
Automatic error correction function in the process improves the safety of network equipment information interaction.
Fig. 3 is referred to, is the flow diagram of another data processing method provided in an embodiment of the present invention.The present embodiment
The detailed process of data processing method is illustrated from interchanger side;The method may include following steps S301- step S302.
S301, interchanger send synchronization request message to controller, and the synchronization request message is interchanger request
The first flow entry on the controller is synchronized to the message on the interchanger, first flow entry is the controller
The flow entry sent before receiving the synchronization request message to the interchanger.
For example, when interchanger detects that the flow entry being locally stored needs synchronous (such as flow entry sequence number is discontinuous)
When, controller is needed to re-issue flow entry for interchanger so that flow entry between the two is synchronous, by exit passageway to control
Device processed sends synchronization request message.Synchronization request message is that interchanger is detected and sent out when needing synchronous flow entry to controller
The request message sent, OpenFlow agreement need to be extended by sending and receiving synchronization request message, the tool of synchronization request message
Body is realized to be described in the step S101 please referred in embodiment shown in FIG. 1, and details are not described herein.
For example, controller can will receive the flow entry received before synchronization request message and be determined as interchanger institute
Request the first synchronous flow entry, it is therefore intended that: interchanger is received to synchronize and be asked after sending synchronization request message to controller
It asks in this period before message, if other occurs again in interchanger one end needs synchronous flow entry, without sending out again
Synchronization request message is sent, because the first flow entry that controller retransmits has contained controller and received synchronization request message
All (including newest) historical datas stored before.Again for example, controller will be before receiving synchronization request message
A part of flow entry in all flow entrys sent to interchanger, which is determined as interchanger, requests the first synchronous flow entry.
S302, interchanger receive the first flow entry that controller is sent.
Interchanger receives the flow entry that controller is repacked and issued, and it is synchronous to complete flow entry.
Fig. 4 is referred to, is the flow diagram of another data processing method provided in an embodiment of the present invention.The present embodiment
The detailed process of data processing method is illustrated from interchanger side;The method may include following steps S401- step S407.
S401, interchanger test to stored flow entry
Interchanger tests to locally stored flow entry, in some embodiment of the invention, can be to each flow table
The corresponding sequence number of item is tested, specifically, can test to the sequence number continuity to flow entry.
S402 sends synchronization request message to controller according to inspection result.
Specifically, when examining the sequence number for arriving stored flow entry discontinuous or stored flow entry is lost,
Synchronization request message is sent to controller.
It should be noted that situations such as causing the flow entry sequence number of interchanger storage inside discontinuous or flow entry loss
The reason of be generally placed upon, when interchanger is restarted flow entry all lose, or due in interchanger inter-process OpenFlow assist
The process for discussing message and FES(Forward EntryService for handling flow entry) process is inconsistent, interprocess communication
It may there is a situation where data packetloss.
When interchanger detects that the flow entry serial number that is locally stored is discontinuous, interchanger needs controller to re-issue stream
List item sends synchronization request message, synchronization request to controller by exit passageway so that flow entry between the two is synchronous
Message is the message that interchanger requests synchronous flow entry.Synchronization request message is that interchanger detects when needing synchronous flow entry
The request message sent to controller is waited, OpenFlow agreement need to be extended by sending and receiving synchronization request message, synchronous
The specific implementation of request message please refers to be described in the step S101 in embodiment shown in FIG. 1, and details are not described herein.
In some embodiment of the invention, first time point is carried in synchronization request message, first time point is used to indicate
The controller before the first time point is determined as described first to the flow entry that the interchanger is sent by the controller
Flow entry.For example, the time point that first time point can be defined as interchanger sending synchronization request message elapses forward certain
The time point of a period.
S403, interchanger receive the synchronous beginning message that controller is sent, and the synchronous message that starts is for notifying interchanger institute
Controller is stated to start to send the first flow entry.
It should be noted that the synchronous message that starts is to be extended rear controller to OpenFlow agreement to send to interchanger
Message, which is used to that exchange control unit to be notified to start to send the synchronous flow entry of request.The synchronous structure for starting message
It is as follows:
S404, interchanger receive the first flow entry that controller is sent.
Specifically, interchanger receives the first flow entry that controller is repacked and issued by exit passageway.
S405, interchanger receive the synchronization end message that controller is sent, and synchronous end message is for notifying interchanger control
Device processed terminates to send flow entry.
It should be noted that synchronous end message is to be extended rear controller to OpenFlow agreement to send to interchanger
Message, the message for notify exchange control unit terminate send flow entry.The structure of synchronous end message is as follows:
Wherein, the ofp_header.ofp_type on OpenFlow protocol message head indicates that the type of message, value are
OFPT_FLOW_SMOOTH_FINISH, when controller sends OFPT_FLOW_SMOOTH_FINISH message to interchanger, table
Show that the requested flow entry of interchanger has been sent.
Further, interchanger can according to synchronous message and the synchronous end message of starting to the first flow entry setting flag,
Label, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.
In some embodiment of the invention, the synchronous message that starts carried for the second time point, and the second time point connect for interchanger
The synchronous time point for starting message is received, synchronous end message carries third time point, and third time point receives for interchanger
The time point of synchronous end message.Interchanger can during receiving the first flow entry, to after the second time point and
The first flow entry received before third time point setting flag one by one, is issued with indicating that these flow entrys are that controller is newest
, for distinguishing the flow entry locally probably already existed and again received flow entry.For there is no sync mark in interchanger
Flow entry, interchanger can be deleted preferentially.
Certainly, in other embodiments, interchanger can save the second time point and third time point, receive
Not to the first flow entry setting flag during first flow entry, and after the first flow entry receives, just according to preservation
The second time point and third time point to the first flow entry received in the two time points carry out batch sync mark.
In some embodiment of the invention, the first flow entry that controller is sent carries label, and label is used to indicate described
First flow entry is requested synchronous flow entry by the interchanger, i.e. controller synchronizes label to the first flow entry,
Therefore interchanger is not necessarily to oneself setting flag you can learn that the first flow entry is its requested flow entry.
Through the embodiment of the present invention, controller requests the synchronization request message of synchronous flow entry by desampler, will
Its flow entry requested is retransmitted to interchanger, so that the flow entry realized between controller and interchanger is synchronous, is avoided
The nonsynchronous phenomenon of the flow entry between controller and interchanger is caused because interchanger loses flow entry, increases data transmission
Automatic error correction function in the process improves the safety of network equipment information interaction.
It is a kind of structural schematic diagram of controller provided in an embodiment of the present invention, including message sink please also refer to Fig. 5
Module 51, flow entry obtain module 52, flow entry sending module 53, synchronous beginning message transmission module 54, synchronous end message
Sending module 55 and the first mark module 56, each module routine are specific as follows.
Message reception module 51, for receiving synchronization request message, the synchronization request message is requested for interchanger by institute
The message that the first flow entry on controller is synchronized on the interchanger is stated, first flow entry is that the controller is connecing
Receive the flow entry sent before the synchronization request message to the interchanger.
It should be noted that interchanger includes flow table, exit passageway and OpenFlow agreement, wherein exit passageway is to connect
The interface of interchanger and controller is connect, the message reception module 51 of controller is by this Interface Controller and management interchanger, i.e.,
It ceases receiving module 51 and the synchronization request message from interchanger is received by exit passageway.OpenFlow agreement is used to describe to control
The interaction standard of information used and the interface standard of controller and interchanger between device and interchanger.Synchronization request message is
The request message that interchanger, which detects, to be sent to controller when need synchronous flow entry, to complete synchronization request message
It sends and receives, OpenFlow agreement need to be extended, specifically, the structure of synchronization request message is as follows:
Wherein, the ofp_header.ofp_type on OpenFlow protocol message head indicates that the type of message, value are
OFPT_FLOW_SMOOTH_REQUEST receives exchange when controller receives OFPT_FLOW_SMOOTH_REQUEST message
The request of the synchronous flow entry of machine.
Fig. 6 is referred to, is that the flow entry of the embodiment of the present invention obtains the structural schematic diagram of module 52, flow entry obtains module
52 for obtaining first flow entry according to the synchronization request message;Specifically, it includes parsing that flow entry, which obtains module 52,
Unit 521, flow entry determination unit 522 and flow entry acquiring unit 523.
Wherein, resolution unit 521 obtain first time point for parsing synchronization request message.
It should be noted that carrying first time point in synchronization request message, come from when message reception module 51 receives
When the synchronization request message of interchanger, 521 pairs of the resolution unit messages for carrying the synchronization request message carry out dissection process, obtain
First time point entrained by it.For example, first time point can be defined as interchanger issue synchronization request message when
Between put the time point for elapsing some period forward.
Wherein, flow entry determination unit 522, the flow table for the controller before the first time point to be transmitted across
Item is determined as the first flow entry.
It should be noted that flow entry determination unit 522 will at the first time after resolution unit 521 obtains first time point
The flow entry that controller has been transmitted across before point is determined as the first flow entry.
Implement, by the first time point in synchronization request message, to be equivalent to provided with the time in embodiment in the present invention
The filter condition of dimension.For example, another time can also be carried in addition to carrying first time point in synchronization request message
Point, to indicate the filter condition of time dimension for " after another time point to first time point before ", i.e., by another
Controller is determined as the first flow entry to the flow entry that the interchanger is sent after time point and before first time point.Citing comes again
It says, the filter condition of the time dimension in synchronization request message, can also include multiple discontinuous time intervals.In addition to the time
Dimension filters out condition, and the filter condition of other dimensions can also be carried in the synchronization request message that interchanger is sent, if you need to
The flow entry to be synchronized is specifically identified (such as flow entry sequence number), and controller determines that corresponding flow entry is according to the mark
First flow entry.
In the present embodiment, it by the way that filter condition is arranged in synchronization request message, thus can avoid sending without synchronizing
Flow entry, save to the resource occupation of exit passageway and reduce the data processing load of controller, interchanger.
Wherein, flow entry acquiring unit 523, for obtaining first flow entry.
Specifically, flow entry acquiring unit 523 obtains the first flow entry determined according to first time point, that is, obtain first
The flow entry that controller has been transmitted across before time point, and all flow entrys are packaged, preparation is sent to interchanger again.
Flow entry sending module 53, for the first flow entry to be sent to the interchanger.
Specifically, the first flow entry after flow entry sending module 53 will acquire and be packaged by exit passageway is sent to friendship
It changes planes, interchanger receives flow entry again, realizes that controller is synchronous with the flow entry of interchanger with this.
It is synchronous to start message transmission module 54, for first flow entry to be sent out in the flow entry sending module 523
Before giving the interchanger, synchronous beginning message is sent to interchanger, the synchronous message that starts is for notifying the exchange
Controller described in machine starts to send the first flow entry.
It should be noted that before flow entry is sent to interchanger by flow entry sending module 53, it is synchronous to start message
Sending module 54 also sends synchronous beginning message to interchanger, and the synchronous message that starts is for notifying exchange control unit to start to send
First flow entry.Specifically, need to equally expand OpenFlow agreement to realize sending and receiving for synchronous beginning message
Exhibition, specifically, the synchronous structure for starting message is as follows:
Wherein, the ofp_header.ofp_type on OpenFlow protocol message head indicates that the type of message, value are
OFPT_FLOW_SMOOTH_START is indicated when controller sends OFPT_FLOW_SMOOTH_START message to interchanger
Start to send the requested flow entry of interchanger.
Synchronous end message sending module 55, for sending out first flow entry in the flow entry sending module 523
After giving the interchanger, synchronous end message is sent to interchanger, the synchronous end message is for notifying the exchange
Controller described in machine terminates to send the first flow entry.
It should be noted that after flow entry is sent by flow entry sending module 53, synchronous end message sending module
55 synchronize end message to interchanger transmission, and synchronous end message is used to notify exchange control unit terminates to send to request synchronization
Flow entry.Sending and receiving for end message is synchronized to realize, OpenFlow agreement need to be equally extended, specifically,
The structure of synchronous end message is as follows:
Wherein, the ofp_header.ofp_type on OpenFlow protocol message head indicates that the type of message, value are
OFPT_FLOW_SMOOTH_FINISH, when controller sends OFPT_FLOW_SMOOTH_FINISH message to interchanger, table
Show that the requested flow entry of interchanger has been sent.
First mark module 56, it is described for being sent to first flow entry in the flow entry sending module 523
Before interchanger, to the first flow entry setting flag, it is that interchanger request is same that the label, which is used to indicate the first flow entry,
The flow entry of step.
It should be noted that before flow entry is sent to interchanger by flow entry sending module 53, the first mark module
56 can also be used to indicate labeled flow entry to the flow entry setting flag that will be sent, the label synchronizes for interchanger request
Flow entry, that is, indicate that these flow entrys are that controller is newest and issue, and for there is no the flow table of sync mark in interchanger
, interchanger then can be deleted preferentially.In other embodiments, it has sent to synchronize to interchanger due to controller and starts to disappear
Breath, therefore in interchanger side, it can also be by interchanger to the flow entry setting mark received after message receiving synchronization
Note, is issued with indicating that these flow entrys are that controller is newest, without marking flow entry by controller, for not having in interchanger
There is the flow entry of sync mark, interchanger then can be deleted preferentially.
Through the embodiment of the present invention, controller requests the synchronization request message of synchronous flow entry by desampler, will
Its flow entry requested is retransmitted to interchanger, so that the flow entry realized between controller and interchanger is synchronous, is avoided
The nonsynchronous phenomenon of the flow entry between controller and interchanger is caused because interchanger loses flow entry, increases data transmission
Automatic error correction function in the process improves the safety of network equipment information interaction.
Fig. 7 is referred to, is a kind of structural schematic diagram of interchanger provided in an embodiment of the present invention, which includes message
Sending module 61 synchronous starts message reception module 62, flow entry receiving module 63, synchronous end message receiving module 64 and the
Two mark modules 65, each module routine are specific as follows:
Message transmission module 61 is used to send synchronization request message to controller, and the synchronization request message is the exchange
The first flow entry on the controller is synchronized to the message on the interchanger by machine request, and first flow entry is described
The flow entry that controller is sent before receiving the synchronization request message to the interchanger.
It is determined as exchanging it should be noted that controller can will receive the flow entry received before synchronization request message
Machine requests the first synchronous flow entry, it is therefore intended that: interchanger receives together after sending synchronization request message to controller
In this period before step request message, if other occurs again in interchanger one end needs synchronous flow entry, no longer need to
Secondary transmission synchronization request message, because the first flow entry that controller retransmits has contained controller and received synchronization request
All (including newest) historical datas stored before message.
It is the structural schematic diagram of the message transmission module 61 of the embodiment of the present invention specifically, referring to Fig. 8.Message is sent
Module 61 includes flow entry verification unit 611 and message sending unit 612.
Wherein, flow entry verification unit 611 is for testing to stored flow entry.
It should be noted that flow entry verification unit 611 tests to locally stored flow entry, in the present invention one
In a little embodiments, it can test to the corresponding sequence number of each flow entry, specifically, can be to the sequence number to flow entry
Continuity is tested.
Fig. 9 is referred to, is the structural schematic diagram of the message sending unit 612 of the embodiment of the present invention.Message sending unit 612
For sending synchronization request message to controller according to inspection result.Specifically, message sending unit 612 includes that message sends son
Unit 6121.
When examining the sequence number for arriving stored flow entry discontinuous or the stored flow entry is lost, message
Transmission sub-unit 6121 sends synchronization request message to controller.
It should be noted that situations such as causing the flow entry sequence number of interchanger storage inside discontinuous or flow entry loss
The reason of be generally placed upon, when interchanger is restarted flow entry all lose, or due in interchanger inter-process OpenFlow assist
The process for discussing message and FES(Forward Entry Service for handling flow entry) process is inconsistent, interprocess communication
It may there is a situation where data packetloss.
When message transmission sub-unit 6121 detects that the flow entry serial number that is locally stored is discontinuous, interchanger needs to control
Device re-issues flow entry so that flow entry between the two is synchronous, sends synchronization request to controller by exit passageway and disappears
Breath, synchronization request message are the message that interchanger requests synchronous flow entry.Synchronization request message is that interchanger detects that needs are same
Walk flow entry when to controller send request message, send and receive synchronization request message need to OpenFlow agreement into
Row extension, the specific implementation of synchronization request message please refers to be described in the step S101 in embodiment shown in FIG. 1, herein no longer
It repeats.
In some embodiment of the invention, first time point is carried in synchronization request message, first time point is used to indicate
The controller before the first time point is determined as described first to the flow entry that the interchanger is sent by the controller
Flow entry.For example, the time point that first time point can be defined as interchanger sending synchronization request message elapses forward certain
The time point of a period.
It is synchronous to start message reception module 62, it is asked for being synchronized in the message transmission module 61 to controller transmission
It asks after message and before the flow entry receiving module 63 receives first flow entry that the controller issues, connects
The synchronous beginning message that admission controller is sent, the synchronous message that starts is for notifying controller described in the interchanger to start to send out
Send the first flow entry.
It should be noted that the synchronous message that starts is to be extended rear controller to OpenFlow agreement to send to interchanger
Message, which is used to that exchange control unit to be notified to start to send the synchronous flow entry of request.The synchronous structure for starting message
It is as follows:
Flow entry receiving module 63, for receiving the first flow entry of controller transmission.
Specifically, flow entry receiving module 63 receives the first flow entry that controller is packaged and issues by exit passageway.
Synchronous end message receiving module 64, for receiving what the controller issued in the flow entry receiving module 63
After first flow entry, the synchronization end message that controller is sent is received, the synchronous end message is described for notifying
Controller described in interchanger terminates to send first flow entry.
It should be noted that synchronous end message is to be extended rear controller to OpenFlow agreement to send to interchanger
Message, the message for notify exchange control unit terminate send flow entry.The structure of synchronous end message is as follows:
Wherein, the ofp_header.ofp_type on OpenFlow protocol message head indicates that the type of message, value are
OFPT_FLOW_SMOOTH_FINISH, when controller sends OFPT_FLOW_SMOOTH_FINISH message to interchanger, table
Show that the requested flow entry of interchanger has been sent.
Second mark module 65, for starting message with the synchronous end message to described first-class according to the synchronization
List item setting flag, the label, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.?
In the embodiment of the present invention, the synchronous message that starts carried for the second time point, and the second time point received to synchronize for interchanger to be started to disappear
The time point of breath, synchronous end message carry third time point, and third time point is that interchanger receives synchronous end message
Time point.Interchanger can be during receiving the first flow entry, to after the second time point and before third time point
The first flow entry received setting flag one by one, is issued with indicating that these flow entrys are that controller is newest, for distinguishing this
Flow entry that ground probably already exists and again received flow entry.For there is no the flow entry of sync mark, interchanger in interchanger
It can preferentially delete.
Certainly, in other embodiments, interchanger can save the second time point and third time point, receive
Not to the first flow entry setting flag during first flow entry, and after the first flow entry receives, just according to preservation
The second time point and third time point to the first flow entry received in the two time points carry out batch sync mark.
In some embodiment of the invention, the first flow entry that controller is sent carries label, and label is used to indicate described
First flow entry is requested synchronous flow entry by the interchanger, i.e. controller synchronizes label to the first flow entry,
Therefore interchanger is not necessarily to oneself setting flag you can learn that the first flow entry is its requested flow entry.
Through the embodiment of the present invention, controller requests the synchronization request message of synchronous flow entry by desampler, will
Its flow entry requested is retransmitted to interchanger, so that the flow entry realized between controller and interchanger is synchronous, is avoided
The nonsynchronous phenomenon of the flow entry between controller and interchanger is caused because interchanger loses flow entry, increases data transmission
Automatic error correction function in the process improves the safety of network equipment information interaction.
The embodiment of the invention also provides a kind of data processing systems, including such as Fig. 5 to Fig. 7 controller illustrated and such as
The interchanger that Fig. 8 to Figure 10 is illustrated, specific embodiment refer to above-described embodiment, and details are not described herein.
The embodiment of the invention also provides a kind of data processing equipments 7, and as shown in Figure 10, which includes: bus 74,
And it is connected to the processor 71, memory 72 and interface 73 of bus 74, wherein the interface 73 is for sending and receiving message;It should
For storing instruction, which executes the instruction and receives synchronization request message, institute for controlling the interface 73 memory 72
Stating synchronization request message is that interchanger requests the message being synchronized to the first flow entry on the controller on the interchanger,
First flow entry is the flow entry that the controller is sent before receiving the synchronization request message to the interchanger;
The processor 71 executes the instruction and is also used to obtain first flow entry according to the synchronization request message;The processor 71 is held
The row instruction is also used to control the interface 73 and first flow entry is sent to the interchanger.
In embodiments of the present invention, optionally, first time point is carried in the synchronization request message;The processor 71 is held
The row instruction is for obtaining first flow entry according to the synchronization request message, including is used for:
The synchronization request message is parsed, the first time point is obtained;
The first time point front processor 71 is determined as first flow table to the flow entry that the interchanger is sent
?;
Obtain first flow entry.
In embodiments of the present invention, optionally, the instruction is executed for controlling the interface 73 for described the in processor 71
One flow entry is sent to before the interchanger, which executes the instruction and be also used to:
Synchronous beginning message is sent to the interchanger, the synchronous message that starts is for notifying control described in the interchanger
Device processed starts to send first flow entry;
The instruction is executed in processor 71, and first flow entry is sent to the interchanger for controlling the interface 73
Later, which executes the instruction and is also used to:
Synchronous end message is sent to the interchanger, the synchronous end message is for notifying control described in the interchanger
Device processed terminates to send first flow entry.
In embodiments of the present invention, optionally, the instruction is executed for controlling the interface 73 for described the in processor 71
One flow entry is sent to before the interchanger, which executes the instruction and be also used to:
To the first flow entry setting flag, the label is used to indicate first flow entry as the interchanger institute
Request synchronous flow entry.
Therefore, the data processing equipment of the embodiment of the present invention requests the synchronization of synchronous flow entry to be asked by desampler
Message is sought, the flow entry requested is retransmitted to interchanger, to realize between data processing equipment and interchanger
Flow entry is synchronous, avoids causing the flow entry between data processing equipment and interchanger asynchronous because interchanger loses flow entry
The phenomenon that, the automatic error correction function in data transmission procedure is increased, the safety of network equipment information interaction is improved.
The embodiment of the invention also provides another data processing equipments 8, and as shown in figure 11, which includes: bus
84, and it is connected to the processor 81, memory 82 and interface 83 of bus 84, wherein the interface 83 disappears for sending and receiving
Breath;For storing instruction, which executes the instruction and sends together for controlling the interface 83 to controller the memory 82
Request message is walked, the first flow entry on the controller is synchronized to institute for interchanger request by the synchronization request message
State the message on interchanger, first flow entry be the controller before receiving the synchronization request message to the friendship
It changes planes the flow entry of transmission;The processor 81 executes the instruction and is also used to receive first flow table that the controller is sent
?.
In embodiments of the present invention, optionally, first time point, the first time are carried in the synchronization request message
Point is used to indicate the flow entry that the controller sends the controller before the first time point to the interchanger and determines
For first flow entry.
In embodiments of the present invention, optionally, which executes the instruction for controlling the interface 83 to controller
Synchronization request message is sent, including is used for:
It tests to stored flow entry;
The interface 83, which is controlled, according to inspection result sends the synchronization request message to the controller.
In embodiments of the present invention, optionally, which executes the instruction and connects for controlling this according to inspection result
Mouth 83 sends the synchronization request message to the controller, comprising:
When examining the sequence number for arriving the stored flow entry discontinuous or the stored flow entry is lost,
It controls the interface 83 and sends the synchronization request message to the controller.
In embodiments of the present invention, optionally, the instruction is executed for controlling the interface 83 to control in the processor 81
After device transmission synchronization request message and the processor 81 executes the instruction and receives the controller for controlling the interface 83
Before first flow entry sent, it is also used to:
It controls the interface 83 and receives the synchronous beginning message that the controller is sent, the synchronous message that starts is for notifying
Controller described in the interchanger starts to send first flow entry;
The instruction, which is executed, in the processor 81 receives the described first-class of the controller transmission for controlling the interface 83
After list item, it is also used to:
It controls the interface 83 and receives the synchronization end message that the controller is sent, the synchronous end message is for notifying
Controller described in the interchanger terminates to send first flow entry;
According to the synchronous beginning message with the synchronous end message to the first flow entry setting flag, the mark
Note, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.
In embodiments of the present invention, optionally, first flow entry carries label, and the label is used to indicate described the
One flow entry is requested synchronous flow entry by the interchanger.
Therefore, the data processing equipment of the embodiment of the present invention requests the synchronization of synchronous flow entry by sending to controller
Request message, and requested flow entry is obtained, so that the flow entry realized between controller and notebook data processing unit is same
Step avoids causing the flow entry of controller and notebook data processing unit nonsynchronous existing because data processing equipment loses flow entry
As increasing the automatic error correction function in data transmission procedure, improving the safety of network equipment information interaction.
Those of ordinary skill in the art will appreciate that realizing all or part of the process in above-described embodiment method, being can be with
Relevant hardware is instructed to complete by computer program, the program can be stored in a computer-readable storage medium
In, the program is when being executed, it may include such as the process of the embodiment of above-mentioned each method.Wherein, the storage medium can be magnetic
Dish, CD, read-only memory (Read-Only Memory, ROM) or random access memory (Random Access
Memory, RAM) etc..
The above disclosure is only the preferred embodiments of the present invention, cannot limit the right model of the present invention with this certainly
It encloses, therefore equivalent changes made in accordance with the claims of the present invention, is still within the scope of the present invention.
Claims (27)
1. a kind of data processing method characterized by comprising
Controller receives synchronization request message, and the synchronization request message is that interchanger request will be first-class on the controller
List item is synchronized to the message on the interchanger, and first flow entry, which is the controller, to disappear receiving the synchronization request
The flow entry sent before breath to the interchanger;
The controller obtains first flow entry according to the synchronization request message;
First flow entry is sent to the interchanger by the controller.
2. data processing method as described in claim 1, which is characterized in that carried at the first time in the synchronization request message
Point;Correspondingly, the controller obtains first flow entry according to the synchronization request message, comprising:
The controller parses the synchronization request message, obtains the first time point;
The controller before the first time point is determined as described by the controller to the flow entry that the interchanger is sent
First flow entry;
The controller obtains first flow entry.
3. data processing method as described in claim 1, which is characterized in that send out first flow entry in the controller
Before giving the interchanger, further includes:
The controller sends synchronous beginning message to the interchanger, and the synchronous message that starts is for notifying the interchanger
The controller starts to send first flow entry;
After first flow entry is sent to interchanger by the controller, further includes:
The controller sends synchronous end message to the interchanger, and the synchronous end message is for notifying the interchanger
The controller terminates to send first flow entry.
4. data processing method as claimed in claim 2, which is characterized in that send out first flow entry in the controller
Before giving the interchanger, further includes:
The controller sends synchronous beginning message to the interchanger, and the synchronous message that starts is for notifying the interchanger
The controller starts to send first flow entry;
After first flow entry is sent to interchanger by the controller, further includes:
The controller sends synchronous end message to the interchanger, and the synchronous end message is for notifying the interchanger
The controller terminates to send first flow entry.
5. such as data processing method of any of claims 1-4, which is characterized in that in the controller by described the
One flow entry is sent to before the interchanger, further includes:
For the controller to the first flow entry setting flag, it is the friendship that the label, which is used to indicate first flow entry,
It changes planes and requests synchronous flow entry.
6. a kind of data processing method characterized by comprising
Interchanger sends synchronization request message to controller, and the synchronization request message is that the interchanger is requested the control
The first flow entry on device is synchronized to the message on the interchanger, and first flow entry is the controller receiving
State the flow entry sent before synchronization request message to the interchanger;
The interchanger receives first flow entry that the controller is sent.
7. data processing method as claimed in claim 6, which is characterized in that carried at the first time in the synchronization request message
Point, the first time point are used to indicate the controller and send out the controller before the first time point to the interchanger
The flow entry sent is determined as first flow entry.
8. data processing method as claimed in claim 6, which is characterized in that the interchanger sends synchronization request to controller
Message, comprising:
Interchanger tests to stored flow entry;
The synchronization request message is sent to the controller according to inspection result.
9. data processing method as claimed in claim 7, which is characterized in that the interchanger sends synchronization request to controller
Message, comprising:
Interchanger tests to stored flow entry;
The synchronization request message is sent to the controller according to inspection result.
10. data processing method as claimed in claim 8, which is characterized in that it is described according to inspection result to the controller
Send the synchronization request message, comprising:
When examining the sequence number for arriving the stored flow entry discontinuous or the stored flow entry is lost, to institute
It states controller and sends the synchronization request message.
11. data processing method as claimed in claim 9, which is characterized in that it is described according to inspection result to the controller
Send the synchronization request message, comprising:
When examining the sequence number for arriving the stored flow entry discontinuous or the stored flow entry is lost, to institute
It states controller and sends the synchronization request message.
12. the data processing method as described in any one of claim 6-11, which is characterized in that in the interchanger to described
Controller is sent after synchronization request message and the interchanger receive first flow entry that the controller is sent it
Before, further includes:
The interchanger receives the synchronous beginning message that the controller is sent, and the synchronous message that starts is for notifying the friendship
The controller of changing planes starts to send first flow entry;
After first flow entry that the interchanger receives that the controller is sent, further includes:
The interchanger receives the synchronization end message that the controller is sent, and the synchronous end message is for notifying the friendship
The controller of changing planes terminates to send first flow entry;
The interchanger according to synchronous message and the synchronous end message of starting to the first flow entry setting flag,
The label, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.
13. the data processing method as described in any one of claim 6-11, which is characterized in that first flow entry carries
Label, the label, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.
14. a kind of controller characterized by comprising
Message reception module, for receiving synchronization request message, the synchronization request message is that interchanger is requested the control
The first flow entry on device is synchronized to the message on the interchanger, and first flow entry is the controller receiving
State the flow entry sent before synchronization request message to the interchanger;
Flow entry obtains module, for obtaining first flow entry according to the synchronization request message;
Flow entry sending module, for first flow entry to be sent to the interchanger.
15. controller as claimed in claim 14, which is characterized in that carry first time point in the synchronization request message;
The flow entry obtains module
Resolution unit obtains the first time point for parsing the synchronization request message;
Flow entry determination unit, the flow entry for the controller before the first time point to be transmitted across are determined as described
First flow entry;
Flow entry acquiring unit, for obtaining first flow entry.
16. controller as claimed in claim 14, which is characterized in that further include:
It is synchronous to start message transmission module, for first flow entry to be sent to the friendship in the flow entry sending module
Before changing planes, synchronous beginning message is sent to the interchanger, the synchronous message that starts is for notifying described in the interchanger
Controller starts to send first flow entry;
Synchronous end message sending module, for first flow entry to be sent to the friendship in the flow entry sending module
After changing planes, synchronous end message is sent to the interchanger, the synchronous end message is for notifying described in the interchanger
Controller terminates to send first flow entry.
17. controller as claimed in claim 15, which is characterized in that further include:
It is synchronous to start message transmission module, for first flow entry to be sent to the friendship in the flow entry sending module
Before changing planes, synchronous beginning message is sent to the interchanger, the synchronous message that starts is for notifying described in the interchanger
Controller starts to send first flow entry;
Synchronous end message sending module, for first flow entry to be sent to the friendship in the flow entry sending module
After changing planes, synchronous end message is sent to the interchanger, the synchronous end message is for notifying described in the interchanger
Controller terminates to send first flow entry.
18. the controller as described in any one of claim 14-17, which is characterized in that further include:
First mark module, for the flow entry sending module by first flow entry be sent to the interchanger it
Before, to the first flow entry setting flag, the label is used to indicate first flow entry is requested by the interchanger
Synchronous flow entry.
19. a kind of interchanger characterized by comprising
Message transmission module, for sending synchronization request message to controller, the synchronization request message is that the interchanger is asked
Seek the message the first flow entry on the controller being synchronized on the interchanger, first flow entry is the control
The flow entry that device is sent before receiving the synchronization request message to the interchanger;
Flow entry receiving module, first flow entry issued for receiving the controller.
20. interchanger as claimed in claim 19, which is characterized in that first time point is carried in the synchronization request message,
The first time point is used to indicate the controller and sends the controller before the first time point to the interchanger
Flow entry be determined as first flow entry.
21. interchanger as claimed in claim 19, which is characterized in that the message transmission module includes:
Flow entry verification unit, for testing to stored flow entry;
Message sending unit, for sending the synchronization request message to the controller according to inspection result.
22. interchanger as claimed in claim 20, which is characterized in that the message transmission module includes:
Flow entry verification unit, for testing to stored flow entry;
Message sending unit, for sending the synchronization request message to the controller according to inspection result.
23. interchanger as claimed in claim 21, which is characterized in that the message sending unit includes:
Message transmission sub-unit, for when examining the sequence number to the stored flow entry discontinuous or described stored
Flow entry when losing, send the synchronization request message to the controller.
24. interchanger as claimed in claim 22, which is characterized in that the message sending unit includes:
Message transmission sub-unit, for when examining the sequence number to the stored flow entry discontinuous or described stored
Flow entry when losing, send the synchronization request message to the controller.
25. the interchanger as described in any one of claim 19-24, which is characterized in that further include:
It is synchronous to start message reception module, for the message transmission module to the controller send synchronization request message it
Afterwards and before the flow entry receiving module receives first flow entry that the controller issues, reception, which synchronizes, to be started
Message, the synchronous message that starts is for notifying controller described in the interchanger to start to send first flow entry;
Synchronous end message receiving module, for receiving described first that the controller issues in the flow entry receiving module
After flow entry, synchronous end message is received, the synchronous end message is for notifying controller described in the interchanger to terminate
Send first flow entry;
Second mark module, for being set with the synchronous end message to first flow entry according to the synchronous beginning message
Tagging, the label, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.
26. the interchanger as described in any one of claim 19-24, which is characterized in that first flow entry carries label,
The label, which is used to indicate first flow entry, is requested synchronous flow entry by the interchanger.
27. a kind of data processing system, which is characterized in that including such as described in any item controllers of claim 14-18 and such as
The described in any item interchangers of claim 19-26.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310611749.5A CN104683243B (en) | 2013-11-26 | 2013-11-26 | A kind of data processing method, apparatus and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310611749.5A CN104683243B (en) | 2013-11-26 | 2013-11-26 | A kind of data processing method, apparatus and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN104683243A CN104683243A (en) | 2015-06-03 |
CN104683243B true CN104683243B (en) | 2019-02-01 |
Family
ID=53317862
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201310611749.5A Active CN104683243B (en) | 2013-11-26 | 2013-11-26 | A kind of data processing method, apparatus and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN104683243B (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111327437B (en) * | 2018-12-14 | 2023-04-07 | 中国电信股份有限公司 | Flow table processing method, flow table processing device, and SDN network system |
CN110851186B (en) * | 2019-11-08 | 2022-12-16 | 迈普通信技术股份有限公司 | Network equipment restarting method and device, electronic equipment and readable storage medium |
CN113965580A (en) * | 2020-06-29 | 2022-01-21 | 北京字节跳动网络技术有限公司 | Method and device for synchronizing messages |
CN112737948A (en) * | 2020-12-30 | 2021-04-30 | 北京威努特技术有限公司 | Data transmission method and device between VLANs and industrial control firewall equipment |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101741605A (en) * | 2008-11-11 | 2010-06-16 | 华为技术有限公司 | Method, apparatus and system for processing message |
CN102859952A (en) * | 2010-04-19 | 2013-01-02 | 日本电气株式会社 | Switch, and flow table control method |
CN103023826A (en) * | 2012-12-26 | 2013-04-03 | 华中科技大学 | Routing control method for OpenFlow controller |
CN103155497A (en) * | 2010-10-15 | 2013-06-12 | 日本电气株式会社 | Communication system, control device, node, processing rule setting method and program |
WO2013108761A1 (en) * | 2012-01-16 | 2013-07-25 | 日本電気株式会社 | Network system and path information synchronization method |
-
2013
- 2013-11-26 CN CN201310611749.5A patent/CN104683243B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101741605A (en) * | 2008-11-11 | 2010-06-16 | 华为技术有限公司 | Method, apparatus and system for processing message |
CN102859952A (en) * | 2010-04-19 | 2013-01-02 | 日本电气株式会社 | Switch, and flow table control method |
CN103155497A (en) * | 2010-10-15 | 2013-06-12 | 日本电气株式会社 | Communication system, control device, node, processing rule setting method and program |
WO2013108761A1 (en) * | 2012-01-16 | 2013-07-25 | 日本電気株式会社 | Network system and path information synchronization method |
CN103023826A (en) * | 2012-12-26 | 2013-04-03 | 华中科技大学 | Routing control method for OpenFlow controller |
Non-Patent Citations (1)
Title |
---|
openflow-spec-v1.3.2;OPEN NETWORKING FOUNDATION;《https://www.cs.princeton.edu/courses/archive/fall13/cos597E/papers/openflow-spec-v1.3.2.pdf》;20131125;全文 |
Also Published As
Publication number | Publication date |
---|---|
CN104683243A (en) | 2015-06-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN104683243B (en) | A kind of data processing method, apparatus and system | |
KR102214868B1 (en) | Systems and methods for synchronizing nodes of a robotic system | |
CN109218349A (en) | A kind of method and device of management server cluster | |
EP3240244B1 (en) | Controller area network synchronization | |
CN103139157B (en) | A kind of based on the network communication method of socket, Apparatus and system | |
CN105450785B (en) | File transmission method and device | |
CN105591912B (en) | A kind of selection method and device of forward-path | |
KR20120102732A (en) | An apparatus and a method of receiving and storing data packets controlled by a central controller | |
KR101716832B1 (en) | An assembly and a method of receiving and storing data while saving bandwidth by controlling updating of fill levels of queues | |
CN104247354B (en) | Interface arrangement and bus system | |
CN102857354B (en) | Alarm information reporting method, apparatus and system | |
CN103281346A (en) | Disconnection reconnection method, network system and proxy server | |
KR20120113744A (en) | Distributed processing of data frames by mulitiple adapters using time stamping and a central controller | |
JP2012039539A (en) | Communication apparatus, repeating device and communication control method | |
CN104054309A (en) | Device for efficient use of packet buffering and bandwidth resources at the network edge | |
CN109450711A (en) | The choosing method of host node, device, system and storage medium in distributed system | |
JP6322996B2 (en) | Wireless communication apparatus and method, and wireless communication system | |
CN106455042B (en) | A kind of time synchronization between nodes method, wireless sensor network and its node | |
CN108650296A (en) | The means of communication, device and system | |
CN103650401A (en) | Internal communication method for mobile terminal | |
CN114726676A (en) | Method for processing redundant message in CAN bus dual-channel backup | |
CN108462653B (en) | TTE-based rapid protocol control frame sending method | |
CN109088830A (en) | A kind of port status synchronous method and device | |
CN106612307B (en) | A kind of implementation method and device of always online business | |
CN109815258A (en) | A kind of method and device of data processing |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |