A business workflow method, system, and storage medium based on open-source HarmonyOS

Abstract

This invention discloses a business flow method, system, and storage medium based on the open-source HarmonyOS. It monitors whether any abnormal data processing events occur within the system of a first terminal device. If such an event occurs, a business flow request is sent to a second terminal device, enabling the second terminal device to recover from the abnormal data processing event in the first terminal device based on the received request. Both the first and second terminal devices are based on the HarmonyOS distributed soft bus. This invention, utilizing the design of the HarmonyOS distributed soft bus, transfers data processing events to another authenticated and secure terminal device when an abnormal data processing event occurs within the system of the first terminal device. This ensures data processing security while improving business recovery and data recovery efficiency.

Description

Technical Field

[0001] This invention relates to the fields of computer science and information technology, and in particular to a business flow method, system and storage medium based on the open-source HarmonyOS. Background Technology

[0002] In the current network environment, terminal devices may be subject to external interference, leading to service interruptions and data loss. Existing recovery methods typically involve backups, professional data recovery software, or cloud services. However, these methods are not only complex but also highly dependent on the severity of the situation and available resources, resulting in low recovery efficiency.

[0003] Therefore, the methods in the existing technology need further improvement. Summary of the Invention

[0004] In view of the shortcomings of the above-mentioned related technologies, the purpose of this invention is to provide a business flow method, system and storage medium based on open source HarmonyOS, to overcome the defects of low efficiency in business recovery and data recovery in the prior art.

[0005] The technical solution adopted by this invention to solve the technical problem is as follows:

[0006] In a first aspect, this embodiment discloses a business flow method based on the open-source HarmonyOS, wherein the method is applied to a first terminal device and includes:

[0007] Monitor whether any abnormal data processing events occur within the monitoring terminal system;

[0008] If an abnormal data processing event occurs, a service transfer request is sent to the second terminal device so that the second terminal device can recover from the abnormal data processing event that occurred in the first terminal device based on the received service transfer request; both the first terminal device and the second terminal device are terminal devices based on HarmonyOS distributed soft bus.

[0009] Optionally, before the step of sending the service transfer request to the second terminal device, the method further includes:

[0010] Obtain the device authentication information of the second terminal device;

[0011] Based on the device authentication information, the second terminal device is subjected to identity authentication, permission allocation, and access log recording operations respectively. Based on the verification results of identity authentication, permission allocation, and access log recording, it is determined whether the second terminal device is a secure terminal.

[0012] Optionally, the step of determining whether an abnormal data processing event has occurred within the monitoring terminal system includes:

[0013] Real-time acquisition of the terminal system's operating status and performance indicators;

[0014] The operating status and performance indicators are analyzed to determine whether any abnormal operating status or performance indicator events have occurred.

[0015] If an abnormal operation or performance indicator event occurs, the log file is read, and the log file is used to determine whether it is an abnormal event in data processing.

[0016] Optionally, the service transfer request includes the service type and processing event information corresponding to the abnormal event in data processing; the second terminal device responds to the service transfer request, obtains the service type and abnormal event information corresponding to the abnormal event in data processing, and obtains the data information required to process the abnormal event based on the abnormal event information, so as to realize the recovery processing of the abnormal event in data processing.

[0017] Secondly, a business workflow method based on the open-source HarmonyOS, which includes:

[0018] The first terminal device monitors whether any abnormal data processing events occur within its own system.

[0019] If the first terminal device detects an abnormal data processing event within its system, it sends a service transfer request to the second terminal device; wherein, both the first terminal device and the second terminal device are terminal devices based on the HarmonyOS distributed soft bus.

[0020] The second terminal device recovers from the data processing anomaly that occurred in the first terminal device based on the received service flow request.

[0021] Optionally, the step of the second terminal device restoring the service flow interruption event that occurred in the first terminal device according to the received recovery request includes:

[0022] The second terminal device responds to the recovery request and determines the service type and abnormal event information corresponding to the data processing abnormal event based on the recovery request;

[0023] Obtain the data information required for handling abnormal events based on business type and abnormal event information;

[0024] The abnormal events are recovered based on the acquired data.

[0025] Optionally, after the second terminal device executes the service flow recovery event, it further includes:

[0026] The second terminal device obtains the hardware status and software configuration of the first terminal device, and determines the cause of the abnormal data processing event in the first terminal device based on the hardware status and software configuration.

[0027] Thirdly, a business workflow system based on the open-source HarmonyOS, which includes a first terminal device and a second terminal device;

[0028] The first terminal device monitors whether any abnormal data processing events occur within the terminal system; if an abnormal data processing event occurs, it sends a service transfer request to the second terminal device.

[0029] The second terminal device recovers from abnormal data processing events that occurred in the first terminal device based on the received service flow request.

[0030] Optionally, the first terminal device further includes a security authentication module;

[0031] The security authentication module is used to obtain the device authentication information of the second terminal device, and perform identity authentication, permission allocation and access log recording operations on the second terminal device according to the device authentication information, and determine whether the second terminal device is a secure terminal based on the verification results of identity authentication, permission allocation and access log recording.

[0032] Fourthly, a computer storage medium, wherein the computer-readable storage medium stores a business flow program based on open-source HarmonyOS, and when the business flow program based on open-source HarmonyOS is executed by a processor, it implements the steps of the business flow method based on open-source HarmonyOS.

[0033] Beneficial effects:

[0034] This embodiment discloses a business flow method, system, and storage medium based on the open-source HarmonyOS. It monitors whether any abnormal data processing events occur within the system of a first terminal device. If such an event occurs, a business flow request is sent to a second terminal device, enabling the second terminal device to recover from the abnormal data processing event in the first terminal device based on the received request. Both the first and second terminal devices are based on the HarmonyOS distributed soft bus. This embodiment's method and system, utilizing the design of the HarmonyOS distributed soft bus, enables business flow between multiple devices when an abnormal data processing event occurs within the system of the first terminal device. The data processing event is transferred to another authenticated and secure terminal device for processing, ensuring data processing security while improving business recovery and data recovery efficiency. Attached Figure Description

[0035] Figure 1This is a flowchart illustrating the steps of a device control method based on the open-source HarmonyOS according to an embodiment of the present invention.

[0036] Figure 2 This is a system architecture diagram of the open-source HarmonyOS in an embodiment of the present invention;

[0037] Figure 3 This is a system architecture diagram of the equipment control system in an embodiment of the present invention;

[0038] Figure 4 This is a flowchart illustrating the steps involved in the specific application of the device control method in this embodiment of the invention. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0040] In existing technologies, terminal devices often encounter abnormal data processing events during use. For example, data transmission failures may occur during data output. When such failures occur, the terminal device typically restarts data processing to restore the service. During data storage, abnormal events can also lead to data breaches. In the event of a data breach, the terminal device's security system may be vulnerable to attack. Therefore, to avoid further losses from these abnormal events, it is necessary to handle them promptly and restore normal system operation and information maintenance.

[0041] However, traditional data recovery methods often require first diagnosing the cause of the fault, locating the fault point through analysis, implementing recovery operations on the fault point, and testing to determine whether the fault point has returned to normal after the recovery operation. Only after the system returns to normal can the data processing corresponding to the abnormal event be recovered. Therefore, it can be seen that the data processing and recovery methods in the existing technology are cumbersome. When the data processing of abnormal events is urgent, it is impossible to handle it in a timely manner, cannot ensure the rapid recovery of data processing in the terminal system, and cannot avoid the loss caused by abnormal events in the shortest possible time.

[0042] HarmonyOS is an open-source distributed operating system that provides a unified software platform for various devices. Because the system's functions and services are divided into independent service units, the operating system is more flexible and efficient. Modular development allows for more efficient development and management of system functions and services, while the service-oriented architecture promotes system reusability and composability. Based on HarmonyOS, a distributed operating system enables distributed collaboration among multiple devices, allowing for rapid response to abnormal events within the system.

[0043] To overcome the problem of low efficiency in handling data processing anomalies in existing technologies, this invention discloses a business flow method, system, and storage medium based on the open-source HarmonyOS. The method monitors whether anomalies occur in the system of a first terminal device. If an anomaly occurs, a business flow request is sent to a second terminal device, which then recovers from the anomaly based on the received request. Both the first and second terminal devices are based on the HarmonyOS distributed soft bus. This embodiment's method and system, utilizing the design of the HarmonyOS distributed soft bus, can transfer data processing events to another secure terminal device when an anomaly occurs in the system of the first terminal device. This ensures data processing security while improving business and data recovery efficiency, thereby achieving rapid response to anomalies.

[0044] The following description, in conjunction with the accompanying drawings, further illustrates a business flow method, system, and storage medium based on the open-source HarmonyOS disclosed in this embodiment.

[0045] like Figure 1 As shown, this embodiment discloses a business flow method based on the open-source HarmonyOS, applied to a first terminal device. The business flow method includes:

[0046] Step S1: Monitor whether any abnormal data processing events occur within the monitoring terminal system.

[0047] In this step, both the first and second terminal devices are based on the open-source HarmonyOS operating system. Because HarmonyOS employs a layered, hierarchical design, it enables business flow between multiple devices. For example... Figure 2 As shown, the open-source HarmonyOS consists of a kernel layer, a system service layer, an application framework layer, and an application layer from bottom to top. This hierarchical design allows the open-source HarmonyOS to adapt to the needs of different devices and to tailor or add corresponding subsystems or functions according to actual needs in multi-device deployment scenarios.

[0048] Combination Figure 3As shown, the HarmonyOS distributed soft bus is located in the system service layer 10 of the open-source HarmonyOS. Within this layer are components such as distributed task scheduling 110, distributed data management 120, distributed soft bus 130, and a multi-language runtime subsystem 140. These components together constitute the basic capability system set of open-source HarmonyOS, providing fundamental support for the operation, scheduling, and migration of distributed applications across multiple devices. Specifically, distributed task scheduling is used to execute tasks on multiple nodes to achieve high-performance task scheduling; distributed data management is used to manage data access, consistency, and integrity in a distributed environment, involving data synchronization across different locations; the distributed soft bus is used to shield the protocol differences between various devices to enable device discovery, connection, and communication; and the multi-language runtime subsystem is used to support the compilation and execution of multiple programming languages, thus supporting multiple languages.

[0049] Based on the distributed task scheduling, distributed data management, and distributed soft bus settings in the open-source HarmonyOS, when an abnormal event occurs in the first terminal device and business processing cannot be performed normally, the business process that needs to be processed can be transferred to the second terminal device based on the above distributed setup, thereby improving the efficiency of business processing.

[0050] The first and second terminal devices can be HarmonyOS-enabled devices with communication and information processing capabilities, such as smartphones, tablets, or computers. If multi-device collaboration is established between HarmonyOS devices via a distributed soft bus, multiple HarmonyOS devices need to be connected to the same local area network (LAN). Therefore, to achieve business flow between HarmonyOS devices, this step first obtains the device information of multiple HarmonyOS devices connected to the same LAN, resulting in a device list composed of these HarmonyOS devices. The device information included in this device list can be device name, device type, and / or device icon, or other device-related information. The device type is a mobile phone, computer, or tablet; the device name can be the name given to the device at the factory or a name modified by the user; and the device icon can be an icon corresponding to the device type. Each HarmonyOS device logs into the same device account, thus enabling another HarmonyOS device that has established multi-device collaboration with that device to promptly obtain the data corresponding to the business processing anomaly and handle the anomaly event when a business processing anomaly occurs on the first terminal.

[0051] In the specific implementation of this step, the first terminal device monitors in real time whether any abnormal events occur in the data processing within the system. Abnormal events in data processing may include: interruption of data processing task execution, errors or slowdown in execution, inability of the console to display data information, abnormal reporting of data processing results, or data loss. The first terminal device may be equipped with an anomaly monitoring module to obtain the running status information of data processing, and compare the data contained in the obtained running status information with the data in the normal running status, and determine whether an abnormal event in data processing has occurred based on the comparison results.

[0052] In detail, the steps in this process of monitoring whether abnormal data processing events occur within the terminal system include:

[0053] Step S11: Obtain the real-time operating status and performance indicators of the terminal system.

[0054] If the first terminal device uses an anomaly monitoring module to monitor abnormal events, this module is connected to various hardware modules or processors to obtain real-time operating status and performance indicators of the first terminal system. Operating status includes the device's network connection status, the signal strength corresponding to the network connection status, CPU and memory usage, remaining storage space, battery level, temperature, account information, and fault information. Performance indicators include: hardware performance indicators, communication capability performance indicators (network communication capability, information reception and reflection capability, data processing capability, and data storage capability), security performance indicators (including encryption chips and hardware-level security protection), business processing data performance indicators, or environmental performance indicators (temperature and humidity adaptability or noise and temperature adaptability).

[0055] Step S12: Analyze the operating status and performance indicators to determine whether any abnormal operating status or performance indicator events have occurred.

[0056] After obtaining the aforementioned operating status and performance indicators, these are analyzed. Each status data and performance indicator data is compared with the data during normal operation to analyze whether any abnormal operating status or performance indicator events have occurred. Specifically, the first terminal device stores standard values ​​for each status data and performance indicator data during normal device operation. The anomaly monitoring module can obtain these standard values ​​from the first terminal device. Alternatively, if the first terminal device does not contain the aforementioned standard value information, the anomaly monitoring module can obtain the standard value information from other terminal devices, thereby enabling the analysis of the operating status and performance indicators to determine whether any abnormal operating status or performance indicator events have occurred within the system.

[0057] Step S13: If an abnormal running status or performance indicator event occurs, read the log file and determine whether it is an abnormal event in data processing based on the log file.

[0058] If it is determined that an abnormal operation or performance indicator event has occurred in the system of the first terminal device, the log file corresponding to the abnormal event can be obtained, and the information recorded in the log file can be used to determine whether it is an abnormal event in data processing.

[0059] Specifically, abnormal events in data processing include: thread interruption, timeout, error, or other abnormal situations.

[0060] In another implementation, the method for determining whether an abnormal data processing event has occurred can also be implemented using a trained abnormal event determination model. The acquired current state data of the first terminal device is input into the abnormal event determination model, which analyzes the received state data to determine whether an abnormal event has occurred. Specifically, the abnormal event determination model is trained based on historical state data corresponding to a large number of terminal devices experiencing abnormal events.

[0061] Step S2: If an abnormal data processing event occurs, a service transfer request is sent to the second terminal device so that the second terminal device can recover from the abnormal data processing event that occurred in the first terminal device according to the received service transfer request; both the first terminal device and the second terminal device are terminal devices based on HarmonyOS distributed soft bus.

[0062] When an abnormal data processing event is detected in the first terminal device in step S1, the first terminal device first performs security verification on the second terminal device, which is also running the open-source HarmonyOS. Once the second terminal device passes the security verification, a service transfer request is sent to the second terminal device to handle the abnormal event using the secure second terminal device. Specifically, the first terminal device can either transfer only the service experiencing the abnormal event to the second terminal device, or it can transfer all remaining unfinished services to the second terminal device for processing.

[0063] If the first terminal device detects an abnormal data processing event within its system, it controls the sending of a service transfer request to the second terminal device. This allows the second terminal device to continue processing events that were not processed within its system, thereby enabling the data information to be processed as quickly as possible and avoiding delays in information processing caused by abnormalities within the first terminal device.

[0064] Furthermore, since the data processing anomaly occurred in the first terminal device, it indicates that the first terminal device may be under attack, resulting in security risks to the information stored in the first terminal device. Therefore, when the first terminal device sends a service transfer request to the second terminal device, it is necessary to determine that the second terminal device is a securely authenticated device to prevent the same data processing anomaly from occurring in the second terminal device, which would also prevent the data information from being processed normally. Therefore, before the step of sending the service transfer request to the second terminal device, the steps include: obtaining the device authentication information of the second terminal device; performing identity authentication, permission allocation, and access log recording operations on the second terminal device according to the device authentication information; and determining whether the second terminal device is a securely authenticated terminal based on the verification results of identity authentication, permission allocation, and access log recording.

[0065] Before the first terminal device sends a service transfer request to the second terminal device, it performs device security authentication on the second terminal device, obtains the device authentication information of the second terminal device, and sequentially performs identity verification, permission allocation, and access log recording operations based on the device authentication information. The result of these authentication operations determines whether the second terminal device is a secure terminal device. Device authentication information includes: device identifier and key, device information and corresponding key, digital certificate, etc. These elements are used to perform device identity verification, device permission allocation, and access log recording to obtain a verification result. If all the above verifications are successful, the second terminal device is determined to be a secure device.

[0066] Furthermore, the business flow request includes the business type and processing event information corresponding to the abnormal event in data processing; the second terminal device responds to the business flow request, obtains the business type and abnormal event information corresponding to the abnormal event in data processing, and obtains the data information required to process the abnormal event based on the abnormal event information, so as to realize the recovery processing of the abnormal event in data processing.

[0067] When the second terminal device receives a service transfer request, it retrieves information corresponding to the abnormal event based on the request, such as the service type corresponding to the abnormal event and the processing event information required to handle the event. The service type corresponding to the abnormal event can be data transmission interruption, data leakage, or data processing error, etc.

[0068] After receiving a service transfer request, the second terminal device needs to first determine whether the system has the function to process the service. If the current system has the function to process the service, it sets the time node and priority for processing the service to execute the corresponding service processing, and monitors the service processing status in real time. It adjusts for possible problems during service processing. If an anomaly still occurs, it adjusts the task allocation or time node in real time, or transmits the service processing to other terminal devices for processing, so as to achieve timely handling of abnormal events.

[0069] Specifically, after the second terminal device receives a service transfer request, it can also assess the risk of the corresponding processing service of the service transfer request, and determine whether there are potential risks or situations that cannot be processed normally. If there are potential risks to the second terminal device or the second terminal device is also unable to properly handle the service transfer request, it can propose to switch to other terminal devices for processing or issue an alarm to avoid affecting the second terminal device.

[0070] After the second terminal has finished processing the business flow request, it can also test and verify the processed business to ensure that abnormal events have been handled. The testing and verification can be functional testing, security testing, etc.

[0071] This embodiment, based on the aforementioned business workflow system, also discloses a business workflow method based on the open-source HarmonyOS, such as... Figure 4 As shown, the method includes:

[0072] Step H1: The first terminal device monitors whether any abnormal data processing events have occurred within its system;

[0073] If the first terminal device detects an abnormal data processing event within its system, it sends a service transfer request to the second terminal device; wherein, both the first terminal device and the second terminal device are terminal devices based on the HarmonyOS distributed soft bus.

[0074] In practical implementation, the first terminal device can be equipped with a service recovery controller, which is used to perform control operations related to service flow. First, the service recovery controller monitors the terminal device status in real time, monitors the terminal device's operating status, and determines whether it has been illegally intruded or attacked, or whether any situation has occurred that could harm the terminal device and affect information security. If any of the above situations occur, step H2 is executed.

[0075] Furthermore, the first terminal device can analyze the monitoring data of its own terminal, predict the risk of abnormal events that may occur at the terminal, and then take corresponding protective measures.

[0076] Specifically, the network traffic of this terminal device is monitored, or the application is monitored, or the terminal is located using GPS, in order to collect relevant data information from this terminal. The collected data information is compared with the historical data information of this terminal, the predicted data of the terminal in the next preset time period is analyzed, and the difference between the predicted data and the monitored data is determined, and the risk level is determined based on the difference.

[0077] When analyzing predictive data, a risk prediction model can be established. Historical data from normal operation and abnormal events collected by the terminal device are input into a pre-set network model for training. This allows the trained predictive network model to identify state data under abnormal events based on the input data. Suitable predictive models include Hidden Markov Models, regression analysis models, and time series analysis models. During data training, historically collected network traffic monitoring data, monitoring data collected from application monitoring, and location data obtained from GPS positioning of the terminal are normalized, then concatenated and input into the pre-set network model for training. This trains the network model, outputting prediction results. The parameters of the prediction model are then adjusted based on recently collected actual data to obtain the trained prediction model.

[0078] Based on the establishment of predictive models for risk forecasting and analysis, these models can be optimized according to actual conditions to improve their ability to predict abnormal events. Specifically, the predictive models can be updated and optimized periodically based on data collected recently, or the received data can be analyzed regularly to improve the predictive capabilities of the training dataset.

[0079] Step H2: The second terminal device recovers from the data processing anomaly that occurred in the first terminal device based on the received service flow request.

[0080] By using the business recovery controller to trigger business flow, the business flow being processed on the first terminal device is transferred to the second terminal device, so as to realize the recovery of data processing abnormal events through the second terminal device.

[0081] Furthermore, the step of the second terminal device restoring the service flow interruption event that occurred in the first terminal device according to the received recovery request includes:

[0082] Step H21: The second terminal device responds to the recovery request and determines the service type and abnormal event information corresponding to the data processing abnormal event based on the recovery request.

[0083] Step H22: Obtain the data information required for handling abnormal events based on the business type and abnormal event information.

[0084] Step H23: Perform recovery processing on the abnormal events based on the acquired data information.

[0085] Since the second terminal device needs information about the abnormal data processing event to be recovered in order to recover from the abnormal event, upon receiving a recovery request, it first needs to respond to the request and obtain the service type and abnormal event information related to the abnormal event. Once the service type and corresponding data information are obtained, recovery from the abnormal event is performed based on the data information and service type.

[0086] Furthermore, after the second terminal device executes the service flow recovery event, it also includes:

[0087] The second terminal device obtains the hardware status and software configuration of the first terminal device, and determines the cause of the data processing anomaly in the first terminal device based on the hardware status and software configuration.

[0088] After the second terminal device completes processing the transferred business, it can also obtain the hardware status and software configuration of the first terminal device to analyze the cause of abnormal events in the first terminal device, so as to restore the normal operation of the first terminal device more quickly. The steps for the second terminal device to obtain the hardware status of the first terminal device can be as follows: send a hardware status query command to the first terminal device; the first terminal device can use its own system to view hardware information such as CPU, memory, and hard drive; or it can use command-line tools to obtain hardware information. Software configuration can be obtained by viewing the operating system version information, installed software, and software running status; or by querying log information and analyzing the log information to find the cause of the fault.

[0089] This embodiment provides a fast and secure method for business transfer between terminals, especially for business transfer between risky terminals and secure terminals. It is applicable to various scenarios that need to deal with terminal devices being attacked by hackers, such as enterprise networks and personal devices.

[0090] In addition to disclosing the above-mentioned business flow method, this embodiment also discloses a business flow system based on the open-source HarmonyOS, which includes a first terminal device and a second terminal device.

[0091] The first terminal device monitors whether any abnormal data processing events occur within the terminal system; if an abnormal data processing event occurs, it sends a service transfer request to the second terminal device.

[0092] The second terminal device recovers from abnormal data processing events that occurred in the first terminal device based on the received service flow request.

[0093] Furthermore, the first terminal system also includes a security authentication module; the security authentication module is used to obtain the device authentication information of the second terminal device, and perform identity authentication, permission allocation and access log recording operations on the second terminal device according to the device authentication information, and determine whether the second terminal device is a verified secure terminal based on the verification results of identity authentication, permission allocation and access log recording.

[0094] Furthermore, the steps for determining whether an abnormal data processing event has occurred within the monitoring terminal system include:

[0095] Real-time acquisition of the terminal system's operating status and performance indicators;

[0096] The operating status and performance indicators are analyzed to determine whether any abnormal operating status or performance indicator events have occurred.

[0097] If an abnormal operation or performance indicator event occurs, the log file is read, and the log file is used to determine whether it is an abnormal event in data processing.

[0098] Furthermore, the business flow request includes the business type and processing event information corresponding to the abnormal event in data processing; the second terminal device responds to the business flow request, obtains the business type and abnormal event information corresponding to the abnormal event in data processing, and obtains the data information required to process the abnormal event based on the abnormal event information, so as to realize the recovery processing of the abnormal event in data processing.

[0099] Furthermore, the second terminal device includes: a recovery processing module;

[0100] The recovery processing module is used to respond to the recovery request, determine the business type and abnormal event information corresponding to the data processing abnormal event according to the recovery request; obtain the data information required to process the abnormal event based on the business type and abnormal event information; and perform recovery processing on the abnormal event based on the obtained data information.

[0101] Furthermore, the second terminal device includes: a fault detection module;

[0102] The fault detection module is used to acquire the hardware status and software configuration of the first terminal device, and determine the cause of the data processing abnormal event in the first terminal device based on the hardware status and software configuration.

[0103] This embodiment discloses a computer storage medium, wherein the computer-readable storage medium stores a business flow control program based on open source HarmonyOS. When the business flow control program based on open source HarmonyOS is executed by a processor, it implements the steps of the business flow method based on open source HarmonyOS.

[0104] The method and system of this embodiment provide a business flow method when a data processing anomaly occurs on a terminal device. It is particularly suitable for scenarios where business needs to be processed when encountering external attacks. The system of the terminal device in this embodiment is the HarmonyOS operating system. Through the distributed operating system of HarmonyOS, the business can be quickly transferred and restored, ensuring the continuity and security of the terminal device's business.

[0105] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0106] The embodiments described above are merely examples of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application.

Claims

1. A business workflow method based on open-source HarmonyOS, characterized in that, Applied to the first terminal device, including: Monitor whether any abnormal data processing events occur within the monitoring terminal system; If an abnormal data processing event occurs, a service transfer request is sent to the second terminal device so that the second terminal device can recover from the abnormal data processing event that occurred in the first terminal device based on the received service transfer request; both the first terminal device and the second terminal device are terminal devices based on HarmonyOS distributed soft bus.

2. The business flow method based on open-source HarmonyOS according to claim 1, characterized in that, Before the step of sending the service transfer request to the second terminal device, the method further includes: Obtain the device authentication information of the second terminal device; Based on the device authentication information, the second terminal device is subjected to identity authentication, permission allocation, and access log recording operations respectively. Based on the verification results of identity authentication, permission allocation, and access log recording, it is determined whether the second terminal device is a secure terminal.

3. The business flow method based on open-source HarmonyOS according to claim 1, characterized in that, The steps for determining whether an abnormal data processing event has occurred within the monitoring terminal system include: Real-time acquisition of the terminal system's operating status and performance indicators; The operating status and performance indicators are analyzed to determine whether any abnormal operating status or performance indicator events have occurred. If an abnormal operation or performance indicator event occurs, the log file is read, and the log file is used to determine whether it is an abnormal event in data processing.

4. The business flow method based on open-source HarmonyOS according to claim 1, characterized in that, The business flow request contains the business type and processing event information corresponding to the abnormal event involving data processing; The second terminal device responds to the service flow request, obtains the service type and abnormal event information corresponding to the abnormal event in the data processing, and obtains the data information required to process the abnormal event based on the abnormal event information, so as to realize the recovery processing of the abnormal event in the data processing.

5. A business workflow method based on open-source HarmonyOS, characterized in that, include: The first terminal device monitors whether any abnormal data processing events occur within its own system. If the first terminal device detects an abnormal data processing event within its system, it sends a service transfer request to the second terminal device; wherein, both the first terminal device and the second terminal device are terminal devices based on the HarmonyOS distributed soft bus. The second terminal device recovers from the data processing anomaly that occurred in the first terminal device based on the received service flow request.

6. The business flow method based on open-source HarmonyOS according to claim 5, characterized in that, The steps for the second terminal device to restore the service flow interruption event that occurred in the first terminal device according to the received recovery request include: The second terminal device responds to the recovery request and determines the service type and abnormal event information corresponding to the data processing abnormal event based on the recovery request; Obtain the data information required for handling abnormal events based on business type and abnormal event information; The abnormal events are recovered based on the acquired data.

7. The business flow method based on open-source HarmonyOS according to claim 5, characterized in that, After the second terminal device executes the service flow recovery event, it also includes: The second terminal device obtains the hardware status and software configuration of the first terminal device, and determines the cause of the data processing anomaly in the first terminal device based on the hardware status and software configuration.

8. A business workflow system based on the open-source HarmonyOS, characterized in that, Including a first terminal device and a second terminal device; The first terminal device monitors whether any abnormal data processing events occur within the terminal system. If an abnormal event occurs during data processing, a business transfer request is sent to the second terminal device; The second terminal device recovers from abnormal data processing events that occurred in the first terminal device based on the received service flow request.

9. The business workflow system based on open-source HarmonyOS according to claim 8, characterized in that, The first terminal device also includes a security authentication module; The security authentication module is used to obtain the device authentication information of the second terminal device, and perform identity authentication, permission allocation and access log recording operations on the second terminal device according to the device authentication information, and determine whether the second terminal device is a secure terminal based on the verification results of identity authentication, permission allocation and access log recording.

10. A computer storage medium, characterized in that, The computer storage medium stores a business flow program based on the open-source HarmonyOS. When the business flow program based on the open-source HarmonyOS is executed by the processor, it implements the steps of the business flow method based on the open-source HarmonyOS as described in any one of claims 1-7.

Images