A method, device and storage medium for storing business data

By saving data asynchronously or synchronously based on the data type of the business application on the server, and controlling client operations through feedback information, the data security problem in client application software is solved, and secure data storage and monitoring are achieved.

CN113221195BActive Publication Date: 2024-11-26BEIJING DAJIA INTERNET INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110441336.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-04-23
Publication Date
2024-11-26
Estimated Expiration
2041-04-23

AI Technical Summary

Technical Problem

In existing technologies, client application software cannot effectively track and monitor business data during use, leading to data leakage, affecting data security, and lacking effective security measures.

Method used

Depending on the type of business data, the server saves data asynchronously or synchronously, and instructs the client to continue running or disable the application software through feedback information to ensure data security.

Benefits of technology

It enables the categorized storage of data of different business types, ensuring data security, preventing data leakage, and improving the data security of client application software.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113221195B_ABST
    Figure CN113221195B_ABST
Patent Text Reader

Abstract

The present disclosure relates to the field of computers, and discloses a method, device and storage medium for saving business data. The method comprises the following steps: a server receives a business data saving request sent by a client for target application software; if the business type of the business data does not conform to a preset mandatory saving rule, the server saves the business data in an asynchronous manner and returns first feedback information at the same time; the first feedback information is used to instruct the client to continue running the target application software; if the business type conforms to the preset mandatory saving rule, the server saves the business data in a synchronous manner and returns second feedback information after the saving result of the business data is a failure; the second feedback information is used to instruct the client to disable the current operation of the target application software; the process of saving business data adopts different strategies to instruct the client to continue running or to prohibit the current operation, thereby effectively saving the business data actually used by the target application software in the client and ensuring the security of the business data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to computer technology, and in particular to a method, device and storage medium for storing business data. Background Art

[0002] At present, client applications have become popular, and correspondingly, application software has also become diverse, such as social software, shopping software, road traffic software, financial management software, medical treatment software, work interaction software, entertainment video software, and access control alarm software, etc.

[0003] Typically, various business data are generated during the use of application software on a client.

[0004] For example, when using financial management application software, you will enter bank account and money-related business data.

[0005] For example, when using entertainment video application software, you can publish works involving business data such as personal copyright.

[0006] However, the application software in the client will face great security risks during use. For example, it is impossible to effectively track the business data generated by each application software during the use of the application software, as well as the specific use stage information of the above business data. This will lead to the leakage of some business data and cannot be monitored in time, thus seriously affecting the security of business data.

[0007] In summary, there is currently no effective solution to ensure the security of business data in application software. Summary of the invention

[0008] The embodiments of the present disclosure provide a method, device and storage medium for storing business data, so as to ensure the security of business data.

[0009] The specific technical solutions provided by this disclosure are as follows:

[0010] In a first aspect, a method for storing business data is applied to a server, comprising:

[0011] receiving a business data saving request sent by a client to a target application software, wherein the target application software runs on the client;

[0012] Determine the business type of the business data based on the business data preservation request;

[0013] If the service type does not conform to the preset mandatory saving rule, the service data of the target application software is saved in an asynchronous manner, and first feedback information is returned to the client, where the first feedback information is used to instruct the client to continue running the target application software;

[0014] If the business type meets the preset mandatory saving rules, the business data of the target application software is saved in a synchronous manner, and when the saving result of the business data is failure, second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software.

[0015] Optionally, based on the business data saving request, determining the business type of the business data includes:

[0016] If the business data preservation request is a non-mandatory preservation request, determining that the business type of the business data does not comply with a preset mandatory preservation rule;

[0017] If the business data preservation request is a mandatory preservation request, it is determined that the business type of the business data complies with a preset mandatory preservation rule.

[0018] Optionally, if the service type does not conform to the preset mandatory saving rule, the service data of the target application software is saved in an asynchronous manner, and first feedback information is returned to the client, where the first feedback information is used to instruct the client to continue running the target application software, including:

[0019] If the service type does not conform to the preset mandatory preservation rule, returning first feedback information to the client after receiving the service data preservation request, the first feedback information is used to instruct the client to continue running the target application software;

[0020] Save the business data of the target application software into the database.

[0021] Optionally, the business data of the target application software is saved in a database, including:

[0022] The business data of the target application software is sent to the distributed publish-subscribe message system or the internal thread pool, and the business data of the target application software is saved in the database through the distributed publish-subscribe message system or the internal thread pool.

[0023] Optionally, if the service type meets the preset mandatory saving rule, the service data of the target application software is saved in a synchronous manner, and when the saving result of the service data is a failure, second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software, including:

[0024] If the business type meets the preset mandatory preservation rules, the business data of the target application software is saved in the database after receiving the business data preservation request;

[0025] If the saving result is a failure, second feedback information is returned to the client, and the second feedback information is used to indicate that the target application software has received abnormal information and disabled the current operation.

[0026] Optionally, the business data includes at least business data identification information ID, usage phase information and usage data;

[0027] Save the business data of the target application software into the database, including:

[0028] Create at least three new fields in the database;

[0029] In the at least three created fields, the ID, the usage stage information and the usage data are saved respectively; among them, the usage data is saved in the json format.

[0030] In a second aspect, a method for storing business data is applied to a client, comprising:

[0031] In response to a data saving operation triggered for a target application software in a running state, generating a corresponding business data saving request;

[0032] Sending a business data saving request to a server so that the server performs the following operations: receiving the business data saving request, and determining the business type of the business data based on the business data saving request; if the business type does not conform to a preset mandatory saving rule, saving the business data of the target application software in an asynchronous manner and generating first feedback information; if the business type conforms to the preset mandatory saving rule, saving the business data of the target application software in a synchronous manner, and generating second feedback information when the saving result of the business data is failure;

[0033] If the first feedback information returned by the server is received, continue to run the target application software;

[0034] If the second feedback information returned by the server is received, the current operation of the target application software is disabled.

[0035] Optionally, in response to a data saving operation triggered for a target application software in a running state, generating a corresponding service data saving request includes:

[0036] In response to a data saving operation triggered on a target application software in a running state, determining an editing type of business data in the target application software;

[0037] When the editing type of the business data is modification, the modified business data is obtained, the modified business data is fully transmitted to the server, and a business data saving request is generated based on the modified business data;

[0038] When the editing type of the business data is unmodified, the business data identifier or content distribution network CDN address is extracted, and a business data save request is generated based on the identifier or CDN address, wherein the identifier or CDN address is used to provide a basis for the server to find and save the business data.

[0039] Optionally, in response to a data saving operation triggered for a target application software in a running state, the method includes:

[0040] In response to one or any combination of a data adding operation, a data deleting operation, a data modifying operation and a data status changing operation triggered for the target application software.

[0041] In a third aspect, a device for storing business data is applied to a server, comprising:

[0042] A receiving unit, configured to receive a service data saving request sent by a client to a target application software, wherein the target application software runs on the client;

[0043] A determination unit, configured to determine a business type of the business data based on a business data saving request;

[0044] A saving unit, configured to save the business data of the target application software in an asynchronous manner if the business type does not conform to a preset mandatory saving rule, and return first feedback information to the client, wherein the first feedback information is used to instruct the client to continue running the target application software;

[0045] And, if the business type meets the preset mandatory saving rules, the business data of the target application software is saved in a synchronous manner, and when the saving result of the business data is failure, the second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software.

[0046] Optionally, based on the business data saving request, the business type of the business data is determined, and the determining unit is used to:

[0047] If the business data preservation request is a non-mandatory preservation request, determining that the business type of the business data does not comply with a preset mandatory preservation rule;

[0048] If the business data preservation request is a mandatory preservation request, it is determined that the business type of the business data complies with a preset mandatory preservation rule.

[0049] Optionally, if the service type does not meet the preset mandatory saving rule, the service data of the target application software is saved in an asynchronous manner, and first feedback information is returned to the client, the first feedback information is used to instruct the client to continue running the target application software, and the saving unit is used to:

[0050] If the service type does not conform to the preset mandatory preservation rule, returning first feedback information to the client after receiving the service data preservation request, the first feedback information is used to instruct the client to continue running the target application software;

[0051] Save the business data of the target application software into the database.

[0052] Optionally, the business data of the target application software is saved in a database, and the saving unit is used to:

[0053] The business data of the target application software is sent to the distributed publish-subscribe message system or the internal thread pool, and the business data of the target application software is saved in the database through the distributed publish-subscribe message system or the internal thread pool.

[0054] Optionally, if the service type meets the preset mandatory saving rule, the service data of the target application software is saved in a synchronous manner, and when the saving result of the service data is a failure, second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software. The saving unit is used to:

[0055] If the business type meets the preset mandatory preservation rules, the business data of the target application software is saved in the database after receiving the business data preservation request;

[0056] If the saving result is a failure, second feedback information is returned to the client, and the second feedback information is used to indicate that the target application software has received abnormal information and disabled the current operation.

[0057] Optionally, the business data at least includes business data identification information ID, usage phase information and usage data; the business data of the target application software is saved in a database, and the saving unit is used to:

[0058] Create at least three new fields in the database;

[0059] In the at least three created fields, the ID, the usage stage information and the usage data are saved respectively; among them, the usage data is saved in the json format.

[0060] In a fourth aspect, a device for storing business data is applied to a client, comprising:

[0061] A response unit, configured to generate a corresponding business data save request in response to a data save operation triggered for a target application software in a running state;

[0062] A sending unit, used to send a business data saving request to a server, so that the server performs the following operations: receiving the business data saving request, and determining the business type of the business data based on the business data saving request, if the business type does not meet the preset mandatory saving rule, saving the business data of the target application software in an asynchronous manner and generating first feedback information, if the business type meets the preset mandatory saving rule, saving the business data of the target application software in a synchronous manner, and generating second feedback information when the saving result of the business data is failure;

[0063] A processing unit, configured to continue running the target application software if first feedback information returned by the server is received;

[0064] And, if the second feedback information returned by the server is received, the current operation of the target application software is disabled.

[0065] Optionally, in response to a data saving operation triggered for a target application software in a running state, a corresponding service data saving request is generated, and the response unit is used to:

[0066] In response to a data saving operation triggered on a target application software in a running state, determining an editing type of business data in the target application software;

[0067] When the editing type of the business data is modification, the modified business data is obtained, the modified business data is fully transmitted to the server, and a business data saving request is generated based on the modified business data;

[0068] When the editing type of the business data is unmodified, the business data identifier or content distribution network CDN address is extracted, and a business data save request is generated based on the identifier or CDN address, wherein the identifier or CDN address is used to provide a basis for the server to find and save the business data.

[0069] Optionally, in response to a data saving operation triggered for a target application software in a running state, the response unit is configured to:

[0070] In response to one or any combination of a data adding operation, a data deleting operation, a data modifying operation and a data status changing operation triggered for the target application software.

[0071] A fifth aspect is a server, comprising:

[0072] A memory for storing executable instructions;

[0073] A processor is used to read and execute executable instructions stored in a memory to implement any method as described in the first aspect.

[0074] A sixth aspect is a client, comprising:

[0075] A memory for storing executable instructions;

[0076] A processor is used to read and execute executable instructions stored in a memory to implement any method as described in the second aspect.

[0077] In a seventh aspect, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor, the processor is enabled to execute any method described in the first aspect.

[0078] In an eighth aspect, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor, the processor is enabled to execute any method described in the second aspect.

[0079] In a ninth aspect, a computer program product comprises executable instructions, and when the executable instructions of the computer program product are executed by a processor, the method as described in any one of the first aspects above can be implemented.

[0080] In a tenth aspect, a computer program product comprises executable instructions, and when the executable instructions of the computer program product are executed by a processor, the method as described in any one of the second aspects above can be implemented.

[0081] In summary, in the embodiment of the present disclosure, the server receives a business data saving request sent by the client for the target application software, and further determines the business type of the business data. If the business type does not meet the preset mandatory saving rules, the server saves the business data of the target application software in an asynchronous manner and returns the first feedback information at the same time. If the business type meets the preset mandatory saving rules, the server saves the business data of the target application software in a synchronous manner, and returns the second feedback information when the saving result of the business data is a failure. In this way, the client can continue to run the target application software after receiving the first feedback information, and disable the current operation of the target application software after receiving the second feedback information. The above process realizes the classified storage of business data, that is, the business data in the target application software corresponding to the business data saving request is effectively divided, and the synchronous or asynchronous storage processing of different business types in the server is realized, and then the client is instructed to prohibit the current operation or continue to run the next operation, which can restrict the use of business data and effectively save the actual usage data of the target application software in the client, thereby ensuring the security of business data. BRIEF DESCRIPTION OF THE DRAWINGS

[0082] Figure 1 A schematic diagram of a system architecture for storing business data in an embodiment of the present application;

[0083] Figure 2This is a schematic diagram of the process of storing business data by the server in an embodiment of the present application;

[0084] Figure 3 A schematic diagram of a user clicking on a target application software in an embodiment of the present application;

[0085] Figure 4 A schematic diagram of a user sliding a target application software in an embodiment of the present application;

[0086] Figure 5 This is a schematic diagram of a user dragging a target application software in an embodiment of the present application;

[0087] Figure 6 This is a schematic diagram of the process of saving business data by the client in an embodiment of the present application;

[0088] Figure 7 This is a schematic diagram of saving business data in application scenario 1 of an embodiment of the present application;

[0089] Figure 8 This is a schematic diagram of saving business data in application scenario 2 of an embodiment of the present application;

[0090] Fig. 9 A schematic diagram of the logical architecture of a server in an embodiment of the present disclosure;

[0091] Fig.10 A schematic diagram of the logical architecture of a client in an embodiment of the present disclosure;

[0092] Fig.11 A schematic diagram of the physical architecture of a server in an embodiment of the present disclosure;

[0093] Fig.12 Schematic diagram of the physical architecture of the client in the embodiment of the present disclosure. DETAILED DESCRIPTION

[0094] In order to ensure the security of business data in the target application software, in an embodiment of the present application, after receiving the business data saving request sent by the client, the server further determines the business type of the corresponding business data. In this way, when the business type does not meet the preset mandatory saving rules, the server saves the business data of the target application software in an asynchronous manner, and uses the first feedback information to enable the client to continue running the target application software; and when the business type meets the preset mandatory saving rules, the server saves the business data of the target application software in a synchronous manner, and uses the second feedback information to enable the client to disable the current operation of the target application software, thereby restricting the use of the business data and ensuring the security of the business data.

[0095] The preferred implementation modes of the present application are described in detail below with reference to the accompanying drawings.

[0096] See also Figure 1 As shown, in the embodiment of the present disclosure, the system includes at least one client and a server. Figure 1 In the figure, client 1, client 2 and client n are used to exemplify clients running target application software. It is assumed that target application software 1 is running in client 1, target application software 2 is running in client 2, and target application software n is running in client n. Server 1, server 2 and server n are used to exemplify servers interacting with clients. Accordingly, server 1 is used to store business data in target application software 1, server 2 is used to store business data in target application software 2, and server n is used to store business data in target application software n.

[0097] During the implementation, data can be exchanged between the client 1, 2 or n and the corresponding server 1, 2 or n, and the target application software is running in the client 1, 2 or n. When a business data saving request is generated in the target application software, the client 1, 2 or n sends the business data saving request to the server 1, 2 or n, so that the server 1, 2 or n can adopt different strategies to process according to the specific type of business data.

[0098] In the embodiments of the present disclosure, the implementation of the method for saving business data is mainly divided into two types: server side and client side, which are introduced below respectively.

[0099] Server side: After receiving the business data saving request sent by the client for the target application software, determine the business type of the business data. If the business type does not comply with the preset mandatory saving rules, save the business data of the target application software asynchronously; if the business type complies with the preset mandatory saving rules, save the business data of the target application software synchronously.

[0100] Client side: In response to the data save operation triggered for the target application software in the running state, a corresponding business data save request is generated. If the first feedback information returned by the server is received, the target application software continues to run. If the second feedback information returned by the server is received, the current operation of the target application software is disabled.

[0101] The following first introduces the method of saving business data on the server side. Figure 2 As shown, in the embodiment of the present disclosure, the specific process of the server saving business data is as follows:

[0102] Step 200: The server receives a business data saving request sent by the client to the target application software, wherein the target application software runs on the client.

[0103] In actual applications, when a user performs a preset action on a target application, the client (e.g., a smartphone, tablet computer, etc.) can determine that the user has triggered a data save operation for the target application. Therefore, a business data save request can be generated based on the data save operation and sent to the server.

[0104] For example, see Figure 3 As shown, when the target application software is running on the client, a variety of business data may be generated in the process of the user logging in by clicking the input box on the target application software and entering the user name and password. If the user name and password are changed, it may involve the problem of illegal login. In this case, the client can determine that the user has triggered a data saving operation for the target application software, and generate a business data saving request based on the data saving operation and send the business data saving request to the server.

[0105] For example, see Figure 4 As shown, when the target application software is running on the client, a variety of business data may be generated in the process of the user adjusting the application progress by sliding the progress bar on the target application software. It is assumed that abnormal adjustment of the progress bar may affect the viewed work content, etc. In this case, the client can determine that the user has triggered a data saving operation for the target application software, and generate a business data saving request based on the data saving operation and send the business data saving request to the server.

[0106] For example, see Figure 5 As shown, when the target application software is running on the client, the user may generate various business data in the process of dragging the existing data on the target application software to save locally. If the existing data is a private work with user copyright, it may involve copyright infringement. In this case, the client can determine that the user has triggered a data saving operation for the target application software, and generate a business data saving request based on the data saving operation and send the business data saving request to the server.

[0107] In this way, the server can process the corresponding business data based on the received business data saving request to confirm what specific business data the target application software generates during operation and at which stages the business data is used, thereby achieving the purpose of monitoring the operation of the target application software on the client.

[0108] Step 201: Based on the received service data saving request, the server determines the service type of the service data.

[0109] Considering the different importance of different business data to users and the limited processing capacity of the server, after receiving a business data saving request, the server must first determine the business type of the business data to determine further processing strategies.

[0110] Specifically, when executing step 201, the following methods may be used but are not limited to:

[0111] Mode 1: If the business data saving request is a non-mandatory saving request, the server determines that the business type of the business data does not comply with a preset mandatory saving rule.

[0112] For example, the change of username and password is not very important information for some users who frequently change their passwords, and the corresponding business data save request can be set as a non-mandatory save request. Accordingly, the server determines that the business type of the business data does not meet the preset mandatory save rules.

[0113] For another example, when a user does not care about the application of a published copyrighted work, the corresponding business data saving request may be set as a non-mandatory saving request. Accordingly, the server determines that the business type of the business data does not comply with the preset mandatory saving rule.

[0114] In the above cases, the server determines that the business type of the business data does not comply with the preset mandatory storage rule.

[0115] Mode 2: If the business data saving request is a mandatory saving request, the server determines that the business type of the business data complies with a preset mandatory saving rule.

[0116] For example, the change of user name and password is very important to users of some access control alarm application software, and the corresponding business data saving request can be set as a must save request. Accordingly, the business type meets the preset mandatory saving rules.

[0117] For another example, operations such as data transfer in and out are crucial to users in financial management software, and the corresponding business data save request can be set as a must-save request. Accordingly, the business type complies with the preset mandatory save rules.

[0118] For another example, when a work published by a user may cause a major dispute due to copyright issues, the corresponding business data preservation request may be set as a mandatory preservation request, and accordingly, the business type complies with the preset mandatory preservation rules.

[0119] In the above cases, the server determines that the business type of the business data complies with the preset mandatory storage rule.

[0120] Corresponding to the above-mentioned method 1, the server saves the business data of the target application software in an asynchronous manner.

[0121] Step 202: If the service type does not conform to the preset mandatory saving rule, the server saves the service data of the target application software in an asynchronous manner and returns first feedback information to the client, where the first feedback information is used to instruct the client to continue running the target application software.

[0122] During the implementation process, when it is determined that the business type does not comply with the preset mandatory preservation rules, the server returns the first feedback information to the client after receiving the business data preservation request, that is, the server immediately returns success to the client after receiving the business data preservation request. It should be noted that the success here only means that the business data preservation request has been successfully received, and does not indicate the server's processing of the business data corresponding to the business data preservation request.

[0123] Here, the purpose of the server returning success to the client is to enable the client to continue running the target application software, that is, not to affect the user's experience of using the target application software. At the same time, the server converts the processing of the business data corresponding to the business data save request into asynchronous processing.

[0124] After converting the processing of the business data corresponding to the above business data saving request into asynchronous processing, the server saves the business data of the target application software into the database. The specific implementation steps are as follows:

[0125] Step a: The server sends the business data of the target application software to the distributed publish-subscribe messaging system or the internal thread pool.

[0126] Here, considering that the continued operation of the target application software in the client needs to interact with the server, in order to minimize the impact on the user's experience of using the target application software, the process of server asynchronous processing is divided into two cases for explanation.

[0127] Specifically include:

[0128] Case (1): The server sends the business data to the distributed publish-subscribe messaging system (Kafka), which processes the business data asynchronously. For example, Kafka extracts the business data and extracts the business data identification information ID, usage phase information, and usage data. Kafka is a high-throughput distributed publish-subscribe messaging system that can ensure speed and stability when processing business data.

[0129] Case (2): The server sends the business data to the internal thread pool, which processes the business data asynchronously. For example, the internal thread pool extracts the business data and extracts the business data identification information ID, usage phase information, and usage data of the business data. The internal thread pool can process the business data in parallel by setting up multiple threads, and the processing of these threads is performed in the background, so it will not affect the interaction between the server and the target application software in the client.

[0130] Step b: The server saves the business data of the target application software into the database through the distributed publish-subscribe message system or the internal thread pool.

[0131] During the implementation process, the server processes the business data asynchronously through the distributed publish-subscribe message system or the internal thread pool. For example, the internal thread pool extracts the business data and extracts the business data identification information ID, usage phase information, and usage data of the business data. The server continues to save the business data of the target application software into the database to save the business data.

[0132] Corresponding to the above-mentioned method 2, the server saves the business data of the target application software in a synchronous manner.

[0133] Step 203: If the service type meets the preset mandatory saving rule, the server saves the service data of the target application software in a synchronous manner, and returns second feedback information to the client when the saving result of the service data is failure, and the second feedback information is used to instruct the client to disable the current operation of the target application software.

[0134] During the implementation process, if it is determined that the business type meets the preset mandatory preservation rules, the server will save the business data of the target application software to the database after receiving the business data preservation request. That is, the server will immediately save the business data of the target application software after receiving the business data preservation request, and the server will synchronously save the business data to the database.

[0135] Meanwhile, the operation of the target application software in the client includes the suspension of the interaction with the server, and the target application software in the client can continue to operate only after the server returns the saved result.

[0136] When performing synchronous saving, two situations are described according to the saving result of the server.

[0137] Specifically include:

[0138] Case 1: If the saving result of the server is failure, that is, the server fails to successfully save the business data into the database, the server returns second feedback information to the client. Here, the form and specific content of the second feedback information are not limited.

[0139] During implementation, the target application software on the client can disable the current operation after receiving the second feedback information. It should be noted that the second feedback information is received on the client after the client sends a request to save the service data to the target application software.

[0140] For example, when the range of changing the deposit amount in the target application software, the financial management software, exceeds the preset range, the corresponding business data fails to be saved on the server, and the server throws an exception to the financial management software on the client. When the financial management software receives the exception information, it cannot change the deposit amount, and further saving is impossible.

[0141] Case 2: If the saving result of the server is successful, that is, the server successfully saves the business data into the database, the server returns second feedback information to the client. Here, the form and specific content of the second feedback information are not limited.

[0142] During the implementation process, the target application software on the client can continue to run after receiving the second feedback information. It should be noted that the second feedback information is received on the client after the client sends the business data saving request to the target application software, and the target application software continues to run, that is, the target application software in the client continues to run the next step generated by the business data saving request.

[0143] For example, when the range of changing the deposit amount in the target application software, the financial management software, does not exceed the preset range, after the corresponding business data is successfully saved on the server, the server will notify the target application software on the client. When the target application software receives the notification, it will synchronously save the user's change information on the deposit amount and proceed to the next step.

[0144] Furthermore, after the server sends the business data of the target application software to the database, a save operation is performed in the database. The steps of saving the business data in the database are described below.

[0145] Specifically include:

[0146] Step (1): The server creates at least three new fields in the database.

[0147] During specific implementation, the above-mentioned business data at least includes business data identification information ID, usage stage information and usage data.

[0148] Usually, the business data corresponding to the business data saving request is a complete business data, in which the ID, usage phase information, usage data and other information data are recorded. Here, the ID, usage phase information, usage data and other information data are collectively referred to as the entire content of the business data; obviously, the above-mentioned ID, usage phase information and usage data are different components of the same business data. Since the usage phase information and usage data may change after the above-mentioned business data saving request is processed, the server usually also records the usage phase information and usage data together.

[0149] For example, when the target application software is access control alarm software, assuming that there is an operation to change the password in the software, the business data at this time includes at least business data identification information ID (such as "Li San"), usage stage information (such as "password change stage") and usage data (such as, the password before change is "xxx", and the password after change is "yyy").

[0150] Accordingly, the server needs to create at least three new fields in the database to store the above business data (i.e., "Li San", "Change Password Phase", and "xxx" or "yyy"). It should be noted that when the business data transmitted by the client to the server is full data, in order to ensure the integrity of data storage, more fields need to be created in the database to store the business data.

[0151] Step (2): The server saves the business data identification information ID, the usage phase information and the usage data in at least three created fields respectively; wherein the usage data is saved in json format.

[0152] In order to facilitate subsequent searches, the server will save all business data identification information IDs in one field. When searching, you can directly search for the ID name in the field. The storage of usage stage information and usage data is also classified and saved.

[0153] In addition, the server saves the usage data in JSON format, which is a text format that is completely independent of the language. It is easy for people to read and write, and it is also easy for machines to parse and generate. When a set of values ​​needs to be represented, JSON can not only improve readability, but also reduce complexity.

[0154] The following describes the client side, that is, the client executes the method of saving business data. Figure 6 As shown, in the embodiment of the present disclosure, the specific process of the client saving business data is as follows:

[0155] Step 600: The client generates a corresponding business data saving request in response to a data saving operation triggered for a target application software in a running state.

[0156] During the implementation, when the target application software is in the running state, that is, when the target application software is running on the client (for example, a smart phone, a tablet computer, etc.), the user operates the target application software in the running state, thereby triggering a data saving operation. When the data saving operation is triggered, a corresponding business data saving request is generated.

[0157] For example, when a user performs a preset click action in a target application and enters a user name and password in the input box on the target application to log in, various business data may be generated. If the user name and password are set by the user to be prohibited from being changed, the client can determine that the user has triggered a data save operation for the target application.

[0158] For another example, when the target application software is running on the client, the user may generate various business data in the process of adjusting the application progress by sliding the progress bar on the target application software. If the abnormal adjustment of the progress bar may affect the viewed work content, etc. If the work content is set to be confidential by the user, the client can determine that the user has triggered a data saving operation for the target application software.

[0159] It should be noted here that the user can preset the triggering conditions of the data saving operation according to his own needs during the process of running the target application software on the client, which will not be elaborated here.

[0160] In specific implementation, the client responds to a data save operation triggered on a target application software in a running state, and the client monitors whether changes have occurred in the data in the target application software that can trigger a data save operation, that is, the client responds to one or any combination of data addition operations, data deletion operations, data modification operations, and data status change operations triggered on the target application software.

[0161] For example, the number of digits of the password in the target application software can be increased.

[0162] Another example is the deletion of the author's name of a published work in the target application software.

[0163] Another example is the modification of user data in the target application software.

[0164] For another example, the data status of the access rights to the works in the target application software is changed.

[0165] Based on the data saving operation triggered on the target application software, the client determines the editing type of the business data in the target application software, that is, whether the above data addition operation, data deletion operation, data modification operation and data status change operation have caused the business data in the target application software to be modified.

[0166] Specifically include:

[0167] Case 1): When the edit type of the business data is modification, that is, when the target application software generates modified business data, the client obtains the modified business data, transmits the modified business data in full to the server, and generates a business data save request based on the modified business data. It should be noted that in this case, the corresponding actual use data in the target application software of the client is the modified business data.

[0168] Case 2): When the edit type of the business data is unmodified, that is, the target application software does not generate the modified business data, it should be noted that in this case, the corresponding actual usage data in the target application software of the client is the original business data. Based on the original business data, the client extracts the business data identifier or content delivery network (Content Delivery Network, cdn) address, and the above business data identifier is usually the business data id.

[0169] Furthermore, the client generates a business data saving request based on the identifier or CDN address.

[0170] Since the business data is stored in both the local client and the server, as long as the client does not modify the business data, the server can obtain all the contents of the business data on the server side through the business data identifier or CDN address. In this way, the process of transmitting business data from the client to the server can be omitted, thereby improving the processing efficiency of business data; and, the server saves all the contents of the found business data again according to the business data saving request, and the location of the saved data is different from the original storage location, that is, the server unifies the business data corresponding to the business data saving request and saves them centrally. The business data corresponding to the business data saving request are stored in the existing storage location (for example, the newly created database a). Compared with the original storage location in the target application software, the business data stored separately here is more centralized to facilitate subsequent management and reference.

[0171] On the other hand, if the client modifies the business data based on the user's instruction, the client will transmit the modified business data to the server, so that the server can save the modified business data according to the business data saving request.

[0172] Step 601: After the client generates a business data save request, the client sends the business data save request to the server, so that the server performs the following operations: receives the business data save request, and based on the business data save request, determines the business type of the business data; if the business type does not comply with the preset mandatory save rule, saves the business data of the target application software in an asynchronous manner and generates a first feedback message; if the business type complies with the preset mandatory save rule, saves the business data of the target application software in a synchronous manner, and generates a second feedback message when the result of saving the business data is a failure.

[0173] Specifically, the process in which the server saves the business data in an asynchronous or synchronous manner after receiving the business data saving request is the same as step 202 and step 203, which will not be elaborated here.

[0174] The server generates first feedback information in the process of saving business data in an asynchronous manner; and the server generates second feedback information in the process of saving business data in a synchronous manner; and the first feedback information and the second feedback information are sent by the server to the client to further indicate the next operation of the target application software on the client.

[0175] Step 602: The client determines whether the received feedback information is the first feedback information or the second feedback information. If it is the first feedback information, execute step 603; if it is the second feedback information, execute step 604.

[0176] Since the first feedback information and the second feedback information are the results returned to the client by the server after adopting different storage forms for different types of business data, and the further operations of the client corresponding to different storage forms will be different, the client must first determine whether the received feedback information is the first feedback information or the second feedback information.

[0177] Step 603: If the first feedback information returned by the server is received, the client continues to run the target application software.

[0178] During the implementation, after the client receives the first feedback information returned by the server, the client continues to run the target application software at the current progress of the target application software. That is, after generating the data saving operation, the target application software continues to respond to other operations of the user.

[0179] Step 604: If the second feedback information returned by the server is received, the client disables the current operation of the target application software.

[0180] During the implementation, when the client receives the second feedback information returned by the server, the client prohibits the target application software from continuing to run under the current progress of the target application software, that is, the current operation of the target application software is disabled. After generating the data saving operation, the target application software cannot continue to respond to the user's next operation.

[0181] The above embodiment is further described in detail below using several specific application scenarios.

[0182] Application scenario 1: A user modifies the name in personal information in a running target application software (for example, a social software).

[0183] See also Figure 7 As shown, in the personal information interface of the target application software presented by the client, the user clicks the "Modify" button and instructs to change the name from "Zhang San" to "Li Si". Then, the client responds to the data modification operation triggered on the target application software, generates a corresponding business data save request x based on the business data x of changing "Zhang San" to "Li Si", and sends the business data save request x to the server.

[0184] After receiving the business data saving request x, the server determines, based on the business data saving request x and the user requirement field included in the business data x, that the business type of the business data x does not comply with the preset mandatory saving rule.

[0185] Among them, when the server receives the business data saving request x, it does not need to wait for the saving result of the business data x, that is, in the process of processing the business data x, it can immediately return the notification message x (that is, the first feedback information) to the client, and after receiving the notification message x, the client will continue to run the target application software, allowing the user to continue with the next step after modifying the name; accordingly, the server will save the information contained in the business data x: the name "Li Si" to the database.

[0186] The above business data saving process is an asynchronous saving method, that is, the client first sends the modified name "Li Si" to the server, and then the server saves the name "Li Si" contained in the business data x. It can be seen that in the case of asynchronous saving of business data, the continued interaction between the client and the server is not affected by the saving operation of the business data.

[0187] Application scenario 2: A user modifies the fund amount in a running target application software (for example, a financial management software).

[0188] See also Figure 8As shown, in the fund number interface of the target application software presented by the client, the user clicks the "Modify" button and instructs to change the fund number from "100000" to "10000". Then, the client responds to the data modification operation triggered on the target application software, generates a corresponding business data save request y based on the business data y that changes "100000" to "10000", and sends the business data save request y to the server.

[0189] After receiving the business data saving request y, the server determines, based on the business data saving request y and according to the fund amount field included in the business data y, whether the business type of the business data y complies with the preset mandatory saving rule.

[0190] The above-mentioned business data saving process is a synchronous saving method, that is, when the server receives the business data saving request y, it needs to wait for the saving result of the business data y, that is, in the process of processing the business data y, the server will save the information contained in the business data y: the fund number "100000" to the database; and, when the saving result of the above-mentioned business data y is failure, the server returns a notification message y (that is, the second feedback information) to the client to prohibit the client from continuing to run the current operation; for example, when the user clicks the "Save" button after modifying the fund number, the client will refuse to execute the save operation.

[0191] It can be seen that when the synchronous saving method is used to save business data, the continued interaction between the client and the server will be affected by the saving result of the business data.

[0192] It should be noted that when the synchronous saving method is adopted, after refusing to execute the saving operation corresponding to the "Save" button, the client can still continue to execute other operations except the data modification operation in the target application software according to the user's instructions.

[0193] Based on the same inventive concept, refer to Fig. 9 As shown, an embodiment of the present application provides a device for storing business data, which is applied to a server and includes:

[0194] A receiving unit 910 is used to receive a service data saving request sent by a client to a target application software, wherein the target application software runs on the client;

[0195] A determination unit 920, configured to determine a service type of the service data based on the service data saving request;

[0196] The saving unit 930 is used to save the business data of the target application software in an asynchronous manner if the business type does not meet the preset mandatory saving rule, and return first feedback information to the client, where the first feedback information is used to instruct the client to continue running the target application software;

[0197] And, if the business type meets the preset mandatory saving rules, the business data of the target application software is saved in a synchronous manner, and when the saving result of the business data is failure, the second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software.

[0198] Optionally, based on the service data saving request, determining the service type of the service data, the determining unit 920 is configured to:

[0199] If the business data preservation request is a non-mandatory preservation request, determining that the business type of the business data does not comply with a preset mandatory preservation rule;

[0200] If the business data preservation request is a mandatory preservation request, it is determined that the business type of the business data complies with a preset mandatory preservation rule.

[0201] Optionally, if the service type does not meet the preset mandatory saving rule, the service data of the target application software is saved in an asynchronous manner, and first feedback information is returned to the client, the first feedback information is used to instruct the client to continue running the target application software, and the saving unit 930 is used to:

[0202] If the service type does not conform to the preset mandatory preservation rule, returning first feedback information to the client after receiving the service data preservation request, so that the client continues to run the target application software;

[0203] Save the business data of the target application software into the database.

[0204] Optionally, the business data of the target application software is saved in a database, and the saving unit 930 is used to:

[0205] The business data of the target application software is sent to the distributed publish-subscribe message system or the internal thread pool, and the business data of the target application software is saved in the database through the distributed publish-subscribe message system or the internal thread pool.

[0206] Optionally, if the service type meets the preset mandatory saving rule, the service data of the target application software is saved in a synchronous manner, and when the saving result of the service data is a failure, second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software. The saving unit 930 is used to:

[0207] If the business type meets the preset mandatory preservation rules, the business data of the target application software is saved in the database after receiving the business data preservation request;

[0208] If the saving result is a failure, second feedback information is returned to the client, and the second feedback information is used to indicate that the target application software has received abnormal information and disabled the current operation.

[0209] Optionally, the business data at least includes business data identification information ID, usage phase information and usage data; the business data of the target application software is saved in the database, and the saving unit 930 is used to:

[0210] Create at least three new fields in the database;

[0211] In the at least three created fields, the ID, the usage stage information and the usage data are saved respectively; among them, the usage data is saved in the json format.

[0212] Based on the same inventive concept, refer to Fig.10 As shown, an embodiment of the present application provides a device for storing business data, which is applied to a client and includes:

[0213] A response unit 1010, configured to generate a corresponding business data save request in response to a data save operation triggered for a target application software in a running state;

[0214] The sending unit 1020 is used to send the business data saving request to the server, so that the server performs the following operations: receiving the business data saving request, and determining the business type of the business data based on the business data saving request, if the business type does not meet the preset mandatory saving rule, saving the business data of the target application software in an asynchronous manner and generating first feedback information, if the business type meets the preset mandatory saving rule, saving the business data of the target application software in a synchronous manner, and generating second feedback information when the saving result of the business data is failure;

[0215] The processing unit 1030 is configured to continue running the target application software if the first feedback information returned by the server is received;

[0216] And, if the second feedback information returned by the server is received, the current operation of the target application software is disabled.

[0217] Optionally, in response to a data saving operation triggered for a target application software in a running state, a corresponding service data saving request is generated, and the response unit 1010 is used to:

[0218] In response to a data saving operation triggered on a target application software in a running state, determining an editing type of business data in the target application software;

[0219] When the editing type of the business data is modification, the modified business data is obtained, the modified business data is fully transmitted to the server, and a business data saving request is generated based on the modified business data;

[0220] When the editing type of the business data is unmodified, the business data identifier or content distribution network CDN address is extracted, and a business data save request is generated based on the identifier or CDN address, wherein the identifier or CDN address is used to provide a basis for the server to find and save the business data.

[0221] Optionally, in response to a data saving operation triggered for a target application software in a running state, the response unit 1010 is configured to:

[0222] In response to one or any combination of a data adding operation, a data deleting operation, a data modifying operation and a data status changing operation triggered for the target application software.

[0223] Based on the same inventive concept, refer to Fig.11 As shown, an embodiment of the present disclosure provides a server 1100, including: a memory 1101, used to store executable instructions; a processor 1102, used to read and execute the executable instructions stored in the memory, and execute any one of the methods of the first aspect above.

[0224] The processor 1102 generally controls the overall operation of the server 1100, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The memory 1101 is configured to store various types of data to support operations on the server 1100. Examples of such data include instructions for any application or method operating on the server 1100, contact data, phone book data, messages, pictures, videos, etc. The memory 1101 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0225] Based on the same inventive concept, refer to Fig.12 As shown, an embodiment of the present disclosure provides a client 1200. For example, the client 1200 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0226] Reference Fig.12The client 1200 may include one or more of the following components: a processing component 1202 , a memory 1204 , a power component 1206 , a multimedia component 12012 , an audio component 1212 , an input / output (I / O) interface 1212 , a sensor component 1214 , and a communication component 1216 .

[0227] The processing component 1202 generally controls the overall operation of the client 1200, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 1202 may include one or more processors 1220 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 1202 may include one or more modules to facilitate the interaction between the processing component 1202 and other components. For example, the processing component 1202 may include a multimedia module to facilitate the interaction between the multimedia component 12012 and the processing component 1202.

[0228] The memory 1209 is configured to store various types of data to support operations on the client 1200. Examples of such data include instructions for any application or method operating on the client 1200, contact data, phone book data, messages, pictures, videos, etc. The memory 1204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0229] The power supply component 1206 provides power to the various components of the client 1200. The power supply component 1206 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the client 1200.

[0230] The multimedia component 12012 includes a screen that provides an output interface between the client 1200 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 12012 includes a front camera and / or a rear camera. When the client 1200 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0231] The audio component 1212 is configured to output and / or input audio signals. For example, the audio component 1212 includes a microphone (MIC), and when the client 1200 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 1204 or sent via the communication component 1216. In some embodiments, the audio component 1212 also includes a speaker for outputting audio signals.

[0232] I / O interface 1212 provides an interface between processing component 1202 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0233] The sensor assembly 1214 includes one or more sensors for providing various aspects of status assessment for the client 1200. For example, the sensor assembly 1214 can detect the open / closed state of the client 1200, the relative positioning of components, such as the display and keypad of the client 1200, the sensor assembly 1214 can also detect the position change of the client 1200 or a component of the client 1200, the presence or absence of user contact with the client 1200, the orientation or acceleration / deceleration of the client 1200, and the temperature change of the client 1200. The sensor assembly 1214 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 1214 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1214 can also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0234] The communication component 1216 is configured to facilitate wired or wireless communication between the client 1200 and other devices. The client 1200 can access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 1216 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1216 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0235] In an exemplary embodiment, the client 1200 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform any of the methods of the second aspect described above.

[0236] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium. When instructions in the storage medium are executed by a processor, the processor is enabled to execute the method described in any one of the first aspects above.

[0237] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium. When the instructions in the storage medium are executed by a processor, the processor is enabled to execute the method described in any one of the second aspects above.

[0238] Based on the same inventive concept, an embodiment of the present application provides a computer program product, comprising executable instructions. When the executable instructions of the computer program product are executed by a processor, the method described in any one of the first aspects above can be implemented.

[0239] Based on the same inventive concept, an embodiment of the present application provides a computer program product, comprising executable instructions. When the executable instructions of the computer program product are executed by a processor, the method described in any one of the second aspects above can be implemented.

[0240] To summarize, in an embodiment of the present application, the server receives a business data saving request sent by the client to the target application software, and further determines the business type of the business data. If the business type does not meet the preset mandatory saving rules, the server saves the business data of the target application software in an asynchronous manner and returns a first feedback message at the same time. If the business type meets the preset mandatory saving rules, the server saves the business data of the target application software in a synchronous manner, and returns a second feedback message when the saving result of the business data is a failure. In this way, the client can continue to run the target application software after receiving the first feedback information, and disable the current operation of the target application software after receiving the second feedback information. The above-mentioned triggering of the user in the target application software realizes the classified storage of the business data, that is, the business data in the target application software corresponding to the business data saving request is effectively divided, and the synchronous or asynchronous storage processing of different business types in the server is realized, thereby instructing the client to prohibit the current operation or continue to run, effectively saving the actual usage data of the target application software in the client, thereby ensuring the security of the business data.

[0241] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program product systems. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product system implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0242] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program product systems according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0243] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0244] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0245] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for storing business data, applied to a server, It is characterized in that The method includes: Receiving a service data saving request sent by a client for a target application software, wherein the target application software runs on the client; Determining a business type of the business data based on the business data saving request; If the service type does not conform to the preset mandatory saving rule, the service data of the target application software is saved in an asynchronous manner, and first feedback information is returned to the client, where the first feedback information is used to instruct the client to continue running the target application software; If the business type meets the preset mandatory saving rules, the business data of the target application software is saved in a synchronous manner. During the process of saving the business data, the interaction with the target application software in the client is suspended. When the saving result of the business data is failure, second feedback information is returned to the client. The second feedback information is used to instruct the client to disable the current operation of the target application software.

2. The method according to claim 1, It is characterized in that The determining the business type of the business data based on the business data saving request includes: If the business data saving request is a non-mandatory saving request, determining that the business type of the business data does not comply with a preset mandatory saving rule; If the business data saving request is a mandatory saving request, it is determined that the business type of the business data complies with a preset mandatory saving rule.

3. The method according to claim 1, It is characterized in that If the service type does not conform to the preset mandatory saving rule, the service data of the target application software is saved in an asynchronous manner, and first feedback information is returned to the client, where the first feedback information is used to instruct the client to continue running the target application software, including: If the service type does not conform to the preset mandatory preservation rule, returning the first feedback information to the client after receiving the service data preservation request, wherein the first feedback information is used to instruct the client to continue running the target application software; The business data of the target application software is saved in a database.

4. The method according to claim 3, It is characterized in that Saving the business data of the target application software into a database includes: The business data of the target application software is sent to a distributed publish-subscribe message system or an internal thread pool, and the business data of the target application software is saved in a database through the distributed publish-subscribe message system or the internal thread pool.

5. The method according to claim 1, It is characterized in that If the business type meets the preset mandatory saving rule, the business data of the target application software is saved in a synchronous manner, and when the saving result of the business data is failure, second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software, including: If the business type meets the preset mandatory saving rule, then after receiving the business data saving request, the business data of the target application software is saved in the database; If the saving result is a failure, second feedback information is returned to the client, where the second feedback information is used to indicate that the target application software has received abnormal information and disabled the current operation.

6. The method according to claim 3 or 5, It is characterized in that The business data at least includes business data identification information ID, usage phase information and usage data; The step of saving the business data of the target application software into a database comprises: Create at least three new fields in the database; In the at least three created fields, the ID, the usage stage information and the usage data are saved respectively; wherein the usage data is saved in a json format.

7. A method for storing business data, applied to a client, It is characterized in that The method includes: In response to a data saving operation triggered for a target application software in a running state, generating a corresponding business data saving request; Sending the business data saving request to a server so that the server performs the following operations: receiving the business data saving request, and determining the business type of the business data based on the business data saving request; if the business type does not conform to a preset mandatory saving rule, saving the business data of the target application software in an asynchronous manner and generating first feedback information; if the business type conforms to the preset mandatory saving rule, saving the business data of the target application software in a synchronous manner, suspending the interaction with the target application software in the client during the process of saving the business data, and generating second feedback information when the saving result of the business data is failure; If the first feedback information returned by the server is received, continue to run the target application software; If the second feedback information returned by the server is received, the current operation of the target application software is disabled.

8. The method according to claim 7, It is characterized in that In response to a data saving operation triggered for a target application software in a running state, a corresponding business data saving request is generated, including: In response to a data saving operation triggered on a target application software in a running state, determining an editing type of business data in the target application software; When the editing type of the business data is modification, obtaining the modified business data, transmitting the modified business data in full to the server, and generating the business data saving request based on the modified business data; When the editing type of the business data is unmodified, the identifier or content distribution network (CDN) address of the business data is extracted, and the business data save request is generated based on the identifier or the CDN address, wherein the identifier or the CDN address is used to provide a basis for the server to find and save the business data.

9. The method according to claim 8, It is characterized in that In response to a data saving operation triggered for a target application software in a running state, the method includes: In response to one or any combination of a data adding operation, a data deleting operation, a data modifying operation and a data status changing operation triggered for the target application software.

10. A device for storing business data, applied to a server, It is characterized in that include: A receiving unit, configured to receive a service data saving request sent by a client to a target application software, wherein the target application software runs on the client; A determination unit, configured to determine a service type of the service data based on the service data saving request; a saving unit, configured to save the business data of the target application software in an asynchronous manner if the business type does not conform to a preset mandatory saving rule, and return first feedback information to the client, wherein the first feedback information is used to instruct the client to continue running the target application software; Furthermore, if the business type meets the preset mandatory saving rules, the business data of the target application software is saved in a synchronous manner, and the interaction with the target application software in the client is suspended during the process of saving the business data. When the saving result of the business data is failure, second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software.

11. The device for storing business data according to claim 10, It is characterized in that The determining unit determines the service type of the service data based on the service data saving request, wherein the determining unit is configured to: If the business data saving request is a non-mandatory saving request, determining that the business type of the business data does not comply with a preset mandatory saving rule; If the business data saving request is a mandatory saving request, it is determined that the business type of the business data complies with a preset mandatory saving rule.

12. The device for storing business data according to claim 10, It is characterized in that If the service type does not meet the preset mandatory saving rule, the service data of the target application software is saved in an asynchronous manner, and first feedback information is returned to the client, wherein the first feedback information is used to instruct the client to continue running the target application software. The saving unit is used to: If the service type does not conform to the preset mandatory preservation rule, returning the first feedback information to the client after receiving the service data preservation request, wherein the first feedback information is used to instruct the client to continue running the target application software; The business data of the target application software is saved in a database.

13. The device for storing business data according to claim 12, It is characterized in that The business data of the target application software is saved in a database, wherein the saving unit is used to: The business data of the target application software is sent to a distributed publish-subscribe message system or an internal thread pool, and the business data of the target application software is saved in a database through the distributed publish-subscribe message system or the internal thread pool.

14. The device for storing business data according to claim 10, It is characterized in that If the business type meets the preset mandatory saving rule, the business data of the target application software is saved in a synchronous manner, and when the saving result of the business data is failure, second feedback information is returned to the client, and the second feedback information is used to instruct the client to disable the current operation of the target application software. The saving unit is used to: If the business type meets the preset mandatory saving rule, then after receiving the business data saving request, the business data of the target application software is saved in the database; If the saving result is a failure, second feedback information is returned to the client, where the second feedback information is used to indicate that the target application software has received abnormal information and disabled the current operation.

15. The device for storing business data according to claim 12 or 14, It is characterized in that The business data at least includes business data identification information ID, usage phase information and usage data; the business data of the target application software is saved in a database, and the saving unit is used to: Create at least three new fields in the database; In the at least three created fields, the ID, the usage stage information and the usage data are saved respectively; wherein the usage data is saved in a json format.

16. A device for storing business data, applied to a client, It is characterized in that include: A response unit, configured to generate a corresponding business data save request in response to a data save operation triggered for a target application software in a running state; A sending unit, configured to send the business data saving request to a server, so that the server performs the following operations: receiving the business data saving request, and determining the business type of the business data based on the business data saving request, if the business type does not conform to a preset mandatory saving rule, saving the business data of the target application software in an asynchronous manner and generating first feedback information, if the business type conforms to the preset mandatory saving rule, saving the business data of the target application software in a synchronous manner, suspending the interaction with the target application software in the client during the process of saving the business data, and generating second feedback information when the saving result of the business data is failure; a processing unit, configured to continue running the target application software if the first feedback information returned by the server is received; And, if the second feedback information returned by the server is received, the current operation of the target application software is disabled.

17. The device for storing business data according to claim 16, It is characterized in that In response to a data saving operation triggered for a target application software in a running state, a corresponding service data saving request is generated, and the response unit is used to: In response to a data saving operation triggered on a target application software in a running state, determining an editing type of business data in the target application software; When the editing type of the business data is modification, obtaining the modified business data, transmitting the modified business data in full to the server, and generating the business data saving request based on the modified business data; When the editing type of the business data is unmodified, the identifier or content distribution network (CDN) address of the business data is extracted, and the business data save request is generated based on the identifier or the CDN address, wherein the identifier or the CDN address is used to provide a basis for the server to find and save the business data.

18. The device for storing business data according to claim 17, It is characterized in that In response to a data saving operation triggered for a target application software in a running state, the response unit is used to: In response to one or any combination of a data adding operation, a data deleting operation, a data modifying operation and a data status changing operation triggered for the target application software.

19. A server, It is characterized in that include: A memory for storing executable instructions; A processor, configured to read and execute the executable instructions stored in the memory to implement the method according to any one of claims 1 to 6.

20. A client, It is characterized in that include: A memory for storing executable instructions; A processor, configured to read and execute the executable instructions stored in the memory to implement the method according to any one of claims 7 to 9.

21. A computer-readable storage medium, It is characterized in that When the instructions in the storage medium are executed by a processor, the processor is enabled to execute the method according to any one of claims 1 to 6.

22. A computer-readable storage medium, It is characterized in that When the instructions in the storage medium are executed by a processor, the processor is enabled to execute the method as described in any one of claims 7 to 9.

23. A computer program product, It is characterized in that The computer program product comprises executable instructions. When the executable instructions of the computer program product are executed by a processor, the method according to any one of claims 1 to 6 can be implemented.

24. A computer program product, It is characterized in that The computer program product comprises executable instructions. When the executable instructions of the computer program product are executed by a processor, the method according to any one of claims 7 to 9 can be implemented.