WO2017124982A1 - 一种保护倒换的方法和节点 - Google Patents

一种保护倒换的方法和节点 Download PDF

Info

Publication number
WO2017124982A1
WO2017124982A1 PCT/CN2017/071192 CN2017071192W WO2017124982A1 WO 2017124982 A1 WO2017124982 A1 WO 2017124982A1 CN 2017071192 W CN2017071192 W CN 2017071192W WO 2017124982 A1 WO2017124982 A1 WO 2017124982A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
field
request
protection
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/071192
Other languages
English (en)
French (fr)
Inventor
郑好棉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to JP2018555809A priority Critical patent/JP6562435B2/ja
Priority to EP17741013.1A priority patent/EP3393059B1/en
Priority to KR1020187023155A priority patent/KR102064853B1/ko
Publication of WO2017124982A1 publication Critical patent/WO2017124982A1/zh
Priority to US16/038,531 priority patent/US10674240B2/en
Anticipated expiration legal-status Critical
Priority to US16/861,659 priority patent/US10993005B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/08—Intermediate station arrangements, e.g. for branching, for tapping-off
    • H04J3/085—Intermediate station arrangements, e.g. for branching, for tapping-off for ring networks, e.g. SDH/SONET rings, self-healing rings, meashed SDH/SONET networks
    • 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
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/03—Arrangements for fault recovery
    • H04B10/038—Arrangements for fault recovery using bypasses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/27—Arrangements for networking
    • H04B10/275—Ring-type networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/14—Monitoring arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • 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
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0057—Operations, administration and maintenance [OAM]
    • H04J2203/006—Fault tolerance and 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/0088—Signalling aspects

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to an Ethernet ring protection switching method and a node.
  • the traditional optical transmission network is mainly in a ring or linear topology, and provides multiplex section protection, channel ring protection, linear 1:1 multiplex section protection, linear 1+1 multiplex section protection, and end-to-end subnet connection protection.
  • Subnetwork Connection Protection (SNCP) and other protection technologies are mainly in a ring or linear topology, and provides multiplex section protection, channel ring protection, linear 1:1 multiplex section protection, linear 1+1 multiplex section protection, and end-to-end subnet connection protection.
  • SNCP Subnetwork Connection Protection
  • the traditional optical network protection technology needs to reserve a large amount of network bandwidth resources and low bandwidth utilization.
  • SMP Shared Mesh Protection
  • ASON Automatically Switched Optical Network
  • FIG. 1 is a prior art APS overhead coding format.
  • the overhead part of the APS message can be used to describe the state of the SMP protection switching. There are 4 bytes and 32 bits. There are three types of information to be described:
  • (1) Request includes the types of protection switching requests included in the first to fourth bits, such as SF (Singnal Failure), SD (Signal Degrade), and RR (Reverse Request). ), NR (No Request), MS (Manual Switch), and FS (Forced Switch).
  • Requested Signal A service ID (Identifier) indicating a service requesting to share a protection resource, for example, W1, etc., in the ninth to the 16th bits. Set all 0s when there is no request.
  • Bridged Signal A service ID included in the 17th bit to the 24th bit indicating that the bridged service has been completed, for example, W1. Set all 0s when no service has completed bridging.
  • the definition of the above coding format can be found in detail in the ITU-T G.ODUSMP standard. It can be seen from the coding format in FIG. 1 that the valid field is only 20 bits, and the reserved field has 12 bits, and the overhead field is not fully utilized, resulting in waste of overhead resources.
  • the embodiment of the present invention provides a method and a node for protecting switching, which can solve the problem of waste of overhead resources.
  • an embodiment of the present invention provides a protection switching method, including: when a working path between a first end node and a second end node fails, the first end node sends a first to an intermediate node. a protection switching request message, wherein the protection path of the working path includes the first end node, the second end node, and at least one of the intermediate nodes; the first end node receives a second from the intermediate node
  • the protection switching request message is configured to switch the service data to the protection path, where the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, and the overhead information
  • the group includes a request type field, a request signal identification field, and a bridge identification field; the request type field indicates a fault type of the working path, and the request signal identifier field is a service identifier of a service requesting protection of resources, the bridge identifier
  • the field indicates whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridged.
  • two overhead information groups may be included in one overhead frame to express the overhead information of the two time slots, and the overhead field is fully utilized, thereby improving the efficiency of protection switching.
  • the cost information group further includes a request flag field, where the request flag bit field is used to indicate that the service identifier of the request signal identifier field corresponds to Whether the service requests protection of resources.
  • two overhead groups may be included in an overhead frame, and a request flag field is set in the overhead information group, which is used to indicate whether the service corresponding to the service identifier of the overhead information group requests protection resources, and fully utilizes Overhead resources.
  • the request type field occupies 4 bits
  • the request signal identifier field occupies 8 bits or 9 Bit or 10 bits
  • the request flag field occupies 1 bit
  • the bridge identification field occupies 1 bit.
  • the request signal identification field can occupy 8 to 10 bits, making full use of the APS overhead field.
  • the third possible implementation manner of the first aspect before the first end node sends the first protection switching request message, The bridging between the first end node and the intermediate node is completed.
  • the first end node receives the second protection switching request After the message, the selection between the first end node and the intermediate node is completed.
  • the first end node detects the service of the first working path When the fault is recovered, the method further includes: the first end node sending a third protection switching request message to the intermediate node; the first node receiving the fourth protection switching request message of the third node, The service data is switched to the transmission on the working path; one of the third protection switching request message and the fourth protection switching request message includes at least two overhead information groups, and the request type field in the overhead information group indicates the The service identifier of the request signal identifier field corresponds to the fault recovery of the working path of the service.
  • two overhead information groups may be included in one overhead frame to express the overhead information of the two time slots, and the overhead field is fully utilized, thereby improving the efficiency of protection switching.
  • an embodiment of the present invention provides a protection switching method, including: when a working path between a first end node and a second end node fails, the intermediate node receives the first protection of the first end node. a switching request message, wherein the protection path of the working path includes the first end node, the second An end node and at least one of the intermediate nodes; the intermediate node transmitting a first protection switching request message to a downstream neighboring node of the intermediate node; the intermediate node receiving a second downstream node from the intermediate node a protection switching request message; the intermediate node sends a second protection switching request message to the first end node, where the one of the first protection switching request message and the second protection request message includes at least two overhead information groups
  • the cost information group includes a request type field, a request signal identifier field, and a bridge identifier field.
  • the request type field indicates a fault type of the working path
  • the request signal identifier field is a service identifier of a service requesting protection of resources.
  • the bridge identifier field indicates whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridged.
  • two overhead information groups may be included in one overhead frame to express the overhead information of the two time slots, and the overhead field is fully utilized, thereby improving the efficiency of protection switching.
  • the cost information group further includes a request flag field, where the request flag bit field is used to indicate the service of the request signal identifier field. Identifies whether the corresponding service requests protection resources.
  • two overhead groups may be included in an overhead frame, and a request flag field is set in the overhead information group, which is used to indicate whether the service corresponding to the service identifier of the overhead information group requests protection resources, and fully utilizes Overhead resources.
  • the request type field occupies 4 bits
  • the request signal identifier field occupies 8 bits or 9 Bit or 10 bits
  • the request flag field occupies 1 bit
  • the bridge identification field occupies 1 bit.
  • the request signal identification field can occupy 8 to 10 bits, making full use of the APS overhead field.
  • the intermediate node receives the first protection switching request of the first end node After the message, the bridging between the downstream neighbor nodes between the intermediate node and the intermediate node is completed.
  • the intermediate node receives the upstream neighboring node of the intermediate node After the second protection switching request message, the selection between the upstream neighboring node and the intermediate node of the intermediate node is completed.
  • an embodiment of the present invention provides a protection switching method, including: when a working path between a first end node and a second end node fails, the second end node receives the first protection from the intermediate node. a switching request message, wherein the protection path of the working path includes the first end node, the second end node, and at least one of the intermediate nodes; and the second end node sends a second protection switching request message to the intermediate node
  • the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, where the overhead information group includes a request type field, a request signal identifier field, and a bridge identifier.
  • a request type field indicating a fault type of the working path
  • the request signal identifier field being a service identifier of a service requesting a protection resource
  • the bridge identifier field indicating whether the protection resource corresponding to the service identifier of the request signal identifier field is Has been bridged.
  • two overhead information groups may be included in one overhead frame to express the overhead information of the two time slots, and the overhead field is fully utilized, thereby improving the efficiency of protection switching.
  • the The information group further includes a request flag field, where the request flag bit field is used to indicate whether the service corresponding to the service identifier of the request signal identifier field requests protection resources.
  • two overhead groups may be included in an overhead frame, and a request flag field is set in the overhead information group, which is used to indicate whether the service corresponding to the service identifier of the overhead information group requests protection resources, and fully utilizes Overhead resources.
  • the request type field occupies 4 bits
  • the request signal identifier field occupies 8 bits or 9 Bit or 10 bits
  • the request flag field occupies 1 bit
  • the bridge identification field occupies 1 bit.
  • the request signal identification field can occupy 8 to 10 bits, making full use of the APS overhead field.
  • the second end node receives the first protection of the intermediate node After the request message is switched, the selection between the intermediate node and the second end node is completed.
  • the second end node sends the The bridging between the second end node and the intermediate node is completed before the second protection switching request message.
  • an embodiment of the present invention provides a first end node, including: a sending module, configured to send a first protection to an intermediate node when a working path between the first end node and the second end node fails a switching request message, wherein the protection path of the working path includes the first end node, the second end node, and at least one of the intermediate nodes; and a receiving module, configured to receive a second protection switching from the intermediate node And the request message, the service data is switched to the protection path, where the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, where the overhead information group includes a request type field, a request signal identification field, and a bridge identification field; the request type field indicating a fault type of the working path, the request signal identifier field being a service identifier of a service requesting protection of resources, the bridge identifier field indication Whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridged.
  • a sending module configured to send
  • two overhead information groups may be included in one overhead frame to express the overhead information of the two time slots, and the overhead field is fully utilized, thereby improving the efficiency of protection switching.
  • the cost information group further includes a request flag field, where the request flag bit field is used to indicate the service of the request signal identifier field. Identifies whether the corresponding service requests protection resources.
  • two overhead groups may be included in an overhead frame, and a request flag field is set in the overhead information group, which is used to indicate whether the service corresponding to the service identifier of the overhead information group requests protection resources, and fully utilizes Overhead resources.
  • an embodiment of the present invention provides an intermediate node, including: a receiving module, configured to receive, when the working path between the first end node and the second end node fails, receive the first end of the first end node a protection switching request message, wherein the protection path of the working path includes the first end node, the second end node, and at least one of the intermediate nodes; and a sending module, configured to send a downstream neighboring node to the intermediate node Sending a first protection switching request message; receiving a module, configured to receive a downstream from the intermediate node a second protection switching request message of the neighboring node, where the sending module is configured to send a second protection switching request message to the first end node, where the one of the first protection switching request message and the second protection request message is an overhead frame Include at least two overhead information groups, the overhead information group including a request type field, a request signal identification field, and a bridge identification field; the request type field indicating a fault type of the working path, and the request signal identifier field
  • two overhead information groups may be included in one overhead frame to express the overhead information of the two time slots, and the overhead field is fully utilized, thereby improving the efficiency of protection switching.
  • the cost information group further includes a request flag field, where the request flag bit field is used to indicate the service of the request signal identifier field. Identifies whether the corresponding service requests protection resources.
  • two overhead groups may be included in an overhead frame, and a request flag field is set in the overhead information group, which is used to indicate whether the service corresponding to the service identifier of the overhead information group requests protection resources, and fully utilizes Overhead resources.
  • an embodiment of the present invention provides a second end node, including: a receiving module, configured to receive, when the working path between the first end node and the second end node fails, receive the first node from the intermediate node a protection switching request message, wherein the protection path of the working path includes the first end node, the second end node, and at least one of the intermediate nodes; and the second end node sends a second protection switching to the intermediate node a request message, where the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, the overhead information group including a request type field, a request signal identification field, and a a bridge identifier field; the request type field indicates a fault type of the work path, the request signal identifier field is a service identifier of a service requesting a protection resource, and the bridge identifier field indicates a protection corresponding to the service identifier of the request signal identifier field Whether the resource has been bridged.
  • a receiving module configured to receive, when
  • two overhead information groups may be included in one overhead frame to express the overhead information of the two time slots, and the overhead field is fully utilized, thereby improving the efficiency of protection switching.
  • the cost information group further includes a request flag field, where the request flag bit field is used to indicate the service of the request signal identifier field. Identifies whether the corresponding service requests protection resources.
  • two overhead groups may be included in an overhead frame, and a request flag field is set in the overhead information group, which is used to indicate whether the service corresponding to the service identifier of the overhead information group requests protection resources, and fully utilizes Overhead resources.
  • an embodiment of the present invention provides an OTN device, including: a main control board, a tributary board, a cross board, and a circuit board; the main control board runs a pre-configured program, and controls the tributary board, the cross board, and the circuit board. Any one or more of the boards, the method of any one of the first aspect and the first aspect, the second aspect, and any one of the possible implementations of the second aspect The method of any one of the possible implementations of the third aspect and the third aspect.
  • the embodiment of the present invention provides a network system, comprising: the node according to any one of the fourth aspect and the fourth aspect, and the fifth aspect and the fifth aspect Possible implementations of the described nodes.
  • the embodiment of the present invention provides a network system, comprising: the node according to any one of the fifth aspect and the fifth aspect, and the sixth aspect and the sixth aspect Possible implementations of the described nodes.
  • At least two overhead information groups are included in one overhead frame of the protection switching request message, one of which
  • the overhead information group includes a request type field, a request signal identifier field, and a bridge identifier field;
  • the request type field indicates a fault type of the working path, and the request signal identifier field is a service identifier of a service requesting protection of the resource, where
  • the bridge flag field indicates whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridged.
  • FIG. 1 is a schematic diagram of an APS overhead coding format in the prior art
  • FIG. 2 is a schematic diagram of a network topology structure of an APS according to an embodiment of the present invention
  • FIG. 3 is a flow chart of protection switching signaling using a prior art APS overhead coding format
  • FIG. 4 is a schematic diagram of a connection structure between a node A and a node E according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a format of an APS message according to an embodiment of the present invention.
  • FIG. 5b is a schematic diagram of an APS overhead coding format provided by an embodiment of the present invention.
  • FIG. 5c is a schematic diagram of an APS overhead coding format according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of an APS overhead coding format provided by an embodiment of the present invention.
  • FIG. 6 is a signaling flowchart of a protection switching of an APS overhead coding format according to an embodiment of the present invention
  • FIG. 6b is a signaling flowchart of a protection switching of an APS overhead coding format according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of an APS overhead coding format provided by an embodiment of the present invention.
  • FIG. 7b is a schematic diagram of an APS overhead coding format provided by an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of another APS overhead coding format provided by an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of another APS overhead coding format provided by an embodiment of the present invention.
  • FIG. 10a is a signaling flowchart of fault recovery in an APS overhead coding format according to an embodiment of the present invention.
  • FIG. 10b is a signaling flowchart of fault recovery in an APS overhead coding format according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a message overhead coding format of an NR (W1, 0, 1) according to an embodiment of the present invention
  • FIG. 12 is a signaling flowchart of a protection switching of an APS overhead coding format according to an embodiment of the present invention.
  • FIG. 12b is a signaling flowchart of a protection switching of an APS overhead coding format according to an embodiment of the present invention
  • FIG. 13 is a schematic diagram of a message overhead coding format of an SF (W2, 1, 0) according to an embodiment of the present invention
  • FIG. 14 is a schematic structural diagram of a network node according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a network node according to an embodiment of the present invention.
  • FIG. 16 is a schematic structural diagram of a network node according to an embodiment of the present invention.
  • FIG. 17 is a schematic structural diagram of a network system according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of an OTN device according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of a network topology structure of an SMP according to an embodiment of the present invention.
  • S1 and S2 are two working paths, and the paths are A-B and C-D, respectively.
  • P1 is the protection path of S1
  • the path is A-E-F-G-B
  • P2 is the protection path of S2
  • the path is C-E-F-G-D
  • the path of shared protection resources of S1 and S2 is E-F-G.
  • the protection resources include resources such as nodes, links, and bandwidth.
  • the service ID of the service corresponding to S1 and P1 is W1
  • the service ID of the service corresponding to S2 and P2 is W2.
  • the APS overhead can represent the overhead of multiple protection switching types, such as SMP, 1+1 protection, 1:1 protection, linear protection, and so on.
  • the APS message carrying the APS overhead is used to indicate a protection switching signaling message, such as an SMP protection switching signaling message, and one frame of the APS overhead per 8 frames expresses an SMP protection switching signaling message.
  • the cost of which link granularity is used depends on the link granularity of the protection path of the service on the working path carrying the fault.
  • the APS overhead of different link granularities corresponds to the same transmission bandwidth and number of timeslot resources, but the APS overhead is encoded in the same format.
  • the minimum link granularity is ODU (Optical Channel Data Unit) 0, and its bandwidth is 1.25 G, occupying one slot resource.
  • the other link granularities may include: ODU1, ODU2, ODU3, and ODU4, and the bandwidths are 2.5G, 10G, 40G, and 100G, respectively, occupying 2, 8, 32, and 80 time slot resources respectively.
  • ODU2 link is used to protect the traffic of the ODU0 link
  • one of the eight time slots is used in the protection switching, and the overhead of the ODU2 should be used.
  • FIG. 3 is a flow chart of protection switching signaling using a prior art APS overhead coding format.
  • FIG. 3 in the network topology shown in FIG. 2, when it is detected that S1 is faulty, it is necessary to activate the protection path P1 of S1: A-E-F-G-B.
  • the processing of the node involves bridging and selection. Specifically, bridging means activating a node for transmitting data, and selecting to activate a node for receiving data.
  • both bridging and selection have two directions
  • bridging 1 and bridging 2 indicates that data is transmitted from two directions
  • selection 1 and selection 2 indicate that data is received from two directions, respectively.
  • Bridging 1 and selection 1 indicate data transmission in one direction
  • bridging 2 and selection 2 indicate data transmission in the other direction.
  • end node A there is only one direction for bridging and selection, and the bridging and selection are in the opposite direction.
  • establishing a bridge between the EAs on the node E that is, establishing a bridge 2 on the node E for transmitting data to the node A
  • establishing a selection between the AEs on the node E that is, establishing a selection 1 on the node E, Used to receive data from node A.
  • end node A has only one direction of bridging or selection (bridge 3 or select 4)
  • intermediate node E has bridging and selection in one direction (bridge 1 + select 1, or bridge 2+ select 2
  • bridge 3 and option 4 For two-way services, end node A has bridge 3 and option 4, and intermediate node E has bridging and selection in both directions.
  • the end node includes a source node and a sink node, and the intermediate node refers to a node having at least one neighbor node.
  • the direction of signaling transmission can be from the source node to the sink node, and also from the sink node to the source node.
  • the upstream direction and the downstream direction are opposite, and either one direction may be the upstream direction and the other direction may be the downstream direction.
  • the node A is the source node of S1 and P1
  • the node B is the sink node of S1 and P1 as an example.
  • S1 or P1 the direction from node A to node B is the downstream direction
  • the direction from node B to node A is the upstream direction.
  • the source node A of P1 completes the bridging with the downstream node E, and sends a signal failure message SF (W1, W1) to the downstream node E.
  • Resource availability includes idle resources between A-Es, or resources between A-Es are occupied by low priority services.
  • the signal invalidation message can be represented by the APS overhead, and the APS overhead coding format is SF (W1, W1). Where SF(W1, W1) indicates that the signal is invalid, requesting activation of the protection path, and the node that sent the message has completed bridging.
  • the node E After receiving the signal failure message SF (W1, W1), the node E confirms that the resources between the E-Fs are available, the node E completes the bridging, and sends the same signal failure message SF (W1, W1) to the downstream node F.
  • the processing flow of the nodes F and G is similar to that of the node E, and is not described here.
  • the sink node B of P1 After the sink node B of P1 receives the signal failure message SF(W1, W1), it confirms that the protection resources between the G-Bs are available, completing the selection and bridging.
  • the Node B then sends a reverse request message RR (W1, W1) to the upstream node G, informing the node G to complete the selection.
  • the reverse request message may be represented by an APS overhead, and the encoding format is RR (W1, W1), indicating a reverse request, requesting activation of the protection path, and the node transmitting the reverse request message has completed bridging.
  • the node G After receiving the reverse request message, the node G receives the reverse request message RR (W1, W1), confirms that the resources between the G-Fs are available, completes the selection, and sends the same reverse request message RR (W1, W1) to the upstream node F.
  • the processing flow of the nodes F and E is similar to that of the node G, and will not be described again.
  • the source node A After the source node A receives the reverse request message RR (W1, W1), the selection is completed, and the protection switching of W1 is completed, that is, W1 is switched from the working path S1 to the protection path P1.
  • the embodiment of the present invention provides an APS overhead coding format, which can fully utilize the overhead resource.
  • the APS message includes APS overhead and payload.
  • the APS overhead is a part of the OTN overhead, and is used to carry the status information of the protection switching, such as the protection switching request type, the service ID, and the like, and the payload part is used to carry the service information.
  • the embodiment of the present invention mainly defines an APS overhead part.
  • FIG. 5b is a schematic diagram of an APS overhead coding format provided by an embodiment of the present invention. As shown in Figure 5b, the encoding format Among them, there are 4 types of information described:
  • Request Type A type indicating the protection switching request included in the first to fourth bits, such as SF, SD, RR, NR, MS, and FS.
  • the SF is used in the scenario where the working path is faulty, and the service is switched from the working path to the protection path;
  • the SD is used to degrade the working path signal, and the service is switched from the working path to the protection path;
  • the RR is used to respond to the SF, SD, and the like.
  • the NR is used to recover the fault from the working path, and the service is switched from the protection path to the working path.
  • the MS and FS are used for the scenario of manual switching and forced switching.
  • Request Signal ID A service ID including a service ID of a request to protect a path resource, such as W1, in the fifth to twelfth bits.
  • the service ID service is in the normal state. When there is no request for the protection path resource, the Request Signal ID can be set to all 0s.
  • the service path and the protection path may correspond to the same service ID. For example, the service ID of the service corresponding to S1 and P1 is W1, and the service ID of the service corresponding to S2 and P2 is W2.
  • Requested Flag Included in the 13th bit, indicating whether the service whose service ID is Request Signal ID has been requested.
  • the protection path resource corresponding to the service ID of the Request Signal ID is requested, and the RF can be set to 1. If the working path is not faulty, the service corresponding protection path resource whose service ID is Request Signal ID is not Requested, RF can be set to zero. If the Request Signal ID is set to all 0s, the RF flag bit has no meaning.
  • BF Bridge Flag It is included in the 14th bit, indicating whether the service whose service ID is Request Signal ID is bridged on the node corresponding to the protection path. If the service with the service ID of the Request Signal ID is bridged on the node corresponding to the protection path, the BF is set to 1; if the service with the service ID of the Request Signal ID is not bridged on the node corresponding to the protection path, the BF is set to 0. If the Request Signal ID is set to all 0s, the BF flag has no meaning.
  • bit positions of the foregoing four types of information in the APS overhead coding are not limited to the foregoing embodiments.
  • the locations of RF and BF can be interchanged.
  • the Request Flag since the Request Flag can also be uniquely identified by the Request Type, the Request Flag may not be included in the above encoding format. As shown in Figure 5c, the RF flag is omitted and the BF can be shifted one bit forward and the reserved field is incremented by one bit.
  • the type of the protection switching request such as SF, SD, RR, MS, FS, etc., indicates that the Request Flag is 1; the type of the NR protection switching request indicates that the Request Flag is 0.
  • the foregoing encoding format may further include a selection flag Selector Flag (SeF).
  • the selection flag bit may be represented by one bit in the reserved field, indicating whether the service whose service ID is the Request Signal ID has been selected. If the service ID is the Request Signal ID, the SeF is set to 1 on the node corresponding to the protection path. If the service ID is the Request Signal ID, the service is not established on the node corresponding to the protection path. 0. If the Request Signal ID is set to all 0s, the selection flag is meaningless.
  • the service ID of the service requesting the protection path resource is not limited to 8 bit lengths, and may be increased to 9 bits or 10 bits. If it is necessary to increase the bit, the RF and BF bits are postponed to the following bits, and the bits of the Resv reserved field are occupied. For example, if 9 bits are required to indicate the Request Signal ID, the first to fourth bits are the Request Type, and the fifth to third bits are the Request Signal ID. The 14th bit is RF, the 15th bit is BF, and the 16th bit is Resv. If 10 bits are required to indicate the Request Signal ID, the first to fourth bits are the Request Type, the fifth to the 14th bits are the Request Signal ID, the 15th bit is the RF, and the 16th bit is the BF. If the above encoding format also includes a Selector Flag, the reserved field has only 1 bit available, and the service ID can be increased to 9 bits.
  • the 17th to 32nd bits have the same meanings as the first to the 16th bits, but correspond to different time slots.
  • the above 4-byte encoding format is regarded as one frame.
  • the first to the 16th bits represent the slot 1
  • the 17th to 32nd bits represent the slot 2.
  • 4 frames, 16 frames, and 40 frames are respectively required to represent the APS message.
  • the overhead information of two time slots is expressed in one frame, the number of frames is reduced by half compared with the prior art, that is, the overhead resources are saved by 50%, and the APS overhead field is fully utilized. .
  • FIG. 6 is a signaling flowchart of a protection switching of an APS overhead coding format according to an embodiment of the present invention.
  • S1 in the network topology shown in FIG. 2, when it is detected that S1 is faulty, it is necessary to activate the protection path P1 of S1: A-E-F-G-B.
  • SF(W1,1,1) indicates that the signal is invalid, and the status of the protection resource corresponding to W1 is updated as: has been requested by W1, and is bridged.
  • RR (W1, 1, 1) indicates a reverse request, and the status of the protection resource corresponding to W1 is updated as follows: it has been requested by W1 and is bridged.
  • FIG. 7 is a schematic diagram of an APS overhead coding format according to an embodiment of the present invention.
  • the signal failure message SF (W1, 1, 1) is taken as an example for description.
  • the service of the ODU0 link is protected by the ODU2 link.
  • the protection resources of one slot in the ODU2 link need to be occupied.
  • the overhead coding format of Figure 7a indicates that the first time slot of the ODU2 link is requested by W1 and is bridged; the overhead coding format of Figure 7b indicates that the second time slot of the ODU2 link is requested by W1 and is bridged.
  • the first time slot and the second time slot may be any time slots in the ODU2 link, and may be configured on the node before the working path fails.
  • FIG. 8 is a schematic diagram of another APS overhead coding format provided by an embodiment of the present invention.
  • the signal failure message SF (W1, 1, 1; W1, 1, 1) is taken as an example for description.
  • the service of the ODU1 link is protected by the ODU2 link.
  • the protection resources of the two slots in the ODU2 link need to be occupied.
  • the overhead coding format of Figure 8 indicates that the first time slot and the second time slot of the ODU2 link are requested by W1 and are bridged.
  • the first time slot and the second time slot may be any time slots in the ODU2 link, and may be configured on the node before the working path fails.
  • FIG. 9 is a schematic diagram of another APS overhead coding format provided by an embodiment of the present invention.
  • the signal failure message SF (W1, 1, 1; W2, 1, 1) is taken as an example for description.
  • the service of the two ODU0 links is protected by the ODU2 link.
  • the two slots in the ODU2 link need to occupy the protection resources.
  • Each ODU0 link occupies one time slot.
  • the overhead coding format of Figure 9 indicates that the first time slot of ODU2 is requested by W1 and is bridged, and the second time slot of the ODU2 link is W2. Requested and bridged.
  • FIG. 6a is a process of initiating a protection switching signaling by the node A
  • FIG. 6b is a process of simultaneously initiating a protection switching signaling by the node A and the node B.
  • FIG. 6a is an example of FIG. 6a:
  • Node A When node A detects that the working path is faulty, it sends a signal invalidation message to the downstream node E. And, node A receives a reverse request message from the downstream node E.
  • the node A detects that the working path S1 is faulty, and the node A itself detects the link failure, or the node B notifies the node A after detecting the link failure.
  • node A detects that the working path is faulty, it can establish a bridge between A-Es after confirming that resources between node A and downstream node E are available.
  • bridge 3 shown in FIG.
  • the resources available here are free, that is, no other services are occupied. Of course, the availability of resources may also include resources being occupied by low priority services.
  • Node A may send a signal invalidation message SF (W1, 1, 1) to downstream node E after establishing a bridge between A-Es.
  • the node A when the node A receives the reverse request message RR (W1, 1, 1) of the node E, depending on when the node E sends the message to the node A, refer to the execution step of the node E. After receiving the RR (W1, 1, 1) message sent by the node E, the node A determines that the resource between the node A and the node E is available, and establishes a selection between the E-A, such as the selection 4 shown in FIG.
  • the signal invalidation message sent by the node A to the downstream node E can be represented by the APS overhead, and the coding format is SF (W1, 1, 1), indicating that the signal is invalid, the protection path P1 has been requested by W1, and the bridge has been established.
  • the reverse request message received by the node A from the downstream node E may be represented by the APS overhead, and the coding format is RR (W1, 1, 1), indicating the reverse request, confirming the protection path P1 of the activated W1, and the node transmitting the message has Establish a bridge.
  • the overhead coding formats of the signal failure message SF (W1, 1, 1) and the reverse request message RR (W1, 1, 1) can be referred to FIG. 5b to 5d, FIG. 7a, FIG. 7b, FIG. 8 and FIG.
  • the present invention is not limited to the number of services for requesting protection path resources in the overhead coding, the number of time slots occupying protection resources, and the like.
  • Node E After receiving the signal failure message from the node A, the node E sends a signal failure message to the downstream node F, sends a reverse request message to the upstream node A, and the node E receives the reverse request message from the downstream node F.
  • the node E may establish a bridge between the EFs after determining that resources between the node E and the downstream node F are available, for example, as shown in FIG. Bridge 1 of node E; and, after determining that resources between node E and upstream node A are available, a choice between AEs is established, for example, selection 1 of node E as shown in FIG.
  • the node E may establish a selection between the A-Es after receiving the RR (W1, 1, 1) message from the node F.
  • the node E may first send a signal failure message SF (W1, 1, 1) to the downstream node F, and then send a reverse request message RR (W1, 1, 1) to the upstream node A; or, the node E may also first forward to the upstream node.
  • A sends an RR (W1, 1, 1) message, and then sends an SF (W1, 1, 1) message to the downstream node F.
  • the node E may immediately send an RR (W1, 1, 1) message to the node A after receiving the SF (W1, 1, 1) message from the node A.
  • the node E may further send an RR (W1, 1, 1) message to the node A after receiving the RR (W1, 1, 1) message sent by the node F.
  • Sending this message to the node E can refer to the process in which the node A receives the RR (W1, 1, 1) message of the node E.
  • the node E After receiving the RR (W1, 1, 1) message of the node F, the node E establishes a bridge between the EAs after determining that the resources between the node E and the upstream node A are available, for example, the node E as shown in FIG. Bridging 2; and, after determining that resources between node E and downstream node F are available, a choice between FEs can be established, for example, selection 2 as shown in FIG.
  • Node F After receiving the signal failure message from the upstream node E, the node F sends a signal failure message to the downstream node G, sends a reverse request message to the upstream node E, and the node F receives the reverse request message from the downstream node G.
  • the processing flow of the node F is similar to that of the node E, and will not be described again.
  • Node G After receiving the signal failure message from the upstream node F, the node G transmits a signal failure message to the downstream node B, sends a reverse request message to the upstream node F, and the node G receives the reverse request message from the downstream node B.
  • the processing flow of the node G is similar to that of the node E, and will not be described again.
  • Node B After receiving the signal failure message from the upstream node G, the Node B sends a reverse request message to the upstream node G.
  • the node B After receiving the signal failure message SF(W1, 1, 1) from the upstream node G, the node B confirms that the resource between the node B and the node G is available, establishes a selection between the GB, and bridges between the BGs, and A reverse request message is sent to the upstream node G. Specifically, the Node B establishes a selection between the G-Bs and a bridge between the B-Gs, which may be to establish a connection first, and then establish a bridge; or establish a bridge first, and then establish a selection; and may also establish selection and bridging at the same time.
  • the node B may also send a signal invalidation message to the direction of the node A, and the node A sends a reverse request message to the direction of the node B, and the signaling process is similar.
  • node A and node B simultaneously send a signal invalidation message to the opposite node.
  • the node A transmits an SF (W1, 1, 1) message to the direction of the node B
  • the node B transmits an SF (W1, 1, 1) message to the direction of the node A.
  • the processing steps for each node to receive an SF (W1, 1, 1) message are similar.
  • each node may not send an RR (W1, 1, 1) message after receiving the SF (W1, 1, 1) message.
  • the node A and the node B may also initiate a bearer switching signaling process at different times. The present invention does not limit the sequence of the signaling process.
  • the APS message of one frame can express the overhead of two time slots, which improves the utilization of overhead resources, thereby improving the efficiency of protection switching when the working path is faulty. .
  • FIG. 10a and FIG. 10b are signaling flowcharts of fault recovery in an APS overhead coding format according to an embodiment of the present invention.
  • the signaling flow shown in FIG. 6a and FIG. 6b that is, after the service W1 is switched from the working path S1 to the protection path P1, the working path S1 is recovered, and the service is rolled back from the protection path P1 to the working path S1.
  • NR(W1, 0, 1) indicates no request
  • the status of the protection resource corresponding to W1 is updated to: no request, bridged.
  • NR(0,0,0) indicates no request, and the protection resource status is updated to: no service bridging.
  • FIG. 10a is a flow of protection recovery signaling initiated by node A
  • FIG. 10b is a flow of protection recovery signaling initiated by node A and node B, which is illustrated by using FIG. 10a as an example:
  • Node A When node A detects failure recovery of the working path, it sends a first no-request message to the downstream node E and receives a second no-request message from the downstream node E.
  • the fault recovery may be detected by the source and the sink node, or may be detected by any one of the source node and the sink node, or the source and the sink node may be detected at the same time.
  • the E-A selection can be released.
  • node A may release the selection between E-A before transmitting the NR (W1, 0, 1) message or after transmitting the NR (W1, 0, 1) message.
  • the node A when the node A receives the second request message NR(0, 0, 0) sent by the node E, depending on when the node E sends the message to the node A, refer to the execution step of the node E. After receiving the NR (0, 0, 0) message of the node E, the node A releases the bridge between the A-Es.
  • the first no-request message sent by the node A to the downstream node E may be represented by the APS overhead, and the coding format is NR (W1, 0, 1), indicating that the protection resource corresponding to W1 has no request, but the bridge has been established.
  • the second no-request message of the node A receiving the downstream node E may be represented by the APS overhead, and the coding format is NR (0, 0, 0), indicating that the protection resource has no request, and no bridging is established.
  • FIG. 11 is a schematic diagram of a message overhead coding format of NR (W1, 0, 1) according to an embodiment of the present invention.
  • the overhead coding format of Figure 11 indicates that there is no request for the first time slot and the second time slot of the ODU2 link, but a bridge has been established.
  • the overhead coding format of NR(0,0,0) can be seen in FIG. 11, and the Request Signal ID and the Bridge Flag in NR(W1, 0, 1) are both set to 0.
  • the overhead coding formats of the first no-request message NR (W1, 0, 1) and the second no-request message NR (0, 0, 0) can also refer to Figures 5b - 5d, Figure 7a, Figure 7b, Figure 8 and Figure 9.
  • the number of services for requesting protection path resources in the overhead coding, the number of time slots occupying protection resources, and the like are not limited by the present invention.
  • Node E receives the first no-request message of the upstream node A, sends a first no-request message to the downstream node F, sends a second no-request message to the upstream node A, and the node E receives the first from the downstream node F. Two no request messages.
  • the node E receives the first no-request message NR (W1, 0, 1) of the upstream node A. And, after transmitting the first no-request message, the node E releases the selection between the FEs, for example, the selection 2 of the node E as shown in FIG. 4; and releases the bridge between the EAs, for example, as shown in FIG. Bridge E of E.
  • the node E may first send the first no-request message NR (W1, 0, 1) to the downstream node F, and then send the second no-request message NR (0, 0, 0) to the upstream node A; or, the node E may also first The NR (0, 0, 0) message is sent to the upstream node A, and the NR (W1, 0, 1) is sent to the downstream node F.
  • the node E may send an NR (0, 0, 0) message to the node A immediately after receiving the NR (W1, 0, 1) message from the node A.
  • the node E may further send an NR (0, 0, 0) message to the node A after receiving the NR (0, 0, 0) message of the node F.
  • the node E When the node E receives the second requestless message NR(0,0,0) of the node F, depending on when the node F sends the message to the node E, the node A can receive the NR of the node E (0, 0, 0) The process of the message. After receiving the NR(0,0,0) message of the node F, the node E releases the bridge between the E-Fs, for example, as shown in FIG. Bridge 1 is shown; and, the choice between A-E is released, for example, selection 1 as shown in FIG.
  • Node F After receiving the first no-request message from the upstream node E, the node F sends a first no-request message to the downstream node G, sends a second no-request message to the upstream node E, and the node F receives the message from the downstream node G. The second no request message.
  • the processing flow of the node F is similar to that of the node E, and will not be described again.
  • Node G After receiving the first no-request message from the upstream node F, the node G sends a first no-request message to the downstream node B, sends a second no-request message to the upstream node F, and the node G receives the message from the downstream node B. The second no request message.
  • the processing flow of the node G is similar to that of the node F, and will not be described again.
  • Node B After receiving the first no-request message from the upstream node G, the Node B sends a second no-request message to the upstream node G.
  • the Node B after receiving the first no-request message NR (W1, 0, 1) from the upstream node G, the Node B releases the bridging between the BGs and the selection between the GBs, and sends a second no-request to the upstream node G.
  • the Node B releases the selection between the G-Bs and the bridge between the B-Gs, which may be to release the selection first, and then release the bridge; or release the bridge first, then release the selection; and simultaneously release the selection and the bridge.
  • the node B sends a first no-request message to the direction of the node A, and the node A sends a second no-request message to the direction of the node B, and the signaling process is similar.
  • node A and node B simultaneously send a first no-request message to the opposite node.
  • the node A sends an NR (W1, 0, 1) message to the direction of the node B, and after receiving the message, the node B sends an NR (0, 0, 0) message to the direction of the node A.
  • Node B sends an NR (W1, 0, 1) message to the direction of Node A.
  • Node A After receiving the message, Node A sends an NR (0, 0, 0) message to the direction of Node B.
  • the processing steps for each node to receive an NR (W1, 0, 1) message are similar. Since the NR (W1, 0, 1) message is sent bidirectionally, each node may not release the bridge and select after receiving the NR (0, 0, 0) message.
  • the node A and the node B may also initiate a bearer switching signaling process at different times. The present invention does not limit the sequence of the signaling process.
  • the APS message of one frame can express the overhead of two time slots, thereby improving the utilization of overhead resources, thereby improving service recovery when the working path is faulty. effectiveness.
  • FIG. 12 is a signaling flowchart of a protection switching of an APS overhead coding format according to an embodiment of the present invention.
  • the path of the protection path P1 of the working path S1 and the protection path P2 of the working path S2 share the protection resource is E-F-G, and the priority of the shared protection resource occupied by the service W2 is higher than that of the service W1.
  • the signaling flow shown in Figures 6a and 6b that is, after W1 is switched from S1 to P1, when it is detected that S2 fails, it is necessary to activate the protection path P2 of S2: C-E-F-G-D.
  • the signaling process involves the service W1 being rolled back from the protection path P1 to the working path S1. This process is resumed with the working path S1 of FIG. 10a and FIG. 10b, and the service W1 is rolled back from the protection path P1 to the working path.
  • the signaling process is similar.
  • the over-signaling process of the W2 preempting the shared protection resource involves the APS message SF (W2, 1, 0), indicating that the signal is invalid, and the status of the protection resource corresponding to the W2 is updated as: Request, but not bridged.
  • FIG. 12a is a flow of the protection switching signaling initiated by the node C before the node D
  • FIG. 12b is a flow of the protection switching signaling initiated by the node C and the node D.
  • FIG. 12a Be explained:
  • Node C When detecting that the working path fails, the node C sends a first signal failure message to the downstream node E and receives a first signal failure message from the downstream node E.
  • the node C is the source node of S2 and P2
  • the node D is the sink node of S2 and P2 as an example.
  • the direction from the node C to the node D is the downstream direction
  • the direction from the node D to the node C is the upstream direction.
  • the node C detects that the working path S2 fails.
  • the node C itself detects the link failure, or the node D notifies the node C after detecting the link failure.
  • node C detects that the working path is faulty, it can determine that the resources between node C and node E are available, and establish a bridge between C-Es.
  • the resources available here are free, that is, no other services are occupied.
  • Node C may send a first signal failure message SF (W2, 1, 1) to downstream node E after establishing a bridge between C-Es.
  • the node C When the node C receives the first signal failure message SF (W2, 1, 1) from the downstream node E, depending on when the node D initiates the protection switching signaling flow in the direction of the node C, for details, refer to the node D and the node.
  • the execution steps of E After receiving the SF (W2, 1, 1) message sent by the node E, the node C determines that the resource between the node C and the node E is available, and establishes a selection between the E-Cs.
  • the first signal failure message may be delivered through the APS message in an encoding format of SF (W2, 1, 1) indicating that the signal is invalid, the protection path P2 has been requested by W2, and is bridged.
  • the overhead coding format of the signal failure message SF (W2, 1, 1) may refer to the embodiments shown in FIG. 5b to 5d, FIG. 7a, FIG. 7b, FIG. 8 and FIG. 9, for the request protection path in the overhead coding.
  • the number of services of the resource, the number of time slots occupying the protection resources, and the like are not limited in the present invention.
  • Node E After receiving the first signal failure message of the upstream node C, the node E sends a second signal failure message to the downstream node F, receives the first signal failure message from the downstream node F, and sends the first signal to the upstream node C. Invalid message.
  • the node E After receiving the first signal failure message SF (W2, 1, 1) of the upstream node C, the node E detects that the resources between the EFs are occupied by W1, does not establish a bridge between the EFs, and reaches the downstream node F. A second signal failure message SF (W2, 1, 0) is sent. After receiving the SF (W2, 1, 1) message of the node C, the node E determines that the resources between the node E and the upstream node C are available, and can establish a selection between the C-Es. Optionally, the node E may further establish a selection between C-Es after receiving the first signal failure message SF (W2, 1, 1) of the downstream node F.
  • the node E can compare the priorities of W1 and W2, and after determining that the priority of W2 is higher than the priority of W1, the node E is notified that the upstream node A of P1 rolls back the service W1 from P1 to the working path S1.
  • the node E may also notify the node B to roll back the service W1 to the working path S1 through the nodes F and G.
  • the process of the service W1 rollback is similar to the signaling process of FIG. 10a and FIG. 10b, and details are not described herein again.
  • the node E When the node E receives the first signal failure message SF (W2, 1, 1) transmitted from the downstream node F, depends on when the node D initiates a protection switching signaling procedure in the direction of the node C. After receiving the SF (W2, 1, 1) message of the node F, the node E determines that the resource between the node E and the node F is available, and establishes the relationship between the F-E. Select, and, after determining that resources between node E and node C are available, establish a bridge between E-Cs. After establishing a bridge between E-Cs, node E sends an SF (W2, 1, 1) message to upstream node C.
  • the node E After receiving the SF (W2, 1, 1) message from the downstream node F, the node E determines that the resources between the node E and the node F are available, and establishes a bridge between the E-Fs. Alternatively, if node E has not yet established a choice between C-Es, a selection between C-Es may also be established at this time. And, the node E also sends an SF (W2, 1, 1) message to the downstream node F.
  • the node E may first send an SF (W2, 1, 1) message to the upstream node C, and then send an SF (W2, 1, 1) message to the downstream node F; or, the node first sends the SF to the downstream node F (W2) , 1, 1) message, and then send an SF (W2, 1, 1) message to the upstream node C.
  • FIG. 13 is a schematic diagram of a message overhead coding format of an SF (W2, 1, 0) according to an embodiment of the present invention.
  • the ODU0 link when used to protect the services of the ODU0 link, the ODU0 link needs to occupy the protection resources of one time slot in the ODU2 link.
  • the overhead coding format shown in Figure 13 indicates that the first time slot of the ODU2 link is requested by W2, but is not bridged.
  • the overhead coding format of the second signal failure message SF (W2, 1, 0) can also refer to the embodiments shown in FIG. 5b to 5d, FIG. 7a, FIG. 7b, FIG. 8 and FIG. 9, for the request protection path in the overhead coding.
  • the number of services of the resource, the number of time slots occupying the protection resources, and the like are not limited in the present invention.
  • Node F receives the second signal failure message of the upstream node E, sends a second signal failure message to the downstream node G, receives the first signal failure message from the downstream node G, and sends the first signal failure to the upstream node E. Message.
  • the node F and the processing flow are similar to the node E and will not be described again.
  • Node G receives the second signal failure message of the upstream node F, sends a first signal failure message to the downstream node D, receives the first signal failure message from the downstream node D, and sends the first signal failure to the upstream node F. Message.
  • the node G After receiving the second signal failure message SF(W2, 1, 0) of the upstream node F, the node G detects that the resource between the node G and the downstream node D is available, establishes a bridge between the GD, and sends the bridge to the downstream node D.
  • the first signal fails message SF(W2, 1, 1).
  • the node G After receiving the SF (W2, 1, 0) message of the node F, the node G notifies the node B to roll back W1 from the protection path P1 to the working path S1. At this time, the resources between the node G and the node F are not occupied by other services, and the node G can establish a selection between the F-Gs.
  • the node G may further establish a selection between the F-Gs after receiving the first signal failure message SF (W2, 1, 1) sent by the upstream node F.
  • the node G After the node G receives the first signal failure message SF(W2, 1, 1) of the downstream node D, if the node G has received the second signal failure message SF (W2, 1, 0) from the upstream node F, then It can be determined that the resource between the node G and the node F has been released by the service W1, and the resources between the GFs are available. Node G can establish a bridge between G-Fs, establish a selection between D-Gs, and node G sends an SF (W2, 1, 1) message to upstream node F.
  • the node G may first receive the SF (W2, 1, 1) message from the node D, and then receive the SF (W2, 1, 0) message of the node F.
  • the node G receives the SF (W2, 1, 1) message of the node D, and does not receive the SF (W2, 1, 0) message of the node F, then the resources between the GFs are May be occupied by the business W1.
  • Node G can first establish a choice between D-G, but does not establish a G-F between Bridging and sending an SF (W2, 1, 0) message to the upstream node F.
  • the node G When the node G receives the SF (W2, 1, 1) message of the node F, depending on when the node F sends the message.
  • the node F may send an SF (W2, 1, 1) message to the node G after receiving the SF (W2, 1, 1) message of the node G.
  • the node F may also receive the SF (W2, 1, 1) message of the node E and then send the SF (W2, 1, 1) message to the node G.
  • Node D The node D receives the first signal failure message of the upstream node G, and sends a first signal failure message to the upstream node G.
  • Node D may also determine that the node G to node D resources are not occupied by other services, are in an available state, establish a selection between G-Ds, and bridge between D-Gs after detecting that the working path has failed. And, the node D transmits a first signal failure message SF (W2, 1, 1) to the upstream node G.
  • SF first signal failure message
  • the node D may initiate a protection switching signaling process after detecting that the working path S2 has failed. Alternatively, after receiving the SF (W2, 1, 1) message of the upstream node G, the node D initiates a protection switching signaling procedure. Specifically, the node D may send the first signal failure message SF (W2, 1, 1) to the upstream node G before receiving the first signal failure message SF (W2, 1, 1) of the upstream node G. Alternatively, the node D may also send an SF (W2, 1, 1) message to the upstream node G after receiving the SF (W2, 1, 1) message of the upstream node G.
  • the protection switching signaling procedure may be separately initiated by the node C or the node D.
  • node C and node D simultaneously send a first signal failure message to the opposite node.
  • node C and node D simultaneously detect a working path failure
  • node C sends SF (W2, 1, 1) to node E
  • node D sends SF (W2, 1, 1) to node G
  • node E The node F sends the SF (W2, 1, 0)
  • the node G sends the SF (W2, 1, 0) to the node F; at this time, the node F receives the SF (W2, 1, 0) from both directions, and determines the service.
  • W1 has been rolled back, then W2 bridging and selection can be established, and SF (W2, 1, 1) is sent to node E and node G; after receiving SF (W2, 1, 1), node E sends SF to node F. (W2, 1, 1), and send SF (W2, 1, 1) to node C; after receiving SF (W2, 1, 1), node G sends SF (W2, 1, 1) to node F, and The SF (W2, 1, 1) is sent to the node D.
  • Each node can establish bridging and selection separately after receiving the SF (W2, 1, 1) message.
  • the APS message of one frame can express the overhead of two time slots, and the APS overhead field is fully utilized, thereby improving the efficiency of protection switching when the working path is faulty.
  • FIG. 14 is a schematic structural diagram of a network node according to an embodiment of the present invention.
  • the first end node 140 includes a sending module 141 and a receiving module 142.
  • the first end node 140 can be a common end node of the working path and the protection path.
  • the sending module 141 is configured to send a first protection switching request message to the intermediate node when the working path between the first end node and the second end node fails, where the protection path of the working path includes The first end node, the second end node, and at least one of the intermediate nodes;
  • the receiving module 142 is configured to receive a second protection switching request message from the intermediate node, and switch the service data to the protection path for transmission;
  • the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, where the overhead information group includes a request type field and a request signal label. Identification field and a bridge identification field;
  • the request type field indicates a fault type of the working path
  • the request signal identifier field is a service identifier of a service requesting a protection resource
  • the bridge identifier field indicates whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridging.
  • the overhead information group further includes a request flag field, where the request flag bit field is used to indicate whether the service corresponding to the service identifier of the request signal identifier field requests protection resources.
  • the overhead information group further includes a reserved field, where the request type field occupies 4 bits, the request signal identifier field occupies 8 bits, and the request flag bit field occupies 1 bit, and the bridge identifier The field occupies 1 bit, and the reserved field occupies 2 bits.
  • the request type field occupies 4 bits
  • the request signal identifier field occupies 10 bits
  • the request flag field occupies 1 bit
  • the bridge identifier field occupies 1 bit.
  • the overhead information group further includes a reserved field, where the request type field occupies 4 bits, the request signal identification field occupies 9 bits, the request flag field occupies 1 bit, and the bridge identifier field 1 bit, and the reserved field occupies 1 bit.
  • the overhead information group may further include a selection flag field, where the selection flag bit field is used to indicate whether the protection resource corresponding to the service identifier of the request signal identifier field has been selected.
  • the first protection switching request message and the second protection switching request message are APS messages.
  • an overhead frame of the protection switching request message may include two cost group information, express the overhead of the two time slots, fully utilize the overhead field, and improve the protection. The efficiency of switching.
  • FIG. 15 is a schematic structural diagram of a network node according to an embodiment of the present invention.
  • the intermediate node 150 includes a receiving module 151 and a transmitting module 152.
  • the intermediate node 150 can be one of a plurality of intermediate nodes in the protection path.
  • the receiving module 151 is configured to receive a first protection switching request message of the first end node when the working path between the first end node and the second end node fails, where the protection path of the working path includes the a first end node, the second end node, and at least one of the intermediate nodes;
  • the sending module 152 is configured to send a first protection switching request message to a downstream neighboring node of the intermediate node;
  • the receiving module 151 is configured to receive a second protection switching request message from a downstream neighboring node of the intermediate node;
  • the sending module 152 is configured to send a second protection switching request message to the first end node
  • the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, where the overhead information group includes a request type field, a request signal identifier field, and a bridge identifier field. ;
  • the request type field indicates a fault type of the working path
  • the request signal identifier field is a service identifier of a service requesting a protection resource
  • the bridge identifier field indicates whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridging.
  • the overhead information group further includes a request flag field, where the request flag bit field is used to indicate whether the service corresponding to the service identifier of the request signal identifier field requests protection resources.
  • the overhead information group further includes a reserved field, where the request type field occupies 4 bits, the request signal identifier field occupies 8 bits, and the request flag bit field occupies 1 bit, and the bridge identifier The field occupies 1 bit, and the reserved field occupies 2 bits.
  • the request type field occupies 4 bits
  • the request signal identifier field occupies 10 bits
  • the request flag field occupies 1 bit
  • the bridge identifier field occupies 1 bit.
  • the overhead information group further includes a reserved field, where the request type field occupies 4 bits, the request signal identification field occupies 9 bits, the request flag field occupies 1 bit, and the bridge identifier field 1 bit, and the reserved field occupies 1 bit.
  • the overhead information group may further include a selection flag field, where the selection flag bit field is used to indicate whether the protection resource corresponding to the service identifier of the request signal identifier field has been selected.
  • the first protection switching request message and the second protection switching request message are APS messages.
  • an overhead frame of the protection switching request message may include two cost group information, express the overhead of the two time slots, fully utilize the overhead field, and improve the protection. The efficiency of switching.
  • FIG. 16 is a schematic structural diagram of a network node according to an embodiment of the present invention.
  • the second end node 160 includes a receiving module 161 and a transmitting module 162.
  • the second end node 160 can be a common end node on the working path and the protection path.
  • the receiving module 161 is configured to receive a first protection switching request message from the intermediate node when the working path between the first end node and the second end node fails, where the protection path of the working path includes the first An end node, the second end node, and at least one of the intermediate nodes;
  • the sending module 162 sends a second protection switching request message to the intermediate node
  • the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, where the overhead information group includes a request type field, a request signal identifier field, and a bridge identifier field. ;
  • the request type field indicates a fault type of the working path
  • the request signal identifier field is a service identifier of a service requesting a protection resource
  • the bridge identifier field indicates whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridging.
  • the overhead information group further includes a request flag field, where the request flag bit field is used to indicate whether the service corresponding to the service identifier of the request signal identifier field requests protection resources.
  • the overhead information group further includes a reserved field, where the request type field occupies 4 bits, the request signal identifier field occupies 8 bits, and the request flag bit field occupies 1 bit, and the bridge identifier The field occupies 1 bit, and the reserved field occupies 2 bits.
  • the request type field occupies 4 bits
  • the request signal identifier field occupies 10 bits
  • the request flag field occupies 1 bit
  • the bridge identifier field occupies 1 bit.
  • the overhead information group further includes a reserved field, where the request type field occupies 4 bits, the request signal identification field occupies 9 bits, the request flag field occupies 1 bit, and the bridge identifier field 1 bit, and the reserved field occupies 1 bit.
  • the overhead information group may further include a selection flag field, where the selection flag bit field is used to indicate whether the protection resource corresponding to the service identifier of the request signal identifier field has been selected.
  • the first protection switching request message and the second protection switching request message are APS messages.
  • an overhead frame of the protection switching request message may include two cost group information, and the overhead of the two time slots is expressed in the process of the protection switching, and the reservation in the overhead field is fully utilized. Fields increase the efficiency of protection switching.
  • FIG. 17 is a schematic structural diagram of four network systems according to an embodiment of the present invention.
  • the system may include the first end node in the embodiment of FIG. 14 and the intermediate node in the embodiment of FIG. 15; and may also include the intermediate node in the embodiment of FIG. 15 and the second in the embodiment of FIG. End node; may also include the first end node of the embodiment of FIG. 14, the intermediate node of the embodiment of FIG. 15, and the second end node of the embodiment of FIG. 16; may also include the first end node of the embodiment of FIG. 14 and the implementation of FIG. The second end node of the example.
  • the first end node, the intermediate node, and the second end node are included in the system as an example for description.
  • the intermediate node can contain multiple.
  • the first end node When the working path between the first end node and the second end node fails, the first end node sends a first protection switching request message to the intermediate node, where the protection path of the working path includes the first end a node, the second end node, and at least one of the intermediate nodes;
  • the intermediate node receives the first exchange switching request message of the first end node, and sends a first switching replacement request message to the second end node;
  • the second end node receives the first protection switching request message from the intermediate node, and sends a second protection switching request message to the intermediate node;
  • the intermediate node receives the second protection switching request message from the second end node, and sends a second protection switching request message to the first end node;
  • the first end node receives a second protection switching request message from the intermediate node, and switches service data to the protection path for transmission;
  • the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, where the overhead information group includes a request type field, a request signal identifier field, and a bridge identifier field. ;
  • the request type field indicates a fault type of the working path
  • the request signal identifier field is a service identifier of a service requesting a protection resource
  • the bridge identifier field indicates whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridging.
  • an overhead frame of the protection switching request message may include two cost group information, express the overhead of the two time slots, fully utilize the overhead field, and improve the protection. The efficiency of switching.
  • FIG. 18 is a schematic structural diagram of hardware of an OTN (Optical Transport Network) device according to an embodiment of the present invention.
  • the OTN device includes a main control board 181, an OTN circuit board 182, a cross board 183, and an OTN circuit board 184.
  • the direction of transmission of the service can be from the customer side to the line side, and also from the line side to the customer side.
  • the service sent or received by the client side is called the client side service
  • the service received or sent by the line side is called the wavelength division side service.
  • the service processing flow in the two directions is a reverse process.
  • the client side to the line side direction is taken as an example for description:
  • the main control board 181 is connected to the OTN tributary board 182, the cross board 183, and the OTN circuit board 184 via a bus, and functions to control and manage the OTN tributary board 182, the cross board 183, and the OTN circuit board 184.
  • the OTN tributary board 182 completes the package mapping of the customer service.
  • the customer service includes a variety of service types, such as ATM (Asynchronous Transfer Mode) service, SDH (Synchronous Digital Hierarchy) service, Ethernet service, CPRI (Common Public Radio Interface) service, Storage business, etc.
  • the tributary board 182 is configured to receive the client service from the client side, map the received client service package to an ODU (Optical Channel Data Unit) signal, and add a corresponding OTN management monitoring overhead.
  • the ODU signal may be a low-order ODU signal, such as ODU0, ODU1, ODU2, ODU3, ODUflex, etc.
  • the OTN management monitoring overhead may be an ODU overhead.
  • Different types of customer services are packaged into different ODU signals in different ways.
  • the cross board 183 completes the full cross connection of the tributary board and the circuit board to realize flexible cross scheduling of the ODU signal.
  • the cross board can realize the transmission of the ODU signal from any one of the tributary boards to any one of the circuit boards, or the OTU signal can be transmitted from any one of the circuit boards to any one of the circuit boards, and the customer signal can be transmitted from any one of the tributary boards. Transfer to any of the tributary boards.
  • the OTN circuit board 184 forms an OTU (Optical Channel Transport Unit) signal and transmits it to the line side.
  • the OTN board 184 can multiplex the low order multiplexed ODU signals into the higher order ODU signals before the ODU signals form the OTU signal.
  • the high-order ODU signal adds the corresponding OTN management monitoring overhead to form an OTU signal and transmits it to the optical transmission channel on the line side.
  • the high-order ODU signal can be ODU1, ODU2, ODU3, ODU4, etc.
  • the OTN management monitoring overhead can be OTU overhead.
  • the main control board 181 can execute a pre-configured program code to control any one or more of the OTN tributary board 182, the cross board 183, and the OTN circuit board 184 to perform the following functions:
  • the first protection switching request message is sent to the intermediate node, where the working path is protected.
  • the path includes the first end node, the second end node, and at least one of the intermediate nodes; an OTN circuit board 184 or an OTN tributary board 182 receives a second protection switching request message from the intermediate node,
  • the cross board 183 switches the traffic data to the protection path for transmission.
  • the one of the first protection switching request message and the second protection request message includes at least two overhead information groups, where the overhead information group includes a request type field, a request signal identifier field, and a bridge identifier field. ;
  • the request type field indicates a fault type of the working path
  • the request signal identifier field is a service identifier of a service requesting a protection resource
  • the bridge identifier field indicates whether the protection resource corresponding to the service identifier of the request signal identifier field has been bridging.
  • the overhead information group further includes a request flag field, where the request flag bit field is used to indicate whether the service corresponding to the service identifier of the request signal identifier field requests protection resources.
  • the overhead information group further includes a reserved field, where the request type field occupies 4 bits, the request flag bit field occupies 1 bit, and the bridge identifier field occupies 1 bit.
  • the request signal identification field may occupy 8 bits, 9 bits, or 10 bits, and the corresponding reserved fields occupy 2 bits, 1 bit, and 0 bits, respectively.
  • an overhead frame of an APS message may include two cost group information, expresses the overhead of two time slots, and fully utilizes the overhead field, thereby improving the efficiency of protection switching.
  • the method steps shown in FIGS. 6a, 6b, 10a, 10b, 12a, and 12b can be implemented by the OTN device 180 shown in FIG.
  • the OTN device 180 shown in FIG. 18 only shows the main control board 181, the OTN circuit board 182, the cross board 183, and the OTN circuit board 184, it will be understood by those skilled in the art in the specific implementation process.
  • the OTN device 180 also contains other devices necessary to achieve proper operation.
  • the OTN device 180 may also include hardware devices that implement other additional functions, depending on the particular needs.
  • the OTN device 180 may also only include the components necessary to implement the embodiments of the present invention, and does not necessarily include all of the devices shown in FIG.
  • aspects of the present invention, or possible implementations of various aspects may be embodied as a system, method, or computer program product.
  • aspects of the invention, or possible implementations of various aspects may be in the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, etc.), or a combination of software and hardware aspects, They are collectively referred to herein as "circuits," “modules,” or “systems.”
  • aspects of the invention, or possible implementations of various aspects may take the form of a computer program product, which is a computer readable program code stored in a computer readable medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Computing Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例公开了一种保护倒换的方法，包括：当第一端节点和第二端节点之间的工作路径发生故障时，所述第一端节点向中间节点发送第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；所述第一端节点接收来自所述中间节点的第二保护倒换请求消息，将业务数据切换到所述保护路径上传输；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段。所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧能够指示两个时隙的开销，提高了开销资源的利用率。

Description

一种保护倒换的方法和节点 技术领域
本发明涉及通信技术领域，具体涉及一种以太网环保护倒换方法及节点。
背景技术
传统的光传输网络以环形或线性拓扑为主，可提供复用段保护、通道环保护、线性1:1复用段保护、线性1+1复用段保护以及端到端的子网连接保护(Subnetwork Connection Protection，SNCP)等一系列保护技术。在支持单链路故障的的前提下，传统的光网络保护技术需要预留的保护资源占用了大量的网络带宽资源，带宽利用率低。
随着电信技术的发展，出现了基于自动交换光网络(Automatically Switched Optical Network，ASON)的共享网格保护(Shared Mesh Protection，SMP)技术，它于传统的光网络保护技术最显著的区别在于：SMP技术能够提供动态实时的路径恢复，不需要预留保护路径的带宽资源，可在故障发生后根据失效链路或节点实时计算，确定保护路径。在SMP技术中，为了降低保护倒换的时间，可以通过自动保护倒换(Automatic Protection Switched，APS)开销来传递保护倒换的消息，从而实现整个业务的保护倒换。
国际电联电信标准化部门(Telecommunication Standardization Sector of the International Telecommunications Union，ITU-T)G.ODUSMP标准中规定了实现SMP保护倒换的APS开销编码格式。如图1所示，图1是现有技术中APS开销编码格式。APS消息的开销部分可以用于描述SMP保护倒换的状态，共有4个字节，32个比特位，有三类信息被描述：
(1)Request：包含在第1比特～第4比特中，表示保护倒换请求的类型，例如SF(Singnal Failure，信号故障)、SD(Signal Degrade，信号劣化)、RR(Reverse Request，反向请求)、NR(No Request，无请求)、MS(Manual Switch，手动倒换)和FS(Forced Switch，强制倒换)等。
(2)Requested Signal：包含在第9比特～第16比特中，表示请求共享保护资源的业务的业务ID(Identifier)，例如W1等。无请求时设置全0。
(3)Bridged Signal：包含在第17比特～第24比特中，表示已经完成桥接的业务的业务ID，例如W1等。无任何业务已经完成桥接时设置全0。
上述编码格式的定义可详细参见ITU-T G.ODUSMP标准。从图1中的编码格式可以看出，其中，有效字段只有20比特，预留字段有12比特，没有充分利用开销字段，造成开销资源的浪费。
发明内容
有鉴于此，本发明实施例提供一种保护倒换的方法和节点，可以解决开销资源浪费问题。
第一方面，本发明实施例提供了一种保护倒换的方法，包括：当第一端节点和第二端节点之间的工作路径发生故障时，所述第一端节点向中间节点发送第一 保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；所述第一端节点接收来自所述中间节点的第二保护倒换请求消息，将业务数据切换到所述保护路径上传输；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
本发明实施例中，在一个开销帧中可以包含两个开销信息组，来表达两个时隙的开销信息，充分利用了开销字段，从而提高了保护倒换的效率。
结合第一方面，在第一方面第一种可能的实现方式中，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
本发明实施例中，在一个开销帧中可以包含了两个开销组，并在开销信息组设置请求标志位字段，用于表示该开销信息组的业务标识对应的业务是否请求保护资源，充分利用了开销资源。
结合第一方面、或第一方面第一种可能的实现方式，在第一方面第二种可能的实现方式中，所述请求类型字段占4比特，所述请求信号标识字段占8比特或9比特或10比特，所述请求标志字段占1比特，所述桥接标识字段占1比特。
在APS开销中，请求信号标识字段可以占用8～10个比特位，充分利用了APS开销字段。
结合第一方面、或第一方面第一种至第二种任一可能的实现方式，在第一方面第三种可能的实现方式中，第一端节点在发送第一保护倒换请求消息之前，完成第一端节点和所述中间节点之间的桥接。
结合第一方面、或第一方面第一种至第三种任一可能的实现方式，在第一方面第四种可能的实现方式中，第一端节点在接收到所述第二保护倒换请求消息后，完成第一端节点和所述中间节点之间的选择。
结合第一方面、或第一方面第一种至第四种任一可能的实现方式，在第一方面第五种可能的实现方式中，所述第一端节点检测到第一工作路径的业务故障恢复时，所述方法还包括：所述第一端节点向所述中间节点发送第三保护倒换请求消息；所述第一节点接收到所述第三节点的第四保护倒换请求消息，将业务数据切换至工作路径上传输；所述第三保护倒换请求消息和第四保护倒换请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组中的请求类型字段指示所述请求信号标识字段的业务标识对应业务的工作路径故障恢复。
本发明实施例中，在一个开销帧中可以包含两个开销信息组，来表达两个时隙的开销信息，充分利用了开销字段，从而提高了保护倒换的效率。
第二方面，本发明实施例提供了一种保护倒换的方法，包括：当第一端节点和第二端节点之间的工作路径发生故障时，中间节点接收到第一端节点的第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二 端节点以及至少一个所述中间节点；所述中间节点向所述中间节点的下游相邻节点发送第一保护倒换请求消息；所述中间节点接收来自所述中间节点的下游相邻节点的第二保护倒换请求消息；所述中间节点向第一端节点发送第二保护倒换请求消息；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
本发明实施例中，在一个开销帧中可以包含两个开销信息组，来表达两个时隙的开销信息，充分利用了开销字段，从而提高了保护倒换的效率。
结合第二方面的实现方式，在第二方面第一种可能的实现方式中，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
本发明实施例中，在一个开销帧中可以包含了两个开销组，并在开销信息组设置请求标志位字段，用于表示该开销信息组的业务标识对应的业务是否请求保护资源，充分利用了开销资源。
结合第二方面、或第二方面第一种可能的实现方式，在第二方面第二种可能的实现方式中，所述请求类型字段占4比特，所述请求信号标识字段占8比特或9比特或10比特，所述请求标志字段占1比特，所述桥接标识字段占1比特。
在APS开销中，请求信号标识字段可以占用8～10个比特位，充分利用了APS开销字段。
结合第二方面、或第二方面第一种至第二种任一可能的实现方式，在第二方面第三种可能的实现方式中，中间节点接收到第一端节点的第一保护倒换请求消息后，完成中间节点和中间节点之间的下游相邻节点之间的桥接。
结合第二方面、或第二方面第一种至第三种任一可能的实现方式，在第二方面第四种可能的实现方式中，所述中间节点接收到中间节点的上游相邻节点的第二保护倒换请求消息后，完成中间节点的上游相邻节点和中间节点之间的选择。
第三方面，本发明实施例提供了一种保护倒换的方法，包括：当第一端节点和第二端节点之间的工作路径发生故障时，第二端节点接收来自中间节点的第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；第二端节点向所述中间节点发送第二保护倒换请求消息；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
本发明实施例中，在一个开销帧中可以包含两个开销信息组，来表达两个时隙的开销信息，充分利用了开销字段，从而提高了保护倒换的效率。
结合第三方面的实现方式，在第三方面第一种可能的实现方式中，所述开销 信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
本发明实施例中，在一个开销帧中可以包含了两个开销组，并在开销信息组设置请求标志位字段，用于表示该开销信息组的业务标识对应的业务是否请求保护资源，充分利用了开销资源。
结合第三方面、或第三方面第一种可能的实现方式，在第三方面第二种可能的实现方式中，所述请求类型字段占4比特，所述请求信号标识字段占8比特或9比特或10比特，所述请求标志字段占1比特，所述桥接标识字段占1比特。
在APS开销中，请求信号标识字段可以占用8～10个比特位，充分利用了APS开销字段。
结合第三方面、或第三方面第一种至第二种任一可能的实现方式，在第三方面第三种可能的实现方式中，所述第二端节点接收到中间节点的第一保护倒换请求消息后，完成所述中间节点和所述第二端节点之间的选择。
结合第三方面、或第三方面第一种至第二种任一可能的实现方式，在第三方面第三种可能的实现方式中，所述第二端节点向所述中间节点发送所述第二保护倒换请求消息之前，完成所述第二端节点和所述中间节点之间的桥接。
第四方面，本发明实施例提供了一种第一端节点，包括：发送模块，用于当第一端节点和第二端节点之间的工作路径发生故障时，向中间节点发送第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；接收模块，用于接收来自所述中间节点的第二保护倒换请求消息，将业务数据切换到所述保护路径上传输；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
本发明实施例中，在一个开销帧中可以包含两个开销信息组，来表达两个时隙的开销信息，充分利用了开销字段，从而提高了保护倒换的效率。
结合第四方面的实现方式，在第四方面第一种可能的实现方式中，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
本发明实施例中，在一个开销帧中可以包含了两个开销组，并在开销信息组设置请求标志位字段，用于表示该开销信息组的业务标识对应的业务是否请求保护资源，充分利用了开销资源。
第五方面，本发明实施例提供了一种中间节点，包括：接收模块，用于当第一端节点和第二端节点之间的工作路径发生故障时，接收到第一端节点的第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；发送模块，用于向所述中间节点的下游相邻节点发送第一保护倒换请求消息；接收模块，用于接收来自所述中间节点的下游 相邻节点的第二保护倒换请求消息；发送模块，用于向第一端节点发送第二保护倒换请求消息；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
本发明实施例中，在一个开销帧中可以包含两个开销信息组，来表达两个时隙的开销信息，充分利用了开销字段，从而提高了保护倒换的效率。
结合第五方面的实现方式，在第五方面第一种可能的实现方式中，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
本发明实施例中，在一个开销帧中可以包含了两个开销组，并在开销信息组设置请求标志位字段，用于表示该开销信息组的业务标识对应的业务是否请求保护资源，充分利用了开销资源。
第六方面，本发明实施例提供了一种第二端节点节点，包括：接收模块，用于当第一端节点和第二端节点之间的工作路径发生故障时，接收来自中间节点的第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；第二端节点向所述中间节点发送第二保护倒换请求消息；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
本发明实施例中，在一个开销帧中可以包含两个开销信息组，来表达两个时隙的开销信息，充分利用了开销字段，从而提高了保护倒换的效率。
结合第六方面的实现方式，在第六方面第一种可能的实现方式中，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
本发明实施例中，在一个开销帧中可以包含了两个开销组，并在开销信息组设置请求标志位字段，用于表示该开销信息组的业务标识对应的业务是否请求保护资源，充分利用了开销资源。
第七方面，本发明实施例提供了一种OTN设备，包括：主控板、支路板、交叉板和线路板；主控板运行预先配置的程序，控制支路板、交叉板和线路板中的任意一种或多种单板，执行如第一方面及第一方面的任意一种可能的实现方式所述的方法、如第二方面及第二方面的任意一种可能的实现方式所述的方法、如第三方面及第三方面的任意一种可能的实现方式所述的方法。
第十方面，本发明实施例提供了一种网络系统，包括：如第四方面及第四方面任意一种可能的实现方式所述的节点，以及如第五方面以及第五方面任意一种 可能的实现方式所述的节点。
第十一方面，本发明实施例提供了一种网络系统，包括：如第五方面及第五方面任意一种可能的实现方式所述的节点，以及如第六方面以及第六方面任意一种可能的实现方式所述的节点。
根据本发明提供的技术方案，在第一端节点、中间节点、第二端节点等节点设备保护倒换的过程中，在保护倒换请求消息的一个开销帧中包含至少两个开销信息组，其中一个开销信息组中包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标志位字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。采用本发明实施例提供的APS开销编码格式，由于一个开销帧可以表达两个时隙的开销，充分利用了开销字段，提高了业务保护倒换的效率。
附图说明
下面将对描述背景技术和实施例时所使用的附图作简单的介绍。
图1是现有技术中APS开销编码格式示意图；
图2是本发明实施例提供的一种APS的网络拓扑结构示意图；
图3是采用现有技术的APS开销编码格式的保护倒换信令流程图；
图4是本发明实施例提供的一种节点A和节点E的连接结构示意图；
图5a是本发明实施例提供的一种APS消息格式示意图；
图5b是本发明实施例提供的一种APS开销编码格式示意图；
图5c是本发明实施例提供的一种APS开销编码格式示意图；
图5d是本发明实施例提供的一种APS开销编码格式示意图；
图6a是采用本发明实施例提供的一种APS开销编码格式的保护倒换的信令流程图；
图6b是采用本发明实施例提供的一种APS开销编码格式的保护倒换的信令流程图；
图7a是本发明实施例提供的一种APS开销编码格式示意图；
图7b是本发明实施例提供的一种APS开销编码格式示意图；
图8是本发明实施例提供的另一种APS开销编码格式示意图；
图9是本发明实施例提供的另一种APS开销编码格式示意图；
图10a是采用本发明实施例提供的一种APS开销编码格式的故障恢复的信令流程图；
图10b是采用本发明实施例提供的一种APS开销编码格式的故障恢复的信令流程图；
图11是本发明实施例提供的一种NR(W1，0，1)的消息开销编码格式示意图；
图12a是采用本发明实施例提供的一种APS开销编码格式的保护倒换的信令流程图；
图12b是采用本发明实施例提供的一种APS开销编码格式的保护倒换的信令流程图；
图13是本发明实施例提供的一种SF(W2，1，0)的消息开销编码格式示意图；
图14是本发明实施例提供的一种网络节点的结构示意图；
图15是本发明实施例提供的一种网络节点的结构示意图；
图16是本发明实施例提供的一种网络节点的结构示意图
图17是本发明实施例提供的一种网络系统的结构示意图；
图18是本发明实施例提供的一种OTN设备的结构示意图。
具体实施方式
下面结合附图，对本发明的实施例进行描述。
SMP(Shared Mesh Protection，共享网格保护)允许保护资源被多条工作路径共享，其中这多条工作路径并不需要有相同的源节点和宿节点。图2是本发明实施例提供的一种SMP的网络拓扑结构示意图。S1、S2为两条工作路径，其路径分别为A-B、C-D。P1为S1的保护路径，其路径为A-E-F-G-B，P2为S2的保护路径，其路径为C-E-F-G-D，S1和S2的共享保护资源的路径为E-F-G。其中，保护资源包括节点、链路、带宽等资源。S1、P1对应的业务的业务ID为W1，S2、P2对应的业务的业务ID为W2。当工作路径发生故障时，会触发保护倒换流程，使得工作路径上的业务倒换至保护路径上。例如，工作路径S1发生故障时，S1上的业务可以倒换至保护路径P1上。
为了实现业务的保护倒换，需要为承载业务的保护路径配置APS(Automatic Protection Switched，自动保护倒换)开销。APS开销可以表示多种保护倒换类型的开销，例如，SMP、1+1保护、1:1保护、线性保护等。携带APS开销的APS消息用于表示保护倒换信令消息，例如SMP保护倒换信令消息等，每8帧的APS开销中有1帧表达SMP保护倒换信令消息。在APS开销中，使用哪一种链路粒度的开销取决于承载故障的工作路径上业务的保护路径的链路粒度。不同链路粒度的APS开销对应的传输带宽及时隙资源数量不同，但APS开销的编码格式相同。在OTN(Optical Transport Network，光传送网络)中，最小的链路粒度为ODU(Optical channel Data Unit)0，其带宽为1.25G，占用一个时隙资源。其他的链路粒度可以包括：ODU1、ODU2、ODU3、ODU4，其带宽分别为2.5G、10G、40G和100G，分别占用2、8、32、80个时隙资源。例如，当使用ODU2链路保护ODU0链路的业务时，保护倒换时使用8个时隙中的其中一个，应该使用ODU2的开销。
现有技术中采用如图1所示的APS开销编码格式进行保护倒换的信令传递。图3是采用现有技术的APS开销编码格式的保护倒换信令流程图。如图3所示，在图2所示的网络拓扑结构中，当检测到S1发生故障时，需要激活S1的保护路径P1：A-E-F-G-B。激活S1的保护路径的过程中，节点的处理过程涉及到桥接和选择。具体地，桥接表示激活某个节点用于发送数据，选择表示激活某个节点用于接收数据。如图4所示，对中间节点E来说，桥接和选择均有两个方向，桥接1和桥接 2分别表示从两个方向上发送数据，选择1和选择2分别表示从两个方向上接收数据。桥接1和选择1表示一个方向上的数据传输，桥接2和选择2表示另一个方向上的数据传输。对端节点A来说，桥接和选择均只有一个方向，并且桥接和选择是相反方向的。例如，在节点E上建立E-A之间的桥接，即在节点E上建立桥接2，用于对节点A发送数据；在节点E上建立A-E之间的选择，即在节点E上建立选择1，用于接收来自节点A的数据。对于单向业务来说，端节点A只有一个方向上的桥接或者选择(桥接3或者选择4)，中间节点E具有一个方向上的桥接和选择(桥接1+选择1，或者桥接2+选择2)；对于双向业务来说，端节点A具有桥接3和选择4，中间节点E具有两个方向上的桥接和选择。端节点包括源节点和宿节点，中间节点指的具有至少一个相邻节点的节点。
信令传输的方向可以从源节点到宿节点，还可以从宿节点到源节点。上游方向和下游方向是相对的，可以以任意一个方向为上游方向，以另一个方向为下游方向。本发明实施例中，以节点A为S1、P1的源节点，节点B为S1、P1的宿节点为例进行说明。在S1或P1中，从节点A到节点B的方向为下游方向，从节点B到节点A方向为上游方向。
具体地，P1的源节点A确认A-E之间的资源可用后，完成与下游节点E的桥接，并向下游节点E发送信号失效消息SF(W1，W1)。资源可用包括A-E之间的资源空闲，或者A-E之间的资源被低优先级的业务占用。信号失效消息可以通过APS开销表示，APS开销编码格式为SF(W1，W1)。其中SF(W1，W1)表示信号失效，请求激活保护路径，并且发送该消息的节点已完成桥接。
节点E收到信号失效消息SF(W1，W1)后，确认E-F之间的资源可用，节点E完成桥接，并向下游节点F发送相同的信号失效消息SF(W1，W1)。节点F、G的处理流程和节点E类似，此处不再赘述。
直到P1的宿节点B收到信号失效消息SF(W1，W1)后，确认G-B之间的保护资源可用，完成选择和桥接。然后节点B向上游节点G发送反向请求消息RR(W1，W1)，通知节点G完成选择。反向请求消息可以通过APS开销表示，编码格式为RR(W1，W1)，表示反向请求，请求激活保护路径，并且发送该反向请求消息的节点已完成桥接。
节点G收到反向请求消息后RR(W1，W1)，确认G-F之间的资源可用后，完成选择，并向上游节点F发送同样的反向请求消息RR(W1，W1)。节点F、E的处理流程和节点G类似，不再赘述。
直到源节点A收到反向请求消息RR(W1，W1)后，完成选择，W1的保护倒换完成，即W1从工作路径S1倒换至保护路径P1中。
使用现有技术的APS开销编码格式，存在预留字段没有被充分利用，导致开销资源浪费的问题，因此，本发明实施例提出一种APS开销编码格式，可充分利用开销资源。如图5a所示，APS消息包括APS开销和净荷。APS开销为OTN开销的一部分，用于携带保护倒换的状态信息，例如保护倒换请求类型，业务ID等，净荷部分用于携带业务信息。本发明实施例主要对APS开销部分进行定义。图5b是本发明实施例提供的一种APS开销编码格式示意图。如图5b所示，该编码格式 中，有4类信息被描述：
(1)Request Type：包含在第1比特～第4比特中，表示保护倒换请求的类型，例如SF、SD、RR、NR、MS和FS等。例如，SF用于工作路径发生故障，业务从工作路径倒换至保护路径的场景；SD用于工作路径信号劣化，业务从工作路径倒换至保护路径的场景；RR用于对SF、SD等的响应消息；NR用于工作路径恢复故障，业务从保护路径倒换至工作路径的场景；MS和FS分别用于手动倒换和强制倒换的场景。
(2)Request Signal ID：包含在第5比特～第12比特中，表示工作路径发生故障，请求保护路径资源的业务ID，例如W1等。该业务ID的业务处于正常状态，对保护路径资源无请求时Request Signal ID可以设置全0。工作路径和保护路径可以对应于同一个业务ID，例如S1、P1对应的业务的业务ID为W1，S2、P2对应的业务的业务ID为W2。
(3)Requested Flag(RF)：包含在第13比特中，表示业务ID为Request Signal ID的业务是否已经被请求。当工作路径发生故障时，则业务ID为Request Signal ID的业务对应的保护路径资源被请求，RF可以设为1；工作路径无故障时，则业务ID为Request Signal ID的业务对应保护路径资源不被请求，RF可以设为0。若Request Signal ID设置为全0时，RF标志位无表示意义。
(4)Bridge Flag(BF)：包含在第14比特中，表示业务ID为Request Signal ID的业务是否在保护路径对应的节点上建立桥接。若业务ID为Request Signal ID的业务在保护路径对应的节点上已建立桥接，则BF设置为1；若业务ID为Request Signal ID的业务在保护路径对应的节点上未建立桥接，则BF设置为0。若Request Signal ID设置为全0时，BF标志位无表示意义。
可选地，上述四类信息在APS开销编码的比特位置不限于上述的实施方式。例如，RF和BF的位置可以互换。
可选地，由于Request Flag还可以通过Request Type进行唯一标识，因此Request Flag可以不包含在上述编码格式中。如图5c所示，RF标志位被省略，BF可以向前移动一个比特位，预留字段增加了一个比特位。例如，通过SF、SD、RR、MS、FS等保护倒换请求的类型，指示Request Flag为1；通过NR保护倒换请求的类型，指示Request Flag为0。
可选地，如图5d所示，上述编码格式中还可以包含选择标志位Selector Flag(SeF)。具体地，选择标志位可以在预留字段中的一个比特位表示，表示业务ID为Request Signal ID的业务是否已经选择。若业务ID为Request Signal ID的业务在保护路径对应的节点上已建立选择，则SeF设置为1；若业务ID为Request Signal ID的业务在保护路径对应的节点上未建立选择，则SeF设置为0。若Request Signal ID设置为全0时，选择标志位无意义。
可选地，请求保护路径资源的业务的业务ID不限于8个比特位长度，可以增加至9个比特或10个比特。如果需要增加比特位，将RF、BF往后面的比特位顺延，占用Resv预留字段的比特位即可。例如，如果需要9个比特来表示Request Signal ID，则第1比特～第4比特为Request Type，第5比特～第13比特为Request Signal ID， 第14比特为RF，第15比特为BF，第16比特为Resv。如果需要10个比特来表示Request Signal ID，则第1比特～第4比特为Request Type，第5比特～第14比特为Request Signal ID，第15比特为RF，第16比特为BF。如果上述编码格式中还包含Selector Flag，则预留字段只有1个比特位可使用，此时业务ID可以增加至9个比特。
本发明实施例提出的编码格式中第17比特～第32比特与第1比特～第16比特的含义相同，只是对应了不同的时隙。例如在ODU1链路中，包含两个时隙。将上述的4字节的编码格式看作是一个帧，在一个帧中，第1比特～第16比特表示时隙1，第17比特～第32比特表示时隙2。对于两个时隙以上的链路粒度，例如ODU2、ODU3、ODU4等，分别需要4帧、16帧、40帧来表示APS消息。本发明实施例中，由于一个帧中表达了两个时隙的开销信息，相对于现有技术来说，帧的数量减少了一半，也即开销资源节约了50％，充分利用了APS开销字段。
图6a和图6b是采用本发明实施例提供的一种APS开销编码格式的保护倒换的信令流程图。如图6a和图6b所示，在图2所示的网络拓扑结构中，当检测到S1发生故障时，需要激活S1的保护路径P1：A-E-F-G-B。信令流程中涉及的APS消息有两条：SF(W1，1，1)和RR(W1，1，1)。其中，SF(W1，1，1)表示信号失效，W1对应的保护资源状态更新为：已被W1请求，且已桥接。RR(W1，1，1)表示反向请求，W1对应的保护资源的状态更新为：已被W1请求，且已桥接。
下面将结合几个例子对本发明实施例提出的一种APS开销编码格式进行说明。
图7a和图7b是本发明实施例提供的一种APS开销编码格式示意图。具体地，以信号失效消息SF(W1，1，1)为例进行说明。例如，采用ODU2链路保护ODU0链路的业务，ODU0链路发生故障时，需要占用ODU2链路中一个时隙的保护资源。图7a的开销编码格式表示ODU2链路的第一时隙被W1请求，并且已桥接；图7b的开销编码格式表示ODU2链路的第二时隙被W1请求，并且已桥接。其中，第一时隙和第二时隙可以是ODU2链路中的任意时隙，可以是工作路径发生故障之前在节点上配置。
图8是本发明实施例提供的另一种APS开销编码格式示意图。具体地，以信号失效消息SF(W1，1，1；W1，1，1)为例进行说明。例如，采用ODU2链路保护ODU1链路的业务，ODU1链路发生故障时，需要占用ODU2链路中的两个时隙的保护资源。图8的开销编码格式表示ODU2链路的第一时隙和第二时隙被W1请求，并且已桥接。其中，第一时隙和第二时隙可以是ODU2链路中的任意时隙，可以在工作路径发生故障之前在节点上配置。
图9是本发明实施例提供的另一种APS开销编码格式示意图。具体地，以信号失效消息SF(W1，1，1；W2，1，1)为例进行说明。例如，采用ODU2链路保护两条ODU0链路的业务，两条ODU0链路均发生故障时，需要占用ODU2链路中的两个时隙的保护资源，每条ODU0链路各占用一个时隙。图9的开销编码格式表示ODU2的第一时隙被W1请求，并且已桥接，ODU2链路的第二时隙被W2 请求，并且已桥接。
下面对图6a和图6b所示的信令流程中每个节点的执行步骤作出具体的说明。图6a和图6b的区别在于：图6a是由节点A发起保护倒换信令流程，图6b是由节点A和节点B同时发起保护倒换信令流程，下面以图6a为例进行说明：
节点A：节点A检测到工作路径发生故障时，向下游节点E发送信号失效消息。并且，节点A接收到来自下游节点E的反向请求消息。
具体地，节点A检测到工作路径S1发生故障可以是节点A自身检测到链路故障，或者节点B检测到链路故障后通知给节点A。节点A检测到工作路径发生故障时，可以在确认节点A和下游节点E之间的资源可用后，建立A-E之间的桥接。例如图4所示的桥接3。这里的资源可用指的资源是空闲的，即没有其他业务占用。当然，资源可用还可以包括资源被低优先级的业务占用。节点A可以在建立A-E之间的桥接之后，向下游节点E发送信号失效消息SF(W1，1，1)。
具体地，节点A何时收到节点E的反向请求消息RR(W1，1，1)，取决于节点E何时向节点A发送该消息，可参见节点E的执行步骤。节点A收到节点E发送的RR(W1，1，1)消息后，确定节点A和节点E之间的资源可用，建立E-A之间的选择，例如图4所示的选择4。
节点A向下游节点E发送的信号失效消息可以通过APS开销表示，编码格式为SF(W1，1，1)，表示信号失效，保护路径P1已被W1请求，并且已建立桥接。节点A接收来自下游节点E的反向请求消息可以通过APS开销表示，编码格式为RR(W1，1，1)，表示反向请求，确认激活W1的保护路径P1，并且发送该消息的节点已建立桥接。具体地，信号失效消息SF(W1，1，1)和反向请求消息RR(W1，1，1)的开销编码格式可以参考图5b～5d、图7a、图7b、图8和图9所示的实施例，对于开销编码中的请求保护路径资源的业务数量、占用保护资源的时隙数量等，本发明不作限定。
节点E：节点E接收到来自节点A的信号失效消息后，向下游节点F发送信号失效消息，向上游节点A发送反向请求消息，并且，节点E接收来自下游节点F的反向请求消息。
具体地，节点E接收到信号失效消息SF(W1，1，1)后，可以在确定节点E和下游节点F之间的资源可用后，建立E-F之间的桥接，例如，如图4所示节点E的桥接1；并且，可以在确定节点E和上游节点A之间的资源可用后，建立A-E之间的选择，例如，如图4所示节点E的选择1。可选地，节点E可以在收到来自节点F的RR(W1，1，1)消息后，再建立A-E之间的选择。
节点E可以先向下游节点F发送信号失效消息SF(W1，1，1)，再向上游节点A发送反向请求消息RR(W1，1，1)；或者，节点E也可以先向上游节点A发送RR(W1，1，1)消息，再向下游节点F发送SF(W1，1，1)消息。
具体地，节点E可以在接收到来自节点A的SF(W1，1，1)消息后，立即向节点A发送RR(W1，1，1)消息。可选地，节点E还可以在接收到节点F发送的RR(W1，1，1)消息后，再向节点A发送RR(W1，1，1)消息。
节点E何时接收到节点F的反向请求消息RR(W1，1，1)，取决于节点F何时 向节点E发送该消息，可参考节点A接收节点E的RR(W1，1，1)消息的过程。节点E接收到节点F的RR(W1，1，1)消息后，在确定节点E和上游节点A之间的资源可用后，建立E-A之间的桥接，例如，如图4所示节点E的桥接2；并且，可以在确定节点E和下游节点F之间的资源可用后，建立F-E之间的选择，例如，如图4所示的选择2。
节点F：节点F接收来自上游节点E的信号失效消息后，向下游节点G发送信号失效消息，向上游节点E发送反向请求消息，并且，节点F接收来自下游节点G的反向请求消息。
节点F的处理流程和节点E类似，不再赘述。
节点G：节点G接收来自上游节点F的信号失效消息后，向下游节点B发送信号失效消息，向上游节点F发送反向请求消息，并且，节点G接收来自下游节点B的反向请求消息。
节点G的处理流程和节点E类似，不再赘述。
节点B：节点B接收来自上游节点G的信号失效消息后，向上游节点G发送反向请求消息。
具体地，节点B收到来自上游节点G的信号失效消息SF(W1，1，1)后，确认节点B和节点G之间资源可用，建立G-B之间的选择以及B-G之间的桥接，并向上游节点G发送反向请求消息。具体地，节点B建立G-B之间的选择以及B-G之间的桥接，可以是先建立选择，再建立桥接；或者先建立桥接，再建立选择；还可以同时建立选择和桥接。
本发明实施例中，还可以由节点B向节点A的方向发送信号失效消息，节点A向节点B的方向发送反向请求消息，信令流程类似。或者，如图6b所示，节点A和节点B同时向对端节点发送信号失效消息。具体地，节点A向节点B的方向发送SF(W1，1，1)消息，同时，节点B向节点A的方向发送SF(W1，1，1)消息。各个节点收到SF(W1，1，1)消息的处理步骤类似。由于SF(W1，1，1)消息是双向发送的，因此各节点在收到SF(W1，1，1)消息后可以不用向发送RR(W1，1，1)消息。可选地，节点A和节点B还可以在不同的时刻分别发起保换倒换信令流程，本发明对于信令流程的顺序不作限定。
本发明实施例提出的一种APS开销编码格式中，由于一个帧的APS消息可以表达两个时隙的开销，提高了开销资源的利用率，从而在工作路径故障时，提高了保护倒换的效率。
图10a和图10b是采用本发明实施例提供的一种APS开销编码格式的故障恢复的信令流程图。在图6a和图6b所示的信令流程之后，即业务W1从工作路径S1倒换至保护路径P1之后，工作路径S1故障恢复，业务从保护路径P1回退至工作路径S1中。如图10a和图10b所示，信令流程中涉及到的APS消息有两条：NR(W1，0，1)和NR(0，0，0)。其中，NR(W1，0，1)表示无请求，W1对应的保护资源状态更新为：无请求，已桥接。NR(0，0，0)表示无请求，保护资源状态更新为：无业务桥接。
下面对图10a和图10b所示的信令流程中每个节点的执行步骤作出具体的说 明。图10a和图10b的区别在于：图10a是由节点A发起保护恢复信令流程，图10b是由节点A和节点B同时发起保护恢复信令流程，下面以图10a为例进行说明：
节点A：节点A检测到工作路径的故障恢复时，向下游节点E发送第一无请求消息，并接收来自下游节点E的第二无请求消息。
一般来说，故障恢复可以是源、宿节点先后检测到的，也可以是源节点和宿节点两个节点中任意一个检测到，或者源、宿节点同时检测到。检测到工作路径S1的故障恢复后，节点A在向节点E发送第一无请求消息NR(W1，0，1)时，可以释放E-A之间选择。可选地，节点A可以在发送NR(W1，0，1)消息之前或者发送NR(W1，0，1)消息之后，释放E-A之间的选择。
具体地，节点A何时接收到节点E发送的第二请求消息NR(0，0，0)，取决于节点E何时向节点A发送该消息，可参见节点E的执行步骤。节点A收到节点E的NR(0，0，0)消息后，释放A-E之间的桥接。
节点A向下游节点E发送的第一无请求消息可以通过APS开销表示，编码格式为NR(W1，0，1)，表示W1对应的保护资源无请求，但已建立桥接。节点A接收下游节点E的第二无请求消息可以通过APS开销表示，编码格式为NR(0，0，0)，表示保护资源无请求，未建立桥接。图11为本发明实施例提供的一种NR(W1，0，1)的消息开销编码格式示意图。例如采用ODU2链路保护ODU1链路的业务时，ODU1链路发生故障时，需要占用ODU2链路中两个时隙的保护资源。图11的开销编码格式表示ODU2链路的第一时隙和第二时隙无请求，但已建立桥接。NR(0，0，0)的开销编码格式可参见图11，将NR(W1，0，1)中的Request Signal ID和Bridge Flag均设置为0。第一无请求消息NR(W1，0，1)和第二无请求消息NR(0，0，0)的开销编码格式还可以参考图5b～5d、图7a、图7b、图8和图9所示的实施例，对于开销编码中的请求保护路径资源的业务数量、占用保护资源的时隙数量等，本发明不作限定。
节点E：节点E接收到上游节点A的第一无请求消息，向下游节点F发送第一无请求消息，向上游节点A发送第二无请求消息，并且，节点E接收来自下游节点F的第二无请求消息。
具体地，节点E接收到上游节点A的第一无请求消息NR(W1，0，1)后。并且，节点E在发送第一无请求消息后，释放F-E之间的选择，例如，如图4所示节点E的选择2；并且，释放E-A之间的桥接，例如，如图4所示节点E的桥接2。
节点E可以先向下游节点F发送第一无请求消息NR(W1，0，1)，再向上游节点A发送第二无请求消息NR(0，0，0)；或者，节点E也可以先向上游节点A发送NR(0，0，0)消息，再向下游节点F发送NR(W1，0，1)。
具体地，节点E可以在接收到来自节点A的NR(W1，0，1)消息之后，立即向节点A发送NR(0，0，0)消息。可选地，节点E还可以在接收到节点F的NR(0，0，0)消息后，再向节点A发送NR(0，0，0)消息。
节点E何时接收到节点F的第二无请求消息NR(0，0，0)，取决于节点F何时向节点E发送该消息，可参考节点A接收节点E的NR(0，0，0)消息的过程。节点E接收到节点F的NR(0，0，0)消息后，释放E-F之间的桥接，例如，如图4 所示的桥接1；并且，释放A-E之间的选择，例如，如图4所示的选择1。
节点F：节点F接收来自上游节点E的第一无请求消息后，向下游节点G发送第一无请求消息，向上游节点E发送第二无请求消息，并且，节点F接收来自下游节点G的第二无请求消息。
节点F的处理流程和节点E类似，不再赘述。
节点G：节点G接收来自上游节点F的第一无请求消息后，向下游节点B发送第一无请求消息，向上游节点F发送第二无请求消息，并且，节点G接收来自下游节点B的第二无请求消息。
节点G的处理流程和节点F类似，不再赘述。
节点B：节点B接收来自上游节点G的第一无请求消息后，向上游节点G发送第二无请求消息。
具体地，节点B收到来自上游节点G的第一无请求消息NR(W1，0，1)之后，释放B-G之间的桥接以及G-B之间的选择，并向上游节点G发送第二无请求消息NR(0，0，0)。具体地，节点B释放G-B之间的选择以及B-G之间的桥接，可以是先释放选择，再释放桥接；或者先释放桥接，再释放选择；还可以同时释放选择和桥接。
本发明实施例中，还可以由节点B向节点A的方向发送第一无请求消息，节点A向节点B的方向发送第二无请求消息，信令流程类似。或者，如图10b所示，节点A和节点B同时向对端节点发送第一无请求消息。具体地，节点A向节点B的方向发送NR(W1，0，1)消息，节点B收到该消息后，向节点A的方向发送NR(0，0，0)消息。同时，节点B向节点A的方向发送NR(W1，0，1)消息，节点A收到该消息后，向节点B的方向发送NR(0，0，0)消息。各节点收到NR(W1，0，1)消息的处理步骤类似。由于NR(W1，0，1)消息是双向发送的，因此各节点在收到NR(0，0，0)消息后可以不用释放桥接和选择。可选地，节点A和节点B还可以在不同的时刻分别发起保换倒换信令流程，本发明对于信令流程的顺序不作限定。
本发明实施例提出的一种APS开销编码格式中，由于一个帧的APS消息可以表达两个时隙的开销，提高了开销资源的利用率，从而在工作路径故障恢复时，提高了业务恢复的效率。
图12a和图12b是采用本发明实施例提供的一种APS开销编码格式的保护倒换的信令流程图。在图2所示的网络拓扑结构中，工作路径S1的保护路径P1和工作路径S2的保护路径P2共享保护资源的路径为E-F-G，并且业务W2占用共享保护资源的优先级比业务W1高。在图6a和图6b所示的信令流程之后，即当W1从S1倒换至P1之后，当检测到S2发生故障时，需要激活S2的保护路径P2：C-E-F-G-D。由于W2的优先级比W1的优先级高，W2可以抢占共享保护资源E-F-G。本实施例中，信令流程涉及到业务W1从保护路径P1回退至工作路径S1，这个过程和图10a、图10b的工作路径S1故障恢复、业务W1从保护路径P1回退至工作路径的信令流程类似。如图12a和图12b所示，W2抢占共享保护资源的过信令流程涉及到APS消息SF(W2，1，0)，表示信号失效，W2对应的保护资源状态更新为：已被W2 请求，但未桥接。
下面对图12a和图12b所示的信令流程中每个节点的执行步骤作出具体的说明。图12a和图12b的区别在于：图12a是由节点C比节点D先发起保换倒换信令流程，图12b是由节点C和节点D同时发起保护倒换信令流程，下面以图12a为例进行说明：
节点C：节点C检测到工作路径发生故障时，向下游节点E发送第一信号失效消息，并接收来自下游节点E的第一信号失效消息。
本发明实施例中，以节点C为S2、P2的源节点，节点D为S2、P2的宿节点为例进行说明。在S2或P2中，从节点C到节点D的方向为下游方向，从节点D到节点C方向为上游方向。
具体地，节点C检测到工作路径S2发生故障可以是节点C自身检测到链路故障，或者节点D检测到链路故障后通知给节点C。节点C检测到工作路径发生故障时，可以确定节点C和节点E之间的资源可用后，建立C-E之间的桥接。这里的资源可用指的资源是空闲的，即没有其他业务占用。节点C可以在建立C-E之间的桥接之后，向下游节点E发送第一信号失效消息SF(W2，1，1)。
节点C何时接收到来自下游节点E的第一信号失效消息SF(W2，1，1)，取决于节点D何时向节点C的方向发起保护倒换信令流程，具体可以参见节点D和节点E的执行步骤。节点C收到节点E发送的SF(W2，1，1)消息之后，确定节点C和节点E之间的资源可用，建立E-C之间的选择。
第一信号失效消息可以通过APS消息传递，编码格式为SF(W2，1，1)，表示信号失效，保护路径P2已被W2请求，并且已桥接。具体地，信号失效消息SF(W2，1，1)的开销编码格式可以参考图5b～5d、图7a、图7b、图8和图9所示的实施例，对于开销编码中的请求保护路径资源的业务数量、占用保护资源的时隙数量等，本发明不作限定。
节点E：节点E接收到上游节点C的第一信号失效消息后，向下游节点F发送第二信号失效消息，接收来自下游节点F的第一信号失效消息，并向上游节点C发送第一信号失效消息。
具体地，节点E接收到上游节点C的第一信号失效消息SF(W2，1，1)后，检测到E-F之间的资源被W1占用，不建立E-F之间的桥接，并向下游节点F发送第二信号失效消息SF(W2，1，0)。节点E在收到节点C的SF(W2，1，1)消息后，确定节点E和上游节点C之间的资源可用，可以建立C-E之间的选择。可选地，节点E还可以在接收到下游节点F的第一信号失效消息SF(W2，1，1)之后，再建立C-E之间的选择。节点E可以比较W1和W2的优先级，确定W2的优先级比W1的优先级高后，通知节点E在P1的上游节点A将业务W1从P1回退至工作路径S1中。可选地，节点E还可以通过节点F、G通知节点B将业务W1回退至工作路径S1。其中，业务W1回退的过程和图10a、图10b的信令流程类似，此处不再赘述。
节点E何时接收来自下游节点F发送的第一信号失效消息SF(W2，1，1)，取决于节点D何时向节点C的方向发起保护倒换信令流程。节点E收到节点F的SF(W2，1，1)消息后，确定节点E和节点F之间的资源可用后，建立F-E之间的 选择，并且，在确定节点E和节点C之间的资源可用后，建立E-C之间的桥接。节点E在建立E-C之间的桥接之后，向上游节点C发送SF(W2，1，1)消息。
节点E接收到来自下游节点F的SF(W2，1，1)消息后，确定节点E和节点F之间的资源可用，建立E-F之间的桥接。可选地，如果节点E还没有建立C-E之间的选择，还可以在此时建立C-E之间的选择。并且，节点E还向下游节点F发送SF(W2，1，1)消息。具体地，节点E可以先向上游节点C发送SF(W2，1，1)消息，再向下游节点F发送SF(W2，1，1)消息；或者，节点先向下游节点F发送SF(W2，1，1)消息，再向上游节点C发送SF(W2，1，1)消息。
具体地，节点E向下游节点F发送第二信号失效消息SF(W2，1，0)，表示信号失效，保护路径P2已被W2请求，但并未建立桥接。图13为本发明实施例提供的一种SF(W2，1，0)的消息开销编码格式示意图。例如采用ODU2链路保护ODU0链路的业务时，ODU0链路发生故障时，需要占用ODU2链路中一个时隙的保护资源。图13所示的开销编码格式表示ODU2链路的第一时隙被W2请求，但未桥接。第二信号失效消息SF(W2，1，0)的开销编码格式还可以参考图5b～5d、图7a、图7b、图8和图9所示的实施例，对于开销编码中的请求保护路径资源的业务数量、占用保护资源的时隙数量等，本发明不作限定。
节点F：节点F接收到上游节点E的第二信号失效消息，向下游节点G发送第二信号失效消息，接收来自下游节点G的第一信号失效消息，并向上游节点E发送第一信号失效消息。
节点F和处理流程和节点E类似，不再赘述。
节点G：节点G接收到上游节点F的第二信号失效消息，向下游节点D发送第一信号失效消息，接收来自下游节点D的第一信号失效消息，并向上游节点F发送第一信号失效消息。
节点G接收到上游节点F的第二信号失效消息SF(W2，1，0)后，检测到节点G和下游节点D之间的资源可用，建立G-D之间的桥接，并向下游节点D发送第一信号失效消息SF(W2，1，1)。节点G接收到节点F的SF(W2，1，0)消息后，通知节点B将W1从保护路径P1回退至工作路径S1。此时，节点G和节点F之间的资源未被其他业务占用，节点G可以建立F-G之间的选择。可选地，节点G还可以在接收到上游节点F发送的第一信号失效消息SF(W2，1，1)后，再建立F-G之间的选择。
节点G接收到下游节点D的第一信号失效消息SF(W2，1，1)后，如果此时节点G已从上游节点F接收到第二信号失效消息SF(W2，1，0)，则可确定节点G和节点F之间的资源已被业务W1释放，G-F之间的资源可用。节点G可以建立G-F之间的桥接，建立D-G之间的选择，并且节点G向上游节点F发送SF(W2，1，1)消息。
可选地，节点G可以先接收来自节点D的SF(W2，1，1)消息，后接收节点F的SF(W2，1，0)消息。如图12b所示，如果节点G接收到节点D的SF(W2，1，1)消息时，未接收到节点F的SF(W2，1，0)消息，则此时G-F之间的资源有可能被业务W1占用。节点G可以先建立D-G之间的选择，但不建立G-F之间的 桥接，并向上游节点F发送SF(W2，1，0)消息。
节点G何时收到节点F的SF(W2，1，1)消息，取决于节点F何时发送该消息。节点F可以在收到节点G的SF(W2，1，1)消息后，即向节点G发送SF(W2，1，1)消息。节点F还可以在收到节点E的SF(W2，1，1)消息，再向节点G发送SF(W2，1，1)消息。
节点D：节点D接收到上游节点G的第一信号失效消息，向上游节点G发送第一信号失效消息。
节点D还可以在检测到工作路径发生故障后，确定节点G到节点D资源未被其他业务占用，处于可用状态，建立G-D之间的选择，以及D-G之间的桥接。并且，节点D向上游节点G发送第一信号失效消息SF(W2，1，1)。
节点D可以在检测到工作路径S2发生故障后，发起保护倒换信令流程。或者，节点D在接收到上游节点G的SF(W2，1，1)消息之后，再发起保护倒换信令流程。具体地，节点D可以在收到上游节点G的第一信号失效消息SF(W2，1，1)之前，向上游节点G发送第一信号失效消息SF(W2，1，1)。或者，节点D还可以在收到上游节点G的SF(W2，1，1)消息之后，向上游节点G发送SF(W2，1，1)消息。
本实施例中，可以由节点C或节点D单独发起保护倒换信令流程。或者如图12b所示，节点C和节点D同时向对端节点发送第一信号失效消息。具体地，当节点C和节点D同时检测到工作路径故障时，节点C向节点E发送SF(W2，1，1)，节点D向节点G发送SF(W2，1，1)；节点E向节点F发送SF(W2，1，0)，节点G向节点F发送SF(W2，1，0)；此时节点F从两个方向均收到SF(W2，1，0)后，确定业务W1已回退，则可以建立W2的桥接和选择，并且向节点E和节点G发送SF(W2，1，1)；节点E收到SF(W2，1，1)后，向节点F发送SF(W2，1，1)，并向节点C发送SF(W2，1，1)；节点G收到SF(W2，1，1)后，向节点F发送SF(W2，1，1)，并向节点D发送SF(W2，1，1)。各节点可以在接收到SF(W2，1，1)消息后分别建立桥接和选择。
本发明实施例提出的一种APS开销编码格式中，由于一个帧的APS消息可以表达两个时隙的开销，充分利用了APS开销字段，从而在工作路径故障时，提高了保护倒换的效率。
图14是本发明实施例提供的一种网络节点的结构示意图。如图14所示，第一端节点140包括：发送模块141和接收模块142。第一端节点140可以是工作路径和保护路径的共同端节点。
具体地，发送模块141，用于当所述第一端节点和第二端节点之间的工作路径发生故障时，向中间节点发送第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；
接收模块142，用于接收来自所述中间节点的第二保护倒换请求消息，将业务数据切换到所述保护路径上传输；
其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标 识字段和一个桥接标识字段；
所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
可选地，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
可选地，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占8比特，所述请求标志位字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占2比特。
可选地，所述请求类型字段占4比特，所述请求信号标识字段占10比特，所述请求标志字段占1比特，所述桥接标识字段占1比特。
可选地，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占9比特，所述请求标志字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占1比特。
可选地，所述开销信息组还可以包括一个选择标志字段，所述选择标志位字段用于指示所述请求信号标识字段的业务标识对应的保护资源是否已经被选择。
可选地，所述第一保护倒换请求消息和第二保护倒换请求消息为APS消息。
本发明实施例中，在节点进行保护倒换的过程中，保护倒换请求消息的一个开销帧中可以包含两个开销组信息，表达了两个时隙的开销，充分利用了开销字段，提高了保护倒换的效率。
图15是本发明实施例提供的一种网络节点的结构示意图。如图15所示，中间节点150包括：接收模块151和发送模块152。中间节点150可以是保护路径中多个中间节点中的其中一个。
接收模块151，用于当第一端节点和第二端节点之间的工作路径发生故障时，接收到第一端节点的第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；
发送模块152，用于向所述中间节点的下游相邻节点发送第一保护倒换请求消息；
接收模块151，用于接收来自所述中间节点的下游相邻节点的第二保护倒换请求消息；
所述发送模块152，用于向第一端节点发送第二保护倒换请求消息；
其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；
所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
可选地，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
可选地，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占8比特，所述请求标志位字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占2比特。
可选地，所述请求类型字段占4比特，所述请求信号标识字段占10比特，所述请求标志字段占1比特，所述桥接标识字段占1比特。
可选地，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占9比特，所述请求标志字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占1比特。
可选地，所述开销信息组还可以包括一个选择标志字段，所述选择标志位字段用于指示所述请求信号标识字段的业务标识对应的保护资源是否已经被选择。
可选地，所述第一保护倒换请求消息和第二保护倒换请求消息为APS消息。
本发明实施例中，在节点进行保护倒换的过程中，保护倒换请求消息的一个开销帧中可以包含两个开销组信息，表达了两个时隙的开销，充分利用了开销字段，提高了保护倒换的效率。
图16是本发明实施例提供的一种网络节点的结构示意图。如图16所示，第二端节点160包括：接收模块161和发送模块162。第二端节点160可以是工作路径和保护路径上的共同端节点。
接收模块161，用于当第一端节点和第二端节点之间的工作路径发生故障时，接收来自中间节点的第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；
发送模块162，向所述中间节点发送第二保护倒换请求消息；
其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；
所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
可选地，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
可选地，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占8比特，所述请求标志位字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占2比特。
可选地，所述请求类型字段占4比特，所述请求信号标识字段占10比特，所述请求标志字段占1比特，所述桥接标识字段占1比特。
可选地，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占9比特，所述请求标志字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占1比特。
可选地，所述开销信息组还可以包括一个选择标志字段，所述选择标志位字段用于指示所述请求信号标识字段的业务标识对应的保护资源是否已经被选择。
可选地，所述第一保护倒换请求消息和第二保护倒换请求消息为APS消息。
本发明实施例中，在节点进行保护倒换的过程中，保护倒换请求消息的一个开销帧中可以包含两个开销组信息，表达了两个时隙的开销，充分利用了开销字段中的预留字段，提高了保护倒换的效率。
图17是本发明实施例提供的四种网络系统的结构示意图。如图17所示，该系统可以包括图14实施例中的第一端节点和图15实施例中的中间节点；还可以包括图15实施例中的中间节点和图16实施例中的第二端节点；还可以包括图14实施例的第一端节点、图15实施例的中间节点和图16实施例的第二端节点；还可以包括图14实施例的第一端节点和图16实施例的第二端节点。
本发明实施例中，以系统中包括第一端节点、中间节点和第二端节点为例进行说明。其中，中间节点可以包含多个。
当第一端节点和第二端节点之间的工作路径发生故障时，所述第一端节点向中间节点发送第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；
中间节点接收到第一端节点的第一保换倒换请求消息，向第二端节点发送第一保换倒换请求消息；
第二端节点接收来自中间节点的第一保护倒换请求消息，向中间节点发送第二保护倒换请求消息；
中间节点接收来自第二端节点的第二保护倒换请求消息，向第一端节点发送第二保护倒换请求消息；
所述第一端节点接收来自所述中间节点的第二保护倒换请求消息，将业务数据切换到所述保护路径上传输；
其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；
所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
本发明实施例中，在节点进行保护倒换的过程中，保护倒换请求消息的一个开销帧中可以包含两个开销组信息，表达了两个时隙的开销，充分利用了开销字段，提高了保护倒换的效率。
图18是本发明实施例提供的一种OTN(Optical Transport Network，光传送网)设备的硬件结构示意图。如图18所示，OTN设备包括主控板181、OTN线路板182、交叉板183和OTN线路板184。业务的传输方向可以从客户侧到线路侧，还可以从线路侧到客户侧。客户侧发送或接收的业务称为客户侧业务，线路侧接收或发送的业务称为波分侧业务。两个方向上的业务处理流程互为逆向过程，本实施例中以客户侧到线路侧方向为例进行说明：
主控板181通过总线或直接与OTN支路板182、交叉板183、OTN线路板184相连，对OTN支路板182、交叉板183、OTN线路板184起控制管理的功能。
OTN支路板182，完成客户业务的封装映射。客户业务包括多种业务类型，例如ATM(Asynchronous Transfer Mode，异步传输模式)业务、SDH(Synchronous Digital Hierarchy，同步数字体系)业务、以太业务、CPRI(Common Public Radio Interface，通用公共无线电接口)业务、存储业务等。具体地，支路板182用于接收来自客户侧的客户业务，将接收到的客户业务封装映射到ODU(Optical Channel Data Unit，光通道数据单元)信号并添加相应的OTN管理监控开销。在OTN支路板182上，ODU信号可以为低阶ODU信号，例如ODU0、ODU1、ODU2、ODU3、ODUflex等，OTN管理监控开销可以为ODU开销。针对不同类型的客户业务，采用不同的方式封装映射到不同的ODU信号中。
交叉板183，完成支路板和线路板的全交叉连接，实现ODU信号的灵活交叉调度。具体地，交叉板可以实现将ODU信号从任意一个支路板传输到任意一个线路板，或者将OTU信号从任意一个线路板传输到任意一个线路板，还可以将客户信号从任意一个支路板传输到任意一个支路板。
OTN线路板184，将ODU信号形成OTU(Optical Channel Transport Unit，光通道传输单元)信号并发送到线路侧。在ODU信号形成OTU信号之前，OTN线路板184可以将低阶多路ODU信号复用到高阶ODU信号中。然后高阶ODU信号添加相应OTN管理监控开销形成OTU信号并发送到线路侧的光传输通道中。在OTN线路板上，高阶ODU信号信号可以为ODU1、ODU2、ODU3、ODU4等，OTN管理监控开销可以为OTU开销。
主控板181可以执行预先配置的程序代码，控制OTN支路板182、交叉板183、OTN线路板184中的任意一种或多种单板完成下面的功能：
例如，OTN线路板184或OTN支路板182检测到第一端节点和第二端节点之间的工作路径发生故障时，向中间节点发送第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；OTN线路板184或OTN支路板182接收来自所述中间节点的第二保护倒换请求消息，
交叉板183将业务数据切换到所述保护路径上传输。
其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；
所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
可选地，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
可选地，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求标志位字段占1比特，所述桥接标识字段占1比特。请求信号标识字段可以占用8比特、9比特或10比特，对应预留字段分别占用2比特、1比特和0比特。
本发明实施例中，APS消息的一个开销帧中可以包含两个开销组信息，表达了两个时隙的开销，充分利用了开销字段，提高了保护倒换的效率。
具体地，通过图18所示的OTN设备180可以实现图6a、图6b、图10a、图10b、图12a和图12b所示的方法步骤。应注意，尽管图18所示的OTN设备180仅仅示出了主控板181、OTN线路板182、交叉板183和OTN线路板184，但是在具体实现过程中，本领域的技术人员应当明白，OTN设备180还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，OTN设备180还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，OTN设备180也可仅仅包含实现本发明实施例所必须的器件，而不必包含图18中所示的全部器件。
本领域普通技术人员将会理解，本发明的各个方面、或各个方面的可能实现方式可以被具体实施为系统、方法或者计算机程序产品。因此，本发明的各方面、或各个方面的可能实现方式可以采用完全硬件实施例、完全软件实施例(包括固件、驻留软件等等)，或者组合软件和硬件方面的实施例的形式，在这里都统称为“电路”、“模块”或者“系统”。此外，本发明的各方面、或各个方面的可能实现方式可以采用计算机程序产品的形式，计算机程序产品是指存储在计算机可读介质中的计算机可读程序代码。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。

Claims (18)

  1. 一种保护倒换的方法，其特征在于，所述方法包括：
    当第一端节点和第二端节点之间的工作路径发生故障时，所述第一端节点向中间节点发送第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；
    所述第一端节点接收来自所述中间节点的第二保护倒换请求消息，将业务数据切换到所述保护路径上传输；
    其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；
    所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
  2. 如权利要求1所述的方法，其特征在于，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
  3. 如权利要求2所述的方法，其特征在于，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占8比特，所述请求标志位字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占2比特。
  4. 如权利要求2所述的方法，其特征在于，所述请求类型字段占4比特，所述请求信号标识字段占10比特，所述请求标志字段占1比特，所述桥接标识字段占1比特。
  5. 如权利要求2所述的方法，其特征在于，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占9比特，所述请求标志字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占1比特。
  6. 如权利要求1-5任一所述的方法，其中，所述第一保护倒换请求消息和第二保护倒换请求消息为自动保换倒换APS消息。
  7. 如权利要求1，3或5所述的方法，其特征在于，所述开销信息组还可以包括一个选择标志字段，所述选择标志位字段用于指示所述请求信号标识字段的业务标识对应的保护资源是否已经被选择。
  8. 一种第一端节点，其特征在于，所述第一端节点包括：
    发送模块，用于当所述第一端节点和第二端节点之间的工作路径发生故障时，向中间节点发送第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；
    接收模块，用于接收来自所述中间节点的第二保护倒换请求消息，将业务数据切换到所述保护路径上传输；
    其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标 识字段和一个桥接标识字段；
    所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
  9. 如权利要求8所述的第一端节点，其特征在于，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
  10. 如权利要求9所述的第一端节点，其特征在于，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占8比特，所述请求标志位字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占2比特。
  11. 如权利要求9所述的第一端节点，其特征在于，所述请求类型字段占4比特，所述请求信号标识字段占10比特，所述请求标志字段占1比特，所述桥接标识字段占1比特。
  12. 如权利要求9所述的第一端节点，其特征在于，所述开销信息组还包括一预留字段，其中所述请求类型字段占4比特，所述请求信号标识字段占9比特，所述请求标志字段占1比特，所述桥接标识字段占1比特，以及所述预留字段占1比特。
  13. 如权利要求8-12任一所述的第一端节点，其中，所述第一保护倒换请求消息和第二保护倒换请求消息为自动保护倒换APS消息。
  14. 如权利要求8，10或12所述的第一端节点，其特征在于，所述开销信息组还可以包括一个选择标志字段，所述选择标志位字段用于指示所述请求信号标识字段的业务标识对应的保护资源是否已经被选择。
  15. 一种中间节点，其特征在于，所述中间节点包括：
    接收模块，用于当第一端节点和第二端节点之间的工作路径发生故障时，接收到第一端节点的第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；
    发送模块，用于向所述中间节点的下游相邻节点发送第一保护倒换请求消息；接收模块，用于接收来自所述中间节点的下游相邻节点的第二保护倒换请求消息；还用于向第一端节点发送第二保护倒换请求消息；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
  16. 如权利要求15所述的中间节点，其特征在于，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
  17. 一种第二端节点，其特征在于，所述第二端节点包括：
    接收模块，用于当第一端节点和第二端节点之间的工作路径发生故障时，接收来自中间节点的第一保护倒换请求消息，其中所述工作路径的保护路径包括所述第一端节点、所述第二端节点以及至少一个所述中间节点；
    发送模块，用于向所述中间节点发送第二保护倒换请求消息；其中，所述第一保护倒换请求消息和第二保护请求消息中的一个开销帧包括至少两个开销信息组，所述开销信息组包括一个请求类型字段、一个请求信号标识字段和一个桥接标识字段；所述请求类型字段指示工作路径的故障类型，所述请求信号标识字段为请求保护资源的业务的业务标识，所述桥接标识字段指示所述请求信号标识字段的业务标识对应的保护资源是否已经被桥接。
  18. 如权利要求17所述的第二端节点，其特征在于，所述开销信息组还包括一个请求标志字段，所述请求标志位字段用于指示所述请求信号标识字段的业务标识对应的业务是否请求保护资源。
PCT/CN2017/071192 2016-01-19 2017-01-14 一种保护倒换的方法和节点 Ceased WO2017124982A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2018555809A JP6562435B2 (ja) 2016-01-19 2017-01-14 プロテクション切替方法およびノード
EP17741013.1A EP3393059B1 (en) 2016-01-19 2017-01-14 Protection switching method and node
KR1020187023155A KR102064853B1 (ko) 2016-01-19 2017-01-14 보호 절체 방법 및 노드
US16/038,531 US10674240B2 (en) 2016-01-19 2018-07-18 Protection switching method and node
US16/861,659 US10993005B2 (en) 2016-01-19 2020-04-29 Protection switching method and node

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610034671.9A CN105721045B (zh) 2016-01-19 2016-01-19 一种保护倒换的方法和节点
CN201610034671.9 2016-01-19

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/038,531 Continuation US10674240B2 (en) 2016-01-19 2018-07-18 Protection switching method and node

Publications (1)

Publication Number Publication Date
WO2017124982A1 true WO2017124982A1 (zh) 2017-07-27

Family

ID=56147187

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/071192 Ceased WO2017124982A1 (zh) 2016-01-19 2017-01-14 一种保护倒换的方法和节点

Country Status (6)

Country Link
US (2) US10674240B2 (zh)
EP (1) EP3393059B1 (zh)
JP (1) JP6562435B2 (zh)
KR (1) KR102064853B1 (zh)
CN (1) CN105721045B (zh)
WO (1) WO2017124982A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114337952A (zh) * 2020-09-30 2022-04-12 烽火通信科技股份有限公司 一种通信链路协商的方法和系统

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7552796B2 (en) 2006-04-27 2009-06-30 United Technologies Corporation Turbine engine tailcone resonator
CN105721045B (zh) * 2016-01-19 2018-08-21 华为技术有限公司 一种保护倒换的方法和节点
JP6803692B2 (ja) * 2016-06-30 2020-12-23 グローリー株式会社 現金処理システム、現金処理方法及び携帯端末
CN109155740B (zh) 2016-09-21 2021-07-20 华为技术有限公司 保护倒换方法和节点
CN108419259B (zh) * 2018-02-11 2021-05-28 烽火通信科技股份有限公司 基于保留开销字段实现灵活以太网保护倒换的方法及系统
CN110581746B (zh) * 2018-06-11 2020-12-18 中国移动通信集团广东有限公司 一种拉远波分接入单元、组网结构及组网方法
CN113709601B (zh) * 2020-05-20 2022-10-28 华为技术有限公司 一种光传输设备、系统及光传输方法
CN113727220B (zh) * 2020-05-26 2023-04-11 华为技术有限公司 业务资源预配置方法、设备和系统
CN117856883A (zh) * 2020-09-27 2024-04-09 华为技术有限公司 一种业务保护方法和网络节点

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090003326A1 (en) * 2007-06-26 2009-01-01 Hirokazu Ozaki Interface switching method and device
CN102868544A (zh) * 2011-07-06 2013-01-09 中兴通讯股份有限公司 一种实现共享网格保护的方法及系统
CN104067539A (zh) * 2014-04-29 2014-09-24 华为技术有限公司 支持混合粒度业务共享资源的处理方法与节点
CN105721045A (zh) * 2016-01-19 2016-06-29 华为技术有限公司 一种保护倒换的方法和节点

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4045197B2 (ja) * 2003-03-28 2008-02-13 富士通株式会社 伝送装置及びコンカチネーション設定方法
CN100403660C (zh) * 2004-09-04 2008-07-16 华为技术有限公司 双纤光复用段共享保护环的保护方法及其节点装置
CN100352226C (zh) * 2004-12-13 2007-11-28 华为技术有限公司 实现m：n环网保护倒换操作的方法
CN101051995B (zh) * 2006-06-05 2012-07-04 华为技术有限公司 基于无连接网络的保护倒换方法
JP5039639B2 (ja) * 2008-06-09 2012-10-03 株式会社日立製作所 パスプロテクション機能を有する通信装置及びその通信装置を使用するネットワークシステム
US20100135291A1 (en) * 2008-11-28 2010-06-03 Nortel Networks Limited In-band signalling for point-point packet protection switching
CN102013922B (zh) 2009-09-04 2014-03-12 华为技术有限公司 光网络中的信息处理方法、光通信装置及系统
CN102457435B (zh) 2010-10-27 2015-02-25 杭州华三通信技术有限公司 Fc网络中的报文转发方法和fc系统及fc设备
CN102098123B (zh) * 2011-02-28 2013-11-06 中国人民解放军理工大学 复用段共享保护环保护倒换协议的节点寻址方法
US9385943B2 (en) 2011-09-19 2016-07-05 Infinera Corporation Encoding and processing of signaling messages for ODU SMP
CN103313148B (zh) 2012-03-13 2018-08-14 中兴通讯股份有限公司 开销修改及防止子网同时倒换的方法、装置、网元和网络
US9258215B2 (en) * 2013-01-02 2016-02-09 Infinera Corporation Optical layer protection switching applications
CN103200467B (zh) * 2013-03-14 2016-03-23 烽火通信科技股份有限公司 光网络设备中的网元协议报文传递装置及方法
KR20150077265A (ko) 2013-12-27 2015-07-07 한국전자통신연구원 Odu smp 네트워크에서 보호 경로를 선택하는 방법 및 장치
US20150186216A1 (en) * 2013-12-27 2015-07-02 Electronics And Telecommunications Research Institute Method and apparatus for selecting protection path on odu smp (optical channel data unit shared mesh protection) network
KR102017880B1 (ko) * 2014-07-16 2019-09-03 한국전자통신연구원 ODUflex(GFP)신호를 지원하는 광 전달망에서의 보호절체 장치 및 보호절체 방법
CN104158586B (zh) * 2014-08-06 2017-01-11 华为技术有限公司 一种倒换实现方法、站点及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090003326A1 (en) * 2007-06-26 2009-01-01 Hirokazu Ozaki Interface switching method and device
CN102868544A (zh) * 2011-07-06 2013-01-09 中兴通讯股份有限公司 一种实现共享网格保护的方法及系统
CN104067539A (zh) * 2014-04-29 2014-09-24 华为技术有限公司 支持混合粒度业务共享资源的处理方法与节点
CN105721045A (zh) * 2016-01-19 2016-06-29 华为技术有限公司 一种保护倒换的方法和节点

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114337952A (zh) * 2020-09-30 2022-04-12 烽火通信科技股份有限公司 一种通信链路协商的方法和系统
CN114337952B (zh) * 2020-09-30 2023-06-09 烽火通信科技股份有限公司 一种通信链路协商的方法和系统

Also Published As

Publication number Publication date
EP3393059B1 (en) 2025-07-30
KR102064853B1 (ko) 2020-01-10
US20200260163A1 (en) 2020-08-13
EP3393059A1 (en) 2018-10-24
CN105721045A (zh) 2016-06-29
CN105721045B (zh) 2018-08-21
EP3393059A4 (en) 2018-12-19
KR20180102629A (ko) 2018-09-17
US20180324505A1 (en) 2018-11-08
JP2019507561A (ja) 2019-03-14
US10993005B2 (en) 2021-04-27
US10674240B2 (en) 2020-06-02
JP6562435B2 (ja) 2019-08-21

Similar Documents

Publication Publication Date Title
US10993005B2 (en) Protection switching method and node
US9432749B2 (en) Communication system, communication control method, and transmission apparatus
EP2451186B1 (en) Method for assigning and processing label in optical network, optical communication device and optical communication system
US9154373B2 (en) Failure protection method and node apparatus
WO2006026914A1 (en) Service protecting method for optical transmission network and node device
CN106803814A (zh) 一种灵活以太网路径的建立方法、装置及系统
CN102013922B (zh) 光网络中的信息处理方法、光通信装置及系统
US11251863B2 (en) Protection switching method and node
WO2017201953A1 (zh) 一种客户业务处理的方法和设备
JP2015136023A (ja) 冗長パス提供方法および伝送装置
CN102136865B (zh) 业务恢复方法、系统和节点设备
CN101686151B (zh) 一种业务传送网络的通道保护方法和系统
CN101848035B (zh) 一种otn网络中共享保护的方法、系统和节点设备
US7835271B2 (en) Signaling protocol for p-cycle restoration
US20160366048A1 (en) Communication system, node and signal path control method in communication system
CN100421359C (zh) 通信网络中实现m：n保护的方法及其网络节点装置
CN100438475C (zh) 环网中保护倒换的实现方法
WO2011017863A1 (zh) 光数据单元环路共享保护控制方法与装置
EP2953294B1 (en) Protection switching method, system, and node
CN101686094A (zh) 一种业务传送网络的通道保护方法和系统
CN102868544A (zh) 一种实现共享网格保护的方法及系统
CN102724066A (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: 17741013

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018555809

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2017741013

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017741013

Country of ref document: EP

Effective date: 20180719

ENP Entry into the national phase

Ref document number: 20187023155

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020187023155

Country of ref document: KR

WWG Wipo information: grant in national office

Ref document number: 2017741013

Country of ref document: EP