Data processing system, method and equipment

Abstract

The invention provides a data processing system, method and equipment, which can be applied to the technical field of computers. The data processing system comprises a service request management platform used for generating a service request list of unplanned operation according to a received user input operation and sending the service request list to an operation and maintenance working platform; the operation and maintenance working platform is used for generating an electronic log according to the service request list; the job management platform is used for calling the electronic log and sending key information corresponding to the unplanned job to the centralized job scheduling platform according to the electronic log; and the centralized job scheduling platform is used for executing unplanned jobs according to the key information. According to the method and the device, the automatic implementation of the unplanned operation can be realized, the workload of manual operation is reduced, and the operation risk of the unplanned operation is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing system, method and device. Background Art

[0002] With the advent of the big data era, the banking industry has also undergone a comprehensive digital transformation. More and more new technologies and systems are being put into use, resulting in increasingly frequent changes in operations.

[0003] At present, the number of service request forms created for unplanned jobs has increased exponentially, while the job scheduling operations triggered by service requests still use traditional email / telephone communications and are manually performed by front-line operators on the corresponding platform, which not only increases the risk but also increases the workload of manual operations. Summary of the invention

[0004] The present application provides a data processing system, method and device, which can realize the automated implementation of unplanned operations, reduce the workload of manual operations, and reduce the operational risks of unplanned operations.

[0005] In a first aspect, the present application provides a data processing system, including a service request management platform, an operation and maintenance work platform, a job management platform, and a centralized job scheduling platform;

[0006] The service request management platform is used to: generate service request forms for unplanned operations based on received user input operations, and send the service request forms to the operation and maintenance work platform;

[0007] The operation and maintenance work platform is used to: generate an electronic log according to the service request form;

[0008] The operation management platform is used to: call the electronic log, and send the key information corresponding to the unplanned operation to the centralized operation scheduling platform according to the electronic log;

[0009] The centralized job scheduling platform is used to execute the unplanned jobs according to the key information.

[0010] In a possible implementation, the system further includes a rule base; the rule base includes execution date restriction conditions, execution time restriction conditions, and preceding execution conditions of unplanned operations.

[0011] In a possible implementation manner, the operation management platform is specifically used for:

[0012] Determining whether to schedule the unplanned job according to the conditions configured in the rule base;

[0013] If it is determined to schedule the unplanned job, the key information corresponding to the unplanned job is sent to the centralized job scheduling platform; the key information includes at least one of the following items: operation type, scheduling platform, date, node number, and sub-node number.

[0014] In a possible implementation manner, the operation management platform is further used for:

[0015] Acquire multiple service request forms generated by the service request management platform within a preset time period;

[0016] Analyzing the compliance and / or effectiveness of the plurality of service request tickets;

[0017] The rule base is updated according to the standardization and / or validity of the plurality of service request forms.

[0018] In a possible implementation manner, the service request management platform is specifically used for:

[0019] After the service request form is generated, the service request form is transferred to a service request review node; the service request review node is used for a service request reviewer to review the service request form;

[0020] After detecting that the service request review node has passed the review, the service request form is sent to the operation and maintenance work platform.

[0021] In a possible implementation manner, the operation and maintenance work platform is specifically used for:

[0022] When the service request form is received, the service request form is transferred to an operation and maintenance work review node; the operation and maintenance work review node is used for an operation and maintenance work reviewer to review the service request form;

[0023] If it is detected that the operation and maintenance work review node has passed the review, the electronic log is generated according to the service request form;

[0024] If it is detected that the operation and maintenance work review node fails the review, the service request form will be returned to the service request management platform.

[0025] In a second aspect, the present application provides a data processing method, the method comprising:

[0026] Generate a service request for unplanned operations based on received user input operations;

[0027] Generate electronic logs based on service request tickets;

[0028] Call the electronic log and determine the key information corresponding to the above unplanned operations based on the electronic log;

[0029] Based on the above key information, perform the above unplanned operations.

[0030] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0031] The memory stores computer-executable instructions;

[0032] The processor executes the computer-executable instructions stored in the memory to implement the data processing method provided in the first aspect.

[0033] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the data processing method provided in the first aspect.

[0034] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the data processing method provided in the first aspect.

[0035] The data processing system, method and equipment provided by the present application can realize a non-planned operation pipeline with centralized management, standardized operation content and automated operation implementation by integrating a service request management platform, an operation and maintenance work platform, a job management platform and a centralized operation scheduling platform, thereby reducing the frequency of manual operations, reducing the operational risks of non-planned operations, and standardizing the management of non-planned operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0037] Figure 1 A schematic diagram of a service request processing flow provided in the prior art;

[0038] Figure 2 A schematic diagram of the architecture of a data processing system provided in an embodiment of the present application;

[0039] Figure 3 A processing flow diagram of a data processing system provided in an embodiment of the present application;

[0040] Figure 4 A schematic diagram of a configuration interface of a rule library provided in an embodiment of the present application;

[0041] Figure 5 A schematic diagram of another configuration interface of a rule library provided in an embodiment of the present application;

[0042] Figure 6 A schematic diagram of a Kafka middleware information exchange framework provided in an embodiment of the present application;

[0043] Figure 7 A flowchart of a data processing method provided in an embodiment of the present application;

[0044] Figure 8 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application.

[0045] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0046] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0047] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0048] The following is an explanation of some of the technical terms involved in the embodiments of this application:

[0049] Service request management platform: a management platform that supports the creation, circulation, and approval of service request forms.

[0050] Operation and maintenance work platform: a comprehensive platform that integrates multiple production management and monitoring functions, supports real-time alarm monitoring, exception handling and implementation of production operation scheduling.

[0051] Job management platform: responsible for summarizing job implementation requirements, providing interfaces for calling the centralized job scheduling platform and managing it.

[0052] Centralized job scheduling platform: also known as batch centralized scheduling system (BoEing Job Scheduler, BJS), can automatically schedule the execution of jobs in the job schedule according to pre-set scheduling rules, and can feedback and update job status information.

[0053] Service Request: A work order created because the project team needs to start or stop certain work plans for production changes, maintenance, or upgrades.

[0054] Service request reviewer: The person responsible for reviewing service request forms on the service request management platform.

[0055] Electronic log: A collection of electronic log operation steps generated on the production operation workbench, triggered by a service request, including specific operation content, operation time and other information.

[0056] Unplanned operations: Compared with planned operations, unplanned operations mainly refer to sudden or non-routine operations that are not included in the original work schedule and cannot be arranged according to the inherent plan.

[0057] With the advent of the big data era, the banking industry has also undergone a comprehensive digital transformation. More and more new technologies and systems are being put into use, and changes are becoming increasingly frequent.

[0058] Currently, the number of service request forms for unplanned jobs is growing exponentially, and the job scheduling operations triggered by these service requests still use traditional email / telephone communications and are manually performed by front-line operators on the corresponding platform, which is risky and increases the workload.

[0059] For example, refer to Figure 1 , Figure 1 The present invention is a schematic diagram of a service request processing flow provided in the prior art.

[0060] exist Figure 1 First, the operator manually operates on the corresponding platform based on email communication to generate an electronic log. Then other operators manually trigger the execution of corresponding functions in the centralized job scheduling platform based on the electronic log.

[0061] As the number of service requests continues to rise, the pressure on front-line operators to perform manual operations is increasing day by day. In addition, due to problems such as incomplete and non-standard descriptions of service requests, operational errors frequently occur, which in turn leads to a surge in operational risks or a geometric increase in workload, seriously threatening the smooth and efficient production operation.

[0062] In view of the above-mentioned technical problems, a business data processing system is provided in an embodiment of the present application. By integrating a service request management platform, an operation and maintenance work platform, a job management platform and a centralized job scheduling platform, it is possible to realize a non-planned job pipeline with centralized management, standardized operation content and automated operation implementation, thereby reducing the frequency of manual operations, reducing the operational risks of non-planned operations, and standardizing the management of non-planned operations.

[0063] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0064] Reference Figure 2 , Figure 2 This is a schematic diagram of the architecture of a data processing system provided in an embodiment of the present application; the data processing system includes a service request management platform 201, an operation and maintenance work platform 202, a job management platform 203 and a centralized job scheduling platform 204.

[0065] In some implementations, the service request management platform 201 is used to generate a service request form for an unplanned operation according to a received user input operation, and send the service request form to the operation and maintenance work platform 202 .

[0066] Specifically, an operator can initiate a service request form on the service request management platform 201 and transfer it to a service request reviewer.

[0067] The service request management platform 201 may send the service request form to the operation and maintenance work platform 202 in response to an audit-approved instruction triggered by a service request auditor.

[0068] In some embodiments, the service request management platform 201 is responsible for receiving user input operations. These input operations can come from different channels, such as online forms, telephone requests, emails, etc. After receiving the user input, the service request management platform 201 can generate a service request form for an unplanned operation based on the input content. The service request form records in detail key information such as the user's needs, the urgency of the request, and the type of operation. After the service request form is generated, it is sent to the operation and maintenance work platform 202 for the next step of processing.

[0069] The operation and maintenance work platform 202 is used to generate an electronic log according to the above service request form.

[0070] In some embodiments, after receiving the service request form, the operation and maintenance work platform 202 can automatically (according to system configuration) or based on user operations generate an electronic log. The electronic log not only records the content of the service request form, but also includes notes and progress updates during the processing process.

[0071] In some implementations, after the operation and maintenance work platform 202 generates the electronic log, it can store it and prepare it for the job management platform 203 to call.

[0072] The job management platform 203 is used to call the electronic log and send the key information corresponding to the unplanned job to the centralized job scheduling platform 204 according to the electronic log.

[0073] In some implementations, the job management platform 203 may call the electronic log periodically or according to specific rule conditions.

[0074] In some implementations, the job management platform 203 may extract key information of unplanned jobs from the electronic log, such as job type, required resources, execution time, etc. After extracting the key information, the job management platform 203 may send the key information to the centralized job scheduling platform 204 for job scheduling and execution.

[0075] The centralized job scheduling platform 204 is used to execute the above-mentioned unplanned jobs according to the above-mentioned key information.

[0076] In some embodiments, after receiving the key information, the centralized job scheduling platform 204 can automatically or manually (based on the job type and urgency) schedule and execute unplanned jobs according to system configuration and available resources.

[0077] Through the above methods, efficient processing of unplanned operations is achieved. From user input to the execution of unplanned operations, the entire process is automated and digitized, greatly improving work efficiency and accuracy.

[0078] The data processing system provided in the embodiments of the present application can realize an unplanned operation pipeline with centralized management, standardized operation content, and automated operation implementation by integrating a service request management platform, an operation and maintenance work platform, a job management platform, and a centralized job scheduling platform, thereby reducing the frequency of manual operations, reducing the operational risks of unplanned operations, and standardizing the management of unplanned operations.

[0079] Reference Figure 3 , Figure 3 A processing flow diagram of a data processing system provided in an embodiment of the present application.

[0080] In some embodiments, after generating a service request form, the service request management platform transfers the service request form to a service request review node; the service request review node is used for service request reviewers to review the service request form; after detecting that the service request review node has passed the review, the service request management platform sends the service request form to the operation and maintenance work platform.

[0081] When the operation and maintenance work platform receives a service request form, the service request form is transferred to the operation and maintenance work review node; the operation and maintenance work review node is used for the operation and maintenance work review personnel to review the above service request form.

[0082] If the operation and maintenance work platform detects that the operation and maintenance work review node has passed the review, an electronic log will be generated based on the above service request form; if it detects that the above operation and maintenance work review node has failed the review, the above service request form will be returned to the above service request management platform.

[0083] In some implementations, the electronic log triggered by the service request form is in draft form (not visible to the front line), and is formally published on a dedicated interface by a production operation analyst, and service request forms that do not meet the requirements are returned.

[0084] In some implementations, the centralized job scheduling platform may call a unified interface provided by the job management platform according to pre-set rules to execute corresponding unplanned job plans.

[0085] In some implementations, if automatic scheduling fails, front-line operators can log in to the operation and maintenance work platform to perform operations and transfer service request forms.

[0086] In some implementations, after executing the corresponding unplanned work plan, the centralized job scheduling platform can determine the execution result. If the execution is successful, the clearance order is verified. If the execution fails, manual processing is assisted. After the manual processing is successful, the clearance order is verified.

[0087] In some implementations, the automatically scheduled successful service request form can be transferred back to the service request management platform. After the service request management platform receives the transferred service request form, if the service request form initiator closes the service request form, it means that the processing flow of the entire service request form is completed.

[0088] The data processing system provided in the embodiment of the present application can realize the orderly flow of work orders and the automation of job scheduling by integrating the service request platform, the operation and maintenance work platform, the job management platform and the centralized job scheduling platform. It solves the problems of lack of standardized operation procedures, decentralized operations and management loopholes in front-line manual operations when implementing unplanned operations in the production and operation field of large banks. It realizes the online management and automated implementation process of unplanned operations in service request scenarios, which helps to promote centralized management of production and operation operations, standardization of operation content, and automation of operation implementation, effectively reducing the risk of manual operation execution and the number of operation steps.

[0089] Based on the contents described in the above embodiments, in some embodiments of the present application, the above data processing system also includes a rule base; the rule base includes execution date constraints, execution time constraints and preceding execution conditions of unplanned jobs.

[0090] In some implementations, the rule base can be established by integrating existing rules through preliminary research.

[0091] Reference Figure 4 , Figure 4 A schematic diagram of a configuration interface of a rule library provided in an embodiment of the present application.

[0092] Specifically, Figure 4 For rules configured for date conditions.

[0093] In some implementations, the rule configuration of the date condition can limit the date range according to the "date range", the "date limit" specifies whether the preset condition is met or not, and the rule is linked according to AND / OR, which can support nesting multiple sub-rules, such as Figure 3 The display rules are as follows: the date is a holiday or not the end of the month, and the date range is between 2024-08-08 and 2024-10-11.

[0094] In some implementations, the rule base may also include rules configured for time and preconditions.

[0095] Reference Figure 5 , Figure 5 A schematic diagram of another configuration interface of a rule library provided in an embodiment of the present application.

[0096] like Figure 5 As shown, after configuring the date, you should also configure the specific execution time and the preceding execution condition. The preceding execution condition is the preceding non-time condition, and the time requirement is the preceding time condition.

[0097] After configuring the rules and saving them, the system can automatically schedule according to the corresponding rules. The automatic scheduling rules shown above are: holidays or not the end of the month, and the date range is between 2024-08-08 and 2024-10-11. At 14:53 every day, after task 001 is completed, the automatic scheduling operation corresponding to 000 will be automatically executed.

[0098] In some implementations, for some special rules, such as operations that the system cannot automatically schedule, such as receiving notifications, semi-automatic and semi-manual operations can be used. After receiving the notification, the front-line operator clicks to trigger the corresponding automatic scheduling operation, and the subsequent process is consistent with the automatic scheduling process.

[0099] In some implementations, the job management platform can determine whether to schedule an unplanned job based on the conditions configured in the rule base; if it is determined to schedule an unplanned job, the key information corresponding to the unplanned job is sent to the centralized job scheduling platform. Optionally, the key information includes at least one of the following: operation type, scheduling platform, date, node number, and subnode number.

[0100] In some implementations, the system can poll the electronic operation log of the day every minute based on pre-configured rule conditions, automatically determine whether to automatically schedule unplanned jobs, and transmit information such as operation type, scheduling platform, date, node number, sub-node number, etc. to the centralized job scheduling platform through the air interface provided by the job management platform to perform corresponding operations.

[0101] Among them, automatic scheduling failures can be marked in the electronic log, and front-line personnel can be reminded to perform manual operations.

[0102] In some implementations, a job plan that fails in automatic scheduling can be manually re-done, with one person operating and one person reviewing to confirm the start and end of the operation.

[0103] For example, the manual re-planning process for a failed job includes:

[0104] a) Operation starts:

[0105] In some implementations, the operation starts with a manual judgment of the execution conditions of the previous order. After clicking, the system automatically judges according to the given time. If the previous order is a condition that the system cannot judge, such as "accepting notification", a prompt box will pop up and continue after manual confirmation. Among them, if the system determines that the previous order is not satisfied, it can also be manually enforced.

[0106] b) Review begins

[0107] In some implementations, the review begins with manual work, and the actual automatic scheduling of unplanned jobs is a review of the "operator starting the operation". If the scheduling fails, a pop-up reminder will appear. At this time, the front-line operator needs to communicate with the project team to see if the information is filled in correctly. After confirmation, log in to the centralized job scheduling platform to perform manual scheduling operations.

[0108] c) Operation completed

[0109] In some implementations, the end of the operation is manually performed to determine whether the execution result meets expectations. After automatic scheduling or manual operation on a centralized job scheduling platform, the execution result is automatically determined based on the "successful execution result set". When the node fails to achieve the established execution result, the project team can be communicated with, and the project team can take over the investigation and manually force the "end of the operation" to be completed, to facilitate the flow of subsequent service request forms.

[0110] d) Review completed

[0111] In some implementations, the end of the review is a confirmation of the flow of the service request form during manual re-doing, and the relevant operation information of the manual re-doing is automatically written into the content of the service request form.

[0112] In some implementations, it is also possible to obtain multiple service request forms generated by the service request management platform within a preset time period; analyze the standardization and / or validity of the multiple service request forms; and update the above-mentioned rule library based on the standardization and / or validity of the multiple service request forms.

[0113] In the above implementation, when manually supplementing the scheduling of unplanned jobs, the overall process is innovatively divided into four steps of "operation start, review start, operation end, review end" on the basis of one person operating and one person reviewing. Each step has its own execution task, which further reduces the system load pressure while ensuring rationality.

[0114] The data processing system provided in the embodiment of the present application proposes an automated process for scheduling unplanned operations and implements this function. A rule library for unplanned scheduling is added on the basis of the planned rule library, thereby realizing a comprehensive upgrade from manual execution to automatic scheduling of unplanned operation scheduling such as emergency changes, standard changes, and production verification, which greatly reduces the risks of front-line operations, improves work efficiency, and makes the overall process more standardized.

[0115] In order to replace the original unplanned manual work, a service request type unplanned work pipeline is designed, and it is positioned according to the three platforms (service request management platform, operation and maintenance work platform, and operation management platform). Through platform integration, each platform can play its own role, among which: the service request management platform is responsible for the creation and review of event tickets; the operation and maintenance work platform is responsible for the generation and operation of electronic logs for unplanned operations; the operation management platform is responsible for accepting operation instructions, uniformly publishing and executing them, breaking through the barriers of each platform, connecting the three platforms in series, and finally realizing assembly line operation, centralized management of production and operation operations, standardized operation content, and automated operation implementation, effectively reducing the risk of manual operation execution and the number of operation steps.

[0116] Reference Figure 6 , Figure 6 A schematic diagram of a Kafka middleware information exchange framework provided in an embodiment of the present application.

[0117] In some implementations, clients connected to different servers use kafka message queues for communication, and webSocket is used to establish a long link between the client and the server. The main information exchange process is as follows:

[0118] Client a sends the information it wants to send and its own sessionId to server a. Server a processes the relevant information and performs database operations, pushes the processing results to client a as soon as possible, and then sends the message and client a's SessionId to the kafka middleware. Server a and server b apply for different topics with their own IP addresses to ensure that the Topic names between different servers are different, and different Topic messages are consumed only once. Topic1 pushes the message to server a, and Topic2 pushes the message to server b. Then the server pushes the message to the client that has established a long socket connection. Note that client a will be excluded based on SessionId at this time to prevent client a from receiving messages twice.

[0119] Among them, Kafka is a distributed stream processing platform that provides message persistence and a message middleware based on publish-subscribe mode. It also supports point-to-point communication by configuring the same groupId on the consumer side. WebSocket is a full-duplex communication protocol on a single TCP connection, which allows real-time two-way communication between the client and the server.

[0120] Due to production safety requirements, all manual operations require one person to operate and one person to review. The original operation process does not support real-time data updates, and the data between each client is completely isolated, resulting in inconsistent data between the front-end and back-end, and inconsistent data between each client. When the number of front-line operations increases at night, it is easy to perform multiple operations on the same step due to inconsistent data, which greatly affects the front-line safety operation and maintenance, and is likely to cause irreversible consequences.

[0121] In an embodiment of the present application, when different clients interact with each other, based on this project, only the same production package is deployed on multiple servers, and the IP addresses of different servers are innovatively used as different Topics, so as to achieve the purpose of creating different Topics on two servers with the same deployment package, so that clients connected to different servers can communicate seamlessly through Kafka. At the same time, webSocket is used to build a long link, and its heartbeat reconnection and the background broadcast every ten minutes (pushing the latest background data to the front end) are used to ensure the accuracy of the interface data and avoid the problem of inconsistent data display between the front and back ends or different clients.

[0122] Based on the contents described in the above embodiments, a data processing method is also provided in the embodiments of the present application. The data processing method includes:

[0123] S1. Generate a service request form for an unplanned operation based on the received user input operation.

[0124] S2. Generate an electronic log based on the above service request form.

[0125] S3. Call the electronic log and determine the key information corresponding to the unplanned operation according to the electronic log.

[0126] S4. Based on the above key information, perform the above unplanned operations.

[0127] Reference Figure 7 , Figure 7 The following is a flow chart of a data processing method provided in an embodiment of the present application. In some embodiments of the present application, the data processing method includes:

[0128] 1. The user enters service request information into the service request management platform.

[0129] 2. The service request management platform generates a service request form based on the input service request information.

[0130] 3. The service request management platform reviews the service request form.

[0131] 4.1. If the review fails, the service request management platform will return the service request to the user.

[0132] 4.2. If the review is passed, the service request management platform will send a service request form to the operation and maintenance work platform.

[0133] 5. The operation and maintenance work platform generates electronic logs based on service request forms.

[0134] 6. The operation and maintenance work platform reviews the electronic log.

[0135] 7.1. If the review fails, the operation and maintenance work platform will return the service request form to the service request management platform.

[0136] 7.2. If the review is passed, the operation and maintenance work platform will publish an electronic log.

[0137] 8. The job management platform automatically schedules electronic logs.

[0138] 9. The centralized job scheduling platform schedules and executes unplanned jobs.

[0139] 10. The centralized job scheduling platform returns scheduling information to the job management platform.

[0140] 11. The job management platform returns scheduling information to the operation and maintenance work platform.

[0141] In case of scheduling failure:

[0142] 12. Manual scheduling electronic log of the job management platform.

[0143] 13. The centralized job scheduling platform schedules and executes unplanned jobs.

[0144] 14. The centralized job scheduling platform returns scheduling information to the job management platform.

[0145] 15. The job management platform returns scheduling information to the operation and maintenance work platform.

[0146] In case of successful scheduling:

[0147] 16. The service request management platform closes the service request ticket.

[0148] Furthermore, based on the contents described in the above embodiments, an electronic device is also provided in an embodiment of the present application, which includes at least one processor and a memory; wherein the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory to implement the various steps in the data processing method described in the above embodiments.

[0149] In order to better understand the embodiments of the present application, refer to Figure 8 , Figure 8 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application.

[0150] like Figure 8 As shown, the electronic device 80 of this embodiment includes: a processor 801 and a memory 802; wherein:

[0151] Memory 802, used to store computer-executable instructions;

[0152] The processor 801 is used to execute the computer-executable instructions stored in the memory to implement the various steps in the data processing method described in the above embodiment.

[0153] Optionally, the memory 802 may be independent or integrated with the processor 801 .

[0154] When the memory 802 is independently provided, the device further includes a bus 803 for connecting the memory 802 and the processor 801 .

[0155] An embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, each step in the data processing method described in the above embodiment is implemented.

[0156] An embodiment of the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, the computer program implements the various steps in the data processing method described in the above embodiment.

[0157] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0158] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0159] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0160] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the method described in each embodiment of the present application.

[0161] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0162] The memory may include high-speed memory, and may also include non-volatile storage, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0163] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0164] The storage medium may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory, electrically erasable programmable read-only memory, erasable programmable read-only memory, programmable read-only memory, read-only memory, magnetic memory, flash memory, magnetic disk or optical disk. The storage medium may be any available medium that can be accessed by a general or special purpose computer.

[0165] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A data processing system, characterized in that: Including service request management platform, operation and maintenance work platform, job management platform and centralized job scheduling platform; The service request management platform is used to: generate a service request form for an unplanned operation according to a received user input operation, and send the service request form to the operation and maintenance work platform; The operation and maintenance work platform is used to: generate an electronic log according to the service request form; The operation management platform is used to: call the electronic log, and send the key information corresponding to the unplanned operation to the centralized operation scheduling platform according to the electronic log; The centralized job scheduling platform is used to execute the unplanned job according to the key information.

2. The system according to claim 1, characterized in that The system also includes a rule base; the rule base includes execution date restriction conditions, execution time restriction conditions and preceding execution conditions of unplanned operations.

3. The system according to claim 2, characterized in that The operation management platform is specifically used for: Determining whether to schedule the unplanned job according to the conditions configured in the rule base; If it is determined to schedule the unplanned job, the key information corresponding to the unplanned job is sent to the centralized job scheduling platform; the key information includes at least one of the following items: operation type, scheduling platform, date, node number, and sub-node number.

4. The system according to claim 2, characterized in that The operation management platform is also used for: Acquire multiple service request forms generated by the service request management platform within a preset time period; Analyzing the compliance and / or effectiveness of the plurality of service request tickets; The rule base is updated according to the standardization and / or validity of the plurality of service request forms.

5. The system according to claim 1, characterized in that The service request management platform is specifically used for: After the service request form is generated, the service request form is transferred to a service request review node; the service request review node is used for a service request reviewer to review the service request form; After detecting that the service request review node has passed the review, the service request form is sent to the operation and maintenance work platform.

6. The system according to claim 1 or 5, characterized in that: The operation and maintenance work platform is specifically used for: When the service request form is received, the service request form is transferred to an operation and maintenance work review node; the operation and maintenance work review node is used for an operation and maintenance work reviewer to review the service request form; If it is detected that the operation and maintenance work review node has passed the review, the electronic log is generated according to the service request form; If it is detected that the operation and maintenance work review node fails the review, the service request form will be returned to the service request management platform.

7. A data processing method, characterized in that: The method comprises: Generate a service request for unplanned operations based on received user input operations; generating an electronic log according to the service request form; calling the electronic log, and determining key information corresponding to the unplanned operation according to the electronic log; The unplanned operation is performed according to the key information.

8. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the data processing method according to claim 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the data processing method according to claim 7 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the data processing method according to claim 7 when being executed by a processor.

Images