Business management method, apparatus, device, storage medium, and program product

Abstract

The application discloses a service management method, device, equipment, storage medium and program product. The method comprises the following steps: acquiring a predicted total processing time length of a target service, the target service being processed by N devices, wherein N is a positive integer; splitting the predicted total processing time length according to a work flow of the target service to obtain N predicted device processing time lengths, the N predicted device processing time lengths corresponding to the N devices one by one, the work flow comprising a processing flow of the N devices; in the case that an actual device processing time length of a first device in the N devices is greater than a predicted device processing time length, determining an abnormal behavior in the first device; and executing a management strategy corresponding to the abnormal behavior. According to the embodiment of the application, the compliance rate and stability of an index work can be improved.

Description

Technical Field

[0001] This application belongs to the field of business processing technology, and in particular relates to a business management method, apparatus, equipment, storage medium and program product. Background Technology

[0002] In the current process of promoting the timeliness of indicators, it is impossible to effectively manage and monitor the indicator processing process. Therefore, when a failure occurs and the timeliness is delayed, it is often impossible to notify the relevant person in charge in time, so that the person in charge can investigate and deal with the problem, and it is also impossible to provide corresponding solutions to the failure. This leads to serious delays in timeliness and further prevents business personnel from obtaining the required indicator data in a timely manner, reducing the achievement rate and stability of indicator operations. Summary of the Invention

[0003] This application provides a business management method, apparatus, device, storage medium, and program product that can solve the problem of low compliance rate and stability of existing target operations.

[0004] In a first aspect, embodiments of this application provide a business management method, the method comprising:

[0005] Obtain the estimated total processing time of the target service, which is processed by N devices, where N is a positive integer;

[0006] The total estimated processing time is broken down according to the work process of the target business to obtain N estimated equipment processing times. The N estimated equipment processing times correspond one-to-one with the N equipment. The work process includes the processing flow of the N equipment.

[0007] If, among the N devices, the actual processing time of the first device exceeds the expected processing time, the abnormal behavior in the first device is determined.

[0008] Execute the management strategy corresponding to the abnormal behavior.

[0009] In some embodiments, the N devices include source devices and local devices, and the abnormal behavior is: the actual processing time of the first processing flow of the source device is abnormal;

[0010] The management strategy corresponding to the execution of the abnormal behavior includes at least one of the following:

[0011] If the local device does not receive source file job data before the time limit baseline, an alarm message is sent to the associated device of the target service. The time limit baseline is set according to the first expected device processing time of the source device, and the source file job data is the data obtained by the source device from processing the first source table through the first processing flow.

[0012] If the local device does not receive the source file job data within the estimated total processing time, a first alarm flag is set for the first source table;

[0013] If the number of first alarm flags in the first source table exceeds the first threshold within the first preset time period, then a second alarm flag is set for the first source table.

[0014] In some embodiments, the N devices include source devices and local devices, and the abnormal behavior is: the transmission time of source file job data from the source device to the local device is greater than a preset transmission threshold;

[0015] The management strategy corresponding to the execution of the abnormal behavior includes:

[0016] The transmission process of source file operation data is changed from batch transmission to real-time transmission. The source file operation data is the data obtained by the source device through the first processing flow to process the first source table.

[0017] In some embodiments, the N devices include local devices, and the abnormal behavior is: the second processing flow of the local device is abnormal;

[0018] The management strategy corresponding to the execution of the abnormal behavior includes at least one of the following:

[0019] The source file operation data is determined as the data source of the first sub-processing flow. The source file operation data is the data obtained by the source equipment through the first processing flow to process the first source table. The second processing flow includes the first sub-processing flow.

[0020] The priority of the first sub-process is changed from the first priority to the second priority, where the second priority is higher than the first priority;

[0021] The workflow of the first sub-process is broken down.

[0022] In some embodiments, the N devices include local devices, and the abnormal behavior is: the second processing flow of the local device is abnormal;

[0023] The management strategy corresponding to the execution of the abnormal behavior includes:

[0024] Determine the second estimated processing time for the local device;

[0025] If the second processing flow is not completed within the processing time of the second device after the local device receives the source file operation data, an alarm message is sent to the associated device of the target service.

[0026] In some embodiments, after executing the management policy corresponding to the abnormal behavior, the method further includes:

[0027] This displays the completion rate of the target service within the estimated total processing time.

[0028] Secondly, embodiments of this application provide a business management device, the device comprising:

[0029] The acquisition module is used to acquire the estimated total processing time of the target service, which is processed by N devices, where N is a positive integer;

[0030] The splitting module is used to split the total estimated processing time according to the work process of the target business to obtain N estimated device processing times, wherein the N estimated device processing times correspond one-to-one with the N devices, and the work process includes the processing flow of the N devices;

[0031] The determination module is used to determine abnormal behavior in the first device when the actual device processing time of the first device in the N devices is greater than the expected device processing time.

[0032] The execution module is used to execute the management strategy corresponding to the abnormal behavior.

[0033] Thirdly, embodiments of this application provide a business management device, the device including: a processor and a memory storing computer program instructions;

[0034] The processor implements the above business management method when executing computer program instructions.

[0035] Fourthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the above-mentioned business management method.

[0036] Fifthly, embodiments of this application provide a computer program product, which includes computer program instructions. When the computer program instructions are executed by a processor, they implement the above-mentioned business management method.

[0037] This application estimates the total expected processing time for target tasks and breaks it down according to the target business workflow. It then estimates the expected processing time for N devices performing the processing flow on N devices. When the actual processing time exceeds the expected processing time, it confirms an abnormal behavior and executes the corresponding management strategy to eliminate the workflow anomaly. This establishes a time-sensitive operational mechanism that automatically identifies abnormal behavior when a fault occurs and further executes the corresponding management strategy, ensuring the target task achievement rate and stability. Attached Figure Description

[0038] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 This is a flowchart illustrating a business management method provided in an embodiment of this application;

[0040] Figure 2 This is a schematic diagram of the hardware structure of a business management device provided in an embodiment of this application;

[0041] Figure 3 This is a schematic diagram of the structure of a business management device provided in an embodiment of this application. Detailed Implementation

[0042] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples of this application.

[0043] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0044] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0045] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. The embodiments will now be described in detail with reference to the accompanying drawings.

[0046] In the current process of advancing the timeliness of indicators, there is no effective management and monitoring of the indicator processing. Therefore, when a failure occurs and causes a delay in timeliness, the existing fault handling measures are to switch between the two clusters after the failure. However, the existing fault handling measures are relatively crude. The current process of advancing the timeliness of indicators lacks a complete operation mechanism and timeliness monitoring mechanism. Therefore, it is impossible to notify the relevant person in charge in the first place when a failure causes a delay, so that the person in charge can investigate and deal with the problem. This results in a serious delay in timeliness, and business personnel cannot obtain the required indicator data in a timely manner.

[0047] To address the aforementioned issues, this application incorporates the entire process of indicator processing into the operational scope, establishing a complete timeliness operation mechanism and monitoring and early warning mechanism. This mechanism can be automatically adjusted according to actual application requirements, providing a favorable guarantee for achieving timeliness targets.

[0048] Specifically, in order to solve the problems of the prior art, embodiments of this application provide a business management method, apparatus, device, storage medium, and program product. The business management method provided by embodiments of this application will be described first below.

[0049] Figure 1 A flowchart illustrating a business management method according to an embodiment of this application is shown. The method includes the following steps:

[0050] S110, obtain the estimated total processing time of the target service, wherein the target service is processed by N devices, and N is a positive integer.

[0051] In this embodiment, after the user determines the metrics that need to be monitored, these metrics can be identified as the target service. The estimated total processing time of the target service can then be determined based on the acquisition process of the target service or the user's needs. The target service is processed jointly by N devices.

[0052] The process of obtaining the target business is as follows: retrieve the source table corresponding to the target business from the database. The source table records the raw data required by the target business. Use N devices to perform a series of processing operations on the raw data in the source table to obtain the target business.

[0053] In one embodiment, a series of processing operations includes end-processing operations, intermediate processing operations, and source file operations. End-processing operations are those that directly obtain metrics, source file operations are those that directly apply source tables from the database, and intermediate processing operations are other processing operations besides end-processing operations and source file operations. There is a correspondence between metrics and end-processing operations; one end-processing operation may correspond to one metric or multiple metrics. Because there is a correspondence between target business and end-processing operations, the end-processing operations corresponding to the target business can be determined through the target business. Furthermore, based on the interdependencies between operations, the intermediate processing operations corresponding to the target business can be determined through the end-processing operations, tracing back to the source of the processing operations level by level, and identifying the source file operations and source tables corresponding to the target business.

[0054] S120, the estimated total processing time is divided into N estimated device processing times according to the work process of the target business, and the N estimated device processing times correspond one-to-one with the N devices. The work process includes the processing flow of the N devices.

[0055] In this embodiment, since the operation process of the target service is composed of the processing processes of N devices, the total expected processing time of the target service can include the expected processing time of N devices, and the processing process of each device corresponds to an expected processing time of one device.

[0056] In addition, to ensure that the target business can be completed within the total processing time set by the user, the total processing time can also include a buffer period. The buffer period is a buffer time reserved to avoid delays caused by the impact of unexpected events on the workflow.

[0057] In one embodiment, N is 2, and the N devices include local devices and source devices. The workflow is then divided into source device processing workflow and local device processing workflow. The estimated total processing time is 8 hours. Based on the processing tasks included in the source device processing workflow and the local device processing workflow, the estimated total processing time of 8 hours can be divided into: 2 hours of estimated source device processing time, 4 hours of estimated local device processing time, and 2 hours of buffer time.

[0058] S130, if the actual processing time of the first device among the N devices is longer than the expected processing time, an abnormal behavior in the first device is determined.

[0059] In this embodiment, if the actual processing time of the first device among N devices is found to be longer than the expected processing time, it can be determined that the processing flow of the first device is abnormal, and the abnormal behavior in the abnormal processing flow can be further determined. The abnormal behavior may include the calculation process of the processing flow being too complex, the waiting process being too long, and the data transmission time between different devices being too long, etc.

[0060] S140, execute the management strategy corresponding to the abnormal behavior.

[0061] In this embodiment, different abnormal behaviors correspond to different management strategies. When abnormal behavior is detected in the work process of the target business and the abnormal behavior is identified, the management strategy corresponding to the abnormal behavior can be executed to eliminate the abnormality of the work process through targeted management strategies.

[0062] This application estimates the total expected processing time for target tasks and breaks it down according to the target business workflow. It then estimates the expected processing time for N devices performing the processing flow on N devices. When the actual processing time exceeds the expected processing time, it confirms an abnormal behavior and executes the corresponding management strategy to eliminate the workflow anomaly. This establishes a time-sensitive operational mechanism that automatically identifies abnormal behavior when a fault occurs and further executes the corresponding management strategy, ensuring the target task achievement rate and stability.

[0063] As an optional embodiment, the N devices include source devices and local devices, and the abnormal behavior is: the actual processing time of the first processing flow of the source device is abnormal;

[0064] The above S140 may include at least one of the following:

[0065] If the local device does not receive source file job data before the time limit baseline, an alarm message is sent to the associated device of the target service. The time limit baseline is set according to the first expected device processing time of the source device, and the source file job data is the data obtained by the source device from processing the first source table through the first processing flow.

[0066] If the local device does not receive the source file job data within the estimated total processing time, a first alarm flag is set for the first source table;

[0067] If the number of first alarm flags in the first source table exceeds the first threshold within the first preset time period, then a second alarm flag is set for the first source table.

[0068] In this embodiment, N is 2, and the N devices include source devices and local devices. The source devices are used to process the source table through the first processing flow to obtain source file operation data, and send the source file operation data to the local devices. The local devices further process the source file operation data to obtain the target service.

[0069] The timeline is the point in time at which the local device should receive the source work data, set based on the start time of the work process and the first estimated processing time of the source device. If the local device does not receive the source work data before the timeline, it can be considered that the actual processing time of the first processing process is abnormal, and an alarm message can be sent to the associated device of the target business to remind the relevant personnel of the target business that the source device has failed.

[0070] If the local device fails to receive the source file data within the estimated total processing time after the start time of the workflow, a first alarm flag can be set for the first source table corresponding to the target service. If the first alarm flag of the first source table exceeds a first threshold within a first preset time period, a second alarm flag can be set for the first source table. The first and second alarm flags are used to indicate different degrees of problems in the workflow of the target service and can be viewed by relevant personnel and managers of the target service.

[0071] Using the above methods, when a malfunction causes a delay, the relevant person in charge can be notified immediately, allowing them to investigate and resolve the problem.

[0072] As an optional embodiment, the N devices include source devices and local devices, and the abnormal behavior is: the transmission time of source file job data from the source device to the local device is greater than a preset transmission threshold;

[0073] The above-mentioned S140 may include:

[0074] The transmission process of source file operation data is changed from batch transmission to real-time transmission. The source file operation data is the data obtained by the source device through the first processing flow to process the first source table.

[0075] In this embodiment, N is 2, and the N devices include source devices and local devices. During the process of the source device transmitting source file job data to the local device, the transmission time may be too long due to the large amount of source file job data. In this case, the transmission process of source file job data can be changed from batch transmission to real-time transmission.

[0076] Specifically, batch transmission involves the source device obtaining all source file operation data through the first processing step, and then transmitting all the source file operation data to the local device at once. Real-time transmission, on the other hand, involves transmitting the source file operation data to the local device in batches during the first processing step of the source device. By changing the transmission method of the source file operation data, the data transmission time can be reduced, and the compliance rate of the operation process can be improved.

[0077] As an optional embodiment, the N devices include local devices, and the abnormal behavior is: the second processing flow of the local device is abnormal;

[0078] The above-mentioned S140 may also include at least one of the following:

[0079] The source file operation data is determined as the data source of the first sub-processing flow. The source file operation data is the data obtained by the source equipment through the first processing flow to process the first source table. The second processing flow includes the first sub-processing flow.

[0080] The priority of the first sub-process is changed from the first priority to the second priority, where the second priority is higher than the first priority;

[0081] The workflow of the first sub-process is broken down.

[0082] In this embodiment, the abnormal behavior of the local device includes various types, and different execution strategies can be adopted for different types of abnormal behavior of the local device. The second processing flow includes multiple sub-processing flows.

[0083] In one embodiment, the abnormal behavior of the local device is that the processing path of the first sub-processing flow is too complex. For example, the data source of the first sub-processing flow is the result of other sub-processing flows in the second processing flow, which includes multiple unnecessary data. Filtering out these unnecessary data requires a lot of time. To overcome the above problem, the source file operation data can be directly identified as the data source of the first sub-processing flow, and the path of the first sub-processing flow can be penetrated to avoid the complexity of the path causing the second processing flow to take too long.

[0084] In another embodiment, the abnormal behavior of the local device is that the priority of the first sub-processing process is too low. Since the priority is too low, the waiting time of the first sub-processing process is too long. In order to overcome the above problem, the priority of the first sub-processing process can be changed from the first priority to the second priority. Since the second priority is higher than the first priority, the waiting time of the first sub-processing process can be shortened, and the second processing process can be prevented from taking too long.

[0085] In another embodiment, the abnormal behavior of the local device is that the workflow of the first sub-processing process is too slow. Since the workflow of the first sub-processing process may include multiple items, one or more of these items may significantly affect the progress of the workflow. To overcome this problem, the workflow can be divided into multiple sub-workflows to avoid the workflow being slowed down by one or more items. This, in turn, prevents the second processing process from taking too long.

[0086] As an optional embodiment, the N devices include local devices, and the abnormal behavior is: the second processing flow of the local device is abnormal;

[0087] The above-mentioned S140 may include:

[0088] Determine the second estimated processing time for the local device;

[0089] If the second processing flow is not completed within the processing time of the second device after the local device receives the source file operation data, an alarm message is sent to the associated device of the target service.

[0090] In this embodiment, the second estimated device processing time is the processing time of the local device estimated by the user. If the local device does not complete the second processing flow within the second device processing time after receiving the source file job data, it can be determined that there is an abnormality in the second processing flow. Then, an alarm message can be sent to the associated device of the target business to remind the staff of the target business that the local device has failed.

[0091] As an optional embodiment, after S140 above, it may further include:

[0092] This displays the completion rate of the target service within the estimated total processing time.

[0093] In this embodiment, to enable timeliness operation personnel to promptly view timeliness-related data and quickly understand the reasons for delays, a timeliness monitoring platform can be established for all parties to view in a timely manner. This platform can display the completion rate of target tasks within the estimated total processing time, the completion time of each target task, and the current status of each source file's operational data.

[0094] Based on the business management method provided in the above embodiments, this application also provides specific implementations of the business management device. Please refer to the following embodiments.

[0095] First see Figure 2 The business management device 200 provided in this application embodiment includes the following modules:

[0096] The acquisition module 201 is used to acquire the estimated total processing time of the target service, which is processed by N devices, where N is a positive integer;

[0097] The splitting module 202 is used to split the total estimated processing time according to the work process of the target business to obtain N estimated device processing times, wherein the N estimated device processing times correspond one-to-one with the N devices, and the work process includes the processing flow of the N devices;

[0098] The determination module 203 is used to determine abnormal behavior in the first device when the actual device processing time of the first device in the N devices is greater than the expected device processing time.

[0099] The execution module 204 is used to execute the management strategy corresponding to the abnormal behavior.

[0100] This application estimates the total expected processing time for target tasks and breaks it down according to the target business workflow. It then estimates the expected processing time for N devices performing the processing flow on N devices. When the actual processing time exceeds the expected processing time, it confirms an abnormal behavior and executes the corresponding management strategy to eliminate the workflow anomaly. This establishes a time-sensitive operational mechanism that automatically identifies abnormal behavior when a fault occurs and further executes the corresponding management strategy, ensuring the target task achievement rate and stability.

[0101] As one implementation of this application, the execution module 204 may further include:

[0102] The first execution unit is configured to send an alarm message to the associated device of the target service if the local device does not receive the source file job data before the time limit baseline. The time limit baseline is set according to the first expected device processing time of the source device, and the source file job data is the data obtained by the source device through the first processing flow to process the first source table.

[0103] The second execution unit is configured to set a first alarm flag on the first source table if the local device does not receive the source file job data within the estimated total processing time.

[0104] The third execution unit is configured to set a second alarm flag for the first source table if the number of first alarm flags in the first source table exceeds a first threshold within a first preset time period.

[0105] As one implementation of this application, the execution module 204 may further include:

[0106] The fourth execution unit is used to convert the transmission process of source file operation data from batch transmission to real-time transmission. The source file operation data is the data obtained by the source device through the first processing flow to process the first source table.

[0107] As one implementation of this application, the execution module 204 may further include:

[0108] The fifth execution unit is used to determine the source file operation data as the data source of the first sub-processing flow, wherein the source file operation data is the data obtained by the source equipment through the first processing flow to process the first source table, and the second processing flow includes the first sub-processing flow;

[0109] The sixth execution unit is used to modify the priority of the first sub-processing flow from the first priority to the second priority, wherein the second priority is higher than the first priority;

[0110] The seventh execution unit is used to split the workflow of the first sub-processing process.

[0111] As one implementation of this application, the execution module 204 may further include:

[0112] A determining unit is used to determine the second estimated device processing time corresponding to the local device;

[0113] The eighth execution unit is used to send an alarm message to the associated device of the target service if the second processing flow is not completed within the second device processing time after the local device receives the source file job data.

[0114] As one implementation of this application, the aforementioned business management device 200 may further include:

[0115] The display unit is used to display the completion rate of the target service within the estimated total processing time.

[0116] Figure 3 A schematic diagram of the hardware structure of the business management device provided in an embodiment of this application is shown.

[0117] The business management device may include a processor 301 and a memory 302 storing computer program instructions.

[0118] Specifically, the processor 301 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0119] Memory 302 may include mass storage for data or instructions. For example, and not limitingly, memory 302 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 302 may include removable or non-removable (or fixed) media. Where appropriate, memory 302 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 302 is non-volatile solid-state memory.

[0120] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the methods according to one aspect of this disclosure.

[0121] The processor 301 reads and executes computer program instructions stored in the memory 302 to implement any of the business management methods in the above embodiments.

[0122] In one example, the service management device may further include a communication interface 303 and a bus 310. For example, Figure 3As shown, the processor 301, memory 302, and communication interface 303 are connected through bus 310 and complete communication with each other.

[0123] The communication interface 303 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0124] Bus 310 includes hardware, software, or both, that couples components of a business management device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGp) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LpC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (pCI) bus, a pCI-Express (pCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 310 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.

[0125] The business management device can be based on the above embodiments to realize the business management method and apparatus described above.

[0126] Furthermore, in conjunction with the business management methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the business management methods in the above embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here. The aforementioned computer-readable storage medium may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc., and is not limited thereto.

[0127] In addition, this application also provides a computer program product, including computer program instructions, which, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.

[0128] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0129] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0130] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0131] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations 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, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0132] The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A business management method, characterized in that, The business management methods include: Obtain the estimated total processing time of the target service, which is processed by N devices, where N is a positive integer, the target service includes indicators that need to be monitored, and the N devices include source devices and local devices; The total estimated processing time is broken down according to the work process of the target business to obtain N estimated equipment processing times. The N estimated equipment processing times correspond one-to-one with the N equipment. The work process includes the processing flow of the N equipment. If, among the N devices, the actual processing time of the first device exceeds the expected processing time, an abnormal behavior is determined in the first device. The abnormal behavior includes an abnormality in the second processing flow of the local device, which includes multiple sub-processing flows. Execute the management strategy corresponding to the abnormal behavior; The management strategy corresponding to the execution of the abnormal behavior includes at least one of the following: The source file operation data is determined as the data source of the first sub-processing flow. The source file operation data is the data obtained by the source equipment through the first processing flow to process the first source table. The second processing flow includes the first sub-processing flow. The priority of the first sub-process is changed from the first priority to the second priority, where the second priority is higher than the first priority; The workflow of the first sub-process is broken down.

2. The business management method according to claim 1, characterized in that, The N devices include source devices and local devices, and the abnormal behavior is: the actual processing time of the first processing flow of the source device is abnormal; The management strategy corresponding to the execution of the abnormal behavior includes at least one of the following: If the local device does not receive source file job data before the time limit baseline, an alarm message is sent to the associated device of the target service. The time limit baseline is set according to the first expected device processing time of the source device, and the source file job data is the data obtained by the source device from processing the first source table through the first processing flow. If the local device does not receive the source file job data within the estimated total processing time, a first alarm flag is set for the first source table; If the number of first alarm flags in the first source table exceeds the first threshold within the first preset time period, then a second alarm flag is set for the first source table.

3. The business management method according to claim 1, characterized in that, The N devices include source devices and local devices, and the abnormal behavior is: the transmission time of source file operation data from the source device to the local device is greater than a preset transmission threshold. The management strategy corresponding to the execution of the abnormal behavior includes: The transmission process of source file operation data is changed from batch transmission to real-time transmission. The source file operation data is the data obtained by the source device through the first processing flow to process the first source table.

4. The business management method according to claim 1, characterized in that, The N devices include local devices, and the abnormal behavior is: the second processing flow of the local device is abnormal; The management strategy corresponding to the execution of the abnormal behavior includes: Determine the second estimated processing time for the local device; If the second processing flow is not completed within the processing time of the second device after the local device receives the source file operation data, an alarm message is sent to the associated device of the target service.

5. The business management method according to claim 1, characterized in that, After executing the management policy corresponding to the abnormal behavior, the method further includes: This displays the completion rate of the target service within the estimated total processing time.

6. A business management device, characterized in that, The device includes: The acquisition module is used to acquire the estimated total processing time of the target service, which is processed by N devices, where N is a positive integer. The target service includes indicators that need to be monitored, and the N devices include source devices and local devices. The splitting module is used to split the total estimated processing time according to the work process of the target business to obtain N estimated device processing times, wherein the N estimated device processing times correspond one-to-one with the N devices, and the work process includes the processing flow of the N devices; The determination module is used to determine abnormal behavior in the first device when the actual processing time of the first device in the N devices is greater than the expected processing time. The abnormal behavior includes an abnormality in the second processing flow of the local device, and the second processing flow includes multiple sub-processing flows. An execution module is used to execute the management strategy corresponding to the abnormal behavior; the execution of the management strategy corresponding to the abnormal behavior includes at least one of the following: determining the source file operation data as the data source of the first sub-processing flow, the source file operation data being the data obtained by the source device processing the first source table through the first processing flow, the second processing flow including the first sub-processing flow; modifying the priority of the first sub-processing flow from a first priority to a second priority, the second priority being higher than the first priority; and splitting the workflow of the first sub-processing flow.

7. A business management device, characterized in that, The business management device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the business management method as described in any one of claims 1-5.

8. A computer storage medium, characterized in that, The computer storage medium stores computer program instructions, which, when executed by a processor, implement the business management method as described in any one of claims 1-5.

9. A computer program product, characterized in that, The computer program product includes computer program instructions, which, when executed by a processor, implement the business management method according to any one of claims 1-5.

Images