A service footprint-based operation and maintenance method and device

Abstract

The application relates to the network operation and maintenance technical field, in particular to a service footprint-based operation and maintenance method and device. The method is applied to an SDN controller, and the method comprises the following steps: obtaining a target service to be processed, and generating an operation ID corresponding to the target service; determining a target processing module and a service processing logic required for processing the target service; when any target processing module is called to process the target service based on the service processing logic, generating a service running log corresponding to the target processing module and carrying the operation ID, and each service running log constitutes an actual service footprint of the target service; generating an operation log corresponding to the target service and carrying the operation ID; and performing operation and maintenance based on the operation log and the service running log corresponding to each target processing module.

Description

TECHNICAL FIELD

[0001] The present application relates to the network operation and maintenance technical field, in particular to a kind of operation and maintenance method and device based on service footprint. BACKGROUND

[0002] SDN (Software Defined Network, software-defined network) is a new network innovation architecture, and is an implementation way of network virtualization, and its core technology is to separate the control layer and forwarding layer of network equipment (such as switch or router) by unified southbound interface protocol (such as OpenFlow and NETCONF protocol), so as to realize intelligent management of control layer and operation and maintenance of network resources and network service.

[0003] Service footprint refers to which modules the service has passed in the SDN controller, whether synchronous call or asynchronous call between modules is part of the service footprint.

[0004] At present, after the problem of the existing network appears, the experienced maintenance personnel needs to invest a lot of time to logically infer the problem from the massive logs and data by exporting the service log and service running data of the SDN controller.

[0005] However, exporting full amount of service log and service running data is very time-consuming, and cannot meet the needs of customers for rapid preliminary positioning and rapid recovery of environment. If the exported full amount of service log and service running data is too much, it will increase the data transmission time and problem positioning time; if the exported full amount of service log and service running data is too little, it may miss the key log, and cannot meet the needs of customers for rapid preliminary positioning and rapid recovery of environment. The problem positioning is difficult, and the business familiarity and maintenance experience of maintenance personnel are required, new maintenance personnel cannot quickly start positioning the problem of the existing network, and the stability of operation and maintenance team is also required. SUMMARY

[0006] The present application provides an operation and maintenance method and device based on service footprint.

[0007] In the first aspect, the present application provides an operation and maintenance method based on service footprint, applied to SDN controller, and the method comprises:

[0008] Obtain the target service to be processed, and generate the operation ID corresponding to the target service;

[0009] Determine the target processing module and service processing logic required for processing the target service;

[0010] When invoking any target processing module to process the target service based on the service processing logic, a service running log carrying the operation ID corresponding to the target processing module is generated, and each service running log constitutes an actual service footprint of the target service;

[0011] An operation log carrying the operation ID corresponding to the target service is generated;

[0012] Operation and maintenance are performed based on the operation log and the service running log corresponding to each target processing module.

[0013] Optionally, the SDN controller is preset with an expected service footprint of each service; after the target service to be processed is obtained, the method further includes:

[0014] Based on the service attribute of the target service, an expected service footprint ID corresponding to the target service is determined, and the operation log carries the expected service footprint ID corresponding to the target service.

[0015] Optionally, the operation log corresponding to one service further includes an operator of the service, operation content, service processing time and service processing result; the expected service footprint corresponding to one service includes a processing module expected to be called when processing the service, an expected processing result of each processing module expected to be called, and an emergency recovery scheme when the processing result of each processing module expected to be called is abnormal.

[0016] Optionally, the method further includes:

[0017] Based on the operation ID of any service, each service operation and maintenance log and / or expected service footprint corresponding to the operation ID is queried and obtained, and the actual service footprint and / or expected service footprint of the service obtained by the query is displayed through a display interface.

[0018] Optionally, the method further includes:

[0019] If the processing result of any target processing module is inconsistent with the expected processing result, an emergency recovery scheme corresponding to the target processing result is determined, and the emergency recovery scheme is executed.

[0020] In a second aspect, the present application provides an operation and maintenance device based on a service footprint, applied to an SDN controller, and the device includes:

[0021] An acquisition unit is configured to acquire a target service to be processed and generate an operation ID corresponding to the target service;

[0022] A determination unit is configured to determine a target processing module and service processing logic required for processing the target service;

[0023] The generating unit is configured to generate a service running log corresponding to the target processing module and carrying the operation ID when invoking any target processing module to process the target service based on the service processing logic, and each service running log constitutes an actual service footprint of the target service.

[0024] The generating unit is further configured to generate an operation log corresponding to the target service and carrying the operation ID.

[0025] The operation unit is configured to perform operation and maintenance based on the operation log and the service running log corresponding to each target processing module.

[0026] Optionally, the SDN controller is preset with an expected service footprint of each service, and after obtaining the target service to be processed,

[0027] The determining unit is further configured to determine an expected service footprint ID corresponding to the target service based on the service attribute of the target service, and the operation log carries the expected service footprint ID corresponding to the target service.

[0028] Optionally, the operation log corresponding to one service further includes an operator of the service, operation content, service processing time and service processing result; and the expected service footprint corresponding to one service includes a processing module expected to be invoked when processing the service, expected processing results of each processing module expected to be invoked, and an emergency recovery scheme when the processing result of each processing module expected to be invoked is abnormal.

[0029] Optionally, the apparatus further includes:

[0030] The querying unit is configured to query and obtain each service operation and maintenance log and / or expected service footprint corresponding to the operation ID of any service based on the operation ID.

[0031] The display unit is configured to display the actual service footprint and / or expected service footprint of the service obtained through the display interface.

[0032] Optionally, the apparatus further includes:

[0033] The executing unit is configured to determine an emergency recovery scheme corresponding to the target processing result and execute the emergency recovery scheme if the processing result of any target processing module is inconsistent with the expected processing result.

[0034] In a third aspect, an embodiment of the present application provides a service footprint-based operation and maintenance apparatus, which includes:

[0035] A memory configured to store program instructions.

[0036] A processor configured to invoke program instructions stored in the memory to perform the steps of the method of any of the above first aspects.

[0037] In a fourth aspect, the embodiments of the present application further provide a computer readable storage medium, which stores computer executable instructions for causing a computer to perform the steps of the method of any of the above first aspects.

[0038] In summary, the embodiments of the present application provide a service footprint-based operation and maintenance method, which is applied to an SDN controller. The method comprises: obtaining a target service to be processed, and generating an operation ID corresponding to the target service; determining a target processing module and service processing logic required for processing the target service; when any target processing module is called to process the target service based on the service processing logic, generating a service running log corresponding to the target processing module, which carries the operation ID; each service running log constitutes an actual service footprint of the target service; generating an operation log corresponding to the target service, which carries the operation ID; and performing operation and maintenance based on the operation log and the service running log corresponding to each target processing module.

[0039] By using the service footprint-based operation and maintenance method provided by the embodiments of the present application, the operation ID used for uniquely identifying each service is used to obtain the operation log and the service running log of the service corresponding to the operation ID from a large log file, and the operation and maintenance are performed based on the operation log and the service running log of the service, which greatly improves the operation and maintenance efficiency and ensures that the online fault can be processed in time. BRIEF DESCRIPTION OF DRAWINGS

[0040] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the drawings needed in the description of the embodiments of the present application or the prior art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments described in the present application, and other drawings can also be obtained by those skilled in the art according to these drawings of the embodiments of the present application.

[0041] Figure 1 A detailed flowchart of a service footprint-based operation and maintenance method provided by the embodiments of the present application;

[0042] Figure 2 A service processing process schematic diagram provided by the embodiments of the present application;

[0043] Figure 3 A service expected footprint display flowchart provided by the embodiments of the present application;

[0044] Figure 4A service actual footprint display flowchart provided by an embodiment of the present application;

[0045] Figure 5 A footprint difference and emergency plan display flowchart provided by an embodiment of the present application;

[0046] Figure 6 A structural schematic diagram of a device based on a service footprint provided by an embodiment of the present application;

[0047] Figure 7 A hardware architecture schematic diagram of a device based on a service footprint provided by an embodiment of the present application. DETAILED DESCRIPTION

[0048] The terminology used in the present application is merely for the purpose of describing particular embodiments and is not intended to be limiting of the present application. As used in the present application and the claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0049] It should be understood that, although the terms first, second, third, etc. can be used herein to describe various information, these terms are not intended to denote a particular order of the information. These terms are used merely to distinguish one type of information from another. For example, a first information can be termed a second information, and similarly, a second information can be termed a first information, without departing from the scope of the present application. Furthermore, the word "if" can be interpreted as meaning "when" or "upon" or "in response to determining," depending on the context.

[0050] For example, refer to Figure 1 A detailed flowchart of a service footprint based operation and maintenance method provided by an embodiment of the present application is shown, the method is applied to an SDN controller, and the method comprises the following steps:

[0051] Step 100: obtaining a target service to be processed, and generating an operation ID corresponding to the target service.

[0052] It should be noted that each service to be processed (southbound service and northbound task) can be a configuration issuing task issued by a user to each network device under the management of the SND controller based on the SDN controller.

[0053] After the SDN controller obtains a target service to be processed, an operation ID for uniquely identifying the target service can be generated.

[0054] In the embodiments of the present application, the SDN controller is preconfigured with expected service footprints of each service, for example, service 1 corresponds to expected service footprint 1, and the expected service footprint ID is 1 (e.g., ID 1); service 2 corresponds to expected service footprint 2, and the expected service footprint ID is 2 (e.g., ID 2).

[0055] Then, after obtaining the target service to be processed, the above method can further include the following steps:

[0056] Based on the service attribute of the target service, determine the expected service footprint ID corresponding to the target service, and the operation log carries the expected service footprint ID corresponding to the target service.

[0057] In the embodiments of the present application, the expected service footprint corresponding to one service includes the processing module expected to be called when processing the service, the expected processing result of each processing module expected to be called, and the emergency recovery scheme when the processing result of each processing module expected to be called is abnormal.

[0058] Step 110: Determine the target processing module and service processing logic required for processing the target service.

[0059] Specifically, the SDN controller parses the target service and determines the target processing module and service processing logic required for processing the target service.

[0060] For example, for service 1, the SDN controller parses service 1 and determines that the processing modules required for processing service 1 are processing module 1, processing module 2 and processing module 3. The service processing logic refers to the sequence, dependency relationship and the like of processing the service by each processing module. For example, the processing modules required for processing service 1 are processing module 1, processing module 2 and processing module 3, and each processing module processes service 1 in series. Then, the SDN controller main thread first calls processing module 1 to process service 1, and then calls processing module 2 to process service 1 after processing is completed, and then calls processing module 3 to process service 1 after processing is completed. After processing module 3 is processed, it is determined that service 1 is processed.

[0061] Step 120: When any target processing module is called to process the target service based on the service processing logic, generate the service running log corresponding to the target processing module carrying the operation ID, and each service running log constitutes the actual service footprint of the target service.

[0062] Specifically, since the target service module required for processing the target service and the service processing logic between each target service module have been determined above, when processing the target service, each target processing module can be called to process the target service according to the determined service processing logic.

[0063] In the embodiment of the present application, when the main thread of the SDN controller calls a target processing module for target service processing, the target processing module corresponding service running log is generated, for example, the target processing module 1 is called, and the network configuration is issued through the NETCONF channel, then the service running log includes the operation ID of the target service, the time of calling the target processing module 1, the network configuration start issuing time, the network configuration issuing end time, the network configuration issuing result, the processing module name and the like. The service running logs of all modules processing a service can constitute the actual service footprint of the service.

[0064] Step 130: generating the operation log corresponding to the target service carrying the operation ID.

[0065] Specifically, since the operation ID for uniquely identifying the target service has been generated, after the target service execution ends, the operation ID corresponding to the target service is generated, and in addition to carrying the operation ID of the target service, the operator of the target service, the operation content, the service processing time and the service processing result (service processing success / failure) can also be carried in the operation log.

[0066] Step 140: operation and maintenance based on the operation log and the service running log corresponding to each target processing module.

[0067] In the embodiment of the present application, the SDN controller can query and obtain each service operation and maintenance log and / or expected service footprint corresponding to the operation ID based on any service operation ID, and display the actual service footprint and / or expected service footprint of the service obtained through the display interface.

[0068] For example, the UI of the SDN controller supports displaying the actual service footprint through the operation ID, that is, the actual processing module name in the SDN controller service log and the operation result in the operation log are obtained through the operation ID, and the UI performs actual service footprint profiling on the obtained module name and operation result and displays.

[0069] For another example, the UI of the SDN controller supports displaying the service expected footprint through the operation ID, that is, the expected service footprint ID in the SDN controller operation log is obtained through the operation ID, and then the pre-stored expected service footprint of the SDN controller is obtained through the expected service footprint ID and displayed.

[0070] Further, in the embodiment of the present application, if the processing result of any target processing module is inconsistent with the expected processing result, the emergency recovery scheme corresponding to the target processing result is determined and the emergency recovery scheme is executed.

[0071] For example, due to all the services of the SDN controller, including northbound services and southbound services, each service has a service expected footprint and a corresponding emergency plan (each module in the expected footprint has a corresponding emergency recovery plan for handling exceptions). Then, the UI of the SDN controller supports comparing and displaying the difference between the actual service footprint and the service expected footprint through the operation ID, and giving the corresponding emergency plan to quickly recover the environment.

[0072] Of course, if the service processing logic of each processing module fails, resulting in service processing failure, the administrator can be notified in the form of an alarm for fault handling. In the embodiment of the present application, only the corresponding emergency plan is given for the service processing exception of each service processing module, for example, if the processing result of processing module 3 is abnormal, processing module 3 can be automatically rolled back, and the network configuration that has been issued is rolled back. After the rollback is completed, the service configuration is issued again.

[0073] As can be seen from the above, the operation and maintenance scheme provided by the present application does not need manual positioning, the SDN controller can visually display the preliminary positioning of the problem and the emergency plan, greatly improving the operation and maintenance efficiency, and meeting the needs of customers for rapid preliminary positioning and rapid recovery of the environment. After preliminary positioning, in-depth positioning only needs to export the service log and service running data of the related error module, greatly improving the export and positioning efficiency. The difficulty of problem positioning is reduced, and the operation and maintenance personnel can quickly familiarize with the corresponding service with the help of the service expected footprint. Whether the service processing modules are synchronous or asynchronous, the operation ID can be used to link the actual service processing flow, improving the positioning efficiency.

[0074] The operation and maintenance method based on the service footprint provided by the embodiment of the present application will be described in detail below in combination with a specific application scenario. For example, refer to Figure 2 Fig. 1 is a schematic diagram of a service processing process provided by the embodiment of the present application.

[0075] All the services of the SDN controller (including northbound services and southbound services) have a service expected footprint and a corresponding emergency plan (each module in the expected footprint has a corresponding recovery plan for handling exceptions). A REST API for obtaining the service expected footprint is provided externally, and the service expected footprint and the corresponding emergency plan are obtained through the service expected footprint ID for calling by the UI page.

[0076] Each operation of each service of the SDN controller has a unique operation ID, and the operation ID links all the processing modules of the corresponding service. The linking method is that the operation ID is included in the input parameter of each processing module, and the operation log (the operation log includes the operation ID and the operation result). A REST API for obtaining the operation result and the service expected footprint ID is provided externally, and the operation log is obtained through the operation ID for calling by the UI page.

[0077] For all services of the SDN controller, at the entry point of each processing module of each service, as well as at the entry and exit points of network device configurations distributed via the NETCONF channel, service footprint data is added to the service footprint database. Each service footprint includes an operation ID, operation time, and module name. A REST API is provided externally to retrieve the actual service footprint. By using the operation ID, the service footprint data in the service footprint database and the operation results in the operation log are retrieved, concatenated, and returned as the actual service footprint for the UI page to call.

[0078] The SDN controller's UI supports calling the SDN controller's REST API via operation ID to display the expected business footprint and the actual business footprint, as well as the difference between the expected and actual business footprints and corresponding contingency plans.

[0079] For example, see Figure 3 The diagram shown is a flowchart of a business expected footprint display provided in an embodiment of this application. The user selects an operation ID on the page and clicks to obtain the expected footprint. The SDN controller obtains the expected footprint ID corresponding to the operation ID from the operation log, obtains the expected footprint corresponding to the expected footprint ID from the business expected footprint database, and displays it on the page.

[0080] For example, see Figure 4 The diagram shows a flowchart of a business actual footprint display provided in an embodiment of this application. The user selects an operation ID on the page and clicks to obtain the actual footprint. Specifically, the SDN controller obtains the operation result corresponding to the operation ID from the operation log through the operation ID, obtains the actual footprint data corresponding to the operation ID from the business actual footprint database through the operation ID, concatenates them into a business actual footprint, and displays it on the page.

[0081] For example, see Figure 5 The diagram shows a flowchart of a footprint difference and emergency plan display provided in an embodiment of this application. The user selects an operation ID on the page and clicks to obtain the footprint difference and emergency plan. The SDN controller obtains the expected footprint from the business expected footprint database through the operation DI, and obtains the actual footprint data from the business actual footprint database through the operation ID. It compares the expected footprint with the actual footprint and determines whether the comparison results are consistent. If consistent, it returns the business actual footprint and displays it on the page. If inconsistent, it returns the business actual footprint plus the confirmed expected footprint, with a red 'x' added to the connecting line to indicate a broken link, along with the corresponding emergency plan, and displays it on the page.

[0082] For example, see Figure 6As shown, a structure schematic diagram of a service footprint-based operation and maintenance device provided by an embodiment of the present application is shown. The device is applied to an SDN controller, and the device comprises:

[0083] An acquisition unit 60 is configured to acquire a target service to be processed, and generate an operation ID corresponding to the target service;

[0084] A determination unit 61 is configured to determine a target processing module and a service processing logic required for processing the target service;

[0085] A generation unit 62 is configured to, when invoking any target processing module to process the target service based on the service processing logic, generate a service running log corresponding to the target processing module and carrying the operation ID, and each service running log constitutes an actual service footprint of the target service.

[0086] The generation unit 62 is further configured to generate an operation log corresponding to the target service and carrying the operation ID.

[0087] An operation and maintenance unit 63 is configured to perform operation and maintenance based on the operation log and the service running log corresponding to each target processing module.

[0088] Optionally, the SDN controller is preset with an expected service footprint of each service; after acquiring the target service to be processed,

[0089] The determination unit 61 is further configured to determine an expected service footprint ID corresponding to the target service based on a service attribute of the target service, and the operation log carries the expected service footprint ID corresponding to the target service.

[0090] Optionally, the operation log corresponding to one service further comprises an operator of the service, operation content, service processing time and service processing result; and the expected service footprint corresponding to one service comprises a processing module expected to be invoked when processing the service, expected processing results of each processing module expected to be invoked, and an emergency recovery scheme when the processing result of each processing module expected to be invoked is abnormal.

[0091] Optionally, the device further comprises:

[0092] A query unit is configured to query each service operation and maintenance log and / or expected service footprint corresponding to an operation ID of any service based on the operation ID.

[0093] A display unit is configured to display the actual service footprint and / or expected service footprint of the service obtained through the query by using a display interface.

[0094] Optionally, the device further comprises:

[0095] The execution unit is configured to determine an emergency recovery scheme corresponding to the target processing result and execute the emergency recovery scheme if the processing result of any target processing module is inconsistent with the expected processing result.

[0096] The above units can be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs), etc. For example, when a certain unit above is implemented in the form of a processing element scheduling program code, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can invoke program code. For another example, the units can be integrated together to implement a system-on-a-chip (SOC).

[0097] Further, the business footprint-based operation and maintenance device provided by the embodiments of the present application can be implemented from the hardware layer. The hardware architecture diagram of the business footprint-based operation and maintenance device can be seen from FIG. 1. Figure 7 As shown in FIG. 1, the business footprint-based operation and maintenance device can include a memory 70 and a processor 71.

[0098] The memory 70 is configured to store program instructions, and the processor 71 invokes the program instructions stored in the memory 70 to execute the above method embodiments according to the obtained program instructions. The specific implementation and technical effects are similar, and will not be repeated here.

[0099] Optionally, the present application also provides a business footprint-based operation and maintenance device, which includes at least one processing element (or chip) for executing the above method embodiments.

[0100] Optionally, the present application also provides a program product, such as a computer readable storage medium, which stores computer executable instructions for causing the computer to execute the above method embodiments.

[0101] Here, the machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device that contains or stores information, such as executable instructions, data, etc. For example, the machine-readable storage medium can be a Random Access Memory (RAM), a volatile memory, a non-volatile memory, a flash memory, a storage drive, such as a hard drive, a solid-state drive, any type of storage disk (e.g., a floppy disk, a DVD, a CD, etc.), or any suitable storage medium, or a combination thereof.

[0102] The systems, apparatuses, modules or units disclosed in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0103] For the convenience of description, the above apparatuses are described in various units by functions respectively. Of course, the functions of the units can be implemented in one or more software and / or hardware in the implementation of the present application.

[0104] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, a disk storage, a CD-ROM, an optical storage, etc.) containing computer-usable program code.

[0105] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce a device implemented in accordance with the flowcharts and / or block diagrams. Figure 1 The device for implementing the function specified in one flow or multiple flows and / or blocks. Figure 1 The device for implementing the function specified in one flow or multiple flows and / or blocks.

[0106] Moreover, these computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the flow Figure 1 The flow Figure 1 The flow

[0107] The computer program instructions can also be loaded into a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the flow Figure 1 The flow Figure 1 The flow

[0108] The above description is only preferred embodiments of the present application and is not used to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A service footprint-based operation and maintenance method, characterized in that, The method applied to an SDN controller comprises: acquiring a target service to be processed and generating an operation ID corresponding to the target service; determining a target processing module and service processing logic required for processing the target service; generating a service running log corresponding to the target processing module and carrying the operation ID when any target processing module is called to process the target service based on the service processing logic, each service running log constituting an actual service footprint of the target service; generating an operation log corresponding to the target service and carrying the operation ID; performing operation and maintenance based on the operation log and the service running log corresponding to each target processing module; wherein the SDN controller is preset with an expected service footprint of each service type, the expected service footprint corresponding to one service including a processing module expected to be called, expected processing results of each processing module expected to be called, and an emergency recovery scheme when the processing results of each processing module expected to be called are abnormal; comparing the actual processing result of any target processing module after the processing is completed with the corresponding expected processing result in the expected service footprint; if the processing result of the target processing module is inconsistent with the expected processing result, determining the emergency recovery scheme corresponding to the processing result and executing the emergency recovery scheme.

2. The method of claim 1, wherein, After acquiring the target service to be processed, the method further comprises: determining an expected service footprint ID corresponding to the target service based on the service attribute of the target service, the operation log carrying the expected service footprint ID corresponding to the target service.

3. The method of claim 2, wherein, The operation log corresponding to one service further includes an operator of the service, operation content, service processing time, and service processing result.

4. The method of claim 1 or 2, wherein, The method further comprises: querying and acquiring each service operation and maintenance log and / or expected service footprint corresponding to the operation ID of any service based on the operation ID, and displaying the actual service footprint and / or expected service footprint of the service obtained through the query on a display interface.

5. A service footprint-based operation and maintenance device, characterized in that, The device applied to an SDN controller comprises: an acquisition unit configured to acquire a target service to be processed and generate an operation ID corresponding to the target service; a determination unit configured to determine a target processing module and service processing logic required for processing the target service; a generation unit configured to, when any target processing module is called to process the target service based on the service processing logic, generate a service running log corresponding to the target processing module and carrying the operation ID, each service running log constituting an actual service footprint of the target service; the generation unit is further configured to generate an operation log corresponding to the target service and carrying the operation ID; an operation and maintenance unit configured to perform operation and maintenance based on the operation log and the service running log corresponding to each target processing module; wherein the SDN controller is preset with an expected service footprint of each service, the expected service footprint corresponding to one service including a processing module expected to be called, expected processing results of each processing module expected to be called, and an emergency recovery scheme when the processing results of each processing module expected to be called are abnormal; After any target processing module finishes processing, actual processing results thereof are compared with corresponding expected processing results in the expected service footprint; If the processing results of the target processing module are inconsistent with the expected processing results, an emergency recovery scheme corresponding to the processing results is determined, and the emergency recovery scheme is executed.

6. The apparatus of claim 5, wherein, After a target service to be processed is obtained, The determination unit is further configured to determine an expected service footprint ID corresponding to the target service based on a service attribute of the target service, and the operation log carries the expected service footprint ID corresponding to the target service.

7. The apparatus of claim 5 or 6, wherein, The device further includes: A query unit configured to query each service operation and / or maintenance log and / or expected service footprint corresponding to an operation ID of any service based on the operation ID. A display unit configured to display the actual service footprint and / or expected service footprint of the service obtained through a display interface.

8. A service footprint-based operation and maintenance device, characterized in that, The service footprint-based operation and maintenance device includes: A memory configured to store program instructions; A processor configured to call the program instructions stored in the memory and execute the steps of the method according to any one of claims 1-4.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing the computer to execute the steps of the method according to any one of claims 1-4.

Images