WO2018202141A1 - 业务恢复方法、装置及系统、存储介质、处理器 - Google Patents

业务恢复方法、装置及系统、存储介质、处理器 Download PDF

Info

Publication number
WO2018202141A1
WO2018202141A1 PCT/CN2018/085637 CN2018085637W WO2018202141A1 WO 2018202141 A1 WO2018202141 A1 WO 2018202141A1 CN 2018085637 W CN2018085637 W CN 2018085637W WO 2018202141 A1 WO2018202141 A1 WO 2018202141A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
connection
route
network element
alternate
Prior art date
Application number
PCT/CN2018/085637
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 中兴通讯股份有限公司
Publication of WO2018202141A1 publication Critical patent/WO2018202141A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery

Definitions

  • the present disclosure relates to the field of communications technologies, and, for example, to a service recovery method, apparatus and system, storage medium, and processor.
  • SDN Software Defined Network
  • the control plane of the SDN is separate from the data forwarding plane, enabling centralized control and programmable network operation. Due to the separation of the control plane and the data forwarding plane, when the service of the transport network fails, the SDN can be centralized and controlled to flexibly realize the dynamic recovery of the service.
  • the first service recovery based on SDN is that after the first service of the transport network fails, the SDN controller can recalculate the route for the first service of the fault and deliver the cross-connection to the relevant NE node to establish a cross-connection for the first service.
  • a new path to restore the first service thereby protecting the continuity of the first service.
  • the calculation of the new route and the configuration of the node are performed, so the first service needs to be restored. The time is longer, generally it is required to be within 1000ms. Therefore, the first service recovery efficiency is low.
  • the embodiment of the present application provides a service recovery method, device, system, storage medium, and processor, which improve the efficiency of service recovery.
  • An embodiment of the present application provides a service recovery method, where the method includes: after the first service is established, the information about the backup route of the first service is obtained, and the information about the backup route obtained by using the backup route is sent to the The network element node corresponding to the standby route saves the backup route connection in an inactive state on the network element node, where the backup route connection is saved in the inactive state on the network element node; After the first service is interrupted, the connection activation message is sent to the network element node corresponding to the alternate route of the first service, and the alternate route connection saved in the inactive state on the network element node is activated; The first service is restored.
  • the embodiment of the present application provides a service recovery system, where the system includes: a network element node, configured to receive, after the first service is established, information about an alternate route connection of the first service delivered by the controller, and Saving the alternate routing connection in an inactive state; receiving, after the first service interruption, a connection activation message delivered by the controller, wherein the connection activation message is used to save the inactive state
  • the alternate routing connection is activated, and the activated standby routing connection is used to instruct the controller to recover the first service according to the activated standby routing connection.
  • the controller is configured to: after the first service is established, the information about the backup route of the first service and the information of the backup route obtained by using the backup route is sent to the network element node corresponding to the backup route, where The standby routing connection is saved in the inactive state on the network element node; after the first service is interrupted, the connection activation message is sent to the network element node corresponding to the alternate route of the first service, and the pair is saved in an inactive state.
  • the alternate routing connection on the network element node is activated, wherein the alternate routing connection is saved in the inactive state on the network element node, and the first service is restored according to the activated standby routing connection.
  • the embodiment of the present application provides a service recovery apparatus, where the apparatus includes:
  • a second sending module configured to: after the first service is established, the information about the backup route of the first service and the information of the standby route obtained by using the backup route is sent to the network corresponding to the backup route Meta node.
  • the first sending module is configured to send a connection activation message to the network element node corresponding to the alternate route of the first service after the first service is interrupted, and activate the standby routing connection that is saved in the inactive state on the network element node.
  • the recovery module is configured to restore the first service according to the activated alternate routing connection.
  • An embodiment of the present application provides a service recovery apparatus, where the apparatus includes: a first receiving module, configured to receive, after the first service is established, information about an alternate route connection of the first service delivered by a controller, where And storing the alternate routing connection in an inactive state; the second receiving module is configured to receive a connection activation message sent by the controller after the first service is interrupted, where the connection activation message is used to The standby routing connection saved in the inactive state is activated, and the activated standby routing connection is used to instruct the controller to recover the first service according to the activated standby routing connection.
  • the embodiment of the present application provides a storage medium, where the storage medium includes a stored program, where the device where the storage medium is located is controlled to perform the foregoing service recovery method when the program is running.
  • the embodiment of the present application provides a processor, where the processor is configured to run a program, where the program is executed to execute the service recovery method described above.
  • the connection activation message is sent to the network element node corresponding to the alternate route of the service, and the alternate route connection saved in the inactive state on the network element node is activated, according to the activated
  • the backup route connection recovers the first service, and solves the problem that the service recovery efficiency is low due to the large amount of information exchanged between the network element and the controller after the service interruption in the service recovery process.
  • the problem is to improve the business recovery rate.
  • FIG. 1 is a schematic flowchart of a service recovery method according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a service recovery method according to another embodiment of the present application.
  • FIG. 4 is a structural block diagram of a service recovery apparatus according to an embodiment of the present application.
  • FIG. 5 is a structural block diagram of a service recovery apparatus according to another embodiment of the present application.
  • FIG. 6 is a structural block diagram of a service recovery apparatus according to still another embodiment of the present application.
  • FIG. 7 is a flowchart of a service before establishing a connection according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a working connection after an embodiment of the present application is established.
  • FIG. 9 is a schematic diagram of a pre-computed backup connection according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of the working connection interruption after recovery according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a standby connection resource occupied according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of re-establishing a backup connection resource after being occupied according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a multi-service simultaneous recovery use case according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of comparison of a service recovery method and related technologies according to an embodiment of the present application.
  • a route pre-computation technology can improve the efficiency of SDN first service recovery.
  • the route pre-computation is that after the first service is established, the SDN controller calculates an alternate route for the first service. After the first service fails, the route does not need to be recalculated. Instead, the backup route is used to recover the first service. The backup route does not occupy related physical resources and also saves network resources.
  • the route pre-computing technology improves the efficiency of the first service recovery, it only advances the route calculation part of the first service recovery process. However, this part of the operation process does not occupy a lot of time for the service recovery process. Another reason that affects the efficiency of the first service recovery is the transmission, transmission, and processing of messages between the network element and the controller.
  • the foregoing service recovery technology and route pre-computing technology are: after the service is interrupted, the controller sends a cross-connection message to the network element node, and each cross-connection corresponds to a cross-connect message, and the message usually also includes the complete Connection information, a large amount of information. Therefore, in a scenario where multiple first services need to be restored at the same time, the controller needs to deliver multiple connection recovery messages at the same time, and the amount of information is large, which seriously affects the efficiency of the first service recovery.
  • This embodiment provides a service recovery method, including the following first step and second step.
  • a connection activation message is sent to the network element node corresponding to the backup route of the first service, and an alternate route connection saved on the network element node in an inactive state is sent. Activate.
  • the first service is restored according to the activated alternate route connection.
  • FIG. 1 is a schematic flowchart of a service recovery method according to an embodiment of the present application, where the process includes:
  • Step 102 After the first service is established, the information about the backup route of the first service and the information of the backup route obtained by using the backup route is sent to the network element node corresponding to the backup route.
  • the alternate routing connection is saved on the network element node in an inactive state.
  • Step 104 After the first service is interrupted, send a connection activation message to the network element node corresponding to the alternate route of the first service, and activate the alternate route connection saved in the inactive state on the network element node.
  • connection activation message is sent to the network element node to activate a plurality of alternate routing connections corresponding to the plurality of first services stored in the inactive state on the network element node. That is, the connection activation message is sent to the network element node corresponding to the alternate route of the first service, and the standby route connection saved in the inactive state is activated, including: when the first service includes When a plurality of different services are used, the connection activation message is sent to the network element node corresponding to each of the multiple different services, and the backup route connection is saved in the inactive state on the corresponding network element node of the plurality of different services. activation. Step 106: Restore the first service according to the activated standby route connection.
  • the embodiment of the present application can send a connection activation message to the network element node corresponding to the alternate route of the first service after the first service is interrupted, and activate the alternate route connection saved in the inactive state on the network element node, according to the activation.
  • the subsequent backup route connection recovers the first service, and solves the problem that the service recovery efficiency is low due to the large amount of information exchanged between the network element and the controller in the service recovery process after the service is interrupted. Increased business recovery rate.
  • the backup route connection information that is established for the first service is delivered to the network element node corresponding to the backup route.
  • the information about the alternate route connection obtained by using the backup route is sent to the network element node corresponding to the backup route, which may include, but is not limited to, the following manner:
  • the information about the alternate route connection obtained by using the route to the backup route is sent to the network element node corresponding to the backup route by using the extension field of the extended message of the OpenFlow protocol.
  • the extension field includes: the first extension. a field and a second extension field, where the first extension field is used to mark a flow entry corresponding to the information of the alternate route connection as a pre-configured alternate route connection of the first service, and the second extension field is used to The pre-configured alternate route connection identifying the first service is in an inactive state.
  • network protocols other than the OpenFlow protocol may also be used.
  • Other network protocols may also carry the information of the alternate routing connection through the extended field of the extended message of the protocol, which is not limited in this embodiment of the present application.
  • the method further includes: to the first service The network element node corresponding to the alternate route sends a delete message, where the delete message is used to delete the alternate route connection saved in the inactive state on the network element node; and determine a new alternate route connection for the first service.
  • FIG. 2 is a schematic flowchart of a service recovery method according to another embodiment of the present application, where the process includes:
  • Step 202 After the first service is established, receive information about the alternate route connection of the first service delivered by the controller, and save the alternate route connection in an inactive state.
  • Step 204 After the first service is interrupted, receive a connection activation message sent by the controller.
  • connection activation message is used to activate the alternate routing connection saved in an inactive state, and the activated alternate routing connection is used to instruct the controller to connect according to the activated alternate routing The first service is restored.
  • the network element node corresponding to the alternate route sends a connection activation message to activate the backup route connection that is saved in the inactive state on the network element node, and restores the first service according to the activated backup route connection, thereby solving the service interruption.
  • the service recovery rate is low due to the large amount of information exchanged between the network element and the controller, and the service recovery rate is improved.
  • the technical solution provided by the present application can be applied to an SDN network.
  • the user of the controller initiates multiple service establishment requests to the controller, and the protection recovery type carried by these requests is pre-configured pre-computation recovery. After the controller completes these service establishments, the calculation of the alternate routes of these services is performed. After the route calculation is completed, the routing-related resources are not locked and occupied in the control plane, but the resources required for the alternate routes of these services do not conflict with each other.
  • the "information of the alternate route connection” includes the “service connection information” described below, and the "alternate route connection” includes the “alternate connection” and the “service connection” described below.
  • the controller uses the alternate route to establish the service connection information, and delivers the service connection information to the corresponding network element node in the manner of pre-configured connection messages.
  • the network element node After receiving the pre-configured connection message, the network element node temporarily stores the connected flow entry in an inactive state, does not establish a cross-connection, and does not occupy related time slots or bandwidth resources.
  • the alternate route is recalculated and configured. If the controller detects some service interruption, the controller sends an activation standby connection message (corresponding to the connection activation message of the foregoing embodiment) corresponding to the interrupt service to the relevant network element node, and recovers the service, and each activation is activated.
  • the alternate connection message can simultaneously activate alternate connections for multiple services on each network element node.
  • FIG. 3 is a flowchart of a service recovery according to an embodiment of the present application, including the following steps:
  • Step 302 Perform a service connection operation to complete establishment of a service work connection.
  • step 304 the controller pre-calculates an alternate route for the service.
  • step 306 the controller establishes connection information using the alternate route.
  • Step 308 The controller sends a flow entry to the network element device.
  • Step 310 The standby flow entry in the network element is in an inactive state.
  • Step 312 whether an interrupt alarm of the working connection is generated, if yes, go to step 314, if no, go to step 316.
  • step 314 the controller checks whether the alternate connection resource is occupied. If yes, go to step 318, if no, go to step 320.
  • step 316 the controller checks whether the alternate connection resource is occupied. If yes, then go to step 322, if no, go to step 310.
  • step 318 the controller recalculates the path for recovery, and proceeds to step 324.
  • step 320 the active standby entry is deleted and the original connection command is deleted, and the process proceeds to step 324.
  • Step 322 Deliver the backup flow entry to the network element device.
  • step 324 the service recovery process is completed.
  • the foregoing method may be implemented by means of software and a general hardware platform, and may also be implemented by hardware.
  • the above method can also be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, such as a Read-Only Memory ROM or a Random Access Memory (RAM), a magnetic disk, and an optical disk, and includes a plurality of instructions for using one terminal device (
  • the method of various embodiments of the present application may be a mobile phone, a computer, a server, and a network device.
  • a service recovery device is also provided, which is used to implement the foregoing embodiments and implementation manners, and has not been described again.
  • the term "module” may implement a combination of at least one of software and hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 4 is a structural block diagram of a service recovery apparatus according to an embodiment of the present invention. As shown in FIG. 4, the method includes: a first sending module 40 and a restoring module 42.
  • the first sending module 40 is configured to send a connection activation message to the network element node corresponding to the alternate route of the first service after the first service is interrupted, and perform an alternate routing connection that is saved in the inactive state on the network element node. activation.
  • the recovery module 42 is configured to recover the first service according to the activated alternate routing connection.
  • the service recovery apparatus provided in this embodiment can send a connection activation message to the network element node corresponding to the alternate route of the service after the first service is interrupted, and activate the backup route connection saved in the inactive state on the network element node, according to The activated backup route connection recovers the first service, and solves the problem that the service recovery efficiency is low due to the large amount of information exchanged between the network element and the controller in the service recovery process after the service interruption. , thereby improving the business recovery rate.
  • FIG. 5 is a structural block diagram of a service recovery apparatus according to another embodiment of the present application. As shown in FIG. 5, the apparatus further includes: a second sending module 44.
  • the second sending module 44 is configured to: after the first service is established, the information about the backup route of the first service and the information of the backup route obtained by using the backup route is sent to the network element corresponding to the backup route node.
  • the second sending module 44 is further configured to deliver, by using an extension field of the extended message based on the OpenFlow protocol, information about the alternate routing connection obtained by using the alternate route to the corresponding route corresponding to the backup route.
  • the extension field includes: a first extension field and a second extension field, where the first extension field is used to mark a flow entry corresponding to the information of the alternate route connection as the first service A pre-configured alternate route connection, where the second extension field is used to identify that the pre-configured alternate route connection of the first service is in an inactive state.
  • the second sending module 44 is further configured to: when the resource required for the alternate routing connection of the first service is occupied by the second service, send and delete to the network element node corresponding to the standby route. a message, wherein the delete message is used to delete an alternate route connection saved in the network element node in an inactive state; and determine a new alternate route connection for the first service.
  • the first sending module 40 is further configured to send a connection activation message to the network element node to reserve multiple backups corresponding to the plurality of first services stored in the network element node in an inactive state.
  • the routing connection is activated. That is, when the first service includes a plurality of different services, the connection activation message is sent to the network element node corresponding to each of the multiple different services, and the multiple different services are saved in an inactive state.
  • the alternate route connections on the respective NE nodes are activated.
  • a service recovery device is also provided, which is used to implement the foregoing embodiments and implementation manners, and has not been described again.
  • the term "module” may implement a combination of at least one of software and hardware of a predetermined function.
  • FIG. 6 is a structural block diagram of a service recovery apparatus according to another embodiment of the present application. As shown in FIG. 6, the method includes: a first receiving module 60 and a second receiving module 62.
  • the first receiving module 60 is configured to: after the first service is successfully established, receive information about the alternate routing connection of the first service delivered by the controller, and save the alternate routing connection in an inactive state.
  • the second receiving module 62 is configured to receive, after the first service interruption, a connection activation message sent by the controller, where the connection activation message is used to connect to the standby route saved in an inactive state. The activation is performed, and the activated alternate route connection is used to instruct the controller to recover the first service according to the activated alternate route connection.
  • the configuration information of the standby route connection of the service delivered by the controller is received, and the alternate route connection is saved in an inactive state, and then after the first service is interrupted. And sending a connection activation message to the network element node corresponding to the service alternate route to activate the backup route connection that is saved in the inactive state on the network element node, and recover the first service according to the activated backup route connection,
  • the service recovery efficiency is low due to the large amount of information exchanged between the network element and the controller during the service recovery process, and the service recovery rate is improved.
  • a service recovery system including: a network element node and a controller.
  • the network element node is configured to receive, after the first service is established, the information about the backup route connection of the first service delivered by the controller, and save the standby route connection in an inactive state; after the first service is interrupted Receiving a connection activation message sent by the controller, wherein the connection activation message is used to activate the alternate routing connection saved in an inactive state, and the activated alternate routing connection is used to indicate the controller Recovering the first service according to the activated backup route connection; the controller is configured to send a connection activation message to the network element node corresponding to the backup route of the first service after the first service is interrupted, and the pair is activated.
  • the standby routing connection saved on the network element node is activated, wherein the standby routing connection is saved in the inactive state on the network element node, and the first service is restored according to the activated standby routing connection. .
  • a processor is further provided, wherein the processor is configured to run a program, wherein the program is executed to execute the service recovery method described above.
  • the technical solution provided by the embodiment of the present application can not only calculate the route, but also reduce the information amount and the number of information of the connection message after the first service interruption, and can significantly improve the first service recovery efficiency.
  • FIG. 14 is a comparative diagram of the technical solution of the embodiment of the present application and the recovery process of the related art.
  • the route pre-computation recovery technology provided by the embodiment of the present application can shorten the recovery time to less than 500 ms.
  • the controller pre-calculates the restoration route and delivers the configuration to the network element node in advance, and stores the information on the node in an inactive state.
  • the controller sends a connection activation message to activate the standby connection.
  • the activation message does not contain complete connection information, and the amount of information is small, and an activation message supports activation of multiple service backup connections, which can reduce the occurrence of a fault.
  • the time required for route calculation and message interaction during service recovery improves service recovery efficiency.
  • the OpenFlow protocol is extended based on the OpenFlow Switch Specification v1.5.1, so that the Openflow protocol can support the flow entry and identify the activation state, so that the Openflow protocol supports the flow table modification flow_Mod message to pre-configure the pre-calculated route, so that Openflow is enabled.
  • the protocol supports activation and deletion of inactive flow entry entries. For example, it can be:
  • the flow entry of the Openflow expands the new field "Status" to identify the activation state of the flow entry.
  • the expanded flow entry structure is as shown in Table 1.
  • This field contains the attribute "active_status”, which is an enumerated type and contains two states: active state (OFPAS_ACTIVE) and inactive state (OFPAS_INACTIVE). As shown below: This field supports extensions for other states.
  • the Modify Flow Entry message (Flow_Mod message) of the Openflow protocol is extended, and the "status" field is added to support the pre-configuration of the pre-computed route to be delivered to the corresponding network element node.
  • the cookie field can be used to identify the pre-configured flow entry of the connected service.
  • the Flow_Mod message can be used to indicate that the delivered flow entry indicates both active and inactive states.
  • the extended Openflow protocol adds a new message type flow entry activation message "ofp_flow_activate", the message type supports modifying the activation state of the flow entry, functions to activate the pre-configured route, and additionally passes the cookie.
  • the cookie_mask field can support a connection expressing at least 20 services, so that multiple activation connections can be activated simultaneously by one activation message.
  • the message type omits the details of other extraneous fields, shortens the length of the activation message, and improves the efficiency of activating the pre-configured route.
  • the field structure of the message is as follows, where a cookie field can be used to identify a pre-configured flow entry for the service.
  • the network control domain has four network element nodes NE1, NE2, NE3, and NE4, and each network element node has a node port and an inter-port link for interconnection.
  • the network control domain is under the control of a domain controller.
  • the network user sends a service establishment request to the controller, and requests to establish a transmission service between the service access point 1 and the service access point 5.
  • the protection recovery type of the service is pre-configured pre-computation recovery.
  • the SDN controller After receiving the service establishment request, the SDN controller performs route calculation to obtain an optimal path 1 ⁇ 2 ⁇ 4 ⁇ 5 (node port number). And establishing a connection according to the route, establishing a service connection and obtaining a working connection 1, the topology and the simplified node flow table are as shown in FIG. 8.
  • the SDN controller starts to calculate an alternate route for the service, and obtains an alternate optimal path 1 ⁇ 3 ⁇ 7 ⁇ 8 ⁇ 6 ⁇ 5 (node port number).
  • the connection information is sent to the corresponding network element nodes NE1, NE2, and NE3 in the manner of the extended Flow_Mod message.
  • the cookie field in the message contains the pre-configured subnet connection identifier PRE_SNC_ID of the service to mark the flow entry as a pre-configured route for the service, and the status of the message "status" is the inactive state OFPAS_INACTIVE.
  • the dynamic recovery connection processing module deployed in the network element node parses the connection information in the message, and the connected flow entry is not The activated state is temporarily stored, does not establish a cross-connection, does not occupy the relevant time slot or bandwidth resources, and returns a pre-configuration success message to the controller.
  • the topology and service flow table are as shown in Figure 9.
  • the present embodiment completes the establishment of the work service and the pre-computation and pre-configuration of the standby recovery connection.
  • the embodiment completes a process of using the standby connection (alternate route connection) for service recovery.
  • the fault of the working connection 1 is interrupted, and the related network element node reports a service fault alarm to the controller.
  • the controller checks whether the resource related to the standby connection is already occupied. In this embodiment, the resource of the standby connection 1 is not occupied, and the controller will lock the standby routing resource in the control plane, and simultaneously to the network element node NE1.
  • the NE2 and NE3 deliver the extended stream activation message ofp_flow_activate to activate the pre-configured connection.
  • the cookie and Cookie_mask fields of the message are filtered together with the IDentity (ID) carrying the service, and the status carried by the "status" is the active state OFPAS_ACTIVE.
  • the dynamic connection processing device of the network element nodes NE1, NE2, and NE3 deletes the faulty service cross-connection, changes the corresponding flow entry to an inactive state, and activates and establishes an alternate cross-connection. And then return the cross-establishment result to the controller.
  • the obtained service recovery result is as shown in FIG.
  • the controller recalculates the process of establishing the standby connection.
  • the SDN controller detects that the working connection of the newly established service 2 occupies the resources of the standby connection 1, for example, the bandwidth resources of the port 6 and the port 8, as shown in FIG.
  • the controller sends a delete message to the network element nodes NE1, NE2, and NE3 to delete the pre-configured connection, and the PRE_SNC_ID of the service pre-configured route is added to the cookie of the message.
  • the SDN controller recalculates the alternate route for service 1, and obtains the alternate optimal path 1 ⁇ 3 ⁇ 7 ⁇ 9 ⁇ 10 ⁇ 11 ⁇ 12 ⁇ 5 (node port number).
  • the connection information is sent to the corresponding network element nodes NE1, NE2, NE3, and NE4 in a manner of pre-configured connection messages.
  • the dynamic recovery connection processing module deployed in the network element node parses the connection information in the message, and connects the connected flow entry.
  • Temporary storage in an inactive state does not establish a cross-connection, does not occupy relevant time slots or bandwidth resources, and returns a pre-configuration success message to the controller.
  • the topology and service flow table are as shown in Figure 12.
  • the present embodiment completes the process of performing service recovery in the case that the standby connection resource is occupied during a service failure.
  • the SDN controller After receiving the fault alarm of service 1, the SDN controller checks that the standby connection resource has been occupied, and then the controller recalculates the route for service 1, and obtains the optimal path 1 ⁇ 3 ⁇ 7 ⁇ 9 ⁇ 10 ⁇ 11 ⁇ 12 ⁇ 5 (node port number).
  • the controller sends the original connection and the backup connection flow deletion message to the network element nodes NE1, NE2, and NE3, and sends a new connection establishment message to NE1, NE2, NE3, and NE4.
  • the service standby connection establishment procedure is started.
  • This embodiment implements a use case process of simultaneously activating multiple service backup connections after a multi-service failure.
  • the working connections (working connection 1, working connection 2, working connection 3) and the standby connection (alternate connection 1, backup connection 2, backup connection 3) of three connection services are established by the steps of the first embodiment.
  • the resulting topology is shown in Figure 13.
  • the working connection 1, 2, and 3 are interrupted at the same time, and the related network element node reports a service failure alarm to the controller.
  • the controller checks whether the resources related to the standby connection of the three services are already occupied. In this embodiment, the resources of the three standby connections are not occupied, and the controller will lock the standby routing resource in the control plane.
  • the extended flow activation message ofp_flow_activate is sent to the network element nodes NE1, NE2, and NE3 to activate the pre-configured connection.
  • the cookie of the message and the cookie_mask field cooperate to filter out the IDs of the three interrupted services, and the status carried by the "status" is the active state OFPAS_ACTIVE.
  • the dynamic connection processing device of the network element nodes NE1, NE2, and NE3 changes the flow entry of the working connection that matches the faulty service ID to an inactive state, and activates the faulty service ID. Match the alternate connection and return the cross-establishment result to the controller. It acts as an alternate connection that activates multiple services of a network element node with the same activation message.
  • Embodiments of the present application also provide a storage medium.
  • the storage medium may be configured to save the program code executed by the service recovery method provided in the first embodiment.
  • the storage medium may be located in any one of the computer terminal groups in the computer network, or in any one of the mobile terminal groups.
  • the disclosed technical contents may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, unit or module, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present application in essence or in part, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions.
  • a computer device which may be a personal computer, server or network device, etc.
  • the foregoing storage medium includes: a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk, and the like, which can store program codes. .
  • the service recovery method, device and system, storage medium and processor provided by the disclosure solve the business caused by the large amount of information exchanged between the network element and the controller during the service recovery process after the service interruption.
  • the problem of low recovery efficiency improves the business recovery rate.

Landscapes

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

Abstract

公开申请了一种业务恢复方法、装置及系统、存储介质、处理器，所述方法包括：在第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点，其中，所述备用路由连接以未激活状态保存在所述网元节点上；在第一业务中断后，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在所述网元节点上的备用路由连接进行激活；根据激活后的备用路由连接对所述第一业务进行恢复。

Description

业务恢复方法、装置及系统、存储介质、处理器 技术领域
本公开涉及通信技术领域，例如涉及一种业务恢复方法、装置及系统、存储介质、处理器。
背景技术
软件定义网络(Software Defined Network，SDN)是一种新型的网络架构。SDN的控制面与数据转发面是分离的，能够实现集中化的控制，以及可编程的网络操作。由于控制面与数据转发面的分离，当传送网的业务发生故障时，SDN可以集中管控，灵活地实现业务的动态恢复。
基于SDN的第一业务恢复是在传送网的第一业务发生故障后，SDN控制器可以为故障第一业务重新计算路由并下发到相关的网元节点建立交叉连接，为第一业务建立一条新的路径，实现第一业务的恢复，从而保护第一业务的持续性。在故障发生前，只有工作路径占用相关物理资源，相对第一业务保护来说比较节约物理资源，但是在故障发生后才进行新路由的计算及节点配置的下发，因此第一业务恢复需要的时间较长，一般要求在1000ms以内。因此，第一业务恢复效率低。
发明内容
本申请实施例提供一种业务恢复方法、装置及系统、存储介质、处理器，提高了业务恢复的效率。
本申请实施例提供了一种业务恢复方法，所述方法包括：在第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点，将所述备用路由连接以未激活状态保存在所述网元节点上，其中，所述备用路由连接以未激活状态保存在所述网元节点上；在第一业务中断后，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在网元节点上的备用路由连接进行激活；根据激活后的备用路由连接对所述第一业务进行恢复。
本申请实施例提供了一种业务恢复系统，所述系统包括：网元节点，设置 为在第一业务建立完成后，接收控制器下发的所述第一业务的备用路由连接的信息，并以未激活状态保存所述备用路由连接；在所述第一业务中断后，接收所述控制器下发的连接激活消息，其中，所述连接激活消息用于对以未激活状态保存的所述备用路由连接进行激活，激活后的备用路由连接用于指示所述控制器根据激活后的备用路由连接对所述第一业务进行恢复。
控制器，设置为在第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点，其中，所述备用路由连接以未激活状态保存在所述网元节点上；在第一业务中断后，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在网元节点上的备用路由连接进行激活，其中，所述备用路由连接以未激活状态保存在所述网元节点上，并根据激活后的备用路由连接对所述第一业务进行恢复。
本申请实施例提供了一种业务恢复装置，所述装置包括：
第二下发模块，设置为在所述第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点。
第一下发模块，设置为在第一业务中断后，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在网元节点上的备用路由连接进行激活。
恢复模块，设置为根据激活后的备用路由连接对所述第一业务进行恢复。
本申请实施例提供了一种业务恢复装置，所述装置包括：第一接收模块，设置为在第一业务建立完成后，接收控制器下发的所述第一业务的备用路由连接的信息，并以未激活状态保存所述备用路由连接；第二接收模块，设置为在所述第一业务中断后，接收所述控制器下发的连接激活消息，其中，所述连接激活消息用于对以未激活状态保存的所述备用路由连接进行激活，激活后的备用路由连接用于指示所述控制器根据激活后的备用路由连接对所述第一业务进行恢复。
本申请实施例提供了一种存储介质，所述存储介质包括存储的程序，其中，在所述程序运行时控制所述存储介质所在设备执行上述所述的业务恢复方法。
本申请实施例提供了一种处理器，所述处理器用于运行程序，其中，所述 程序运行时执行上述所述的业务恢复方法。
本申请实施例通过在第一业务中断后，向业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在网元节点上的备用路由连接进行激活，根据激活后的备用路由连接对所述第一业务进行恢复，解决了相关技术中，在业务恢复过程中由于网元与控制器之间的在业务中断后交互的信息量较大而导致的业务恢复效率低的问题，提高了业务恢复率。
附图说明
图1是本申请一实施例的业务恢复方法的流程示意图；
图2是本申请另一实施例的业务恢复方法的流程示意图；
图3是本申请一实施例的业务恢复的流程图；
图4是本申请一实施例的业务恢复装置的结构框图；
图5是本申请另一实施例的业务恢复装置的结构框图；
图6是本申请又一实施例的业务恢复装置的结构框图；
图7是本申请一实施例的业务建立连接前的流程图；
图8是本申请一实施例的工作连接建立后的示意图；
图9是本申请一实施例的预计算备用连接后的示意图；
图10是本申请一实施例的工作连接中断进行恢复后的示意图；
图11是本申请一实施例的备用连接资源被占用的示意图；
图12是本申请一实施例的备用连接资源被占用后重新建立的示意图；
图13是本申请一实施例的多业务同时恢复用例示意图；
图14为本申请实施例的业务恢复方法与相关技术的对比示意图。
具体实施方式
下面结合附图和具体实施例对本申请作详细说明。
本申请中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清 楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
一种路由预计算技术，可以提高SDN第一业务恢复的效率。路由预计算是在第一业务建立之后，SDN控制器为该第一业务计算一条备用的路由。在第一业务发生故障后，不需要重新计算路由，而是使用备用路由来对第一业务进行恢复，并且备用路由不会占用相关的物理资源，也起到了节约网络资源的作用。
路由预计算技术虽然提高了第一业务恢复的效率，但是只是把第一业务恢复过程的路由计算部分提前了，然而这部分操作过程并不会占用很多业务恢复过程的时间。影响第一业务恢复效率的其他原因是网元与控制器间消息的传递、收发及处理等。
上述的业务恢复技术和路由预计算技术都是：在业务中断后，控制器向网元节点下发交叉连接消息，每条交叉连接都要对应一条交叉连接消息，而且该消息通常还会包含完整的连接信息，信息量大。从而在多个第一业务同时需要恢复的场景下，控制器同一时间需要下发多个连接恢复消息，信息量很大，严重影响第一业务恢复效率。
本实施例提供了一种业务恢复方法，包括以下第一步和第二步。
第一步，在所述第一业务中断后，向所述第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在所述网元节点上的备用路由连接进行激活。
第二步，根据激活后的备用路由连接对所述第一业务进行恢复。
图1是本申请一实施例的业务恢复方法的流程示意图，该流程包括：
步骤102，在第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点。
在一实施例中，所述备用路由连接以未激活状态保存在所述网元节点上。
步骤104，在所述第一业务中断后，向所述第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在网元节点上的备用路由连接进行激活。
在一个可选示例中，向网元节点下发连接激活消息对以未激活状态保存在网元节点上的多个第一业务对应的多个备用路由连接进行激活。也即，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在所 述网元节点上的备用路由连接进行激活，包括：当所述第一业务包括多个不同业务时，向所述多个不同业务各自对应的网元节点下发连接激活消息，对以未激活状态保存在所述多个不同业务各自对应的网元节点上的备用路由连接进行激活。步骤106，根据激活后的备用路由连接对所述第一业务进行恢复。
本申请实施例能够在第一业务中断后，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在网元节点上的备用路由连接进行激活，根据激活后的备用路由连接对所述第一业务进行恢复，解决了业务中断后，在业务恢复过程中由于网元与控制器之间的交互的信息量较大而导致的业务恢复效率低的问题，提高了业务恢复率。
在所述第一业务建立完成后，将针对所述第一业务建立的备用路由连接信息下发至备用路由对应的网元节点。
在一个可选示例中，将利用所述备用路由得到的备用路由连接的信息下发至备用路由对应的网元节点，可以包括但不限于以下方式：
通过基于开放流交换OpenFlow协议的扩展消息的扩展字段，将利用针对所述备用路由得到的备用路由连接的信息下发至备用路由对应的网元节点，其中，所述扩展字段包括：第一扩展字段和第二扩展字段，所述第一扩展字段用于标记所述备用路由连接的信息对应的流表项为所述第一业务的预配置的备用路由连接，所述第二扩展字段用于标识所述第一业务的预配置的备用路由连接为未激活状态。
在另一个可选示例中，也可以是OpenFlow协议以外的其他网络协议，其他网络协议也能够通过协议的扩展消息的扩展字段来携带备用路由连接的信息，本申请实施例对此不作限定。
在另一个可选示例中，若以未激活状态保存在所述网元节点上的备用路由连接所需的资源已被第二业务占用，则所述方法还包括：向所述第一业务的备用路由对应的网元节点发送删除消息，其中，所述删除消息用于删除以未激活状态保存在所述网元节点上的备用路由连接；为所述第一业务确定新的备用路由连接。
图2是本申请另一实施例的业务恢复方法的流程示意图，该流程包括：
步骤202，在第一业务建立完成后，接收控制器下发的所述第一业务的备用路由连接的信息，并以未激活状态保存所述备用路由连接。
步骤204，在所述第一业务中断后，接收所述控制器下发的连接激活消息。
在一个可选示例中，所述连接激活消息用于对以未激活状态保存的所述备用路由连接进行激活，激活后的备用路由连接用于指示所述控制器根据激活后的备用路由连接对所述第一业务进行恢复。
在第一业务建立成功后，接收控制器下发的所述第一业务的备用路由连接的配置信息，并以未激活状态保存所述备用路由连接，然后在第一业务中断后，向业务的备用路由对应的网元节点下发连接激活消息对以未激活状态保存在网元节点上的备用路由连接进行激活，根据激活后的备用路由连接对所述第一业务进行恢复，解决了业务中断后，在业务恢复过程中由于网元与控制器之间的交互的信息量较大而导致的业务恢复效率低的问题，提高了业务恢复率。
在一个可选示例中，本申请提供的技术方案可以应用于SDN网络中。
控制器的用户向控制器发起多个业务建立请求，这些请求携带的保护恢复类型为预配置预计算恢复。在控制器完成这些业务建立后，进行这些业务的备用路由的计算。路由计算完成后，路由相关的资源并不会在控制平面被锁定与占用，但是这些业务的备用路由所需的资源不会互相冲突。
在一实施例中，上述“备用路由连接的信息”包括下面所述的“业务连接信息”，上述“备用路由连接”包括下面所述的“备用连接”和“业务连接”。在控制器完成备用路由计算后，控制器利用备用路由建立业务连接信息，并将业务连接信息以预配置连接消息的方式分别下发到对应的网元节点上。
网元节点接收到预配置连接消息后，将连接的流表项以未激活的状态进行暂存，并不建立交叉连接，也不占用相关时隙或带宽资源。
若某个业务在正常运行中备用路由被占用，则重新计算并配置备用路由。若控制器检测到某些业务中断，控制器则向相关的网元节点发送与这些中断业务对应的激活备用连接消息(相当于上述实施例的连接激活消息)，对业务进行恢复，每条激活备用连接消息可以同时激活每个网元节点上多个业务的备用连接。
如图3所示，图3为本申请实施例的一种业务恢复的流程图，包括以下步骤：
步骤302，执行业务连接操作，完成业务工作连接的建立。
步骤304，控制器为业务预先计算出一条备用路由。
步骤306，控制器使用备用路由建立连接信息。
步骤308，控制器向网元设备下发流表项。
步骤310，网元中的备用流表项处于未激活状态。
步骤312，是否产生工作连接的中断告警，如果是，则转步骤314，如果否，则转步骤316。
步骤314，控制器检查备用连接资源是否被占用，如果是，则转步骤318，如果否，则转步骤320。
步骤316，控制器检查备用连接资源是否被占用，如果是，则转步骤322，如果否，则转步骤310。
步骤318，控制器重新计算路径进行恢复，转至步骤324。
步骤320，向网元设备下发激活备用流表项、删除原连接命令，转至步骤324。
步骤322，向网元设备下发删除备用流表项。
步骤324，业务恢复过程完成。
在一实施例中，上述方法可借助软件和通用硬件平台的方式来实现，当然也可以通过硬件的方式来实现。在另一实施例中，上述方法也可以以软件产品的形式体现出来。该计算机软件产品存储在一个存储介质，如只读存储器(Read-Only Memory ROM)或随机存取存储器(Random Access Memory，RAM)、磁碟、以及光盘中，包括若干指令使用一台终端设备(可以是手机，计算机，服务器，以及网络设备等)执行本申请各个实施例的方法。
在本实施例中还提供了一种业务恢复装置，该装置用于实现上述实施例及实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和硬件中至少一项的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图4是本申请一实施例的业务恢复装置的结构框图，如图4所示，包括：第一下发模块40和恢复模块42。
第一下发模块40，设置为在第一业务中断后，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在网元节点上的备用路由连接进行激活。
恢复模块42，设置为根据激活后的备用路由连接对所述第一业务进行恢复。
本实施例提供的业务恢复装置能够在第一业务中断后，向业务的备用路由对应的网元节点下发连接激活消息对以未激活状态保存在网元节点上的备用路由连接进行激活，根据激活后的备用路由连接对所述第一业务进行恢复，解决了业务中断后，在业务恢复过程中由于网元与控制器之间的交互的信息量较大而导致的业务恢复效率低的问题，进而提高了业务恢复率。
在一个可选示例中，图5是本申请另一实施例的业务恢复装置的结构框图，如图5所示，所述装置还包括：第二下发模块44。
第二下发模块44，设置为在所述第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至备用路由对应的网元节点。
在一个可选示例中，所述第二下发模块44，还设置为通过基于OpenFlow协议的扩展消息的扩展字段，将利用所述备用路由得到的备用路由连接的信息下发至备用路由对应的网元节点，其中，所述扩展字段包括：第一扩展字段和第二扩展字段，所述第一扩展字段用于标记所述备用路由连接的信息对应的流表项为所述第一业务的预配置的备用路由连接，所述第二扩展字段用于标识所述第一业务的预配置的备用路由连接为未激活状态。
在一个可选示例中，所述第二下发模块44，还设置为，在第一业务的备用路由连接所需的资源已被第二业务占用时，向备用路由对应的网元节点发送删除消息，其中，所述删除消息用于删除以未激活状态保存在所述网元节点的备用路由连接；为所述第一业务确定新的备用路由连接。
在一个可选示例中，所述第一下发模块40，还设置为向网元节点下发连接激活消息对以未激活状态保存在网元节点上的多个第一业务对应的多个备用路由连接进行激活。也即，设置为当所述第一业务包括多个不同业务时，向所述多个不同业务各自对应的网元节点下发连接激活消息，对以未激活状态保存在所述多个不同业务各自对应的网元节点上的备用路由连接进行激活。
在本实施例中还提供了一种业务恢复装置，该装置用于实现上述实施例及实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和硬件中至少一项的组合。尽管以下实施例所描述的装置以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是本申请又一实施例的业务恢复装置的结构框图，如图6所示，包括：第一接收模块60和第二接收模块62。
第一接收模块60，设置为在第一业务建立成功后，接收控制器下发的所述第一业务的备用路由连接的信息，并以未激活状态保存所述备用路由连接。
第二接收模块62，设置为在所述第一业务中断后，接收所述控制器下发的连接激活消息，其中，所述连接激活消息用于对以未激活状态保存的所述备用路由连接进行激活，激活后的备用路由连接用于指示所述控制器根据激活后的备用路由连接对所述第一业务进行恢复。
通过上述各个模块的综合作用，在业务建立成功后，接收控制器下发的所述业务的备用路由连接的配置信息，并以未激活状态保存所述备用路由连接，然后在第一业务中断后，向业务的备用路由对应的网元节点下发连接激活消息对以未激活状态保存在网元节点上的备用路由连接进行激活，根据激活后的备用路由连接对所述第一业务进行恢复，解决了业务中断后，在业务恢复过程中由于网元与控制器之间的交互的信息量较大而导致的业务恢复效率低的问题，提高了业务恢复率。
在本实施例中，还提供了一种业务恢复系统，包括：网元节点和控制器。
网元节点，设置为在第一业务建立完成后，接收控制器下发的第一业务的备用路由连接的信息，并以未激活状态保存所述备用路由连接；在所述第一业务中断后，接收所述控制器下发的连接激活消息，其中，所述连接激活消息用于对以未激活状态保存的所述备用路由连接进行激活，激活后的备用路由连接用于指示所述控制器根据激活后的备用路由连接对所述第一业务进行恢复；控制器，设置为在第一业务中断后，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在网元节点上的备用路由连接进行激活，其中，所述备用路由连接以未激活状态保存在所述网元节点上，并根据激活后的备用路由连接对所述第一业务进行恢复。
在本实施例中，还提供了一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述所述的业务恢复方法。
本申请实施例所提供的技术方案不仅可以计算路由，还可以减少第一业务中断后恢复连接消息的信息量及信息数，可以明显提高第一业务恢复效率。如图14所示，图14为本申请实施例的技术方案和相关技术的恢复流程的对比示 意图。本申请实施例提供的路由预计算恢复技术可以将恢复时间缩短到500ms以内。
下面通过多个例子对上述实施例进行详细说明。
在一实施例中，业务建立完成后，控制器预计算恢复路由并将配置提前下发到网元节点，并以未激活的状态在节点上存储。在业务中断后，控制器下发连接激活消息对备用连接进行激活，该激活消息不包含完整的连接信息，信息量小，且一个激活消息支持多个业务备用连接的激活，可以减少故障发生后业务恢复过程中路由计算和消息交互所需要的时间，提高业务恢复效率。
本实施例基于OpenFlow Switch Specification v1.5.1扩展了Openflow协议，使得Openflow协议能够支持流表项，以及标识激活状态，使得Openflow协议支持下发流表修改Flow_Mod消息对预计算路由进行预配置，使得Openflow协议支持激活和删除未激活的流表项。例如可以是：
1)在一实施例中，Openflow的流表项扩展新的字段“Status”，以标识流表项的激活状态，扩展后的流表项结构如表1所示。
表1
Figure PCTCN2018085637-appb-000001
该字段包含属性“active_status”，该属性为枚举类型，包含有两种状态：激活状态(OFPAS_ACTIVE)和未激活状态(OFPAS_INACTIVE)。如下所示：该字段支持其他状态的扩展。
Figure PCTCN2018085637-appb-000002
2)在另一实施例中，扩展Openflow协议的Modify Flow Entry消息(Flow_Mod消息)，增加“status”字段，以支持预计算路由的预配置下发到对应的网元节点上。如下所示，可用Cookie字段来标识该连接业务的预配置流表项。进行该协议扩展后，通过Flow_Mod消息可以使下发的流表项表示激活和未激活的两种状态。
OFP_ASSERT(sizeof(struct ofp_flow_mod)＝＝56)；
3)在又一实施例中，扩展Openflow协议添加新的消息类型流表项激活消息“ofp_flow_activate”，该消息类型支持修改流表项的激活状态，起到激活预配置路由的作用，另外通过cookie和cookie_mask字段可以支持表达至少20个业务的连接，从而由一条激活消息可以同时激活多个备用连接。该消息类型与Flow_Mod消息相比省略了其他无关字段的细节，缩短了激活消息的长度，提高了激活预配置路由的效率。该消息的字段结构如下所示，其中可用Cookie字段来标识该业务的预配置流表项。
Figure PCTCN2018085637-appb-000003
实施例一
本实施例将进行工作业务的建立以及备用恢复连接的预计算及预配置，作为以下几个实施例共同的初始条件部分。如附图7所示，网络控制域有四个网元节点NEl、NE2、NE3、NE4，每个网元节点间有节点端口和端口间链路进行互连。该网络控制域处于域控制器的控制之下。
第一步，网络用户向控制器发送业务建立请求，请求在服务接入点1和服务接入点5之间建立一条传输业务，该业务的保护恢复类型为预配置预计算恢复。
第二步，SDN控制器收到业务建立请求后进行路由计算得到最优路径1←→2←→4←→5(节点端口号)。并依据该路由建立连接，建立好业务连接后得到工作连接1，拓扑以及简化的节点流表如附图8所示。
第三步，在完成业务建立后，SDN控制器开始为该业务计算备用路由，得到备用最优路径1←→3←→7←→8←→6←→5(节点端口号)。并依据建立备用连接信息，将连接信息以扩展的Flow_Mod消息的方式，分别下发到对应的网元节点NE1、NE2、NE3上。该消息中的Cookie字段包含该业务的预配置子网连接标识PRE_SNC_ID，以标记该流表项为该业务的预配置路由，同时该消息的“status”的状态为未激活状态OFPAS_INACTIVE。
第四步，网元节点NE1、NE2、NE3收到预配置连接的消息后，部署在网元节点中的动态恢复连接处理模块解析该消息中的连接信息，并将连接的流表项以未激活的状态进行暂存，并不建立交叉连接，也不占用相关时隙或带宽资源，并向控制器返回预配置成功消息。预配置完成后，拓扑及业务流表情况如附图9所示。
因此，本实施例完成了工作业务的建立以及备用恢复连接的预计算及预配置。
实施例二
在实施例一完成的基础上，本实施例完成了一次使用备用连接(备用路由连接)进行业务恢复的过程。
第一步，在业务运行过程中，工作连接1发生故障造成中断，相关网元节点向控制器上报业务故障告警。控制器收到业务故障告警后，查看备用连接相关的资源是否已经被占用，该实施例中备用连接1的资源没有被占用，控制器将在控制平面锁定备用路由资源，同时向网元节点NE1、NE2、NE3下发扩展的流激活消息ofp_flow_activate来激活预配置连接。该消息的Cookie和Cookie_mask字段配合携带该业务的身份标识号码(IDentity，ID)进行过滤，且“status”携带的状态为激活状态OFPAS_ACTIVE。
第二步，网元节点NE1、NE2、NE3的动态连接处理装置接收到该消息命令后，将删除故障业务交叉连接，把相应的流表项变为未激活状态，并激活与建立备用交叉连接，然后向控制器返回交叉建立结果。得到的业务恢复结果如附图10所示。
实施例三
在实施例一完成的基础上，本实施例完成一次备用连接资源被占用的情况下控制器重新计算建立备用连接的过程。
第一步，在业务运行过程中，SDN控制器检测到新建立业务的工作连接2把备用连接1的资源进行了占用，例如端口6、端口8的带宽资源，如附图11所示。
第二步，那么控制器将向网元节点NE1、NE2、NE3下发删除消息，将预配置连接删除，该消息的Cookie中附加业务预配置路由的PRE_SNC_ID。SDN控制器重新为业务1计算备用路由，得到备用最优路径1←→3←→7←→9←→10←→11←→12←→5(节点端口号)。并依据建立备用连接信息，将连接信息以预配置连接消息的方式分别下发到对应的网元节点NE1、NE2、NE3、NE4上。
第三步，网元节点NE1、NE2、NE3、NE4收到预配置连接的消息后，部署在网元节点中的动态恢复连接处理模块解析该消息中的连接信息，并将连接的流表项以未激活的状态进行暂存，并不建立交叉连接，也不占用相关时隙或带宽资源，并向控制器返回预配置成功消息。预配置完成后，拓扑及业务流表情况如附图12所示。
实施例四
在实施例一完成的基础上，本实施例完成一次业务发生故障过程中备用连接资源被占用的情况下控制器进行业务恢复的过程。
第一步，SDN控制器在收到业务1的故障告警后，检查到备用连接资源已经被占用，那么控制器重新为业务1计算路由，得到最优路径1←→3←→7←→9←→10←→11←→12←→5(节点端口号)。
第二步，路由计算完成后，控制器向网元节点NE1、NE2、NE3下发原连接、备用连接流删除消息，并向NE1、NE2、NE3、NE4下发新连接建立消息。新业务连接建立完成后，再启动业务备用连接建立程序。
实施例五
本实施例实现多业务故障后同时激活多个业务备用连接的用例过程。
第一步，通过实施例一的步骤建立三个连接业务的工作连接(工作连接1、工作连接2、工作连接3)和备用连接(备用连接1、备用连接2、备用连接3)。 得到的拓扑，如附图13所示。
第二步，在业务运行过程中，工作连接1、2、3同时发生故障造成中断，相关网元节点向控制器上报业务故障告警。控制器收到业务故障告警后，查看这三个业务的备用连接相关的资源是否已经被占用，该实施例中三个备用连接的资源均没有被占用，控制器将在控制平面锁定备用路由资源，同时向网元节点NE1、NE2、NE3下发扩展的流激活消息ofp_flow_activate来激活预配置连接。该消息的cookie和cookie_mask字段配合可以过滤出这三个中断业务的ID，且“status”携带的状态为激活状态OFPAS_ACTIVE。
第三步，网元节点NE1、NE2、NE3的动态连接处理装置接收到该消息命令后，把与故障业务ID相匹配的工作连接的流表项变为未激活状态，并激活与故障业务ID相匹配的备用连接，然后向控制器返回交叉建立结果。起到了用同一激活消息来激活一个网元节点多个业务的备用连接的作用。
本申请的实施例还提供了一种存储介质。在一实施例中，上述存储介质可以设置为保存上述实施例一所提供的业务恢复方法所执行的程序代码。
在一实施例中，上述存储介质可以位于计算机网络中计算机终端群中的任意一个计算机终端中，或者位于移动终端群中的任意一个移动终端中。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
在本申请的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的技术内容，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
工业实用性
本公开提供的一种业务恢复方法、装置及系统、存储介质、处理器，解决了业务中断后，在业务恢复过程中由于网元与控制器之间的交互的信息量较大而导致的业务恢复效率低的问题，提高了业务恢复率。

Claims (12)

  1. 一种业务恢复方法，所述方法包括：
    在第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点，其中，所述备用路由连接以未激活状态保存在所述网元节点上；在所述第一业务中断后，向所述第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在所述网元节点上的备用路由连接进行激活；
    根据激活后的备用路由连接对所述第一业务进行恢复。
  2. 根据权利要求1所述的方法，其中，将利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点，包括：
    通过基于开放流交换OpenFlow协议的扩展消息的扩展字段，将利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点，其中，所述扩展字段包括：第一扩展字段和第二扩展字段，所述第一扩展字段用于标记所述备用路由连接的信息对应的流表项为所述第一业务的预配置的备用路由连接，所述第二扩展字段用于标识所述第一业务的预配置的备用路由连接为未激活状态。
  3. 根据权利要求1或2所述的方法，其中，若以未激活状态保存在所述网元节点上的备用路由连接所需的资源已被第二业务占用，则所述方法还包括：
    向所述第一业务的备用路由对应的网元节点发送删除消息，其中，所述删除消息用于删除以未激活状态保存在所述网元节点上的备用路由连接；
    为所述第一业务确定新的备用路由连接。
  4. 根据权利要求1所述的方法，其中，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在所述网元节点上的备用路由连接进行激活，包括：
    当所述第一业务包括多个不同业务时，向所述多个不同业务各自对应的网元节点下发连接激活消息，对以未激活状态保存在所述多个不同业务各自对应的网元节点上的备用路由连接进行激活。
  5. 一种业务恢复装置，应用于控制器，所述装置包括：
    第二下发模块，设置为在所述第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点；
    第一下发模块，设置为在第一业务中断后，向第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在所述网元节点上的备用路由连接进行激活；
    恢复模块，设置为根据激活后的备用路由连接对所述第一业务进行恢复。
  6. 根据权利要求5所述的装置，其中，所述第二下发模块是设置为通过基于开放流交换OpenFlow协议的扩展消息的扩展字段，将利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点，其中，所述扩展字段包括：第一扩展字段和第二扩展字段，所述第一扩展字段用于标记所述备用路由连接的信息对应的流表项为所述第一业务的预配置的备用路由连接，所述第二扩展字段用于标识所述第一业务的预配置的备用路由连接为未激活状态。
  7. 根据权利要求5或6所述的装置，其中，所述第二下发模块是设置为：
    若以未激活状态保存在所述网元节点上的备用路由连接所需的资源已被第二业务占用，则向所述第一业务的备用路由对应的网元节点发送删除消息，其中，所述删除消息用于删除以未激活状态保存在所述网元节点上的备用路由连接；为所述第一业务确定新的备用路由连接。
  8. 根据权利要求5所述的装置，其中，所述第一下发模块是设置为：
    当所述第一业务包括多个不同业务时，向所述多个不同业务各自对应的网元节点下发连接激活消息，对以未激活状态保存在所述多个不同业务各自对应的网元节点上的备用路由连接进行激活。
  9. 一种业务恢复装置，应用于网元节点，所述装置包括：
    第一接收模块，设置为在第一业务建立完成后，接收控制器下发的所述第一业务的备用路由连接的信息，并以未激活状态保存所述备用路由连接；
    第二接收模块，设置为在所述第一业务中断后，接收所述控制器下发的连接激活消息，其中，所述连接激活消息用于对以未激活状态保存的所述备用路由连接进行激活，激活后的备用路由连接用于指示所述控制器根据激活后的备用路由连接对所述第一业务进行恢复。
  10. 一种业务恢复系统，其特征在于，所述系统包括：
    网元节点，设置为在第一业务建立完成后，接收控制器下发的所述第一业务的备用路由连接的信息，并以未激活状态保存所述备用路由连接；在所述第 一业务中断后，接收所述控制器下发的连接激活消息，其中，所述连接激活消息用于对以未激活状态保存的所述备用路由连接进行激活，激活后的备用路由连接用于指示所述控制器根据激活后的备用路由连接对所述第一业务进行恢复；
    控制器，设置为在第一业务建立完成后，计算所述第一业务的备用路由并利用所述备用路由得到的备用路由连接的信息下发至所述备用路由对应的网元节点，其中，所述备用路由连接以未激活状态保存在所述网元节点上；在第一业务中断后，向所述第一业务的备用路由对应的网元节点下发连接激活消息，对以未激活状态保存在所述网元节点上的备用路由连接进行激活，根据激活后的备用路由连接对所述第一业务进行恢复。
  11. 一种存储介质，所述存储介质包括存储的程序，其中，在所述程序运行时控制所述存储介质所在设备执行权利要求1至4中任一项所述的方法。
  12. 一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行权利要求1至4中任一项所述的方法。
PCT/CN2018/085637 2017-05-05 2018-05-04 业务恢复方法、装置及系统、存储介质、处理器 WO2018202141A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710313910.9 2017-05-05
CN201710313910.9A CN108809824A (zh) 2017-05-05 2017-05-05 业务恢复方法、装置及系统、存储介质、处理器

Publications (1)

Publication Number Publication Date
WO2018202141A1 true WO2018202141A1 (zh) 2018-11-08

Family

ID=64016387

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085637 WO2018202141A1 (zh) 2017-05-05 2018-05-04 业务恢复方法、装置及系统、存储介质、处理器

Country Status (2)

Country Link
CN (1) CN108809824A (zh)
WO (1) WO2018202141A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111787368A (zh) * 2020-05-21 2020-10-16 视联动力信息技术股份有限公司 一种服务器测试方法和装置
US12034570B2 (en) 2022-03-14 2024-07-09 T-Mobile Usa, Inc. Multi-element routing system for mobile communications

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1556637A (zh) * 2003-12-30 2004-12-22 ���ͨ�ſƼ��ɷ����޹�˾ 一种在格状网中利用共享备用通道进行故障恢复的方法
CN1934561A (zh) * 2004-02-12 2007-03-21 城域信息包系统公司 网络拓扑的恢复机制
CN101626527A (zh) * 2009-08-19 2010-01-13 烽火通信科技股份有限公司 一种ason网络实现备用路由优化的返回式共享恢复的方法
WO2016168603A1 (en) * 2015-04-15 2016-10-20 Nokia Solutions And Networks Oy Self-organizing network concepts for small cells backhauling

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1556637A (zh) * 2003-12-30 2004-12-22 ���ͨ�ſƼ��ɷ����޹�˾ 一种在格状网中利用共享备用通道进行故障恢复的方法
CN1934561A (zh) * 2004-02-12 2007-03-21 城域信息包系统公司 网络拓扑的恢复机制
CN101626527A (zh) * 2009-08-19 2010-01-13 烽火通信科技股份有限公司 一种ason网络实现备用路由优化的返回式共享恢复的方法
WO2016168603A1 (en) * 2015-04-15 2016-10-20 Nokia Solutions And Networks Oy Self-organizing network concepts for small cells backhauling

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111787368A (zh) * 2020-05-21 2020-10-16 视联动力信息技术股份有限公司 一种服务器测试方法和装置
US12034570B2 (en) 2022-03-14 2024-07-09 T-Mobile Usa, Inc. Multi-element routing system for mobile communications

Also Published As

Publication number Publication date
CN108809824A (zh) 2018-11-13

Similar Documents

Publication Publication Date Title
US11349687B2 (en) Packet processing method, device, and system
US9178756B2 (en) Method and device for processing location information of fault point
CN101702663B (zh) 一种环网拓扑信息的更新方法和装置
US20040042416A1 (en) Virtual Local Area Network auto-discovery methods
US9813286B2 (en) Method for virtual local area network fail-over management, system therefor and apparatus therewith
CN104869057A (zh) 开放流交换机优雅重启处理方法、装置及开放流控制器
CN101364927A (zh) 实现虚拟专用网vpn故障恢复的方法、设备及系统
CN110891018B (zh) 网络流量恢复方法、装置、sdn控制器及存储介质
WO2014090083A1 (zh) 分布式弹性网络互连的业务承载方法及装置
CN112615914B (zh) 一种利用边界网关协议传递组播热备表项的方法
CN107645394A (zh) 一种sdn网络中的交换机配置方法
WO2023015897A1 (zh) 一种光网络智能控制方法、装置及系统
CN104160667A (zh) 双上行相切环收敛的方法、设备和系统
CN109302328B (zh) 一种vxlan网络热备切换方法及系统
CN109039916B (zh) 报文转发方法、装置及存储介质
CN104040973B (zh) 聚合组链路协商方法、装置和系统
CN114401274A (zh) 一种通信线路创建方法、装置、设备及可读存储介质
WO2018202141A1 (zh) 业务恢复方法、装置及系统、存储介质、处理器
CN112217680B (zh) 基于软件定义广域网的控制器能力基准测试方法和装置
CN103414591A (zh) 一种端口故障恢复时的快速收敛方法和系统
CN108282346A (zh) 软件升级方法及装置
CN106130783B (zh) 一种端口故障处理方法及装置
WO2017181781A1 (zh) 流量的转发方法及装置
CN105391565A (zh) 备份业务配置实现同步的方法
WO2015135280A1 (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: 18794130

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

Country of ref document: EP

Kind code of ref document: A1