WO2016165422A1 - 业务动态恢复的方法、装置及软件定义网络sdn控制器 - Google Patents
业务动态恢复的方法、装置及软件定义网络sdn控制器 Download PDFInfo
- Publication number
- WO2016165422A1 WO2016165422A1 PCT/CN2016/070488 CN2016070488W WO2016165422A1 WO 2016165422 A1 WO2016165422 A1 WO 2016165422A1 CN 2016070488 W CN2016070488 W CN 2016070488W WO 2016165422 A1 WO2016165422 A1 WO 2016165422A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- recovery
- thread
- data
- service data
- Prior art date
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/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
- 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
Definitions
- This document relates to, but is not limited to, the field of telecommunication network management technology, and in particular to a method, device and software defined network SDN controller for dynamic service recovery.
- the device After the software defined network (SDN) technology is introduced into the transmission network system, the device only needs to maintain the service flow table to ensure real-time and accurate data transmission.
- SDN software defined network
- the SDN controller service starts the dynamic recovery function to process.
- one or more optical fibers in the transmission network are interrupted or the node fails, tens of thousands of service interruptions are caused, and the time required for dynamic recovery services is in the order of seconds, so that a large number of services requiring dynamic recovery are completed in a few seconds.
- Recovery which is a major problem for SDN controllers.
- the embodiments of the present invention provide a method, a device, and a software-defined network SDN controller for service dynamic recovery, to solve the technical problem of how to quickly recover an interrupt service caused by a fiber break or a node failure.
- An embodiment of the present invention provides a method for dynamic service recovery, which is applied to a software-defined network SDN controller, including:
- the service path recovery calculation is performed on the services in the service list, and the service path of each service is completed, by using a plurality of service recovery threads that are pre-built and based on the first service data that is required for service recovery. restore.
- the method further includes: before the obtaining the service interruption command in the transmission network, determining the service list affected by the service interruption, the method further includes:
- Pre-establishing a plurality of service recovery threads and a plurality of the first service data Pre-establishing a plurality of service recovery threads and a plurality of the first service data, and the number of the service recovery threads is the same as the number of the first service data, and the number of the service recovery threads and the central processing of the transmission network system
- the CPU resources are matched, and the first service data includes network topology information and link bandwidth information required for service recovery.
- the multiple service recovery threads are pre-built, and the service path recovery calculation is performed on the services in the service list according to the pre-built multiple service data required for service recovery.
- the steps of restoring the business path of each business including:
- the step of causing the first thread to perform a service path recovery calculation on the first service according to the first service data corresponding to the first thread includes:
- the method further includes:
- the method further includes: before the first thread is configured to modify the second service data according to the route of the first corresponding service, the method further includes:
- the step of determining whether the second service data meets the first corresponding service re-routing requirement includes:
- the second service data meets the weight of the first corresponding service. a routing request; when the link bandwidth information required to determine that the service path of the first corresponding service is greater than or equal to the corresponding link bandwidth information in the second service data, the second service data does not meet the Re-routing requirements for the first corresponding service.
- the step of determining whether the second service data meets the re-routing requirement of the first corresponding service is:
- the first service is re-routed by the preset number of times, and the second service data is still unable to satisfy the first corresponding service after the re-routing, and the first service is stopped, and the log record is stopped. Said the first business.
- the method further includes:
- the foregoing uses a plurality of pre-built service recovery threads, and performs service path recovery calculation on the services in the service list according to a plurality of pre-built multiple service data required for service recovery, and completes each After the step of recovering the business path of the service, the method further includes:
- An embodiment of the present invention further provides an apparatus for dynamically recovering services, including:
- the service list module is configured to obtain an instruction for interrupting a service in the transmission network, and determine a service list of the service affected by the service interruption;
- Business recovery module set to use multiple pre-built business recovery threads, and based on advance The first service data required for service recovery is constructed, and the service path recovery calculation is performed on the services in the service list, and the service path recovery of each service is completed.
- the service recovery module includes:
- a first recovery unit configured to select a first thread of the plurality of service recovery threads as a processing thread of the first service in the service list, according to the first service data corresponding to the first thread, to enable the first A thread performs a service path recovery calculation on the first service;
- a second recovery unit configured to select a second thread of the plurality of service recovery threads as a processing thread of the second service in the service list, according to the first service data corresponding to the second thread, to enable the first The second thread performs a service path recovery calculation on the second service.
- the first recovery unit includes:
- Determining a subunit configured to enable the first thread to determine a first corresponding service after the first service is rerouted
- a processing subunit configured to determine that the first service data meets a rerouting requirement of the first corresponding service, so that the first thread modifies a location corresponding to the first thread according to the route of the first corresponding service
- the first service data is described, and the service path recovery calculation for the first service is completed.
- the first recovery unit further includes:
- An update subunit configured to enable the first thread to modify the second service data according to the route of the first corresponding service; where the second service data is pre-built, including network topology information and a link required for service recovery Bandwidth information.
- the first recovery unit further includes:
- the determining subunit is configured to determine whether the second service data meets the rerouting requirement of the first corresponding service, and when the determination result is yes, modify the second service data according to the route of the first corresponding service And determining, when the determination result is no, the first corresponding service after the first service is re-routed again.
- the device further includes:
- the update module is configured to monitor a content change of the second service data, and when the content of the second service data changes, modify each of the first service data according to the changed second service data.
- An embodiment of the present invention further provides a software defined network SDN controller, comprising the apparatus for dynamic service recovery according to any of the preceding claims.
- the embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the above method.
- the foregoing technical solution of the embodiment of the present invention performs a service path recovery calculation on a service in a service list affected by the interruption according to a plurality of pre-built multiple service data by using a plurality of pre-built service recovery threads, thereby completing each service.
- the service path is restored, and the efficiency is ensured.
- the time for ensuring the service recovery is within the required range, and the purpose of rapid recovery is achieved.
- FIG. 1 is a schematic flowchart diagram of a method for dynamically recovering services according to an embodiment of the present invention
- FIG. 2 is a schematic structural diagram of an apparatus for dynamically recovering services according to an embodiment of the present invention
- Fig. 3 shows a network topology diagram in an application example of the present invention.
- the embodiment of the present invention provides a method, a device, and a software-defined network SDN controller for service dynamic recovery, which are difficult to ensure that a large number of services requiring dynamic recovery are completed in a few seconds, and recovers by using multiple pre-built services.
- the thread performs the service path recovery calculation on the service in the service list affected by the interruption according to the pre-built multiple first service data, thereby completing the service path recovery of each service, and having high efficiency, ensuring that the service recovery time is within the required range. , to achieve the purpose of rapid recovery.
- FIG. 1 is a schematic flowchart of a method for dynamically recovering services according to an embodiment of the present invention.
- the embodiment of the present invention provides a method for dynamically recovering services, which is applied to a software-defined network SDN controller, including:
- Step 101 Obtain an instruction for interrupting a service in the transmission network, and determine a service list of the service affected by the service interruption.
- step 102 a plurality of service recovery threads are pre-built, and the service path recovery calculation is performed on the services in the service list according to the plurality of pre-built first service data required for service recovery, and each service is completed.
- Business path recovery is performed on the services in the service list according to the plurality of pre-built first service data required for service recovery, and each service is completed.
- step 101 determines a service list of services affected by service interruption in the transmission network, and lists all services affected by all optical fiber interruptions or node failures, and then step 102 utilizes multiple service recovery.
- the thread performs the service path recovery calculation on the service in the service list according to the first service data required for the service recovery, re-routes the service in the service list, and completes the service path recovery of each service; wherein the service recovery thread And the first service data is pre-built to ensure that the service recovery thread can perform the service path recovery calculation on the service in the service list in time after the fiber break or the node fails.
- the above embodiment of the present invention ensures that the time for service recovery is within the required range and achieves the purpose of rapid recovery.
- a plurality of service recovery threads and a plurality of first service data are pre-built, and the first service data includes network topology information and link bandwidth information required for service recovery, and required for the service recovery.
- the network topology information and the link bandwidth information are the same as the network topology information and the network bandwidth information that are actually running, wherein the number of service recovery threads is the same as the number of the first service data, so that the service recovery thread has a one-to-one correspondence with the first service data, and
- the number of service recovery threads matches the central processor CPU resources of the transport network system, so that as long as the physical computer CPU resources are increased, the efficiency of service recovery is higher.
- the plurality of service recovery threads are operated in parallel, that is, in step 102, the first thread of the plurality of service recovery threads is selected as the processing thread of the first service in the service list, Determining, by the first thread, a service path recovery calculation for the first service according to the first service data corresponding to the first thread;
- the K value matches the CPU of the central processing unit, and when the number of services in the service list is less than K, It is only necessary to select N service recovery threads and corresponding N first service data from the K service recovery threads and the K first service data, so that the services in the service list are processed in parallel, where N is equal to the number of services in the service list; When the number of services in the service list is greater than K, then N is equal to K, and the remaining services in the service list are waiting for idle thread acquisition processing.
- the step of performing a service path recovery calculation on the service in each selected service list in each of the service recovery threads for example, in the step of performing a service path recovery calculation on the first service by the first thread
- the first service data meets the re-routing requirement of the first corresponding service, that is, the first service data can meet the link bandwidth information requirement required by any service path of the first corresponding service, so that the first thread is And modifying the first service data corresponding to the first thread according to the route of the first corresponding service, and completing a service path recovery calculation for the first service.
- the first thread modifies the first service data corresponding to the first thread according to the route of the first corresponding service
- the first thread is configured to modify the second route according to the route of the first corresponding service.
- the second service data records the initialization data of all service network topologies and corresponding link bandwidth information in the network transmission, which is the same as the actual network operation data, and the first service data is the same as the second service data before the service is restored.
- the first thread modifies the write operation of the update process of the second service data according to the route of the first corresponding service as a transaction, so as to ensure that the second service data is consistent with the actual link remaining bandwidth, and the remaining bandwidth of the link is The total bandwidth of the link minus the bandwidth occupied by all services passing through this link.
- the second service data Before determining, by the first thread, the second service data according to the route of the first corresponding service, determining whether the second service data meets a re-routing requirement of the first corresponding service, that is, determining the When the link bandwidth information required for any service path of a corresponding service is smaller than the corresponding link bandwidth information of the second service data, that is, the corresponding chain in the second service data.
- the route bandwidth is sufficient for the route of any service path of the first corresponding service, the second service data meets the re-routing requirement of the first corresponding service; and the link required for determining any service path of the first corresponding service
- the bandwidth information is greater than or equal to the corresponding link bandwidth information in the second service data, the second service data does not meet the re-routing requirement of the first corresponding service.
- the second service data is modified according to the route of the first corresponding service, and when the determination result is no, the first corresponding service after the first service is re-routed is determined, and After determining that the first service data meets the re-routing requirement of the first corresponding service, the first thread is configured to modify the first service data corresponding to the first thread according to the route of the first corresponding service, and determine again Whether the second service data meets the re-routing requirement of the first corresponding service. If the result of the determination is no, the first service is re-routed by the preset number of times, and the second service data is still unable to meet the first corresponding service after the re-routing, and the first service is stopped and the log is stopped. The first service is recorded, and the number of reroutings of the first service may be set according to actual operation conditions, so that the service recovery efficiency is higher and the success rate of service recovery is met.
- the content of the second service data is changed during the service recovery process, and when the content of the second service data changes, each of the first services is modified according to the changed second service data. data.
- the first service data is updated by the second service data, so that the service recovery thread obtains higher accuracy according to the first service data and performs service recovery calculation on the service in the service list, so that the efficiency of service recovery is greater. improve.
- the monitoring the content change of the second service data and modifying the update process of each of the first service data according to the second service data is concurrent with the service path recovery calculation process of each service recovery thread, and the update process does not need to be performed. Interact to ensure the efficiency of business recovery.
- each service in the service list is deleted from the service list; when the service in the service list is empty, the service is ended.
- the embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the above method.
- the service recovery thread and the first service data matched with the service data are pre-built, that is, 10 service recovery threads are pre-built.
- 10 copies of the first service data, and each of the first service data is named data 1 - data 10; at the same time, a second service data is stored, each of the first service data and the second service data is the same, and the network is recorded
- the topology initializes the bandwidth information.
- the first service data and the second service data are as shown in Table 1 below.
- the remaining bandwidth represents link bandwidth information in the first service data and the second service data
- the link represents network topology information
- FIG. 3 is a network topology diagram of an application example of the present invention.
- the BE link is interrupted, and three services affected by the BE link interruption are assumed, and services for services affected by the service interruption are determined.
- List the business list is shown in Table 2 below.
- Three service recovery threads are taken as processing threads from the 10 service recovery threads, which are respectively the first thread, the second thread, and the third thread, and the three service recovery threads are respectively named as data 1, data 2, and data 3.
- First business data The first thread performs the service path recovery calculation on the service 1 according to the data 1
- the second thread performs the service path recovery calculation on the service 2 according to the data 2
- the third thread performs the service path recovery calculation on the service 3 according to the data 3.
- the service recovery of the three service recovery threads is processed in parallel.
- the service re-routing strategy is a minimum hop, and it is assumed that three services in the service list complete the service recovery in sequence.
- the first thread determines the corresponding service 1' after the service 1 performs rerouting, determines that the data 1 satisfies the rerouting requirement of the corresponding service 1', and the first thread modifies the data 1 according to the route of the corresponding service 1', in parallel, the second thread determines After the service 2 performs the rerouting service 2', the judgment data 2 satisfies the rerouting requirement of the corresponding service 2', the second thread modifies the data 2 according to the route of the corresponding service 2', and the third thread determines that the service 3 performs the rerouting Corresponding to the service 3', the judgment data 3 satisfies the rerouting requirement of the corresponding service 3', and the third thread modifies the data 3 according to the route of the corresponding service
- the second service data is judged to satisfy the rerouting request of the corresponding service 1', and the first thread modifies the second service data according to the route of the corresponding service 1'. Service 1 is restored and the service 1 in the service list is deleted.
- the second service data is shown in Table 4 below.
- Each first service data is modified according to the content change of the second service data, that is, 10 pieces of first service data of the data 1 to 10 are updated.
- the service 1 completes the service recovery
- the corresponding service 2' re-routing of the service 2 is completed, and the data 2 satisfies the re-routing requirement of the corresponding service 2'
- the second thread modifies the data 2 according to the route of the corresponding service 2', after which the judgment is performed.
- the second service data satisfies the rerouting requirement of the corresponding service 2', so that the second thread modifies the second service data according to the route of the corresponding service 2'.
- Service 2 is restored and the service 2 in the service list is deleted.
- the second service data is shown in Table 5 below.
- each first service data is modified according to the content change of the second service data, that is, 10 pieces of first service data of the data 1 to 10 are updated.
- the third thread modifies the data 3 according to the route corresponding to the service 3', it is determined whether the second service data meets the re-routing requirement of the corresponding service 3', that is, the link bandwidth information required to determine any service path of the corresponding service 3' is smaller than
- the second service data satisfies the re-routing requirement of the corresponding service 3', where the link bandwidth information required for the BH in the service 3' is determined (500M)
- the link bandwidth information (500M) required by the HI and the HI is greater than the corresponding BH remaining bandwidth (0M) and the HI remaining bandwidth (0M) in the second service data, respectively, so the second service data does not satisfy the rerouting of the corresponding service 3'
- Each first service data is modified according to the content change of the second service data, that is, 10 pieces of first service data of the data 1 to 10 are updated.
- the three services in the service list are all restored, the service list is empty, and the service recovery ends.
- FIG. 2 is a schematic structural diagram of an apparatus for dynamically recovering services according to an embodiment of the present invention.
- a device for dynamically recovering services is provided, which includes:
- the service list module 21 is configured to obtain an instruction for interrupting a service in the transmission network, and determine a service list of the service affected by the service interruption;
- the service recovery module 22 is configured to adopt a plurality of pre-built service recovery threads, and perform service path recovery calculation on the services in the service list according to the plurality of pre-built first service data required for service recovery. Complete the business path recovery for each business.
- the service list module 21 is configured to determine a service list of services affected by service interruption in the transmission network, and the list lists all services affected by all optical fiber interruptions or node failures, and then the service recovery module. 22 is configured to perform service path recovery calculation on the service in the service list by using multiple pre-built service recovery threads and multiple copies of the first service data required for service recovery, re-routing the services in the service list, and completing each
- the service path recovery of the service ensures that the service recovery thread can perform the service path recovery calculation for the service in the service list in time after the fiber break or the node fails, ensuring that the service recovery time is within the required range and achieves the purpose of rapid recovery. .
- the service recovery module 22 includes:
- a first recovery unit configured to select a first thread of the plurality of service recovery threads as a processing thread of the first service in the service list, according to the first service data corresponding to the first thread, to enable the first A thread performs a service path recovery calculation on the first service;
- a second recovery unit configured to select a second thread of the plurality of service recovery threads as a processing thread of the second service in the service list, according to the first service data corresponding to the second thread, And causing the second thread to perform a service path recovery calculation on the second service.
- the first recovery unit includes:
- Determining a subunit configured to enable the first thread to determine a first corresponding service after the first service is rerouted
- a processing subunit configured to determine that the first service data meets a rerouting requirement of the first corresponding service, so that the first thread modifies a location corresponding to the first thread according to the route of the first corresponding service
- the first service data is described, and the service path recovery calculation for the first service is completed.
- the first recovery unit further includes:
- An update subunit configured to enable the first thread to modify the second service data according to the route of the first corresponding service; where the second service data is pre-built, including network topology information and a link required for service recovery Bandwidth information.
- the first recovery unit further includes:
- the determining subunit is configured to determine whether the second service data meets the rerouting requirement of the first corresponding service, and when the determination result is yes, modify the second service data according to the route of the first corresponding service And determining, when the determination result is no, the first corresponding service after the first service is re-routed again.
- the device further includes:
- the update module is configured to monitor a content change of the second service data, and when the content of the second service data changes, modify each of the first service data according to the changed second service data.
- An embodiment of the present invention further provides a software defined network SDN controller, comprising the apparatus for dynamic service recovery according to any of the preceding claims.
- the foregoing embodiment of the present invention determines the service list of the service affected by the service interruption in the transmission network, and uses multiple service recovery threads to perform service path recovery on the service in the service list according to the first service data required for service recovery. Calculating, re-routing the service in the service list, and completing the service path recovery of each service; wherein the service recovery thread and the first service data are pre-built, and the service recovery can be timely invoked after the fiber break or the node fails. Thread to industry The service in the service list performs the service path recovery calculation to ensure that the service recovery time is within the required range and achieves the purpose of rapid 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. / instruction to achieve its corresponding function.
- the invention is not limited to any specific form of combination of hardware and software.
- the above technical solution can complete the service path recovery of each service, and has high efficiency, ensuring that the time for service recovery is within the required range, and achieves the purpose of rapid recovery.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
一种业务动态恢复的方法、装置及软件定义网络SDN控制器。所述方法应用于软件定义网络SDN控制器，包括：获得传输网络中业务中断的指令，确定所述业务中断所影响业务的业务列表；采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复。上述技术方案的业务动态恢复具备高效性，保证业务恢复的时间在要求范围内，达到快速恢复的目的。
Description
本文涉及但不限于电信网络管理技术领域，特别是指一种业务动态恢复的方法、装置及软件定义网络SDN控制器。
在软件定义网络(Software Defined Network，SDN)技术引入传输网络系统后，设备只需维护好业务流表，保证数据实时、准确的传输。当发生业务流中断后，SDN控制器业务会启动动态恢复功能来处理。但是当传输网络一根或多根光纤中断或节点失效后，会造成数以万计的业务中断，而动态恢复业务的时间要求是在秒级的，这样大量需要动态恢复的业务在数秒内完成恢复，而这对于SDN控制器来说是一个重大难题。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种业务动态恢复的方法、装置及软件定义网络SDN控制器，以解决如何实现因光纤中断或节点失效造成的中断业务得到快速恢复的技术问题。
本发明的实施例提供一种业务动态恢复的方法，应用于软件定义网络SDN控制器，包括：
获得传输网络中业务中断的指令，确定所述业务中断所影响业务的业务列表；
采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复。
其中，所述获得传输网络中业务中断的指令，确定所述业务中断所影响的业务列表之前，所述方法还包括：
预先构建多个业务恢复线程和多份所述第一业务数据，且所述业务恢复线程的数量和所述第一业务数据的数量相同，所述业务恢复线程的数量与传输网络系统的中央处理器CPU资源匹配，所述第一业务数据包括业务恢复所需要的网络拓扑信息以及链路带宽信息。
可选的，所述采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复的步骤，包括：
选取多个业务恢复线程中的第一线程为所述业务列表中的第一业务的处理线程，依据所述第一线程相对应的第一业务数据，使所述第一线程对第一业务进行业务路径恢复计算；同时
选取多个业务恢复线程中的第二线程为所述业务列表中的第二业务的处理线程，依据所述第二线程相对应的第一业务数据，使所述第二线程对第二业务进行业务路径恢复计算。
其中，依据所述第一线程相对应的第一业务数据，使所述第一线程对第一业务进行业务路径恢复计算的步骤包括：
使所述第一线程确定所述第一业务进行重路由后的第一对应业务；
判断所述第一业务数据满足所述第一对应业务的重路由要求，使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业务数据，完成对第一业务的业务路径恢复计算。
其中，所述使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业务数据的步骤之后，所述方法还包括：
使所述第一线程根据所述第一对应业务的路由修改第二业务数据；其中所述第二业务数据为预先构建，包括业务恢复所需要的网络拓扑信息以及链路带宽信息。
其中，在使所述第一线程根据所述第一对应业务的路由修改第二业务数据之前，所述方法还包括：
判断所述第二业务数据是否满足所述第一对应业务的重路由要求，当判断结果为是时，根据所述第一对应业务的路由对应修改所述第二业务数据，以及当判断结果为否时，确定所述第一业务再次重路由后的第一对应业务。
其中，所述判断所述第二业务数据是否满足所述第一对应业务重路由要求的步骤，包括：
判断所述第一对应业务的任一业务路径所需的链路带宽信息小于所述第二业务数据中对应的链路带宽信息时，所述第二业务数据满足所述第一对应业务的重路由要求；判断所述第一对应业务的任一业务路径所需的链路带宽信息大于或等于所述第二业务数据中对应的链路带宽信息时，所述第二业务数据不满足所述第一对应业务的重路由要求。
其中，所述判断所述第二业务数据是否满足所述第一对应业务的重路由要求的步骤中：
当判断结果为否，对第一业务经过预设次数的再次重路由，所述第二业务数据仍不能满足再次重路由后的第一对应业务时，停止恢复所述第一业务，日志记录所述第一业务。
其中，所述方法还包括：
监测第二业务数据的内容变化，当所述第二业务数据的内容发生变化时，根据变化后的所述第二业务数据，修改每一所述第一业务数据。
其中，所述采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复的步骤之后，所述方法还包括：
每一业务的业务路径恢复完成或停止恢复后，删除所述业务列表中的对应业务；
当所述业务列表中的所述业务为空时，业务恢复结束。
本发明的实施例还提供一种业务动态恢复的装置，包括：
业务列表模块，设置为获得传输网络中业务中断的指令，确定所述业务中断所影响业务的业务列表；
业务恢复模块，设置为采用预先构建的多个业务恢复线程，并依据预先
构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复。
可选的，所述业务恢复模块包括：
第一恢复单元，设置为选取多个业务恢复线程中的第一线程为所述业务列表中的第一业务的处理线程，依据所述第一线程相对应的第一业务数据，使所述第一线程对第一业务进行业务路径恢复计算；同时
第二恢复单元，设置为选取多个业务恢复线程中的第二线程为所述业务列表中的第二业务的处理线程，依据所述第二线程相对应的第一业务数据，使所述第二线程对第二业务进行业务路径恢复计算。
可选的，所述第一恢复单元包括：
确定子单元，设置为使所述第一线程确定所述第一业务进行重路由后的第一对应业务；
处理子单元，设置为判断所述第一业务数据满足所述第一对应业务的重路由要求，使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业务数据，完成对第一业务的业务路径恢复计算。
可选的，所述第一恢复单元还包括：
更新子单元，设置为使所述第一线程根据所述第一对应业务的路由修改第二业务数据；其中所述第二业务数据为预先构建，包括业务恢复所需要的网络拓扑信息以及链路带宽信息。
可选的，所述第一恢复单元还包括：
判断子单元，设置为判断所述第二业务数据是否满足所述第一对应业务的重路由要求，当判断结果为是时，根据所述第一对应业务的路由对应修改所述第二业务数据，以及当判断结果为否时，确定所述第一业务再次重路由后的第一对应业务。
可选的，所述装置还包括：
更新模块，设置为监测第二业务数据的内容变化，当所述第二业务数据的内容发生变化时，根据变化后的所述第二业务数据，修改每一所述第一业务数据。
本发明的实施例还提供一种软件定义网络SDN控制器，包括如上述任一项所述的业务动态恢复的装置。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行上述的方法。
本发明实施例的上述技术方案的有益效果如下：
本发明实施例的上述技术方案通过使用预先构建的多个业务恢复线程根据预先构建的多份第一业务数据对中断所影响的业务列表中的业务进行业务路径恢复计算，从而完成每一业务的业务路径恢复，具备高效性，保证业务恢复的时间在要求范围内，达到快速恢复的目的。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1表示本发明实施例的业务动态恢复的方法的流程示意图；
图2表示本发明实施例的业务动态恢复的装置的结构示意图；
图3表示本发明应用示例中的网络拓扑图。
下面将结合附图及具体实施例进行详细描述。
本发明实施例针对相关的难以保证大量需要动态恢复的业务在数秒内完成恢复的问题，提供一种业务动态恢复的方法、装置及软件定义网络SDN控制器，通过使用预先构建的多个业务恢复线程根据预先构建的多份第一业务数据对中断所影响的业务列表中的业务进行业务路径恢复计算，从而完成每一业务的业务路径恢复，具备高效性，保证业务恢复的时间在要求范围内，达到快速恢复的目的。
如图1所示为本发明实施例的业务动态恢复的方法的流程示意图，本发明实施例提供一种业务动态恢复的方法，应用于软件定义网络SDN控制器，包括：
步骤101，获得传输网络中业务中断的指令，确定所述业务中断所影响业务的业务列表；
步骤102，采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复。
在本发明上述实施例中，步骤101确定传输网络中业务中断所影响业务的业务列表，该列表中罗列了所有光纤发生中断或节点失效后所影响的所有业务，然后步骤102利用多个业务恢复线程依据多份用于业务恢复所需要的第一业务数据对业务列表中的业务进行业务路径恢复计算，对业务列表中的业务重路由，完成每一业务的业务路径恢复；其中该业务恢复线程和第一业务数据皆为预先构建，保证在光纤发生中断或节点失效后能够及时调用该业务恢复线程对业务列表中的业务进行业务路径恢复计算。本发明的上述实施例保证了业务恢复的时间在要求范围内，达到快速恢复的目的。
本发明的上述实施例中，预先构建多个业务恢复线程和多份第一业务数据，该第一业务数据包括业务恢复所需要的网络拓扑信息以及链路带宽信息，且该业务恢复所需要的网络拓扑信息以及链路带宽信息与实际运行的网络拓扑信息和网络带宽信息相同，其中业务恢复线程的数量和第一业务数据的数量相同，使业务恢复线程与第一业务数据一一对应，并且该业务恢复线程的数量与传输网络系统的中央处理器CPU资源匹配，这样只要增加物理计算机CPU资源，则业务恢复的效率越高。
在本发明的上述实施例中，多个业务恢复线程是并行操作的，即在步骤102中，选取多个业务恢复线程中的第一线程为所述业务列表中的第一业务的处理线程，依据所述第一线程相对应的第一业务数据，使所述第一线程对第一业务进行业务路径恢复计算；同时
选取多个业务恢复线程中的第二线程为所述业务列表中的第二业务的处理线程，依据所述第二线程相对应的第一业务数据，使所述第二线程对第二业务进行业务路径恢复计算。
这里，可以理解的，通过预先构建K个业务恢复线程和K份第一业务数据，K值与中央处理器CPU资源匹配，当业务列表中的业务数量小于K时，
只需从K个业务恢复线程和K份第一业务数据中选取N个业务恢复线程和对应N份第一业务数据，使其并行处理业务列表中业务，其中N等于业务列表中业务数量；当业务列表中的业务数量大于K时，则N等于K，业务列表中的剩余业务等待空闲线程获取处理。
这样多个业务恢复线程同时对业务列表中的业务进行业务路径恢复计算，在并行处理下，多个业务的恢复处理互不影响，使业务恢复达到高效处理的效果。
其中，在每一个业务恢复线程对每一个选取的业务列表中的业务进行业务路径恢复计算的步骤中，如第一线程对第一业务进行业务路径恢复计算的步骤中，
使所述第一线程确定所述第一业务进行重路由后的第一对应业务，即第一线程通过对第一业务进行业务路径计算得出的一个第一对应业务；
判断所述第一业务数据满足所述第一对应业务的重路由要求，即第一业务数据能够满足第一对应业务的任一业务路径所需的链路带宽信息要求，使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业务数据，完成对第一业务的业务路径恢复计算。
其中，当第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业务数据之后，使所述第一线程根据所述第一对应业务的路由修改第二业务数据；其中所述第二业务数据为预先构建，包括业务恢复所需要的网络拓扑信息以及链路带宽信息。该第二业务数据记录网络传输中所有业务网络拓扑及对应链路带宽信息的初始化数据，其与实际网络运行数据相同，且在业务进行恢复前第一业务数据与该第二业务数据相同。此外，第一线程根据第一对应业务的路由修改第二业务数据的更新过程的写操作为事务处理，从而保证第二业务数据与实际的链路剩余带宽是一致的，链路剩余带宽即为链路总带宽减去经过此链路所有业务占用带宽。
其中，在使所述第一线程根据所述第一对应业务的路由修改第二业务数据之前，判断所述第二业务数据是否满足所述第一对应业务的重路由要求，即判断所述第一对应业务的任一业务路径所需的链路带宽信息小于所述第二业务数据中对应的链路带宽信息时，也就是说所述第二业务数据中对应的链
路带宽足够第一对应业务的任一业务路径的路由，所述第二业务数据满足所述第一对应业务的重路由要求；判断所述第一对应业务的任一业务路径所需的链路带宽信息大于或等于所述第二业务数据中对应的链路带宽信息时，所述第二业务数据不满足所述第一对应业务的重路由要求。当判断结果为是时，根据所述第一对应业务的路由对应修改所述第二业务数据，以及当判断结果为否时，确定所述第一业务再次重路由后的第一对应业务，重新判断第一业务数据满足所述第一对应业务的重路由要求后，使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的第一业务数据，并再次判断第二业务数据是否满足所述第一对应业务的重路由要求。当判断结果为否，对第一业务经过预设次数的再次重路由，所述第二业务数据仍不能满足再次重路由后的第一对应业务时，停止恢复所述第一业务，并通过日志记录所述第一业务，其中第一业务的重路由次数可以依据实际操作的情况进行设置，使其更符合业务恢复高效率、以及满足业务恢复的成功率的要求。
其中，在进行业务恢复过程中，监测第二业务数据的内容变化，当所述第二业务数据的内容发生变化时，根据变化后的所述第二业务数据，修改每一所述第一业务数据。这样通过第二业务数据更新第一业务数据，使业务恢复线程依据第一业务数据对业务列表中业务进行业务恢复计算得到的对应业务具备更高的准确性，从而业务恢复的效率得到更大的提高。当然，该监测第二业务数据的内容变化并根据第二业务数据修改每一所述第一业务数据的更新过程与每一业务恢复线程的业务路径恢复计算过程是并发的，且该更新过程无需进行交互，从而保证业务恢复的高效性。
另外，业务列表中每一业务的在业务路径恢复完成或者停止恢复之后，从业务列表中删除该业务；当业务列表中的业务为空时，业务恢复结束。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行上述的方法。
在本发明一应用示例中，假定传输网络系统的CPU为10核，则预先构建与其匹配的业务恢复线程和第一业务数据，即预先构建10个业务恢复线程
和10份第一业务数据，并对每份第一业务数据命名为数据1-数据10；同时在存储一份第二业务数据，每份第一业务数据和第二业务数据相同，记录有网络拓扑初始化带宽信息。第一业务数据和第二业务数据都如下表1所示。
表1
| 链路 | 总带宽(M) | 剩余带宽(M) |
| AC | 1000 | 1000 |
| AF | 1000 | 1000 |
| FB | 1000 | 500 |
| CB | 1000 | 1000 |
| BH | 1000 | 1000 |
| BE | 2000 | 500 |
| CD | 2000 | 2000 |
| DE | 1000 | 1000 |
| EI | 2000 | 500 |
| DG | 1000 | 1000 |
| GK | 1000 | 1000 |
| IK | 1000 | 500 |
| HI | 1000 | 1000 |
在该表1中，剩余带宽(总带宽减去经过此链路所有业务占用带宽)表示第一业务数据和第二业务数据中的链路带宽信息，链路表示网络拓扑信息。
如图3所示为本发明一应用示例中的网络拓扑图，在该传输网络中，BE链路发生中断，假定BE链路中断所影响的业务有3条，确定业务中断所影响业务的业务列表，所述业务列表如下表2所示。
表2
| 业务 | 业务路由 | 业务带宽(M) |
| 业务1 | F-B-E-I | 500 |
| 业务2 | B-E-I | 500 |
| 业务3 | B-E-I-K | 500 |
从10个业务恢复线程取其中3个业务恢复线程作为处理线程，分别为第一线程、第二线程、第三线程，且3个业务恢复线程分别对应命名为数据1、数据2、数据3的第一业务数据。第一线程依据数据1对业务1进行业务路径恢复计算，第二线程依据数据2对业务2进行业务路径恢复计算，第三线程依据数据3对业务3进行业务路径恢复计算。3个业务恢复线程的业务恢复是并行处理的。
为更清楚明白的描述本发明实施例，在该应用示例中，假定业务重路由策略是最小跳，并且假设业务列表中的3个业务依次完成业务恢复。第一线程确定业务1进行重路由后的对应业务1’，判断数据1满足对应业务1’的重路由要求，第一线程根据对应业务1’的路由修改数据1，并行的，第二线程确定业务2进行重路由后的对应业务2’，判断数据2满足对应业务2’的重路由要求，第二线程根据对应业务2’的路由修改数据2，第三线程确定业务3进行重路由后的对应业务3’，判断数据3满足对应业务3’的重路由要求，第三线程根据对应业务3’的路由修改数据3，如下表3所示。
表3
| 业务 | 业务路由 | 业务带宽(M) |
| 业务1’ | F-B-H-I | 500 |
| 业务2’ | B-H-I | 500 |
| 业务3’ | B-H-I-K | 500 |
由于3个线程对3个业务依次重路由业务确定，之后，判断第二业务数据满足对应业务1’的重路由要求，第一线程根据对应业务1’的路由修改第二业务数据。业务1恢复完成，删除业务列表中的业务1。第二业务数据如下表4所示。
表4
| 链路 | 总带宽(M) | 剩余带宽(M) |
| AC | 1000 | 1000 |
| AF | 1000 | 1000 |
| FB | 1000 | 500 |
| CB | 1000 | 1000 |
| BH | 1000 | 500 |
| BE | 2000 | 500 |
| CD | 2000 | 2000 |
| DE | 1000 | 1000 |
| EI | 2000 | 500 |
| DG | 1000 | 1000 |
| GK | 1000 | 1000 |
| IK | 1000 | 500 |
| HI | 1000 | 500 |
根据检测到第二业务数据的内容变化，修改每个第一业务数据，即更新数据1-数据10这10份第一业务数据。在业务1完成业务恢复后，业务2的对应业务2’重路由完成，且数据2满足对应业务2’的重路由要求，第二线程根据对应业务2’的路由修改数据2，之后，判断第二业务数据满足对应业务2’的重路由要求，使第二线程根据对应业务2’的路由修改第二业务数据。业务2恢复完成，删除业务列表中的业务2。第二业务数据如下表5所示。
表5
| 链路 | 总带宽(M) | 剩余带宽(M) |
| AC | 1000 | 1000 |
| AF | 1000 | 1000 |
| FB | 1000 | 500 |
| CB | 1000 | 1000 |
| BH | 1000 | 0 |
| BE | 2000 | 500 |
| CD | 2000 | 2000 |
| DE | 1000 | 1000 |
| EI | 2000 | 500 |
| DG | 1000 | 1000 |
| GK | 1000 | 1000 |
| IK | 1000 | 500 |
| HI | 1000 | 0 |
同样的，根据检测到第二业务数据的内容变化，修改每个第一业务数据，即更新数据1-数据10这10份第一业务数据。
第三线程根据对应业务3’的路由修改数据3之后，判断第二业务数据是否满足对应业务3’的重路由要求，即判断对应业务3’的任一业务路径所需的链路带宽信息小于第二业务数据中对应的剩余带宽(链路带宽信息)时，第二业务数据满足所述对应业务3’的重路由要求，这里判断发现业务3’中BH所需的链路带宽信息(500M)和HI所需的链路带宽信息(500M)分别大于第二业务数据中对应的BH剩余带宽(0M)和HI剩余带宽(0M)，因此第二业务数据不满足对应业务3’的重路由要求，确定所业务3再次重路由后的对应业务3”，得到对应业务3”的业务路由为B-C-D-G-K，判断第二业务数据满足对应业务3”的重路由要求，第二线程根据对应业务3”的路由修改第二业务数据。业务3恢复完成，删除业务列表中的业务3。第二业务数据如下表6所示。
表6
| 链路 | 总带宽(M) | 剩余带宽(M) |
| AC | 1000 | 1000 |
| AF | 1000 | 1000 |
| FB | 1000 | 500 |
| CB | 1000 | 500 |
| BH | 1000 | 0 |
| BE | 2000 | 500 |
| CD | 2000 | 1500 |
| DE | 1000 | 1000 |
| EI | 2000 | 500 |
| DG | 1000 | 500 |
| GK | 1000 | 500 |
| IK | 1000 | 500 |
| HI | 1000 | 0 |
根据检测到第二业务数据的内容变化，修改每个第一业务数据，即更新数据1-数据10这10份第一业务数据。
业务列表中的3个业务都恢复完成，业务列表为空，业务恢复结束。
如图2所示为本发明实施例的业务动态恢复的装置的结构示意图，本发明实施例对应业务动态恢复的方法，提出了一种业务动态恢复的装置，包括：
业务列表模块21，设置为获得传输网络中业务中断的指令，确定所述业务中断所影响业务的业务列表；
业务恢复模块22，设置为采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复。
在本发明上述实施例中，业务列表模块21设置为确定传输网络中业务中断所影响业务的业务列表，该列表中罗列了所有光纤发生中断或节点失效后所影响的所有业务，然后业务恢复模块22设置为通过预先构建的多个业务恢复线程和多份用于业务恢复所需要的第一业务数据对业务列表中的业务进行业务路径恢复计算，对业务列表中的业务重路由，完成每一业务的业务路径恢复，保证了在光纤发生中断或节点失效后能够及时调用业务恢复线程对业务列表中的业务进行业务路径恢复计算，保证了业务恢复的时间在要求范围内，达到快速恢复的目的。
可选的，所述业务恢复模块22包括：
第一恢复单元，设置为选取多个业务恢复线程中的第一线程为所述业务列表中的第一业务的处理线程，依据所述第一线程相对应的第一业务数据，使所述第一线程对第一业务进行业务路径恢复计算；同时
第二恢复单元，设置为选取多个业务恢复线程中的第二线程为所述业务列表中的第二业务的处理线程，依据所述第二线程相对应的第一业务数据，
使所述第二线程对第二业务进行业务路径恢复计算。
可选的，所述第一恢复单元包括：
确定子单元，设置为使所述第一线程确定所述第一业务进行重路由后的第一对应业务；
处理子单元，设置为判断所述第一业务数据满足所述第一对应业务的重路由要求，使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业务数据，完成对第一业务的业务路径恢复计算。
可选的，所述第一恢复单元还包括：
更新子单元，设置为使所述第一线程根据所述第一对应业务的路由修改第二业务数据；其中所述第二业务数据为预先构建，包括业务恢复所需要的网络拓扑信息以及链路带宽信息。
可选的，所述第一恢复单元还包括：
判断子单元，设置为判断所述第二业务数据是否满足所述第一对应业务的重路由要求，当判断结果为是时，根据所述第一对应业务的路由对应修改所述第二业务数据，以及当判断结果为否时，确定所述第一业务再次重路由后的第一对应业务。
可选的，所述装置还包括：
更新模块，设置为监测第二业务数据的内容变化，当所述第二业务数据的内容发生变化时，根据变化后的所述第二业务数据，修改每一所述第一业务数据。
本发明的实施例还提供一种软件定义网络SDN控制器，包括如上述任一项所述的业务动态恢复的装置。
本发明的上述实施例通过确定传输网络中业务中断所影响业务的业务列表，利用多个业务恢复线程依据多份用于业务恢复所需要的第一业务数据对业务列表中的业务进行业务路径恢复计算，对业务列表中的业务重路由，完成每一业务的业务路径恢复；其中该业务恢复线程和第一业务数据皆为预先构建，保证在光纤发生中断或节点失效后能够及时调用该业务恢复线程对业
务列表中的业务进行业务路径恢复计算，保证了业务恢复的时间在要求范围内，达到快速恢复的目的。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本发明不限制于任何特定形式的硬件和软件的结合。
以上所述是本发明的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明所述原理的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本发明的保护范围。
上述技术方案能够完成每一业务的业务路径恢复，具备高效性，保证业务恢复的时间在要求范围内，达到快速恢复的目的。
Claims (18)
- 一种应用于软件定义网络SDN控制器的业务动态恢复的方法，包括：获得传输网络中业务中断的指令，确定所述业务中断所影响业务的业务列表；采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复。
- 根据权利要求1所述的方法，所述方法还包括：所述获得传输网络中业务中断的指令，确定所述业务中断所影响的业务列表之前，预先构建多个业务恢复线程和多份所述第一业务数据，且所述业务恢复线程的数量和所述第一业务数据的数量相同，所述业务恢复线程的数量与传输网络系统的中央处理器CPU资源匹配，所述第一业务数据包括业务恢复所需要的网络拓扑信息以及链路带宽信息。
- 根据权利要求1所述的方法，其中，所述采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复的步骤，包括：选取多个业务恢复线程中的第一线程为所述业务列表中的第一业务的处理线程，依据所述第一线程相对应的第一业务数据，使所述第一线程对第一业务进行业务路径恢复计算；同时选取多个业务恢复线程中的第二线程为所述业务列表中的第二业务的处理线程，依据所述第二线程相对应的第一业务数据，使所述第二线程对第二业务进行业务路径恢复计算。
- 根据权利要求3所述的方法，其中，依据所述第一线程相对应的第一业务数据，使所述第一线程对第一业务进行业务路径恢复计算的步骤包括：使所述第一线程确定所述第一业务进行重路由后的第一对应业务；判断所述第一业务数据满足所述第一对应业务的重路由要求，使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业 务数据，完成对第一业务的业务路径恢复计算。
- 根据权利要求4所述的方法，所述方法还包括：所述使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业务数据的步骤之后，使所述第一线程根据所述第一对应业务的路由修改第二业务数据；其中所述第二业务数据为预先构建，包括业务恢复所需要的网络拓扑信息以及链路带宽信息。
- 根据权利要求5所述的方法，所述方法还包括：在使所述第一线程根据所述第一对应业务的路由修改第二业务数据之前，判断所述第二业务数据是否满足所述第一对应业务的重路由要求，当判断结果为是时，根据所述第一对应业务的路由对应修改所述第二业务数据，以及当判断结果为否时，确定所述第一业务再次重路由后的第一对应业务。
- 根据权利要求6所述的方法，其中，所述判断所述第二业务数据是否满足所述第一对应业务重路由要求的步骤，包括：判断所述第一对应业务的任一业务路径所需的链路带宽信息小于所述第二业务数据中对应的链路带宽信息时，所述第二业务数据满足所述第一对应业务的重路由要求；判断所述第一对应业务的任一业务路径所需的链路带宽信息大于或等于所述第二业务数据中对应的链路带宽信息时，所述第二业务数据不满足所述第一对应业务的重路由要求。
- 根据权利要求6所述的方法，其中，所述判断所述第二业务数据是否满足所述第一对应业务的重路由要求的步骤，包括：当判断结果为否，对第一业务经过预设次数的再次重路由，所述第二业务数据仍不能满足再次重路由后的第一对应业务时，停止恢复所述第一业务，日志记录所述第一业务。
- 根据权利要求5所述的方法，所述方法还包括：监测第二业务数据的内容变化，当所述第二业务数据的内容发生变化时，根据变化后的所述第二业务数据，修改每一个所述第一业务数据。
- 根据权利要求1所述的方法，还包括：所述采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复 计算，完成每一业务的业务路径恢复的步骤之后，每一业务的业务路径恢复完成或停止恢复后，删除所述业务列表中的对应业务；当所述业务列表中的所述业务为空时，业务恢复结束。
- 一种业务动态恢复的装置，包括：业务列表模块，设置为获得传输网络中业务中断的指令，确定所述业务中断所影响业务的业务列表；业务恢复模块，设置为采用预先构建的多个业务恢复线程，并依据预先构建的多份用于业务恢复所需要的第一业务数据，对所述业务列表中的业务进行业务路径恢复计算，完成每一业务的业务路径恢复。
- 根据权利要求11所述的装置，其中，所述业务恢复模块包括：第一恢复单元，设置为选取多个业务恢复线程中的第一线程为所述业务列表中的第一业务的处理线程，依据所述第一线程相对应的第一业务数据，使所述第一线程对第一业务进行业务路径恢复计算；同时第二恢复单元，设置为选取多个业务恢复线程中的第二线程为所述业务列表中的第二业务的处理线程，依据所述第二线程相对应的第一业务数据，使所述第二线程对第二业务进行业务路径恢复计算。
- 根据权利要求12所述的装置，其中，所述第一恢复单元包括：确定子单元，设置为使所述第一线程确定所述第一业务进行重路由后的第一对应业务；处理子单元，设置为判断所述第一业务数据满足所述第一对应业务的重路由要求，使所述第一线程根据所述第一对应业务的路由修改与所述第一线程对应的所述第一业务数据，完成对第一业务的业务路径恢复计算。
- 根据权利要求13所述的装置，所述第一恢复单元还包括：更新子单元，设置为使所述第一线程根据所述第一对应业务的路由修改第二业务数据；其中所述第二业务数据为预先构建，包括业务恢复所需要的网络拓扑信息以及链路带宽信息。
- 根据权利要求14所述的装置，所述第一恢复单元还包括：判断子单元，设置为判断所述第二业务数据是否满足所述第一对应业务的重路由要求，当判断结果为是时，根据所述第一对应业务的路由对应修改 所述第二业务数据，以及当判断结果为否时，确定所述第一业务再次重路由后的第一对应业务。
- 根据权利要求14所述的装置，所述装置还包括：更新模块，设置为监测第二业务数据的内容变化，当所述第二业务数据的内容发生变化时，根据变化后的所述第二业务数据，修改每一所述第一业务数据。
- 一种软件定义网络SDN控制器，包括如权利要求11-16任一项所述的业务动态恢复的装置。
- 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1～10中任一项所述的方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510604269.5A CN106549865A (zh) | 2015-09-21 | 2015-09-21 | 业务动态恢复的方法、装置及软件定义网络sdn控制器 |
| CN201510604269.5 | 2015-09-21 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016165422A1 true WO2016165422A1 (zh) | 2016-10-20 |
Family
ID=57125740
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/070488 WO2016165422A1 (zh) | 2015-09-21 | 2016-01-08 | 业务动态恢复的方法、装置及软件定义网络sdn控制器 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106549865A (zh) |
| WO (1) | WO2016165422A1 (zh) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10484265B2 (en) | 2017-04-27 | 2019-11-19 | At&T Intellectual Property I, L.P. | Dynamic update of virtual network topology |
| US10979888B2 (en) | 2017-11-10 | 2021-04-13 | At&T Intellectual Property I, L.P. | Dynamic mobility network recovery system |
| WO2021212823A1 (zh) * | 2020-04-23 | 2021-10-28 | 中兴通讯股份有限公司 | 一种重新路由方法及装置、电子设备、计算机可读介质 |
| US11243882B2 (en) | 2020-04-15 | 2022-02-08 | International Business Machines Corporation | In-array linked list identifier pool scheme |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108282373B (zh) * | 2018-02-23 | 2021-01-26 | 烽火通信科技股份有限公司 | 基于sptn控制器快速恢复业务数据的系统及方法 |
| CN109474966A (zh) * | 2018-11-29 | 2019-03-15 | 努比亚技术有限公司 | 移动终端控制方法、移动终端及计算机可读存储介质 |
| CN112039764B (zh) * | 2019-06-03 | 2022-12-09 | 中兴通讯股份有限公司 | 一种实现重路由的方法及装置 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1866852A (zh) * | 2005-05-20 | 2006-11-22 | 华为技术有限公司 | 网络域中实现路径计算的方法 |
| CN101651625A (zh) * | 2009-09-03 | 2010-02-17 | 中兴通讯股份有限公司 | 多业务恢复的选路装置及选路方法 |
| WO2015007346A1 (en) * | 2013-07-19 | 2015-01-22 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for local path protection |
| CN104734954A (zh) * | 2015-03-27 | 2015-06-24 | 华为技术有限公司 | 一种用于软件定义网络的路由确定方法和装置 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102487329B (zh) * | 2010-12-02 | 2016-03-30 | 中兴通讯股份有限公司 | 业务恢复方法及装置 |
| CN102780604B (zh) * | 2011-05-13 | 2016-03-30 | 中兴通讯股份有限公司 | 计算预置恢复路由的方法及装置 |
| US20140317256A1 (en) * | 2013-04-17 | 2014-10-23 | Cisco Technology, Inc. | Loop and Outage Avoidance in Software Defined Network |
-
2015
- 2015-09-21 CN CN201510604269.5A patent/CN106549865A/zh active Pending
-
2016
- 2016-01-08 WO PCT/CN2016/070488 patent/WO2016165422A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1866852A (zh) * | 2005-05-20 | 2006-11-22 | 华为技术有限公司 | 网络域中实现路径计算的方法 |
| CN101651625A (zh) * | 2009-09-03 | 2010-02-17 | 中兴通讯股份有限公司 | 多业务恢复的选路装置及选路方法 |
| WO2015007346A1 (en) * | 2013-07-19 | 2015-01-22 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for local path protection |
| CN104734954A (zh) * | 2015-03-27 | 2015-06-24 | 华为技术有限公司 | 一种用于软件定义网络的路由确定方法和装置 |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10484265B2 (en) | 2017-04-27 | 2019-11-19 | At&T Intellectual Property I, L.P. | Dynamic update of virtual network topology |
| US10979888B2 (en) | 2017-11-10 | 2021-04-13 | At&T Intellectual Property I, L.P. | Dynamic mobility network recovery system |
| US11243882B2 (en) | 2020-04-15 | 2022-02-08 | International Business Machines Corporation | In-array linked list identifier pool scheme |
| WO2021212823A1 (zh) * | 2020-04-23 | 2021-10-28 | 中兴通讯股份有限公司 | 一种重新路由方法及装置、电子设备、计算机可读介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106549865A (zh) | 2017-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016165422A1 (zh) | 业务动态恢复的方法、装置及软件定义网络sdn控制器 | |
| US10949233B2 (en) | Optimized virtual network function service chaining with hardware acceleration | |
| US9870262B2 (en) | Processing element management in a streaming data system | |
| US9146775B2 (en) | Operator graph changes in response to dynamic connections in stream computing applications | |
| WO2017097130A1 (zh) | 一种分布式存储系统的服务节点切换方法和装置 | |
| US8990628B2 (en) | Unfusing a failing part of an operator graph | |
| KR102342063B1 (ko) | 네트워크 장애의 선제적 핸들링 기법 | |
| JP2015534769A (ja) | データネットワークにおける負荷分散 | |
| US9152491B2 (en) | Job continuation management apparatus, job continuation management method and job continuation management program | |
| CN104158693A (zh) | 数据服务的容灾备份方法和系统 | |
| US20150200802A1 (en) | Systems and methods for improved fault tolerance in solicited information handling systems | |
| CN105790825A (zh) | 一种分布式保护中控制器热备份的方法和装置 | |
| WO2016206502A1 (zh) | 一种业务控制方法及装置、计算机存储介质 | |
| US20180013613A1 (en) | System and method for managing network connections | |
| WO2021212823A1 (zh) | 一种重新路由方法及装置、电子设备、计算机可读介质 | |
| US20210120097A1 (en) | Scheduling solution configuration method and apparatus, computer readable storage medium thereof, and computer device | |
| CN117411840A (zh) | 链路故障处理方法、装置、设备、存储介质和程序产品 | |
| US20150163089A1 (en) | Method and apparatus for managing resources of transport network | |
| WO2017000845A1 (zh) | 一种流量控制方法及装置 | |
| CN109039822B (zh) | 一种bfd协议报文过滤方法及系统 | |
| CN106487561A (zh) | 一种服务器服务更新的方法和系统 | |
| KR100431208B1 (ko) | 멀티프로토콜 레이블 스위칭 시스템의 결함을 허용하는명시적 경로 관리방법 및 장치 | |
| US10567507B2 (en) | Message processing method and apparatus, and message processing system | |
| RU2675050C1 (ru) | Способ и устройство выбора адреса управления доступом к среде mac | |
| US20140122722A1 (en) | Allocation of resources in a networked computing environment |
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: 16779397 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16779397 Country of ref document: EP Kind code of ref document: A1 |