WO2011072581A1 - 共享mesh保护的实现方法和设备及光网络系统 - Google Patents

共享mesh保护的实现方法和设备及光网络系统 Download PDF

Info

Publication number
WO2011072581A1
WO2011072581A1 PCT/CN2010/079505 CN2010079505W WO2011072581A1 WO 2011072581 A1 WO2011072581 A1 WO 2011072581A1 CN 2010079505 W CN2010079505 W CN 2010079505W WO 2011072581 A1 WO2011072581 A1 WO 2011072581A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
node
sub
label
protection path
Prior art date
Application number
PCT/CN2010/079505
Other languages
English (en)
French (fr)
Inventor
孙俊
蔡军州
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP10837018.0A priority Critical patent/EP2503742B1/en
Priority to ES10837018.0T priority patent/ES2449367T3/es
Publication of WO2011072581A1 publication Critical patent/WO2011072581A1/zh
Priority to US13/524,822 priority patent/US9161106B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0079—Operation or maintenance aspects
    • H04Q2011/0081—Fault tolerance; Redundancy; Recovery; Reconfigurability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/009—Topology aspects
    • H04Q2011/0098—Mesh

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and device for implementing shared mesh protection and an optical network system. Background technique
  • Optical networks are widely used because of their high service transmission rate. They can transmit customer services by establishing one or more optical network connections that meet the bandwidth requirements of customers. The reliability of service transmission is an important measure of the stability of optical networks. index.
  • the reliability of optical network traffic transmission can be achieved by various protection and recovery techniques, such as the use of control plane rerouting techniques to recover optical network connections.
  • the control plane is a control network running in the optical network.
  • the optical network provides a control channel and runs a generalized Multi-Protocol Label Switching (GMPLS) protocol family.
  • GMPLS protocol family includes a routing protocol and a signaling protocol.
  • the routing protocol is mainly responsible for collecting optical network topology information (including node and link information) and calculating a path through which the connection passes.
  • the signaling protocol is mainly responsible for establishing light according to the calculated path. Internet connection.
  • the rerouting function can be provided for the connection, ie when the connection (working connection) transmitting the customer service fails, the control plane uses the pre-configured recovery path (or recalculates the path) to establish a new connection. (Resume connection), transfer customer business.
  • This method does not need to always provide two connections for the customer's service. It only needs to re-provide another available connection in case of a connection failure, so the bandwidth utilization is high, but due to the recovery technology using the control plane, the recovery time is usually Longer.
  • the connection established by the GMPLS control plane technology is usually called the Label Switch Path (LSP).
  • the LSP is triggered by the first node, and the re-routing process is triggered by the first node.
  • each shared Mesh protection service includes a working path and a recovery path.
  • the working paths of two shared Mesh protection services are separated, and their recovery paths can share channel resources.
  • the AMS (Automatic Protection Switching) overhead is used to transmit the shared Mesh protection message. Since the same channel can be used to share multiple services, the APS cost of the channel needs to be able to distinguish messages of different services.
  • the existing technology mainly implements shared Mesh protection through manual configuration of the network management system.
  • this method has strong dependence on devices such as the network management system, and the configuration operation is usually very complicated, and the network operation risk is large. Summary of the invention
  • the embodiments of the present invention provide a method and a device for implementing the shared Mesh protection, and an optical network system, which enables each node on the protection path to determine the service to be restored simply and accurately, and the configuration operation is simple, and the protection switching of the subsequent service can be performed. Provide reliable support.
  • the embodiment of the present invention provides the following technical solutions:
  • An embodiment of the present invention provides a method for implementing shared Mesh protection, including:
  • the first node receives the second type of message sent by the second node, and the second type of message carries the second forward incoming sub-tag assigned by the second node to the protection path of the first service, where the second forward The sub-tag is used to indicate a specific feature of the recovery information that carries the first service;
  • the recovery information of the first service is transmitted to the second node according to the indication of the first forward outgoing sub-tag.
  • the embodiment of the invention further provides an implementation method for sharing Mesh protection, including:
  • the second node allocates a second forward sub-label to the protection path of the first service, where the second forward sub-label is used to indicate a specific feature of the recovery information of the first service;
  • the second forward incoming subtag is sent to the first node on the protection path of the first service by the second type of message.
  • the embodiment of the invention further provides an optical network node, including:
  • a receiving module configured to receive a second type of message sent by the second node, where the second type of message carries a second forward incoming sub-label allocated by the second node to the protection path of the first service, where the second positive
  • the incoming sub-label is used to indicate a specific feature of the recovery information carrying the first service
  • a first allocation module configured to allocate, according to the second forward sub-label, a first forward sub-label, a first forward sub-label, and a second forward sub-port for a protection path of the first service Labels have a corresponding relationship;
  • a recovery information sending module configured to: when the working path of the first service is faulty, transmit the recovery information of the first service to the second node according to the indication of the first forward outgoing sub-tab.
  • the embodiment of the invention further provides an optical network node, including:
  • a first allocation module configured to allocate a second forward incoming sub-label to the protection path of the first service, where the second forward-input sub-label is used to indicate a specific feature of the recovery information of the first service;
  • a message sending module configured to send, by using the second type of message, the second forward incoming subtag to the first node on the protection path of the first service.
  • An embodiment of the present invention further provides an optical network system, which is characterized in that
  • a second node configured to allocate a second forward ingress subtag for the protection path of the first service, where the second forward ingress subtag is used to indicate a specific feature of the recovery information of the first service; Transmitting the second forward incoming subtag to a first node on a protection path of the first service.
  • a first node configured to receive a second type of message sent by the second node, where the second type of message carries a second forward incoming sub-label assigned by the second node to the protection path of the first service; a forward-forward sub-label, the first forward-out sub-label is allocated to the protection path of the first service, where the first forward sub-label and the second forward sub-label have a corresponding relationship;
  • the recovery information of the first service is transmitted to the second node according to the indication of the first forward outgoing sub-tag.
  • a sub-tag for indicating a specific feature of the service recovery information is allocated and transmitted by a node on the protection path, so that the upstream node or the downstream node of the node transmits the service recovery according to the node.
  • the information can be used to directly determine the service to be restored when the node on the protection path receives the service recovery information, and the configuration operation is simple, which can provide reliable support for the automatic fast protection switching of the subsequent service.
  • FIG. 1 is a schematic diagram of a message delivery direction indication according to an embodiment of the present invention
  • FIG. 1 is a schematic diagram of an optical network topology structure according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for implementing shared Mesh protection according to Embodiment 1 of the present invention
  • FIG. 3 is a flowchart of a method for implementing shared Mesh protection according to Embodiment 2 of the present invention
  • FIG. A flowchart of a method for implementing shared Mesh protection is provided in the third embodiment.
  • FIG. 4 is a schematic diagram of an APS overhead division according to Embodiment 3 of the present invention.
  • FIG. 4 is a schematic diagram of an APS overhead allocation according to Embodiment 3 of the present invention.
  • Figure 4-d is a schematic diagram of a splitter distribution according to Embodiment 3 of the present invention.
  • FIG. 5 is a schematic diagram of an optical network node according to Embodiment 4 of the present invention.
  • FIG. 6 is a schematic diagram of an optical network node according to Embodiment 5 of the present invention.
  • FIG. 7 is a schematic diagram of an optical network system according to Embodiment 6 of the present invention. detailed description
  • the embodiments of the present invention provide a method and a device for implementing the shared Mesh protection, and an optical network system, which enables each node on the protection path to determine the service to be restored simply and accurately, and the configuration operation is simple, and the service can be automatically and quickly Protection switching provides reliable support.
  • the signaling protocol of the control plane may be, for example, a resource resert protocol (RSVP-TE, Resource ReSerVation Protocol-Traffic Engineering), which is mentioned in the embodiment of the present invention. Both can be messages and objects in GMPLS RSVP-TE.
  • RSVP-TE Resource ReSerVation Protocol-Traffic Engineering
  • the direction in which traffic data is transmitted from the first node to the last node is called the Downstream direction, also known as the forward direction, that is, the direction in which the Path message is transmitted.
  • the service data is transmitted from the last node.
  • the direction to the head node is called the Upstream direction, also known as the reverse direction, which is the direction of the Resv message.
  • the Path message is a message type defined by RSVP-TE, and can be sent from the source node (the first node) along the calculated route to the destination node (the last node) to notify the node along the path. The connection is established.
  • the Resv message is also a type of message defined by RSVP-TE. It can be sent from the destination node to the source node.
  • a two-way connection can be established.
  • the two-way service will have a reverse. If it is a one-way service, there is no reverse, but whether it is a one-way or two-way service, the Resv message will be transmitted and processed.
  • the direction in which the Path message is received is called the forward inbound direction.
  • the direction in which the Path message is sent is called the forward direction.
  • the direction in which the Resv message is received is called the reverse direction.
  • the direction in which the Resv message is sent is called Reverse the direction.
  • the node between the head node and the last node may be referred to as an intermediate node, and the intermediate node may be 0, one or more.
  • the node that sends the Path message can be called the upstream node, and the node that receives the Path message is the downstream node. It can be understood that the upstream node and the downstream node are relatively speaking.
  • the first node can be called the upstream node of each other node, and the last node can be It is called the downstream node of each other node.
  • the optical network shown in Figure 1-b there are three shared Mesh protection services.
  • the solid line indicates the working path of each service, and the dotted line indicates the protection path of each service. Since the working paths of the three services are separated from each other, their protection paths can share resources. For example, the protection path of service 1 and service 2 share the channel 2 (CH2) resource, the protection path of service 1 and service 3 share the channel 3 (CH3) resource, and the protection path of service 2 and service 3 share channel 8 (CH8). Resources.
  • node N1 in the working path of service 1, if node N1 is the head node, node N2 is the last node. In the protection path of service 1, if node N1 is the head node, nodes N6 and N7 are in the middle. Node, node N2 is the last node.
  • the first node N1 can use the APS overhead of channel 2 (CH2) to send recovery information to node N6, and initiate automatic protection switching to switch service 1 to protection. Transfer on the path, and so on.
  • CH2 APS overhead of channel 2
  • the node on the protection path allocates and delivers a label for indicating a specific feature of the service recovery information, and obtains recovery information of the upstream node or the downstream node of the sub-tag to transmit the service.
  • each node on the protection path can directly determine the service to be restored when receiving the recovery information of the service.
  • a method for implementing the shared Mesh protection includes:
  • the second node allocates a second forward sub-label to the protection path of the first service, where the second forward sub-label is used to indicate a specific feature of the recovery information of the first service.
  • the specific feature of the recovery information of the first service may include, for example, a specific identifier included in the recovery information of the first service (for example, a service distinguisher), a specific data structure that the recovery information of the first service has, and a recovery of the first service.
  • the identity of the sub-APS overhead of the information eg, the number of sub-overheads or other related features.
  • the second forward sub-label allocated by the second node to the protection path of the first service may be any information that can indicate a specific feature of the recovery information of the first service, for example, the sub-tag can be Demonstrating one or more of the following specific characteristics of the recovery information of the first service: the specific identifier included in the recovery information of the first service, the specific data structure of the recovery information of the first service, or the recovery information carrying the first service The specific number of sub-APS overhead numbers, etc.
  • the message of the second type mentioned in the embodiments of the present invention may be, for example, a Resv message, or another message having a similar function, and the message of the second type may also carry the indication information of the protection path of the first service.
  • the indication information of the protection path for creating the first service carried by the message of the second type may be any, for example, the indication information may be carried by an indication bit in the second type of message, or the child carried in the message may be directly utilized.
  • the label serves as an indication of the protection path for creating the first service, and of course other methods are also possible.
  • the second node may be the last node of the protection path of the first service, or may be the intermediate node of the protection path of the first service, and the first node is the upstream node of the second node.
  • the second node may carry the allocated second forward sub-label in the second type of message, and use the signaling message to protect the second forward sub-label to the first service.
  • the upstream node on the path sends, so as to obtain the first node of the second forward-input sub-label, and correspondingly allocates the first forward sub-label (wherein the second forward-in sub-label and the first forward-out sub-tab
  • the value of the label may be equal, or have a corresponding derivation correspondence.
  • the first forward sub-label corresponding to the first node is also used to indicate a specific feature of the recovery information of the first service, and the first forward The label and the second forward incoming subtag indicate the same characteristics of the first service recovery information.
  • the first node may transmit the recovery information of the first service to the second node according to the indication of the first forward outgoing sub-tag.
  • the second node receives the recovery information of the first service transmitted by the first node, the second node can directly The second forward-input sub-label is allocated to determine that the service to be restored is the first service, and the first service can be automatically switched to its protection path for transmission.
  • the second forward-input sub-label assigned by the second node indicates that the recovery information of the first service carries the service distinguisher 1, and the second node may carry the second forward-incoming sub-tag in the second type of message.
  • the first node may allocate the first forward sub-label according to the obtained second forward sub-label (for example, the values of the second forward sub-label and the first forward sub-label are equal)
  • the first node may transmit the recovery information carrying the service distinguisher 1 to the second node according to the indication of the first forward outgoing sub-label; the second node receives the first
  • the information about the service distinguisher 1 carried by the node is transmitted, the service to be restored is directly determined to be the first service.
  • a sub-tag for indicating a specific feature of the service recovery information is allocated and transmitted by a node on the protection path, so that the upstream node or the downstream node of the node transmits the service recovery according to the node.
  • the information can be used to directly determine the service to be restored when the node on the protection path receives the service recovery information, and the configuration operation is simple, which can provide reliable support for the automatic fast protection switching of the subsequent service.
  • the second node may further receive the first type of message sent by the first node, where the first mentioned in the embodiments of the present invention
  • the type of the message may be, for example, a Path message, or another message having a similar function.
  • the first type of message received by the second node may carry the first node to allocate a first reverse entry sub-label for the protection path of the first service.
  • the first reverse incoming sub-tag is used to indicate a specific feature of the recovery information that carries the first service (for example, a sub-automatic protection switching overhead indicating the recovery information of the first service or a service distinguisher carried in the recovery information of the first service),
  • the first type of message may also carry indication information for creating a protection path of the first service.
  • the second node may further allocate, according to the first reverse incoming subtag, a second reverse outgoing subtag for the protection path of the first service, where the second reverse outgoing subtag and the The first reverse-into-sub-label has a corresponding relationship; and when the working path of the first service is known to be faulty, The recovery information of the first service is transmitted to the first node according to the indication of the second reverse outgoing subtag.
  • the second node may further calculate a reverse outgoing interface and a reverse outgoing channel of the protection path of the first service on the second node according to the routing information; and establish a protection path of the first service on the second node.
  • the reverse binding relationship wherein the reverse binding relationship may include a mapping of the reverse outgoing interface of the protection path of the first service on the second node, the reverse outgoing channel, and the mapping of the second reverse outgoing sub-label
  • the first service is switched to the protection path of the first service according to the established reverse binding relationship when the working path of the first service is faulty.
  • the second node may further calculate a forward ingress interface of the protection path of the first service on the second node according to the routing information, and allocate a forward ingress channel to the protection path of the first service; a forward binding relationship of the protection path of the first service on the second node, where the forward binding relationship may include a forward ingress interface, a forward ingress channel, and the foregoing And the first service is switched to the protection path of the first service according to the established forward binding relationship when the working path of the first service is faulty.
  • the second node may protect the first service according to the recommendation of the first node or according to the local allocation situation.
  • the path assigns a second forward sub-label
  • the second node may be within the range of the sub-tags allocated by the first node.
  • a protection path of a service allocates a second forward sub-label
  • the second node may be the first service according to the indication of the indication information of the sub-label assigned by the head node.
  • the protection path assigns a second forward sub-label.
  • each upstream node of the second node may add a reverse incoming sub-label assigned to the protection path of the first service to the first type of message, and the second node may collect and record the received first
  • Each upstream node carried in a type of message is a reverse-input sub-label assigned to the protection path of the first service for subsequent better maintenance and management. Further, the following describes the processing procedure of the node (for example, the first node) that obtains the subtag on the protection path. Referring to FIG.
  • a method for implementing the shared Mesh protection according to the second embodiment of the present invention includes: 310: receiving by the first node a second type of message sent by the second node, the second type of message And carrying a second forward-input sub-label allocated by the second node to the protection path of the first service, where the second forward-input sub-label is used to indicate a specific feature of the recovery information that carries the first service.
  • the specific feature of the recovery information of the first service may include, for example, a specific identifier included in the recovery information of the first service (for example, a service distinguisher), a specific data structure that the recovery information of the first service has, and a recovery of the first service.
  • a specific identifier included in the recovery information of the first service for example, a service distinguisher
  • a specific data structure that the recovery information of the first service has for example, a specific data structure that the recovery information of the first service has, and a recovery of the first service.
  • the identity of the sub-APS overhead of the information eg, the number of sub-overheads or other related features.
  • the first node may be the first node of the protection path of the first service, or may be the intermediate node of the protection path of the first service, and the second node is the downstream node of the first node.
  • the second type of the message may also carry the indication information of the protection path of the first service, where the indication information of the protection path of the first service may be any, and the indication information may be, for example, a specific indication in the Resv message.
  • the indication information carried by the bit, or directly the sub-label carried in the signaling message, may of course be other indication information identifiable by the first node.
  • the first forward sub-label is allocated to the protection path of the first service, and the first forward sub-label and the second forward sub-label have a corresponding relationship.
  • the values of the second forward sub-label and the first forward sub-label may be equal, or have corresponding derivation correspondences.
  • the first forward sub-label corresponding to the first node is also used to indicate the first A specific feature of the recovery information of a business.
  • the recovery information of the first service is transmitted to the second node according to the indication of the first forward outgoing sub-label.
  • the first node may transmit the recovery information of the first service to the second node according to the indication of the first forward outgoing sub-tag.
  • the second node receives the recovery information of the first service that is transmitted by the first node, the second node can directly determine, according to the indication of the second forward incoming sub-label, that the service to be restored is the first service, and then Quickly switch the first service to its protection path for transmission.
  • the second forward-input sub-label assigned by the second node indicates the number 1 of the sub-APS overhead of the recovery information carrying the first service, and the second node may carry the second forward-input sub-label in the second type.
  • the message is sent to the first node; the first node may allocate the first forward sub-label according to the obtained second forward sub-label (for example, the second forward sub-label and the first forward sub-label The value is equal), when the working path of the first service is known to be faulty, the first node can follow the first forward direction
  • the sub-tag indicates that the recovery information is transmitted to the second node by using the sub-AP APS overhead; when the second node receives the recovery information transmitted by the first node by using the sub-AP APS overhead, the sub-APS overhead of the bearer recovery information may be The number directly determines that the service to be restored is the first service.
  • the first node and the second node can transmit the recovery information of the service according to the foregoing manner, and the second node can simply determine the service to be restored when receiving the recovery information, and then automatically and quickly perform the service for subsequent operations. Protection switching provides reliable support.
  • a sub-tag for indicating a specific feature of the service recovery information is allocated and transmitted by a node on the protection path, so that the upstream node or the downstream node of the node transmits the recovery information of the service accordingly.
  • each node on the protection path can directly determine the service to be restored when receiving the service recovery information, and the configuration operation is simple, and can provide reliable support for the automatic fast protection switching of the subsequent service.
  • the first node may calculate a forward outgoing interface of the protection path of the first service on the first node according to the routing information, and allocate a forward outgoing channel to the protection path of the first service; a forward binding relationship on the first node, where the forward binding relationship may include a forward outgoing interface, a forward outgoing channel, and a first forward outgoing label of the protection path of the first service. Mapping the binding relationship; When the working path of the first service is faulty, the first service is switched to the protection path of the first service according to the forward binding relationship established above.
  • the first node may further calculate a reverse inbound interface of the protection path of the first service on the first node according to the routing information, and allocate a reverse tunnel to the protection path of the first service. And assigning, to the protection path of the first service, a first reverse incoming sub-label, where the first reverse-input sub-label is used to indicate a specific feature of the recovery information of the first service (for example, a sub-instruction that may indicate recovery information of the first service) Automatically protecting the switching overhead or the service distinguisher carried in the recovery information of the first service; and transmitting the first reverse incoming subtag to the second node on the protection path of the first service by using the first type of message,
  • the first type of message also carries indication information for creating a protection path of the first service.
  • the first node may calculate, according to the routing information, a forward ingress interface of the protection path of the first service on the first node, and allocate a positive path to the protection path of the first service.
  • the foregoing forward binding relationship may further include: a forward inbound interface and a forward-incoming channel of the protection path of the first service on the first node
  • the mapping relationship with the first forward-input sub-tag is performed; and the first forward-input sub-tag is sent to the third node on the protection path of the first service by using the second type of message.
  • the first node may also carry the indication information of the sub-tag that it proposes to allocate in the first type of message;
  • the second node may be the first service according to the recommendation of the first node or according to the local allocation situation.
  • the protection path allocates a second forward sub-label;
  • the first node may also carry the indication information of the range of the sub-tags that it specifies to be assigned in the first type of message; the second node may specify the allocated sub-tags in the range of the first node, The protection path of the first service allocates a second forward sub-label;
  • the first node may further include, in the first type of message, the indication information of the allocated sub-tag by the first node, and the second node may specify, according to the indication information of the allocated sub-label of the first node, The protection path of the first service allocates a second forward sub-label.
  • each upstream node of the second node may add a reverse incoming sub-label assigned to the protection path of the first service to the first type of message, and the second node may collect and record the received first
  • Each upstream node carried in a type of message is a reverse-input sub-label assigned to the protection path of the first service for subsequent better maintenance and management.
  • each downstream node of the first node may add a forward-input sub-label assigned to the protection path of the first service to the second type of message, and the first node may collect and record the received
  • Each downstream node carried in the second type of message is a forward-input sub-label assigned to the protection path of the first service for subsequent better maintenance and management.
  • the sub-APS (Sub-APS) overhead is allocated to the different services of the shared Mesh protection service
  • the sub-Label can be used.
  • An identifier indicating the sub-APS overhead used by the service (for example, the number of the sub-APS overhead).
  • the information in the sub-APS overhead used by the service ie, the recovery information
  • the service is switched. If the APS overhead is not divided, the entire APS overhead is shared by all services sharing the Mesh protection service.
  • the label may be used to indicate the identification information of the shared Mesh protection service (for example, the service distinguisher).
  • the recovery information including the identification information of the service is transmitted in the APS overhead to perform the switching.
  • the process of establishing the protection path of the service S1 (shared Mesh protection service) is taken as an example for description.
  • the first type of message is a Path message
  • the second type of message is a Resv message as an example.
  • a method for implementing shared Mesh protection according to Embodiment 3 of the present invention may include:
  • the first node calculates, according to the routing information, the protection path of the service S1 on the reverse inbound interface of the local node, and allocates the reverse ingress channel. According to the local allocation, the protection path of the service S1 corresponds to the reverse entry of the node.
  • the direction is assigned to the Label (referred to as the reverse sub-label).
  • the first node establishes the reverse binding relationship of the service SI on the local node, including: the reverse incoming interface, the reverse incoming channel and the reverse incoming label binding relationship, the reverse outgoing interface of the first node, and the reverse outgoing channel.
  • the reverse out of the Label can be no.
  • the first node sends the assigned reverse incoming sub-label to the downstream node by using a Path message.
  • the first node may also carry the indication information of the shared Mesh protection path in the Path message, so as to indicate that the currently established LSP is a shared Mesh protection path.
  • each of the upstream nodes may carry the indication information of the shared Mesh protection path in the Path message sent to the downstream node, so as to indicate to each downstream node that the currently established LSP is a shared Mesh protection path, and each downstream node receives the Path.
  • the information about the created Mesh protection path carried in the Path message is used to identify the currently established LSP as the shared Mesh protection path, and then the corresponding process is started.
  • the intermediate node receives the Path message sent by the upstream node; calculates the reverse outgoing interface and the reverse incoming interface of the protection path of the service S1 on the local node according to the routing information, and allocates a reverse outgoing channel for the service S1. , reverse into the channel;
  • the intermediate node may allocate a sub-label (referred to as a reverse sub-label) in the reverse direction of the node according to the sub-label carried by the received Path message for the protection path of the service SI, where the assigned reverse label Label
  • a sub-label (referred to as a reverse sub-label) in the reverse direction of the node according to the sub-label carried by the received Path message for the protection path of the service SI, where the assigned reverse label Label
  • the value of the sub-label (the upstream sub-label of the upstream node) carried by the received Path message is the same as that of the sub-label (the upstream sub-label of the upstream node); the intermediate node further allocates the sub-label in the reverse direction of the node for the service S1 according to the local allocation. (referred to as the reverse sub-label).
  • the intermediate node can establish the reverse binding relationship of the service SI on the local node, and can include: a reverse inbound interface, a reverse incoming channel, a reverse incoming label, a reverse outgoing interface, a reverse outgoing channel, and a reverse outgoing label. Binding relationship.
  • the intermediate node sends the assigned reverse sub-label to the downstream node through a Path message.
  • the last node receives the Path message sent by the upstream node, and calculates a reverse outgoing interface and a forward incoming interface of the protection path of the service S1 on the local node according to the routing information, and allocates a reverse outgoing channel and a forward incoming channel.
  • the last node assigns a child LabeK, that is, a reverse label to the protection direction of the service in the reverse direction of the node, according to the child label carried in the Path message, where the value of the assigned backward label Label can be
  • the value of the sub-label (the upstream sub-label of the upstream node) carried by the received Path message is the same; the reverse binding relationship of the service S1 on the local node is further established, including: reverse outgoing interface, reverse outgoing channel Reverse the binding relationship of the Label; at the end node, the reverse inbound interface, the reverse incoming channel, and the reverse incoming sub-label may not.
  • the final node may further allocate a child label (referred to as a forward-injection label) in the forward direction of the node for the protection path of the service S1 according to the local allocation, and establish a forward binding relationship of the service SI on the node.
  • the method may include: a binding relationship between the forward incoming interface, the forward incoming channel, and the forward incoming label, and the forward outgoing interface, the forward outgoing channel, and the forward outgoing Label of the last node may be absent.
  • the last node combines the forward and reverse binding relationships to establish a sub-label mapping binding relationship, which may include: a forward inbound interface, a forward incoming channel, a forward incoming sub-label, a reverse outgoing interface, a reverse outgoing channel, and Reverse the mapping binding relationship of the child Label.
  • the last node can record the established binding relationship in the form of a data table, so as to continue the fast and accurate query.
  • the last node sends the forwarded sub-label to the upstream node through the Resv message.
  • the last node can also carry the indication information of the shared Mesh protection path in the Resv message, so as to indicate to the upstream node that the currently established LSP is the shared Mesh protection path. .
  • each of the downstream nodes may carry the indication information for creating the shared Mesh protection path in the Resv message sent to the upstream node, so as to indicate to each upstream node that the currently established LSP is a shared Mesh protection path, and each upstream node receives the Resv.
  • the message is generated, according to the indication information of the shared Mesh protection path carried in the Resv message, it is clarified that the currently established LSP is a shared Mesh protection. Protect the path, and then start the corresponding process, the following is no longer - description.
  • the intermediate node receives the Resv message, and calculates a forward outgoing interface and a forward incoming interface of the protection path of the service S1 according to the routing information, and allocates a forward outgoing channel and a forward incoming channel;
  • the intermediate node allocates a child label (that is, a forward label) in the forward direction of the node according to the child label carried in the Resv message, and the value of the positive label of the assigned forward label can be received and received for the protection path of the service SI.
  • the value of the sub-label (the downstream forward label of the downstream node) carried by the Resv message is the same; and the sub-label is assigned to the protection path of the service S1 in the forward direction of the node according to the local allocation. Child Label).
  • the intermediate node can establish the forward binding relationship of the service S1 on the local node, including: the forward inbound interface, the forward incoming channel, the forward incoming sub-label, the forward outgoing interface, the forward outgoing channel, and the forward outgoing Binding relationship of the child Label;
  • the intermediate node combines the previously established reverse binding relationship of the service S1 on the local node, and can establish a sub-label mapping binding relationship of the service S1, which may include: a forward inbound interface, a forward incoming channel, and a forward incoming sub-label.
  • Forward output interface forward output channel, forward outgoing Label; reverse input interface, reverse input channel, reverse input label, reverse output interface, reverse output channel, reverse output sub-label.
  • the intermediate node may record the established binding relationship in the form of a data table for subsequent fast and accurate query.
  • the intermediate node sends the assigned forward incoming sub-label to the upstream node through the Resv message.
  • the first node receives the Resv message, and calculates a protection path of the service S1 on the local node according to the routing information, and allocates a forward outgoing channel.
  • the first node allocates a child label (that is, a forward label) in the forward direction of the node according to the child label carried in the Resv message, and the value of the positive label of the assigned forward label can be received and received for the protection path of the service SI.
  • the value of the sub-label (the downstream forward label of the downstream node) carried by the Resv message is the same; the forward binding relationship of the protection path of the service S1 on the node can be established, which may include: The binding relationship to the outgoing channel and the forward outgoing Label, the forward inbound interface, the forward incoming channel, and the forward incoming Label of the first node may not be;
  • the first node combines the forward and reverse binding relationships to establish a sub-label mapping relationship, including: a forward outgoing interface, a forward outgoing channel, a forward outgoing label; a reverse incoming interface, a reverse incoming channel, and a reverse Enter The mapping binding relationship of the child Label.
  • the first node can record the established binding relationship in the form of a data table, so as to continue the fast and accurate query.
  • any node on the protection path may also carry the indication information of the sub-label proposed to be allocated in the Path message sent to the downstream node, and may be used to provide a recommendation for the sub-label assigned by the downstream node.
  • the downstream node can allocate the forward incoming label as much as possible according to the recommendation of the upstream node. For example, if the upstream node finds that the downstream node does not assign the forward incoming label according to the recommendation of the node, the upstream node can choose to accept the child Label according to the local policy. , or reject the child Label and can report further errors.
  • Any node may also carry a sub-Label set (which may include one or more sub-tags) in the Path message sent to the downstream node, and is used to limit the range of the sub-Label allocated by the downstream node, and the downstream node is allocated according to the range given by the upstream node. For example, if the upstream node finds that the downstream node does not allocate the sub-label according to the range specified by the node, the upstream node can reject the sub-label according to the local policy, and can further report an error.
  • a sub-Label set which may include one or more sub-tags
  • the first node may carry the indication information of the sub-labels allocated by the specified part or all the downstream nodes in the Path message sent to the downstream node, and may be used to specify the sub-labels allocated by some or all of the downstream nodes.
  • the downstream node allocates the forward incoming label according to the indication of the first node. For example, if the first node finds that the downstream nodes are not assigned the forward incoming label according to the indication of the first node, the first node may reject the child Label according to the local policy, and may Further error.
  • each node may add, for example, the value of the sub-label assigned by the node to the Upsteam direction to the Path message and send it to the downstream node; and assign the local node to the Downstream direction.
  • the value of the subtag is added to the Resv message and sent to the upstream node.
  • the Path message When the Path message is transmitted to the last node, the Path message carries the sub-tag information used by all nodes passing the LSP in the Upstream direction.
  • the Resv message is transmitted to the head node, the Resv message carries all the nodes that the LSP passes in the Downstream. Subtag information used by the direction.
  • sub-tags and indication information can be carried in the object of the message.
  • several objects carrying sub-tags or indication information are first introduced. You can extend the Protection object to add a shared Mesh protection flag.
  • An indicator bit is extended in the protection object to indicate that the established LSP is a shared Mesh protection path.
  • the format can be as follows:
  • Length 16 bits indicating the length of the object
  • Class-num 8 bits , indicating the type number of the object, the value is 37;
  • the N (1 bit) setting (1) indicates that the message exchange of the control plane is used for notification during protection switching
  • setting (1) means that after the protection switching, the service is transmitted by the protection LSP; M (1 bit), when set to 1 , the established LSP is the path used for shared Mesh protection; LSP Flags ( 6 bits ) indicating the type of recovery of the LSP;
  • Link Flags ( 6 bits ) indicating the type of link protection.
  • the "M" bit in the Protection object carried in the Path message of the protection path of the shared Mesh protection service is set to 1 to indicate that the node that receives the Path message is currently creating a shared Mesh protection service. Protection path.
  • the object is used to carry sub-label information in the Downstream direction and is carried by a Resv message.
  • the format is as follows: twenty three
  • Length 16 bits indicating the length of the object
  • Class-num 8 bits , indicating the type number of the object
  • Sublabel 16 bits, indicating the subtag value.
  • the node may, for example, use the value of the sub-label of the assigned LSP in the Dowstream direction as the value of the Sublabel field of the Sublabel object, and carry the Sublabel object in the Resv message and send it to the upstream node.
  • the object can be used to carry the suggested sub-tag information, which can be carried by the Path message, and the format can be 3 ⁇ 4:
  • the meanings of the fields of the Suggested Sublabel object defined above may be as follows: Length ( 16 bits ) , indicating the length of the object;
  • Class-num 8 bits , indicating the type number of the object
  • Sublabel 16 bits, indicating the suggested subtag value.
  • the value of the suggested sub-label may be used as the value of the Sublabel field of the Suggested Sublabel object, and the Suggested Sublabel object is carried in The Path message is sent to the downstream node.
  • the downstream node can assign the forward sub-label according to the suggested sub-tag value in the Suggested Sublabel object after obtaining the Suggested Sublabel object. For example, if the upstream node finds that the downstream node does not have the sub-label assigned according to the recommended sub-tag value in the Suggested Sublabel, it can proceed according to the local policy. Further, a new object can be defined: Sublabel Set object
  • This object is used to carry the specified allocation range of the sub-label. It can be carried in the Path message.
  • the format can be 3 ⁇ 4:
  • Length 16 bits , the length of the object
  • Class-num 8 bits , the type number of the object
  • 0 can indicate the inclusion list, indicating one or more Sublabels in the Sublabel Set; 1 can indicate the exclusion list, indicating that one or more Sublabels in the Sublabel Set are excluded; 2 can indicate the inclusion range, Indicates the range of sublabels included. For example, there are two subtags in Sublabel Set. The first one indicates the starting value of the subtag range, the second indicates the ending value. If it is 0, it indicates that there is no limit. 3 indicates the exclusion range. , indicating the range of excluded Sublabels. For example, there are two sub-labels in the Sublabel Set. The first one indicates the starting value of the sub-label range, and the second indicates the ending value. If it is 0, it means there is no limit.
  • Sublabel Type ( 14 bits ) , indicating the type of subtag.
  • Sublabel 16 bits, indicating the subtag value.
  • the specified sub-label range information may be carried in each Sublabel field of the Sublabel Set object, and sent to the downstream through the Path message.
  • the node, the downstream node may allocate an appropriate sub-tab according to the sub-tag range information in the Sublabel Set object. For example if the upstream node is found from below If the sub-label of the Sublabel object carried in the Resv message received by the cursor node is not within the range given by the Sublabel Set, the sub-label is rejected, and a failure indication may be returned.
  • Upstreamsublabel object
  • the object is used to carry the sub-tag information in the Upstream direction in the bidirectional LSP, and can be carried in the Path message.
  • the format can be as follows:
  • the meanings of the fields of the Upstreamsublabel object defined above may be as follows: Length ( 16 bits ) , indicating the length of the object;
  • Class-num 8 bits , indicating the type number of the object
  • Sublabel 16 bits, indicating the subtag value.
  • the value of the sub-label assigned by the upstream node is used as the value of the Sublabel field of the Upstreamsublabel object, and the Upstreamsublabel object is carried in the Path message and sent to the downstream node.
  • the object is a Sublabel ER0 sub-object, which is used to carry sub-tag information in the ERO object to display sub-label control.
  • the format can be as follows:
  • each field of the Sublabel ERO subobject defined above can be as follows: U( 1 bit ), used to identify the direction of Sublabel. If it is 0, it can indicate downstream sublabel; if it is 1, it is upstream sublabel , used in bidirectional LSPs;
  • Length 8 bits indicating the length of the object
  • Sublabel 16 bits, indicating the subtag value.
  • the value of the specified sub-label can be used as a Sublabel ERO sub-sub-label.
  • the value of the Sublabel field of the object is implemented by carrying the Sublabel ERO sub-object in the ERO object of the Path message.
  • the object is a Sublabel RRO sub-object, which is used to carry sub-tag information in the RRO object, so as to collect sub-labels used by the LSP, and the format can be as follows:
  • the meanings of the fields of the Sublabel ERO subobject defined above may be as follows: U(1 bit), which is used to identify the direction of the Sublabel. If it is 0, it indicates the downstream sublabel. If it is 1, it can indicate the upstream sublabel. In the LSP;
  • Length 8 bits indicating the length of the object
  • Sublabel 16 bits, indicating the subtag value.
  • each node may, for example, use the value of the sub-label assigned by the node in the Upsteam direction as the value of the Sublabel field of the Sublabel RRO sub-object, and the Sublabel RRO sub-sub The object is carried in the Path message and sent to the downstream node.
  • the value of the sub-label assigned to the Downstream direction is used as the value of the Sublabel field of the Sublabel RRO sub-object.
  • the Sub-label RRO sub-object is carried in the Resv message and sent to the upstream node.
  • the RRO object carried by the Path carries the sub-tag information used by all the nodes passing the LSP in the Upstream direction.
  • the RRO object carried by the Resv carries the LSP. Subtag information used by all nodes passing in the Downstream direction.
  • a child label can be allocated for the protection path of the service S1, and a mapping relationship is established.
  • the service first node or the last node detects the fault and switches the service S1 to the protection path.
  • the corresponding sub-label mapping relationship is found, the related information in the APS overhead is set, and the recovery information is transmitted through the APS overhead.
  • each node finds the corresponding sub-label mapping relationship according to the specific characteristics of the recovery information, establishes a corresponding connection, and continues to transmit the recovery information to other nodes through the APS overhead to establish a protection path.
  • the connection up to the end node (or the first node).
  • the last node (or the first node) can find the corresponding sub-label mapping relationship according to the recovery information carried in the received APS overhead, and can switch the service S1 to the protection path, and transmit the service S1 through the protection path to make the service S1. Get a quick recovery.
  • the 4-byte APS overhead can be divided into 8 shares, a total of 8 Sub-APS overheads (such as shown in Figure 4-b), each sub-overhead is 4 bits, and each sub-overhead can define up to 16 shares.
  • Mesh protects related messages.
  • Each Sub-APS overhead is responsible for transmitting a service-related message.
  • a channel's APS overhead can transmit up to eight shared Mesh protection service-related messages, that is, a channel can share protection paths for up to eight shared Mesh protection services.
  • the sub-label can correspond to the Sub-APS overhead. If the sub-label is assigned, it is equal to the sub-APS overhead, and the sub-label carries the sub-APS overhead number.
  • the shared Mesh protection path flag is carried in the protection object of the Path message that creates the shared Mesh protection path, and is used to indicate that the Path message creates a shared Mesh protection path. See Figure 4-c. The following takes the process of creating a shared Mesh protection path for Service 2 as an example.
  • the first node N1 uses the routing information to calculate the reverse incoming interface of the protection path of the service 2 on the local node, and allocates the reverse incoming channel; the node N1 allocates the Sub-APS overhead for the reverse inbound direction of the protection path of the service 2, and allocates The protection path of service 2 is in the reverse-entry label of node N1. For example, if the 2# Sub-APS overhead of the CH2 channel is allocated for service 2, the protection path of service 2 is indicated by the reverse-entry label of node N1.
  • the node N1 can establish a reverse binding relationship, which can include: a reverse incoming interface, a reverse incoming channel , Reverse the binding relationship of the Label.
  • the node N1 can use the number 2 of the 2 # Sub-APS overhead as an Upstreamsublabel object.
  • the value of the Sublabel field, the Upstreamsublabel object is sent to the node N6 through the Path message, so that the Sub-APS overhead information allocated by the node N1 for the service 2 is notified to the node N6;
  • the node N1 and the node N6 may carry the shared Mesh protection path flag in the Protection object in the Path message sent to the downstream node, so as to indicate to the respective downstream nodes that the currently established LSP is a shared Mesh protection path, and each downstream node ( The node N6 and the node N5 may, after receiving the Path message, carry the shared Mesh protection path flag according to the Protection object in the Path message, and clarify that the currently established LSP is a shared Mesh protection path, and then start the corresponding process. - Description.
  • the node N1 may, for example, use the value of the sub-label for indicating the Sub-APS cost number of the proposed allocation as the Sublabel field in the Suggested Sublabel object.
  • the node N1 may use the value of the sub-label indicating the sub-APS overhead range of the limited allocation as the value of the Sublabel field in the Sublabel Set object.
  • the coverage area information of the Sub-APS overhead is carried by carrying the Sublabel Set object in the Path message.
  • the node N1 may, for example, use the value of the sub-tag for indicating the Sub-APS cost number assigned by the node as The value of the Sublabel field in the Sublabel ERO sub-object is implemented by carrying the Sublabel ERO sub-object in the ERO object of the Path message.
  • the node N6 receives the Path message, and uses the routing information to calculate the reverse inbound interface and the reverse outbound interface of the protection path of the service 2 on the local node, and allocates the reverse inbound channel and the reverse outbound channel; according to the Upstreamsublabel object carried in the Path message.
  • the value of Sublabel allocates the 2 # Sub-APS overhead of the CH2 channel to the service 2, and the reverse outgoing label Label allocated by the node N6 indicates the 2 # Sub-APS overhead.
  • the node N6 also allocates the Sub-APS overhead in the reverse direction of the local node according to the local allocation, and allocates the reverse sub-Label, for example, if the service 2 is allocated the 1 # Sub-APS overhead of the CH8 channel, Then, the protection path of the service 2 is forwarded to the sub-label in the node N6 to indicate the 2 # Sub-APS overhead (that is, the downstream node N5 transmits the recovery information of the service 2 using the 1 # Sub-APS overhead of the CH8 channel).
  • the node N6 can establish a reverse binding relationship of the service 2 on the local node, which may include: Reverse Binding Interface, Reverse Inbound Channel, Reverse Inward Label, Reverse Outbound, Reverse Outbound, and Reverse Out Label.
  • the node N6 may use the number 1 of the 1 # Sub-APS overhead as the value of the Sublabel field in the Upstreamsublabel object, and send the Upstreamsublabel object to the node N5 through the Path message, thereby notifying the node of the Sub-APS overhead information allocated by the node N6 for the service 2. N5.
  • the last node N5 receives the Path message, and uses the routing information to calculate the reverse outgoing interface and the forward incoming interface of the protection path of the service 2 on the local node, and allocates the reverse outgoing channel and the forward incoming channel; according to the Upstreamsublabel object carried in the Path message.
  • the information is used to allocate the 1 # Sub-APS overhead of the CH8 channel to the service 2, and the reverse outgoing label labeled by the node N5 indicates the 1 # Sub-APS overhead.
  • the node N5 can establish the reverse binding relationship of the protection path of the service 2 on the local node, and can include: a reverse outgoing interface, a reverse outgoing channel, and a reverse outgoing label binding relationship.
  • the node N5 also allocates a Sub-APS overhead in the forward direction of the local node according to the local allocation, and allocates a forward incoming label. For example, if the service 2 is allocated the 1 # Sub-APS overhead of the CH8 channel, Then, the protection path of the service 2 is forwarded to the sub-label of the node 1 to indicate the 1 # Sub-APS overhead (that is, the upstream node N6 transmits the recovery information of the service 2 using the 1 # Sub-APS overhead of the CH8 channel); thus, the node N5
  • the forward binding relationship of the service 2 on the local node can be established, including: the binding relationship between the forward incoming interface, the forward incoming channel, and the forward incoming label.
  • Node N5 combines the forward and reverse binding relationships to establish a sub-label mapping relationship, which may include: a forward inbound interface, a forward incoming channel, a forward incoming sub-label, a reverse outgoing interface, a reverse outgoing channel, and a reverse The mapping binding relationship of the child Label.
  • the last node N5 can record the established binding relationship in the form of a data table for subsequent fast and accurate query.
  • the node N5 may use the number 1 of the 1 # Sub-APS overhead as the value of the Sublabel field in the Sublabel object, and send the Sublabel object to the node N6 through the Resv message, so that the Sub-APS overhead information allocated by the node N5 for the service 2 can be notified.
  • Node N6 Node N6.
  • the node N5 and the node N6 may carry the shared Mesh protection path flag in the Protection object in the Resv message sent to the upstream node, so as to indicate to each upstream node that the currently established LSP is a shared Mesh protection path, and each upstream node ( Node N6 and node N1 can carry the shared Mesh protection path according to the Protection object in the Resv message after receiving the Resv message.
  • the path flag indicates that the currently established LSP is a shared Mesh protection path, and then the corresponding process is started.
  • the node N6 receives the Resv message, and calculates the forward inbound interface and the forward outgoing interface of the protection path of the service 2 on the local node according to the routing information, and allocates the forward inbound channel and the forward outbound channel; the Sublabel of the Sublabel object carried according to the Resv message
  • the information in the field allocates the 1 # Sub-APS overhead of the CH8 channel to the service 2, and the forward outgoing label assigned by the node N6 indicates the 1 # Sub-APS overhead.
  • the node N6 also allocates a Sub-APS overhead in the forward direction of the local node for the protection path of the service 2 according to the local allocation, and allocates a forward incoming label. For example, if the service 2 is assigned 2 # Sub on the CH2 channel.
  • the protection path of the service 2 indicates the 2 # Sub-APS overhead in the forward incoming label of the node N6 (ie, the upstream node N1 transmits the recovery information of the service 2 using the 2 # Sub-APS overhead of the CH2 channel)
  • the node N6 can establish the forward binding relationship of the service 2 on the node, which may include: a forward inbound interface, a forward incoming channel, a forward incoming label, a forward outgoing interface, a forward outgoing channel, The binding relationship of the forward label.
  • the node N6 can establish a sub-label mapping relationship, which can be: a forward inbound interface, a forward incoming channel, a forward incoming label, a forward outgoing interface, and a reverse binding relationship that has been established when the Path message is received.
  • a sub-label mapping relationship can be: a forward inbound interface, a forward incoming channel, a forward incoming label, a forward outgoing interface, and a reverse binding relationship that has been established when the Path message is received.
  • Forward outgoing channel, forward outgoing Label forward ingoing Label
  • reverse inbound interface reverse incoming channel, reverse incoming label, reverse outgoing interface, reverse outgoing channel, and reverse outgoing label binding relationship.
  • the intermediate node N6 can record the established binding relationship in the form of a data table, so as to perform subsequent fast and accurate queries.
  • the node N6 may use the number 2 of the 2 # Sub-APS overhead as the value of the Sublabel field in the Sublabel object, and send the Sublabel object to the node N1 through the Resv message, thereby notifying the node of the Sub-APS overhead information allocated by the node N6 for the service 2. Nl.
  • the first node N1 receives the Resv message, calculates the forward outgoing interface of the protection path of the service 2 on the local node according to the routing information, and allocates the forward outgoing channel; according to the information in the Sublabel field of the Sublabel object carried by the Resv, the CH2 channel is 2 # Sub-APS overhead is allocated to service 2, and the forward outgoing label assigned by node N1 indicates 2 # Sub-APS overhead.
  • the node N1 can establish the forward binding relationship of the service 2 on the local node, including: the binding relationship between the forward outgoing interface, the forward outgoing channel, and the forward outgoing label.
  • Node N1 combines the forward and reverse binding relationships to establish a sub-label mapping relationship, which may include: The mapping binding relationship to the outgoing interface, the forward outgoing channel, the forward outgoing Label, the reverse incoming interface, the reverse incoming channel, and the reverse incoming sub-label.
  • the first node N1 can record the established binding relationship in the form of a data table for subsequent fast and accurate query.
  • each node on the protection path of the service 2 allocates Sub-APS overhead for the service 2, and each node uses the Sub-APS overhead allocated for the service 2 to carry the recovery information of the transport service 2.
  • the specified Sub-APS overhead information may be carried in the Sublabel ERO sub-object and sent to the downstream nodes through the Path message.
  • each node After receiving the Path message, each node allocates the corresponding Sub-APS overhead according to the Sublabel ERO sub-object information in the ERO carried by the node, and uses the corresponding sub-label to indicate.
  • the Sub-APS overhead information that is allocated in the reverse direction may be carried in the Sublabel RRO sub-object, added to the RRO object, and sent to the RRO object through the Path message.
  • the downstream node adds the Sub-APS overhead information for the forward allocation to the Sublabel RRO sub-object, adds it to the RRO object, and sends it to the upstream node through the Resv message.
  • the RRO object carried by the Path message has the Sub-APS overhead information used by all the nodes on the protection path of the service 2 in the reverse direction of the service 2; when the Resv message is transmitted to the first node In the case of N1, the RRO object carried by the RRO object has the Sub-APS overhead information that all nodes on the protection path of the service 2 are using in the forward direction of the service 2.
  • the first node N1 (or the last node N5) of the service 2 can detect the fault, switch the service 2 to the protection path, and find the sub-label mapping relationship of the service 2, and the corresponding Sub-APS
  • the state of the overhead is changed to recovery, and the recovery information is sent to other nodes through the APS overhead.
  • each node finds the corresponding sub-label mapping relationship according to the specific characteristics of the recovery information, establishes a corresponding connection, and continues to transmit recovery information to other nodes through the APS overhead to establish a protection path.
  • the connection up to the end node N5 (or the first node N1).
  • the last node N5 finds the corresponding sub-label mapping relationship according to the recovery information carried in the received APS overhead, and can switch the service 2 to the protection path and transmit the service 2 through the service 2 protection path. Enable business 2 to get a quick recovery.
  • the configuration process of the protection path of other services can be deduced by the above method. Scene two
  • This scenario can be applied to the scenario where all the services of the shared AMS are shared by the shared Mesh.
  • the APS overhead is not divided.
  • the shared AMS overhead is shared by all the services protected by the Mesh.
  • the service distinguisher of the service to be switched (the service distinguisher is used to identify the differentiated service, and the service distinguisher can determine which service is), and is carried in the recovery message (for example, the recovery information may include only the distinguisher information)
  • the APS overhead of the shared channel is used for the transmission.
  • the nodes on the protection path can establish corresponding connections according to the service classifiers carried in the APS, and switch the corresponding services.
  • the sub-label corresponds to the service distinguisher, and the sub-label is allocated, which is equivalent to the allocation service discriminator, and the sub-label can carry the service discriminator.
  • a shared Mesh protection path flag may be carried in the protection object of the Path message that creates the shared Mesh protection path, and is used to indicate that the Path message creates a shared Mesh protection path. See Figure 4-d. The following takes the process of creating a shared Mesh protection path for Service 2 as an example.
  • the node N1 calculates the reverse incoming interface of the protection path of the service 2 on the local node according to the routing information, and allocates the reverse incoming channel; allocates the service distinguisher for the reverse direction of the service 2, and allocates the reverse entry.
  • Label for example, if the service distinguisher 2 is allocated for the service 2, the protection path of the service 2 indicates the service distinguisher 2 at the reverse entry label of the node N1 (ie, the service indicating the service 2 transmitted by the downstream node N6 includes the service The distinguisher 2); the node N1 can establish a reverse binding relationship, and can include: a reverse inbound interface, a reverse incoming channel, and a reverse incoming label binding relationship.
  • the node N1 can use the number 2 of the traffic distinguisher 2 as the value of the Sublabel in the Upstreamsublabel object, and send the Upstreamsublabel object to the node N6 through the Path message, thereby notifying the node N6 of the service distinguisher information allocated by the node N1 for the service 2.
  • the node N1 and the node N6 may carry the shared Mesh protection path flag in the Protection object in the Path message sent to the downstream node, so as to indicate to the respective downstream nodes that the currently established LSP is a shared Mesh protection path, and each downstream node ( The node N6 and the node N5 may, after receiving the Path message, carry the shared Mesh protection path flag according to the Protection object in the Path message, and clarify that the currently established LSP is a shared Mesh protection path, and then start the corresponding process. - Description.
  • the node N1 needs to give a recommendation to the service distinguisher allocated by the node N6, the node N1
  • the value of the sub-label of the service distinguisher for indicating the recommended allocation may be used as the value of the Sublabel field in the Suggested Sublabel object, and the recommended service classifier information may be carried by carrying the Suggested Sublabel object in the Path message;
  • the node N1 may use the value of the sub-label indicating the range of the service classifier that defines the allocation as the value of the Sublabel field in the Sublabel Set object,
  • the Sublabel Set object is carried in the Path message to carry the limited range information of the service distinguisher.
  • the node N1 may, for example, use the value of the sub-tag for indicating the service classifier of the specified allocation as the Sublabel ERO sub-sub
  • the value of the Sublabel field in the object is implemented by carrying the Sublabel ERO sub-object in the ERO object of the Path message.
  • the node N6 receives the Path message, and uses the routing information to calculate the reverse inbound interface and the reverse outbound interface of the protection path of the service 2 on the local node, and allocates the reverse inbound channel and the reverse outbound channel; according to the Upstreamsublabel object carried in the Path message.
  • the value of Sublabel, the service distinguisher 2 is assigned to the service 2
  • the reverse outgoing label of the node N6 is assigned to the service distinguisher 2.
  • the node N6 also allocates a service classifier for the service 2 in the reverse direction of the node according to the local allocation, and allocates a reverse-entry label. For example, if the service classifier 1 is allocated for the service 2, the protection path of the service 2 The node N6 is forwarded to the sub-label to indicate the service distinguisher 1 (ie, the service distinguisher 1 is included in the recovery information indicating the service 2 transmitted by the downstream node N5). So far, the node N6 can establish the reverse of the service 2 on the node.
  • the binding relationship may include: a reverse incoming interface, a reverse incoming channel, a reverse incoming sub-label, a reverse outgoing interface, a reverse outgoing channel, and a reverse outgoing sub-label binding relationship.
  • the node N6 can use the number 1 of the traffic distinguisher 1 as the value of the Sublabel field in the Upstreamsublabel object, and send the Upstreamsublabel object to the node N5 through the Path message, thereby notifying the node N5 of the service distinguisher information allocated by the node N6 for the service 2.
  • the last node N5 receives the Path message, and uses the routing information to calculate the reverse outgoing interface and the forward incoming interface of the protection path of the service 2 on the local node, and allocates the reverse outgoing channel and the forward incoming channel; according to the Upstreamsublabel object carried in the Path message.
  • the service distinguisher 1 is assigned to the service 2
  • the reverse outgoing sub-label assigned by the node N5 indicates the service distinguisher 1.
  • the node N5 can establish a reverse binding relationship of the protection path of the service 2 on the node, which may include: a reverse outbound interface, a reverse outbound channel, and a reverse The binding relationship of the Label.
  • the node N5 also allocates a service classifier for the service 2 in the forward direction of the node according to the local allocation, and allocates a forward incoming label. For example, if the traffic distinguisher 1 is allocated for the service 2, the protection path of the service 2
  • the forward incoming sub-label of the node N5 indicates the service distinguisher 1 (ie, the service distinguisher 1 is included in the recovery information indicating the service 2 transmitted by the upstream node N6); thus, the node N5 can establish the positive of the service 2 on the node
  • the binding relationship includes: a forward inbound interface, a forward incoming channel, and a forward incoming label.
  • Node N5 combines the forward and reverse binding relationships to establish a sub-label mapping relationship, which may include: a forward inbound interface, a forward incoming channel, a forward incoming sub-label, a reverse outgoing interface, a reverse outgoing channel, and a reverse The mapping binding relationship of the child Label.
  • the last node N5 can record the established binding relationship in the form of a data table for subsequent fast and accurate query.
  • the node N5 may use the number 1 of the traffic distinguisher 1 as the value of the Sublabel field in the Sublabel object, and send the Sublabel object to the node N6 through the Resv message, thereby notifying the node N6 of the service distinguisher information allocated by the node N5 for the service 2. .
  • the node N5 and the node N6 may carry the shared Mesh protection path flag in the Protection object in the Resv message sent to the upstream node, so as to indicate to each upstream node that the currently established LSP is a shared Mesh protection path, and each upstream node ( After the Resv message is received, the node N6 and the node N1 can carry the shared Mesh protection path flag according to the Protection object in the Resv message, and clarify that the currently established LSP is the shared Mesh protection path, and then start the corresponding process. - Description.
  • the node N6 receives the Resv message, and calculates the forward inbound interface and the forward outgoing interface of the protection path of the service 2 on the local node according to the routing information, and allocates the forward inbound channel and the forward outbound channel; the Sublabel of the Sublabel object carried according to the Resv message In the field, the traffic distinguisher 1 is assigned to the service 2, and the forward outgoing label assigned by the node N6 indicates the traffic distinguisher 1.
  • the node N6 also allocates a service classifier in the forward direction of the node for the protection path of the service 2 according to the local allocation, and allocates a forward incoming label. For example, if the service distinguisher 2 is allocated for the service 2, the service 2 The protection path indicates that the traffic distinguisher 2 is in the forward incoming label of the node N6 (ie, the service distinguisher 2 is included in the recovery information indicating the service 2 transmitted by the upstream node N1).
  • the node N6 can establish the forward binding relationship of the service 2 on the node, which may include: a forward inbound interface, a forward incoming channel, a forward incoming sub-label, a forward outgoing interface, a forward outgoing channel, and a positive The binding relationship to the child Label.
  • the node N6 can establish a sub-label mapping relationship, which can be: a forward inbound interface, a forward incoming channel, a forward incoming label, a forward outgoing interface, and a reverse binding relationship that has been established when the Path message is received.
  • a sub-label mapping relationship can be: a forward inbound interface, a forward incoming channel, a forward incoming label, a forward outgoing interface, and a reverse binding relationship that has been established when the Path message is received.
  • Forward outgoing channel, forward outgoing Label forward ingoing Label
  • reverse inbound interface reverse incoming channel, reverse incoming label, reverse outgoing interface, reverse outgoing channel, and reverse outgoing label binding relationship.
  • the intermediate node N6 can record the established binding relationship in the form of a data table, so as to perform subsequent fast and accurate queries.
  • the node N6 may use the number 2 of the traffic distinguisher 2 as the value of the Sublabel field in the Sublabel object, and send the Sublabel object to the node N1 through the Resv message, thereby notifying the node N1 of the service distinguisher information allocated by the node N6 for the service 2.
  • the first node N1 receives the Resv message, calculates the forward outgoing interface of the protection path of the service 2 on the local node according to the routing information, and allocates the forward outgoing channel.
  • the service distinguisher 2 is allocated to the service according to the information of the Sublabel object carried by the Resv. 2, the forward outgoing label Label assigned by the node N1 indicates the service distinguisher 2.
  • the node N1 can establish the forward binding relationship of the service 2 on the local node, including: the forward outgoing interface, the forward outgoing channel, and the forward outgoing label binding relationship.
  • Node N1 combines the forward and reverse binding relationships to establish a sub-label mapping relationship, which may include: a forward outgoing interface, a forward outgoing channel, a forward outgoing label; a reverse incoming interface, a reverse incoming channel, and a reverse The mapping binding relationship of the sub-label.
  • the first node N1 can record the established binding relationship in the form of a data table for subsequent fast and accurate query.
  • each node on the protection path of the service 2 allocates a service classifier for the service 2, and the service information of the service 2 transmitted by each node includes the allocated service classifier.
  • the service distinguisher information may be carried in the Sublabel ERO sub-object and sent to the downstream nodes through the Path message. After receiving the Path message, each node allocates a corresponding service classifier according to the Sublabel ERO sub-object information in the ERO carried by the node, and uses the corresponding sub-label to indicate.
  • the traffic distinguisher information for the reverse assignment is carried in the Sublabel RRO sub-object, added to the RRO object, and sent to the downstream node through the Path message; the traffic distinguisher information allocated for the forward direction is placed in the Sublabel RRO sub-object, added to the RRO In the object, it is sent to the upstream node through a Resv message.
  • the RRO object carried by the Path message has the service distinguisher information used by all the nodes on the protection path of the service 2 in the reverse direction of the service 2; when the Resv message is transmitted to the first node N1
  • the RRO object carried by the RRO object has the traffic distinguisher information that all nodes on the protection path of the service 2 are using in the service 2 forward.
  • the first node N1 (or the last node N5) of the service 2 can detect the fault, switch the service 2 to the protection path, find the sub-label mapping relationship of the service 2, and the corresponding APS overhead.
  • the state is modified to be restored, and the recovery information of the distinguisher information carrying the service 2 is sent to other nodes through the APS overhead.
  • each node finds the corresponding sub-label mapping relationship according to the distinguisher information of the service 2 carried in the recovery information, establishes a corresponding connection, and continues to transmit the recovery information to other nodes through the APS overhead. , establish a connection on the protection path, until the end node N5 (or the first node N1).
  • the last node N5 finds the corresponding sub-label mapping relationship according to the recovery information carried in the received APS overhead, and can switch the service 2 to the protection path and transmit the service 2 through the service 2 protection path. Enable business 2 to get a quick recovery.
  • the configuration process of the protection path of other services can be deduced by the above method.
  • a sub-tag for indicating a specific feature of the service recovery information is allocated and transmitted by a node on the protection path, so that the upstream node or the downstream node of the node transmits the recovery information of the service accordingly.
  • each node on the protection path can directly determine the service to be restored when receiving the service recovery information, and the configuration operation is simple, and can provide reliable support for the automatic fast protection switching of the subsequent service.
  • an embodiment of the present invention further provides an optical network node.
  • an optical network node 500 may specifically include: a receiving module 510, a first allocating module 520, and a recovery information sending module 530.
  • the receiving module 510 is configured to receive a Resv message sent by the second node, where the Resv message carries a second forward sub-label allocated by the second node for the protection path of the first service, where the second forward sub-label is used to indicate the bearer The specific characteristics of the recovery information of the first service.
  • the specific feature of the recovery information of the first service may include, for example, a specific identifier included in the recovery information of the first service (for example, a service distinguisher), a specific data structure that the recovery information of the first service has, and a recovery of the first service.
  • a specific identifier included in the recovery information of the first service for example, a service distinguisher
  • a specific data structure that the recovery information of the first service has for example, a specific data structure that the recovery information of the first service has, and a recovery of the first service.
  • the identity of the sub-APS overhead of the information eg, the number of sub-overheads or other related features.
  • the first distribution module 520 is configured to allocate, according to the second forward incoming subtag, a first forward outgoing subtag for the protection path of the first service, where the first forward subtag and the second forward subtag have Correspondence relationship.
  • the second forward sub-label allocated by the second node to the protection path of the first service may be any information that can indicate a specific feature of the recovery information of the first service, for example, the sub-tag can be Demonstrating one or more of the following specific characteristics of the recovery information of the first service: the specific identifier included in the recovery information of the first service, the specific data structure of the recovery information of the first service, and the recovery information carrying the first service The specific number of sub-APS overhead numbers, etc.
  • the recovery information sending module 530 is configured to: when the working path of the first service is faulty, transmit the recovery information of the first service to the second node according to the indication of the first forward outgoing sub-tab.
  • the second node may be the last node of the protection path of the first service, or may be the intermediate node of the protection path of the first service, and the optical network node 500 is the upstream node of the second node.
  • the second node may carry the allocated second forward sub-label in the second type of message, and use the signaling message to protect the second forward sub-label to the first service.
  • the upstream node on the path sends, in order to obtain the optical network node 500 of the second forward sub-label, correspondingly allocates a first forward sub-label (wherein the second forward sub-label and the first forward-out
  • the values of the sub-tags may be equal, or have a corresponding derivation correspondence.
  • the first forward-out sub-label corresponding to the optical network node 500 is also used to indicate the specific feature of the recovery information of the first service, and the first forward direction.
  • the specific label of the first service recovery information indicated by the sub-label and the second forward sub-label is the same).
  • the optical network node 500 may transmit the recovery information of the first service to the second node according to the indication of the first forward outgoing sub-tag. And the first When the two nodes receive the recovery information of the first service transmitted by the optical network node 500, the two nodes can directly determine the service to be restored as the first service according to the indication of the second forward incoming sub-label. Automatically switch the first service to its protection path for transmission.
  • the optical network node 500 may further include:
  • a route calculation module configured to calculate a forward outgoing interface of the protection path of the first service on the optical network node 500 according to the routing information, and allocate a forward outgoing channel to the protection path of the first service;
  • a binding relationship establishing module configured to establish a forward binding relationship of the protection path of the first service on the optical network node 500, where the forward binding relationship includes a forward path of the protection path of the first service on the optical network node 500 a mapping binding relationship between the outbound interface, the forward outgoing channel, and the first forward outgoing subtag;
  • the protection switching module is configured to: when the working path of the first service is faulty, establish a forward binding relationship established by the module according to the binding relationship, and switch the first service to the protection path of the first service.
  • the route calculation module may be further configured to: calculate, according to the routing information, a reverse ingress interface of the protection path of the first service on the optical network node, and be the first service The protection path is assigned to the reverse channel;
  • the optical network node 500 can also include:
  • a second allocation module configured to allocate a first reverse incoming sub-label to the protection path of the first service, where the first reverse-input sub-label is used to indicate a specific feature of the recovery information of the first service;
  • a first message sending module configured to send, by using a first type of message, the first reverse incoming sub-tag to a second node on a protection path of the first service, where the first type of message further carries the first service The indication of the protection path.
  • the binding relationship establishing module may be further configured to: establish a reverse binding relationship of the protection path of the first service on the optical network node 500, where the reverse binding relationship may include the protection path of the first service on the optical network node 500.
  • the route calculation module may be further configured to calculate, according to the routing information, a forward inbound interface of the protection path of the first service on the optical network node 500, and serve as a protection path of the first service. Allocating positive ingress channels;
  • Optical network node 500 can also include:
  • a third allocation module configured to allocate, by the protection path of the first service, a first forward sub-label, where the first forward-input sub-label is used to indicate a specific feature of the recovery information of the first service;
  • the forward binding relationship established by the binding relationship establishing module may further include: the protection path of the first service is bound to the forward inbound interface, the forward ingress channel, and the mapping of the first forward ingress subtag on the optical network node 500.
  • a second message sending module configured to send, by using the second type of message, the first forward incoming sub-label to the third node on the protection path of the first service.
  • each downstream node may add a forward-input sub-label assigned to the first service to the second type of message
  • the optical network node 500 may further include:
  • the sub-tag collection module is configured to collect and record a forward-input sub-label assigned by each downstream node carried in the received second-type message to the protection path of the first service.
  • optical network node 500 of this embodiment may be used as the node N1 or N6 in the foregoing method embodiment, and may be used to implement all the technical solutions in the foregoing method embodiments, and the functions of the respective functional modules may be according to the foregoing method.
  • the method in the embodiment is specifically implemented.
  • an embodiment of the present invention further provides an optical network node.
  • an optical network node 600 may specifically include: a first allocation module 610 and a message sending module 620.
  • the first allocation module 610 is configured to allocate a second forward ingress subtag to the protection path of the first service, where the second forward ingress subtag is used to indicate a specific feature of the recovery information of the first service.
  • the specific feature of the recovery information of the first service may include, for example, a specific identifier included in the recovery information of the first service (for example, a service distinguisher), a specific data structure that the recovery information of the first service has, and a recovery of the first service.
  • a specific identifier included in the recovery information of the first service for example, a service distinguisher
  • a specific data structure that the recovery information of the first service has for example, a specific data structure that the recovery information of the first service has, and a recovery of the first service.
  • the identity of the sub-APS overhead of the information eg, the number of sub-overheads or other related features.
  • the message sending module 620 is configured to send the second forward incoming subtag to the first node on the protection path of the first service by using the second type of message.
  • the first node may be the first node of the protection path of the first service, or may be the intermediate node of the protection path of the first service, and the optical network node 600 is the downstream node of the first node.
  • the first allocation module 610 may be specifically configured to protect the first service.
  • the path allocates a second forward-input sub-label, and the second forward-input sub-label is used to indicate a sub-automatic protection switching overhead of the recovery information of the first service or a service distinguisher carried in the recovery information of the first service.
  • the optical network node 600 may carry the allocated second forward sub-label in the second type of message, and use the signaling message to forward the second forward sub-label to the first service.
  • the upstream node on the protection path sends, so as to obtain the first node of the second forward sub-label, and correspondingly allocates the first forward sub-label (wherein the second forward sub-label and the first forward-out
  • the values of the sub-tags may be equal, or have a corresponding derivation correspondence.
  • the first forward-out sub-label corresponding to the first node is also used to indicate a specific feature of the recovery information of the first service, and the first forward direction is The subtag is the same as the specific feature of the first service recovery information indicated by the second forward subtag.
  • the first node when the first node learns that the working path of the first service is faulty, it can transmit the recovery information of the first service to the optical network node 600 according to the indication of the first forward outgoing sub-tag.
  • the optical network node 600 receives the recovery information of the first service that is transmitted by the first node, the optical network node 600 can directly determine, according to the indication of the second forward incoming sub-label, that the service to be restored is the first service, and further The first service can be automatically switched to its protection path for transmission.
  • the optical network node 600 may further include:
  • a receiving module configured to receive a first type of message sent by the first node, where the first type of message carries the first node to allocate a first reverse incoming subtag for the protection path of the first service, where the first reverse entry
  • the label is used to indicate a specific feature of the recovery information that carries the first service, and the first type of message further carries the indication information of the protection path that creates the first service.
  • a second allocation module configured to allocate, according to the first reverse incoming subtag, the second reverse outgoing subtag, the second reverse outgoing subtag, and the first reverse incoming subtag, for the protection path of the first service Have a corresponding relationship;
  • a recovery information sending module configured to: when the working path of the first service is faulty, transmit the recovery information of the first service to the first node according to the indication of the second reverse outgoing sub-tag.
  • the optical network node 600 may further include:
  • a route calculation module configured to calculate, according to the routing information, a reverse outgoing interface and a reverse outgoing channel of the protection path of the first service on the optical network node 600;
  • the reverse binding relationship establishing module establishes a protection path of the first service on the optical network node 600.
  • a reverse binding relationship where the reverse binding relationship includes a mapping relationship between the reverse outgoing interface, the reverse outgoing channel, and the second reverse outgoing sub-label of the protection path of the first service on the optical network node 600;
  • the first protection switching module is configured to switch the first service to the protection path of the first service according to the reverse binding relationship established by the reverse binding relationship establishment module when the working path of the first service is faulty.
  • the route calculation module may be further configured to calculate, according to the routing information, a forward ingress interface of the protection path of the first service on the second node, and allocate a forward ingress channel to the protection path of the first service;
  • the optical network node 600 can also include:
  • the forward binding relationship establishing module establishes a forward binding relationship of the protection path of the first service on the second node, where the forward binding relationship includes a forward ingress interface of the protection path of the first service on the second node a mapping binding relationship between the forward ingress channel and the second forward ingress subtag;
  • the second protection switching module is configured to switch the first service to the protection path of the first service according to the forward binding relationship established by the forward binding relationship when the working path of the first service is faulty.
  • the first allocation module 610 may be specifically configured to follow the recommendation of the first node or according to the local allocation, The protection path of the first service allocates a second forward sub-label.
  • the first allocation module 610 is specifically configured to specify the range of the allocated sub-tags at the first node. Allocating a second forward sub-label to the protection path of the first service;
  • the first allocation module 610 may be specifically configured to: indicate, according to the indication information of the sub-tag of the allocated sub-tag according to the first node. , assigning a second forward sub-label to the protection path of the first service.
  • each of the upstream nodes may add a reverse-input sub-label assigned to the first service to the first type of message
  • the optical network node 600 may further include:
  • the sub-tag collection module is configured to collect and record the reverse-input sub-labels allocated by the respective upstream nodes carried in the received first-type message for the protection path of the first service.
  • optical network node 600 of this embodiment may be as described in the foregoing method embodiment.
  • the point N5 or N6 may be used to implement all the technical solutions in the foregoing method embodiments, and the functions of the respective functional modules may be specifically implemented according to the method in the foregoing method embodiment.
  • the specific implementation process refer to the related description in the foregoing embodiment. , will not repeat them here.
  • an embodiment of the present invention further provides an optical network system.
  • an optical network system may include: a first node 710 and a second node 720.
  • the second node 720 is configured to allocate, by the protection path of the first service, a second forward incoming sub-label, where the second forward-input sub-label is used to indicate a specific feature of the first service, and the second type of the message Transmitting the second forward ingress subtag to the first node 710 on the protection path of the first service.
  • a first node 710 configured to receive a second type of message sent by the second node 720, where the Resv message carries a second forward sub-label allocated by the second node 720 for the protection path of the first service; Assigning a first forward outgoing sub-label to the protection path of the first service, the first forward outgoing sub-label and the second forward-input sub-label have a corresponding relationship; At this time, the recovery information of the first service is transmitted to the second node 720 according to the indication of the first forward outgoing sub-tag.
  • the first node 710 is further configured to: allocate, by the first service, a first reverse incoming sub-label, where the first reverse incoming sub-label is used to indicate the first service Recovering a specific feature of the information; transmitting, by the first type of message, the first reverse incoming subtag to the second node 720 on the protection path of the first service;
  • the second node 720 may receive the first type of message sent by the first node 710, where the first type of message may carry the first reverse incoming subtag allocated by the first node 710 for the protection path of the first service; a reverse-input sub-label, the second reverse-out sub-label is allocated to the protection path of the first service, and the second reverse-out sub-label and the first reverse-in-sub-label have a corresponding relationship;
  • the recovery information of the first service is transmitted to the first node 710 according to the indication of the second reverse outgoing sub-tag.
  • first node 710 in this embodiment may be the node N1 or N6 in the foregoing method embodiment
  • second node 720 may be the node N5 or N6 in the foregoing method embodiment.
  • functions of the respective functional modules may be specifically implemented according to the method in the foregoing method embodiments.
  • specific implementation process refer to the related description in the foregoing embodiments, and details are not described herein again.
  • a sub-tag for indicating a specific feature of the service recovery information is allocated and transmitted by a node on the protection path, so that the upstream node or the downstream node of the node transmits the recovery information of the service accordingly.
  • each node on the protection path can directly determine the service to be restored when receiving the service recovery information, and the configuration operation is simple, and can provide reliable support for the automatic fast protection switching of subsequent services.
  • the program can be stored in a computer readable storage medium.
  • the storage medium can include: Read-only memory (ROM, Read-Only Memory) or random access memory (RAM, Random Access Memory), disk or optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

共享 Mesh保护的实现方法和设备及光网络系统 本申请要求了 2009年 12月 18日提交的， 申请号为 200910261627.1 , 发 明名称为 "共享 Mesh保护的实现方法和设备及光网络系统"的中国申请的优 先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域，具体涉及共享 Mesh保护的实现方法和设备及 光网络系统。 背景技术
光网络由于具备很高的业务传送速率而被广泛应用， 可以通过建立一条 或多条满足客户业务带宽需求的光网络连接， 传送客户业务； 而业务传送的 可靠性是衡量光网络是否稳定的重要指标。
光网络业务传送的可靠性可以利用各种保护和恢复技术来实现， 例如可 以利用控制平面的重路由技术来对光网络连接进行恢复。 控制平面是运行于 光网络中的一个控制网络， 由光网络提供控制通道， 并在其中运行通用多协 议标签交换 ( GMPLS, Generalized Multi-Protocol Label Switching )协议族。 GMPLS协议族包括路由协议和信令协议， 其中， 路由协议主要负责收集光网 络拓朴信息（包括节点和链路信息）， 计算连接经过的路径； 信令协议主要负 责根据计算出的路径建立光网络连接。
在使用控制平面的情况下， 可以为连接提供重路由功能， 即当传送客户 业务的连接（工作连接）出现故障时， 控制平面使用预先配置的恢复路径（或 重新计算路径）， 建立新的连接（恢复连接）， 传送客户业务。 这种方式不需 要一直为客户业务提供两条连接， 只需在连接故障的情况下重新提供另外一 条可用连接， 因此带宽利用率较高， 但由于使用控制平面的恢复技术， 故障 恢复的时间通常较长。其中，釆用 GMPLS控制平面技术建立起来的连接通常 称作标签交换路径（LSP, Label Switch Path ), LSP由首节点触发建立， 重路 由过程也是由首节点触发。
为进一步提高资源利用率，提出釆用共享 Mesh保护技术为客户业务提供 传送服务，釆用共享 Mesh保护技术为客户业务提供传送服务的连接称作共享 Mesh保护业务。每个共享 Mesh保护业务包括一条工作路径和一条恢复路径。 两个共享 Mesh保护业务的工作路径是分离的， 其恢复路径可以共享通道资 源。 利用通道的自动保护倒换 ( APS, Automatic Protection Switching )开销来 传送共享 Mesh保护消息， 由于同一个通道可以给多条业务共享， 因此在通道 的 APS开销中需要能区分不同业务的消息。
现有技术主要通过网管手工配置实现共享 Mesh保护，但该方式对网管等 设备的依赖性很强， 且配置操作通常十分繁杂， 网络运行风险较大。 发明内容
本发明实施例提供共享 Mesh保护的实现方法和设备及光网络系统， 能够 让保护路径上的各节点简单准确的确定出待恢复的业务， 且配置操作简单， 进而可为后续进行业务的保护倒换提供可靠支持。
为解决上述技术问题， 本发明实施例提供以下技术方案：
本发明实施例提供一种共享 Mesh保护的实现方法， 包括：
第一节点接收第二节点发送的第二类型的消息， 所述第二类型的消息携 带第二节点为第一业务的保护路径分配的第二正向入子标签， 所述第二正向 入子标签用于指示承载第一业务的恢复信息的特定特征；
根据所述第二正向入子标签， 为第一业务的保护路径分配第一正向出子 标签， 所述第一正向出子标签和第二正向入子标签具有对应关系；
在获知第一业务的工作路径故障时， 按照所述第一正向出子标签的指示 向第二节点传送第一业务的恢复信息。
本发明实施例还提供一种共享 Mesh保护的实现方法， 包括：
第二节点为第一业务的保护路径分配第二正向入子标签， 所述第二正向 入子标签用于指示第一业务的恢复信息的特定特征；
通过第二类型的消息将所述第二正向入子标签向第一业务的保护路径上 的第一节点发送。
本发明实施例还提供一种光网络节点， 包括：
接收模块， 用于接收第二节点发送的第二类型的消息， 所述第二类型的 消息携带第二节点为第一业务的保护路径分配的第二正向入子标签， 所述第 二正向入子标签用于指示承载第一业务的恢复信息的特定特征； 第一分配模块， 用于根据所述第二正向入子标签， 为第一业务的保护路 径分配第一正向出子标签， 所述第一正向出子标签和第二正向入子标签具有 对应关系；
恢复信息发送模块， 用于在获知第一业务的工作路径故障时， 按照所述 第一正向出子标签的指示向第二节点传送第一业务的恢复信息。
本发明实施例还提供一种光网络节点， 包括：
第一分配模块， 用于为第一业务的保护路径分配第二正向入子标签， 所 述第二正向入子标签用于指示第一业务的恢复信息的特定特征；
消息发送模块， 用于通过第二类型的消息将所述第二正向入子标签向第 一业务的保护路径上的第一节点发送。
本发明实施例还提供一种光网络系统， 其特征在于， 包括
第二节点， 用于为第一业务的保护路径分配第二正向入子标签， 所述第 二正向入子标签用于指示第一业务的恢复信息的特定特征； 通过第二类型的 消息将所述第二正向入子标签向第一业务的保护路径上的第一节点发送。
第一节点， 用于接收第二节点发送的第二类型的消息， 所述第二类型的 消息携带第二节点为第一业务的保护路径分配的第二正向入子标签； 根据所 述第二正向入子标签， 为第一业务的保护路径分配第一正向出子标签， 所述 第一正向出子标签和第二正向入子标签具有对应关系； 在获知第一业务的工 作路径故障时， 按照所述第一正向出子标签的指示向第二节点传送第一业务 的恢复信息。
由上可见， 本发明实施例中， 由保护路径上的节点分配并传递用于指示 业务的恢复信息的特定特征的子标签， 以便于该节点的上游节点或下游节点 据此传送该业务的恢复信息， 进而可以实现保护路径上的各节点在接收到业 务的恢复信息时能够直接确定出待恢复的业务， 且配置操作简单， 可以为后 续进行业务的自动快速的保护倒换提供可靠的支持。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面 描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。 图 1-a是本发明实施例提供的一种消息传递方向指示示意图；
图 1-b是本发明实施例提供的一种光网络拓朴结构示意图；
图 2是本发明实施例一提供的一种共享 Mesh保护的实现方法流程图； 图 3是本发明实施例二提供的一种共享 Mesh保护的实现方法流程图； 图 4-a是本发明实施例三提供的一种共享 Mesh保护的实现方法流程图； 图 4-b是本发明实施例三提供的一种 APS开销划分示意图；
图 4-c是本发明实施例三提供的一种 APS开销分配示意图；
图 4-d是本发明实施例三提供的一种区分器分配示意图；
图 5是本发明实施例四提供的一种光网络节点示意图；
图 6是本发明实施例五提供的一种光网络节点示意图；
图 7是本发明实施例六提供的一种光网络系统示意图。 具体实施方式
本发明实施例提供共享 Mesh保护的实现方法和设备及光网络系统， 能够 让保护路径上的各节点简单准确的确定出待恢复的业务， 且配置操作简单， 进而可为后续进行业务的自动快速的保护倒换提供可靠的支持。
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有做 出创造性劳动前提下所获得的所有其他实施例 , 都属于本发明保护的范围。
本发明实施例中， 控制平面的信令协议例如可釆用 GMPLS带流量工程的 资源予贞留协议 ( RSVP-TE, Resource reSerVation Protocol-Traffic Engineering ), 本发明实施例中提到的消息和对象都可以是 GMPLS RSVP-TE中的消息和对 象。
首先参见图 1-a, 为便于理解描述， 可将业务数据从首节点传到末节点的 方向称为 Downstream方向， 也称为正向， 也就是 Path消息传递的方向； 业务数 据从末节点传到首节点的方向称为 Upstream方向， 也称为反向， 也就是 Resv 消息传递的方向。 其中， Path消息是 RSVP-TE定义的一种消息类型， 可以从源 节点 （首节点）沿着计算好的路由发往目的节点 （末节点）， 以通知沿途节点 建立连接； Resv消息也是 RSVP-TE定义的一种消息类型， 可以从目的节点发 往源节点， 与 Path消息配合使用可以建立一条双向连接。 当然， 双向业务才会 有反向， 若是单向业务， 则没有反向， 但无论是单向还是双向业务， 都会传 递和处理 Resv消息。
对于每个节点而言， 接收 Path消息的方向称为正向入方向， 发出 Path消息 的方向称为正向出方向， 接收 Resv消息的方向称为反向入方向， 发出 Resv消 息的方向称为反向出方向。 首节点和末节点之间的节点可称为中间节点， 中 间节点可以是 0个、 1个或多个。发出 Path消息的节点可称为上游节点，接收 Path 消息的节点是下游节点， 可以理解上游节点和下游节点是相对而言的， 当然， 首节点可称为其它各个节点的上游节点， 末节点可称为其它各个节点的下游 节点。
例如图 1-b所示的光网络中， 存在三条共享 Mesh保护业务， 其中， 实线 表示各条业务的工作路径， 虚线表示各条业务的保护路径。 由于三条业务的 工作路径相互分离， 因此其保护路径可以共享资源。 如业务 1和业务 2的保 护路径共享 2号通道 ( CH2 )资源， 业务 1和业务 3的保护路径共享 3号通道 ( CH3 ) 资源， 业务 2和业务 3的保护路径共享 8号通道（ CH8 ) 资源。
如图 1 -b所示， 在业务 1的工作路径中， 若节点 N1为首节点， 则节点 N2为 末节点， 在业务 1的保护路径中， 若节点 N1为首节点， 则节点 N6和 N7为中间 节点， 节点 N2为末节点， 当业务 1的工作路径故障时， 首节点 N1可以利用 2号 通道（CH2 ) 的 APS开销向节点 N6发送恢复信息， 启动自动保护倒换， 以将 业务 1切换到保护路径上传送， 以此类推。
本发明实施例中， 保护路径上的节点分配并下发用于指示业务的恢复信 息的特定特征的子标签（Label ) , 获得该子标签的上游节点或下游节点据此 传送该业务的恢复信息， 进而使得保护路径上的各节点在接收到业务的恢复 信息时能够直接确定出待恢复的业务。
下面介绍保护路径上分配并下发子标签的节点 （例如第二节点） 的处理 过程，参见图 2 ,本发明实施例一提供的一种共享 Mesh保护的实现方法， 包括：
210、 第二节点为第一业务的保护路径分配第二正向入子标签， 该第二正 向入子标签用于指示第一业务的恢复信息的特定特征。 其中， 第一业务的恢复信息的特定特征例如可以包括： 第一业务的恢复 信息包含的特定标识 （例如业务区分器） 、 第一业务的恢复信息具有的特定 数据结构、承载第一业务的恢复信息的子 APS开销的标识（例如子开销的编号） 或其它相关的特征。
在一种应用场景下， 第二节点为第一业务的保护路径分配的第二正向入 子标签可以是， 能够指示出第一业务的恢复信息的特定特征的任意信息， 例 如该子标签可以指示出第一业务的恢复信息的如下特定特征中的一个或多 个： 第一业务的恢复信息包含的特定标识、 第一业务的恢复信息具有的特定 数据结构或承载第一业务的恢复信息的子 APS开销的编号等等特定特征。
220、 通过第二类型的消息将第二正向入子标签向第一业务的保护路径上 的第一节点发送。
其中， 本发明各实施例中提及的第二类型的消息例如可以是 Resv消息， 或者其它具有类似功能的消息， 第二类型的消息中还可携带创建第一业务的 保护路径的指示信息， 第二类型的消息携带的创建第一业务的保护路径的指 示信息可以是任意的， 例如可通过第二类型的消息中的一个指示位来携带该 指示信息， 或者直接利用该消息中携带的子标签作为创建第一业务的保护路 径的指示信息， 当然也可选择其它方式。
可以理解， 第二节点可以是第一业务的保护路径的末节点， 也可以是第 一业务的保护路径的中间节点， 第一节点为第二节点的上游节点。
在一种应用场景下， 第二节点可以将分配的第二正向入子标签携带在第 二类型的消息中， 利用该信令消息将该第二正向入子标签向第一业务的保护 路径上的上游节点发送， 以便于获得该第二正向入子标签的第一节点， 对应 的分配第一正向出子标签（其中， 第二正向入子标签和第一正向出子标签的 值可以相等， 或具有相应的推导对应关系， 当然， 第一节点对应分配的第一 正向出子标签同样用于指示第一业务的恢复信息的特定特征， 且第一正向出 子标签和第二正向入子标签指示的第一业务恢复信息的特定特征相同）。
进一步的， 当第一节点在获知第一业务的工作路径故障时， 第一节点便 可以按照第一正向出子标签的指示向第二节点传送第一业务的恢复信息。 而 第二节点在接收到第一节点传送的第一业务的恢复信息时， 便可以直接根据 其分配的第二正向入子标签的指示， 确定出待恢复的业务为第一业务， 进而 可以快速的将第一业务自动倒换到其保护路径上进行传送。
举例来说， 例如第二节点分配的第二正向入子标签指示第一业务的恢复 信息携带业务区分器 1 , 第二节点可将第二正向入子标签携带在第二类型的消 息中发送给第一节点； 第一节点可根据获得的第二正向入子标签对应分配第 一正向出子标签（例如第二正向入子标签和第一正向出子标签的值相等）， 当 获知第一业务的工作路径故障时， 第一节点便可以按照第一正向出子标签的 指示， 向第二节点传送携带业务区分器 1的恢复信息； 第二节点在接收到第一 节点传送的携带有业务区分器 1的恢复信息时， 便可根据其携带的业务区分器 信息直接确定出该待恢复的业务为第一业务。
对于各个共享保护业务， 可按照上述方式以此类推。 可以理解， 利用该 机制第二节点在接收到恢复信息时， 可以简单的确定出待恢复的业务， 进而 为后续进行该业务自动快速的保护倒换提供了可靠支持。
由上可见， 本发明实施例中， 由保护路径上的节点分配并传递用于指示 业务的恢复信息的特定特征的子标签， 以便于该节点的上游节点或下游节点 据此传送该业务的恢复信息， 进而可以实现保护路径上的各节点在接收到业 务的恢复信息时能够直接确定出待恢复的业务， 且配置操作简单， 可以为后 续进行业务的自动快速的保护倒换提供可靠的支持。
进一步的， 为第一业务的保护路径分配第二正向入子标签之前， 第二节 点还可以接收第一节点发送的第一类型的消息， 其中， 本发明各实施例中提 及的第一类型的消息例如可以是 Path消息， 或者其它具有类似功能的消息， 第 二节点接收的该第一类型的消息可携带第一节点为第一业务的保护路径分配 第一反向入子标签， 该第一反向入子标签用于指示承载第一业务的恢复信息 的特定特征（例如指示第一业务的恢复信息的子自动保护倒换开销或第一业 务的恢复信息中携带的业务区分器）， 该第一类型的消息中还可携带创建第一 业务的保护路径的指示信息。
在一种应用场景下， 第二节点还可以根据该第一反向入子标签， 为第一 业务的保护路径分配第二反向出子标签， 其中， 第二反向出子标签和所述第 一反向入子标签具有对应关系； 并可以在获知第一业务的工作路径故障时， 按照该第二反向出子标签的指示向第一节点传送第一业务的恢复信息。
在一种应用场景下， 第二节点还可以根据路由信息计算第一业务的保护 路径在第二节点上的反向出接口、 反向出通道； 建立第一业务的保护路径在 第二节点上的反向绑定关系， 其中， 该反向绑定关系可包括第一业务的保护 路径在第二节点上的反向出接口、 反向出通道和上述第二反向出子标签的映 射绑定关系； 并可在获知第一业务的工作路径故障时， 根据建立的反向绑定 关系， 将第一业务倒换到第一业务的保护路径上。
在一种应用场景下， 第二节点还可以根据路由信息计算第一业务的保护 路径在第二节点上的正向入接口， 并为第一业务的保护路径分配正向入通道； 并可建立第一业务的保护路径在第二节点上的正向绑定关系， 该正向绑定关 系可包括第一业务的保护路径在第二节点上的正向入接口、 正向入通道和上 述第二正向入子标签的映射绑定关系； 并可以在获知第一业务的工作路径故 障时， 根据建立的正向绑定关系， 将第一业务倒换到第一业务的保护路径上。
在一种应用场景下， 若上述第一类型的消息还携带第一节点建议分配的 子标签的指示信息； 第二节点可按照第一节点的建议或根据本地分配情况， 为第一业务的保护路径分配第二正向入子标签；
在一种应用场景下， 若上述第一类型的消息还携带第一节点指定分配的 子标签的范围的指示信息； 第二节点则可在第一节点指定分配的子标签的范 围内， 为第一业务的保护路径分配第二正向入子标签；
在一种应用场景下， 若上述第一类型的消息还携带首节点指定分配的子 标签的指示信息； 第二节点则可按照首节点指定分配的子标签的指示信息的 指示， 为第一业务的保护路径分配第二正向入子标签。
在一种应用场景下， 第二节点的各个上游节点可将其为第一业务的保护 路径分配的反向入子标签添加到第一类型的消息， 第二节点可收集并记录接 收到的第一类型的消息中携带的各个上游节点为第一业务的保护路径分配的 反向入子标签， 以便后续更好的维护和管理。 进一步的， 下面介绍保护路径上获取子标签的节点 （如第一节点） 的处 理过程， 参见图 3 , 本发明实施例二的一种共享 Mesh保护的实现方法， 包括： 310、 第一节点接收第二节点发送的第二类型的消息， 该第二类型的消息 携带第二节点为第一业务的保护路径分配的第二正向入子标签， 该第二正向 入子标签用于指示承载第一业务的恢复信息的特定特征。
其中， 第一业务的恢复信息的特定特征例如可以包括： 第一业务的恢复 信息包含的特定标识 （例如业务区分器） 、 第一业务的恢复信息具有的特定 数据结构、承载第一业务的恢复信息的子 APS开销的标识（例如子开销的编号） 或其它相关的特征。
可以理解， 第一节点可以是第一业务的保护路径的首节点， 也可以是第 一业务的保护路径的中间节点， 第二节点为第一节点的下游节点。
其中， 第二类型的消息还可以携带创建第一业务的保护路径的指示信息， 该创建第一业务的保护路径的指示信息可以是任意的， 该指示信息例如可以 是 Resv消息中一个特定的指示位携带的指示信息 , 或者直接是该信令消息中 携带的子标签， 当然也可以是第一节点可识别的其它指示信息。
320、 根据上述第二正向入子标签， 为第一业务的保护路径分配第一正向 出子标签， 该第一正向出子标签和第二正向入子标签具有对应关系。
其中， 第二正向入子标签和第一正向出子标签的值可以相等， 或具有相 应的推导对应关系， 当然， 第一节点对应分配的第一正向出子标签同样用于 指示第一业务的恢复信息的特定特征。
330、 在获知第一业务的工作路径故障时， 按照上述第一正向出子标签的 指示向第二节点传送第一业务的恢复信息。
进一步的， 当第一节点在获知第一业务的工作路径故障时， 第一节点便 可以按照第一正向出子标签的指示向第二节点传送第一业务的恢复信息。 而 第二节点在接收到第一节点传送的第一业务的恢复信息时， 便可以直接根据 其分配的第二正向入子标签的指示， 确定出待恢复的业务为第一业务， 进而 可以快速的将第一业务自动倒换到其保护路径上进行传送。
举例来说， 例如第二节点分配的第二正向入子标签指示承载第一业务的 恢复信息的子 APS开销的编号 1 , 第二节点可将第二正向入子标签携带在第二 类型的消息中发送给第一节点； 第一节点可根据获得的第二正向入子标签对 应分配第一正向出子标签（例如第二正向入子标签和第一正向出子标签的值 相等）， 当获知第一业务的工作路径故障时， 第一节点便可以按照第一正向出 子标签的指示， 利用 1号子 APS开销向第二节点传送恢复信息； 第二节点通过 1 号子 APS开销接收到第一节点传送的恢复信息时，便可根据承载恢复信息的子 APS开销的编号直接确定出该待恢复的业务为第一业务。
对于各个共享保护业务， 可按照上述方式以此类推。 可以理解， 第一节 点和第二节点均可按照上述方式传送业务的恢复信息， 第二节点在接收到恢 复信息时， 可以简单的确定出待恢复的业务， 进而为后续进行该业务自动快 速的保护倒换提供了可靠支持。
由上可见， 本发明实施例中由保护路径上的节点分配并传递用于指示业 务的恢复信息的特定特征的子标签， 以便于该节点的上游节点或下游节点据 此传送该业务的恢复信息， 进而可以实现保护路径上的各节点在接收到业务 的恢复信息时能够直接确定出待恢复的业务， 且配置操作简单， 可以为后续 进行业务的自动快速的保护倒换提供可靠的支持。
进一步的， 第一节点可以根据路由信息计算第一业务的保护路径在第一 节点上的正向出接口， 并为第一业务的保护路径分配正向出通道； 建立第一 业务的保护路径在第一节点上的正向绑定关系， 该正向绑定关系可包括第一 业务的保护路径在第一节点上的正向出接口、 正向出通道和第一正向出子标 签等的映射绑定关系； 在获知第一业务的工作路径故障时， 可根据上述建立 的正向绑定关系， 将第一业务倒换到第一业务的保护路径上。
在一种应用场景下， 对于双向业务， 第一节点还可根据路由信息计算第 一业务的保护路径在第一节点上的反向入接口， 并为第一业务的保护路径分 配反向入通道； 为第一业务的保护路径分配第一反向入子标签， 该第一反向 入子标签用于指示第一业务的恢复信息的特定特征（例如可指示承载第一业 务的恢复信息的子自动保护倒换开销或第一业务的恢复信息中携带的业务区 分器）； 并可通过第一类型的消息将该第一反向入子标签向第一业务的保护路 径上的第二节点发送， 该第一类型的消息中还携带创建第一业务的保护路径 的指示信息。
在一种应用场景下， 若第一节点为中间节点， 第一节点可根据路由信息 计算第一业务的保护路径在第一节点上的正向入接口， 并为第一业务的保护 路径分配正向入通道； 为第一业务的保护路径分配第一正向入子标签， 该第 一正向入子标签用于指示第一业务的恢复信息的特定特征； 上述正向绑定关 系还可包括： 第一业务的保护路径在第一节点上的正向入接口、 正向入通道 和上述第一正向入子标签的映射绑定关系； 并可通过第二类型的消息， 将上 述第一正向入子标签向第一业务的保护路径上的第三节点发送。
在一种应用场景下， 第一节点还可以在第一类型的消息携带其建议分配 的子标签的指示信息； 第二节点可按照第一节点的建议或根据本地分配情况， 为第一业务的保护路径分配第二正向入子标签；
在一种应用场景下， 第一节点还可以在第一类型的消息携带其指定分配 的子标签的范围的指示信息； 第二节点则可在第一节点指定分配的子标签的 范围内， 为第一业务的保护路径分配第二正向入子标签；
在一种应用场景下， 第一节点还可以在第一类型的消息携带首节点指定 分配的子标签的指示信息； 第二节点则可按照首节点指定分配的子标签的指 示信息的指示， 为第一业务的保护路径分配第二正向入子标签。
在一种应用场景下， 第二节点的各个上游节点可将其为第一业务的保护 路径分配的反向入子标签添加到第一类型的消息， 第二节点可收集并记录接 收到的第一类型的消息中携带的各个上游节点为第一业务的保护路径分配的 反向入子标签， 以便后续更好的维护和管理。
在一种应用场景下， 第一节点的各个下游节点可以将其为第一业务的保 护路径分配的正向入子标签添加到第二类型的消息中， 第一节点可以收集并 记录接收到的第二类型的消息中携带的各个下游节点为第一业务的保护路径 分配的正向入子标签， 以便后续更好的维护和管理。 实施例三
本实施例通过一个具体的应用场景， 对本发明技术方案进行更为具体的 介绍。 在一种应用场景下， 若将 APS开销划分成多个独立的物理开销通道， 即 划分成多个子 APS ( Sub-APS )开销， 分别分配给共享 Mesh保护业务的不同业 务所使用， 子 Label可以指示业务所使用的子 APS开销的标识 （例如子 APS开 销的编号） ， 在某个业务的工作路径发生故障时， 通过改变该业务所使用的 子 APS开销中的信息（即恢复信息） ， 以对该业务进行倒换； 若不对 APS开销 进行划分， 整个 APS开销被共享 Mesh保护业务的所有业务所共享使用， 则子 Label可以指示共享 Mesh保护业务的标识信息（例如业务区分器） ， 当某个业 务的工作路径发生故障时，在 APS开销中传送包含该业务的标识信息的恢复信 息， 以对该业务进行倒换。 下面以建立业务 S1 (共享 Mesh保护业务） 的保护 路径的过程为例， 进行说明。
其中， 本实施例以第一类型的消息为 Path消息， 第二类型的消息为 Resv 消息为例进行详细说明
参见图 4-a, 本发明实施例三的一种共享 Mesh保护的实现方法， 可包括：
401、 首节点根据路由信息计算出业务 S1的保护路径在本节点的反向入接 口， 并分配反向入通道； 根据本地的分配情况， 为业务 S1的保护路径对应在 本节点的反向入方向分配子 Label (简称反向入子 Label ) 。
首节点建立业务 SI的在本节点的反向绑定关系， 包括： 反向入接口、 反 向入通道和反向入子 Label的绑定关系， 首节点的反向出接口、 反向出通道和 反向出子 Label可以没有。
首节点通过 Path消息将该分配的反向入子 Label发送给下游节点。
首节点还可在 Path消息中携带创建共享 Mesh保护路径的指示信息， 以便 明示当前建立的 LSP为共享 Mesh保护路径。
进一步的，各个上游节点都可在发送给下游节点的 Path消息中携带创建共 享 Mesh保护路径的指示信息， 以便向各个下游节点明示当前建立的 LSP为共 享 Mesh保护路径，各个下游节点在接收到 Path消息后，根据 Path消息携带的创 建共享 Mesh保护路径的指示信息， 明确当前建立的 LSP为共享 Mesh保护路径， 进而启动相应的流程， 以下不再——说明。
402、 中间节点 （如果存在）接收上游节点发送的 Path消息； 根据路由信 息计算出业务 S1的保护路径在本节点上的反向出接口、 反向入接口， 并为业 务 S1分配反向出通道、 反向入通道；
中间节点可根据接收到的 Path消息携带的子 Label, 为业务 SI的保护路径 在本节点的反向出方向分配子 Label (简称反向出子 Label ) , 其中， 该分配的 反向出子 Label的值可与接收到的 Path消息携带的子 Label (上游节点的反向入 子 Label ) 的值相同； 中间节点进一步根据本地的分配情况， 为业务 S1在本节 点的反向入方向分配子 Label (简称反向入子 Label ) 。 中间节点可以建立业务 SI在本节点的反向绑定关系， 可以包括： 反向入 接口、反向入通道、反向入子 Label、反向出接口、反向出通道和反向出子 Label 的绑定关系。
中间节点通过 Path消息将该分配的反向入子 Label发送给下游节点。
403、 末节点接收上游节点发送的 Path消息； 并根据路由信息计算业务 S1 的保护路径在本节点上的反向出接口、 正向入接口， 并分配反向出通道、 正 向入通道。
末节点根据 Path消息中携带的子 Label, 为业务 SI的保护路径在本节点的 反向的出方向分配子 LabeK即反向出子 Label ) ,其中，该分配的反向出子 Label 的值可与接收到的 Path消息携带的子 Label (上游节点的反向入子 Label ) 的值 相同； 进而建立业务 S1在本节点上的反向绑定关系， 包括： 反向出接口、 反 向出通道、 反向出子 Label的绑定关系； 在末节点， 反向入接口、 反向入通道、 反向入子 Label可以没有。
末节点还可以进一步根据本地的分配情况， 为业务 S1的保护路径在本节 点的正向入方向分配子 Label (简称正向入子 Label ) , 建立业务 SI在本节点上 的正向绑定关系， 可以包括： 正向入接口、 正向入通道和正向入子 Label的绑 定关系， 末节点的正向出接口、 正向出通道、 正向出子 Label可以没有。
末节点结合正向和反向绑定关系， 可建立子 Label映射绑定关系， 可以包 括： 正向入接口、 正向入通道、 正向入子 Label、 反向出接口、 反向出通道和 反向出子 Label的映射绑定关系。
其中， 末节点可以将建立的绑定关系以数据表的形式进行记录， 以便后 续快速准确的查询。
末节点通过 Resv消息将分配的正向入子 Label发送给上游节点； 末节点还 可在 Resv消息中携带创建共享 Mesh保护路径的指示信息， 以便向上游节点明 示当前建立的 LSP为共享 Mesh保护路径。
进一步的， 各个下游节点都可以在发送给上游节点的 Resv消息中携带创 建共享 Mesh保护路径的指示信息， 以便向各个上游节点明示当前建立的 LSP 为共享 Mesh保护路径， 各个上游节点在接收到 Resv消息后， 根据 Resv消息携 带的创建共享 Mesh保护路径的指示信息， 明确当前建立的 LSP为共享 Mesh保 护路径， 进而启动相应的流程， 以下不再——说明。
404、 中间节点（如果存在）接收 Resv消息， 根据路由信息计算业务 S1的 保护路径在本节点上的正向出接口、 正向入接口， 并分配正向出通道、 正向 入通道；
中间节点根据 Resv消息中携带的子 Label, 为业务 SI的保护路径在本节点 的正向出方向分配子 Label (即正向出子 Label ) , 该分配的正向出子 Label的值 可与接收到的 Resv消息携带的子 Label (下游节点的正向入子 Label )的值相同； 并根据本地分配情况， 为业务 S1的保护路径在本节点的正向入方向分配子 Label (即正向入子 Label ) 。
至此， 中间节点可以建立业务 S1在本节点上的正向绑定关系， 包括： 正 向入接口、 正向入通道、 正向入子 Label、 正向出接口、 正向出通道、 正向出 子 Label的绑定关系；
中间节点结合之前建立的业务 S 1在本节点上的反向绑定关系， 可以建立 业务 S1的子 Label映射绑定关系， 可包括： 正向入接口、 正向入通道、 正向入 子 Label、 正向出接口、 正向出通道、 正向出子 Label; 反向入接口、 反向入通 道、 反向入子 Label、 反向出接口、 反向出通道、 反向出子 Label。
其中， 中间节点可以将建立的绑定关系以数据表的形式进行记录， 以便 后续快速准确的查询。
中间节点通过 Resv消息将分配的正向入子 Label发送给上游节点。
进一步的， 首节点接收 Resv消息， 根据路由信息计算出业务 S1的保护路 径在本节点上正向出接口， 并分配正向出通道。
首节点根据 Resv消息中携带的子 Label , 为业务 SI的保护路径在本节点的 正向出方向分配子 Label (即正向出子 Label ) , 该分配的正向出子 Label的值可 与接收到的 Resv消息携带的子 Label (下游节点的正向入子 Label ) 的值相同； 从而可以建立业务 S1的保护路径在本节点上的正向绑定关系， 可包括： 正向 出接口、 正向出通道、 正向出子 Label的绑定关系， 首节点的正向入接口、 正 向入通道、 正向入子 Label可以没有；
首节点结合正向和反向的绑定关系， 可建立子 Label映射关系， 包括： 正 向出接口、 正向出通道、 正向出子 Label; 反向入接口、 反向入通道、 反向入 子 Label的映射绑定关系。
其中， 首节点可以将建立的绑定关系以数据表的形式进行记录， 以便后 续快速准确的查询。
进一步的， 保护路径上的任何节点还可以在发送给下游节点的 Path消息 中， 携带建议分配的子 Label的指示信息， 用于对下游节点分配的子 Label给出 建议。 下游节点可以尽量按上游节点的建议分配正向入子 Label, 例如若上游 节点发现下游节点不是按本节点的建议来分配正向入子 Label, 则上游节点可 以根据本地策略， 选择接受该子 Label, 或拒绝该子 Label并可以进一步报错。
任何节点也可以在发送给下游节点的 Path消息中， 携带子 Label集（可以 包括一个或多个子标签） ， 用于限定下游节点分配的子 Label的范围， 下游节 点按照上游节点给出的范围分配正向入子 Label, 例如若上游节点发现下游节 点不是按本节点指定的范围分配子 Label， 则上游节点可以根据本地策略拒绝 该子 Label, 并可进一步报错。
进一步的， 首节点可以在发送给下游节点的 Path消息中，携带其指定的部 分或全部下游节点分配的子 Label的指示信息， 用于指定部分或全部下游节点 分配的子 Label。 下游节点按照首节点的指示分配正向入子 Label, 例如若首节 点发现下游各节点不是按首节点的指示来分配正向入子 Label , 则首节点可以 根据本地策略， 拒绝子 Label, 并可以进一步报错。
进一步的， 若需要收集 LSP在各个节点使用的子标签信息， 各节点例如可 将本节点为 Upsteam方向分配的子标签的值添加到 Path消息中发送给下游节 点； 将本节点为 Downstream方向分配的子标签的值添加到 Resv消息中发送给 上游节点。 当 Path消息传送到末节点时， Path消息就携带了 LSP经过的所有节 点在 Upstream方向使用的子标签信息了； 当 Resv消息传送到首节点时， Resv 消息就携带了 LSP经过的所有节点在 Downstream方向使用的子标签信息。
可以理解的是，在双向业务中， 需要上述过程中的有关分配反向子 Label, 建立反向绑定关系， 携带反向子 Label等的处理； 而单向业务则可以省略上述 反向的处理过程。
在实际应用中， 子标签以及指示信息都可以携带在消息的对象中， 下面 先介绍几种携带子标签或指示信息的对象。 可以对 Protection对象进行扩展， 增加共享 Mesh保护标志。
在 Protection对象中扩展一个指示位， 用于指示所建立的 LSP是共享 Mesh 保护路径， 其格式可以如下：
0 1 2 3
Β 1 2 3 ΐ| 5 6 7 8 9 β 1 2 3 ί| 5 6 7 8 9 β 1 2 3 4 5 ΰ 7 8 9 β 1
| Length | Class-Nun(37) | C-Type (2) |
|S|P|N|0| 858rued|M| LSP Flags | Reseru8d | Link Flags |
上述扩展后的 Protection对象的各个字段的指示含义可以如下：
Length ( 16 bits ) , 指示该对象的长度；
Class-num ( 8 bits ) , 指示该对象的类型号， 值为 37;
C-Type (8 bits) , 指示该对象的类型， 值为 2;
S ( 1 bit ) , 设置 (为 1 ) 时表示该 LSP是 secondary LSP;
P: ( 1 bit ) 设置 （为 1 ) 时表示该 LSP是保护 LSP;
N ( 1 bit) 设置 （为 1 ) 时表示在保护倒换时， 控制平面的消息交换 用于通告；
0 ( 1 bit ) , 设置 （为 1 ) 时表示在保护倒换后， 业务由保护 LSP传送； M ( 1 bit ) , 设置（为 1 )时表示建立的 LSP是用于共享 Mesh保护的路径； LSP Flags ( 6 bits ) , 指示 LSP的恢复类型；
Link Flags ( 6 bits ) , 指示链路保护类型。
在实际应用中， 可将创建共享 Mesh保护业务的保护路径的 Path消息携带 的 Protection对象中的 "M" 位设置为 1 , 以指示收到该 Path消息的节点当前创 建的是共享 Mesh保护业务的保护路径。
进一步的， 可以定义一个新的对象： Sublabel object
该对象用于携带 Downstream方向的子标签信息， 通过 Resv消息携带， 其 格式如下： 2 3
2 3 4 8 9 θ 2 3 4 β 9 θ 2 3 1* 8 9 θ
Length 1 Class -Nun 1 c Type 1
■ Dc 1 I
^UD dDP 1 Κί 1 上述定义的 Sublabel对象的各个字段的指示含义可以如下：
Length ( 16 bits ) , 指示该对象的长度；
Class-num ( 8 bits ) , 指示该对象的类型号；
C-Type (8 bits) , 指示该对象的类型；
Sublabel ( 16 bits) , 指示子标签值。
在实际应用中， 节点例如可将分配的 LSP的 Dowstream (正向） 方向的子 标签的值作为 Sublabel对象的 Sublabel字段的值， 并将该 Sublabel对象携带在 Resv消息中发送给上游节点。
进一步的， 可定义一个新的对象： Suggested Sublabel object
该对象可以用于携带建议的子标签信息， 可通过 Path消息携带， 其格式可 以 ¾口下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
| Length | Class-Num | C-Type |
上述定义的 Suggested Sublabel对象的各个字段的指示含义可以如下： Length ( 16 bits ) , 指示该对象的长度；
Class-num ( 8 bits ) , 指示该对象的类型号；
C-Type (8 bits) , 指示该对象的类型；
Sublabel ( 16 bits) , 指示建议的子标签值。
在实际应用中， 若需要对下游节点分配的 LSP的 Dowstream方向的子标签 给出建议， 则可将建议的子标签的值作为 Suggested Sublabel对象的 Sublabel字 段的值， 并将该 Suggested Sublabel对象携带在 Path消息中发送给下游节点。 下 游节点可以在获得 Suggested Sublabel对象后，按照 Suggested Sublabel对象中建 议的子标签值来分配正向入子标签。 例如若上游节点发现下游节点没有按照 Suggested Sublabel中建议的子标签值分配的子标签， 可根据本地策略进行处 进一步的， 可以定义一个新的对象： Sublabel Set object
该对象用于携带子标签的指定分配范围， 可在 Path消息中携带， 其格式可 以 ¾口下：
Θ 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
Length I Class-Num | C-Type
Action I Rt ？ served | Sublabel Type
Sublabel 1 I - - -
I Sublabel N 上述定义的 Sublabel Set对象的各个字段的指示含义可以如下：
Length ( 16 bits ) , 该对象的长度；
Class-num ( 8 bits ) , 该对象的类型号；
C-Type (8 bits) , 该对象的类型；
Action: (8 bits) , 例如 0可指示包含列表， 表示包含 Sublabel Set中的一个 或多个 Sublabel; 1可指示排除列表， 表示排除 Sublabel Set中的一个或多个 Sublabel; 2可指示包含范围， 表示包含的 Sublabel的范围， 例如 Sublabel Set中 有两个子标签， 第一个表示子标签范围的起始值， 第二个表示终止值， 如果 为 0, 则可表示没有限制； 3可指示排除范围， 表示排除的 Sublabel的范围。 例 如 Sublabel Set中有两个子标签， 第一个表示子标签范围的起始值， 第二个表 示终止值， 如果为 0, 则可表示没有限制。
Sublabel Type ( 14 bits ) , 指示子标签的类型。
Sublabel ( 16 bits) , 指示子标签值。
在实际应用中， 若需要在 LSP的 Dowstream方向， 对下游节点分配的子标 签的范围进行限制， 可将指定的子标签范围信息携带在 Sublabel Set对象的各 个 Sublabel字段中，通过 Path消息发送给下游节点， 下游节点可根据该 Sublabel Set对象中的子标签范围信息来分配合适的子标签。 例如若上游节点发现从下 游节点接收到的 Resv消息中携带的 Sublabel对象的子标签没有在 Sublabel Set 给的范围内， 则拒绝该子标签， 并可返回失败指示。
进一步的， 可以定义一个新的对象： Upstreamsublabel object
该对象用于在双向 LSP中， 携带 Upstream方向的子标签信息， 可在 Path消 息中携带， 其格式可以如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 8 1
| Length | Class - Nu | C-Type |
上述定义的 Upstreamsublabel对象的各个字段的指示含义可以如下： Length ( 16 bits ) , 指示该对象的长度；
Class-num ( 8 bits ) , 指示该对象的类型号；
C-Type (8 bits) , 指示该对象的类型；
Sublabel ( 16 bits) , 指示子标签值。
在实际应用中， 在双向 LSP的 Upstream方向， 上游节点分配的子标签的值 作为 Upstreamsublabel对象的 Sublabel字段的值， 将该 Upstreamsublabel对象携 带在 Path消息中发送给下游节点。
进一步的， 定义一个新的对象： Sublabel ERO subobject
该对象为 Sublabel ER0子对象， 用于在 ERO对象中携带子标签信息， 以进 行显示子标签控制， 其格式可以如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|U| Type Length 上述定义的 Sublabel ERO subobject的各个字段的指示含义可以如下： U( 1 bit ),用于标识 Sublabel的方向，如果为 0,可指示 downstream sublabel; 如果为 1, 则是 upstream sublabel, 用于双向 LSP中；
Type (7 bits) , 指示该对象的类型；
Length ( 8 bits ) , 指示该对象的长度；
Sublabel ( 16 bits) , 指示子标签值。 在实际应用中， 若首节点需要指定保护路径上的部分或全部下游节点分 配的子标签， 即进行显示子标签控制 （例如用户指定子标签） ， 可以将指定 的子标签的值作为 Sublabel ERO子对象的 Sublabel字段的值， 通过在 Path消息 的 ERO对象中携带该 Sublabel ERO子对象来实现。
进一步的， 定义一个新的对象： Sublabel RRO subobject
该对象为 Sublabel RRO子对象，用于在 RRO对象中携带子标签信息， 以便 收集 LSP使用的子标签， 其格式可以如下：
0 1 2 3
Θ 1 2 3 4 5 6 7 8 9 β 1 2 3 ΐι 5 6 7 8 9 θ 1 2 3 ίι 5 6 7 8 9 β 1
| U | Type | Length | Sublabel |
上述定义的 Sublabel ERO subobject的各个字段的指示含义可以如下： U( 1 bit ),用于标识 Sublabel的方向，如果为 0,可指示 downstream sublabel; 如果为 1, 则可指示 upstream sublabel, 用于双向 LSP中；
Type (7 bits) , 指示该对象的类型；
Length ( 8 bits ) , 指示该对象的长度；
Sublabel ( 16 bits) , 指示子标签值。
在实际应用中， 若需要收集 LSP在各个节点使用的子标签信息， 各节点例 如可将本节点为 Upsteam方向分配的子标签的值作为 Sublabel RRO子对象的 Sublabel字段的值， 将该 Sublabel RRO子对象携带在 Path消息中发送给下游节 点； 将本节点为 Downstream方向分配的子标签的值作为 Sublabel RRO子对象 的 Sublabel字段的值， 将该 Sublabel RRO子对象携带在 Resv消息中发送给上游 节点。
当 Path消息传送到末节点时， 其携带的 RRO对象就携带了 LSP经过的所有 节点在 Upstream方向使用的子标签信息了； 当 Resv消息传送到首节点时，其携 带的 RRO对象就携带了 LSP经过的所有节点在 Downstream方向使用的子标签 信息。
通过如上过程， 可以为业务 S1的保护路径分配好子 Label, 建立好映射关 系。 在分配好子 Label, 建立好子 Label映射关系后， 当业务 S1的工作路径发生 故障时， 业务首节点（或末节点）监测到故障， 将业务 S1切换到保护路径上， 查找到相应的子 Label映射关系， 设置好 APS开销中的相关信息， 通过 APS开 销传送恢复信息。各节点在接收到 APS开销承载的恢复信息时，根据恢复信息 的特定特征， 查找到对应的子 Label映射关系， 建立相应的连接， 并通过 APS 开销继续向其它节点传送恢复信息， 建立保护路径上的连接， 直至末节点（或 首节点）。 末节点（或首节点）才艮据收到的 APS开销中携带的恢复信息， 查找 到相应的子 Label映射关系， 可将业务 S1切换到保护路径上， 通过保护路径传 送业务 S1 , 使业务 S1得到快速的恢复。
进一步， 为便于更好地理解本发明实施例的技术方案， 通过两个更为具 体的应用场景进行详细介绍。
场景一
在本场景下， 4个字节的 APS开销可分成 8份， 共 8个 Sub-APS开销 （例如 图 4-b所示） ， 每个子开销 4个比特， 每个子开销最多可以定义 16种共享 Mesh 保护相关消息。
每个 Sub-APS开销负责传送一条业务相关的消息， 一个通道的 APS开销最 多可以传送 8条共享 Mesh保护业务相关的消息， 即一个通道最多给 8条共享 Mesh保护业务的保护路径共享。
在该场景中， 子 Label可对应于 Sub-APS开销， 分配子 Label, 就等于分配 Sub-APS开销， 子 Label中携带 Sub-APS开销的编号。 可在创建共享 Mesh保护 路径的 Path消息的 Protection对象中携带共享 Mesh保护路径标志， 用于指示该 Path消息创建的是共享 Mesh保护路径。 参见图 4-c, 下面以创建业务 2的共享 Mesh保护路径的过程为例。
首节点 N1利用路由信息， 计算业务 2的保护路径在本节点上的反向入接 口， 并分配反向入通道； 节点 N1为业务 2的保护路径的反向入方向分配 Sub-APS开销， 分配业务 2的保护路径在节点 N1的反向入子 Label, 例如若为业 务 2分配 CH2通道的 2 # Sub-APS开销， 则业务 2的保护路径在节点 N1的反向入 子 Label指示 2 # Sub-APS开销 （即指示出下游节点 N6利用 CH2通道的 2 # Sub-APS开销传送业务 2的恢复信息） ； 节点 N1可以建立反向绑定关系， 可以 包括： 反向入接口、 反向入通道、 反向入子 Label的绑定关系。
节点 N1例如可将 2 # Sub-APS开销的编号 2作为 Upstreamsublabel对象中 Sublabel字段的值， 通过 Path消息将该 Upstreamsublabel对象发送给节点 N6, 从 而将节点 N1为业务 2分配的 Sub-APS开销信息通知给节点 N6;
进一步的， 节点 N1和节点 N6都可在发送给下游节点的 Path消息中的 Protection对象中携带共享 Mesh保护路径标志， 以便向各个下游节点明示当前 建立的 LSP为共享 Mesh保护路径， 各个下游节点 （节点 N6和节点 N5 )则可在 接收到 Path消息后，根据 Path消息中的 Protection对象中携带共享 Mesh保护路径 标志， 明确当前建立的 LSP为共享 Mesh保护路径， 进而启动相应的流程， 以 下不再——说明。
进一步的， 若节点 N1需要对节点 N6分配的 Sub-APS开销进行建议， 节点 N1例如可将用于指示其建议分配的 Sub-APS开销编号的子标签的值， 作为 Suggested Sublabel对象中 Sublabel字段的值， 可通过在 Path消息中携带 Suggested Sublabel对象来携带建议分配的 Sub-APS开销信息；
进一步的， 若节点 N1需要对下游节点分配的 Sub-APS开销的范围进行限 制， 节点 N1可以将指示限定分配的 Sub-APS开销范围的子标签的值， 作为 Sublabel Set对象中 Sublabel字段的值， 通过在 Path消息中携带 Sublabel Set对象 来携带 Sub-APS开销的限定范围信息。
进一步的， 若首节点 N1需要对保护路径上的部分或全部节点分配的 Sub-APS开销进行指定，节点 N1例如可将用于指示其指定分配的 Sub-APS开销 编号的子标签的值，作为 Sublabel ERO子对象中 Sublabel字段的值，通过在 Path 消息的 ERO对象中携带该 Sublabel ERO子对象来实现。
节点 N6接收 Path消息， 利用路由信息计算业务 2的保护路径在本节点上的 反向入接口、 反向出接口， 分配反向入通道和反向出通道； 根据 Path消息携带 的 Upstreamsublabel对象中的 Sublabel的值，将 CH2通道的 2 # Sub-APS开销分配 给业务 2, 节点 N6分配的反向出子 Label指示 2 # Sub-APS开销。
节点 N6还根据本地的分配情况， 为业务 2在本节点的反向入方向分配 Sub-APS开销， 分配反向入子 Label , 例如若为业务 2分配了 CH8通道的 1 # Sub-APS开销， 则业务 2的保护路径在节点 N6反向入子 Label指示 2 # Sub-APS 开销（即指示出下游节点 N5利用 CH8通道的 1 # Sub-APS开销传送业务 2的恢复 信息）。至此， 节点 N6可建立该业务 2在本节点上的反向绑定关系，可以包括： 反向入接口、 反向入通道、 反向入子 Label、 反向出接口、 反向出通道和反向 出子 Label的绑定关系。
节点 N6例如可将 1 # Sub-APS开销的编号 1作为 Upstreamsublabel对象中 Sublabel字段的值， 通过 Path消息将 Upstreamsublabel对象发送给节点 N5, 从而 将节点 N6为业务 2分配的 Sub-APS开销信息通知节点 N5。
末节点 N5接收 Path消息， 利用路由信息计算业务 2的保护路径在本节点上 的反向出接口、 正向入接口， 分配反向出通道和正向入通道； 根据 Path消息携 带的 Upstreamsublabel对象中的信息， 将 CH8通道的 1 # Sub-APS开销分配给业 务 2, 节点 N5分配的反向出子 Label指示 1 # Sub-APS开销。 至此， 节点 N5可以 建立业务 2的保护路径在本节点上的反向绑定关系， 可包括： 反向出接口、 反 向出通道、 反向出子 Label的绑定关系。
节点 N5还根据本地的分配情况， 为业务 2在本节点的正向入方向分配 Sub-APS开销， 分配正向入子 Label , 例如若为业务 2分配了 CH8通道的 1 # Sub-APS开销， 则业务 2的保护路径在节点 N5正向入子 Label指示 1 # Sub-APS 开销（即指示出上游节点 N6利用 CH8通道的 1 # Sub-APS开销传送业务 2的恢复 信息）； 至此， 节点 N5可以建立业务 2在本节点上的正向绑定关系， 包括： 正 向入接口、 正向入通道、 正向入子 Label的绑定关系。
节点 N5结合正向和反向的绑定关系可建立子 Label映射关系， 可包括： 正 向入接口、 正向入通道、 正向入子 Label、 反向出接口、 反向出通道、 反向出 子 Label的映射绑定关系。
其中， 末节点 N5可以将建立的绑定关系以数据表的形式进行记录， 以便 后续快速准确的查询。
节点 N5例如可将 1 # Sub-APS开销的编号 1作为 Sublabel对象中 Sublabel字 段的值， 通过 Resv消息将 Sublabel对象发送给节点 N6, 从而可将节点 N5为业 务 2分配的 Sub-APS开销信息通知节点 N6。
进一步的， 节点 N5和节点 N6都可在发送给上游节点的 Resv消息中的 Protection对象中携带共享 Mesh保护路径标志， 以便向各个上游节点明示当前 建立的 LSP为共享 Mesh保护路径， 各个上游节点 （节点 N6和节点 N1 )则可在 接收到 Resv消息后， 根据 Resv消息中的 Protection对象中携带共享 Mesh保护路 径标志 , 明确当前建立的 LSP为共享 Mesh保护路径 , 进而启动相应的流程 , 以下不再——说明。
节点 N6接收 Resv消息，根据路由信息计算出业务 2的保护路径在本节点上 的正向入接口、 正向出接口， 分配正向入通道和正向出通道； 根据 Resv消息 携带的 Sublabel对象的 Sublabel字段中的信息， 将 CH8通道的 1 # Sub-APS开销 分配给业务 2, 节点 N6分配的正向出子 Label指示 1 # Sub-APS开销。
节点 N6还根据本地的分配情况，为业务 2的保护路径在本节点的正向入方 向分配 Sub-APS开销， 分配正向入子 Label, 例如若为业务 2分配了 CH2通道上 的 2 # Sub-APS开销， 则业务 2的保护路径在节点 N6的正向入子 Label指示 2 # Sub-APS开销 （即指示出上游节点 N1利用 CH2通道的 2 # Sub-APS开销传送业 务 2的恢复信息） ； 至此， 节点 N6就可以建立业务 2在本节点上的正向绑定关 系， 可以包括： 正向入接口、 正向入通道、 正向入子 Label、 正向出接口、 正 向出通道、 正向出子 Label的绑定关系。
节点 N6结合接收到 Path消息时已建立好的反向绑定关系， 就可以建立子 Label映射关系， 可包括： 正向入接口、 正向入通道、 正向入子 Label、 正向出 接口、正向出通道、正向出子 Label;反向入接口、反向入通道、反向入子 Label、 反向出接口、 反向出通道和反向出子 Label的映射绑定关系。
其中， 中间节点 N6可以将建立的绑定关系以数据表的形式进行记录， 以 便后续快速准确的查询。
节点 N6例如可将 2 # Sub-APS开销的编号 2作为 Sublabel对象中 Sublabel字 段的值， 通过 Resv消息将 Sublabel对象发送给节点 N1 , 从而将节点 N6为业务 2 分配的 Sub-APS开销信息通知节点 Nl。
首节点 N1接收 Resv消息，根据路由信息计算出业务 2的保护路径在本节点 上的正向出接口， 分配正向出通道； 根据 Resv携带的 Sublabel对象的 Sublabel 字段中的信息，将 CH2通道的 2 # Sub-APS开销分配给业务 2, 节点 N1分配的正 向出子 Label指示 2 # Sub-APS开销。
至此， 节点 N1可建立业务 2在本节点上的正向绑定关系， 包括： 正向出接 口、 正向出通道、 正向出子 Label的绑定关系。
节点 N1结合正向和反向的绑定关系可建立子 Label映射关系， 可包括： 正 向出接口、 正向出通道、 正向出子 Label; 反向入接口、 反向入通道、 反向入 子 Label的映射绑定关系。
其中， 首节点 N1可以将建立的绑定关系以数据表的形式进行记录， 以便 后续快速准确的查询。
至此， 业务 2的保护路径上的各节点就为业务 2分配好了 Sub-APS开销， 各 节点利用为业务 2分配好的 Sub-APS开销， 承载传送业务 2的恢复信息。
进一步的， 若节点 N1需要对业务 2使用的 Sub-APS开销进行显示指定或显 示控制， 可以将指定的 Sub-APS开销信息携带在 Sublabel ERO子对象中， 通过 Path消息发送到下游各节点。 各节点在收到 Path消息后， 根据其携带的 ERO中 的 Sublabel ERO子对象信息分配相应的 Sub-APS开销， 并利用相应的子 Label 进行指示。
进一步的， 若需要收集业务 2在各个节点使用的 Sub-APS开销信息， 则可 将为反向分配的 Sub-APS开销信息携带在 Sublabel RRO子对象中， 添加到 RRO 对象， 通过 Path消息发送到下游节点； 将为正向分配的 Sub-APS开销信息放入 Sublabel RRO子对象， 添加到 RRO对象里， 通过 Resv消息发送到上游节点。 可 以理解， 当 Path消息传到了末节点 N5时， 其携带的 RRO对象就具有了业务 2的 保护路径上的所有节点在业务 2反向使用的 Sub-APS开销信息； 当 Resv消息传 到了首节点 N1时，其携带的 RRO对象就具有了业务 2的保护路径上的所有节点 在业务 2正向使用的 Sub-APS开销信息。
当业务 2工作路径发生故障时， 业务 2的首节点 N1 (或末节点 N5 )可监测 到故障， 将业务 2切换到保护路径， 查找到业务 2的子 Label映射关系， 将相应 的 Sub-APS开销的状态修改为恢复， 通过 APS开销将恢复信息发送给其它节 点。 各节点在收到 APS开销承载的恢复信息时， 根据恢复信息的特定特征， 查 找到对应的子 Label映射关系， 建立相应的连接， 并通过 APS开销继续向其它 节点传送恢复信息， 建立保护路径上的连接， 直至末节点 N5 (或首节点 N1 ) 。 末节点 N5 (或首节点 N1 )根据收到的 APS开销中携带的恢复信息， 查找到相 应的子 Label映射关系， 可将业务 2切换到保护路径上， 并通过业务 2保护路径 传送业务 2, 使业务 2得到快速的恢复。 其它业务的保护路径的配置过程可按 照上述方式以此类推。 场景二
本场景可应用于整个 APS开销被共享 Mesh保护的所有业务共享的场景， 即不对 APS开销进行划分， 而是共享 Mesh保护的所有业务都共享使用共享通 道上的 APS开销，在工作路径故障时，将需要进行倒换的业务的业务区分器（业 务区分器用于标识区分业务， 通过业务区分器可以确定出是哪条业务）携带 在恢复消息 （该恢复信息中例如可以只包括区分器信息） 中， 利用共享通道 的 APS开销进行传送， 保护路径上各节点可根据 APS开销中携带的业务区分 器， 建立相应的连接， 对相应的业务进行倒换。
在该场景中， 子 Label就对应于业务区分器， 分配子 Label, 就等效于分配 业务区分器，子 Label中可携带业务区分器。可在创建共享 Mesh保护路径的 Path 消息的 Protection对象中携带共享 Mesh保护路径标志， 用于指示该 Path消息创 建的是共享 Mesh保护路径。 参见图 4-d, 下面以创建业务 2的共享 Mesh保护路 径的过程为例。
具体的， 节点 N1根据路由信息， 计算业务 2的保护路径在本节点上的反向 入接口、 并分配反向入通道； 为业务 2的反向入方向分配业务区分器， 分配反 向入子 Label, 例如若为业务 2分配了业务区分器 2 , 业务 2的保护路径在节点 N1的反向入子 Label指示业务区分器 2 (即指示出下游节点 N6传送的业务 2的恢 复信息中包含业务区分器 2 )； 节点 N1可以建立反向绑定关系， 可以包括： 反 向入接口、 反向入通道、 反向入子 Label的绑定关系。
节点 N1可将业务区分器 2的编号 2作为 Upstreamsublabel对象中 Sublabel的 值， 通过 Path消息将 Upstreamsublabel对象发送给节点 N6 , 从而将节点 N1为业 务 2分配的业务区分器信息通知给节点 N6。
进一步的， 节点 N1和节点 N6都可在发送给下游节点的 Path消息中的 Protection对象中携带共享 Mesh保护路径标志， 以便向各个下游节点明示当前 建立的 LSP为共享 Mesh保护路径， 各个下游节点 （节点 N6和节点 N5 )则可在 接收到 Path消息后，根据 Path消息中的 Protection对象中携带共享 Mesh保护路径 标志， 明确当前建立的 LSP为共享 Mesh保护路径， 进而启动相应的流程， 以 下不再——说明。
进一步的， 若节点 N1需要对节点 N6分配的业务区分器给出建议， 节点 N1 例如可将用于指示其建议分配的业务区分器的子标签的值， 作为 Suggested Sublabel对象中 Sublabel字段的值，可通过在 Path消息中携带 Suggested Sublabel 对象来携带建议分配的业务区分器信息；
进一步的，若节点 N1需要对下游节点分配的业务区分器的范围进行限制， 节点 N1可以将指示限定分配的业务区分器范围的子标签的值， 作为 Sublabel Set对象中 Sublabel字段的值， 可通过在 Path消息中携带 Sublabel Set对象来携带 业务区分器的限定范围信息。
进一步的， 若首节点 N1需要对保护路径上的部分或全部节点分配的业务 区分器进行指定， 节点 N1例如可将用于指示其指定分配的业务区分器的子标 签的值，作为 Sublabel ERO子对象中 Sublabel字段的值，通过在 Path消息的 ERO 对象中携带该 Sublabel ERO子对象来实现。
节点 N6接收 Path消息， 利用路由信息计算业务 2的保护路径在本节点上的 反向入接口、 反向出接口， 分配反向入通道和反向出通道； 根据 Path消息携带 的 Upstreamsublabel对象中的 Sublabel的值， 将业务区分器 2分配给业务 2 , 节点 N6分配的反向出子 Label指示业务区分器 2。
节点 N6还根据本地的分配情况，为业务 2在本节点的反向入方向分配业务 区分器， 分配反向入子 Label, 例如若为业务 2分配了业务区分器 1 , 则业务 2 的保护路径在节点 N6反向入子 Label指示业务区分器 1 (即指示出下游节点 N5 传送的业务 2的恢复信息中包含业务区分器 1 ) , 至此， 节点 N6就可以建立业 务 2在本节点上的反向绑定关系， 可以包括： 反向入接口、 反向入通道、 反向 入子 Label、 反向出接口、 反向出通道、 反向出子 Label的绑定关系。
节点 N6可将业务区分器 1的编号 1作为 Upstreamsublabel对象中 Sublabel字 段的值， 通过 Path消息将该 Upstreamsublabel对象发送给节点 N5 , 从而将节点 N6为业务 2分配的业务区分器信息通知给节点 N5。
末节点 N5接收 Path消息， 利用路由信息计算业务 2的保护路径在本节点上 的反向出接口、 正向入接口， 分配反向出通道和正向入通道； 根据 Path消息携 带的 Upstreamsublabel对象中的信息， 将业务区分器 1分配给业务 2, 节点 N5分 配的反向出子 Label指示业务区分器 1。 至此， 节点 N5可以建立业务 2的保护路 径在本节点上的反向绑定关系， 可以包括： 反向出接口、 反向出通道、 反向 出子 Label的绑定关系。
节点 N5还根据本地的分配情况，为业务 2在本节点的正向入方向分配业务 区分器， 分配正向入子 Label, 例如若为业务 2分配了业务区分器 1 , 则业务 2 的保护路径在节点 N5的正向入子 Label指示业务区分器 1 (即指示出上游节点 N6传送的业务 2的恢复信息中包含业务区分器 1 ) ； 至此， 节点 N5可以建立业 务 2在本节点上的正向绑定关系， 包括： 正向入接口、 正向入通道、 正向入子 Label的绑定关系。
节点 N5结合正向和反向的绑定关系可建立子 Label映射关系， 可包括： 正 向入接口、 正向入通道、 正向入子 Label、 反向出接口、 反向出通道、 反向出 子 Label的映射绑定关系。
其中， 末节点 N5可以将建立的绑定关系以数据表的形式进行记录， 以便 后续快速准确的查询。
节点 N5例如可将业务区分器 1的编号 1作为 Sublabel对象中 Sublabel字段的 值， 通过 Resv消息将该 Sublabel对象发送给节点 N6 , 从而将节点 N5为业务 2分 配的业务区分器信息通知给节点 N6。
进一步的， 节点 N5和节点 N6都可在发送给上游节点的 Resv消息中的 Protection对象中携带共享 Mesh保护路径标志， 以便向各个上游节点明示当前 建立的 LSP为共享 Mesh保护路径， 各个上游节点 （节点 N6和节点 N1 )则可在 接收到 Resv消息后， 根据 Resv消息中的 Protection对象中携带共享 Mesh保护路 径标志， 明确当前建立的 LSP为共享 Mesh保护路径， 进而启动相应的流程， 以下不再——说明。
节点 N6接收 Resv消息，根据路由信息计算出业务 2的保护路径在本节点上 的正向入接口、 正向出接口， 分配正向入通道和正向出通道； 根据 Resv消息 携带的 Sublabel对象的 Sublabel字段中的信息， 将业务区分器 1分配给业务 2 , 节点 N6分配的正向出子 Label指示业务区分器 1。
节点 N6还根据本地的分配情况，为业务 2的保护路径在本节点的正向入方 向分配业务区分器， 分配正向入子 Label, 例如若为业务 2分配了业务区分器 2, 则业务 2的保护路径在节点 N6的正向入子 Label指示业务区分器 2 (即指示出上 游节点 N1传送的业务 2的恢复信息中包含业务区分器 2 ) 。 至此， 节点 N6就可以建立业务 2在本节点上的正向绑定关系， 可包括： 正 向入接口、 正向入通道、 正向入子 Label、 正向出接口、 正向出通道、 正向出 子 Label的绑定关系。
节点 N6结合接收到 Path消息时已建立好的反向绑定关系， 就可以建立子 Label映射关系， 可包括： 正向入接口、 正向入通道、 正向入子 Label、 正向出 接口、正向出通道、正向出子 Label;反向入接口、反向入通道、反向入子 Label、 反向出接口、 反向出通道和反向出子 Label的映射绑定关系。
其中， 中间节点 N6可以将建立的绑定关系以数据表的形式进行记录， 以 便后续快速准确的查询。
节点 N6例如可将业务区分器 2的编号 2作为 Sublabel对象中 Sublabel字段的 值， 通过 Resv消息将该 Sublabel对象发送给节点 N1 , 从而将节点 N6为业务 2分 配的业务区分器信息通知节点 Nl。
首节点 N1接收 Resv消息，根据路由信息计算出业务 2的保护路径在本节点 上的正向出接口， 分配正向出通道； 根据 Resv携带的 Sublabel对象的信息， 将 业务区分器 2分配给业务 2 , 节点 N1分配的正向出子 Label指示业务区分器 2。 至此， 节点 N1可建立业务 2在本节点上的正向绑定关系， 包括： 正向出接口、 正向出通道、 正向出子 Label的绑定关系。
节点 N1结合正向和反向的绑定关系可建立子 Label映射关系， 可包括： 正 向出接口、 正向出通道、 正向出子 Label; 反向入接口、 反向入通道、 反向入 子 Label的映射绑定关系。
其中， 首节点 N1可以将建立的绑定关系以数据表的形式进行记录， 以便 后续快速准确的查询。
至此， 业务 2的保护路径上的各节点就为业务 2分配好了业务区分器， 各 节点传送的业务 2的恢复信息中包含分配好的业务区分器。
进一步的， 若需要对业务 2使用的业务区分器进行显示的指定或显示控 制， 可以将业务区分器信息携带在 Sublabel ERO子对象中， 通过 Path消息发送 到下游各节点。 各节点在收到 Path消息后， 根据其携带的 ERO中的 Sublabel ERO子对象信息分配相应的业务区分器， 并利用相应的子 Label进行指示。
进一步的， 若需要收集业务 2在各个节点使用的业务区分器信息， 则可将 为反向分配的业务区分器信息携带在 Sublabel RRO子对象中， 添加到 RRO对 象， 通过 Path消息发送到下游节点； 将为正向分配的业务区分器信息放入 Sublabel RRO子对象， 添加到 RRO对象里， 通过 Resv消息发送到上游节点。 可 以理解， 当 Path消息传到了末节点 N5时， 其携带的 RRO对象就具有了业务 2的 保护路径上的所有节点在业务 2反向使用的业务区分器信息； 当 Resv消息传到 了首节点 N1时，其携带的 RRO对象就具有了业务 2的保护路径上的所有节点在 业务 2正向使用的业务区分器信息。
当业务 2工作路径发生故障时， 业务 2的首节点 N1 (或末节点 N5 )可监测 到故障， 将业务 2切换到保护路径， 查找到业务 2的子 Label映射关系， 将相应 的 APS开销的状态修改为恢复， 通过 APS开销将携带业务 2的区分器信息的恢 复信息发送给其它节点。各节点在收到 APS开销承载的恢复信息时，根据恢复 信息携带的业务 2的区分器信息， 查找到对应的子 Label映射关系， 建立相应的 连接，并通过 APS开销继续向其它节点传送恢复信息，建立保护路径上的连接， 直至末节点 N5 (或首节点 N1 ) 。 末节点 N5 (或首节点 N1 )根据收到的 APS 开销中承载的恢复信息， 查找到相应的子 Label映射关系， 可将业务 2切换到保 护路径上， 并通过业务 2保护路径传送业务 2, 使业务 2得到快速的恢复。 其它 业务的保护路径的配置过程可按照上述方式以此类推。
由上可见， 本实施例中由保护路径上的节点分配并传递用于指示业务的 恢复信息的特定特征的子标签， 以便于该节点的上游节点或下游节点据此传 送该业务的恢复信息， 进而可以实现保护路径上的各节点在接收到业务的恢 复信息时能够直接确定出待恢复的业务， 且配置操作简单， 可以为后续进行 业务的自动快速的保护倒换提供可靠的支持。
进一步的， 指定或建议其它节点分配子标签的范围、 以及收集保护路径 上的各节点分配的子标签， 有利于实现良好的维护和管理。
为便于更好的实施本发明实施例的技术方案， 本发明实施例还提供一种 光网络节点。
实施例四、
参见图 5 , 本发明实施例四的一种光网络节点 500, 具体可以包括： 接收 模块 510、 第一分配模块 520和恢复信息发送模块 530。 接收模块 510 , 用于接收第二节点发送的 Resv消息， 该 Resv消息携带第二 节点为第一业务的保护路径分配的第二正向入子标签， 第二正向入子标签用 于指示承载第一业务的恢复信息的特定特征。
其中， 第一业务的恢复信息的特定特征例如可以包括： 第一业务的恢复 信息包含的特定标识 （例如业务区分器） 、 第一业务的恢复信息具有的特定 数据结构、承载第一业务的恢复信息的子 APS开销的标识（例如子开销的编号） 或其它相关的特征。
第一分配模块 520 , 用于根据第二正向入子标签， 为第一业务的保护路径 分配第一正向出子标签， 该第一正向出子标签和第二正向入子标签具有对应 关系。
在一种应用场景下， 第二节点为第一业务的保护路径分配的第二正向入 子标签可以是， 能够指示出第一业务的恢复信息的特定特征的任意信息， 例 如该子标签可以指示出第一业务的恢复信息的如下特定特征中的一个或多 个： 第一业务的恢复信息包含的特定标识、 第一业务的恢复信息具有的特定 数据结构、 承载第一业务的恢复信息的子 APS开销的编号等等特定特征。
恢复信息发送模块 530 , 用于在获知第一业务的工作路径故障时， 按照上 述第一正向出子标签的指示向第二节点传送第一业务的恢复信息。
可以理解， 第二节点可以是第一业务的保护路径的末节点， 也可以是第 一业务的保护路径的中间节点， 光网络节点 500为第二节点的上游节点。
在一种应用场景下， 第二节点可以将分配的第二正向入子标签携带在第 二类型的消息中， 利用该信令消息将该第二正向入子标签向第一业务的保护 路径上的上游节点发送， 以便于获得该第二正向入子标签的光网络节点 500, 对应的分配第一正向出子标签（其中， 第二正向入子标签和第一正向出子标 签的值可以相等， 或具有相应的推导对应关系， 当然， 光网络节点 500对应分 配的第一正向出子标签同样用于指示第一业务的恢复信息的特定特征， 且第 一正向出子标签和第二正向入子标签指示的第一业务恢复信息的特定特征相 同）。
进一步的， 当光网络节点 500在获知第一业务的工作路径故障时， 其便可 以按照第一正向出子标签的指示向第二节点传送第一业务的恢复信息。 而第 二节点在接收到光网络节点 500传送的第一业务的恢复信息时， 便可以直接根 据其分配的第二正向入子标签的指示， 确定出待恢复的业务为第一业务， 进 而可以快速的将第一业务自动倒换到其保护路径上进行传送。
在一种应用场景下， 光网络节点 500还可包括：
路由计算模块， 用于根据路由信息计算第一业务的保护路径在光网络节 点 500上的正向出接口， 并为第一业务的保护路径分配正向出通道；
绑定关系建立模块， 用于建立第一业务的保护路径在光网络节点 500上的 正向绑定关系， 该正向绑定关系包括第一业务的保护路径在光网络节点 500上 的正向出接口、 正向出通道和上述第一正向出子标签的映射绑定关系；
保护倒换模块， 用于在获知第一业务的工作路径故障时， 根据绑定关系 建立模块建立的正向绑定关系， 将第一业务倒换到第一业务的保护路径上。
在一种应用场景下， 若第一业务为双向业务， 路由计算模块还可用于， 根据路由信息计算第一业务的保护路径在上述光网络节点上的反向入接口， 并为第一业务的保护路径分配反向入通道；
光网络节点 500还可以包括：
第二分配模块， 用于为第一业务的保护路径分配第一反向入子标签， 该 第一反向入子标签用于指示第一业务的恢复信息的特定特征；
第一消息发送模块， 用于通过第一类型的消息将该第一反向入子标签向 第一业务的保护路径上的第二节点发送， 该第一类型的消息中还携带创建第 一业务的保护路径的指示信息。
绑定关系建立模块还可用于， 建立第一业务的保护路径在光网络节点 500 上的反向绑定关系， 该反向绑定关系可以包括第一业务的保护路径在光网络 节点 500上的反向入接口、 反向入通道和第一反向入子标签的映射绑定关系。
若光网络节点 500为第一业务的中间节点， 路由计算模块还可用于， 根据 路由信息计算第一业务的保护路径在光网络节点 500上的正向入接口， 并为第 一业务的保护路径分配正向入通道；
光网络节点 500还可包括：
第三分配模块， 用于为第一业务的保护路径分配第一正向入子标签， 该 第一正向入子标签用于指示第一业务的恢复信息的特定特征； 绑定关系建立模块建立的正向绑定关系还可以包括： 第一业务的保护路 径在光网络节点 500上的正向入接口、 正向入通道和上述第一正向入子标签的 映射绑定关系；
第二消息发送模块， 用于通过第二类型的消息， 将上述第一正向入子标 签向第一业务的保护路径上的第三节点发送。
在一种应用场景下， 各个下游节点可以将为第一业务分配的正向入子标 签添加到第二类型的消息中， 光网络节点 500还可包括：
子标签收集模块， 用于收集并记录接收到的第二类型的消息中携带的各 个下游节点为第一业务的保护路径分配的正向入子标签。
需要说明的是， 本实施例的光网络节点 500可以如上述方法实施例中的节 点 N1或 N6 , 可以用于实现上述方法实施例中的全部技术方案， 其各个功能模 块的功能可以根据上述方法实施例中的方法具体实现， 其具体实现过程可参 照上述实施例中的相关描述， 此处不再赘述。
为便于更好的实施本发明实施例的技术方案， 本发明实施例还提供一种 光网络节点。 实施例五、
参见图 6 , 本发明实施例五的一种光网络节点 600 , 具体可以包括： 第一 分配模块 610和消息发送模块 620。
其中， 第一分配模块 610 , 用于为第一业务的保护路径分配第二正向入子 标签， 该第二正向入子标签用于指示第一业务的恢复信息的特定特征。
其中， 第一业务的恢复信息的特定特征例如可以包括： 第一业务的恢复 信息包含的特定标识 （例如业务区分器） 、 第一业务的恢复信息具有的特定 数据结构、承载第一业务的恢复信息的子 APS开销的标识（例如子开销的编号） 或其它相关的特征。
消息发送模块 620 , 用于通过第二类型的消息将上述第二正向入子标签向 第一业务的保护路径上的第一节点发送。
可以理解， 第一节点可以是第一业务的保护路径的首节点， 也可以是第 一业务的保护路径的中间节点， 光网络节点 600为第一节点的下游节点。
在一种应用场景下， 第一分配模块 610具体可以用于， 为第一业务的保护 路径分配第二正向入子标签， 该第二正向入子标签用于指示承载第一业务的 恢复信息的子自动保护倒换开销或第一业务的恢复信息中携带的业务区分 器。
在一种应用场景下， 光网络节点 600可以将分配的第二正向入子标签携带 在第二类型的消息中， 利用该信令消息将该第二正向入子标签向第一业务的 保护路径上的上游节点发送， 以便于获得该第二正向入子标签的第一节点， 对应的分配第一正向出子标签（其中， 第二正向入子标签和第一正向出子标 签的值可以相等， 或具有相应的推导对应关系， 当然， 第一节点对应分配的 第一正向出子标签同样用于指示第一业务的恢复信息的特定特征， 且第一正 向出子标签和第二正向入子标签指示的第一业务恢复信息的特定特征相同）。
进一步的， 当第一节点在获知第一业务的工作路径故障时， 其便可以按 照第一正向出子标签的指示向光网络节点 600传送第一业务的恢复信息。 而光 网络节点 600在接收到第一节点传送的第一业务的恢复信息时， 便可以直接根 据其分配的第二正向入子标签的指示， 确定出待恢复的业务为第一业务， 进 而可以快速的将第一业务自动倒换到其保护路径上进行传送。
若第一业务为双向业务， 光网络节点 600还可以包括：
接收模块， 用于接收第一节点发送的第一类型的消息， 该第一类型的消 息携带第一节点为第一业务的保护路径分配第一反向入子标签， 该第一反向 入子标签用于指示承载第一业务的恢复信息的特定特征， 第一类型的消息中 还携带创建第一业务的保护路径的指示信息；
第二分配模块， 用于根据上述的第一反向入子标签， 为第一业务的保护 路径分配第二反向出子标签， 该第二反向出子标签和第一反向入子标签具有 对应关系；
恢复信息发送模块， 用于在获知第一业务的工作路径故障时， 按照上述 第二反向出子标签的指示向第一节点传送第一业务的恢复信息。
在一种应用场景下， 光网络节点 600还可包括：
路由计算模块， 用于根据路由信息计算第一业务的保护路径在光网络节 点 600上的反向出接口、 反向出通道；
反向绑定关系建立模块， 建立第一业务的保护路径在光网络节点 600上的 反向绑定关系， 该反向绑定关系包括第一业务的保护路径在光网络节点 600上 的反向出接口、 反向出通道和第二反向出子标签的映射绑定关系；
第一保护倒换模块， 用于在获知第一业务的工作路径故障时， 根据上述 反向绑定关系建立模块建立的反向绑定关系， 将第一业务倒换到第一业务的 保护路径上。
在一种应用场景下， 路由计算模块还可以用于， 根据路由信息计算第一 业务的保护路径在第二节点上的正向入接口， 并为第一业务的保护路径分配 正向入通道；
光网络节点 600还可以包括：
正向绑定关系建立模块， 建立第一业务的保护路径在第二节点上的正向 绑定关系， 该正向绑定关系包括第一业务的保护路径在第二节点上的正向入 接口、 正向入通道和上述第二正向入子标签的映射绑定关系；
第二保护倒换模块， 用于在获知第一业务的工作路径故障时， 根据上述 正向绑定关系建立模块建立的正向绑定关系， 将第一业务倒换到第一业务的 保护路径上。
在一种应用场景下， 若第一类型的消息还携带第一节点建议分配的子标 签的指示信息； 第一分配模块 610可以具体用于， 按照第一节点的建议或根据 本地分配情况， 为第一业务的保护路径分配第二正向入子标签。
在另一种应用场景下， 若第一类型的消息还携带第一节点指定分配的子 标签的范围的指示信息； 第一分配模块 610具体用于， 在第一节点指定分配的 子标签的范围内， 为第一业务的保护路径分配第二正向入子标签；
在另一种应用场景下， 若第一类型的消息还携带首节点指定分配的子标 签的指示信息； 第一分配模块 610可具体用于， 按照首节点指定分配的子标签 的指示信息的指示， 为第一业务的保护路径分配第二正向入子标签。
在一种应用场景下， 各个上游节点可以将为第一业务分配的反向入子标 签添加到第一类型的消息中， 光网络节点 600还可以包括：
子标签收集模块， 用于收集并记录接收到的第一类型的消息中携带的各 个上游节点为第一业务的保护路径分配的反向入子标签。
需要说明的是， 本实施例的光网络节点 600可以如上述方法实施例中的节 点 N5或 N6 , 可以用于实现上述方法实施例中的全部技术方案， 其各个功能模 块的功能可以根据上述方法实施例中的方法具体实现， 其具体实现过程可参 照上述实施例中的相关描述， 此处不再赘述。
为便于更好的实施本发明实施例的技术方案， 本发明实施例还提供一种 光网络系统。
实施例六、
参见图 7 , 本发明实施例六的一种光网络系统， 可以包括： 第一节点 710 和第二节点 720。
第二节点 720 , 用于为第一业务的保护路径分配第二正向入子标签， 该第 二正向入子标签用于指示第一业务的恢复信息的特定特征； 通过第二类型的 消息将上述第二正向入子标签向第一业务的保护路径上的第一节点 710发送。
第一节点 710 , 用于接收第二节点 720发送的第二类型的消息， 该 Resv消 息携带第二节点 720为第一业务的保护路径分配的第二正向入子标签； 根据该 第二正向入子标签， 为第一业务的保护路径分配第一正向出子标签， 该第一 正向出子标签和第二正向入子标签具有对应关系； 在获知第一业务的工作路 径故障时， 按照上述第一正向出子标签的指示向第二节点 720传送第一业务的 恢复信息。
进一步的， 若第一业务为双向业务， 第一节点 710还可用于， 为第一业务 的保护路径分配第一反向入子标签， 该第一反向入子标签用于指示第一业务 的恢复信息的特定特征； 通过第一类型的消息将该第一反向入子标签向第一 业务的保护路径上的第二节点 720发送；
第二节点 720可以接收第一节点 710发送的第一类型的消息， 该第一类型 的消息可携带第一节点 710为第一业务的保护路径分配的第一反向入子标签； 根据该第一反向入子标签， 为第一业务的保护路径分配第二反向出子标签， 该第二反向出子标签和第一反向入子标签具有对应关系； 在获知第一业务的 工作路径故障时， 按照上述第二反向出子标签的指示向第一节点 710传送第一 业务的恢复信息。
需要说明的是， 本实施例的第一节点 710可以如上述方法实施例中的节点 N1或 N6、 第二节点 720可以如上述方法实施例中的节点 N5或 N6, 可以用于实 现上述方法实施例中的全部技术方案， 其各个功能模块的功能可以根据上述 方法实施例中的方法具体实现， 其具体实现过程可参照上述实施例中的相关 描述， 此处不再赘述。
需要说明的是， 对于前述的各方法实施例， 为了简单描述， 故将其都表 述为一系列的动作组合， 但是本领域技术人员应该知悉， 本发明并不受所描 述的动作顺序的限制， 因为依据本发明， 某些步骤可以釆用其他顺序或者同 时进行。 其次， 本领域技术人员也应该知悉， 说明书中所描述的实施例均属 于优选实施例， 所涉及的动作和模块并不一定是本发明所必须的。 在上述实施例中， 对各个实施例的描述都各有侧重， 某个实施例中没有 详述的部分， 可以参见其他实施例的相关描述。
综上， 本发明实施例中， 由保护路径上的节点分配并传递用于指示业务 的恢复信息的特定特征的子标签， 以便于该节点的上游节点或下游节点据此 传送该业务的恢复信息， 进而可以实现保护路径上的各节点在接收到业务的 恢复信息时能够直接确定出待恢复的业务， 且配置操作简单， 可以为后续进 行业务的自动快速的保护倒换提供可靠的支持
进一步的， 指定或建议其它节点分配子标签的范围、 以及收集保护路径 上的各节点分配的子标签， 有利于实现良好的维护和管理。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步 骤是可以通过程序来指令相关的硬件来完成， 该程序可以存储于一计算机可 读存储介质中， 存储介质可以包括： 只读存储记忆体 （ROM , Read-Only Memory )或随机存储记忆体（RAM , Random Access Memory )、 磁盘或光盘 等。
以上对本发明实施例所提供的共享 Mesh保护的实现方法和设备及光网络 行了阐述， 以上实施例的说明只是用于帮助理解本发明的方法及其核'、思想； 同时， 对于本领域的一般技术人员， 依据本发明的思想， 在具体实施方式及 应用范围上均会有改变之处， 综上， 本说明书内容不应理解为对本发明的限 制。

Claims

权 利 要求 书
1、 一种共享 Mesh保护的实现方法， 其特征在于， 包括：
第一节点接收第二节点发送的第二类型的消息， 所述第二类型的消息携带 第二节点为第一业务的保护路径分配的第二正向入子标签， 所述第二正向入子 标签用于指示承载第一业务的恢复信息的特定特征；
根据所述第二正向入子标签， 为第一业务的保护路径分配第一正向出子标 签， 所述第一正向出子标签和第二正向入子标签具有对应关系；
在获知第一业务的工作路径故障时， 按照所述第一正向出子标签的指示向 第二节点传送第一业务的恢复信息。
2、 根据权利要求 1所述的方法， 其特征在于，
所述第二正向入子标签用于指示承载第一业务的恢复信息的子自动保护倒 换开销或第一业务的恢复信息中携带的业务区分器。
3、 根据权利要求 2所述的方法， 其特征在于， 所述方法还包括：
根据路由信息计算第一业务的保护路径在第一节点上的正向出接口， 并为 第一业务的保护路径分配正向出通道；
建立第一业务的保护路径在第一节点上的正向绑定关系， 所述正向绑定关 系包括第一业务的保护路径在第一节点上的正向出接口、 正向出通道和所述第 一正向出子标签的映射绑定关系；
在获知第一业务的工作路径故障时， 根据所述建立的正向绑定关系， 将第 一业务倒换到第一业务的保护路径上。
4、 根据权利要求 1所述的方法， 其特征在于， 所述方法还包括：
根据路由信息计算第一业务的保护路径在第一节点上的反向入接口， 并为 第一业务的保护路径分配反向入通道；
为第一业务的保护路径分配第一反向入子标签， 所述第一反向入子标签用 于指示第一业务的恢复信息的特定特征；
通过第一类型的消息将所述第一反向入子标签向第一业务的保护路径上的 第二节点发送， 所述第一类型的消息中还携带创建第一业务的保护路径的指示 信息。
5、 根据权利要求 3所述的方法， 其特征在于， 所述方法还包括： 根据路由信息计算第一业务的保护路径在第一节点上的正向入接口， 并为 第一业务的保护路径分配正向入通道；
为第一业务的保护路径分配第一正向入子标签， 所述第一正向入子标签用 于指示第一业务的恢复信息的特定特征； 所述正向绑定关系还包括： 第一业务 的保护路径在第一节点上的正向入接口、 正向入通道和所述第一正向入子标签 的映射绑定关系；
通过第二类型的消息， 将所述第一正向入子标签向第一业务的保护路径上 的第三节点发送。
6、 一种共享 Mesh保护的实现方法， 其特征在于， 包括：
第二节点为第一业务的保护路径分配第二正向入子标签， 所述第二正向入 子标签用于指示第一业务的恢复信息的特定特征；
通过第二类型的消息将所述第二正向入子标签向第一业务的保护路径上的 第一节点发送。
7、 根据权利要求 6所述的方法， 其特征在于，
所述为第一业务的保护路径分配第二正向入子标签， 所述第二正向入子标 签用于指示第一业务的恢复信息的特定特征， 包括：
为第一业务的保护路径分配第二正向入子标签， 所述第二正向入子标签用 于指示承载第一业务的恢复信息的子自动保护倒换开销或第一业务的恢复信息 中携带的业务区分器。
8、 根据权利要求 6或 7所述的方法， 其特征在于， 所述为第一业务的保护路 径分配第二正向入子标签之前还包括：
接收第一节点发送的第一类型的消息， 所述第一类型的消息携带第一节点 为第一业务的保护路径分配第一反向入子标签， 所述第一反向入子标签用于指 示承载第一业务的恢复信息的特定特征， 所述第一类型的消息中还携带创建第 一业务的保护路径的指示信息；
所述方法还包括：
根据所述第一反向入子标签， 为第一业务的保护路径分配第二反向出子标 签， 所述第二反向出子标签和所述第一反向入子标签具有对应关系；
在获知第一业务的工作路径故障时， 按照所述第二反向出子标签的指示向 第一节点传送第一业务的恢复信息。
9、 根据权利要求 8所述的方法， 其特征在于， 所述方法还包括：
根据路由信息计算第一业务的保护路径在第二节点上的反向出接口、 反向 出通道；
建立第一业务的保护路径在第二节点上的反向绑定关系， 所述反向绑定关 系包括第一业务的保护路径在第二节点上的反向出接口、 反向出通道和所述第 二反向出子标签的映射绑定关系；
在获知第一业务的工作路径故障时， 根据所述建立的反向绑定关系， 将第 一业务倒换到第一业务的保护路径上。
10、 根据权利要求 8所述的方法， 其特征在于，
若所述第一类型的消息还携带第一节点建议分配的子标签的指示信息； 所述为第一业务的保护路径分配第二正向入子标签， 包括：
按照第一节点的建议或根据本地分配情况， 为第一业务的保护路径分配第 二正向入子标签；
或
若所述第一类型的消息还携带第一节点指定分配的子标签的范围的指示信 息；
所述为第一业务的保护路径分配第二正向入子标签， 包括：
在第一节点指定分配的子标签的范围内， 为第一业务的保护路径分配第二 正向入子标签；
或
若所述第一类型的消息还携带首节点指定分配的子标签的指示信息； 所述为第一业务的保护路径分配第二正向入子标签， 包括：
按照首节点指定分配的子标签的指示信息的指示， 为第一业务的保护路径 分配第二正向入子标签。
11、 一种光网络节点， 其特征在于， 包括：
接收模块， 用于接收第二节点发送的第二类型的消息， 所述第二类型的消 息携带第二节点为第一业务的保护路径分配的第二正向入子标签， 所述第二正 向入子标签用于指示承载第一业务的恢复信息的特定特征； 第一分配模块， 用于根据所述第二正向入子标签， 为第一业务的保护路径 分配第一正向出子标签， 所述第一正向出子标签和第二正向入子标签具有对应 关系；
恢复信息发送模块， 用于在获知第一业务的工作路径故障时， 按照所述第 一正向出子标签的指示向第二节点传送第一业务的恢复信息。
12、 根据权利要求 11所述的光网络节点， 其特征在于， 还包括：
路由计算模块， 用于根据路由信息计算第一业务的保护路径在所述光网络 节点上的正向出接口， 并为第一业务的保护路径分配正向出通道；
绑定关系建立模块， 用于建立第一业务的保护路径在所述光网络节点上的 正向绑定关系， 所述正向绑定关系包括第一业务的保护路径在所述光网络节点 上的正向出接口、 正向出通道和所述第一正向出子标签的映射绑定关系；
保护倒换模块， 用于在获知第一业务的工作路径故障时， 根据所述建立的 正向绑定关系， 将第一业务倒换到第一业务的保护路径上。
13、 根据权利要求 11所述的光网络节点， 其特征在于，
所述路由计算模块还用于， 根据路由信息计算第一业务的保护路径在所述 光网络节点上的反向入接口， 并为第一业务的保护路径分配反向入通道；
所述光网络节点还包括：
第二分配模块， 用于为第一业务的保护路径分配第一反向入子标签， 所述 第一反向入子标签用于指示第一业务的恢复信息的特定特征；
第一消息发送模块， 用于通过第一类型的消息将所述第一反向入子标签向 第一业务的保护路径上的第二节点发送， 所述第一类型的消息中还携带创建第 一业务的保护路径的指示信息。
14、 一种光网络节点， 其特征在于， 包括：
第一分配模块， 用于为第一业务的保护路径分配第二正向入子标签， 所述 第二正向入子标签用于指示第一业务的恢复信息的特定特征；
消息发送模块， 用于通过第二类型的消息将所述第二正向入子标签向第一 业务的保护路径上的第一节点发送。
15、 根据权利要求 14所述的光网络节点， 其特征在于，
所述光网络节点还包括： 接收模块， 用于接收第一节点发送的第一类型的消息， 所述第一类型的消 息携带第一节点为第一业务的保护路径分配第一反向入子标签， 所述第一反向 入子标签用于指示承载第一业务的恢复信息的特定特征， 所述第一类型的消息 中还携带创建第一业务的保护路径的指示信息；
第二分配模块， 用于根据所述第一反向入子标签， 为第一业务的保护路径 分配第二反向出子标签， 所述第二反向出子标签和所述第一反向入子标签具有 对应关系；
恢复信息发送模块， 用于在获知第一业务的工作路径故障时， 按照所述第 二反向出子标签的指示向第一节点传送第一业务的恢复信息。
16、 根据权利要求 15所述的光网络节点， 其特征在于，
所述光网络节点还包括：
路由计算模块， 用于根据路由信息计算第一业务的保护路径在所述光网络 节点上的反向出接口、 反向出通道；
反向绑定关系建立模块， 建立第一业务的保护路径在所述光网络节点上的 反向绑定关系， 所述反向绑定关系包括第一业务的保护路径在所述光网络节点 上的反向出接口、 反向出通道和所述第二反向出子标签的映射绑定关系；
第一保护倒换模块， 用于在获知第一业务的工作路径故障时， 根据所述建 立的反向绑定关系， 将第一业务倒换到第一业务的保护路径上。
17、 一种光网络系统， 其特征在于， 包括
第二节点， 用于为第一业务的保护路径分配第二正向入子标签， 所述第二 正向入子标签用于指示第一业务的恢复信息的特定特征； 通过第一类型的消息 将所述第二正向入子标签向第一业务的保护路径上的第一节点发送；
第一节点， 用于接收第二节点发送的第一类型的消息， 所述第一类型的消 息携带第二节点为第一业务的保护路径分配的第二正向入子标签； 根据所述第 二正向入子标签， 为第一业务的保护路径分配第一正向出子标签， 所述第一正 向出子标签和第二正向入子标签具有对应关系； 在获知第一业务的工作路径故 障时， 按照所述第一正向出子标签的指示向第二节点传送第一业务的恢复信息。
PCT/CN2010/079505 2009-12-18 2010-12-07 共享mesh保护的实现方法和设备及光网络系统 WO2011072581A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP10837018.0A EP2503742B1 (en) 2009-12-18 2010-12-07 Method for implementing shared mesh protection, equipment and optical network system
ES10837018.0T ES2449367T3 (es) 2009-12-18 2010-12-07 Método para implementar una protección de malla compartida, un equipo y un sistema de red óptica
US13/524,822 US9161106B2 (en) 2009-12-18 2012-06-15 Method and device for implementing shared mesh protection and optical network system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910261627.1 2009-12-18
CN200910261627.1A CN102104495B (zh) 2009-12-18 2009-12-18 共享Mesh保护的实现方法和设备及光网络系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/524,822 Continuation US9161106B2 (en) 2009-12-18 2012-06-15 Method and device for implementing shared mesh protection and optical network system

Publications (1)

Publication Number Publication Date
WO2011072581A1 true WO2011072581A1 (zh) 2011-06-23

Family

ID=44157039

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/079505 WO2011072581A1 (zh) 2009-12-18 2010-12-07 共享mesh保护的实现方法和设备及光网络系统

Country Status (5)

Country Link
US (1) US9161106B2 (zh)
EP (1) EP2503742B1 (zh)
CN (1) CN102104495B (zh)
ES (1) ES2449367T3 (zh)
WO (1) WO2011072581A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102868544A (zh) * 2011-07-06 2013-01-09 中兴通讯股份有限公司 一种实现共享网格保护的方法及系统
WO2013189039A1 (zh) * 2012-06-20 2013-12-27 华为技术有限公司 一种恢复路径建立的方法、系统和节点设备
EP2779530B1 (en) * 2012-06-20 2017-04-26 Huawei Technologies Co., Ltd. Method, system, and node device for establishing recovery path
CN103812686A (zh) * 2012-11-15 2014-05-21 中兴通讯股份有限公司 一种网状保护的方法和装置
JP6229318B2 (ja) * 2013-06-05 2017-11-15 富士通株式会社 通信システム、通信制御方法、及び、伝送装置
US9729949B2 (en) * 2014-04-23 2017-08-08 Alcatel Lucent Dynamic local decision control in software defined networking-based environment
US9935900B2 (en) * 2014-10-16 2018-04-03 Electronics And Telecommunications Research Institute Method for providing protection switching service in virtual tenant network and controller therefor
US9843508B2 (en) 2015-03-06 2017-12-12 Juniper Networks, Inc. RSVP make-before-break label reuse
US9838306B2 (en) * 2015-03-31 2017-12-05 Juniper Networks, Inc. RSVP make-before-break label reuse
US10341228B1 (en) 2017-03-29 2019-07-02 Juniper Networks, Inc. RSVP make-before-break label reuse
CN113453095B (zh) * 2020-03-26 2023-03-28 华为技术有限公司 恢复路径配置的方法和装置
CN113727220B (zh) * 2020-05-26 2023-04-11 华为技术有限公司 业务资源预配置方法、设备和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030001635A (ko) * 2001-06-25 2003-01-08 에스케이 텔레콤주식회사 멀티-프로토콜 라벨 스위칭 방식이 적용된 데이터통신망에서의 프로텍션 스위칭을 위한 트래픽 경로 설정방법
CN101453411A (zh) * 2007-11-28 2009-06-10 华为技术有限公司 建立标签交换路径的方法、系统和设备
CN101588520A (zh) * 2009-07-07 2009-11-25 北京邮电大学 一种用于mpls-tp网络的段保护方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6917759B2 (en) * 2002-01-31 2005-07-12 Nortel Networks Limited Shared mesh signaling algorithm and apparatus
US7606237B2 (en) * 2003-03-31 2009-10-20 Alcatel-Lucent Usa Inc. Sharing restoration path bandwidth in mesh networks
US20050088963A1 (en) 2003-10-24 2005-04-28 Nortel Networks Limited Method and apparatus for protection switch messaging on a shared mesh network
CN100555922C (zh) 2004-09-10 2009-10-28 华为技术有限公司 一种实现网格状光网络业务恢复的方法
US7420989B2 (en) * 2004-09-30 2008-09-02 Lucent Technologies Inc. Technique for identifying backup path for shared mesh protection
KR100693052B1 (ko) * 2005-01-14 2007-03-12 삼성전자주식회사 Ｍｐｌｓ 멀티캐스트의 고속 재경로 설정 장치 및 방법
CN1866806B (zh) 2005-12-22 2011-11-02 华为技术有限公司 共享格状网恢复的实现方法
US7969868B2 (en) * 2009-02-19 2011-06-28 Infinera Corporation Path-level protection for digitally wrapped payloads

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030001635A (ko) * 2001-06-25 2003-01-08 에스케이 텔레콤주식회사 멀티-프로토콜 라벨 스위칭 방식이 적용된 데이터통신망에서의 프로텍션 스위칭을 위한 트래픽 경로 설정방법
CN101453411A (zh) * 2007-11-28 2009-06-10 华为技术有限公司 建立标签交换路径的方法、系统和设备
CN101588520A (zh) * 2009-07-07 2009-11-25 北京邮电大学 一种用于mpls-tp网络的段保护方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2503742A4 *

Also Published As

Publication number Publication date
US9161106B2 (en) 2015-10-13
US20120257886A1 (en) 2012-10-11
ES2449367T3 (es) 2014-03-19
EP2503742A1 (en) 2012-09-26
EP2503742B1 (en) 2013-12-04
CN102104495B (zh) 2014-07-09
CN102104495A (zh) 2011-06-22
EP2503742A4 (en) 2012-10-03

Similar Documents

Publication Publication Date Title
WO2011072581A1 (zh) 共享mesh保护的实现方法和设备及光网络系统
US10432514B2 (en) Multiprotocol label switching traffic engineering tunnel establishing method and device
CN106803814B (zh) 一种灵活以太网路径的建立方法、装置及系统
US10250459B2 (en) Bandwidth on-demand services in multiple layer networks
US7095712B2 (en) Method and apparatus for protection path setup
US8289843B2 (en) Service failure recovery method and system
US7680029B2 (en) Transmission apparatus with mechanism for reserving resources for recovery paths in label-switched network
JP4509885B2 (ja) シグナリング装置
US20140348028A1 (en) Method for creating ring network label switched path, related device, and communications system
US8149693B2 (en) Method of implementing association in automatic switched optical network (ASON)
WO2017193569A1 (zh) 一种路径建立方法及控制器
WO2011157130A2 (zh) 路径建立方法和装置
US20090103533A1 (en) Method, system and node apparatus for establishing identifier mapping relationship
US7463580B2 (en) Resource sharing among network tunnels
JP5365434B2 (ja) ノード装置及び経路計算方法
JP2009060673A (ja) 経路計算システム、経路計算方法、及び通信ノード
WO2015024440A1 (zh) 一种获取ip链路的链路开销值的方法及系统
WO2010130177A1 (zh) 业务连接建立方法、路径计算单元设备及网络系统
KR101259298B1 (ko) 루팅 장치, 통신 시스템, 및 루팅 방법
CN101488900A (zh) 在下一代网络中传送业务的实现方法及系统
CN101577932B (zh) 在下一代网络中传送业务的实现方法及系统
WO2013063751A1 (zh) 转发邻居-标签交换路径的连接建立方法及装置
KR101624621B1 (ko) 멀티 프로토콜 레이블 스위칭 망에서 동적 백업 보호 경로 결정 방법 및 장치
WO2015062045A1 (zh) 一种控制通道的建立方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10837018

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2010837018

Country of ref document: EP