CN110166360B - OpenFlow switch-based MPLS-TP APS implementation method and system - Google Patents

Abstract

The invention provides a method and a system for realizing MPLS-TP APS based on an OpenFlow switch, wherein the method comprises the following steps: based on OpenFlow information, extending match items and action fields to support the distribution of MPLS-TP OAM configuration; based on Packet _ in information in OpenFlow information, expanding the _ match field to support the acquisition and reporting of MPLS-TP OAM information; creating an APS-Group of an LSP link level based on PW service, wherein the APS-Group comprises an LSP working link and an LSP protection link; the controller configures and issues MPLS-TP OAM based on an OpenFlow protocol; the exchanger reports the OAM information; and monitoring the LSP link state in the OAM information, and switching the LSP working link and the LSP protection link according to the LSP link state. The invention can carry out link fast switching by deploying MPLS-TP APS in the switch system on the premise of not influencing the original L2VPN service and occupying the original table item, and the link switching delay can be controlled within 50 ms.

Description

OpenFlow switch-based MPLS-TP APS implementation method and system

Technical Field

The invention relates to the technical field of switches, in particular to a method and a system for realizing MPLS-TP APS based on an OpenFlow switch.

Background

The OpenFlow Switch converts the message forwarding process originally controlled by the Switch/router completely into a process completed by an OpenFlow Switch (OpenFlow Switch) and a control server (Controller) together, thereby realizing the separation of data forwarding and routing control. The controller can control the flow table in the OpenFlow switch through the interface operation specified in advance, so that the purpose of controlling data forwarding is achieved.

The OpenFlow switch is a core component of the whole OpenFlow network and mainly manages forwarding of a data layer. The OpenFlowSwitch has a FlowTable, which only forwards according to the flow table, and the generation, maintenance and issue of the FlowTable are realized by an external Controller.

Referring to fig. 1, an MPLS L2VPN (Multiprotocol Label Switching Layer 2 Virtual Private Network) provides a two-Layer VPN service based on an MPLS Network, so that an operator can provide two-Layer VPNs based on different media, such as ATM, FR, VLAN, Ethernet and PPP, on a unified MPLS Network. In short, MPLS L2VPN transparently transports user layer two data across an MPLS network. From the user's perspective, an MPLS network is a two-layer switching network that can establish two-layer connections between different nodes. And the OpenFlow controller issues the L2VPN flow to realize flexible tunnel deployment, and the PW layer has one more layer of MPLS label than the LSP layer.

MPLS-TP Oam can be deployed based on L2vpn, and OAM detection deployment can be performed based on LSP or PW layer; the LSP layer deployment mode is to associate OAM _ session to the service LSP layer, the outer layer of the incoming direction is matched with the label value of the service LSP layer, and the outgoing direction is printed with the same LSP label value as the service; after OAM deployment is finished, detection based on services is started, wherein the detection comprises the steps of detecting the state of a service link through CCM, detecting the time delay of the service link through DM, detecting the packet loss of the service link through LM and the like; once the abnormality (link state abnormality/DM delay too high/packet loss rate too high) is detected, the controller is notified and the administrator is allowed to make a corresponding policy.

In the OpenFlow MPLS-TP system, after OAM is supported, switching delay may be required to be in an ms level in some specific scenarios, and if the switching delay is perceived through OAMm (perceived time ms level) and reported to the controller in a message form, the controller calculates a new path and sends the new path to the switch (message interaction between the series of controllers and the switch is performed through a CPU), the time difference between the two paths is inevitably present, but in a real service deployment scenario, the switching delay is very sensitive, and the link switching delay is required to be completed within 50 ms.

Therefore, in order to solve the above technical problems, it is necessary to provide a method and a system for implementing MPLS-TP APS based on an OpenFlow switch.

Disclosure of Invention

In view of this, the present invention provides a method and a system for implementing MPLS-TP APS based on OpenFlow switch.

In order to achieve the above object, an embodiment of the present invention provides the following technical solutions:

an OpenFlow switch-based MPLS-TP APS implementation method, the method comprising:

based on OpenFlow information, extending match items and action fields to support the distribution of MPLS-TP OAM configuration;

based on Packet _ in information in OpenFlow information, expanding the _ match field to support the acquisition and reporting of MPLS-TP OAM information;

creating an APS-Group of an LSP link level based on PW service, wherein the APS-Group comprises an LSP working link and an LSP protection link;

the controller configures and issues MPLS-TP OAM based on an OpenFlow protocol;

the exchanger reports the OAM information;

and monitoring the LSP link state in the OAM information, and switching the LSP working link and the LSP protection link according to the LSP link state.

As a further improvement of the invention, the "extended match entry, action field" is specifically:

extending the OAM _ session as an OAM configuration parameter subject to a match item;

the OAM _ inlabel is extended to the action field.

As a further improvement of the invention, the OAM _ session adopts a unique ID as the identifier of the OAM _ session

As a further improvement of the present invention, the "extension of _ match field" specifically includes:

the identification value of the in _ port information is set in the of _ match field.

As a further improvement of the present invention, the method further comprises:

and obtaining in _ port information and comparing the in _ port information with the identification value, and if the in _ port information is the same as the identification value, judging that the data in the Packet _ in message is OAM information.

As a further improvement of the present invention, in the method, "monitoring the LSP link state in the OAM information, and switching the LSP working link and the LSP protection link according to the LSP link state" specifically includes:

monitoring the LSP link state through OAM _ session in the OAM information;

in a normal state, reporting an OAM Cycle message to a controller in a fixed period;

when the LSP work link is interrupted, reporting an OAM Event message to a controller, and switching the LSP work link to an LSP protection link by the controller;

and after the LSP working link is recovered, the controller switches the LSP protection link to the LSP working link.

As a further improvement of the present invention, the method further comprises:

and reporting the APS-Group event to the controller through an APS-Group event message.

As a further improvement of the present invention, the OAM Cycle message and the OAM Event message respectively include: version information, message type, event type, session ID related to the corresponding OAM event, OAM message segment length, reserved field, CCM state, DM identification value, LM identification value and reserved field.

As a further improvement of the present invention, the APS-Group event packet includes: version information, message type, event type, Group ID related to corresponding APS-Group, OAM message segment length, reserved field and link state.

Correspondingly, an MPLS-TP APS implementation system based on an OpenFlow switch, the system comprising:

the first expansion unit is used for expanding the match item and the action field to support the distribution of MPLS-TP OAM configuration based on the OpenFlow message;

the second expansion unit is used for expanding the of _ match field to support the acquisition and reporting of MPLS-TP OAM information based on the Packet _ in message in the OpenFlow message;

the LSP deployment unit is used for establishing APS-Group of LSP link level based on PW service, and the APS-Group comprises an LSP working link and an LSP protection link;

the controller is used for configuring and issuing MPLS-TP OAM based on an OpenFlow protocol and receiving OAM information reported by the switch;

the switch is used for receiving the configuration sent by the controller and the report of the OAM information;

and the LSP switching unit is used for monitoring the LSP link state in the OAM information and switching the LSP working link and the LSP protection link according to the LSP link state.

The invention has the following beneficial effects:

the invention can carry out link fast switching by deploying MPLS-TP APS in the switch system on the premise of not influencing the original L2VPN service and occupying the original table item, and the link switching delay can be controlled within 50 ms.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a diagram of a traffic model of MPLS L2VPN in the prior art;

fig. 2 is a specific flowchart of an MPLS-TP OAM implementation method based on an OpenFlow switch according to the present invention;

fig. 3 is a schematic block diagram of an MPLS-TP OAM implementation system based on an OpenFlow switch according to the present invention;

FIG. 4 is a diagram of an OpenFlow-based MPLS-TP service model in the prior art;

fig. 5 is a diagram of an MPLS-TP APS service model based on an OpenFlow switch in an embodiment of the present invention;

fig. 6 is a schematic diagram of an OAM Cycle message in a specific embodiment of the present invention;

fig. 7 is a schematic diagram of an OAM Event packet in an embodiment of the present invention

Fig. 8 is a schematic diagram of an APS-Group event packet in an embodiment of the present invention.

Detailed Description

In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Referring to fig. 2, the present invention discloses a method for implementing MPLS-TP APS based on OpenFlow switch, including:

based on OpenFlow information, extending match items and action fields to support the distribution of MPLS-TP OAM configuration;

based on Packet _ in information in OpenFlow information, expanding the _ match field to support the acquisition and reporting of MPLS-TP OAM information;

creating an APS-Group of an LSP link level based on PW service, wherein the APS-Group comprises an LSP working link and an LSP protection link;

the controller configures and issues MPLS-TP OAM based on an OpenFlow protocol;

the exchanger reports the OAM information;

and monitoring the LSP link state in the OAM information, and switching the LSP working link and the LSP protection link according to the LSP link state.

Referring to fig. 3, the present invention also discloses an MPLS-TP APS implementation system based on an OpenFlow switch, which includes:

the first expansion unit is used for expanding the match item and the action field to support the distribution of MPLS-TP OAM configuration based on the OpenFlow message;

the second expansion unit is used for expanding the of _ match field to support the acquisition and reporting of MPLS-TP OAM information based on the Packet _ in message in the OpenFlow message;

the LSP deployment unit is used for establishing APS-Group of LSP link level based on PW service, and the APS-Group comprises an LSP working link and an LSP protection link;

the controller is used for configuring and issuing MPLS-TP OAM based on an OpenFlow protocol and receiving OAM information reported by the switch;

the switch is used for receiving the configuration sent by the controller and the report of the OAM information;

and the LSP switching unit is used for monitoring the LSP link state in the OAM information and switching the LSP working link and the LSP protection link according to the LSP link state.

The method and the system for realizing the MPLS-TP APS based on the OpenFlow switch are realized based on MPLS-TP OAM, and the MPLS-TP OAM is firstly explained in detail below.

Referring to fig. 4, it is shown that in the prior art, according to an MPLS-TP service model based on OpenFlow, after an L2VPN is successfully deployed in a default condition, a tunnel is already opened, and a service can be forwarded, but at this time, there is no detection mechanism, and when a service link is abnormal or fails, a controller cannot timely sense the service (sensing time is very long).

After service enters equipment at the UNI (user network interface) side of the service layer, different users are distinguished in a certain policy (port/vlan tag/other field) matching mode, corresponding tunnel encapsulation is carried out, and the tunnel encapsulation is forwarded to the NNI side (network node interface); after the encapsulation message is sent to the intermediate device, matching the outer-layer MPLS Label, executing the corresponding outer-layer Label Swap and then continuing to forward; and after the encapsulated message is sent to the last hop, matching the label and decapsulating the encapsulated message to be sent to a user corresponding to the UNI side.

The L2VPN service deployment based on MPLS-TP is concretely as follows:

(1) forward deployment

BeiJing node (Encap side)

The traffic flow table matches ports and vlans (virtual Local Area network), then the out action is to add an inner label of 16 and an outer label of 300 and an outer ethernet header, and exit from the corresponding egress.

P node (Swap side)

The traffic flow table matches the tag 300 and the out action is to strip the 300 tag and then add the 400 tag out of the corresponding egress.

Shanghai node (Decap side)

The service flow table is matched with a 400 label, and then the action is to strip off the label of the layer and continuously check the label of the inner layer;

the traffic flow table matches the 16 tag and the out action is to strip this layer of tags out of the corresponding egress.

(2) Backward deployment

BeiJing node (Decap side)

The traffic flow table matches 401 the tag, then the out action is to strip this layer of tags and then continue with the inner layer tags.

The traffic flow table matches the 17 tag and then the egress action is to drop this layer of tags and exit from the corresponding egress.

P node (Swap side)

The traffic flow table is a match 301 tag and the out action is to strip off the 301 tag and then add 401 a tag out of the corresponding egress.

Shanghai node (Encap side)

The traffic flow table matches the port and vlan and then the out action is to add the inner label of 17 and the outer label of 301 and the outer ethernet header and out the corresponding egress.

The invention deploys MPLS-TP OAM based on L2VPN, and OAM detection deployment can be carried out based on LSP or PW layer.

The LSP layer deployment mode is to associate OAM _ session to the service LSP layer, the outer layer of the incoming direction is matched with the label value of the service LSP layer, and the outgoing direction is marked with the same LSP label value as the service.

And the PW layer deployment mode is to associate the OAM _ session to the service PW layer, after the Label of the LSP layer is peeled by a Label of the matched service LSP layer in the incoming direction, the Label value of the service PW layer is matched, and the PW/LSP Label values identical to the service are sequentially marked in the outgoing direction.

After OAM deployment is finished, detection based on services is started, wherein the detection comprises detection of service link state through CCM, detection of service link delay through DM, detection of service link packet loss through LM and the like. Once the abnormality (link state abnormality/DM delay too high/packet loss rate too high) is detected, the controller is notified and the administrator makes a corresponding policy, all OAM flows have a feature, namely that there is only an OAM _ session field in the match field.

Oam flow table defines that matching an OAM _ session object as the OAM parameter configuration subject, using a unique ID as the identifier of this OAM _ session, and then giving out the action of the flow table, which describes exactly the information needed by this OAM, for example: the configuration of the traffic flow table is consistent with the configuration of the ingress tag, the egress port information, the outer ethernet header information, and the like.

The OAM flow table definition of PW and the OAM flow table definition of LSP are the same rule, only the difference of label quantity.

In this embodiment, L2VPN service deployment based on MPLS-TP OAM is specifically as follows:

one, LSP layer

(1) Forward deployment

BeiJing node (Encap side)

The OAM flow table matches OAM _ session1, then the action out is OAM _ inlabel 401, out-tag 300, configuring the ethernet information and egress information to be consistent with the corresponding traffic flow table.

(2) Backward deployment

Shanghai node (Encap side)

The OAM flow table is taken as matching OAM _ session2, then the action is taken as OAM _ inlabel is 400, out-tag is 301, and ethernet information and egress information are configured to be consistent with the corresponding traffic flow table.

Two, PW layer

(1) Forward deployment

BeiJing node (Encap side)

The OAM flow table matches OAM _ session2, then the action out is OAM _ inlabel is 17, the out memory label is 16, the outer label is 300, and the ethernet information and egress information are configured to be consistent with the corresponding traffic flow table.

(2) Backward deployment

Shanghai node (Encap side)

The OAM flow table matches OAM _ session2, then the action is OAM _ inlabel is 16, the out memory label is 17, the outer label is 301, and the ethernet information and egress information are configured to be consistent with the corresponding service flow table.

In the invention, OAMflow only needs to match OAM _ session field, actions is followed by incoming and outgoing labels. And the decision of LSP and PW depends on whether the push is a one-layer mpls label or a two-layer mpls label after actions.

The "extended match entry, action field" is specifically:

extending the OAM _ session as an OAM configuration parameter subject to a match item;

the OAM _ inlabel is extended to the action field.

Specifically, the match entry in this embodiment is expanded as follows:

the action field is expanded as follows

The "extension of _ match field" is specifically:

the identification value of the in _ port information is set in the of _ match field. And obtaining in _ port information and comparing the in _ port information with the identification value, and if the in _ port information is the same as the identification value, judging that the data in the Packet _ in message is OAM information.

All OAM status messages, whether Cycle messages or Event messages, are extended by Packet _ in messages. A Packet _ in message format is defined according to Openflow, and an of _ match field in the message carries in _ port information, and if the in _ port is 0 xfffffef (a preset identification value), which is a reserved port of the customized Openflow OAM, the data carried in the corresponding Packet _ in message is considered as OAM information.

Of course, the flag value is not limited to 0 xfffffef in other embodiments, and may be set to other values.

The MPLS-TP OAM is realized based on the MPLS-TP OAM, and the detailed description is provided below.

Fig. 5 is a diagram of an MPLS-TP APS service model based on an OpenFlow switch in a specific embodiment of the present invention, where a PW in the service model has two available LSP links, which are a working LSP (LSP working link) and a protection LSP (LSP protection link), and a PW service runs on an APS-Group, and when a failure occurs, the working LSP can be switched to the protection LSP.

In the service model, the L2VPN service deployment based on MPLS-TP is specifically as follows:

(1) forward deployment (from BeiJing PE to Shanghai PE)

BeiJing node (Encap side) — creation Aps-group (LSP)

Adding an LSP APS-Group, wherein the Group _ id is 1, and adding a label 300 when a working LSP is moved, and sending the label from a port 2; when the protection LSP is gone, the label 400 is added and sent out from port 3.

BeiJing node (Encap side) — configuring flow table to encapsulate PW label and point to Aps-group (LSP)

The traffic flow table matches ports and vlans and the out action is to go LSP APS-Group 1.

P node (Swap side)

When processing a message from Beijing to Shanghai on a P node of a working LSP, popping up a label 300 and adding a label 3000;

when processing a packet from Beijing to Shanghai on the P node of protection LSP, pop up the label 400 and add the label 4000.

Shanghai node (Decap side)

When processing the packet of the working LSP, popping up the label 3000, and sending the packet to the user;

when processing the message of protection LSP, popping up label 4000, and sending the message to user.

(2) Back deployment (from Shanghai PE to BeiJing PE)

Shanghai node (Encap side) — creating Aps-group (LSP)

Adding an LSP APS-Group, wherein the Group _ id is 1, and adding a label 301 when a working LSP is moved, and sending the label from a port 2; when the protection LSP is gone, the label 401 is added and transmitted from port 3.

Shanghai node (Encap side) — configuring flow table to encapsulate PW label and point to Aps-group (LSP)

The traffic flow table matches ports and vlans and the outgoing action is to go LSP APS-Group 1.

P node (Swap side)

When processing a message from Beijing to Shanghai on a P node of a working LSP, popping up a label 301, and adding a label 3010;

and processing the message from Beijing to Shanghai on the P node of the protection LSP, popping up a label 401, and adding a label 4010.

BeiJing node (Decap side)

When processing a packet of a working LSP, popping up a label 3010, and sending the packet to a user;

when processing the message of protection LSP, pop up label 4010, and send the message to the user.

Creating APS-Group of LSP link level based on service, after matching user message, firstly marking PW label, then pointing to APS-Group (LSP), after deploying response service, deploying corresponding OAM _ session to monitor Working and Protection LSP state; after OAM deployment is finished, detection based on services is started, and once the fact that Working LSP is abnormal (link state abnormality/DM delay is too high/packet loss rate is too high) is detected, the system switches the link to Protection LSP within 50ms, and service connectivity is guaranteed.

The configuration of the APS-based OAM service is specifically as follows:

beijing node

Configuring an OAM flow table 1, wherein an OAM message fixes a work LSP, and when the OAM message is a message with a label 3010, the OAM _ session state with a local label of 300 is updated; the OAM send message adds a label 300.

Configuring an OAM flow table 2, fixing an OAM message to a protection LSP, and updating the state of an OAM _ session with a local label of 400 when the OAM message received is a message with a label 4010; the OAM send message adds a label 400.

The configured LSP Aps-Group1 is associated with flow table 1 of OAM and flow table 2 of OAM.

Shanghai node (Encap side)

Configuring an OAM flow table 1, wherein an OAM message fixes a work LSP, and when the OAM message is received as a message with a label 3000, the OAM _ session state with a local label 301 is updated; OAM sends a message add tag 301.

Configuring an OAM flow table 1, fixing an OAM message to a protection LSP, and updating the state of an OAM _ session with a local label of 401 when the OAM message is received as a message with a label 4000; OAM sends a message add tag 401.

The configuration LSP Aps-Group1 is associated with OAM flow table 1 and OAM flow table 2.

In order to support MPLS-TP APS, OAM messages reported by a switch to a controller are divided into two categories, one category is that Cycle messages are reported periodically, and the Cycle messages comprise CCM states (whether a link is normal) and APS-Group states (currently working in working/protection); the other type is an interrupt event reporting message, which comprises signal fail (CCM LOC) and APS-Group state switching (working switching or protection switching).

The steps of monitoring the state of the LSP link in the OAM information and switching the LSP working link and the LSP protection link according to the state of the LSP link are as follows:

monitoring the LSP link state through OAM _ session in the OAM information;

in a normal state, reporting an OAM Cycle message to a controller in a fixed period;

when the LSP work link is interrupted, reporting an OAM Event message to a controller, and switching the LSP work link to an LSP protection link by the controller;

after the LSP working link is recovered, the controller switches the LSP protection link to the LSP working link;

and reporting the APS-Group event to the controller through an APS-Group event message.

In the embodiment, the message is expanded as follows:

1. OAM Cycle message

When the OAM _ session is not abnormal, the switch will report the OAM Cycle message periodically to notify the controller about the current link status/link delay/link packet loss rate, and the format of the OAM Cycle message is shown in fig. 6.

2. OAM Event message

When an OAM _ session is abnormal, such as signal fail (CCM LOC), the switch will trigger an interrupt message, and the format of the OAM Event message is shown in fig. 7.

3.APS-Group event message

When ASP-Group reports Cycle event periodically or APS reports interrupt event by switching, the format of APS-Group event message is shown in fig. 8.

The fields in the messages of fig. 6-8 are described as follows:

it should be understood that the format of the above message is only the preferred message format in the present invention, and in other embodiments, the message format may be modified appropriately, and all messages capable of transmitting OAM Cycle, OAM interrupt Event, and APS-Group Event all belong to the protection scope of the present invention.

In this embodiment, an MPLS-TP APS implementation mechanism based on an OpenFlow switch is specifically:

switching from working LSP to protection LSP

1. Normal state link reporting

The OAM Cycle message can be reported to the controller in a fixed period, the reporting period is defaulted to 15 seconds, a user can flexibly set according to an actual scene, and the current link state condition can be reflected in the OAM Cycle message.

Every time an OAM Cycle Packet-in period (default 15 seconds), the switch reports an OAM Cycle message to the controller, and the link state is reflected by CCM status.

2. Link state interruption and reporting

CCM messages are sent in a fixed period (LSP defaults for 3.3ms/PW defaults for 10ms), if CCM messages sent by an opposite end are not received in a period of 3.5 times, a switch triggers a signal fail Event and reports the Event to a controller through an OAM Event message.

3. After the system receives the link interruption message, the chip is immediately started to carry out APS switching, and the LSP APS-Group1 sets that all the traffic does not go to the working LSP any more, and directly goes to the protection LSP.

And 4, reporting the APS-Group event message to the controller at a fixed period, wherein the period reporting period is defaulted to 30 seconds, the user can flexibly set the APS-Group event message according to an actual scene, and the APS-Group event message can show whether the current APs-Group is in working or protection.

Second, switching back from protection LSP to working LSP

1. If the link is interrupted, the CCM continuously receives the CCM messages sent by 3 opposite ends, the link is considered to be recovered, and the reported CCM state is normal.

2. After the system receives the message that the CCM state is normal, the chip is started to carry out APS switching, the LSP APS-Group1 sets all the flow not to go to the protection LSP, and the work LSP is gone again;

and 3, reporting the protection state of the APS-Group processing by the APS-Group event message.

According to the technical scheme, the invention has the following advantages:

the invention can carry out link fast switching by deploying MPLS-TP APS in the switch system on the premise of not influencing the original L2VPN service and occupying the original table item, and the link switching delay can be controlled within 50 ms.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions.

For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, the functionality of the modules may be implemented in the same one or more software and/or hardware implementations in implementing one or more embodiments of the present description.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

As will be appreciated by one skilled in the art, embodiments of one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.

Furthermore, it should be understood that although the present description refers to embodiments, not every embodiment may contain only a single embodiment, and such description is for clarity only, and those skilled in the art should integrate the description, and the embodiments may be combined as appropriate to form other embodiments understood by those skilled in the art.

Claims (8)

1. An OpenFlow switch-based MPLS-TP APS implementation method is characterized by comprising the following steps:

based on the OpenFlow message, the extended match item and the action field are issued by supporting MPLS-TP OAM configuration, and the "extended match item and the action field" specifically are: extending the OAM _ session as an OAM configuration parameter subject to a match item; expanding the OAM _ inlabel to an action field;

based on the Packet _ in message in the OpenFlow message, the extension of _ match field to support the acquisition and reporting of MPLS-TP OAM information is specifically: setting an identification value of in _ port information in the of _ match field;

creating an APS-Group of an LSP link level based on PW service, wherein the APS-Group comprises an LSP working link and an LSP protection link;

the controller configures and issues MPLS-TP OAM based on an OpenFlow protocol;

the exchanger reports the OAM information;

and monitoring the LSP link state in the OAM information, and switching the LSP working link and the LSP protection link according to the LSP link state.

2. The OpenFlow switch-based MPLS-TP APS implementation method of claim 1, wherein the OAM _ session adopts a unique ID as an identifier of the OAM _ session.

3. The OpenFlow switch based MPLS-TP APS implementation method of claim 1, wherein the method further comprises:

and obtaining in _ port information and comparing the in _ port information with the identification value, and if the in _ port information is the same as the identification value, judging that the data in the Packet _ in message is OAM information.

4. The OpenFlow switch-based MPLS-TP APS implementation method according to claim 2, wherein the "monitoring an LSP link state in OAM information, and switching an LSP working link and an LSP protection link according to the LSP link state" specifically includes:

monitoring the LSP link state through OAM _ session in the OAM information;

in a normal state, reporting an OAM Cycle message to a controller in a fixed period;

when the LSP work link is interrupted, reporting an OAM Event message to a controller, and switching the LSP work link to an LSP protection link by the controller;

and after the LSP working link is recovered, the controller switches the LSP protection link to the LSP working link.

5. The OpenFlow switch based MPLS-TP APS implementation method of claim 4, wherein the method further comprises:

and reporting the APS-Group event to the controller through an APS-Group event message.

6. The OpenFlow switch-based MPLS-TP APS implementation method of claim 4, wherein the OAM Cycle message and the OAM Event message respectively comprise: version information, message type, event type, session ID related to the corresponding OAM event, OAM message segment length, reserved field, CCM state, DM identification value, LM identification value and reserved field.

7. The OpenFlow switch-based MPLS-TP APS implementation method of claim 5, wherein the APS-Group event message comprises: version information, message type, event type, Group ID related to corresponding APS-Group, OAM message segment length and reserved field.

8. An MPLS-TP APS implementation system based on an OpenFlow switch, the system comprising:

a first extension unit, configured to extend a match entry and an action field to support MPLS-TP OAM configuration issue based on the OpenFlow message, where the "extended match entry and action field" specifically is: extending the OAM _ session as an OAM configuration parameter subject to a match item; expanding the OAM _ inlabel to an action field;

a second extension unit, configured to extend an of _ match field to support MPLS-TP OAM information acquisition and reporting based on a Packet _ in message in the OpenFlow message, where the "extension of _ match field" specifically is: setting an identification value of in _ port information in the of _ match field;

the LSP deployment unit is used for establishing APS-Group of LSP link level based on PW service, and the APS-Group comprises an LSP working link and an LSP protection link;

the controller is used for configuring and issuing MPLS-TP OAM based on an OpenFlow protocol and receiving OAM information reported by the switch;

the switch is used for receiving the configuration sent by the controller and the report of the OAM information;

and the LSP switching unit is used for monitoring the LSP link state in the OAM information and switching the LSP working link and the LSP protection link according to the LSP link state.

Images