CN102843618A - Method and device for SNCP (Sub-network Connection Protection) in butt joint of ASON (Automatically Switched Optical Network) and traditional network - Google Patents

Abstract

The present invention relates to a method and device for SNCP protection when ASON is connected to a traditional network, including: establishing a first service and a second service related to each other; the first service and the second service only have source nodes or sink nodes in the domain of the ASON network , or neither the source node nor the sink node of the first service and the second service is in the domain of the ASON network; provide SNCP protection for the ASON network according to the first service and the second service related to each other. The present invention enables the ASON network to provide a function similar to 1+1 (path) protection no matter which domain it is in by establishing two interrelated services. At the same time, the two services can have recovery attributes independently, and when a path failure occurs in the ASON domain, dynamic rerouting of the control plane can be realized in the ASON domain, thereby improving the security of the ASON network.

Description

Method and device for SNCP protection when ASON is connected with traditional network

technical field

The present invention relates to the field of intelligent optical networks, in particular to SNCP (Subnetwork Connection Protection, subnetwork connection protection) when a kind of ASON (Automatically Switched Optical Network, Automatically Switched Optical Network) based on SDH (Synchronous Digital Hierarchy, Synchronous Digital System) is docked with a traditional network Protection methods and devices.

Background technique

In general, the survivability of a network refers to the ability of the network to continue to operate normally in the event of a failure. In order to enhance the availability of the transport network and maintain the integrity of existing calls, the ASON network needs to adopt certain protection and recovery mechanisms.

Restoration of an ASON network refers to the replacement of failed connections by rerouting using the idle capacity of the network. The recovery method based on the control plane is mainly dynamic rerouting, and after a fault occurs, a recovery path is established in real time by using signaling.

The protection mechanisms supported by the ASON network can be divided into two types: protection based on the transmission plane and protection based on the control plane. Among them, the protection based on the control plane occurs between the source node and the sink node of the control plane protection domain, and the operation of the protection mechanism is completed through the coordination between the source node and the sink node. The 1+1 end-to-end (path) protection is widely used in the protection based on the control plane.

However, in actual networking, ASON networks may be interconnected with traditional networks, and 1+1 path protection also needs to be provided at this time. As shown in Figure 1a, domain A is an ASON domain, domain B is a traditional SDH/MSTP network, and only the source node is in the ASON domain; or, as shown in Figure 1b, when domain A and domain C are traditional SDH (Synchronous Digital Hierarchy , Synchronous Digital Transmission System)/MSTP (Multi-Service Transfer Platform) network, domain B is ASON network, the source and sink nodes of the business are not in ASON network (domain B); when domain B is traditional When SDH/MSTP network and domain A or domain C is ASON network, only the source (or sink) node is in the ASON domain. Existing solutions cannot realize the 1+1 protection when the ASON network is interconnected with the traditional ones in the above two scenarios at the same time, thus reducing the security of the ASON network.

Contents of the invention

The main purpose of the present invention is to provide a method and device for SNCP protection when ASON is connected with traditional network, aiming at improving the security of ASON network.

In order to achieve the above object, the present invention proposes a method for SNCP protection when an ASON is connected to a traditional network, including:

Establish a first service and a second service that are related to each other; only the source node or the sink node of the first service and the second service is in the domain of the ASON network, or the source node and the sink node of the first service and the second service None of them are in the domain of ASON network;

SNCP protection is provided for the ASON network according to the interrelated first service and the second service.

Preferably, when only the source node or the sink node of the first service and the second service is in the domain of the ASON network, the step of establishing the first service and the second service associated with each other includes:

establishing said first service unprotected;

Selecting the same upper service time slot as the first service, establishing the second service, and assigning it to be associated with the first service.

Preferably, the step of establishing a second service and specifying the association with the first service includes:

establishing the local information of the second service, and storing the associated service identifier of the second service as the first service in the local information of the second service; and obtaining the local information of the first service, and The associated service identifier of the first service stored in the local information of the service is the second service;

fetching the routing information of the first service from the local information of the first service, and initiating a path calculation request;

When the first service and the second service follow strictly unrelated routing policies, complete the establishment of the second service according to the path calculation request; otherwise, the establishment of the second service fails, and the local connection between the first and second services is cancelled. The association relationship saved in the message.

Preferably, said completing the establishment of the second service according to the path calculation request includes:

When the source node issues a cross request, a concurrent priority relationship is formed between the first service and the second service.

Preferably, the step of establishing the second service and specifying that it is associated with the first service further includes: prompting a warning message to the user when the first service and the second service do not follow strictly unrelated routing policies.

Preferably, when neither the source node nor the sink node of the first service and the second service is in the domain of the ASON network, the step of establishing the interrelated first service and the second service includes:

Establish two businesses, respectively as the first business and the second business;

Send the associated commands to the source nodes of the first and second services respectively, and the two services respectively save the other party's service identifier as their own associated service identifier in their respective local information;

Create an information exchange channel between the source nodes of the first and second services to associate the two services;

After the association is successful, an association protection relationship between the two services is established, and the routing information of the first and second services is exchanged between the first and second services through the information exchange channel.

Preferably, the service types of the first service and the second service include at least one of the following: 1+1 SNCP service, MSP service or unprotected service.

Preferably, the method further includes: maintaining routing information of the first and second services.

The present invention also proposes a device for SNCP protection when ASON is connected to a traditional network, including:

An association establishment module, configured to establish a first service and a second service that are associated with each other; only the source node or the sink node of the first service and the second service is in the domain of the ASON network, or the first service and the second service Neither the source node nor the sink node is in the domain of the ASON network;

A protection module, configured to provide SNCP protection for the ASON network according to the interrelated first service and second service.

Preferably, the association establishment module includes:

a first establishing unit, configured to establish the unprotected first service;

The second establishing unit is configured to select the same upper service time slot as that of the first service, establish the second service, and assign it to be associated with the first service.

Preferably, the second establishment unit includes:

A service identification subunit, configured to establish local information of the second service, and store the associated service identifier of the second service in the local information of the second service as the first service; and obtain the local information of the first service , and save the associated service identifier of the first service as the second service in the local information of the first service;

a path calculation subunit, configured to fetch the routing information of the first service from the local information of the first service, and initiate a path calculation request;

The establishment subunit is used to complete the establishment of the second service according to the path calculation request when the first service and the second service follow a strictly unrelated routing strategy; otherwise, the establishment of the second service fails, and the first service is cancelled. , the association relationship stored in the local message of the second service.

Preferably, the establishment subunit is further configured to form a concurrent priority relationship between the first service and the second service when the source node sends a cross request; and when the first service and the second service When the service does not follow the strictly irrelevant routing policy, the user will be prompted with an alarm message.

Preferably, the association establishment module includes:

The third establishing unit is used to establish two services, respectively serving as the first service and the second service;

The sending unit is used to send the associated command to the source nodes of the first and second services respectively, and the two services respectively save the other party's service identifier as their own associated service identifier in their respective local information;

A channel creation unit, configured to create an information exchange channel between the source nodes of the first and second services, and associate the two services;

The fourth establishment unit is configured to establish an association protection relationship between the two services after the association is successful, and exchange routing information between the first and second services through the information exchange channel.

A method and device for SNCP protection when ASON is connected to a traditional network proposed by the present invention, when only the source (or sink) node is not in the ASON domain, when the second service is established, the associated first service can be specified at the same time , so that the two services can share the same up (or down) service time slot to achieve concurrent and optimal reception of channel signals; when the source and sink nodes are not in the ASON domain, the user sets the association for the source nodes of the two services respectively The request method can establish an association relationship without interaction between two nodes to provide SNCP protection. At the same time, an associated service does not follow the routing policy alarm, prompting the user when to adjust the associated service route to provide complete SNCP protection. Therefore, the present invention enables the ASON network to provide a function similar to 1+1 (path) protection no matter which domain it is in by establishing two interrelated services. When a fault occurs outside the ASON domain, switching can occur from the working path to the protection path. At the same time, these two services can have recovery properties independently. When a path failure occurs in the ASON domain, dynamic rerouting of the control plane can be realized in the ASON domain, thereby improving the security of the ASON network.

Description of drawings

Figure 1a is a schematic diagram of the first scenario when the ASON of the present invention is connected to a traditional network;

Figure 1b is a schematic diagram of the second scenario when the ASON of the present invention is connected to a traditional network;

Fig. 2 is a schematic flow chart of an embodiment of a method for SNCP protection when ASON of the present invention is docked with a traditional network;

Fig. 3 is a schematic flow chart of establishing interrelated first business and second business in the first scenario in the first embodiment of the method for SNCP protection when the ASON is connected to the traditional network;

Fig. 4 is a schematic flow diagram of establishing a second service in the first scenario and specifying a process associated with the first service in the first embodiment of the method for SNCP protection when the ASON is connected to a traditional network;

Fig. 5 is a schematic flow diagram of establishing interrelated first services and second services in the second scenario of the first embodiment of the method for SNCP protection when the ASON is connected to the traditional network;

Fig. 6 is a schematic structural diagram of an embodiment of a device for SNCP protection when the ASON of the present invention is docked with a traditional network;

FIG. 7 is a schematic structural diagram of an association establishment module in an embodiment of an SNCP protection device in an embodiment of the present invention when the ASON is connected to a traditional network;

Fig. 8 is a schematic structural diagram of the second establishment unit of the first implementation mode in an embodiment of the device for SNCP protection when the ASON of the present invention is connected to a traditional network;

FIG. 9 is a schematic structural diagram of an association establishing module in a second embodiment of an embodiment of an SNCP protection device when an ASON is connected to a traditional network according to the present invention.

In order to make the technical solution of the present invention clearer and clearer, it will be further described below in conjunction with the accompanying drawings.

Detailed ways

The solution of the embodiment of the present invention is mainly: through the establishment of two interrelated services, the ASON network can provide a function similar to 1+1 (path) protection no matter which domain it is in. At the same time, the two services can have recovery attributes independently. When a path failure occurs in the ASON domain, dynamic rerouting of the control plane can be realized in the ASON domain, improving the security of the ASON network.

As shown in Figure 2, an embodiment of the present invention proposes a method for SNCP protection when an ASON is connected to a traditional network, including:

Step S101, establishing a first business and a second business related to each other;

Wherein, only the source node or the sink node of the first service and the second service is in the domain of the ASON network, or neither the source node nor the sink node of the first service and the second service is in the domain of the ASON network.

Step S102, providing SNCP protection for the ASON network according to the interrelated first service and second service.

In order to realize the SNCP protection when the ASON network is interconnected with the traditional network in two scenarios where neither the source node nor the sink node of the service is in the domain of the ASON network and one of the source node or the sink node is in the domain of the ASON network, this embodiment needs to establish Interrelated first service and second service; providing SNCP protection for the ASON network according to the interrelated first service and second service.

First set up the first business (namely the first business in this embodiment), when only the source (or sink) node is not in the domain of the ASON network, set up the second business (the second business in this embodiment) ), specify the associated first service at the same time, so that the two services can share the same upper (or lower) service time slot, and achieve concurrent and optimal reception of channel signals; when the source and sink nodes are not in the domain of the ASON network, adopt The method in which the user sends an association request to the source nodes of the two services separately, and the association relationship can be established without interaction between the two nodes to provide SNCP protection.

Specifically, as shown in FIG. 3, when only the source node or the sink node of the first service and the second service is in the domain of the ASON network, in the above step S101, the step of establishing the first service and the second service that are mutually associated includes :

Step S1011, establishing an unprotected first service;

Step S1012, select the same upper service time slot as that of the first service, establish the second service, and assign it to be associated with the first service.

As shown in Figure 4, the step of establishing the second service in step S1012 and specifying the steps associated with the first service includes:

Step S10121, establish the local information of the second service, and store the associated service identifier of the second service as the first service in the local information of the second service; and obtain the local information of the first service, and store The associated business identifier of the first business stored in the information is the second business;

Step S10122, fetch the routing information of the first service from the local information of the first service, and initiate a path calculation request;

Step S10123, judging whether the first service and the second service follow a strictly unrelated routing policy, if so, proceed to step S10124; otherwise, proceed to step S10125;

Step S10124, complete the establishment of the second service according to the path calculation request;

Step S10125, if the establishment of the second service fails, the association relationship stored in the local messages of the first and second services is canceled, and a warning message is prompted to the user.

Wherein, completing the establishment of the second service according to the path calculation request includes:

When the source node issues a cross request, a concurrent priority relationship is formed between the first service and the second service.

Taking the scenario where only the source node is not in the domain of the ASON network (hereinafter referred to as the ASON domain) as an example, the process of establishing an association relationship between two services is as follows:

First, establish an unprotected service as the first service, and its route is A-B, and its establishment process is the same as that of ordinary ASON services;

Then, establish the second service, as the second service, select the same upper service time slot of the first service to form the concurrent and superior reception relationship of the channel signal, and designate the first service as the associated service of the second service, and complete the second service The second service is associated with the first service.

Wherein, when establishing the second service, first establish the local information of the second service, store the associated service identifier of the second service as the first service, find the local information of the first service at the same time, save the associated service identifier of the first service as The second service; then take out the route A-B of the first service, initiate a path calculation request, and require the route of the second service and the route A-B of the first service to follow strictly unrelated routing policies (including node-independent, link-independent, and SRLG-independent); Since the source nodes of the two services are the same, the routing information of the first service can be obtained directly through its associated service identifier.

Then, the normal service establishment process is carried out through RSVP (Resource Reservation Protocol) signaling, wherein when the source node issues the crossover, the crossover between the first service and the second service is required to form a concurrent and preferential reception relationship; if the second service fails to be established, Then it is necessary to clear the associated service identifier of the first service, and inform the user that the association fails; if the second service is established successfully, the association is successful.

For the scenario where the sink node is not in the ASON domain, the implementation of the association scheme is the same as above, only need to regard the sink node as the source node and reversely establish services.

As shown in Figure 5, when the source node and the sink node of the first service and the second service are not in the ASON domain, the step of establishing the interrelated first service and the second service in the above step S101 includes:

Step S1013, establishing two services as the first service and the second service respectively;

Step S1014, sending the associated commands to the source nodes of the first and second services respectively, and the two services store the other party's service identifier in their respective local information as their own associated service identifiers;

Step S1015, creating an information exchange channel between the source nodes of the first and second services, and associating the two services;

Step S1016, when the association is successful, establish an association protection relationship between the two services, and exchange routing information between the first and second services through the information exchange channel.

Wherein, the service types of the first service and the second service may be 1+1 SNCP service, MSP service or unprotected service.

For the scenario where the source and sink nodes are not in the ASON domain, first establish two services. The service type can be 1+1SNCP service, MSP (Message Smart Platform, message intelligence platform) service or unprotected service, etc. There is no restriction on the service type. However, it is necessary to ensure that the parameters of the two services, such as cascading, unidirectional and bidirectional, and tunneling or not, are consistent so that one service can provide protection for the other.

Then, associate the two businesses.

The following describes the process of establishing an association relationship between two businesses:

1. Issue association commands for two services, and the business association commands must be sent to the first node (source node) of the two services at the same time;

2. After the two services receive the association command, they respectively save the other party's service ID as their own associated service ID. Specifically, the associated service extracts the identifier of another associated service from the associated command, saves it in the local information of the associated service, and saves it in the database, so that the associated service identifier can be obtained again when the node is restarted. The actions of the two businesses in this process are consistent and performed separately.

3. Check whether there is an information exchange channel between the two services, and if not, create an information exchange channel. In this embodiment, the VIPCC (Virtual Control Channel) created through the LMP (Link Association Protocol) is selected as a channel for information exchange, and the VIPCC is used to send OEM (private data) for information exchange. The specific process of creating a VIPCC can use existing mature technical solutions, which will not be described in detail here. It should be noted that the information exchange channel required by the present invention is not limited to VIPCC.

4. After the association is successful, the two services establish an association protection relationship and send their own routing information to each other. The two interrelated services extract their own initial routing information from the local information, and the initial routing information only includes the working connection of the unprotected and MSP service, and the working and protection connection of the 1+1SNCP service. Then, it is assembled into private data in a certain format and sent to the head node of the associated business through VIPCC. At the same time, the associated service will also receive the data sent by the associated service, parse it into the routing information of the associated service according to the defined format, and store it in the local information of the associated service. In order to reduce the operation of the database, the routing information may not be stored in the database. In case of node restart or power failure, just send routing information again after restart.

In this embodiment, it is also necessary to maintain the routing information of the related business, because the initial routing information of the business is not always the same, and there is a possibility that the information exchange channel may fail, so in certain scenarios, the related business needs to Notify the associated service to update its own routing information.

Specifically, when the initial routing information of the associated service changes due to some maintenance behavior, it needs to send its own routing information to the head node of the associated service. Maintenance behaviors include, but are not limited to, business optimization, recovery of services with no reply attribute, modification of recovery connections to initial connections, etc.

When a node restarts, the associated service restores the local information of the service from the database, and if there is an associated service, it sends its own routing information to the head node of the associated service.

When it is detected that the status of the channel for information exchange changes from invalid to valid, because the routing information of the associated service itself may have changed during the period of time when the channel for information exchange is invalid, it is also necessary to report to the associated service at this time. The first node of the service sends its own routing information.

Since the purpose of associating two services is to provide 1+1 SNCP protection, in terms of routing strategy, the two associated services must be strictly irrelevant, and this strategy is only for the current initial connection of the service. That is to say, for an optimized connection or a recovery connection of a service without a reply attribute, it is necessary to follow a routing strategy that is strictly independent of the current initial connection of the associated service; if it is a service with a reply attribute, its recovery connection can choose to The current initial connection of the associated service follows the routing policy of strict don't care or best effort don't care.

In some scenarios, if the initial connection of two related services does not satisfy the strictly unrelated routing policy, the control plane can report an unrelated routing policy to the user when detecting that the routes of the two related services do not meet the strictly unrelated routing policy. Alerts that meet the routing policy. After receiving the alarm, the user can use optimization commands and other means to adjust the route of the associated service. After satisfying the strictly irrelevant routing policy, the control plane will report that the alarm disappears. The specific implementation method is that when the initial routing information of the associated service itself changes or when the routing information updated by the associated service is received, it is necessary to check the two associated services at this time. Whether the business satisfies the routing policy is strictly irrelevant.

Among them, the situations that may lead to the initial connection of two associated services not satisfying the strictly unrelated routing policy include:

1. The two services associated for the first time do not meet the routing policy, or an optimization command is issued for the two services at the same time, so that they are optimized to the same route and other user misoperations.

2. The recovery action triggered by the control plane. When two associated services fail at the same time, since the recovery of different head nodes avoids only the initial connection of the current associated service, the routing strategy may not be satisfied between the two restored connections (for services with no reply, the restored connection is equal to the working connection) .

Under the 1+1SNCP protection mechanism, the working path and the protection path are required to follow strictly independent routing policies. Therefore, after an association relationship is established, when an associated service performs operations such as recovery, it needs to follow a certain routing policy with the associated service to provide SNCP protection. In the above-mentioned first scenario, since the source nodes are the same, the routing information of the first service can be obtained directly through the service identifier; in the second scenario, the routing information of the associated service is obtained through the information exchange channel when the routing information of the associated service changes sent over. In the second scenario, because the source nodes of the two services are different, the associated routing information may not be updated in time, resulting in the two services not following a strictly unrelated routing policy. At this time, the control plane maintains an associated service that does not follow the route The alert status of the policy.

To sum up, this embodiment can provide a function similar to 1+1 (path) protection no matter which domain the ASON network is in. When a fault occurs outside the ASON domain, switching can occur from the working path to the protection path. At the same time, these two services can have recovery attributes independently, and when a path failure occurs in the ASON domain, dynamic rerouting of the control plane can be realized in the ASON domain.

As shown in FIG. 6, an embodiment of the present invention proposes a device for SNCP protection when ASON is connected to a traditional network, including: an association establishment module 601 and a protection module 602; wherein:

An association establishment module 601, configured to establish a first service and a second service that are associated with each other; only the source node or the sink node of the first service and the second service is in the domain of the ASON network, or the source node of the first service and the second service Neither the node nor the sink node is in the domain of the ASON network.

The protection module 602 is configured to provide SNCP protection for the ASON network according to the interrelated first service and the second service.

In order to realize the SNCP protection when the ASON network is interconnected with the traditional network in two scenarios where neither the source node nor the sink node of the service is in the domain of the ASON network and one of the source node or the sink node is in the domain of the ASON network, this embodiment needs to establish Interrelated first service and second service; providing SNCP protection for the ASON network according to the interrelated first service and second service.

First set up the first business (namely the first business in this embodiment), when only the source (or sink) node is not in the domain of the ASON network, set up the second business (the second business in this embodiment) ), specify the associated first service at the same time, so that the two services can share the same upper (or lower) service time slot, and achieve concurrent and optimal reception of channel signals; when the source and sink nodes are not in the domain of the ASON network, adopt The method in which the user sends an association request to the source nodes of the two services separately, and the association relationship can be established without interaction between the two nodes to provide SNCP protection.

Specifically, as shown in FIG. 7, as a first implementation manner, when only the source node or the sink node of the first service and the second service are in the domain of the ASON network, the association establishment module 601 includes: a first establishment unit 6011 and The second establishment unit 6012, wherein:

The first establishing unit 6011 is configured to establish an unprotected first service;

The second establishing unit 6012 is configured to select the same upper service time slot as that of the first service, establish the second service, and assign it to be associated with the first service.

As shown in Figure 8, the second establishment unit 6012 includes: a service identification subunit 60121, a path calculation subunit 60122, and an establishment subunit 60123, wherein:

The service identifier subunit 60121 is configured to establish the local information of the second service, and save the associated service identifier of the second service as the first service in the local information of the second service; and acquire the local information of the first service. information, and save the associated service identifier of the first service as the second service in the local information of the first service;

The path calculation subunit 60122 is used to extract the routing information of the first service from the local information of the first service, and initiate a path calculation request;

The establishment subunit 60123 is used to complete the establishment of the second service according to the path calculation request when the first service and the second service follow a strictly unrelated routing policy; otherwise, the establishment of the second service fails, and cancel the first and second service The association relationship saved in the local message of the service.

Further, the establishment subunit 60123 is also used to form a concurrent and preferential reception relationship between the first service and the second service when the source node sends a cross request; and when the first service and the second service do not follow a strictly unrelated route When the policy is selected, a warning message is prompted to the user.

In this embodiment, taking the scenario where only the source node is not in the domain of the ASON network (hereinafter referred to as the ASON domain) as an example, the process of establishing an association relationship between two services is as follows:

First, establish an unprotected service as the first service, and its route is A-B, and its establishment process is the same as that of ordinary ASON services;

Then, establish the second service, as the second service, select the same upper service time slot of the first service to form the concurrent and superior reception relationship of the channel signal, and designate the first service as the associated service of the second service, and complete the second service The second service is associated with the first service.

Wherein, when establishing the second service, first establish the local information of the second service, store the associated service identifier of the second service as the first service, find the local information of the first service at the same time, save the associated service identifier of the first service as The second service; then take out the route A-B of the first service, initiate a path calculation request, and require the route of the second service and the route A-B of the first service to follow strictly unrelated routing policies (including node-independent, link-independent, and SRLG-independent); Since the source nodes of the two services are the same, the routing information of the first service can be obtained directly through its associated service identifier.

Then, the normal service establishment process is carried out through RSVP signaling. When the source node issues a crossover, the crossover between the first service and the second service is required to form a concurrent and preferential reception relationship; if the second service fails to be established, the first service needs to be cleared. The associated service identifier of the service, and inform the user that the association fails; if the second service is successfully established, the association is successful.

For the scenario where the sink node is not in the ASON domain, the implementation of the association scheme is the same as above, only need to regard the sink node as the source node and reversely establish services.

As shown in Figure 9, as a second implementation manner, when the source node and the sink node of the first service and the second service are not in the ASON domain, the association establishment module 601 includes: a third establishment unit 6013, a sending unit 6014, The channel creation unit 6015 and the fourth establishment unit 6016, wherein:

The third establishment unit 6013 is used to establish two services, respectively serving as the first service and the second service;

The sending unit 6014 is configured to send the associated command to the head nodes of the first and second services respectively, and the two services respectively save the other party's service identifier as their own associated service identifier in their respective local information;

The channel creation unit 6015 is used to create an information exchange channel between the head nodes of the first and second services, and to associate the two services;

The fourth establishment unit 6016 is configured to establish an association protection relationship between the two services after the association is successful, and exchange routing information between the first and second services through the information exchange channel.

For the scenario where neither the source node nor the sink node is in the ASON domain, first establish two services. The service type can be 1+1SNCP service, MSP service or unprotected service, etc. There is no restriction on the service type. However, it is necessary to ensure that the parameters of the two services, such as cascading, unidirectional and bidirectional, and tunneling or not, are consistent so that one service can provide protection for the other.

Then, associate the two businesses.

The following describes the process of establishing an association relationship between two businesses:

1. Issue association commands for two services, and the business association commands must be sent to the first node (source node) of the two services at the same time;

2. After the two services receive the association command, they respectively save the other party's service ID as their own associated service ID. Specifically, the associated service extracts the identifier of another associated service from the associated command, saves it in the local information of the associated service, and saves it in the database, so that the associated service identifier can be obtained again when the node is restarted. The actions of the two businesses in this process are consistent and performed separately.

3. Check whether there is an information exchange channel between the two services, and if not, create an information exchange channel. In this embodiment, the VIPCC (Virtual Control Channel) created through the LMP (Link Association Protocol) is selected as a channel for information exchange, and the VIPCC is used to send OEM (private data) for information exchange. The specific process of creating a VIPCC can use existing mature technical solutions, which will not be described in detail here. It should be noted that the information exchange channel required by the present invention is not limited to VIPCC.

4. After the association is successful, the two services establish an association protection relationship and send their own routing information to each other. The two interrelated services extract their own initial routing information from the local information, and the initial routing information only includes the working connection of the unprotected and MSP service, and the working and protection connection of the 1+1SNCP service. Then, it is assembled into private data in a certain format and sent to the head node of the associated business through VIPCC. At the same time, the associated service will also receive the data sent by the associated service, parse it into the routing information of the associated service according to the defined format, and store it in the local information of the associated service. In order to reduce the operation of the database, the routing information may not be stored in the database. In case of node restart or power failure, just send routing information again after restart.

In this embodiment, it is also necessary to maintain the routing information of the related business, because the initial routing information of the business is not always the same, and there is a possibility that the information exchange channel may fail, so in certain scenarios, the related business needs to Notify the associated service to update its own routing information.

Specifically, when the initial routing information of the associated service changes due to some maintenance behavior, it needs to send its own routing information to the head node of the associated service. Maintenance behaviors include, but are not limited to, business optimization, recovery of services with no reply attribute, modification of recovery connections to initial connections, etc.

When a node restarts, the associated service restores the local information of the service from the database, and if there is an associated service, it sends its own routing information to the head node of the associated service.

When it is detected that the status of the channel for information exchange changes from invalid to valid, because the routing information of the associated service itself may have changed during the period of time when the channel for information exchange is invalid, it is also necessary to report to the associated service at this time. The first node of the service sends its own routing information.

Since the purpose of associating two services is to provide 1+1 SNCP protection, in terms of routing strategy, the two associated services must be strictly irrelevant, and this strategy is only for the current initial connection of the service. That is to say, for an optimized connection or a recovery connection of a service without a reply attribute, it is necessary to follow a routing strategy that is strictly independent of the current initial connection of the associated service; if it is a service with a reply attribute, its recovery connection can choose to The current initial connection of the associated service follows the routing policy of strict don't care or best effort don't care.

In some scenarios, if the initial connection of two related services does not satisfy the strictly unrelated routing policy, the control plane can report an unrelated routing policy to the user when detecting that the routes of the two related services do not meet the strictly unrelated routing policy. Alerts that meet the routing policy. After receiving the alarm, the user can use optimization commands and other means to adjust the route of the associated service. After satisfying the strictly irrelevant routing policy, the control plane will report that the alarm disappears. The specific implementation method is that when the initial routing information of the associated service itself changes or when the routing information updated by the associated service is received, it is necessary to check the two associated services at this time. Whether the business satisfies the routing policy is strictly irrelevant.

Among them, the situations that may lead to the initial connection of two associated services not satisfying the strictly unrelated routing policy include:

1. The two services associated for the first time do not meet the routing policy, or an optimization command is issued for the two services at the same time, so that they are optimized to the same route and other user misoperations.

2. The recovery action triggered by the control plane. When two associated services fail at the same time, because different head nodes restore and avoid only the initial connection of the current associated service, the routing policy may not be satisfied between the two restored connections (for services with no reply, the restored connection is equal to the working connection) .

Under the 1+1SNCP protection mechanism, the working path and the protection path are required to follow strictly independent routing policies. Therefore, after an association relationship is established, when an associated service performs operations such as recovery, it needs to follow a certain routing policy with the associated service to provide SNCP protection. In the above-mentioned first scenario, since the source nodes are the same, the routing information of the first service can be obtained directly through the service identifier; in the second scenario, the routing information of the associated service is obtained through the information exchange channel when the routing information of the associated service changes sent over. In the second scenario, because the source nodes of the two services are different, the associated routing information may not be updated in time, resulting in the two services not following a strictly unrelated routing policy. At this time, the control plane maintains an associated service that does not follow the route The alert status of the policy.

The method and device for SNCP protection in the embodiment of the present invention when ASON is docked with a traditional network, when only the source (or sink) node is not in the ASON domain, when the second service is established, the associated first service can be specified at the same time, so that The two services can share the same up (or down) service time slot to realize the concurrent and optimal reception of channel signals; when the source and sink nodes are not in the ASON domain, the user sends an association request to the source nodes of the two services respectively In this method, an association relationship can be established without interaction between two nodes to provide SNCP protection, and at the same time, an associated service does not follow the routing policy alarm, prompting the user when to adjust the associated service route to provide complete SNCP protection. Therefore, the present invention enables the ASON network to provide a function similar to 1+1 (path) protection no matter which domain it is in by establishing two interrelated services. When a fault occurs outside the ASON domain, switching can occur from the working path to the protection path. At the same time, these two services can have recovery properties independently. When a path failure occurs in the ASON domain, dynamic rerouting of the control plane can be realized in the ASON domain, thereby improving the security of the ASON network.

The above is only a preferred embodiment of the present invention, and does not limit the patent scope of the present invention. Any equivalent structure or process transformation made by using the description of the present invention and the contents of the accompanying drawings, or directly or indirectly used in other related technical fields , are all included in the scope of patent protection of the present invention in the same way.

Claims (13)

1. the method for SNCP SNCP protection is characterized in that when an ASON ASON docked with legacy network, comprising:

Foundation first professional and second business that be mutually related; Only source node or destination node are in the territory of ASON network for said first professional and second business, and perhaps said first professional and the second professional source node and destination node be not all in the territory of ASON network;

For the ASON network SNCP is provided protection with second business according to said first business that is mutually related.

2. method according to claim 1 is characterized in that, when said first professional and second business when only source node or destination node are in the territory of ASON network, said foundation is mutually related and first professionally comprises with the second professional step:

Set up unshielded said first business;

Select for use and the said first professional identical last business time-slot, set up said second business, and appointment and said first business association.

3. method according to claim 2 is characterized in that, saidly sets up second business, and the step of appointment and said first business association comprises:

Set up the local information of second business, and this second professional associated services of preservation is designated said first business in the local information of second business; And the local information of obtaining said first business, and this first professional associated services of preservation is designated said second business in the local information of said first business;

From the local information of said first business, take out the routing iinformation of said first business, initiate to calculate the road request;

When said first professional and second business followed strict irrelevant routing policy, accomplish the second professional foundation according to the request of said calculation road; Otherwise second professional the foundation failed, and cancels the incidence relation of preserving in said first, second professional local message.

4. method according to claim 3 is characterized in that, said foundation according to calculation road request completion second business comprises:

When said source node issues the intersection request, between said first business and second business, form concurrent excellent receipts relation.

5. method according to claim 3; It is characterized in that; Saidly set up second business, and the step of appointment and said first business association comprises further: when said first professional and second business do not followed strict irrelevant routing policy, to the user prompt warning information.

6. method according to claim 1 is characterized in that, when said first professional and the second professional source node and destination node were all not in the territory of ASON network, said foundation was mutually related and first professionally comprises with the second professional step:

Set up two business, respectively professional and second business as first;

Associate Command is sent to first, second professional source node respectively, in local information separately, preserves the associated services sign that the other side's service identification is self respectively by two business;

Between said first, second professional source node, create information interaction passage, carry out the association of two business;

After the association success, set up the correlation protection relation of two business, through said information interaction passage, between said first, second business, send out both routing iinformations mutually.

7. method according to claim 6 is characterized in that, said first professional and the second professional type of service comprise following one of at least: 1+1SNCP is professional, information intelligent platform MSP business or unprotect business.

8. according to claim 6 or 7 described methods, it is characterized in that, also comprise: safeguard said first, second professional routing iinformation.

9. the device of SNCP protection is characterized in that when an ASON docked with legacy network, comprising:

Module is set up in association, is used for setting up first professional and second business that is mutually related; Only source node or destination node are in the territory of ASON network for said first professional and second business, and perhaps said first professional and the second professional source node and destination node be not all in the territory of ASON network;

Protection module is used for for the ASON network SNCP being provided protection with second business according to said first business that is mutually related.

10. device according to claim 9 is characterized in that, said association is set up module and comprised:

First sets up the unit, is used to set up unshielded said first business;

Second sets up the unit, is used to select for use and the said first professional identical last business time-slot, sets up said second business, and appointment and said first business association.

11. device according to claim 10 is characterized in that, said second sets up the unit comprises:

The service identification subelement is used to set up the second professional local information, and in the second professional local information, preserves this second professional associated services and be designated said first business; And the local information of obtaining said first business, and this first professional associated services of preservation is designated said second business in the local information of said first business;

Calculate the way unit, be used for taking out the routing iinformation of said first business, initiate to calculate the road request from the said first professional local information;

Set up subelement, be used for when said first professional and second business followed strict irrelevant routing policy, accomplish the second professional foundation according to the request of said calculation road; Otherwise second professional the foundation failed, and cancels the incidence relation of preserving in said first, second professional local message.

12., it is characterized in that the said subelement of setting up also is used for when said source node issues the intersection request, between said first business and second business, forms concurrent excellent receipts relation based on the described device of claim 11; And when said first professional and second business do not followed strict irrelevant routing policy, to the user prompt warning information.

13. device according to claim 9 is characterized in that, said association is set up module and is comprised:

The 3rd sets up the unit, is used to set up two business, respectively professional and second business as first;

Transmitting element is used for Associate Command is sent to first, second professional source node respectively, in local information separately, preserves the associated services sign that the other side's service identification is self respectively by two business;

Passage is created the unit, is used between said first, second professional source node, creating information interaction passage, carries out the association of two business;

The 4th sets up the unit, is used for after related success, sets up the correlation protection relation of two business, through said information interaction passage, between said first, second business, sends out both routing iinformations mutually.

Images