WO2017008656A1 - 一种实现业务回溯的方法和装置 - Google Patents

一种实现业务回溯的方法和装置 Download PDF

Info

Publication number
WO2017008656A1
WO2017008656A1 PCT/CN2016/088373 CN2016088373W WO2017008656A1 WO 2017008656 A1 WO2017008656 A1 WO 2017008656A1 CN 2016088373 W CN2016088373 W CN 2016088373W WO 2017008656 A1 WO2017008656 A1 WO 2017008656A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
backtracking
snc
information
route
Prior art date
Application number
PCT/CN2016/088373
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 EP16823803.8A priority Critical patent/EP3322158A4/en
Publication of WO2017008656A1 publication Critical patent/WO2017008656A1/zh

Links

Images

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/42—Centralised routing
    • 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
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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

Definitions

  • This article relates to, but is not limited to, the field of optical communication technology, and in particular relates to a method and apparatus for implementing service backtracking.
  • SDN Software Defined Network
  • PTN Packet Transport Network
  • OTN Optical Transport Network
  • the SDN research based on optical network is still in the initial stage.
  • the failure of this service can only be determined.
  • the optical network devices are in different shapes, it is common to issue device command failures.
  • service back-tracking When the actual configuration of the network node fails, the method of avoiding the automatic re-routing of the faulty network node by means of the protocol is usually called service back-tracking.
  • GMPLS Generalized Multiprotocol Label Switching, Under the general multi-protocol label switching architecture, the service backtracking includes the following steps:
  • a path (path) message is sent from the ingress to the downstream (ingress) to apply for the label and the instruction is sent to the device.
  • the Resv message is hop-by-hop from the tail node.
  • the upstream node the received node checks the execution result of the instruction; when the Resv message is delivered to the intermediate node (Transit), it detects that the instruction sent by the intermediate node to the device fails, and the ResvErr (Reserved Request Error) message is executed.
  • the error information is passed to the tail node; the tail node notifies the upstream that the establishment process fails through the PathErr (Path Error) message, and the error information is transmitted back to the first node one by one through the PathErr message, and the node that receives the PathErr message needs to be released.
  • the locally applied tag and the rollback device have executed a successful command; the tail node throws ResvTear (reserved please The message is sent to the intermediate node to clear the flag set by the original signaling.
  • the intermediate node After receiving the ResvTear message, the intermediate node throws the PathErr message to the tail node to clear the flag bit; the service with the backtracking attribute initiates rerouting and will be the first
  • the explicit route in the error information carried in the PathErr message is re-routed as a mandatory condition; the result of the rerouting is converted into an explicit route object in the Path message, and the Path message is sent from the first node to the downstream hop by hop to apply.
  • the label and the issuing instruction are sent to the device.
  • the Resv message is hop-by-hop from the tail node to the upstream node, and the received node checks the execution result of the instruction until the result of the first node checking the instruction is also executed successfully. Established successfully.
  • This document provides a method and device for implementing service backtracking, which can implement service backtracking under the SDN architecture and improve the success rate of service establishment and recovery.
  • the embodiment of the invention provides a method for implementing service backtracking, which is applied to a software defined network controller, and the method includes:
  • the faulty node is determined
  • the method further includes:
  • the service backtracking attribute information of the service is obtained from the service establishment request and saved.
  • the subnet connected to the SNC according to the current route establishment service includes:
  • the route is calculated, the SNC information used to establish the service is determined according to the route, and the SNC information is converted into a southbound protocol command and sent to each network node, according to Whether each SNC executes the instruction determines whether the SNC is successfully established; or
  • determining the faulty node includes:
  • the network node that failed to execute the instruction is determined as the fault node;
  • the network node that has not successfully executed the command and the network node that has triggered the service recovery re-routing by reporting the alarm are determined as the faulty node.
  • performing service backtracking on the service including:
  • the route is recalculated for the service, and the newly calculated route avoids the faulty node.
  • the method further includes:
  • a notification is sent to the network node that successfully executed the instruction to indicate that the instruction that was executed has been revoked.
  • the service backtracking attribute information of the service includes the following information: whether the service has the service backtracking capability, or whether the service has the service backtracking capability and the upper limit of the number of service backtracking times.
  • the service meets the service backtracking conditions, including:
  • the service has service backtracking capability; or
  • the service has a service backtracking capability, and the number of times the service performs service backtracking is less than the upper limit of the number of service backtracking times.
  • the embodiment of the invention provides a method for implementing service backtracking, which is applied to a northbound APP module, and the method includes:
  • the service backtracking attribute information of the service includes the following information: whether the service has the service backtracking capability, or whether the service has the service backtracking capability and the upper limit of the number of service backtracking times.
  • the embodiment of the invention provides a device for implementing service backtracking, which is applied to a software defined network controller, and includes:
  • the routing module is configured to determine the faulty node after the subnet connection failure is established after the subnet that establishes the service according to the current route fails;
  • the query module is configured to query the service backtracking attribute information of the service
  • the service backtracking module is configured to perform service backtracking on the service when the service meets a service backtracking condition.
  • the device further includes:
  • the service attribute obtaining module is configured to obtain the service backtracking attribute information of the service from the service establishment request and save the information after receiving the service establishment request sent by the northbound APP module.
  • the routing module is configured to connect the SNC according to the current route to establish a service according to the current route:
  • the route is calculated, the SNC information used to establish the service is determined according to the route, and the SNC information is converted into a southbound protocol command and sent to each network node, according to Whether each SNC executes the instruction determines whether the SNC is successfully established; or
  • the routing module is configured to determine the faulty node in the following manner:
  • the network node that failed to execute the instruction is determined as the fault node;
  • the network node that has not successfully executed the command and the network node that has triggered the service recovery re-routing by reporting the alarm are determined as the faulty node.
  • the service backtracking module is configured to perform service backtracking on the service in the following manner:
  • the route is recalculated for the service, and the newly calculated route avoids the faulty node.
  • the routing module is further configured to send a notification to the network node that successfully executed the instruction to indicate that the executed instruction is revoked after the subnet connection SNC fails to establish a service according to the current route.
  • the service backtracking attribute information of the service includes the following information: whether the service has the service backtracking capability, or whether the service has the service backtracking capability and the upper limit of the number of service backtracking times.
  • the service meets the service backtracking conditions, including:
  • the service has service backtracking capability; or
  • the service has a service backtracking capability, and the number of times the service performs service backtracking is less than the upper limit of the number of service backtracking times.
  • the embodiment of the invention further provides a device for implementing service backtracking, which is applied to a northbound APP module, and includes:
  • a service attribute setting module configured to determine service backtracking attribute information of the service
  • the service attribute issuance module is configured to send a service establishment request to the software definition network controller, where the service backtracking attribute information of the service is carried.
  • the service backtracking attribute information of the service includes the following information: whether the service has the service backtracking capability, or whether the service has the service backtracking capability and the upper limit of the number of service backtracking times.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented when executed by a processor.
  • the method and device for implementing service backtracking provided by the embodiment of the present invention provide an interface for configuring a service backtracking attribute, and the northbound APP module sends the service backtracking attribute information of the service to the SDN controller.
  • the service backtracking is applied to the service establishment and service recovery in the SDN framework.
  • the node fault information obtained after analyzing the failure command is used as a necessary condition for rerouting, and the success rate of service establishment and recovery is improved.
  • FIG. 1 is an example of a service backtracking process in a GMPLS architecture in the related art.
  • FIG. 2 is a flowchart of a method (SDN controller) for implementing service backtracking according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for implementing service backtracking (Northbound APP module) according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of an apparatus (SDN controller) for implementing service backtracking according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a device (Northbound APP module) for implementing service backtracking according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of an SDN architecture according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for implementing service backtracking (service establishment scenario) according to the present invention.
  • FIG. 8 is a flowchart of a method for implementing service backtracking (service recovery scenario) according to the present invention.
  • FIG. 9 is a schematic diagram of a device networking of a specific example of the present invention.
  • an embodiment of the present invention provides a method for implementing service backtracking, which is applied to a software-defined network controller, and the method includes:
  • S220 Query service backtracking attribute information of the service.
  • S230 Perform service backtracking on the service when the service meets a service backtracking condition
  • the method may also include the following features:
  • the method further includes:
  • the service backtracking attribute information of the service is obtained from the service establishment request and saved;
  • the service backtracking attribute information of the service includes the following information: whether the service has the service backtracking capability, or whether the service has the service backtracking capability and the upper limit value of the service backtracking number;
  • the subnet connected to the SNC according to the current route establishment service includes:
  • the route is calculated, the SNC information used to establish the service is determined according to the route, and the SNC information is converted into a southbound protocol command and sent to each network node, according to Whether each SNC executes the instruction determines whether the SNC is successfully established; or
  • the service meets the service backtracking conditions, including:
  • the service has service backtracking capability; or
  • the service has a service backtracking capability, and the number of times the service performs service backtracking is less than the upper limit of the number of service backtracking times;
  • determining the faulty node includes:
  • the network node that failed to execute the instruction is determined as the fault node;
  • the network node that has not successfully executed the command and the network node that is triggered by the service alarm to trigger the service re-routing are determined as the faulty node;
  • performing service backtracking on the service including:
  • the method further includes:
  • the embodiment of the present invention provides a method for implementing service backtracking, which is applied to a northbound APP module, and the method includes:
  • the method may also include the following features:
  • the service backtracking attribute information of the service includes the following information: whether the service has the service backtracking capability, or whether the service has the service backtracking capability and the service backtracking number upper limit value;
  • an embodiment of the present invention provides a device for implementing service backtracking, which is applied to a software-defined network controller, and includes:
  • the routing module is configured to determine the faulty node after the subnet connection failure is established after the subnet that establishes the service according to the current route fails;
  • the query module is configured to query the service backtracking attribute information of the service
  • the service backtracking module is configured to perform service backtracking on the service when the service meets a service backtracking condition
  • the device may further include the following feature: the device further includes a service attribute obtaining module;
  • the service attribute obtaining module is configured to obtain the service backtracking attribute information of the service from the service establishment request and save the information after receiving the service establishment request sent by the northbound APP module.
  • the routing module is configured to connect the SNC according to the current route to establish a service according to the current route:
  • the route is calculated, the SNC information used to establish the service is determined according to the route, and the SNC information is converted into a southbound protocol command and sent to each network node, according to Whether each SNC executes the instruction determines whether the SNC is successfully established; or
  • the routing module is configured to determine the faulty node in the following manner:
  • the network node that failed to execute the instruction is determined as the fault node;
  • the network node that has not successfully executed the command and the network node that has triggered the service recovery re-routing by reporting the alarm are determined as the faulty node.
  • the service backtracking module is configured to perform service backtracking on the service in the following manner:
  • the route is recalculated for the service, and the newly calculated route avoids the faulty node.
  • the routing module is further configured to send a notification to the network node that successfully executed the instruction to indicate that the executed instruction is revoked after the subnet connection SNC fails to establish a service according to the current route.
  • the service backtracking attribute information of the service includes the following information: whether the service has the service backtracking capability, or whether the service has the service backtracking capability and the upper limit of the number of service backtracking times.
  • the service meets the service backtracking conditions, including:
  • the service has service backtracking capability; or
  • the service has a service backtracking capability, and the number of times the service performs service backtracking is less than the upper limit of the number of service backtracking times.
  • an embodiment of the present invention provides a device for implementing service backtracking, which is applied to a northbound APP module, including:
  • a service attribute setting module configured to determine service backtracking attribute information of the service
  • the service attribute issuance module is configured to send a service establishment request to the software definition network controller, where the service backtracking attribute information of the service is carried.
  • the device may also include the following features:
  • the service backtracking attribute information of the service includes the following information: whether the service has the service backtracking capability, or whether the service has the service backtracking capability and the upper limit of the number of service backtracking times.
  • the SDN architecture of this example includes: a northbound APP module, an SDN controller, and a device supporting a southbound protocol;
  • the northbound APP module is configured to send service backtracking attribute information to the SDN controller through the northbound communication channel;
  • the northbound APP module delivers the service backtracking attribute information and can modify the service backtracking attribute information, while delivering the client service establishment request.
  • the northbound communication channel is a channel capable of transmitting and receiving service establishment requests and customized features, and the actual code stream may be multiple protocols.
  • the SDN controller is configured to receive the service request sent by the user; and has the route calculation capability; the command is sent to the device (optical network device) side through the southbound protocol channel, and the response of the optical network device node can be analyzed.
  • the southbound protocol channel is a channel for information exchange between the SDN controller and the device side, and the actual code stream may be multiple protocols.
  • the device supporting the southbound protocol is configured to convert the protocol content delivered by the SDN controller into an actual command and send it to the optical device, and can feed back the execution result to the controller.
  • this example includes the following steps in the service establishment scenario:
  • S101 The northbound APP sends a service establishment request, and identifies the number of times the service has the service backtracking attribute and the service backtracking.
  • the SDN controller After receiving the service establishment request, the SDN controller calculates a path and finds an optimal path between the source node and the destination node.
  • S104 Convert the SNC into a southbound protocol command and send it to the device (network node).
  • S105 The device parses out the corresponding instruction and executes.
  • S106 The device reports the processing result to the SDN controller, and the SDN controller determines the analysis result.
  • this example includes the following steps in the service recovery scenario:
  • S101 The device-side alarm reported in the south direction triggers the recovery re-routing of the SDN controller.
  • S103 Convert the SNC into a southbound protocol command and send it to the device (network node).
  • S104 The device parses out the corresponding instruction and executes.
  • S105 The device reports the processing result to the controller, and the controller determines the analysis result.
  • the SDN architecture includes the following components:
  • the northbound APP that can deliver the service backtracking attribute and the number of times through the northbound communication channel: it is used to deliver the service backtracking attribute and the number of times, and can modify the service backtracking attribute and the number of times, and can be modified by the http protocol. Send instructions.
  • the northbound communication channel supports the http protocol.
  • SDN controller The northbound support http protocol can correctly parse the request sent by the northbound APP; it has the routing computing capability; the southbound supports the openflow protocol, and the command can be processed to the southbound device after being sent to the device side through the flow_mod.
  • the packet_in message that is acknowledged after the instruction is set, and can determine whether the instruction is all successful according to the information carried in the packet_in message, and can analyze which ports are failed.
  • the southbound openflow protocol channel is the channel for interaction between the SDN controller and the device.
  • the flow_mod message sent by the SDN controller can be converted into an actual command and sent to the optical device, and the processing result can be fed back to the controller through the packet_in message.
  • optical network device nodes which are respectively A, B, C, D, and E, and point B has an internal fault.
  • the northbound APP sends a request to the SDN controller, requesting to establish a service with no protection and no recovery attribute from A to C, and does not specify the route of the service.
  • the initial setting service has a backtracking attribute and can be returned.
  • the number of traces is 2.
  • the method for implementing the service backtracking includes the following steps:
  • the SDN controller receives the service establishment request sent by the northbound APP, and calculates the route as A-B-D-C.
  • S102 The SDN controller converts the route into SNC information.
  • S103 The match and action in the SNC message converted into the flow_mod message are sent to the nodes A, B, C, and D, and each node receives two flow_mod messages.
  • S104 Nodes A, B, C, and D parse the flow_mod message, execute specific instructions, and A, C, and D execute successfully, and all the match and action of the two flow_mods of point B fail to execute.
  • S106 The SDN controller sends a flow_mod message to roll back the instructions that A, C, and D have executed successfully.
  • the SDN controller checks a service backtracking attribute, where the service has a service backtracking attribute.
  • the SDN controller checks the upper limit of the service backtracking number. Currently, the service backtracking is performed for the first time. The upper limit of the number of service backtracking is 2, so the upper limit of the number of service backtracking is not reached.
  • S110 The SDN controller converts the route into SNC information.
  • S111 The match and action in the SNC message converted into the flow_mod message are sent to the nodes A, C, and D, and each node receives two flow_mod messages.
  • S112 Nodes A, C, and D parse the flow_mod message, execute specific instructions, and A, C, and D execute successfully.
  • S113 The node A, C, and D report the execution result to the controller through the packet_in message, and the controller considers that the operation is successful and ends.
  • the northbound APP sends a request to the SDN controller, and successfully establishes a service from the A-C with no protection and recovery attribute.
  • the route of the service is not specified.
  • the initial setting service has a backtracking attribute and the number of backtracking times is 2.
  • the method for implementing the service backtracking includes the following steps:
  • the SDN controller receives an alarm to trigger re-routing, and calculates a route as A-B-D-C.
  • S102 The SDN controller converts the route into SNC information.
  • S103 The match and action in the SNC message converted into the flow_mod message are sent to the nodes A, B, C, and D, and each node receives two flow_mod messages.
  • S104 Nodes A, B, C, and D parse the flow_mod message, execute specific instructions, and A, C, and D execute successfully, and all the match and action of the two flow_mods of point B fail to execute.
  • S106 The SDN controller sends a flow_mod message to roll back the instructions that A, C, and D have executed successfully.
  • the SDN controller checks the service backtracking attribute, and the service has a service backtracking attribute.
  • the SDN controller checks the upper limit of the service backtracking number. Currently, the service backtracking is performed for the first time. The upper limit of the number of service backtracking is 2, so the upper limit of the number of service backtracking is not reached.
  • S110 The SDN controller converts the route into SNC information.
  • S111 The match and action in the SNC message converted into the flow_mod message are sent to the nodes A, C, and D, and each node receives two flow_mod messages.
  • S112 Nodes A, C, and D parse the flow_mod message, execute specific instructions, and A, C, and D execute successfully.
  • S113 The node A, C, and D report the execution result to the controller through the packet_in message, and the controller considers that the operation is successful and ends.
  • the northbound APP sends a request to the SDN controller to request a service from A to C that has no protection and no recovery attribute, and does not specify the route of the service.
  • the service does not have a backtracking attribute.
  • the method for implementing the service backtracking includes the following steps:
  • the SDN controller receives the service establishment request sent by the northbound APP, and calculates the route as A-B-D-C.
  • S102 The SDN controller converts the route into SNC information.
  • S103 The match and action in the SNC message converted into the flow_mod message are sent to the nodes A, B, C, and D, and each node receives two flow_mod messages.
  • S104 Nodes A, B, C, and D parse the flow_mod message, execute specific instructions, and A, C, and D execute successfully, and all the match and action of the two flow_mods of point B fail to execute.
  • S106 The SDN controller sends a flow_mod message to roll back the instructions that A, C, and D have executed successfully.
  • S107 The SDN controller checks the service backtracking attribute, and the service does not have the backtracking attribute, and ends.
  • an embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, which are implemented when executed by a processor.
  • the method and device for implementing service backtracking provided by the foregoing embodiment provide an interface for configuring a service backtracking attribute, and the northbound APP module sends the service backtracking attribute information of the service to the SDN.
  • the controller applies the service backtracking to the service establishment and service recovery in the SDN framework, and uses the node fault information obtained after analyzing the failure command as a necessary condition for rerouting, thereby improving the success rate of service establishment and recovery.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. Instructions to achieve their corresponding functions. This application is not limited to any specific combination of hardware and software.
  • the technical solution provided by the embodiment of the present invention provides an interface for the customer to configure the service backtracking attribute, and the northbound APP module sends the service backtracking attribute information of the service to the SDN controller, and applies the service backtracking to the service establishment and service under the SDN framework.
  • Recovery the node failure information obtained after analyzing the failure instruction is used as a necessary condition for rerouting, and the success rate of service establishment and recovery is improved.

Landscapes

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

Abstract

本文公开了一种实现业务回溯的方法，应用于软件定义网络控制器，该方法包括：在根据当前路由建立业务的子网连接SNC失败后，确定故障节点；查询所述业务的业务回溯属性信息；在所述业务满足业务回溯条件时，对所述业务进行业务回溯。

Description

一种实现业务回溯的方法和装置 技术领域
本文涉及但不限于光通讯技术领域，尤其涉及的是一种实现业务回溯的方法和装置。
背景技术
目前SDN(Software Defined Network，软件定义网络)技术已成为时下讨论的热点，其集中控制、实现控制与转发分离以及多种多样的个性化定制APP等等特性，使其成为时下研究热点。而承载网(主要指PTN(Packet Transport Network，分组传送网)和OTN(Optical Transport Network，光传送网))领域也逐渐在引入SDN技术，但相关标准还处在萌芽和储备状态。
目前基于光网络的SDN研究整体还停留在初级阶段。现有SDN框架下，北向APP下发的业务建立一旦出现设备侧处理的问题，就只能注定本条业务的失败。光网络设备形态各异时，出现设备指令下发失败很普遍，但是现有SDN框架下并没有好的机制来保证业务的成功率。
当网络节点实际配置失败时，在没有告警上报的情况下，借助协议来实现避开故障网络节点自动重路由的方法通常被称为业务回溯，如图1所示，GMPLS(Generalized Multiprotocol Label Switching，通用多协议标记交换)架构下，业务回溯包括如下步骤：
从首节点(Ingress)逐跳向下游发送Path(路径)消息来申请标签和下发指令给设备，当Path消息到达尾节点(Egress)时，Resv(预留)消息从尾节点逐跳传递到上游节点，收到的节点检查指令的执行结果；Resv消息传递到中间节点(Transit)时，检查到中间节点下发给设备的指令执行失败，此时通过ResvErr(预留请求差错)消息把执行的错误信息传递给尾节点；尾节点通过PathErr(路径差错)消息向上游通知此次建立过程失败，并通过PathErr消息将执行错误的信息逐条回传到首节点，收到PathErr消息的节点需要释放本地已经申请的标签并且回退设备已经执行成功的指令；尾节点抛出ResvTear(预留请 求拆除)消息到中间节点来清除原有信令设置的标志位，中间节点收到ResvTear消息后抛出PathErr消息到尾节点来清除标志位；具有回溯属性的业务发起重路由，并将之前首节点PathErr消息中携带的错误信息中的显式路由作为必避条件进行重路由；重路由的结果被转化为Path消息中的显式路由对象，从首节点开始逐跳向下游发送Path消息来申请标签和下发指令给设备，当Path消息到达尾节点时，Resv消息从尾节点逐跳传递到上游节点，收到的节点检查指令的执行结果，直到首节点检查指令结果也是执行成功，本业务建立成功。
在业务恢复场景下，无论是由谁来控制设备，快速恢复出一条能用的路径来保证业务不出现长时间中断是第一优先级的，因此，在SDN架构下找到一种业务回溯的方案是很有必要的。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供一种实现业务回溯的方法和装置，能够在SDN架构下实现业务回溯，提高业务建立、恢复的成功率。
本发明实施例提供了一种实现业务回溯的方法，应用于软件定义网络控制器，该方法包括：
在根据当前路由建立业务的子网连接SNC失败后，确定故障节点；
查询所述业务的业务回溯属性信息；
在所述业务满足业务回溯条件时，对所述业务进行业务回溯。
可选地，在根据当前路由建立业务的子网连接SNC之前，所述方法还包括：
接收到北向APP模块下发的业务建立请求后，从所述业务建立请求中获取所述业务的业务回溯属性信息并保存。
可选地，根据当前路由建立业务的子网连接SNC，包括：
接收到北向APP模块下发的业务建立请求后，计算路由，根据所述路由确定用于建立所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功；或者
在接收到网络节点上报的告警信息后，触发重新计算路由，根据新计算的路由确定用于恢复所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功。
可选地，确定故障节点，包括：
在业务建立过程中，将未成功执行指令的网络节点确定为故障节点；或者
在业务恢复过程中，将未成功执行指令的网络节点以及通过上报告警触发业务恢复重路由的网络节点确定为故障节点。
可选地，对所述业务进行业务回溯，包括：
为所述业务重新计算路由，新计算的路由避开故障节点。
可选地，在根据当前路由建立业务的子网连接SNC失败后，所述方法还包括：
向成功执行了指令的网络节点发送通知以指示撤销已经执行的指令。
可选地，所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
可选地，所述业务满足业务回溯条件包括：
所述业务具有业务回溯能力；或者
所述业务具有业务回溯能力且所述业务进行业务回溯的次数小于所述业务回溯次数上限值。
本发明实施例提供了一种实现业务回溯的方法，应用于北向APP模块，该方法包括：
确定业务的业务回溯属性信息；
向软件定义网络控制器发送业务建立请求，其中携带所述业务的业务回溯属性信息。
可选地，所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
本发明实施例提供了一种实现业务回溯的装置，应用于软件定义网络控制器，包括：
路由模块，设置为在根据当前路由建立业务的子网连接SNC失败后，确定故障节点；
查询模块，设置为查询所述业务的业务回溯属性信息；
业务回溯模块，设置为在所述业务满足业务回溯条件时，对所述业务进行业务回溯。
可选地，所述装置还包括：
业务属性获取模块，设置为接收到北向APP模块下发的业务建立请求后，从所述业务建立请求中获取所述业务的业务回溯属性信息并保存。
可选地，路由模块，设置为采用以下方式根据当前路由建立业务的子网连接SNC：
接收到北向APP模块下发的业务建立请求后，计算路由，根据所述路由确定用于建立所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功；或者
在接收到网络节点上报的告警信息后，触发重新计算路由，根据新计算的路由确定用于恢复所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功。
可选地，路由模块，设置为采用以下方式确定故障节点：
在业务建立过程中，将未成功执行指令的网络节点确定为故障节点；或者
在业务恢复过程中，将未成功执行指令的网络节点以及通过上报告警触发业务恢复重路由的网络节点确定为故障节点。
可选地，业务回溯模块，设置为采用以下方式对所述业务进行业务回溯：
为所述业务重新计算路由，新计算的路由避开故障节点。
可选地，路由模块，还设置为在根据当前路由建立业务的子网连接SNC失败后，向成功执行了指令的网络节点发送通知以指示撤销已经执行的指令。
可选地，所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
可选地，所述业务满足业务回溯条件包括：
所述业务具有业务回溯能力；或者
所述业务具有业务回溯能力且所述业务进行业务回溯的次数小于所述业务回溯次数上限值。
本发明实施例还提供了一种实现业务回溯的装置，应用于北向APP模块，包括：
业务属性设定模块，设置为确定业务的业务回溯属性信息；
业务属性下发模块，设置为向软件定义网络控制器发送业务建立请求，其中携带所述业务的业务回溯属性信息。
可选地，所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述方法。
与相关技术相比，本发明实施例提供的一种实现业务回溯的方法和装置，为客户提供了配置业务回溯属性的接口，北向APP模块将业务的业务回溯属性信息下发给SDN控制器，将业务回溯应用于SDN框架下的业务建立、业务恢复，将分析失败指令后得到的节点故障信息作为重路由的必避条件，提高业务建立、恢复的成功率。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为相关技术中GMPLS架构下的业务回溯流程示例。
图2为本发明实施例的一种实现业务回溯的方法(SDN控制器)的流程图。
图3为本发明实施例的一种实现业务回溯的方法(北向APP模块)的流程图。
图4为本发明实施例的一种实现业务回溯的装置(SDN控制器)的结构示意图。
图5为本发明实施例的一种实现业务回溯的装置(北向APP模块)的结构示意图。
图6为本发明实施例的SDN架构示意图。
图7为本发明的一种实现业务回溯的方法(业务建立场景)的流程图。
图8为本发明的一种实现业务回溯的方法(业务恢复场景)的流程图。
图9为本发明具体示例的设备组网示意图。
本发明的实施方式
下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
如图2所示，本发明实施例提供了一种实现业务回溯的方法，应用于软件定义网络控制器，该方法包括：
S210，在根据当前路由建立业务的子网连接SNC失败后，确定故障节点；
S220，查询所述业务的业务回溯属性信息；
S230，在所述业务满足业务回溯条件时，对所述业务进行业务回溯；
所述方法还可以包括下述特点：
可选地，在根据当前路由建立业务的SNC(Subnetwork Connection，子网连接)之前，所述方法还包括：
接收到北向APP模块下发的业务建立请求后，从所述业务建立请求中获取所述业务的业务回溯属性信息并保存；
其中，所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值；
可选地，根据当前路由建立业务的子网连接SNC，包括：
接收到北向APP模块下发的业务建立请求后，计算路由，根据所述路由确定用于建立所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功；或者
在接收到网络节点上报的告警信息后，触发重新计算路由，根据新计算的路由确定用于恢复所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功；
可选地，所述业务满足业务回溯条件包括：
所述业务具有业务回溯能力；或者
所述业务具有业务回溯能力且所述业务进行业务回溯的次数小于所述业务回溯次数上限值；
可选地，确定故障节点，包括：
在业务建立过程中，将未成功执行指令的网络节点确定为故障节点；或者
在业务恢复过程中，将未成功执行指令的网络节点以及通过上报告警触发业务恢复重路由的网络节点确定为故障节点；
可选地，对所述业务进行业务回溯，包括：
为所述业务重新计算路由，新计算的路由避开故障节点；
可选地，在根据当前路由建立业务的子网连接SNC失败后，还包括：
向成功执行了指令的网络节点发送通知以指示撤销已经执行的指令；
如图3所示，本发明实施例提供了一种实现业务回溯的方法，应用于北向APP模块，该方法包括：
S310，确定业务的业务回溯属性信息；
S320，向软件定义网络控制器发送业务建立请求，其中携带所述业务的业务回溯属性信息；
所述方法还可以包括下述特点：
可选地，所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值；
如图4所示，本发明实施例提供了一种实现业务回溯的装置，应用于软件定义网络控制器，包括：
路由模块，设置为在根据当前路由建立业务的子网连接SNC失败后，确定故障节点；
查询模块，设置为查询所述业务的业务回溯属性信息；
业务回溯模块，设置为在所述业务满足业务回溯条件时，对所述业务进行业务回溯；
所述装置还可以包括下述特点：所述装置还包括业务属性获取模块；
所述业务属性获取模块，设置为接收到北向APP模块下发的业务建立请求后，从所述业务建立请求中获取所述业务的业务回溯属性信息并保存。
可选地，路由模块，设置为采用以下方式根据当前路由建立业务的子网连接SNC：
接收到北向APP模块下发的业务建立请求后，计算路由，根据所述路由确定用于建立所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功；或者
在接收到网络节点上报的告警信息后，触发重新计算路由，根据新计算的路由确定用于恢复所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功。
可选地，路由模块，设置为采用以下方式确定故障节点：
在业务建立过程中，将未成功执行指令的网络节点确定为故障节点；或者
在业务恢复过程中，将未成功执行指令的网络节点以及通过上报告警触发业务恢复重路由的网络节点确定为故障节点。
可选地，业务回溯模块，设置为采用以下方式对所述业务进行业务回溯：
为所述业务重新计算路由，新计算的路由避开故障节点。
可选地，路由模块，还设置为在根据当前路由建立业务的子网连接SNC失败后，向成功执行了指令的网络节点发送通知以指示撤销已经执行的指令。
可选地，所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
可选地，所述业务满足业务回溯条件包括：
所述业务具有业务回溯能力；或者
所述业务具有业务回溯能力且所述业务进行业务回溯的次数小于所述业务回溯次数上限值。
如图5所示，本发明实施例提供了实现业务回溯的装置，应用于北向APP模块，包括：
业务属性设定模块，设置为确定业务的业务回溯属性信息；
业务属性下发模块，设置为向软件定义网络控制器发送业务建立请求，其中携带所述业务的业务回溯属性信息。
所述装置还可以包括下述特点：
所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
示例
如图6所示，本示例的SDN架构包括：北向APP模块、SDN控制器、和支持南向协议的设备；
北向APP模块，设置为通过北向通信通道向SDN控制器下发业务回溯属性信息；
其中，所述北向APP模块在下发客户业务建立请求的同时，下发业务回溯属性信息，且能修改业务回溯属性信息；
其中，北向通信通道是能够收发业务建立请求和定制特性的通道，实际码流可以是多种协议。
SDN控制器，设置为接收用户下发的业务请求；具备路由计算能力；通过南向协议通道把指令下发到设备(光网络设备)侧，能够解析光网络设备节点的应答。
其中，南向协议通道是SDN控制器与设备侧之间信息交互的通道，实际码流可以是多种协议。
支持南向协议的设备，设置为把SDN控制器下发的协议内容转化为实际指令下发到光器件，并能将执行结果反馈给控制器。
如图7所示，本示例在业务建立场景下包括以下几个步骤：
S101：北向APP下发业务建立请求，并标识本业务具有业务回溯属性和业务回溯的次数。
S102：SDN控制器收到业务建立请求后算路，找到源节点和目的节点之间的最佳路径。
S103：将计算得到的路由转化成SNC。
S104：将SNC转化成南向协议指令下发到设备(网络节点)。
S105：设备解析出相应指令并执行。
S106：设备将处理结果上报给SDN控制器，SDN控制器判断分析结果。
S107：若成功，业务建立成功，结束。
S108：若失败，回退本次操作成功下发到设备的指令。
S109：检查业务是否具有业务回溯属性。
S110：若不具有，结束。
S111：若具有，检查当前业务回溯的次数是否到达上限。
S112：若业务回溯的次数达到上限，结束。
S113：若业务回溯的次数未达到上限，分析具体失败的指令，设定节点故障的信息。
S114：将节点故障信息作为必避条件进行重路由。
如图8所示，本示例在业务恢复场景下包括以下几个步骤：
S101：南向上报的设备侧告警触发SDN控制器的恢复重路由。
S102：将计算得到的路由转化成SNC。
S103：将SNC转化成南向协议指令下发到设备(网络节点)。
S104：设备解析出相应指令并执行。
S105：设备将处理结果上报给控制器，控制器判断分析结果。
S106：若成功，业务恢复成功，结束。
S107：若失败，回退本次操作成功下发到设备的指令。
S108：检查业务是否具有业务回溯属性。
S109：若不具有，结束。
S110：若具有，检查当前业务回溯的次数是否到达上限。
S111：若业务回溯的次数达到上限，结束。
S112：若业务回溯的次数未达到上限，分析具体失败的指令，设定节点故障的信息。
S113：将节点故障信息和告警信息作为必避条件进行重路由。
在下述具体示例中，SDN架构包括以下几个组件：
1)能够通过北向通信通道下发业务回溯属性和次数的北向APP：用于在下发客户业务建立请求的同时，下发业务回溯属性和次数，且能修改业务回溯属性和次数，通过http协议下发指令。
其中，北向通信通道支持http协议。
2)SDN控制器：北向支持http协议，能够对北向APP下发的请求进行正确解析；具备路由计算能力；南向支持openflow协议，把指令通过flow_mod下发到设备侧后，能够处理南向设备指令设置完成后应答的packet_in消息，并能根据packet_in消息中携带的信息判断出指令是否全部成功，且能分析失败的端口是哪些。
其中，南向openflow协议通道是SDN控制器和设备之间交互的通道。
3)支持openflow协议的设备：能把SDN控制器下发的flow_mod消息转化为实际指令下发到光器件，并能将处理结果通过packet_in消息反馈给控制器。
如图9所示，有这样5个光网络设备节点，分别为A、B、C、D、E，其中点B存在内部故障。
具体示例1
北向APP向SDN控制器下发请求，请求从A到C建立一条无保护没有恢复属性的业务，不指定该业务的路由，初始设置业务具有回溯属性且可回 溯次数为2。
当SDN控制器收到北向APP下发的业务建立请求，实现业务回溯的方法包括以下步骤：
S101：SDN控制器收到北向APP下发的业务建立请求，计算出路由为A-B-D-C。
S102：SDN控制器将路由转化为SNC信息。
S103：SNC消息转化为flow_mod消息中的match和action下发到节点A、B、C、D，其中每个节点会收到两条flow_mod消息。
S104：节点A、B、C、D解析flow_mod消息，执行具体指令，A、C和D执行成功，点B两条flow_mod的match和action全部执行失败。
S105：节点A、B、C、D将执行结果通过packet_in消息上报给控制器，控制器认为本次操作失败。
S106：SDN控制器下发flow_mod消息回退A、C和D已经执行成功的指令。
S107：SDN控制器检查业务回溯属性，所述业务具有业务回溯属性。
S108：SDN控制器检查业务回溯次数上限，当前为第一次业务回溯，业务回溯次数上限为2，因此未达到业务回溯次数上限。
S109：将节点B作为必避节点进行重路由，计算出的路由结果为A-D-C。
S110：SDN控制器将路由转化为SNC信息。
S111：SNC消息转化为flow_mod消息中的match和action下发到节点A、C、D，其中每个节点会收到两条flow_mod消息。
S112：节点A、C、D解析flow_mod消息，执行具体指令，A、C和D执行成功。
S113：节点A、C、D将执行结果通过packet_in消息上报给控制器，控制器认为本次操作成功，结束。
具体示例2
北向APP向SDN控制器下发请求，成功建立了一条从A-C的无保护有恢复属性的业务，未指定该业务的路由，初始设置业务具有回溯属性且可回溯次数为2。
当SDN控制器收到南向A-C段的告警时，实现业务回溯的方法包括以下步骤：。
S101：SDN控制器收到告警触发重路由，计算出路由为A-B-D-C。
S102：SDN控制器将路由转化为SNC信息。
S103：SNC消息转化为flow_mod消息中的match和action下发到节点A、B、C、D，其中每个节点会收到两条flow_mod消息。
S104：节点A、B、C、D解析flow_mod消息，执行具体指令，A、C和D执行成功，点B两条flow_mod的match和action全部执行失败。
S105：节点A、B、C、D将执行结果通过packet_in消息上报给控制器，控制器认为本次操作失败。
S106：SDN控制器下发flow_mod消息回退A、C和D已经执行成功的指令。
S107：SDN控制器检查业务回溯属性，该业务具有业务回溯属性。
S108：SDN控制器检查业务回溯次数上限，当前为第一次业务回溯，业务回溯次数上限为2，因此未达到业务回溯次数上限。
S109：将节点B和A-C链路作为必避节点进行重路由，计算出的路由结果为A-D-C。
S110：SDN控制器将路由转化为SNC信息。
S111：SNC消息转化为flow_mod消息中的match和action下发到节点A、C、D，其中每个节点会收到两条flow_mod消息。
S112：节点A、C、D解析flow_mod消息，执行具体指令，A、C和D执行成功。
S113：节点A、C、D将执行结果通过packet_in消息上报给控制器，控制器认为本次操作成功，结束。
具体示例3
北向APP向SDN控制器下发请求，请求从A到C建立一条无保护没有恢复属性的业务，不指定该业务的路由，设置业务不具有回溯属性。
当SDN控制器收到北向APP下发的业务建立请求，实现业务回溯的方法包括以下步骤：
S101，SDN控制器收到北向APP下发的业务建立请求，计算出路由为A-B-D-C。
S102：SDN控制器将路由转化为SNC信息。
S103：SNC消息转化为flow_mod消息中的match和action下发到节点A、B、C、D，其中每个节点会收到两条flow_mod消息。
S104：节点A、B、C、D解析flow_mod消息，执行具体指令，A、C和D执行成功，点B两条flow_mod的match和action全部执行失败。
S105：节点A、B、C、D将执行结果通过packet_in消息上报给控制器，控制器认为本次操作失败。
S106：SDN控制器下发flow_mod消息回退A、C和D已经执行成功的指令。
S107：SDN控制器检查业务回溯属性，业务不具有回溯属性，结束。
此外，本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述方法。
上述实施例提供的一种实现业务回溯的方法和装置，为客户提供了配置业务回溯属性的接口，北向APP模块将业务的业务回溯属性信息下发给SDN 控制器，将业务回溯应用于SDN框架下的业务建立、业务恢复，将分析失败指令后得到的节点故障信息作为重路由的必避条件，提高业务建立、恢复的成功率。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序指令来实现其相应功能。本申请不限制于任何特定形式的硬件和软件的结合。
需要说明的是，本申请还可有其他多种实施例，在不背离本申请精神及其实质的情况下，熟悉本领域的技术人员可根据本申请作出各种相应的改变和变形，但这些相应的改变和变形都应属于本申请所附的权利要求的保护范围。
工业实用性
本发明实施例提供的技术方案，为客户提供了配置业务回溯属性的接口，北向APP模块将业务的业务回溯属性信息下发给SDN控制器，将业务回溯应用于SDN框架下的业务建立、业务恢复，将分析失败指令后得到的节点故障信息作为重路由的必避条件，提高业务建立、恢复的成功率。

Claims (20)

  1. 一种实现业务回溯的方法，应用于软件定义网络控制器，该方法包括：
    在根据当前路由建立业务的子网连接SNC失败后，确定故障节点；
    查询所述业务的业务回溯属性信息；
    在所述业务满足业务回溯条件时，对所述业务进行业务回溯。
  2. 如权利要求1所述的方法，其中：
    在根据当前路由建立业务的子网连接SNC之前，所述方法还包括：
    接收到北向APP模块下发的业务建立请求后，从所述业务建立请求中获取所述业务的业务回溯属性信息并保存。
  3. 如权利要求1或2所述的方法，其中：
    根据当前路由建立业务的子网连接SNC，包括：
    接收到北向APP模块下发的业务建立请求后，计算路由，根据所述路由确定用于建立所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功；或者
    在接收到网络节点上报的告警信息后，触发重新计算路由，根据新计算的路由确定用于恢复所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功。
  4. 如权利要求3所述的方法，其中：
    确定故障节点，包括：
    在业务建立过程中，将未成功执行指令的网络节点确定为故障节点；或者
    在业务恢复过程中，将未成功执行指令的网络节点以及通过上报告警触发业务恢复重路由的网络节点确定为故障节点。
  5. 如权利要求1或2所述的方法，其中：
    对所述业务进行业务回溯，包括：
    为所述业务重新计算路由，新计算的路由避开故障节点。
  6. 如权利要求1或2所述的方法，其中：
    在根据当前路由建立业务的子网连接SNC失败后，所述方法还包括：
    向成功执行了指令的网络节点发送通知以指示撤销已经执行的指令。
  7. 如权利要求1或2所述的方法，其中：
    所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
  8. 如权利要求7所述的方法，其中：
    所述业务满足业务回溯条件包括：
    所述业务具有业务回溯能力；或者
    所述业务具有业务回溯能力且所述业务进行业务回溯的次数小于所述业务回溯次数上限值。
  9. 一种实现业务回溯的方法，应用于北向APP模块，该方法包括：
    确定业务的业务回溯属性信息；
    向软件定义网络控制器发送业务建立请求，其中携带所述业务的业务回溯属性信息。
  10. 如权利要求9所述的方法，其中：
    所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
  11. 一种实现业务回溯的装置，应用于软件定义网络控制器，包括：
    路由模块，设置为在根据当前路由建立业务的子网连接SNC失败后，确定故障节点；
    查询模块，设置为查询所述业务的业务回溯属性信息；
    业务回溯模块，设置为在所述业务满足业务回溯条件时，对所述业务进行业务回溯。
  12. 如权利要求11所述的装置，其中：
    所述装置还包括：
    业务属性获取模块，用于接收到北向APP模块下发的业务建立请求后，从所述业务建立请求中获取所述业务的业务回溯属性信息并保存。
  13. 如权利要求11或12所述的装置，其中：
    路由模块，设置为采用以下方式根据当前路由建立业务的子网连接SNC：
    接收到北向APP模块下发的业务建立请求后，计算路由，根据所述路由确定用于建立所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功；或者
    在接收到网络节点上报的告警信息后，触发重新计算路由，根据新计算的路由确定用于恢复所述业务的SNC信息，将所述SNC信息转化成南向协议指令下发到各网络节点，根据各网络节点执行指令的情况判定所述SNC是否建立成功。
  14. 如权利要求13所述的装置，其中：
    路由模块，设置为采用以下方式确定故障节点：
    在业务建立过程中，将未成功执行指令的网络节点确定为故障节点；或者
    在业务恢复过程中，将未成功执行指令的网络节点以及通过上报告警触发业务恢复重路由的网络节点确定为故障节点。
  15. 如权利要求11或12所述的装置，其中：
    业务回溯模块，设置为采用以下方式对所述业务进行业务回溯：
    为所述业务重新计算路由，新计算的路由避开故障节点。
  16. 如权利要求11或12所述的装置，其中：
    路由模块，还设置为在根据当前路由建立业务的子网连接SNC失败后，向成功执行了指令的网络节点发送通知以指示撤销已经执行的指令。
  17. 如权利要求11或12所述的装置，其中：
    所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
  18. 如权利要求17所述的装置，其中：
    所述业务满足业务回溯条件包括：
    所述业务具有业务回溯能力；或者
    所述业务具有业务回溯能力且所述业务进行业务回溯的次数小于所述业务回溯次数上限值。
  19. 一种实现业务回溯的装置，应用于北向APP模块，包括：
    业务属性设定模块，设置为确定业务的业务回溯属性信息；
    业务属性下发模块，设置为向软件定义网络控制器发送业务建立请求，其中携带所述业务的业务回溯属性信息。
  20. 如权利要求19所述的装置，其中：
    所述业务的业务回溯属性信息包括以下信息：业务是否具有业务回溯能力，或者业务是否具有业务回溯能力以及业务回溯次数上限值。
PCT/CN2016/088373 2015-07-10 2016-07-04 一种实现业务回溯的方法和装置 WO2017008656A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP16823803.8A EP3322158A4 (en) 2015-07-10 2016-07-04 Method and device for realizing service backtracking

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510408349.3 2015-07-10
CN201510408349.3A CN106341320A (zh) 2015-07-10 2015-07-10 一种实现业务回溯的方法和装置

Publications (1)

Publication Number Publication Date
WO2017008656A1 true WO2017008656A1 (zh) 2017-01-19

Family

ID=57757362

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/088373 WO2017008656A1 (zh) 2015-07-10 2016-07-04 一种实现业务回溯的方法和装置

Country Status (3)

Country Link
EP (1) EP3322158A4 (zh)
CN (1) CN106341320A (zh)
WO (1) WO2017008656A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220231909A1 (en) * 2019-06-21 2022-07-21 Nippon Telegraph And Telephone Corporation Plug-in generation device, controller, plug-in generation method, and plug-in generation program
CN112350948B (zh) * 2020-10-28 2021-07-16 武汉大学 一种基于sdn的分布式网络溯源系统的分布式网络溯源方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101309525A (zh) * 2008-06-30 2008-11-19 中兴通讯股份有限公司 一种自动交换光网络中依据故障定位的路由恢复方法
CN101924697A (zh) * 2010-06-30 2010-12-22 北京科技大学 一种基于链路回溯恢复策略的双向启动恢复方法
CN103685580A (zh) * 2013-12-18 2014-03-26 武汉邮电科学研究院 基于软件定义网络的北向接口接入系统及方法
US20140192645A1 (en) * 2013-01-04 2014-07-10 Futurewei Technologies, Inc. Method for Internet Traffic Management Using a Central Traffic Controller
CN104158733A (zh) * 2013-05-13 2014-11-19 华为技术有限公司 一种快速重路由方法及装置、传输网络
CN104734954A (zh) * 2015-03-27 2015-06-24 华为技术有限公司 一种用于软件定义网络的路由确定方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100484092C (zh) * 2005-02-03 2009-04-29 华为技术有限公司 层次光网络路由选择失败后的重路由方法
CN104243196B (zh) * 2013-06-21 2019-03-12 中兴通讯股份有限公司 一种sdn架构下的虚拟网络映射保护方法及系统
US9258238B2 (en) * 2013-08-30 2016-02-09 Juniper Networks, Inc. Dynamic end-to-end network path setup across multiple network layers
WO2015089706A1 (zh) * 2013-12-16 2015-06-25 华为技术有限公司 一种重路由顺序规划方法及系统
CN104243308A (zh) * 2014-09-17 2014-12-24 华为技术有限公司 一种重路由的方法、网络设备及控制器
AU2014101209A4 (en) * 2014-09-18 2014-11-13 Tech Mahindra Ltd. System and method for orchestrating dynamic recovery actions for business services across traditional and sdn supporting openflow protocol

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101309525A (zh) * 2008-06-30 2008-11-19 中兴通讯股份有限公司 一种自动交换光网络中依据故障定位的路由恢复方法
CN101924697A (zh) * 2010-06-30 2010-12-22 北京科技大学 一种基于链路回溯恢复策略的双向启动恢复方法
US20140192645A1 (en) * 2013-01-04 2014-07-10 Futurewei Technologies, Inc. Method for Internet Traffic Management Using a Central Traffic Controller
CN104158733A (zh) * 2013-05-13 2014-11-19 华为技术有限公司 一种快速重路由方法及装置、传输网络
CN103685580A (zh) * 2013-12-18 2014-03-26 武汉邮电科学研究院 基于软件定义网络的北向接口接入系统及方法
CN104734954A (zh) * 2015-03-27 2015-06-24 华为技术有限公司 一种用于软件定义网络的路由确定方法和装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP3322158A1 (en) 2018-05-16
EP3322158A4 (en) 2018-05-30
CN106341320A (zh) 2017-01-18

Similar Documents

Publication Publication Date Title
JP5209116B2 (ja) パケット交換網における擬似ワイヤの確立
US10484299B2 (en) Method and apparatus for configuring quality of service
US9210075B2 (en) Method and apparatus for managing end-to-end consistency of bi-directional MPLS-TP tunnels via in-band communication channel (G-ACH) protocol
JP4443442B2 (ja) 中継装置
JP2008199311A (ja) スイッチ装置およびパス監視設定方法
WO2014081766A1 (en) Bandwidth on-demand services in multiple layer networks
EP3777053B1 (en) Border routers in multicast networks and methods of operating the same
WO2015035616A1 (zh) 跨网通信方法及装置
CN110959272B (zh) Ip/mpls网络隧道中的缺陷检测
US8918671B2 (en) Technique for protecting leaf nodes of a point-to-multipoint tree in a communications network in connected mode
WO2017008656A1 (zh) 一种实现业务回溯的方法和装置
WO2021143524A1 (zh) 一种故障检测方法及设备
RU2730390C1 (ru) Способ и устройство для автоматического определения топологии межузловой связи в совместно используемом резервном кольце трансокеанской мультиплексной секции
JP6042838B2 (ja) 管理システム、管理サーバ、および管理方法
EP2704382B1 (en) Method for managing services in a generalized-multi-protocol label switching, GMPLS, controlled network
US11490178B2 (en) Method for establishing service path, network device, and system
WO2018121485A1 (zh) 业务切换方法、装置及业务切换系统
US10432505B2 (en) Systems, apparatuses, and methods for rerouting network traffic
JP6472942B2 (ja) 切替制御装置、切替制御方法、及び切替制御プログラム
US11323365B2 (en) Tearing down a label switched path through a communications network
JP5478684B2 (ja) エッジノード装置、パス制御方法、及びプログラム
WO2022100160A1 (zh) 路径关联信息的获取方法、设备及系统
JP5701963B2 (ja) ネットワーク
JP5734896B2 (ja) 通信システム、通信装置、パス生成制御方法、及びプログラム
WO2017219786A1 (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: 16823803

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016823803

Country of ref document: EP