WO2013178098A1 - 域间故障信息的发送方法及装置 - Google Patents

域间故障信息的发送方法及装置 Download PDF

Info

Publication number
WO2013178098A1
WO2013178098A1 PCT/CN2013/077069 CN2013077069W WO2013178098A1 WO 2013178098 A1 WO2013178098 A1 WO 2013178098A1 CN 2013077069 W CN2013077069 W CN 2013077069W WO 2013178098 A1 WO2013178098 A1 WO 2013178098A1
Authority
WO
WIPO (PCT)
Prior art keywords
lsp
layer lsp
service layer
inter
service
Prior art date
Application number
PCT/CN2013/077069
Other languages
English (en)
French (fr)
Inventor
王明秀
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US14/416,341 priority Critical patent/US20150186202A1/en
Priority to EP13796745.1A priority patent/EP2866394B1/en
Priority to BR112015002613A priority patent/BR112015002613A2/pt
Publication of WO2013178098A1 publication Critical patent/WO2013178098A1/zh

Links

Classifications

    • 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/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0772—Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data

Definitions

  • the present invention relates to the field of communications, and in particular to a method and apparatus for transmitting inter-domain fault information.
  • the backbone network devices include Dense Wavelength Division Multiplexing (DWDM) type devices, Packet Transfer Network (PTN) devices, and synchronization. Devices such as Synchronous Digital Hierarchy (SDH) devices and routers are connected to the backbone network.
  • DWDM Dense Wavelength Division Multiplexing
  • PTN Packet Transfer Network
  • SDH Synchronous Digital Hierarchy
  • different devices belong to different layers, such as the DWDM device network belongs to the service layer, and the PTN device network belongs to the customer layer.
  • AS autonomous systems
  • AS autonomous systems
  • end-to-end customer services need to traverse each network, and each network may belong to different layers and different AS domains.
  • the FA-LSP Forwarding Adjacency-LSP
  • the carrier may deploy protection and recovery in different networks.
  • a network fails, it will not only trigger the protection and recovery of the local layer, but also the customer layer service due to the transmission of alarms. To the alarm, therefore, it is necessary to consider how the client layer and the service layer network protection and recovery are coordinated to ensure reliable recovery of the service without breaking multiple times.
  • a static coordination method is generally used, that is, a delay timer is started in different layers to coordinate. In this way, the client layer cannot know whether the protection and recovery of the service layer fails.
  • the delay timer When the delay timer expires, it determines whether to start protection and recovery by searching for the alarm at the client layer again. Therefore, when the protection and recovery of the service layer fails, the client layer has been waiting for a delay, resulting in a long service break time. At the same time, there are many inter-layer coordination in the same kind of equipment in the network, and the dynamic coordination of cross-domain protection and recovery is still in the research stage. In view of the above problems in the related art, an effective solution has not yet been proposed.
  • the client layer cannot know whether the protection and recovery of the service layer fails in time, and the service interruption time is lengthened.
  • the present invention provides a method and device for transmitting inter-domain fault information, so as to at least solve the above problem.
  • a method for transmitting inter-domain fault information including: a service layer label switching path LSP determines that the service layer LSP protection or recovery fails; and the service layer LSP to the service layer LSP
  • the customer layer LSP sends the inter-domain fault information, where the inter-domain fault information is used to indicate that the service layer LSP protection or recovery is invalid.
  • the QoS layer and the client layer LSP belong to different autonomous systems. AS domain.
  • the method further includes: protecting, or recovering, the service layer LSP by the client layer LSP; and the client layer
  • the client layer LSP continues to send the inter-domain fault information to the client layer LSP of the client layer LSP.
  • the step of protecting or restoring the service layer LSP by the client layer LSP includes: the client layer LSP establishes a new connection according to the inter-domain fault information, and switches the service of the client layer LSP to the new Connection.
  • the method further includes: when the fault indicated by the inter-domain fault information disappears, the service layer LSP sends an inter-domain fault disappearing message to the client layer LSP, where the inter-domain fault disappearing message is used to indicate the The fault indicated by the inter-domain fault information disappears.
  • the method further includes: receiving, by the client layer LSP, the inter-domain failure disappear message, and determining according to pre-configuration Whether the service of the client layer LSP is switched back to the connection of the service layer LSP, and if so, the service of the client layer LSP is switched back to the connection of the service layer LSP.
  • the service layer LSP determines that the service layer LSP protection or recovery fails: the service layer LSP is faulty, or the service layer LSP receives the inter-domain fault information, the service layer LSP is opposite to the service layer LSP. Performing protection or recovery, when the protection or recovery of the service layer LSP fails, the service layer LSP determines that the service layer LSP protection or recovery fails.
  • the method further includes: when the connection of the service layer LSP fails, the client layer LSP starts a pre-configured delay timer; and if the client layer LSP receives the service layer before the delay timer expires The inter-domain fault information sent by the LSP, the client layer LSP stops the delay timer, and protects or recovers the service layer LSP.
  • the step of the service layer LSP transmitting the inter-domain fault information to the client layer LSP of the service layer LSP includes: the first node sending the inter-domain fault information to the second node, where the first node is the ⁇ service layer The first node of the LSP, and the second node is the first node of the client layer LSP.
  • Inter-domain fault information includes: The location of the fault and/or the type of fault.
  • an apparatus for transmitting inter-domain fault information which is located at a head node of a service layer LSP, and the apparatus includes: a determining module configured to determine a service layer LSP protection or restoration And a sending module, configured to send the inter-domain fault information to the client layer LSP of the service layer LSP, where the inter-domain fault information is used to indicate that the service layer LSP protection or recovery fails;
  • the service layer LSP and the client layer LSP belong to different AS domains.
  • the apparatus further includes a protection and recovery module configured to set the service layer LSP when the connection of the service layer LSP fails or the service layer LSP receives the inter-domain failure information Protect or recover.
  • the determining module is configured to determine that the service layer LSP protection or recovery fails when the protection and recovery module fails to protect or recover the service layer LSP.
  • the service layer LSP determines that the service layer LSP protection or recovery fails, and the service layer LSP sends inter-domain fault information to the client layer LSP of the service layer LSP, indicating that the service layer LSP protection or recovery is invalid, so that the client layer LSP is informed of the service in time.
  • Layer LSP protection or recovery fails, and the service layer LSP is protected or restored in time, which shortens the end-to-end service interruption time and improves network survivability.
  • FIG. 1 is a flowchart of a method for transmitting inter-domain fault information according to an embodiment of the present invention
  • FIG. 2 is a device for transmitting inter-domain fault information according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a dynamic coordination framework system in a multi-layer multi-domain network according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a dynamic coordination framework system in a multi-layer multi-domain network according to an embodiment of the present invention
  • FIG. 1 is a flowchart of a method for transmitting inter-domain fault information according to an embodiment of the present invention
  • FIG. 2 is a device for transmitting inter-domain fault information according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a dynamic coordination framework system in a multi-layer multi-domain network according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a dynamic coordination framework system in a multi-layer multi-domain network according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a multi-layer multi-domain network service layer post-fault dynamic coordination example 1 according to an embodiment of the present invention
  • FIG. 7 is a multi-layer multi-domain according to an embodiment of the present invention
  • the client layer cannot know whether the protection and recovery of the service layer fails in time, and the service interruption time is lengthened.
  • the embodiment of the present invention provides a method and device for transmitting inter-domain fault information. By transmitting inter-domain fault information in real time, the client layer can dynamically and timely know whether the service layer protection and recovery is successful. When the service layer protection and recovery fails, the service connection is protected or restored in time, which shortens the end-to-end service fault. Time has improved network survivability.
  • Embodiment 1 provides a method for transmitting inter-domain fault information according to an embodiment of the present invention, so as to send an inter-domain fault information to an upper layer (client layer) LSP when the lower layer (service layer) LSP protection or recovery fails, so that The upper LSP protects or recovers the service connection according to the inter-domain fault information.
  • 1 is a flowchart of a method for transmitting inter-domain fault information according to an embodiment of the present invention. As shown in FIG. 1, the method may include steps S102 to S104: Step S102, the service layer LSP determines that the service layer LSP protection or recovery fails.
  • Step S104 The service layer LSP sends inter-domain fault information to the client layer LSP of the service layer, where the inter-domain fault information is used to indicate that the service layer LSP protection or recovery is invalid, and the service layer LSP is different from the client layer LSP. AS domain.
  • the service layer LSP determines that the service layer LSP protection or recovery fails, and the inter-domain fault information is sent to the customer layer LSP of the service layer LSP, indicating that the service layer LSP protection or recovery is invalid, so that the client layer LSP is informed of the service layer in time.
  • the LSP protection or recovery fails, so that the client layer LSP can protect or recover the service layer LSP in time, shortening the end-to-end service interruption time and improving the network survival.
  • the service layer LSP may start the protection or recovery function to protect or recover the service layer LSP, and the protection or recovery fails.
  • the service layer LSP determines that the service layer LSP protection or recovery fails.
  • the inter-domain fault information may be sent to the upper layer LSP (that is, the client layer LSP of the service layer LSP), indicating that the service layer LSP protection or recovery is invalid, so that the upper layer LSP acquires the lower layer LSP protection or fails in time.
  • the lower layer LSP is protected or restored. Because the upper layer LSP knows more comprehensive link information, the lower layer LSP can be protected or restored more quickly.
  • the inter-domain fault information may include the location of the fault and Information such as the type of barrier.
  • the client layer LSP may protect or recover the service layer LSP.
  • the client layer LSP may send an inter-domain fault to the upper layer LSP of the client layer LSP (the client layer serves as the service layer for the upper layer LSP) information.
  • the inter-domain fault information is transmitted to the upper layer LSP in the multi-layer multi-domain network, so that the upper layer LSP can obtain the protection or recovery failure in time, thereby reducing the end-to-end service. Break time, improve business reliability.
  • the client layer LSP protects or recovers the service layer LSP
  • a new connection may be established according to the inter-domain fault information, and the service of the client layer LSP is switched to the newly established connection.
  • the client layer LSP is configured to optimize re-routing, the client layer LSP can generate a recovery path according to the inter-domain fault information, and switch the end-to-end service of the client layer LSP to the newly established connection.
  • the client layer LPS After the client layer LPS switches the service to the new connection, it can stop sending the inter-domain fault information to the upper layer LSP of the client layer LSP.
  • the service layer LSP may send an inter-domain fault disappearing message to the client layer LSP, where the inter-domain fault disappearing message is used to indicate the inter-domain The fault indicated by the fault message disappears.
  • the upper-layer LSP After receiving the inter-domain fault disappearing message, the upper-layer LSP can dynamically select the connection of the LSP service of the layer according to actual requirements.
  • the inter-domain fault disappearing message is used to indicate that the fault indicated by the inter-domain fault information disappears.
  • the client layer LSP can receive the inter-domain failure disappearing message, and determine whether to cut the service of the client layer LSP back to the connection of the service layer LSP according to the pre-configuration. If yes, the service layer LSP service is switched back to the service layer LSP. connect.
  • protection and recovery can be deployed in different networks. When a network fails, the protection and recovery of the local layer are triggered. Alarm, the client layer starts the delay timer.
  • the delay timer determines whether to start protection and recovery by searching for the presence of an alarm at the client layer.
  • the protection and recovery of the service layer fails, the client layer has been waiting for a delay, resulting in a longer business break.
  • the second node may enable a pre-configured delay timer, where the second section The node is the first node of the client layer LSP. If the client layer LSP receives the inter-domain fault information sent by the service layer LSP before the delay timer expires, the second node may stop the delay timer and protect the service layer LSP. Or restore.
  • the LSP connection includes multiple nodes.
  • the other node may send an inter-domain fault message to the upper layer LSP.
  • the service layer LSP is sent to the client.
  • the layer LSP sends the inter-domain fault information the first node may send the inter-domain fault information to the second node, where the first node is the first node of the service layer LSP, and the second node is the first node of the client layer LSP.
  • the inter-domain fault information may also be sent to the node of the upper LSP through the transfer between the nodes, and processed by the corresponding node.
  • FIG. 2 is a device for transmitting inter-domain fault information according to an embodiment of the present invention, as shown in FIG.
  • the device mainly comprises: a determining module 10 and a transmitting module 20.
  • the determining module 10 is configured to determine the service layer LSP protection or recovery failure; the sending module 20 is coupled to the determining module 10, and is configured to send the inter-domain fault information to the client layer LSP of the service layer LSP, where the customer layer LSP is The upper layer LSP of the service layer LSP, the inter-domain fault information is used to indicate that the service layer LSP protection or recovery is invalid, and the service layer LSP and the client layer LSP belong to different AS domains.
  • the determining module 10 determines that the service layer LSP protection or recovery fails, and the sending module 20 sends inter-domain fault information to the upper layer (customer layer) LSP of the service layer LSP, indicating that the service layer LSP protection or recovery fails, so that the client layer
  • the LSP is informed in time that the LSP protection or recovery of the service layer fails, and the service layer LSP is protected or restored in time, which shortens the end-to-end service interruption time and improves network survivability.
  • the determining module 10 may determine that the service layer LSP protection or recovery failure occurs in the following manner: when the connection of the service layer LSP fails, or when the service layer LSP receives the inter-domain fault information, the protection is performed. The service layer LSP is protected or restored with the recovery module. When the protection or recovery of the service layer LSP fails, the determining module 10 determines that the service layer LSP protection or recovery fails.
  • the apparatus may further include: a protection and recovery module configured to protect or restore the service layer LSP when the connection of the service layer LSP fails, or the service layer LSP receives the inter-domain failure information.
  • Embodiment 2 According to an embodiment of the present invention, a system for multi-layer multi-domain network protection and recovery dynamic coordination is provided, and based on the system, a multi-layer multi-domain network protection and recovery dynamic coordination method is provided, which is implemented in real time.
  • the problem of inter-domain failure information is transmitted, which solves the problem that the client layer cannot know the success of the protection and recovery of the service layer in real time in the multi-layer multi-domain network, shortens the time of end-to-end service interruption, and improves the network survival.
  • the method for dynamic coordination of multi-layer multi-domain network protection and recovery in the preferred embodiment includes the following steps (step 1 to step 3): Step 1: After the service layer network fails, the first node in the network starts the domain.
  • Step 2 After determining the protection and recovery failure of the local layer, the first node of the service layer generates inter-domain fault information, and transmits the inter-domain fault information upstream along the LSP path.
  • Step 3 When the first node of the upper layer network LSP (client layer) detects an inter-domain fault, it is determined whether the layer needs to start protection or recovery. When the protection or recovery is successful, the inter-domain fault information is terminated; when protection or recovery When it fails, continue to pass the inter-domain fault information to the upper layer.
  • step 1 when the first layer of the client layer detects an LSP failure, the timer may also be started at the same time; in step 3, the first node of the client layer receives the inter-domain. In the event of a fault, the timer started in step 1 is terminated.
  • steps 1 and 2 correspond to the step S102 and the step S104 of the foregoing embodiment of the present invention, and the inter-domain fault information is sent to the upper layer LSP when the layer protection or recovery fails.
  • the system for multi-layer multi-domain network protection and recovery dynamic coordination of the preferred embodiment mainly includes: a network detector (corresponding to the determining module 10 of the above embodiment of the present invention), located at a domain boundary node, which is set to be in failure After detecting whether the protection or recovery in the domain is invalid; the inter-domain fault information processor (corresponding to the sending module 20 of the above embodiment of the present invention) is located at the domain boundary node, and is configured to generate fault information after protection and recovery failure. And transmitting the generated inter-domain fault information to the upper layer LSP; the recovery trigger (corresponding to the protection and recovery module of the above embodiment of the present invention) is located at the domain boundary node, and is set to determine after receiving the inter-domain fault information. Perform customer layer protection and recovery.
  • the client layer can wait for the delay timer to time out, and immediately after receiving the inter-domain fault information, immediately start the protection and recovery of the client layer, thereby shortening the fault damage. Time, make full use of network resources, and improve the survivability of the bearer network.
  • there are multiple bearer devices in the communication network and each device belongs to a different layer. These devices may be in different geographies and are therefore distributed across different routing domains.
  • the IETF has released a series of standards to extend RSVP-TE. There are two schemes, one is Hierarchy-LSP (H-LSP for short).
  • H-LSP the LSP created by the Hierachy mode, that is, the H-LSP (defined by the RFC4206 as the FA-LSP), can form a TE link in its upper layer (the client layer); the upper layer LSP can be established.
  • the TE link performs route calculation.
  • the H-LSP can be used as a service layer for multiple client layer LSPs.
  • the S-LSP the LSP created by the Stiching method, that is, the S-LSP
  • the seaming technology requires that the interface switching capability of each LSP segment must be the same.
  • FIG. 3 is a flowchart of a method for dynamic coordination of multi-layer multi-domain network protection and recovery according to an embodiment of the present invention. As shown in FIG. 3, the method may include steps S302 to S312. Step S302, detecting an inter-domain fault. Before the inter-domain fault detection, the upper layer LSP needs to be carried in the Path message when it is established.
  • NOTIFY - REQUEST object which records the IP address of the upper LSP head node.
  • the first node of the FA-LSP After receiving the upper-layer Path message, the first node of the FA-LSP needs to record the IP address as the destination address for sending inter-domain fault information.
  • a layer of LSPs configured with protection and recovery needs to set a reasonable delay timer.
  • the lowest layer of the upper layer network delay timer is set to T1
  • the second layer upper layer network delay timer needs to be set to 2*T1
  • the third layer upper layer network delay timer is set to 3* ⁇ 1, and so on. Service layer delay timer.
  • the first node needs to detect and determine whether the protection or recovery of the layer fails; if it fails, perform subsequent processing; Step S304, the first node of the service layer LSP learns that the protection or recovery failure in the domain is successful. , generate fault information.
  • the fault information may include: fault location, fault type.
  • the fault location includes the FA-LSP fault, the FA-LSP head node fault, and the fault type is the physical fault type of the FA-LSP.
  • FA-LSP failure means that the FA-LSP itself has no protection and recovery attributes.
  • FA-LSP first node failure means that the FA-LSP itself is configured with protection or recovery attributes, but the protection or recovery fails due to lack of resources. Step S306, the inter-domain fault information is generated.
  • the generated inter-domain fault information is set to the inter-domain delivery message, and the filled information includes the fault type, the fault location, and the destination address.
  • the IP address saved in step S302 is set, and the inter-domain failure information is transmitted.
  • Step S308 after receiving the inter-domain fault information, the upper node of the upper layer LSP terminates the delay timer started by the layer, and determines whether protection and recovery can be started.
  • Step S310 After receiving the inter-domain fault information, the first node of the end-to-end LSP terminates the delay timer started by the local layer, and restores the end-to-end service globally according to the protection or recovery of the end-to-end LSP configuration.
  • the first node when a certain layer of LSP is configured to optimize rerouting, the first node needs to transmit the fault information to the route calculation unit, such as the PCE, and receive the calculation result of the route calculation unit, generate a recovery path, and end-to-end service. Switch to the newly created connection.
  • the method of the embodiment of the present invention may further include step S312.
  • Step S312 after the fault disappears, the first node in step S304 needs to generate information that the inter-domain fault disappears, and transmits it to the upstream, and the path and method of the transmission are the same as the fault information.
  • 4 is a schematic diagram of a dynamic coordination framework system in a multi-layer multi-domain network according to an embodiment of the present invention. As shown in FIG.
  • the system mainly includes: a network detector (corresponding to the determining module 10 of the foregoing embodiment of the present invention)
  • the inter-domain fault information processor (corresponding to the transmitting module 20 of the above embodiment of the present invention)
  • the recovery trigger (corresponding to the protection and recovery module of the above embodiment of the present invention).
  • the above three modules are located on the domain boundary nodes to coordinate and coordinate the dynamic coordination of inter-domain protection and recovery.
  • the network detector is set to detect whether the protection or recovery of the layer is invalid when the fault of the layer is caused by the failure of the service layer; in the same layer, multiple protection and recovery methods may be configured. For example, configure end-to-end protection and dynamic re-routing of this layer, and configure multiple protection services such as MPLS FRR and dynamic re-routing.
  • the inter-domain fault information processor is configured to collect the information of the first node of the upper layer LSP (Service Layer FA-LSP), that is, the IP address, which is transmitted when the upper layer LSP triggers the establishment of the local layer LSP.
  • the inter-domain fault information processor is configured to generate inter-domain fault information after receiving the local layer protection and recovery failure information sent by the network detector, and the fault information may include a fault location and a fault type. After the fault information is generated, you can send the fault type, fault location, and destination address in the notify message.
  • the inter-domain fault information processor can also directly receive the inter-domain fault information sent by the service layer from the protocol layer, and can transmit the received inter-domain fault information to the recovery trigger.
  • the recovery trigger is set to determine whether to enable protection or recovery of the layer after receiving the inter-domain failure information of the service layer.
  • the recovery trigger is located at the first node of the client layer LSP. You need to decide which mode to start to restore the service according to the protection and recovery type configured in this layer. When dynamic rerouting is started, the corresponding routing policy is generated and sent to the route calculation unit according to the inter-domain fault information, and then the result returned by the route calculation unit is used.
  • the first node of the upper LSP can consider how to recover the service from a more comprehensive perspective because it has more comprehensive routing topology information and end-to-end configuration.
  • 5 is a schematic diagram of a multi-layer multi-domain network service layer three-layer connection according to an embodiment of the present invention.
  • the network shown in FIG. 5 is composed of four AS domains, where AS1 and AS2 are PTN networks, and AS3 is an optical transport network. (Optical Transport Network, OTN), AS4 is an SDH network.
  • the end-to-end LSP connection is from node A of AS1 to node N of AS2, which is LSP1.
  • LSP2 There are two service layer LSPs, one layer is the border node B of AS1 to the border node L of AS2, which is LSP2, and the layer is the intra-domain LSP in the OTN network AS3, and the E node from AS3 to the H node of AS3 is LSP3;
  • LSP2 It is the service layer LSP of LSP1 and also the client layer LSP of LSP3.
  • the method for establishing a Layer 3 LSP is not specifically described in the embodiment of the present invention.
  • the LSP1 configuration is dynamically restored
  • LSP2 is the unprotected and unrecoverable LSP
  • the LSP3 configuration is dynamically restored.
  • the delay of the LSP2 head node is set to T, the end-to-end LSP, and the delay of the LSP1 head node. Set to 2T.
  • the first node of LSP2 records the destination address of the inter-domain fault transmission as the IP address of the first node of the upper layer LSP, that is, the IP address of the node A, and records the inter-domain between the first node E of LSP3.
  • the destination address of the fault is the IP address of the first node of the upper LSP, that is, the IP address of the B node.
  • the Layer 3 LSP in the embodiment of the present invention uses the client layer to dynamically trigger the service layer LSP as an example.
  • FIG. 6 is a schematic diagram of an example 1 of post-fault dynamic coordination of a multi-layer multi-domain network service layer according to an embodiment of the present invention.
  • the neighboring client layer LSP is not configured with protection and recovery attributes, and the fault continues to be transmitted to the end-to-end head node; when a fiber breakage occurs between the OTN network EH (fault 1),
  • LSP3 After receiving the SF fault, LSP3 starts the optimized re-routing and finds a recovery connection in the local area of this layer, as shown in Figure 6.
  • the first node E of LSP3 detects no inter-domain failure.
  • the EF fails again (fault 2).
  • LSP3 cannot find a new recovery connection in the local area.
  • the first node E of LSP3 An interdomain failure was detected.
  • the E-node generates inter-domain fault information: E-node, node fault, fill in the Notify message, fill in the IP address of the B-node into notify, and send the notify message.
  • the first node of each client layer also receives the fault.
  • the first node of each client layer starts the delay timer according to the configured delay, and the start time of the B node is T, and the node A starts.
  • the timer is 2T.
  • the node B After receiving the inter-domain fault information sent by E, the node B terminates the layer delay timer, changes the Notify message, fills in the IP address of the node A into the notify, and sends the notify message.
  • the end-to-end LSP first node A terminates the local layer delay timer, and transmits the E-node fault information to the route calculation unit.
  • the AS4 domain recovery After receiving the return result of the route calculation unit, the AS4 domain recovery is established. Connect, switch the service to the recovery connection. It is not within the scope of the present invention to recover the process of how the connection triggers the establishment of a multi-layer LSP.
  • the E-node After the fault in the AS3 domain disappears, the E-node generates a notification message that the inter-domain fault disappears and is delivered upstream. After receiving the information that the inter-domain failure disappears, the A node decides to switch the service back to the original connection.
  • 7 is a schematic diagram of a second example of dynamic coordination of a multi-layer multi-domain network service layer after a fault according to an embodiment of the present invention. As shown in FIG. 7, after a service layer fails, dynamic remapping is not configured in the immediately adjacent client layer LSP. The fault is recovered at this level. When a fiber breakage occurs between the EH and the EF of the OTN network, a new recovery connection cannot be found in the local area of the local layer. At this time, the first node E of the LSP3 detects an inter-domain fault.
  • the E node generates inter-domain fault information: E node, node fault, and the IP address of the B node is filled in the notify, and the notify message is sent out.
  • the B-node After receiving the inter-domain fault information sent by the E, the B-node detects that the LSP of the local layer is configured with dynamic re-routing, and transmits the E-node fault information to the route calculation unit. After receiving the result of the route calculation, the node establishes the SDH AS4 domain. The recovery connection, the business is switched to this recovery connection, the inter-domain failure is not continued to upload.
  • the E-node generates a notification message that the inter-domain fault disappears and is delivered upstream.
  • the service layer LSP determines that the service layer LSP protection or recovery fails, and sends inter-domain fault information to the upper layer LSP of the service layer LSP, indicating that the service LSP protection or recovery fails. .
  • the client layer can dynamically and timely know whether the service layer protection and recovery is successful.
  • the service layer protection and recovery fails, the service connection is protected or restored in time, which shortens the end-to-end service fault. Time has improved network survivability.
  • modules or steps of the present invention described above can be implemented with a general purpose computing device, which can be centralized on a single computing device, or distributed. Alternatively, on a network of computing devices, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, The steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into individual integrated circuit modules, or a plurality of the modules or steps may be implemented as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the present invention enables the client layer LSP to know the protection or recovery failure of the service layer LSP in time, and protects or restores the service layer LSP in time, shortens the end-to-end service interruption time, and improves the network. Survivability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种域间故障信息的发送方法及装置，其中，该方法包括：服务层LSP确定所述服务层LSP保护或恢复失效；服务层LSP向该服务层的客户层发送域间故障信息，其中，域间故障信息用于指示服务层LSP保护或恢复失效；其中，服务层LSP与客户层LSP属于不同的AS域。通过本发明，使得客户层LSP及时获知服务层LSP保护或恢复失败，以使客户层LSP及时对服务层LSP进行保护或恢复，缩短了端到端业务损断的时间，提高了网络生存性。

Description

域间故障信息的发送方法及装置
技术领域
本发明涉及通信领域， 具体而言， 涉及一种域间故障信息的发送方法及 装置。
背景技术
在通讯网络中， 存在各种承载设备， 例如， 骨干网设备包括密集型光波 复用 （ Dense Wavelength Division Multiplexing, 简称为 DWDM )类型设备、 分组传送网 （Packet Transfer Network, 简称为 PTN )设备、 同步数字体系 ( Synchronous Digital Hierarchy, 简称为 SDH )设备、 路由器等设备接入骨干 网中。 在这些混合设备的网络中， 不同的设备属于不同的层， 如 DWDM设 备网络属于服务层， PTN设备网络属于客户层。 同时， 由于通讯网络位于不 同的区域， 又分属于不同的自治系统（ Autonomous System , AS ) (也称为 AS域） 。 在这些多层多域的网络中， 端到端的客户业务需要穿越各网络， 各个网 络可能属于不同的层、不同的 AS域。在互联网工程任务组（ Internet Engineering Task Force，简称为 IETF )标准中，不同层的网络中，使用 FA-LSP ( Forwarding Adjacency-LSP )技术建立服务层的连接供客户层使用。 为了提高设备的生存 性， 在不同的网络中， 运营商可能都会部署保护和恢复， 当某处网络故障时， 不仅会触发本层的保护与恢复， 同时由于告警的传递， 客户层业务也收到告 警， 因此， 需要考虑客户层与服务层网络保护与恢复如何进行协调， 来保证 业务的可靠恢复， 又不会损断多次。 当前的运营网络中， 一般使用静态协调的方法， 即在不同层中启动延时 定时器来协调。 在这种方式下， 客户层无法获知服务层的保护与恢复是否失 败， 当延时定时器到后， 通过再次查找客户层是否存在告警来决定是否启动 保护和恢复。 因此， 当服务层的保护与恢复失效的情况下， 客户层一直在等 待延时， 导致业务损断时间加长。 同时， 目前网络中多在同种设备中应用层 间协调， 跨域保护与恢复的动态协调还处于研究阶段。 针对相关技术中上述的问题， 目前尚未提出有效的解决方案。
发明内容
针对相关技术中客户层无法及时获知服务层的保护与恢复是否失败， 而 导致业务损断时间加长的问题， 本发明提供了一种域间故障信息的发送方法 及装置， 以至少解决上述问题。 根据本发明的一个方面， 提供了一种域间故障信息的发送方法， 包括： 服务层标签交换路径 LSP确定所述服务层 LSP保护或恢复失效； 以 及 所述服务层 LSP向该服务层 LSP的客户层 LSP发送域间故障信息， 其中， 所述域间故障信息用于指示所述服务层 LSP保护或恢复失效； 其中， 所述 Λ良务层 LSP与所述客户层 LSP属于不同的自治系统 AS 域。 在所述服务层 LSP向该服务层 LSP的客户层 LSP发送域间故障信息 的步骤之后， 该方法还包括： 所述客户层 LSP对所述服务层 LSP进行保护或恢复； 以及 所述客户层 LSP对所述服务层 LSP的保护或恢复失败时， 所述客户 层 LSP继续向该客户层 LSP的客户层 LSP发送所述域间故障信息。 所述客户层 LSP对所述服务层 LSP进行保护或恢复的步骤包括： 所述客户层 LSP根据所述域间故障信息建立新的连接， 并将所述客 户层 LSP的业务切换到所述新的连接。 该方法还包括： 在所述域间故障信息指示的故障消失时，所述服务层 LSP向所述客户层 LSP发送域间故障消失消息， 其中， 所述域间故障消 失消息用于指示所述域间故障信息指示的故障消失。 在服务层 LSP向所述客户层 LSP发送域间故障消失消息的步骤之后， 该方法还包括： 所述客户层 LSP接收所述域间故障消失消息， 并依据预先配置判断 是否将所述客户层 LSP的业务切回到所述服务层 LSP的连接上，如果是， 则将所述客户层 LSP的业务切回到所述服务层 LSP的连接上。 服务层 LSP确定所述服务层 LSP保护或恢复失效的步骤包括： 服务层 LSP的连接发生故障， 或所述服务层 LSP接收到域间故障信 息时， 所述服务层 LSP对所述服务层 LSP进行保护或恢复， 在所述服务 层 LSP的保护或恢复失败时， 所述服务层 LSP确定所述服务层 LSP保护 或恢复失效。 该方法还包括： 服务层 LSP的连接发生故障时， 所述客户层 LSP开启预先配置的延 时定时器； 以及 如果所述客户层 LSP在所述延时定时器超时前接收到所述服务层 LSP发送的所述域间故障信息， 所述客户层 LSP停止所述延时定时器， 并对所述服务层 LSP进行保护或恢复。 服务层 LSP向该服务层 LSP的客户层 LSP发送域间故障信息的步骤 包括： 第一节点向第二节点发送所述域间故障信息，其中，所述第一节点为 所述 Λ良务层 LSP的首节点， 所述第二节点为所述客户层 LSP的首节点。 域间故障信息包括： 故障的位置和 /或故障类型。 根据本发明的另一方面，提供了一种域间故障信息的发送装置，位于 服务层 LSP的首节点， 其特征在于， 所述装置包括： 确定模块， 其设置成确定服务层 LSP保护或恢复失效； 以及 发送模块， 其设置成向该服务层 LSP的客户层 LSP发送域间故障信 息， 其中， 所述域间故障信息用于指示所述服务层 LSP保护或恢复失效； 其中， 所述 Λ良务层 LSP与所述客户层 LSP属于不同的自治系统 AS 域。 该装置还包括保护与恢复模块， 其设置成在所述服务层 LSP的连接 发生故障，或所述服务层 LSP接收到域间故障信息时，对所述服务层 LSP 进行保护或恢复。 确定模块是设置成在所述保护与恢复模块对所述服务层 LSP的保护 或恢复失败时， 确定所述服务层 LSP保护或恢复失效。 通过本发明， 服务层 LSP确定服务层 LSP保护或恢复失效， 服务层 LSP 向该服务层 LSP的客户层 LSP发送域间故障信息，指示服务层 LSP保护或恢 复失效， 使得客户层 LSP及时获知服务层 LSP保护或恢复失败， 并及时对服 务层 LSP进行保护或恢复， 缩短了端到端业务损断的时间， 提高了网络生存 性。
附图概述
此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中： 图 1是根据本发明实施例的域间故障信息的发送方法的流程图； 图 2是根据本发明实施例的域间故障信息的发送装置； 图 3是根据本发明实施例的多层多域网络保护与恢复动态协调的方法的 流程图； 图 4是根据本发明具体实施例的多层多域网络中动态协调框架系统的示 意图； 图 5是根据本发明实施例的多层多域网络服务层三层连接的示意图； 图 6是根据本发明实施例的多层多域网络服务层故障后动态协调示例一 的示意图； 图 7是根据本发明实施例的多层多域网络服务层故障后动态协调示例二 的示意图。
本发明的较佳实施方式
下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互组合。 针对多层多域网络中， 客户层无法及时获知服务层的保护与恢复是否失 败， 而导致业务瞬断时间加长的问题， 本发明实施例提供了一种域间故障信 息的发送方法及装置， 通过实时传递域间故障信息， 使得客户层能够动态实 时获知服务层保护与恢复是否成功， 在服务层保护与恢复失败时， 及时对业 务连接进行保护或恢复， 缩短了端到端业务损断的时间， 提高了网络生存性。 实施例一 根据本发明实施例， 提供了一种域间故障信息的发送方法， 实现在下层 (服务层） LSP保护或恢复失效时， 向上层（客户层） LSP发送域间故障信 息， 以使上层 LSP根据域间故障信息对业务连接进行保护或恢复。 图 1是根据本发明实施例的域间故障信息的发送方法的流程图， 如图 1 所示， 该方法可以包括步骤 S102至步骤 S104: 步骤 S102, 服务层 LSP确定服务层 LSP保护或恢复失效； 步骤 S104,服务层 LSP向该服务层的客户层 LSP发送域间故障信息，其 中， 域间故障信息用于指示服务层 LSP保护或恢复失效， 服务层 LSP与所述 客户层 LSP属于不同的 AS域。 通过本发明实施例， 服务层 LSP确定服务层 LSP保护或恢复失效， 向该 服务层 LSP的客户层 LSP发送域间故障信息，指示服务层 LSP保护或恢复失 效， 使得客户层 LSP及时获知服务层 LSP保护或恢复失败， 以使客户层 LSP 及时对服务层 LSP进行保护或恢复， 缩短了端到端业务损断的时间， 提高了 网络生存' 1·生。 在本发明实施例中， 服务层网络出现故障时， 或服务层 LSP接收到域间 故障信息时， 服务层 LSP可以启动保护或恢复功能， 对服务层 LSP进行保护 或恢复，在保护或恢复失败时，服务层 LSP确定服务层 LSP保护或恢复失效。 在确定保护或恢复失效时， 可以向上层 LSP (即该服务层 LSP的客户层 LSP ) 发送域间故障信息， 指示服务层 LSP保护或恢复失效， 使得上层 LSP及时获 取下层 LSP保护或恢复失效， 并对下层 LSP进行保护或恢复， 由于上层 LSP 知晓更全面的链路信息， 从而能够更快的对下层 LSP进行保护或恢复。 在本 发明实施例的一个优选实施方式中， 域间故障信息可以包括故障的位置和故 障的类型等信息。 在本发明实施例的一个优选实施方式中，服务层 LSP向客户层 LSP发送 域间故障信息之后， 客户层 LSP可以对服务层 LSP进行保护或恢复。 在客户 层 LSP对服务层 LSP保护或恢复失败时， 客户层 LSP可以向该客户层 LSP 的上层 LSP (该客户层对与其上层 LSP来说， 作为服务层为上层 LSP提供服 务）发送域间故障信息。 通过本优选实方式， 在对下层 LSP保护或恢复失败 时， 向多层多域网络中的上层 LSP传递域间故障信息， 使得上层 LSP能够及 时获知保护或恢复失败， 从而降低端到端业务的损断时间， 提高业务的可靠 性。 进一步， 客户层 LSP对服务层 LSP进行保护或恢复时， 可以根据域间故 障信息建立新的连接， 并将客户层 LSP的业务切换到新建立的连接。 例如， 当客户层 LSP配置为优化重路由时， 客户层 LSP可以根据域间故障信息生成 恢复路径，并将客户层 LSP的端到端业务切换到新建的连接上。在客户层 LPS 将业务切换到新的连接上之后， 可以停止向该客户层 LSP的上层 LSP发送域 间故障信息。 在本发明实施例的一个优选实施方式中， 在域间故障信息指示的故障消 失时， 服务层 LSP可以向客户层 LSP发送域间故障消失消息， 其中， 域间故 障消失消息用于指示域间故障信息指示的故障消失。 上层 LSP接收到域间故 障消失消息后， 可以根据实际需要动态选择该层 LSP业务的连接。 优选地， 服务层 LSP向客户层 LSP发送域间故障消失消息之后， 其中， 域间故障消失 消息用于指示域间故障信息指示的故障消失。 客户层 LSP可以接收域间故障 消失消息， 并依据预先配置判断是否将客户层 LSP的业务切回到服务层 LSP 的连接上， 如果是， 则将客户层 LSP的业务切回到服务层 LSP的连接上。 相关技术中， 为了提高设备的生存性， 可以在不同的网络中部署保护和 恢复， 当某处网络故障时， 不仅会触发本层的保护与恢复， 由于告警的传递， 客户层业务也收到告警， 客户层开启延时计时器， 当延时定时器到后， 通过 再次查找客户层是否存在告警来决定是否启动保护和恢复。 当服务层的保护 与恢复失效的情况下， 客户层一直在等待延时， 导致业务损断时间加长。 在 本发明实施例的一个优选实施方式中， 为了兼容延时定时器的方法， 服务层 网络发生故障时， 第二节点可以开启预先配置的延时定时器， 其中， 第二节 点为客户层 LSP的首节点； 如果客户层 LSP在延时定时器超时前接收到服务 层 LSP发送的域间故障信息， 则第二节点可以停止延时定时器， 并对服务层 LSP进行保护或恢复。
LSP连接上包含有多个节点， 当 LSP连接上的一个节点出现故障时， 可 以由其他节点向上层 LSP发送域间故障消息， 在本发明实施例的一个优选实 施方式中， 服务层 LSP向客户层 LSP发送域间故障信息时， 可以通过第一节 点向第二节点发送域间故障信息， 其中， 第一节点为服务层 LSP的首节点， 第二节点为客户层 LSP的首节点。 在实际应用中， 也可以通过节点间的传递 将域间故障信息发送至上层 LSP的节点， 由相应的节点进行处理。 根据本发明实施例， 还提供了一种域间故障信息的发送装置， 用以实现 本发明实施例的上述方法， 图 2是根据本发明实施例的域间故障信息的发送装置， 如图 2所示， 该 装置主要包括： 确定模块 10和发送模块 20。 其中， 确定模块 10设置成确定 服务层 LSP保护或恢复失效； 发送模块 20与确定模块 10相耦合， 并设置成 向该服务层 LSP的客户层 LSP发送域间故障信息， 其中， 客户层 LSP为服务 层 LSP的上层 LSP, 域间故障信息用于指示服务层 LSP保护或恢复失效， 服 务层 LSP与客户层 LSP属于不同的 AS域。 通过本发明实施例，确定模块 10确定服务层 LSP保护或恢复失效，发送 模块 20向服务层 LSP的上层（客户层） LSP发送域间故障信息， 指示服务层 LSP保护或恢复失效，使得客户层 LSP及时获知服务层 LSP保护或恢复失败， 并及时对服务层 LSP进行保护或恢复， 缩短了端到端业务损断的时间， 提高 了网络生存性。 在本发明实施例的一个优选实施方式中，确定模块 10可以按照以下方式 确定服务层 LSP保护或恢复失效:服务层 LSP的连接发生故障，或服务层 LSP 接收到域间故障信息时， 由保护与恢复模块对服务层 LSP进行保护或恢复， 在服务层 LSP的保护或恢复失败时， 确定模块 10确定服务层 LSP保护或恢 复失效。 优选地， 该装置还可以包括： 保护与恢复模块， 其设置成在服务层 LSP的连接发生故障， 或服务层 LSP接收到域间故障信息时， 对服务层 LSP 进行保护或恢复。 实施例二 根据本发明实施例， 提供了一种多层多域网络保护与恢复动态协调的系 统， 同时基于此系统， 提供了一种多层多域网络保护与恢复动态协调的方法， 通过实时传递域间故障信息， 解决了多层多域网络中， 客户层无法实时获知 服务层保护与恢复是否成功的问题， 缩短了端到端业务损断的时间， 提高了 网络生存' 1·生。 本优选实施例的多层多域网络保护与恢复动态协调的方法， 包括以下几 个步骤 (步骤 1至步骤 3 ) ： 步骤 1 , 当服务层网络发生故障后， 在本网络内部首节点启动域间故障 检测， 检测并判定本层 LSP保护或恢复是否失效； 步骤 2, 服务层首节点判定本层保护与恢复失效后， 生成域间故障信息， 并将域间故障信息沿 LSP路径向上游传递； 步骤 3 , 上层网络 LSP (客户层）的首节点检测到域间故障时， 判断本层 是否需要启动保护或恢复， 当保护或恢复成功， 则终止域间故障信息的传递； 当保护或恢复失败时， 继续向上层传递域间故障信息。 在上述步骤中， 为了兼容传统的静态保护协调机制， 在步骤 1 中， 客户 层首节点检测到 LSP故障时， 也可以同时启动定时器； 在步骤 3中， 客户层 的首节点收到域间故障时， 终止在步骤 1中启动的定时器。 上述步骤 1和步骤 2相当于本发明上述实施例的步骤 S102和步骤 S104, 实现在本层保护或恢复失败时， 将域间故障信息发送至上层 LSP。 本优选实施例的多层多域网络保护与恢复动态协调的系统， 主要包括： 网络检测器（相当于本发明上述实施例的确定模块 10 )，位于域边界节点上， 其设置成在发生故障后， 检测本域内的保护或恢复是否失效； 域间故障信息 处理器（相当于本发明上述实施例的发送模块 20 ) ， 位于域边界节点上， 其 设置成生成保护与恢复失效后的故障信息， 并向上层 LSP传递生成的域间故 障信息； 恢复触发器 （相当于本发明上述实施例的保护与恢复模块） , 位于 域边界节点上， 其设置成在接收到域间故障信息后， 决策进行客户层的保护 与恢复。 通过本优选实施例， 当服务层网络保护恢复失效后， 客户层可以不用等 待延时定时器超时， 在接收到域间故障信息后， 立即启动客户层的保护与恢 复， 缩短了故障损断的时间， 充分利用网络资源， 提高了承载网络的生存性。 实施例三 通讯网络中存在多种承载设备， 每种设备分属不同的层。 而这些设备可 能处于不同的地域， 因此分布在不同的路由域中。 为了解决跨域端到端 LSP 建立的问题， IETF发布了一系列的标准对 RSVP-TE进行了扩展， 其中有两 种方案， 一种为分层 LSP ( Hierarchy-LSP, 简称为 H-LSP ) , —种为缝接 LSP ( Stitching-LSP, 简称为 S-LSP ) 。 1 ) H-LSP, 通过 Hierachy方式创建的 LSP, 即 H-LSP ( RFC4206将它定 义为 FA-LSP ) , 可以在它的上层（客户层）形成一条 TE链路； 上层 LSP的 建立可以使用该 TE链路进行路由计算。 H-LSP作为服务层可以给多条客户层 LSP使用。
2 ) S-LSP, 通过 Stiching方式创建的 LSP, 即 S-LSP, 可以在同一层泛洪 为一条 LSP, 缝接技术要求各个 LSP段（ LSP segment )的接口交换能力必须 相同。 通过缝接建立跨域端到端 LSP连接时， S-LSP最多只能被一条 LSP缝 接。
H-LSP、 S-LSP均可以动态触发或者预先建立成功。 使用上述技术时， 端到端 LSP上使用了不同的 LSP, 不同 LSP上可能均 配置保护与恢复。 在本发明具体实施例中以 H-LSP为例说明， 但本发明实施 例不限于此种模式。 图 3是根据本发明实施例的多层多域网络保护与恢复动态协调的方法的 流程图， 如图 3所示， 该方法可以包括步骤 S302至步骤 S312。 步骤 S302, 检测域间故障。 在域间故障检测之前， 上层 LSP 在建立时， Path 消息中需要携带
NOTIFY— REQUEST对象，此对象中记录了上层 LSP首节点 IP地址。 FA-LSP 的首节点接收到上层 Path消息后， 需要记录此 IP地址，作为发送域间故障信 息的目的地址。 配置了保护与恢复的各层 LSP需要设置合理的延时定时器。 最底层的上 层网络延时定时器设置为 T1 , 第二层上层网络延时定时器需要设置为 2*T1 , 第三层上层网络延时定时器设置为 3*Τ1 , 依次类推， 设置完毕各服务层的延 时定时器。 当作为服务层的 LSP发生故障后， 首节点需要检测并判断本层的保护或 恢复是否失败； 若失效， 进行后续的处理； 步骤 S304, 服务层 LSP的首节点获知本域内保护或恢复失败后， 生成故 障信息。 该故障信息可以包括： 故障位置， 故障类型。 故障位置包括 FA-LSP故障， FA-LSP首节点故障， 故障类型为 FA-LSP 发生的物理故障类型。 FA-LSP故障是指， FA-LSP本身没有配置保护及恢复 属性。 FA-LSP首节点故障是指， FA-LSP本身配置了保护或恢复属性， 但因 资源缺乏等原因导致保护或恢复失败。 步骤 S306, 域间故障信息生成。 在域间故障的发生点， 即保护或恢复失 效的 FA-LSP 的首节点， 将生成的域间故障信息设置到域间传递消息中， 填 充的信息包括故障类型、故障位置， 并将目的地址设置为步骤 S302中保存的 IP地址， 将域间故障信息发送出去。 步骤 S308, 上层 LSP首节点， 接收到域间故障信息后， 终止本层启动的 延时定时器， 判断是否能启动保护与恢复。 当保护与恢复成功后， 则终止域 间故障信息的传递； 当保护与恢复失败后， 重复步骤 S304和步骤 S306, 继 续生成域间故障信息并向上游传递域间故障信息。 步骤 S310, 端到端 LSP的首节点收到域间故障信息后， 终止本层启动的 延时定时器， 根据端到端 LSP配置的保护或恢复， 从全局恢复端到端业务。 在上述步骤中， 当某层 LSP配置为优化重路由时， 首节点需要将故障信 息传递给路由计算单元， 如 PCE, 并接收路由计算单元的算路结果， 生成恢 复路径， 将端到端业务切换到新建的连接上。 优选地， 本发明实施例的方法还可以包括步骤 S312。 步骤 S312, 故障消失后， 步骤 S304中的首节点需要生成域间故障消失 的信息， 向上游传递， 传递的路径及方法与故障信息相同。 图 4是根据本发明具体实施例的多层多域网络中动态协调框架系统的示 意图， 如图 4所示， 该系统主要包括： 网络检测器（相当于本发明上述实施 例的确定模块 10 ) 、 域间故障信息处理器（相当于本发明上述实施例的发送 模块 20 ) 、 恢复触发器（相当于本发明上述实施例的保护与恢复模块） 。 上 述 3个模块均位于域边界节点上，共同协调完成域间保护与恢复的动态协调。 网络检测器设置成在本层发生故障时， 或者当本层的故障是由服务层故 障引起时， 检测本层的保护或者恢复是否失效； 在同一层中， 可能会配置多 种保护与恢复方法， 比如配置本层的端到端保护和动态重路由， 配置 MPLS FRR和动态重路由等多种保护业务的方法， 网络触发器在决策时， 需要考虑 同层配置的所有保护与恢复是否均已启动并失效。 当检测到本层无法恢复业 务时， 将信息传递给域间故障信息处理器。 同时， 网络检测器还设置成搜集 上层 LSP (服务层 FA-LSP )首节点的信息， 即 IP地址， 此信息是在上层 LSP 触发本层 LSP建立时传递下来的。 域间故障信息处理器设置成在接收到网络检测器发送的本层保护与恢复 失效信息后， 生成域间故障信息， 故障信息可以包括故障位置以及故障类型 等。 故障信息生成后， 可以在 notify消息中设置故障类型、 故障位置、 目的 地址后， 发送出去。 域间故障信息处理器还可以从协议层直接收服务层发送 的域间故障信息， 并可以将接收到的域间故障信息传递给恢复触发器。 恢复触发器设置成在接收到服务层的域间故障信息后， 判断是否启动本 层的保护或者恢复。 恢复触发器位于客户层 LSP的首节点， 需要根据本层配 置的保护及恢复类型， 决定启动何种方式恢复业务。 当启动动态重路由时， 需要根据域间故障信息后， 生成对应的路由策略传递给路由计算单元， 然后 根据路由计算单元返回的结果。 上层 LSP的首节点因为拥有更全面的路由拓 朴信息及端到端的配置， 可以从更全面的角度考虑如何恢复业务。 图 5是根据本发明实施例的多层多域网络服务层三层连接的示意图， 如 图 5所示的网络由四个 AS域组成， 其中， AS1和 AS2为 PTN网络， AS3为 光传送网络（Optical Transport Network, OTN ) , AS4为 SDH网络。 端到端 的 LSP连接从 AS1的 A节点到 AS2的 N节点，为 LSP1。有两层服务层 LSP, 一层为 AS1的边界节点 B到 AS2的边界节点 L, 为 LSP2, —层为 OTN网络 AS3内的域内 LSP, 从 AS3的 E节点到 AS3的 H节点， 为 LSP3; 对于 LSP2 来说， 是 LSP1的服务层 LSP, 同时也是 LSP3的客户层 LSP。 3层 LSP的建 立方法不在本发明实施例中进行具体描述。 在如图 5所述的网路中， LSP1配置动态恢复， LSP2为无保护无恢复的 LSP, LSP3配置动态恢复； LSP2首节点的延时设置为 T, 端到端 LSP、 LSP1 首节点的延时设置为 2T。 在三层 LSP建立的过程中， 在 LSP2的首节点 Β记录了域间故障发送的 目的地址为上层 LSP的首节点 IP地址， 即 A节点的 IP地址， 在 LSP3的首 节点 E记录了域间故障发送的目的地址为上层 LSP的首节点 IP地址， 即 B 节点的 IP地址。 本发明实施例中的三层 LSP, 以客户层动态触发服务层 LSP为例， 当服 务层 LSP预先已建立成功时， 上层 LSP在选取合适的服务层 LSP后， 同样需 要记录上层 LSP首节点的 IP地址。 图 6是根据本发明实施例的多层多域网络服务层故障后动态协调示例一 的示意图。 如图 6所示， 当服务层发生故障后， 紧邻的客户层 LSP没有配置 保护与恢复属性， 故障继续传递到端到端首节点； 当 OTN网络 E-H之间发生断纤故障（故障 1 ) , LSP3接收到 SF故障后， 启动优化重路由， 在本层本域内找到一条恢复连接， 如图 6示。 此时， LSP3 的首节点 E检测无域间故障。 当 OTN网络恢复连接路径上 E-F之间又发生断纤故障（故障 2 ) , LSP3 接收到第二个 SF故障后，在本层本域内无法找到新的恢复连接， 此时， LSP3 的首节点 E检测到发生域间故障。
E节点生成域间故障信息： E节点， 节点故障， 填写到 Notify消息中， 将 B节点的 IP地址填写到 notify中， 将 notify消息发送出去。 此时， 由于服务层发生故障， 导致各客户层首节点也会收到故障， 各客 户层首节点按照配置的延时启动延时定时器， B节点启动时间为 T的定时器， A节点启动时间为 2T的定时器。
B节点收到 E发送过来的域间故障信息后， 终止本层延时定时器， 更改 Notify消息中， 将 A节点的 IP地址填写到 notify中， 将 notify消息发送出去。 端到端 LSP首节点 A收到域间故障信息后， 终止本层延时定时器， 将 E 节点故障的信息传递给路由计算单元， 接收路由计算单元的返回结果后， 建 立经过 AS4域的恢复连接， 将业务切换到恢复连接上。 恢复连接如何触发多 层 LSP建立的过程， 不在本发明范围之内。 优选地， 当 AS3域中的故障消失后， E节点生成域间故障消失的通知消 息向上游传递。 A节点接收到域间故障消失的信息后， 决策将业务重新切换 回原来的连接。 图 7是根据本发明实施例的多层多域网络服务层故障后动态协调示例二 的示意图， 如图 7所示， 当服务层发生故障后， 紧邻的客户层 LSP没有配置 了动态重路由， 故障在这一层得到恢复。 当 OTN网络 E-H、 E-F之间均发生断纤故障， 在本层本域内无法找到新 的恢复连接， 此时， LSP3的首节点 E检测到发生域间故障。
E节点生成域间故障信息： E节点， 节点故障， B节点的 IP地址填写到 notify中， 将 notify消息发送出去。 B节点收到 E发送过来的域间故障信息后， 检测到本层的 LSP配置了动 态重路由，将 E节点故障信息传递给路由计算单元，接收路由计算的结果后， 建立了经过 SDH AS4域的恢复连接， 将业务切换到此条恢复连接上， 域间故 障不在继续上传。 优选地， 当 AS3域中的故障消失后， E节点生成域间故障消失的通知消 息向上游传递。 B 节点接收到域间故障消失的信息后， 决策将业务重新切换 回原来的连接， 并删除建立的恢复连接。 从以上的描述中， 可以看出， 本发明实现了如下技术效果： 服务层 LSP 确定服务层 LSP保护或恢复失效，向服务层 LSP的上层 LSP发送域间故障信 息， 指示服务 LSP保护或恢复失效。 通过实时传递域间故障信息， 使得客户 层能够动态实时获知服务层保护与恢复是否成功， 在服务层保护与恢复失败 时， 及时对业务连接进行保护或恢复， 缩短了端到端业务损断的时间， 提高 了网络生存性。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 并 且在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步骤， 或者 将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软件 结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。
工业实用性 与有关技术相比， 本发明使得客户层 LSP及时获知服务层 LSP保护或恢 复失败， 并及时对服务层 LSP进行保护或恢复， 缩短了端到端业务损断的时 间， 提高了网络生存性。

Claims

权 利 要 求 书
1. 一种域间故障信息的发送方法， 包括： 服务层标签交换路径 LSP确定所述服务层 LSP保护或恢复失效； 以 及 所述服务层 LSP向该服务层 LSP的客户层 LSP发送域间故障信息， 其中， 所述域间故障信息用于指示所述服务层 LSP保护或恢复失效； 其中， 所述 Λ良务层 LSP与所述客户层 LSP属于不同的自治系统 AS 域。
2. 根据权利要求 1所述的方法， 其在所述服务层 LSP向该服务层 LSP的客 户层 LSP发送域间故障信息的步骤之后， 还包括： 所述客户层 LSP对所述服务层 LSP进行保护或恢复； 以及 所述客户层 LSP对所述服务层 LSP的保护或恢复失败时， 所述客户 层 LSP继续向该客户层 LSP的客户层 LSP发送所述域间故障信息。
3. 根据权利要求 2所述的方法， 其中， 所述客户层 LSP对所述服务层 LSP 进行保护或恢复的步骤包括： 所述客户层 LSP根据所述域间故障信息建立新的连接， 并将所述客 户层 LSP的业务切换到所述新的连接。
4. 根据权利要求 1所述的方法， 还包括： 在所述域间故障信息指示的故障消失时， 所述服务层 LSP向所述客 户层 LSP发送域间故障消失消息， 其中， 所述域间故障消失消息用于指 示所述域间故障信息指示的故障消失。
5. 根据权利要求 4所述的方法， 其在所述服务层 LSP向所述客户层 LSP发 送域间故障消失消息的步骤之后， 还包括： 所述客户层 LSP接收所述域间故障消失消息， 并依据预先配置判断 是否将所述客户层 LSP的业务切回到所述服务层 LSP的连接上，如果是， 则将所述客户层 LSP的业务切回到所述服务层 LSP的连接上。
6. 根据权利要求 1所述的方法， 其中， 服务层 LSP确定所述服务层 LSP保 护或恢复失效的步骤包括： 服务层 LSP的连接发生故障， 或所述服务层 LSP接收到域间故障信 息时， 所述服务层 LSP对所述服务层 LSP进行保护或恢复， 在所述服务 层 LSP的保护或恢复失败时， 所述服务层 LSP确定所述服务层 LSP保护 或恢复失效。
7. 根据权利要求 6所述的方法， 还包括： 服务层 LSP的连接发生故障时， 所述客户层 LSP开启预先配置的延 时定时器； 以及 如果所述客户层 LSP在所述延时定时器超时前接收到所述服务层
LSP发送的所述域间故障信息， 所述客户层 LSP停止所述延时定时器， 并对所述服务层 LSP进行保护或恢复。
8. 根据权利要求 1所述的方法， 其中， 所述服务层 LSP向该服务层 LSP的 客户层 LSP发送域间故障信息的步骤包括： 第一节点向第二节点发送所述域间故障信息，其中，所述第一节点为 所述 Λ良务层 LSP的首节点， 所述第二节点为所述客户层 LSP的首节点。
9. 根据权利要求 1至 8中任一项所述的方法， 其中， 所述域间故障信息包 括： 故障的位置和 /或故障类型。
10. 一种域间故障信息的发送装置，位于服务层 LSP的首节点，其特征在于， 所述装置包括： 确定模块， 其设置成确定服务层 LSP保护或恢复失效； 以及 发送模块， 其设置成向该服务层 LSP的客户层 LSP发送域间故障信 息， 其中， 所述域间故障信息用于指示所述服务层 LSP保护或恢复失效； 其中， 所述 Λ良务层 LSP与所述客户层 LSP属于不同的自治系统 AS 域。
11. 根据权利要求 10所述的装置， 还包括： 保护与恢复模块， 其设置成在所述服务层 LSP的连接发生故障， 或 所述服务层 LSP接收到域间故障信息时， 对所述服务层 LSP进行保护或 恢复。
12. 根据权利要求 11所述的装置， 其中， 所述确定模块是设置成在所述保护 与恢复模块对所述服务层 LSP 的保护或恢复失败时， 确定所述服务层 LSP保护或恢复失效。
PCT/CN2013/077069 2012-08-08 2013-06-09 域间故障信息的发送方法及装置 WO2013178098A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US14/416,341 US20150186202A1 (en) 2012-08-08 2013-06-09 Method and Device for Sending Inter-Domain Fault Information
EP13796745.1A EP2866394B1 (en) 2012-08-08 2013-06-09 Method and device for sending inter-domain fault information
BR112015002613A BR112015002613A2 (pt) 2012-08-08 2013-06-09 método e dispositivo para enviar informação de falha interdomínio.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210280557.6 2012-08-08
CN201210280557.6A CN103580904A (zh) 2012-08-08 2012-08-08 域间故障信息的发送方法及装置

Publications (1)

Publication Number Publication Date
WO2013178098A1 true WO2013178098A1 (zh) 2013-12-05

Family

ID=49672443

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/077069 WO2013178098A1 (zh) 2012-08-08 2013-06-09 域间故障信息的发送方法及装置

Country Status (5)

Country Link
US (1) US20150186202A1 (zh)
EP (1) EP2866394B1 (zh)
CN (1) CN103580904A (zh)
BR (1) BR112015002613A2 (zh)
WO (1) WO2013178098A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954160A (zh) * 2014-03-28 2015-09-30 中国移动通信集团内蒙古有限公司 一种实现承载网络多重保护的方法及承载网络

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104104600B (zh) * 2013-04-01 2018-03-09 华为技术有限公司 一种lsp建立的方法及网络设备
KR101727782B1 (ko) * 2013-12-06 2017-04-17 한국전자통신연구원 전송망의 자원 관리 방법 및 장치
GB2527798A (en) * 2014-07-02 2016-01-06 Ibm Synchronizing operations between regions when a network connection fails
CN104518960B (zh) 2014-12-05 2018-01-19 华为技术有限公司 一种延时回切的方法、设备及系统
US10880154B2 (en) * 2017-05-03 2020-12-29 At&T Intellectual Property I, L.P. Distinguishing between network- and device-based sources of service failures
CN110048944A (zh) * 2018-01-17 2019-07-23 中兴通讯股份有限公司 端到端重路由的方法及装置
CN116566805B (zh) * 2023-07-10 2023-09-26 中国人民解放军国防科技大学 一种面向体系容灾抗毁的节点跨域调度方法、装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101056203A (zh) * 2007-03-29 2007-10-17 华为技术有限公司 一种提高多层网络业务恢复性能的方法及装置
CN101715149A (zh) * 2009-07-21 2010-05-26 北京邮电大学 一种多层多域分布式光网络并行跨域故障恢复方法和装置
CN102546248A (zh) * 2011-12-30 2012-07-04 华为技术有限公司 多协议标签交换环境下精确定位故障位置的方法、装置及系统

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5768501A (en) * 1996-05-28 1998-06-16 Cabletron Systems Method and apparatus for inter-domain alarm correlation
US20030063613A1 (en) * 2001-09-28 2003-04-03 Carpini Walter Joseph Label switched communication network and system and method for path restoration
US8305882B2 (en) * 2001-12-18 2012-11-06 Horizon Technology Funding Company V Llc Methods, systems, and computer program products for detecting and/or correcting faults in a multiprotocol label switching network by using redundant paths between nodes
JP2003229888A (ja) * 2002-02-01 2003-08-15 Nec Corp ラベルスイッチングネットワーク及びそれに用いるラベルスイッチングパス設定方法
US7197008B1 (en) * 2002-07-05 2007-03-27 Atrica Israel Ltd. End-to-end notification of local protection using OAM protocol
US20050030951A1 (en) * 2003-08-06 2005-02-10 Christian Maciocco Reservation protocol signaling extensions for optical switched networks
DE10341336A1 (de) * 2003-09-08 2005-04-07 Siemens Ag Verfahren zur optimierten Deaktivierung von Inter-Domain Routen
DE102005025421A1 (de) * 2005-06-02 2006-12-07 Siemens Ag Verfahren zur Bereitstellung von Ersatzwegen als schnelle Reaktion auf den Ausfall eines Links zwischen zwei Routing-Domänen
CN100490390C (zh) * 2006-01-10 2009-05-20 华为技术有限公司 业务故障恢复方法
FR2921779B1 (fr) * 2007-09-28 2011-02-18 Alcatel Lucent Communication d'une information de risque dans un reseau multi-domaine
CN103843293B (zh) * 2011-09-27 2017-03-08 日本电气株式会社 通信系统、传输装置、通信装置、故障通知方法以及存储程序的非瞬时计算机可读介质
CN104348720B (zh) * 2013-07-25 2018-05-04 中兴通讯股份有限公司 一种多域路径计算失败的处理方法及路径计算单元
US10148578B2 (en) * 2014-10-17 2018-12-04 Ciena Corporation Optical and packet path computation and selection systems and methods

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101056203A (zh) * 2007-03-29 2007-10-17 华为技术有限公司 一种提高多层网络业务恢复性能的方法及装置
CN101715149A (zh) * 2009-07-21 2010-05-26 北京邮电大学 一种多层多域分布式光网络并行跨域故障恢复方法和装置
CN102546248A (zh) * 2011-12-30 2012-07-04 华为技术有限公司 多协议标签交换环境下精确定位故障位置的方法、装置及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954160A (zh) * 2014-03-28 2015-09-30 中国移动通信集团内蒙古有限公司 一种实现承载网络多重保护的方法及承载网络
CN104954160B (zh) * 2014-03-28 2019-02-26 中国移动通信集团内蒙古有限公司 一种实现承载网络多重保护的方法及承载网络

Also Published As

Publication number Publication date
EP2866394A4 (en) 2015-05-27
BR112015002613A2 (pt) 2017-07-04
CN103580904A (zh) 2014-02-12
EP2866394A1 (en) 2015-04-29
US20150186202A1 (en) 2015-07-02
EP2866394B1 (en) 2018-04-18

Similar Documents

Publication Publication Date Title
EP1845656B1 (en) A method for implementing master and backup transmission path
EP2866394B1 (en) Method and device for sending inter-domain fault information
US8842516B2 (en) Protection/restoration of MPLS networks
US8565098B2 (en) Method, device, and system for traffic switching in multi-protocol label switching traffic engineering
US20020171886A1 (en) Automatic control plane recovery for agile optical networks
EP2360880B1 (en) Optimized fast re-route in MPLS-TP ring topologies
US20120207017A1 (en) Recovery mechanism for point-to-multipoint traffic
EP1802985A2 (en) Efficient protection mechanisms for protecting multicast traffic in a ring topology network utilizing label switching protocols
WO2012037820A1 (zh) 多协议标签交换系统、节点设备及双向隧道的建立方法
WO2009105974A1 (zh) Mpls vpn中实现快速重路由的方法及设备
WO2011157130A2 (zh) 路径建立方法和装置
WO2008119294A1 (fr) Procédé et matériel de restauration du commerce en réseau
EP2652918B1 (en) Segment recovery in connection-oriented network
WO2012016458A1 (zh) 用于二层虚拟专用网络的数据传输方法和装置
WO2013040940A1 (zh) 环网的保护方法及装置
EP2892180B1 (en) Service traffic protection method and apparatus
WO2016188025A1 (zh) 一种点到多点隧道的保护方法和装置
WO2008040254A1 (fr) Procédé de traitement destiné aux informations de liaison d'ingénierie de trafic
US8462617B2 (en) Method for relieving failure, and packet communication device
WO2014079010A1 (zh) 业务保护方法、设备及系统
CN111083033B (zh) 基于多协议标签交换协议的三层虚拟专用网
JP5378239B2 (ja) 情報伝送システム、情報伝送方法および中継スイッチ装置
Nagarajan et al. A fault‐tolerant MPLS‐based control and communication network for the Lucent LambdaRouter
CN116527571A (zh) 一种跨地域广域网二层透明虚电路数据传输系统
KR20030074944A (ko) 광버스트스위칭기반 광 인터넷에서의 오류 보호/복구방법

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: 13796745

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2013796745

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 14416341

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112015002613

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112015002613

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20150206

REG Reference to national code

Ref country code: BR

Ref legal event code: B01E

Ref document number: 112015002613

Country of ref document: BR

Kind code of ref document: A2

Free format text: APRESENTE A TRADUCAO SIMPLES DA FOLHA DE ROSTO DA CERTIDAO DE DEPOSITO DA PRIORIDADE REIVINDICADA; OU DECLARACAO DE QUE OS DADOS DO PEDIDO INTERNACIONAL ESTAO FIELMENTE CONTIDOS NA PRIORIDADE REIVINDICADA, CONTENDO TODOS OS DADOS IDENTIFICADORES (NUMERO DA PRIORIDADE, DATA, DEPOSITANTE E INVENTORES), CONFORME O PARAGRAFO UNICO DO ART. 25 DA RESOLUCAO 77/2013. CABE SALIENTAR NAO FOI POSSIVEL INDIVIDUALIZAR OS TITULARES DA CITADA PRIORIDADE, INFORMACAO NECESSARIA PARA O EXAME DA CESSAO DO DOCUMENTO DE PRIORIDADE, SE FOR O CASO. IDENTIFIQUE O SIGNATARIO DA PETICAO NO020150002099, UMA VEZ QUE NAO E POSSIVEL IDENTIFICAR O NOME DO RESPONSAVEL PELA ASSINATURA DO FORMULARIO, NAO SENDO POSSIVEL DETER

ENPW Started to enter national phase and was withdrawn or failed for other reasons

Ref document number: 112015002613

Country of ref document: BR

Kind code of ref document: A2

Free format text: PEDIDO RETIRADO EM RELACAO AO BRASIL POR NAO ATENDER AS DETERMINACOES REFERENTES A ENTRADA DO PEDIDO NA FASE NACIONAL E POR NAO CUMPRIMENTO DA EXIGENCIA FORMULADA NA RPI NO 2535.