Data management method, device, electronic device and storage medium
By automatically managing the operating conditions and updating conditions in the client, and adaptively adjusting the operation information of the target data to allow the running client, the problem of detecting abnormalities after the release of new functions in the existing technology is solved, and the problem of low reliability is low. Achieve efficient and reliable data management.
Patent Information
- Application Number
- CN202111241484.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-10-25
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-10-25
AI Technical Summary
After the release of new client functions, the existing technology has problems such as low reliability and a lot of manpower through manual detection, and it is impossible to detect functional abnormalities in time.
Through automatic management of running conditions and update conditions in the client, the operation information of the target data is used to determine whether to update the operating conditions. Adaptive adjustment allows the client running the target data without manual intervention, improving the reliability and efficiency of data management .
It realizes automated data management, reduces manual intervention, improves the reliability and efficiency of data management, and can timely adjust the operating range of target data to ensure data stability and controllability.
Smart Images

Figure CN113900692B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology, and in particular to a data management method, device, electronic device and storage medium. Background Art
[0002] When a new feature of a client is released, it is first released to a portion of users to test the new feature so that timely adjustments can be made if there are any problems with the new feature.
[0003] In the related art, after releasing a new function of a client to a part of users, a tester will test the released new function to determine whether the new function of the client has any abnormality. However, the above method consumes a lot of manpower and may fail to detect the abnormality of the new function in time, so the reliability is relatively low. Summary of the invention
[0004] The present disclosure provides a data management method, device, electronic device and storage medium, which can improve the reliability of data management.
[0005] According to one aspect of an embodiment of the present disclosure, a data management method is provided, the data management method comprising:
[0006] Sending target data to at least one client that meets an operating condition, wherein the operating condition is a condition that needs to be met by the client to allow the target data to be run, the target data is used to implement a newly added function in the client, and the at least one client is used to run the target data;
[0007] Determine operation information of the target data, where the operation information indicates operation status of the target data in the at least one client;
[0008] In the case where the operating information meets the update condition, the operating condition is updated to obtain the updated operating condition, where the update condition is a condition that needs to be satisfied by the operating information to trigger the update of the operating condition.
[0009] In the disclosed embodiment, the running conditions are used to control which clients are allowed to run the target data, and the update conditions are used to control whether the running conditions are updated. After the target data is sent to the client, the running information of the target data in the client is automatically obtained, and whether the running conditions need to be updated is determined based on whether the running information meets the update conditions. In this way, the clients allowed to run the target data are adaptively adjusted based on the running status of the target data, without consuming manpower, and the reliability of managing the target data can be improved.
[0010] In some embodiments, sending the target data to at least one client meeting the operating condition includes:
[0011] In response to a first client's request for running the target data, acquiring the running condition, the first client being any client;
[0012] When the first client satisfies the operating condition, the target data is sent to the first client.
[0013] In the disclosed embodiment, the client actively sends an operation request to the electronic device to request the operation target data, so that the client has the initiative to operate the target data, which is conducive to improving the flexibility and control ability of the client.
[0014] In some embodiments, in response to the first client's request for executing the target data, obtaining the executing condition includes:
[0015] In response to the operation request, obtaining a target data identifier carried in the operation request, wherein the target data identifier indicates the target data;
[0016] The operating condition corresponding to the target data identifier is queried.
[0017] In the disclosed embodiment, the corresponding operating condition is queried through the target data identifier, and the target data identifier is equivalent to the index of the operating condition, which is conducive to improving the speed of obtaining the operating condition, thereby improving the query efficiency of the electronic device.
[0018] In some embodiments, the running condition includes first attribute information, the first attribute information indicates attribute information of a client that is allowed to run the target data, and when the first client satisfies the running condition, sending the target data to the first client includes:
[0019] Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client;
[0020] In a case where the attribute information belongs to the first attribute information, the target data is sent to the first client.
[0021] In an embodiment of the present disclosure, a method for controlling the running conditions of target data based on attribute information is provided. If the attribute information of the client belongs to the first attribute information, the client is allowed to run the target data. If the attribute information of the client does not belong to the first attribute information, the client is not allowed to run the target data. Therefore, by changing the first attribute information, it is possible to adjust which clients are allowed to run the target data and which clients are not allowed to run the target data, thereby improving the flexibility of adjusting the clients allowed to run the target data.
[0022] In some embodiments, when the attribute information belongs to the first attribute information, sending the target data to the first client includes at least one of the following:
[0023] The attribute information includes the device information, the first attribute information includes first device information, and when the device information matches the first device information, the target data is sent to the first client;
[0024] The attribute information includes the state information, the first attribute information includes first state information, the first state information indicates a login state, and when the state information is the first state information, the target data is sent to the first client;
[0025] The attribute information includes a user account, the first attribute information includes a first user account, and when the user account belongs to the first user account, the target data is sent to the first client.
[0026] In the embodiment of the present disclosure, three methods are provided in which the first attribute information is the first device information, the first status information and the first user account, so as to limit the clients allowed to run the target data in terms of the device, the login status and the user account, thereby improving the diversity of the running conditions and further improving the flexibility of adjusting the clients allowed to run the target data.
[0027] In some embodiments, the running condition includes second attribute information, the second attribute information indicates attribute information of a client that is not allowed to run the target data, and when the first client satisfies the running condition, sending the target data to the first client includes:
[0028] Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client;
[0029] In a case where the attribute information does not belong to the second attribute information, the target data is sent to the first client.
[0030] In an embodiment of the present disclosure, a method for controlling the running conditions of target data based on second attribute information is provided, and the second attribute information is equivalent to a "blacklist". If the attribute information of the client does not belong to the second attribute information, the client is allowed to run the target data. If the attribute information of the client belongs to the second attribute information, the client is not allowed to run the target data. Therefore, by changing the second attribute information, it is possible to adjust which clients are allowed to run the target data and which clients are not allowed to run the target data, thereby improving the flexibility of adjusting the clients allowed to run the target data.
[0031] In some embodiments, when the attribute information does not belong to the second attribute information, sending the target data to the first client includes at least one of the following:
[0032] The attribute information includes the device information, the second attribute information includes second device information, and when the device information does not match the second device information, sending the target data to the first client;
[0033] The attribute information includes the state information, the second attribute information includes second state information, the second state information indicates a non-logged-in state, and when the state information is not the second state information, sending the target data to the first client;
[0034] The attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
[0035] In the embodiment of the present disclosure, three modes of second attribute information, namely, second device information, second status information and second user account, are provided. Clients that are not allowed to run the target data are set in terms of device, login status and user account, thereby adding the clients to a "blacklist", thereby increasing the diversity of running conditions and further increasing the flexibility of adjusting clients that are allowed to run the target data.
[0036] In some embodiments, sending the target data to at least one client meeting the operating condition includes:
[0037] The target data and the target data identifier are sent to the at least one client, where the target data identifier indicates the target data, and the at least one client is configured to return an exception notification carrying the target data identifier when an exception occurs to the target data.
[0038] In the disclosed embodiment, the target data and the corresponding target data identifier are sent to the first client at the same time. The target data identifier is equivalent to a mark of the target data, so that the first client can subsequently determine whether the target data indicated by the target data identifier has an abnormality. It helps the first client to determine which data has an abnormality based on the data identifier, thereby accurately notifying the electronic device of the abnormal data, which is conducive to shortening the abnormality positioning cycle.
[0039] In some embodiments, the operation information includes an average number of abnormalities of the target data, and the average number of abnormalities refers to the number of abnormalities of the target data within a unit time. When the operation information satisfies an update condition, updating the operation condition to obtain the updated operation condition includes:
[0040] When the average number of abnormalities satisfies the update condition, the operating condition is updated to obtain the updated operating condition, and the update condition is a condition that needs to be satisfied to trigger the update of the average number of abnormalities of the operating condition.
[0041] In the disclosed embodiment, since the average number of exceptions represents the abnormal situation of the target data, the operating conditions can indirectly determine the number of clients allowed to run the target data. Therefore, it is equivalent to deciding whether to change the number of clients allowed to run the target data based on the abnormal situation of the target data, which is beneficial to improving the reliability of managing the target data.
[0042] In some embodiments, the operating condition includes first attribute information, where the first attribute information indicates attribute information of a client that is allowed to run the target data; and when the average number of exceptions satisfies the update condition, updating the operating condition to obtain the updated operating condition includes:
[0043] When the average number of abnormalities is less than a first threshold, adding new first attribute information to the operating condition to obtain the updated operating condition;
[0044] In a case where the average number of abnormal times is greater than a second threshold and less than a third threshold, deleting at least one first attribute information in the operating condition to obtain the updated operating condition, the second threshold is greater than the first threshold, and the third threshold is greater than the second threshold;
[0045] When the average number of abnormalities is not less than the third threshold, the first attribute information in the operating condition is cleared to obtain the updated operating condition.
[0046] In the disclosed embodiment, when the average number of exceptions is small, the operating conditions are updated to increase the number of clients allowed to run the target data; when the average number of exceptions is large, the operating conditions are updated to reduce the number of clients allowed to run the target data; when the average number of exceptions is too large, the target data is directly stopped from running, thereby adaptively adjusting the operating range of the target data according to the number of exceptions of the target data, further improving the reliability and controllability of managing the target data, and without the need for manual intervention, the adaptive method is conducive to shortening the adjustment cycle of the operating range of the target data.
[0047] In some embodiments, the obtaining the operation information of the target data includes:
[0048] Querying at least one exception notification received within a first period of time before a current time point, the exception notification carrying a data identifier, the exception notification indicating that an exception occurs in the data indicated by the data identifier;
[0049] Determining, in the at least one exception notification, the number of exception notifications carrying a target data identifier, wherein the target data identifier indicates the target data;
[0050] The average number of abnormal times is determined according to the first duration and the number.
[0051] In the disclosed embodiment, the average number of abnormalities of the target data is determined by counting the number of abnormal notifications carrying the target data identifier received within the first time period before the current time point, which provides a convenient and fast way to determine the abnormal situation of the target data, so as to detect the abnormal situation of the target data in a timely manner. In addition, by receiving and storing abnormal notifications, it is helpful to record the abnormal situation of the target data, which is convenient for subsequent tracking and review of the abnormal situation of the target data.
[0052] In some embodiments, the exception notification corresponds to multiple exception types, and determining the number of exception notifications carrying the target data identifier in the at least one exception notification includes:
[0053] Among the at least one exception notification, the number of exception notifications that carry the target data identifier and belong to the target exception type is determined.
[0054] In the embodiment of the present disclosure, by counting the number of exception notifications with target data identification and belonging to the target exception type, the average number of exceptions of the target data belonging to the target exception type is determined, and a method for querying exception situations based on the exception type is provided to facilitate timely detection of different types of exceptions of the target data.
[0055] In some embodiments, the operating condition includes second attribute information, and the second attribute information indicates attribute information of a client that is not allowed to run the target data; and when the operating information satisfies the update condition, updating the operating condition to obtain the updated operating condition includes:
[0056] In the case where the operating information includes target attribute information corresponding to the client where the target data has an exception, the target attribute information is determined as the second attribute information, and the second attribute information is added to the operating condition to obtain the updated operating condition.
[0057] In the disclosed embodiment, since an exception occurs in the target data in the client corresponding to the target attribute information, the target attribute information of the client is determined as new second attribute information and added to the operating conditions to obtain updated operating conditions, that is, the target attribute information is added to the "blacklist", so that the client no longer meets the operating conditions of the target data in the future, and the target data is no longer sent to the client, thereby avoiding the situation where the target data in the client is abnormal again from the source.
[0058] In some embodiments, determining the operation information of the target data in the at least one client includes:
[0059] Querying at least one exception notification received within a second time period before the current time point, the exception notification carrying a data identifier and attribute information, the exception notification indicating that an exception occurs in the data indicated by the data identifier in the client corresponding to the attribute information;
[0060] In the at least one exception notification, the target attribute information in the exception notification carrying the target data identifier is obtained, and the target data identifier indicates the target data.
[0061] In the embodiment of the present disclosure, by obtaining the exception notification carrying the target data identifier received within the second time period before the current time point, the target attribute information corresponding to the client where the target data exception occurs is obtained from the exception notification, thereby providing a convenient and fast method for determining the abnormal client, so as to facilitate timely detection of the client where the target data exception occurs.
[0062] In some embodiments, after adding the new second attribute information to the operating condition to obtain the updated operating condition, the data management method further includes:
[0063] Any second attribute information whose survival time reaches a third time period is deleted from the current operating condition, where the survival time refers to the time period during which the second attribute information exists in the operating condition.
[0064] In the embodiment of the present disclosure, considering that the inability of the target data to run normally in the client is temporary, when the duration of adding the target attribute information to the "blacklist" of the target data reaches a third duration, the target attribute information is deleted from the "blacklist" so that the client can meet the running conditions of the target data again and re-run the target data.
[0065] In some embodiments, when the operating information satisfies the update condition, the operating condition is updated, and after obtaining the updated operating condition, the data management method further includes:
[0066] In response to a request from a second client for running the target data, acquiring the updated running condition, the second client being any client;
[0067] When the second client satisfies the updated operating condition, the target data is sent to the second client.
[0068] In the disclosed embodiment, the updated operating conditions are used to determine whether to send target data to other clients, which effectively controls the operating range of the target data according to the operating conditions and improves the controllability of the operating range of the target data.
[0069] According to another aspect of the embodiments of the present disclosure, there is provided a data management system, the data management system comprising a business server and a management server;
[0070] The business server is used to send target data to at least one client that meets the operating conditions, wherein the operating conditions are conditions that need to be met by the client to allow the target data to be run, the target data is used to implement a newly added function in the client, and the at least one client is used to run the target data;
[0071] The management server is used to determine the operation information of the target data, where the operation information indicates the operation status of the target data in the at least one client;
[0072] The management server is further configured to update the operating condition to obtain the updated operating condition when the operating information satisfies an update condition, wherein the update condition is a condition that needs to be satisfied by the operating information to trigger the update of the operating condition.
[0073] In some embodiments, the business server is used to:
[0074] In response to a first client's request for running the target data, acquiring the running condition, the first client being any client;
[0075] When the first client satisfies the operating condition, the target data is sent to the first client.
[0076] In some embodiments, the business server includes a business processing server and a conditional storage server;
[0077] The business processing server is used to respond to the operation request, obtain the target data identifier carried in the operation request, and send a conditional query request carrying the target data identifier to the conditional storage server, where the target data identifier indicates the target data;
[0078] The condition storage server is used to query the operating condition corresponding to the target data identifier in response to the condition query request, and send the operating condition to the business processing server;
[0079] The business processing server is used to receive the operating condition.
[0080] In some embodiments, the management server is used to update the locally stored operating condition when the operating information meets the update condition, obtain the updated operating condition, and send an update notification carrying the updated operating condition to the condition storage server;
[0081] The condition storage server is configured to replace the locally stored operating condition with the updated operating condition in response to the update notification.
[0082] In some embodiments, the running condition includes first attribute information, where the first attribute information indicates attribute information of a client that is allowed to run the target data, and the service server is configured to:
[0083] Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client;
[0084] In a case where the attribute information belongs to the first attribute information, the target data is sent to the first client.
[0085] In some embodiments, the business server is used to perform at least one of the following steps:
[0086] The attribute information includes the device information, the first attribute information includes first device information, and when the device information matches the first device information, the target data is sent to the first client;
[0087] The attribute information includes the state information, the first attribute information includes first state information, the first state information indicates a login state, and when the state information is the first state information, the target data is sent to the first client;
[0088] The attribute information includes a user account, the first attribute information includes a first user account, and when the user account belongs to the first user account, the target data is sent to the first client.
[0089] In some embodiments, the operating condition includes second attribute information, where the second attribute information indicates attribute information of a client that is not allowed to operate the target data, and the service server is configured to:
[0090] Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client;
[0091] In a case where the attribute information does not belong to the second attribute information, the target data is sent to the first client.
[0092] In some embodiments, the business server is used to perform at least one of the following steps:
[0093] The attribute information includes the device information, the second attribute information includes second device information, and when the device information does not match the second device information, sending the target data to the first client;
[0094] The attribute information includes the state information, the second attribute information includes second state information, the second state information indicates a non-logged-in state, and when the state information is not the second state information, sending the target data to the first client;
[0095] The attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
[0096] In some embodiments, the business server is used to send the target data and the target data identifier to the at least one client, the target data identifier indicates the target data, and the at least one client is used to return an exception notification carrying the target data identifier when an exception occurs in the target data.
[0097] In some embodiments, the operation information includes an average number of abnormalities of the target data, where the average number of abnormalities refers to the number of times the target data is abnormal within a unit time period;
[0098] The management server is used to update the operating condition to obtain the updated operating condition when the average number of abnormalities meets the update condition, and the update condition is the condition that needs to be met to trigger the update of the average number of abnormalities of the operating condition.
[0099] In some embodiments, the running condition includes first attribute information, where the first attribute information indicates attribute information of a client that is allowed to run the target data; the management server is configured to:
[0100] When the average number of abnormalities is less than a first threshold, adding new first attribute information to the operating condition to obtain the updated operating condition;
[0101] In a case where the average number of abnormal times is greater than a second threshold and less than a third threshold, deleting at least one first attribute information in the operating condition to obtain the updated operating condition, the second threshold is greater than the first threshold, and the third threshold is greater than the second threshold;
[0102] When the average number of abnormalities is not less than the third threshold, the first attribute information in the operating condition is cleared to obtain the updated operating condition.
[0103] In some embodiments, the management server includes a condition management server and an operation management server;
[0104] The condition management server is used to send a first query request for the target data to the operation management server;
[0105] The operation management server is used to query the average number of abnormalities of the target data in response to the first query request, and send the average number of abnormalities to the condition management server;
[0106] The condition management server is used to receive the average number of abnormalities, and update the operating condition when the average number of abnormalities meets the update condition to obtain the updated operating condition.
[0107] In some embodiments, the operation management server is used to:
[0108] In response to the first query request, query at least one abnormal notification received within a first period before the current time point, the abnormal notification carrying a data identifier, and the abnormal notification indicating that an abnormality occurs in the data indicated by the data identifier;
[0109] Determining, in the at least one exception notification, the number of exception notifications carrying a target data identifier, wherein the target data identifier indicates the target data;
[0110] The average number of abnormal times is determined according to the first duration and the number.
[0111] In some embodiments, the abnormal notification corresponds to multiple abnormal types, and the operation management server is used to:
[0112] Obtaining the target exception type carried in the first query request;
[0113] Among the at least one exception notification, the number of exception notifications that carry the target data identifier and belong to the target exception type is determined.
[0114] In some embodiments, the running condition includes second attribute information, and the second attribute information indicates attribute information of a client that is not allowed to run the target data;
[0115] The management server is used to determine the target attribute information as the second attribute information when the operating information includes the target attribute information corresponding to the client where the target data has an abnormality, and add the second attribute information to the operating condition to obtain the updated operating condition.
[0116] In some embodiments, the management server includes a condition management server and an operation management server;
[0117] The condition management server is used to send a second query request for the target data to the operation management server;
[0118] The operation management server is used to query the target attribute information corresponding to the client where the target data is abnormal in response to the second query request, and send the target attribute information to the condition management server;
[0119] The condition management server is used to receive the target attribute information, determine the target attribute information as the second attribute information, add the second attribute information to the operating condition, and obtain the updated operating condition.
[0120] In some embodiments, the operation management server is used to:
[0121] In response to the first query request, query at least one exception notification received within a second time period before the current time point, the exception notification carrying a data identifier and attribute information, the exception notification indicating that the data indicated by the data identifier has an exception in a client corresponding to the attribute information;
[0122] In the at least one exception notification, the target attribute information in the exception notification carrying the target data identifier is obtained, and the target data identifier indicates the target data.
[0123] In some embodiments, the condition management server is further used to delete any second attribute information whose survival time reaches a third time period from the current operating conditions, where the survival time refers to the time period that the second attribute information exists in the operating conditions.
[0124] In some embodiments, the business server is further used to:
[0125] In response to a request from a second client for running the target data, acquiring the updated running condition, the second client being any client;
[0126] When the second client satisfies the updated operating condition, the target data is sent to the second client.
[0127] According to another aspect of the embodiments of the present disclosure, a data management device is provided, the data management device comprising:
[0128] a data sending unit, configured to send target data to at least one client satisfying an operating condition, wherein the operating condition is a condition that needs to be satisfied by the client to allow the target data to be run, the target data is used to implement a newly added function in the client, and the at least one client is used to run the target data;
[0129] an information acquisition unit, configured to determine operation information of the target data, wherein the operation information indicates an operation status of the target data in the at least one client;
[0130] The condition updating unit is configured to update the operating condition to obtain the updated operating condition when the operating information meets the update condition, and the update condition is the condition that the operating information needs to meet to trigger the update of the operating condition.
[0131] In some embodiments, the data sending unit includes:
[0132] a condition acquisition subunit, configured to execute and obtain the operation condition in response to an operation request of the first client for the target data, wherein the first client is any client;
[0133] The data sending subunit is configured to send the target data to the first client when the first client meets the operating condition.
[0134] In some embodiments, the condition acquisition subunit is configured to execute:
[0135] In response to the operation request, obtaining a target data identifier carried in the operation request, wherein the target data identifier indicates the target data;
[0136] The operating condition corresponding to the target data identifier is queried.
[0137] In some embodiments, the running condition includes first attribute information, where the first attribute information indicates attribute information of a client that is allowed to run the target data, and the data sending subunit is configured to execute:
[0138] Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client;
[0139] In a case where the attribute information belongs to the first attribute information, the target data is sent to the first client.
[0140] In some embodiments, the data sending subunit is configured to perform at least one of the following:
[0141] The attribute information includes the device information, the first attribute information includes first device information, and when the device information matches the first device information, the target data is sent to the first client;
[0142] The attribute information includes the state information, the first attribute information includes first state information, the first state information indicates a login state, and when the state information is the first state information, the target data is sent to the first client;
[0143] The attribute information includes a user account, the first attribute information includes a first user account, and when the user account belongs to the first user account, the target data is sent to the first client.
[0144] In some embodiments, the running condition includes second attribute information, where the second attribute information indicates attribute information of a client that is not allowed to run the target data, and the data sending subunit is configured to execute:
[0145] Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client;
[0146] In a case where the attribute information does not belong to the second attribute information, the target data is sent to the first client.
[0147] In some embodiments, the data sending subunit is configured to perform at least one of the following:
[0148] The attribute information includes the device information, the second attribute information includes second device information, and when the device information does not match the second device information, sending the target data to the first client;
[0149] The attribute information includes the state information, the second attribute information includes second state information, the second state information indicates a non-logged-in state, and when the state information is not the second state information, sending the target data to the first client;
[0150] The attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
[0151] In some embodiments, the data sending unit includes:
[0152] The data and identification sending subunit is configured to send the target data and target data identification to the at least one client, wherein the target data identification indicates the target data, and the at least one client is used to return an exception notification carrying the target data identification when an exception occurs in the target data.
[0153] In some embodiments, the operation information includes an average number of abnormalities of the target data, where the average number of abnormalities refers to the number of abnormalities of the target data within a unit time; the condition updating unit includes:
[0154] The condition update subunit is configured to update the operating condition to obtain the updated operating condition when the average number of abnormalities meets the update condition, and the update condition is the condition that needs to be met to trigger the update of the average number of abnormalities of the operating condition.
[0155] In some embodiments, the running condition includes first attribute information, where the first attribute information indicates attribute information of a client that is allowed to run the target data; the condition updating subunit is configured to execute:
[0156] When the average number of abnormalities is less than a first threshold, adding new first attribute information to the operating condition to obtain the updated operating condition;
[0157] In a case where the average number of abnormal times is greater than a second threshold and less than a third threshold, deleting at least one first attribute information in the operating condition to obtain the updated operating condition, the second threshold is greater than the first threshold, and the third threshold is greater than the second threshold;
[0158] When the average number of abnormalities is not less than the third threshold, the first attribute information in the operating condition is cleared to obtain the updated operating condition.
[0159] In some embodiments, the information acquisition unit includes:
[0160] A notification query subunit is configured to query at least one abnormal notification received within a first time period before a current time point, wherein the abnormal notification carries a data identifier, and the abnormal notification indicates that an abnormality occurs in the data indicated by the data identifier;
[0161] A number determination subunit is configured to determine the number of abnormal notifications carrying a target data identifier in the at least one abnormal notification, wherein the target data identifier indicates the target data;
[0162] The number determination subunit is configured to determine the average number of abnormal times based on the first duration and the number.
[0163] In some embodiments, the exception notification corresponds to multiple exception types, and the number determination subunit is configured to execute in the at least one exception notification to determine the number of exception notifications that carry the target data identifier and belong to the target exception type.
[0164] In some embodiments, the running condition includes second attribute information, and the second attribute information indicates attribute information of a client that is not allowed to run the target data; and the condition updating unit includes:
[0165] The condition updating subunit is configured to determine the target attribute information as the second attribute information when the operating information includes the target attribute information corresponding to the client where the target data has an exception, and add the second attribute information to the operating condition to obtain the updated operating condition.
[0166] In some embodiments, the information acquisition unit includes:
[0167] A notification query subunit is configured to query at least one abnormal notification received within a second time period before a current time point, wherein the abnormal notification carries a data identifier and attribute information, and the abnormal notification indicates that an abnormality occurs in the client corresponding to the attribute information and the data indicated by the data identifier;
[0168] The information acquisition subunit is configured to execute, in the at least one abnormal notification, acquiring the target attribute information in the abnormal notification carrying the target data identifier, where the target data identifier indicates the target data.
[0169] In some embodiments, the condition update subunit is further configured to delete any second attribute information whose survival time reaches a third time period from the current operating condition, where the survival time refers to the time period that the second attribute information exists in the operating condition.
[0170] In some embodiments, the data sending unit is further configured to execute:
[0171] In response to a request from a second client for running the target data, acquiring the updated running condition, the second client being any client;
[0172] When the second client satisfies the updated operating condition, the target data is sent to the second client.
[0173] According to another aspect of the embodiments of the present disclosure, an electronic device is provided, the electronic device comprising:
[0174] processor;
[0175] a memory for storing instructions executable by the processor;
[0176] The processor is configured to execute the instructions to implement the data management method as described in the above aspects.
[0177] According to another aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can execute the data management method as described in the above aspects.
[0178] According to another aspect of the embodiments of the present disclosure, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the data management method as described in the above aspects is implemented.
[0179] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0180] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0181] Figure 1 The diagram is a structural diagram of a data management system according to an exemplary embodiment.
[0182] Figure 2 It is a schematic structural diagram of another data management system according to an exemplary embodiment.
[0183] Figure 3 It is a schematic structural diagram of another data management system according to an exemplary embodiment.
[0184] Figure 4 The invention is a flow chart of a data management method according to an exemplary embodiment.
[0185] Figure 5 The figure is a flow chart of another data management method according to an exemplary embodiment.
[0186] Figure 6 is a flow chart of yet another data management method according to an exemplary embodiment.
[0187] Figure 7 The figure is a flow chart of yet another data management method according to an exemplary embodiment.
[0188] Figure 8 The figure is a flowchart showing how to manage target data according to an exemplary embodiment.
[0189] Fig. 9 The invention is a flowchart of sending target data according to an exemplary embodiment.
[0190] Fig.10 The flowchart of another method of sending target data is shown according to an exemplary embodiment.
[0191] Fig.11 It is a block diagram of a data management device according to an exemplary embodiment.
[0192] Fig.12 It is a block diagram of another data management device according to an exemplary embodiment.
[0193] Fig.13 It is a block diagram of a terminal according to an exemplary embodiment.
[0194] Fig.14 It is a block diagram of a server according to an exemplary embodiment. DETAILED DESCRIPTION
[0195] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.
[0196] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned figure descriptions are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0197] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.
[0198] The embodiment of the present disclosure provides a data management system, which is used to manage data sent to a client, and the data is used to run in the client to implement new functions. Figure 1 is a structural diagram of a data management system provided by an embodiment of the present disclosure, such as Figure 1 As shown, the data management system includes a business server 101 and a management server 102. The business server 101 and the management server 102 can be an independent server, or a server cluster or a distributed cluster composed of multiple servers. A communication connection is established between the business server 101 and the management server 102, and a communication connection is established between the business server 101 and the management server 102 and the client.
[0199] The business server 101 is used to provide business services to the client. The business server 101 sends data to the client so that the client can implement the corresponding function. For example, the business server determines which clients to send data to based on the operating conditions that the client that is allowed to run the data needs to meet. The management server 102 is used to manage the data sent to the client. The management server 102 controls which clients can run the data by managing and updating the operating conditions that the client that is allowed to run the data needs to meet. For example, the management server 102 updates the operating conditions based on the running status of the data in the client.
[0200] In some embodiments, Figure 2 As shown, the business server 101 includes a business processing server 111 and a conditional storage server 121, and the management server 102 includes a conditional management server 112 and an operation management server 122. A communication connection is established between the business processing server 111 and the conditional storage server 121, a communication connection is established between the conditional management server 112 and the operation management server 122, a communication connection is established between the business processing server 111 and the conditional management server 112, and a communication connection is established between the conditional storage server 121 and the operation management server 122. The business processing server 111 and the operation management server 122 establish communication connections with the client, respectively.
[0201] The business processing server 111 is used to send data to the client according to the operating conditions that the client needs to meet to allow the data to run, and the condition storage server 121 is used to store the operating conditions. The condition management server 112 is used to send and update the operating conditions, and the operation management server 122 is used to detect and store the operation status of the data in the client.
[0202] In some embodiments, Figure 3 is a structural diagram of a data management system provided by an embodiment of the present disclosure, such as Figure 3 As shown, the data management system includes a condition management client 301, an operation condition / update condition management module 302, an operation condition / update condition broadcast module 303, a database 304, a condition storage server 305, an operation management server 306, a business processing server 307 and a business client 308, wherein the operation condition / update condition management module 302, the operation condition / update condition broadcast module 303 and the database 304 belong to the above Figure 2 The connection relationship between the various parts of the condition management server is detailed in Figure 3 , the functions of each part are described in detail below:
[0203] (1) The condition management client 301 is a client provided by the condition management server. The condition management client 301 is used to apply for data identification for data, and configure operating conditions and update conditions for data. The operating conditions refer to the conditions that the client needs to meet to run the data, and the update conditions refer to the conditions that trigger the update of the operating information of the operating conditions. The operating information indicates the operating status of the data. The condition management client 301 uploads the configured data identification, operating conditions and update conditions to the operating condition / update condition management module 302 in the condition management server.
[0204] (2) The operating condition / update condition management module 302 is used to manage the operating conditions and update conditions corresponding to each data. After receiving the data identifier, operating condition and update condition uploaded by the condition management client 301, the operating condition / update condition management module 302 stores the data identifier, operating condition and update condition correspondingly in the database 304.
[0205] (3) The operating condition / update condition broadcasting module 303 is used to broadcast the operating conditions. The operating condition / update condition broadcasting module 303 periodically pulls the operating information of the data from the operation management server 306, and pulls the update conditions corresponding to the data from the operating condition / update condition management module 302. If the operating information meets the update conditions, the operating conditions corresponding to the data are updated, and the updated operating conditions are broadcast to the operating condition / update condition management module 302 and the condition storage server 305.
[0206] (4) The condition storage server 305 is used to store the operating conditions. The condition storage server 305 receives the operating conditions from the operating condition / update condition broadcasting module 303, stores the operating conditions, and subsequently provides the operating conditions to the business processing server 308.
[0207] (5) The operation management server 306 is used to detect and store the operation information of the data, which indicates the operation status of the data in the service client 308 , and subsequently provide the operation information to the operation condition / update condition broadcast module 303 .
[0208] (6) The business processing server 307 is used to provide services for the business client 308. The business processing server 307 pulls the operating conditions of the data from the condition storage server 305, and sends the data to the business client 308 when the business client 308 meets the operating conditions. Optionally, the business processing server 307 uses the SDK (Software Development Kit) provided by the condition management server to implement the acquisition and verification functions of the operating conditions, thereby determining whether the business client meets the operating conditions.
[0209] (7) The business client 308 is used to run the data sent by the business processing server 307 to implement the corresponding functions, wherein the business client 308 can be any type of client, for example, the business client 308 is a social client, a content sharing client, an online shopping client, or a video playing client, etc.
[0210] The data management method provided by the embodiments of the present disclosure is applicable to a variety of scenarios.
[0211] For example, it is applied in the scenario of grayscale testing. After the business server releases the client, new functions can be developed for the client to optimize the client. Before releasing the new functions of the client to all users, the new functions of the client can be released to some users to perform grayscale testing on the new functions of the client, so that timely adjustments can be made if there are problems with the new functions.
[0212] For example, if the new function is a game function, the code data used to implement the game function is the game data. The condition management server first configures the corresponding running conditions and update conditions for the game data. The running conditions are the conditions that must be met by the client to allow the game data to run, and the update conditions are the conditions that must be met to trigger the running information to update the running conditions. The running information indicates the running status of the game data in the client.
[0213] Whenever a client requests to use the new function, the business server first determines whether the client meets the operating conditions. If the operating conditions are met, the business server will send the game data to the client. If the operating conditions are not met, the business server will not send the game data to the client, so that the game data only runs in some clients. The condition management server obtains the operating information of the game data and determines whether the operating information meets the update conditions. If the update conditions are met, the operating conditions are updated. If the update conditions are not met, the operating conditions remain unchanged. Therefore, it can adaptively adjust the standards required to allow the game data to run according to the running status of the game data to control the number of clients running the game data, thereby flexibly controlling the scope of the grayscale test.
[0214] Figure 4 is a flow chart of a data management method according to an exemplary embodiment. Figure 4 The method is applied to an electronic device and comprises the following steps:
[0215] 401. The electronic device sends target data to at least one client that meets an operating condition.
[0216] The running condition is the condition that the client must meet to be allowed to run the target data. Since the client that meets the running condition is allowed to run the target data, and the client that does not meet the running condition is not allowed to run the target data, the running condition determines which clients are allowed to run the target data. Therefore, by adjusting the running condition, the number of clients allowed to run the target data can be indirectly controlled.
[0217] The target data is used to implement the newly added function in the client, for example, the target data is code data used to implement the newly added function, etc. The function implemented by the target data can be any type of function.
[0218] The electronic device stores target data and operating conditions. When at least one client satisfies the operating conditions, the target data is sent to the at least one client, and the at least one client runs the target data, thereby realizing the function corresponding to the target data.
[0219] 402. The electronic device determines operation information of the target data.
[0220] The operation information of the target data indicates the operation status of the target data in the at least one client. After sending the target data to the at least one client, the electronic device obtains the operation information of the target data.
[0221] 403. When the operating information meets the update condition, the electronic device updates the operating condition to obtain the updated operating condition.
[0222] The update condition is the condition that the operating information needs to meet to trigger the update of the operating condition. When the operating information meets the update condition, the current operating condition is updated. When the operating information does not meet the update condition, the current operating condition remains unchanged. Since the operating information represents the operating status of the target data, the embodiment of the present disclosure decides whether to update the operating conditions of the target data based on the operating status of the target data.
[0223] After the electronic device obtains the operating information of the target data, it obtains the update conditions corresponding to the target data. If the operating information meets the update conditions, it updates the operating conditions of the target data to obtain updated operating conditions. The updated operating conditions are the same as the operating conditions and will not be repeated here.
[0224] The method provided by the embodiment of the present disclosure uses operating conditions to control which clients are allowed to run target data, and uses update conditions to control whether to update the operating conditions. After the target data is sent to the client, the operating information of the target data in the client is automatically obtained, and whether the operating conditions need to be updated is determined based on whether the operating information meets the update conditions. In this way, the clients allowed to run the target data are adaptively adjusted based on the operating conditions of the target data, without consuming manpower, and the reliability of managing the target data can be improved.
[0225] In the above Figure 2 On the basis of the data management method shown, the operation information includes the average number of abnormalities of the target data or the target attribute information corresponding to the client where the target data has abnormalities. The average number of abnormalities refers to the number of times the target data has abnormalities within a unit time. The electronic device determines whether to update the operating conditions based on whether the operation information meets the update conditions. The specific process is detailed in the following embodiment.
[0226] Figure 5 is a flow chart of another data management method according to an exemplary embodiment. Figure 5 , the method is applied in an electronic device, the method comprising the following steps:
[0227] 501. The electronic device obtains an operating condition in response to an operating request of a first client for target data.
[0228] A communication connection is established between the electronic device and multiple clients, and the electronic device can provide services for the multiple clients. For example, the multiple clients are clients of the same type provided by the server, wherein the first client is any client among the multiple clients.
[0229] The target data is used to implement new functions in the client, and the target data is code data used to implement the new functions. The functions implemented by the target data can be any type of functions. The operating conditions are the conditions that must be met by the client to allow the target data to run. The operating conditions determine which clients are allowed to run the target data. Therefore, by adjusting the operating conditions, the number of clients allowed to run the target data can be indirectly controlled. For example, if you want to send the target data to 30% of the clients to run, you can determine a condition that only 30% of the clients can meet, and determine the condition as the operating condition. Then, based on the operating condition, the target data will only be sent to the 30% of clients that meet the operating condition.
[0230] In the embodiment of the present disclosure, the first client sends the operation request to the electronic device in response to the operation request for the target data, and the electronic device obtains the operation condition corresponding to the target data in response to the operation request.
[0231] In some embodiments, the operation request in the first client is triggered by an operation performed by the user in the first client. For example, a new message sending function is provided in a certain page of the first client, and the first client generates an operation request for message sending data in response to the viewing operation of the page, and the message sending data is used to implement the message sending function. For example, a new game function is provided in the first client, and the first client displays a reminder notification on the homepage, and the reminder notification is used to remind the user whether to use the new game function. The first client generates an operation request for game data in response to the confirmation operation of the reminder notification, and the game data is used to implement the game function.
[0232] In some embodiments, the electronic device responds to the operation request, obtains the target data identifier carried in the operation request, and queries the operation condition corresponding to the target data identifier.
[0233] Among them, the target data identifier is carried in the operation request for the target data, and the target data identifier indicates the target data. The electronic device stores the correspondence between the data identifier of any data and the operation condition of the data, so the electronic device obtains the target data identifier carried in the operation request, and queries the operation condition corresponding to the target data identifier, and the operation condition is the operation condition corresponding to the target data. In the embodiment of the present disclosure, the corresponding operation condition is queried through the target data identifier, and the target data identifier is equivalent to the index of the operation condition, which is conducive to improving the speed of obtaining the operation condition, thereby improving the query efficiency of the electronic device.
[0234] 502. When the first client meets the operating conditions, the electronic device sends target data to the first client.
[0235] When the electronic device obtains the operating conditions corresponding to the target data, it determines whether the first client meets the operating conditions. If the first client meets the operating conditions, it means that the first client is allowed to run the target data. The electronic device sends the target data to the first client so that the first client runs the target data to realize the newly added functions.
[0236] If the first client does not meet the running condition, it means that the first client is not allowed to run the target data, and the electronic device does not send the target data to the first client. In some embodiments, if the first client does not meet the running condition, the electronic device sends a rejection notification to the first client to notify the first client that the target data cannot be run.
[0237] In the disclosed embodiment, the client actively sends an operation request to the electronic device to request the operation target data, so that the client has the initiative to operate the target data, which is conducive to improving the flexibility and control ability of the client.
[0238] In some embodiments, when the first client meets the operating conditions, the electronic device sends target data and a target data identifier to the first client, where the target data identifier indicates the target data. The first client is used to return an exception notification carrying the target data identifier when an exception occurs in the target data.
[0239] The electronic device simultaneously returns the target data and the corresponding target data identifier to the first client. After receiving the target data and the target data identifier, the first client runs the target data, and in the process of running the target data, stores the target data identifier in the target storage space. The target storage space is used to store the data identifier corresponding to the running data. If an abnormality occurs in the first client during the operation, it means that an abnormality occurs in the data corresponding to the data identifier stored in the target storage space. Therefore, the first client directly obtains the target data identifier from the target storage space and returns an abnormality notification carrying the target data identifier to the electronic device to notify the electronic device that an abnormality occurs in the target data indicated by the target data identifier.
[0240] In the disclosed embodiment, the electronic device simultaneously sends the target data and the corresponding target data identifier to the first client. The target data identifier is equivalent to a mark of the target data, so that the first client can subsequently determine whether the target data indicated by the target data identifier has an abnormality. This helps the first client to determine which data has an abnormality based on the data identifier, thereby accurately notifying the electronic device of the abnormal data, which is beneficial to shortening the abnormality location cycle.
[0241] In some embodiments, the running condition includes first attribute information, and the first attribute information indicates attribute information of a client that is allowed to run the target data. When the first client meets the running condition, the electronic device sends the target data to the first client, including: obtaining the attribute information carried in the running request, and sending the target data to the first client when the attribute information belongs to the first attribute information.
[0242] The attribute information includes at least one of device information, status information or user account, the device information is information of the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is the user account logged in by the first client. If the attribute information of the first client belongs to the first attribute information in the operating condition, it means that the first client is a client that is allowed to run the target data, so the electronic device sends the target data to the first client. If the attribute information of the first client does not belong to the first attribute information in the operating condition, it means that the first client is not a client that is allowed to run the target data, so the electronic device does not need to send the target data to the first client.
[0243] In an embodiment of the present disclosure, a method for controlling the running conditions of target data based on first attribute information is provided. The first attribute information is equivalent to a "white list". If the attribute information of the client belongs to the first attribute information, the client is allowed to run the target data. If the attribute information of the client does not belong to the first attribute information, the client is not allowed to run the target data. Therefore, by changing the first attribute information, it is possible to adjust which clients are allowed to run the target data and which clients are not allowed to run the target data, thereby improving the flexibility of adjusting the clients allowed to run the target data.
[0244] In some embodiments, when the attribute information belongs to the first attribute information, sending the target data to the first client includes at least one of the following:
[0245] (1) The attribute information includes device information, the first attribute information includes first device information, and the electronic device sends the target data to the first client when the device information matches the first device information.
[0246] If the device information of the first client matches the first device information in the operating condition, it means that the first client is a client that is allowed to run the target data, so the electronic device sends the target data to the first client. If the attribute information of the first client does not match the first attribute information in the operating condition, it means that the first client is not a client that is allowed to run the target data, so the electronic device does not need to send the target data to the first client.
[0247] For example, the first device information is the target device model, the target device model is the model of the device where the client that allows the target data to run belongs, and the device information corresponding to the first client is the device model of the device where the first client belongs. Then the condition for the electronic device to send the target data to the first client is that the device model corresponding to the first client belongs to the target device model.
[0248] (2) The attribute information includes state information, the first attribute information includes first state information, the first state information indicates a login state, and the electronic device sends the target data to the first client when the state information is the first state information.
[0249] Among them, the client allowed to run the target data is a client in a logged-in state, and the attribute information of the first client is the status information of the first client. If the status information is the first status information, that is, the first client is in a logged-in state, the electronic device sends the target data to the first client. If the status information is not the first status information, that is, the first client is not in a logged-in state, the electronic device does not need to send the target data to the first client.
[0250] (3) The attribute information includes a user account, the first attribute information includes a first user account, and the electronic device sends the target data to the first client when the user account belongs to the first user account.
[0251] If the user account of the first client belongs to the first user account in the running condition, it means that the first client is a client that is allowed to run the target data, so the electronic device sends the target data to the first client. If the first user account of the first client does not belong to the first user account in the running condition, it means that the first client is not a client that is allowed to run the target data, so the electronic device does not need to send the target data to the first client.
[0252] For example, if the last digit of the first user account is 0-3, then if the last digit of the user account of the first client belongs to any one of 0-3, then the user account belongs to the first user account, and if the last digit of the user account of the first client does not belong to any one of 0-3, then the user account does not belong to the first user account. For another example, the first user account is: after hash processing, the last three digits belong to the user account of 0-300, etc. Among them, by increasing the first user account, the number of clients allowed to run the target data can be increased.
[0253] In the embodiment of the present disclosure, three methods are provided in which the first attribute information is the first device information, the first status information and the first user account, so as to limit the clients allowed to run the target data in terms of the device, the login status and the user account, thereby improving the diversity of the running conditions and further improving the flexibility of adjusting the clients allowed to run the target data.
[0254] In some embodiments, the running condition includes second attribute information, and the second attribute information indicates attribute information of a client that is not allowed to run the target data. When the first client meets the running condition, the electronic device sends the target data to the first client, including: obtaining the attribute information carried in the running request, and sending the target data to the first client when the attribute information does not belong to the second attribute information.
[0255] The attribute information includes at least one of device information, status information or user account, the device information is information of the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is the user account logged in by the first client. If the attribute information of the first client does not belong to the second attribute information in the operating condition, it means that the first client is not a client that is not allowed to run the target data, so the electronic device sends the target data to the first client. If the attribute information of the first client belongs to the second attribute information in the operating condition, it means that the first client is not a client that is not allowed to run the target data, so the electronic device does not need to send the target data to the first client.
[0256] In an embodiment of the present disclosure, a method for controlling the running conditions of target data based on second attribute information is provided, and the second attribute information is equivalent to a "blacklist". If the attribute information of the client does not belong to the second attribute information, the client is allowed to run the target data. If the attribute information of the client belongs to the second attribute information, the client is not allowed to run the target data. Therefore, by changing the second attribute information, it is possible to adjust which clients are allowed to run the target data and which clients are not allowed to run the target data, thereby improving the flexibility of adjusting the clients allowed to run the target data.
[0257] In some embodiments, when the attribute information belongs to the second attribute information, sending the target data to the first client includes at least one of the following:
[0258] (1) The attribute information includes device information, the second attribute information includes second device information, and when the device information does not match the second device information, the target data is sent to the first client.
[0259] If the device information of the first client does not match the second device information in the operating condition, it means that the first client does not hit the "blacklist", and the first client is not a client that is not allowed to run the target data, so the electronic device sends the target data to the first client. If the attribute information of the first client matches the second attribute information in the operating condition, it means that the first client hits the "blacklist", and the first client is a client that is not allowed to run the target data, so the electronic device does not need to send the target data to the first client.
[0260] For example, the second device information is a target device identifier, which is an identifier corresponding to a client that is not allowed to run the target data, and the device information corresponding to the first client is a device identifier corresponding to the device where the first client is located. Then the condition for the electronic device to send the target data to the first client is that the device identifier corresponding to the first client does not belong to the target device identifier.
[0261] (2) The attribute information includes state information, the second attribute information includes second state information, the second state information indicates a non-logged-in state, and when the state information is not the second state information, the target data is sent to the first client.
[0262] Among them, the client that is not allowed to run the target data is a client that is not logged in, and the attribute information of the first client is the status information of the first client. If the status information is not the second status information, that is, the first client is not in the logged in state, the electronic device sends the target data to the first client. If the status information is the second status information, that is, the first client is in the logged in state, the electronic device does not need to send the target data to the first client.
[0263] (3) The attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
[0264] If the user account of the first client does not belong to the second user account in the running condition, it means that the first client does not hit the "blacklist", and the first client is not a client that is not allowed to run the target data, so the electronic device sends the target data to the first client. If the first user account of the first client belongs to the second user account in the running condition, it means that the first client hits the "blacklist", and the first client is not a client that is not allowed to run the target data, so the electronic device does not need to send the target data to the first client.
[0265] In the embodiment of the present disclosure, three modes of second attribute information, namely, second device information, second status information and second user account, are provided. Clients that are not allowed to run the target data are set in terms of device, login status and user account, thereby adding the clients to a "blacklist", thereby increasing the diversity of running conditions and further increasing the flexibility of adjusting clients that are allowed to run the target data.
[0266] It should be noted that the above embodiment is described by taking the operating condition including the first attribute information or the operating condition including the second attribute information as an example. In another embodiment, the operating condition includes both the first attribute information and the second attribute information. If the attribute information corresponding to the first client belongs to the first attribute information and does not belong to the second attribute information, the electronic device sends the target data to the first client.
[0267] It should be noted that the above steps 501-502 only take the first client among multiple clients as an example to illustrate the process of the electronic device sending target data to the first client, wherein any client among the multiple clients can send an operation request to the electronic device, so that the electronic device returns the target data to the client when the client meets the operation conditions. Therefore, the electronic device implements sending the target data to at least one client that meets the operation conditions by executing the above steps 501-502 at least once.
[0268] It should be noted that the above steps 501-502 are only described by taking the client actively requesting the electronic device to run the target data as an example. In another embodiment, the electronic device can also actively send the target data to at least one client, that is, the electronic device obtains the running conditions of the target data, determines at least one client that meets the running conditions among multiple clients, directly sends the target data to the at least one client, and the at least one client runs the target data.
[0269] 503. The electronic device determines operation information of the target data.
[0270] After the electronic device sends the target data to at least one client, the at least one client runs the received target data, and the electronic device obtains the running information of the target data, where the running information indicates the running status of the target data in the at least one client.
[0271] In some embodiments, the operation information includes the average number of abnormalities, which refers to the number of times the target data is abnormal within a unit time. The electronic device determines the operation information of the target data, including: querying at least one abnormal notification received within a first time before the current time point, the abnormal notification carries a data identifier, and the abnormal notification indicates that the data indicated by the data identifier is abnormal. In at least one abnormal notification, determine the number of abnormal notifications carrying the target data identifier, and the target data identifier indicates the target data; determine the average number of abnormalities based on the first time and the number. Optionally, the first time is a time preset by the electronic device, for example, the first time is 1 hour or 2 hours.
[0272] When an abnormality occurs in the data, the client sends an abnormality notification carrying the data identifier to the electronic device. The electronic device will receive abnormality notifications sent by multiple clients, and the data identifiers carried in each abnormality notification may be the same or different. The electronic device then uses the data identifier as a dimension to determine the number of abnormalities when the data is abnormal. In other words, it determines the number of abnormalities corresponding to the same data identifier.
[0273] Since the exception notification indicates that an exception has occurred in the data indicated by the data identifier, the exception notification carrying the target data identifier indicates that an exception has occurred in the target data. In order to query the average number of exceptions of the target data, the electronic device determines the number of exception notifications carrying the target data identifier in at least one exception notification, which is the number of times the target data has been abnormal within a first time period at the current time point. Therefore, the electronic device can determine the average number of times the target data has been abnormal based on the first time period and the number. For example, the electronic device determines the ratio of the first time period to the unit time period, and determines the quotient obtained by dividing the number by the ratio as the average number of exceptions of the target data.
[0274] In the disclosed embodiment, the average number of abnormalities of the target data is determined by counting the number of abnormal notifications carrying the target data identifier received within the first time period before the current time point, which provides a convenient and fast way to determine the abnormal situation of the target data, so as to detect the abnormal situation of the target data in a timely manner. In addition, by receiving and storing abnormal notifications, it is helpful to record the abnormal situation of the target data, which is convenient for subsequent tracking and review of the abnormal situation of the target data.
[0275] In some embodiments, if there are multiple exception types corresponding to the exception notification, the electronic device determines the number of exception notifications carrying the target data identifier in at least one exception notification, including: determining the number of exception notifications carrying the target data identifier and belonging to the target exception type in at least one exception notification.
[0276] The target anomaly type can be any one of a plurality of anomaly types, that is, the electronic device can query the number of anomalies of any anomaly type. In the disclosed embodiment, the electronic device determines the average number of anomalies of the target data belonging to the target anomaly type by counting the number of anomaly notifications with target data identification and belonging to the target anomaly type, and provides a method for querying anomalies with anomaly type as a dimension, so as to facilitate timely detection of different types of anomalies of the target data.
[0277] Optionally, the exception notification received by the electronic device carries an exception stack where the exception occurred, and the electronic device analyzes the exception stack in the exception notification to determine the exception type corresponding to the exception notification.
[0278] In some embodiments, the operation information includes target attribute information corresponding to the client where the target data is abnormal. The electronic device determines the operation information of the target data, including: querying at least one abnormal notification received within a second period before the current time point, the abnormal notification carries a data identifier and attribute information, the abnormal notification indicates the data indicated by the data identifier, an abnormality occurs in the client corresponding to the attribute information, and in at least one abnormal notification, the target attribute information in the abnormal notification carrying the target data identifier is obtained, and the target data identifier indicates the target data.
[0279] When an abnormality occurs in the data, the client sends an abnormality notification carrying the data identifier and the attribute information of the client to the electronic device. The electronic device will receive abnormality notifications sent by multiple clients, and the data identifiers carried in each abnormality notification may be the same or different. The electronic device then uses the data identifier as a dimension to determine the number of abnormalities when the data is abnormal. In other words, it determines the number of abnormalities corresponding to the same data identifier.
[0280] Since the exception notification indicates that an exception has occurred in the data indicated by the data identifier, the exception notification carrying the target data identifier indicates that an exception has occurred in the target data. In order to query the target attribute information corresponding to the client where the target data exception has occurred, the electronic device determines the exception notification carrying the target data identifier in at least one exception notification. The attribute information carried in the exception notification is the target attribute information corresponding to the client where the target data exception has occurred.
[0281] In the embodiment of the present disclosure, by obtaining the exception notification carrying the target data identifier received within the second time period before the current time point, the target attribute information corresponding to the client where the target data exception occurs is obtained from the exception notification, thereby providing a convenient and fast method for determining the abnormal client, so as to facilitate timely detection of the client where the target data exception occurs.
[0282] 504. When the operating information meets the update condition, the electronic device updates the operating condition to obtain the updated operating condition.
[0283] The update condition is the condition that the operating information needs to meet to trigger the update of the operating condition. If the operating information meets the update condition, the current operating condition is updated. If the operating information does not meet the update condition, the current operating condition remains unchanged.
[0284] After the electronic device obtains the operation information of the target data, it obtains the update condition corresponding to the target data, and when the operation information satisfies the update condition, it updates the operation condition of the target data to obtain the updated operation condition, thereby changing the client that is allowed to run the target data. In the disclosed embodiment, since the operation information indicates the abnormal situation of the target data, the operation condition can indirectly determine the number of clients that are allowed to run the target data. Therefore, it is equivalent to deciding whether to change the number of clients that are allowed to run the target data according to the abnormal situation of the target data, which is conducive to improving the reliability of managing the target data.
[0285] In some embodiments, the operation information includes the average number of abnormalities of the target data, and the operation condition includes first attribute information, and the first attribute information indicates attribute information of the client that allows the target data to be operated. Then, when the average number of abnormalities meets the update condition, the electronic device updates the operation condition to obtain the updated operation condition. Optionally, updating the operation condition includes the following three situations:
[0286] (1) When the average number of abnormalities is less than the first threshold, new first attribute information is added to the operating condition to obtain an updated operating condition.
[0287] If the average number of abnormalities is less than the first threshold, it means that the number of abnormalities in the target data is small, and it can be considered that the target data can operate normally. The range of clients running the target data can be expanded. Therefore, the electronic device adds new first attribute information to the operating conditions to obtain updated operating conditions, so that the clients corresponding to the new first attribute information also become clients allowed to run the target data.
[0288] The number of clients allowed to run the target data determined by the updated operating conditions is greater than the number of clients allowed to run the target data determined by the operating conditions. Therefore, by adding new first attribute information, the number of clients allowed to run the target data is increased, that is, the scope of clients running the target data is expanded.
[0289] (2) When the average number of abnormalities is greater than the second threshold and less than the third threshold, at least one first attribute information is deleted from the operating condition to obtain an updated operating condition, in which the second threshold is greater than the first threshold and the third threshold is greater than the second threshold.
[0290] If the average number of abnormalities is greater than the second threshold and less than the third threshold, it means that the target data has a large number of abnormalities. It can be considered that the target data is difficult to operate normally and the range of clients that run the target data can be narrowed. Therefore, the electronic device deletes at least one first attribute information in the operating conditions and obtains updated operating conditions, thereby making the client corresponding to the first attribute information a client that is not allowed to run the target data.
[0291] The number of clients allowed to run the target data determined by the updated operating conditions is less than the number of clients allowed to run the target data determined by the operating conditions. Therefore, by deleting the first attribute information, the number of clients allowed to run the target data is reduced, that is, the scope of clients running the target data is narrowed.
[0292] (3) When the average number of abnormalities is not less than the third threshold, the first attribute information in the operating condition is cleared to obtain an updated operating condition.
[0293] If the average number of exceptions is not less than the third threshold, it means that the target data has too many exceptions. It can be considered that the target data cannot run normally and needs to be stopped directly. Therefore, the electronic device clears the first attribute information in the operating conditions and obtains the updated operating conditions. That is, no client meets the conditions for allowing the target data to run, so the target data is stopped to avoid abnormal situations caused by running the target data.
[0294] Optionally, the first threshold, the second threshold and the third threshold are all preset by the electronic device. It should be noted that when the average number of abnormalities is not less than the first threshold and not greater than the second threshold, the average number of abnormalities does not meet the update condition, so there is no need to update the operating condition.
[0295] In the disclosed embodiment, when the average number of exceptions is small, the operating conditions are updated to increase the number of clients allowed to run the target data; when the average number of exceptions is large, the operating conditions are updated to reduce the number of clients allowed to run the target data; when the average number of exceptions is too large, the target data is directly stopped from running, thereby adaptively adjusting the operating range of the target data according to the number of exceptions of the target data, further improving the reliability and controllability of managing the target data, and without the need for manual intervention, the adaptive method is conducive to shortening the adjustment cycle of the operating range of the target data.
[0296] In some embodiments, the operating condition includes second attribute information, and the second attribute information indicates attribute information of a client that is not allowed to run the target data. Then, when the operating information satisfies the update condition, the electronic device updates the operating condition to obtain the updated operating condition, including: when the operating information includes the target attribute information corresponding to the client where the target data is abnormal, the target attribute information is determined as the second attribute information, and the second attribute information is added to the operating condition to obtain the updated operating condition. Among them, the target attribute information can be the device identifier of the device where the client is located, or the user account logged in by the client, etc., which is not limited in the embodiments of the present disclosure.
[0297] Since an exception has occurred in the target data in the client corresponding to the target attribute information, it means that the target data cannot operate normally in the client. In order to prevent the target data from occurring an exception in the client again, the electronic device can determine the target attribute information of the client as new second attribute information, add it to the operating conditions, and obtain updated operating conditions, that is, add the target attribute information to the "blacklist", so that when the client subsequently requests to operate the target data again, the client does not meet the updated operating conditions, and the target data is no longer sent to the client, thereby preventing the target data from occurring an exception in the client again from the source.
[0298] In some embodiments, the electronic device deletes any second attribute information whose survival time reaches a third time period from the current operating conditions, where the survival time refers to the time period that the second attribute information exists in the operating conditions.
[0299] In the disclosed embodiment, considering that the target data cannot be normally operated in the client is temporary, the electronic device determines the target attribute information as the new second attribute information, and when the time after adding it to the operating condition reaches the third time, the target attribute information is deleted from the operating condition of the target data. That is, when the time after adding the target attribute information to the "blacklist" of the target data reaches the third time, the target attribute information is deleted from the "blacklist" so that the client can hit the operating condition of the target data again and re-operate the target data.
[0300] It should be noted that the above steps 503-504 are only described by taking the acquisition of operation information once as an example. In another embodiment, the electronic device periodically acquires the operation information of the target data, determines whether the operation information satisfies the update condition, updates the operation condition if the update condition is satisfied, and keeps the operation condition unchanged if the update condition is not satisfied. For example, if the period is 1 minute, the electronic device acquires the operation information once every 1 minute, and determines whether the operation condition needs to be updated based on the acquired operation information.
[0301] 505. The electronic device obtains updated operating conditions in response to the second client's operating request for the target data.
[0302] 506. When the second client meets the updated operating condition, the electronic device sends the target data to the second client.
[0303] The second client is any client among the plurality of clients. In some embodiments, the function implemented by the target data is an online function, so before each operation of the target data by the client, it is necessary to request the target data from the electronic device, and the first client and the second client can be the same client or different clients.
[0304] After the electronic device updates the operating condition to obtain the updated operating condition, it determines whether to send the target data according to the updated operating condition. Steps 505-506 are similar to the above steps 501-502 and will not be described in detail here.
[0305] In the disclosed embodiment, the updated operating conditions are used to determine whether to send target data to other clients, which effectively controls the operating range of the target data according to the operating conditions and improves the controllability of the operating range of the target data.
[0306] The method provided by the embodiment of the present disclosure uses operating conditions to control which clients are allowed to run target data, and uses update conditions to control whether to update the operating conditions. After the target data is sent to the client, the operating information of the target data in the client is automatically obtained, and whether the operating conditions need to be updated is determined based on whether the operating information meets the update conditions. In this way, the clients allowed to run the target data are adaptively adjusted based on the operating conditions of the target data, without consuming manpower, and the reliability of managing the target data can be improved.
[0307] In the above Figure 1 The data management system shown and Figure 4 On the basis of the data management method shown, the business server and the management server in the data management system manage the operating scope of the target data. The specific process is detailed in the following embodiment.
[0308] Figure 6 is a flowchart of another data management method according to an exemplary embodiment. Figure 6 , the method is applied in a data management system and comprises the following steps:
[0309] 601. The service server sends target data to at least one client that meets an operating condition.
[0310] 602. The management server determines the operation information of the target data.
[0311] 603. When the operation information satisfies the update condition, the management server updates the operation condition and obtains the updated operation condition.
[0312] Wherein, when the operation information meets the update condition, the management server directly updates the operation condition in the business server to the updated operation condition, so that the subsequent business server sends the target data according to the updated operation condition. Alternatively, the management server updates the locally stored operation condition to obtain the updated operation condition, notifies the business server of the updated operation condition, and the business server replaces the locally stored operation condition with the updated operation condition.
[0313] The above steps 601-603 and Figure 4 The same is true for steps 401-403 in the above description, which will not be repeated here.
[0314] The method provided by the embodiment of the present disclosure uses operating conditions to control which clients are allowed to run target data, and uses update conditions to control whether to update the operating conditions. After the target data is sent to the client, the operating information of the target data in the client is automatically obtained, and whether the operating conditions need to be updated is determined based on whether the operating information meets the update conditions. In this way, the clients allowed to run the target data are adaptively adjusted based on the operating conditions of the target data, without consuming manpower, and the reliability of managing the target data can be improved.
[0315] In the above Figure 1 The data management system shown and Figure 5 On the basis of the data management method shown, the business server and the management server in the data management system manage the operating scope of the target data. The specific process is detailed in the following embodiment.
[0316] Figure 7 is a flowchart of another data management method according to an exemplary embodiment. Figure 7 , the method is applied in a data management system, the method comprising the following steps:
[0317] 701. The business server obtains an operation condition in response to an operation request for target data from a first client.
[0318] 702. When the first client meets the operating condition, the business server sends target data to the first client.
[0319] In some embodiments, the business server sends target data and a target data identifier to at least one client, where the target data identifier indicates the target data, and the at least one client is configured to return an exception notification carrying the target data identifier when an exception occurs to the target data.
[0320] In some embodiments, the operation condition includes first attribute information, and the first attribute information indicates attribute information of a client that is allowed to operate the target data. The business server obtains the attribute information carried in the operation request, and the attribute information includes at least one of device information, state information, or user account. The device information is information about the device where the first client is located, the state information indicates whether the first client is logged in, and the user account is the user account logged in by the first client; when the attribute information belongs to the first attribute information, the target data is sent to the first client.
[0321] In some embodiments, the business server performs at least one of the following steps: the attribute information includes device information, the first attribute information includes first device information, and when the device information matches the first device information, the target data is sent to the first client; the attribute information includes status information, the first attribute information includes first status information, the first status information indicates a login status, and when the status information is the first status information, the target data is sent to the first client; the attribute information includes a user account, the first attribute information includes a first user account, and when the user account belongs to the first user account, the target data is sent to the first client.
[0322] In some embodiments, the operation condition includes second attribute information, and the second attribute information indicates attribute information of a client that is not allowed to operate the target data. The business server obtains attribute information carried in the operation request, and the attribute information includes at least one of device information, state information, or user account. The device information is information about the device where the first client is located, the state information indicates whether the first client is logged in, and the user account is the user account logged in by the first client; if the attribute information does not belong to the second attribute information, the target data is sent to the first client.
[0323] In some embodiments, the business server performs at least one of the following steps: the attribute information includes device information, the second attribute information includes second device information, and when the device information does not match the second device information, the target data is sent to the first client; the attribute information includes status information, the second attribute information includes second status information, the second status information indicates a non-logged-in state, and when the status information is not the second status information, the target data is sent to the first client; the attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
[0324] By executing the above steps 701-702 at least once, the service server can send target data to at least one client that meets the operating conditions.
[0325] 703. The management server determines the operation information of the target data.
[0326] 704. When the operation information satisfies the update condition, the management server updates the operation condition to obtain the updated operation condition.
[0327] Wherein, when the operation information meets the update condition, the management server directly updates the operation condition in the business server to the updated operation condition. Alternatively, the management server updates the locally stored operation condition to obtain the updated operation condition, notifies the business server of the updated operation condition, and the business server replaces the locally stored operation condition with the updated operation condition.
[0328] In some embodiments, the operation information includes the average number of abnormalities of the target data, and the operation condition includes the first attribute information, and the first attribute information indicates the attribute information of the client that is allowed to operate the target data. When the average number of abnormalities is less than the first threshold, the management server adds new first attribute information to the operation condition to obtain the updated operation condition; when the average number of abnormalities is greater than the second threshold and less than the third threshold, the management server deletes at least one first attribute information from the operation condition to obtain the updated operation condition, the second threshold is greater than the first threshold, and the third threshold is greater than the second threshold; when the average number of abnormalities is not less than the third threshold, the management server clears the first attribute information in the operation condition to obtain the updated operation condition.
[0329] In some embodiments, the operating condition includes second attribute information, and the second attribute information indicates attribute information of a client that is not allowed to operate the target data. Then, when the operating information includes target attribute information corresponding to a client in which the target data is abnormal, the management server determines the target attribute information as the second attribute information, adds the second attribute information to the operating condition, and obtains an updated operating condition.
[0330] In some embodiments, the management server deletes any second attribute information whose survival time reaches a third time period from the current operating conditions, where the survival time refers to the time period that the second attribute information exists in the operating conditions.
[0331] 705. The business server obtains updated operating conditions in response to the second client's operating request for the target data.
[0332] 706. When the second client meets the updated operating condition, the service server sends the target data to the second client.
[0333] Among them, the above steps 701-706 and Figure 5 The same is true for steps 501-506 in .
[0334] In the disclosed embodiment, the running conditions are used to control which clients are allowed to run the target data, and the update conditions are used to control whether the running conditions are updated. After the target data is sent to the client, the running information of the target data in the client is automatically obtained, and whether the running conditions need to be updated is determined based on whether the running information meets the update conditions. In this way, the clients allowed to run the target data are adaptively adjusted based on the running status of the target data, without consuming manpower, and the reliability of managing the target data can be improved.
[0335] In the above Figure 2 or Figure 3 The data management system shown and Figure 5On the basis of the data management method shown, the business processing server, conditional storage server, conditional management server and operation management server in the data management system manage the operation scope of the target data. The specific process is detailed in the following embodiment.
[0336] Figure 8 is a flowchart showing a method of managing target data according to an exemplary embodiment. Figure 8 , the method is applied in a data management system, the method comprising the following steps:
[0337] 801. The business processing server responds to a first client's operation request for target data, obtains a target data identifier carried in the operation request, and sends a conditional query request carrying the target data identifier to a conditional storage server.
[0338] A communication connection is established between the business processing server and multiple clients. The business processing server can provide services to the multiple clients. The first client is any client among the multiple clients. Figure 5 The operation request, target data, and target data identifier in the embodiment are the same and will not be repeated here.
[0339] The business processing server is used to send target data to the client. If the business processing server does not store the operating conditions corresponding to each data, the business processing server responds to the operating request for the target data and sends a condition query request carrying the target data identifier to the condition storage server. The condition query request is used to query the operating conditions corresponding to the target data identifier, that is, to query the operating conditions corresponding to the target data identifier.
[0340] 802. The condition storage server queries the operating condition corresponding to the target data identifier in response to the condition query request, and sends the operating condition to the business processing server.
[0341] The condition storage server stores the correspondence between the data identifier of any data and the operating condition of the data. The condition storage server responds to the condition query request, obtains the target data identifier carried in the condition query request, queries the operating condition corresponding to the target data identifier, and returns the queried operating condition to the business processing server. The operating condition is the condition that the client needs to meet to allow the target data to be run.
[0342] 803. The business processing server receives the operating conditions.
[0343] 804. When the first client meets the operating condition, the business processing server sends the target data to the first client.
[0344] This step 804 is similar to the above Figure 5 The same is true for step 502 in the above, the only difference is the execution entity, which will not be repeated here.
[0345] It should be noted that the above steps 801-804 only take the first client among multiple clients as an example to illustrate the process of sending target data to the first client, wherein any client among the multiple clients can send a run request to the business processing server, so that the business processing server returns the target data to the client when the client meets the run conditions. Therefore, by executing the above steps 801-804 at least once, it is achieved to send the target data to at least one client that meets the run conditions.
[0346] 805. The condition management server sends an information query request for target data to the operation management server.
[0347] The operation management server is used to manage the operation information of the target data, and the operation information indicates the operation status of the target data in at least one client, that is, the operation management server can detect the operation status of the target data in at least one client.
[0348] The condition management server is used to determine whether to update the operating conditions of the target data according to the operating information of the target data, so the condition management server sends an information query request for the target data to the operation management server, and the information query request is used to query the operating information of the target data. In some embodiments, the information query request carries a target data identifier, and the target data identifier indicates the target data.
[0349] 806. The operation management server queries the operation information of the target data in response to the information query request, and sends the operation information to the condition management server.
[0350] In some embodiments, the operation information includes the average number of exceptions, and the information query request is a first query request, and the first query request is used to query the average number of exceptions of the target data. Then, the operation management server responds to the first query request and queries at least one exception notification received within a first time period before the current time point, and the exception notification carries a data identifier, and the exception notification indicates that an exception occurs in the data indicated by the data identifier. The operation management server determines the number of exception notifications carrying a target data identifier in at least one exception notification, and the target data identifier indicates the target data; and determines the average number of exceptions based on the first time period and the number.
[0351] In some embodiments, there are multiple exception types corresponding to the exception notifications, and the first query request carries a target exception type. The operation management server obtains the target exception type carried in the first query request, and in at least one exception notification, determines the number of exception notifications that carry the target data identifier and belong to the target exception type.
[0352] In some embodiments, the operation information includes target attribute information corresponding to the client where the target data has an exception, and the information query request is a second query request, and the second query request is used to query the target attribute information corresponding to the client where the target data has an exception. Then, in response to the first query request, the operation management server queries at least one exception notification received within the second time period before the current time point, the exception notification carries a data identifier and attribute information, and the exception notification indicates that the data indicated by the data identifier has an exception in the client corresponding to the attribute information; in at least one exception notification, the target attribute information in the exception notification carrying the target data identifier is obtained, and the target data identifier indicates the target data.
[0353] The process of determining the average number of abnormalities in step 806 is the same as the process of determining the operation information in step 503 above, and the only difference is the execution subject, which will not be repeated here.
[0354] 807. The condition management server receives the operation information, and when the operation information satisfies the update condition, updates the locally stored operation condition to obtain the updated operation condition.
[0355] The process of updating the operating conditions in step 807 is the same as the process of updating the operating conditions in step 504 above, the difference lies in the execution subject, which will not be repeated here.
[0356] 808. The condition management server sends an update notification carrying the updated operating condition to the condition storage server.
[0357] Since the business processing server needs to query the operating conditions from the condition storage server, the condition management server will send an update notification carrying the updated operating conditions to the condition storage server after obtaining the updated operating conditions. The update notification is used to notify the condition storage server to replace the operating conditions with the updated operating conditions. In some embodiments, the update notification carries the target data identifier and the updated operating conditions.
[0358] 809. In response to the update notification, the condition storage server replaces the locally stored operating condition with the updated operating condition.
[0359] In response to the update notification, the condition storage server obtains the updated operating condition carried in the update notification, and replaces the operating condition locally stored in the condition storage server with the updated operating condition.
[0360] In some embodiments, the update notification also carries a target data identifier, and the condition storage server queries the operating condition corresponding to the target data identifier among multiple operating conditions stored locally, and replaces the queried operating condition with the updated operating condition.
[0361] The method provided by the embodiment of the present disclosure uses operating conditions to control which clients are allowed to run target data, and uses update conditions to control whether to update the operating conditions. After the target data is sent to the client, the operating information of the target data in the client is automatically obtained, and whether the operating conditions need to be updated is determined based on whether the operating information meets the update conditions. In this way, the clients allowed to run the target data are adaptively adjusted based on the operating conditions of the target data, without consuming manpower, and the reliability of managing the target data can be improved.
[0362] Fig. 9 is a flowchart showing a method of sending target data according to an exemplary embodiment. Fig. 9 Taking updating the operating conditions to narrow the operating range of the target data as an example, the method includes the following steps:
[0363] 1. When the client user needs to use a new function, the client requests the target data from the business processing server. The business processing server sends a conditional query request carrying the target data identifier to the conditional storage server. The conditional storage server returns the operating conditions corresponding to the target data to the business processing server. The business processing server determines whether the client meets the operating conditions. If so, it returns the target data and the target data identifier to the client. If not, the process ends.
[0364] 2. The client runs the target data. When an exception occurs in the target data, the client reports an exception notification to the operation management server. The exception notification includes an exception stack and a target data identifier of the target data.
[0365] 3. The operation management server receives an exception notification carrying a data identifier sent by at least one client, and counts the number of times the statistical exception occurs according to the data identifier in the exception notification.
[0366] The operation management server determines multiple exception notifications corresponding to each data identifier based on the data identifier as a dimension, and determines the number of exceptions that occur in the data indicated by each data identifier according to the number of exception notifications corresponding to the data identifier.
[0367] In the case where the exception notification corresponds to multiple exception types, the operation management server can also determine the multiple exception notifications corresponding to each exception type, and the number of exception notifications corresponding to each data identifier in the exception notification corresponding to each exception type. Therefore, the operation management server can manage the multiple exception notifications received based on the data identifier as a dimension or the exception type as a dimension.
[0368] 4. The conditional broadcast module in the conditional management server periodically queries the operation management server for the number of abnormalities of the target data. The operation management server returns the target data identifier of the target data and the number of abnormalities of the target data within a unit time, that is, the average number of abnormalities.
[0369] The condition management server may customize the time for periodically querying the number of exceptions, for example, the condition management server queries the number of exceptions once every 1 minute.
[0370] 5. The condition broadcast module in the condition management server queries the condition management module in the condition management server for the update condition corresponding to the target data identifier. The condition management module returns the update condition corresponding to the target data identifier to the condition broadcast module, and the update condition is used to update the operating condition of the target data. The condition broadcast module determines whether the average number of abnormalities of the target data hits the update condition. If not, the process ends.
[0371] 6. If the average number of abnormalities hits the update condition, the condition broadcast module sends the target data identifier and the hit update condition identifier to the condition management module. The condition management module determines the new operating condition corresponding to the target data based on the target data identifier and the update condition identifier, and returns the new operating condition. The condition broadcast module receives the new operating condition and notifies the condition storage server to update the operating condition corresponding to the target data. The condition storage server updates the locally stored operating condition and writes the new operating condition.
[0372] In the disclosed embodiment, the hit reduction strategy is taken as an example, that is, when the average number of abnormalities is large, the operating conditions are updated so that the number of clients allowed to run the target data determined by the updated operating conditions is reduced, thereby narrowing the operating range of the target data.
[0373] For example, the running conditions include a device model, which refers to the model of the device where the client that is allowed to run the target data is located. When the average number of exceptions is greater than a second threshold, at least one device model is deleted from the running conditions, so that the number of clients that hit the running conditions is reduced by 10%.
[0374] For example, the running condition includes a user account, which refers to a user account that allows the client to log in to run the target data. For example, the user account in the running condition refers to a user account whose last three digits are between 0 and 300. If the average number of abnormal times is greater than the second threshold, some user accounts are deleted from the running condition, so that the number of clients that hit the running condition is reduced by 10%.
[0375] It should be noted that this embodiment only updates the operating conditions based on the average number of exceptions, and controls the clients that hit the operating conditions from a macro perspective. In other embodiments, it is also possible to control the clients that fail to hit the operating conditions from a micro perspective, such as adding the attribute information of the client whose target data has an exception to the "blacklist" corresponding to the target data, so that the client no longer hits the new operating conditions. For example, if the attribute information is a device identifier, then the device identifier of the device where the client is located is added to the "blacklist", or if the attribute information is a user identifier, then the user identifier of the client logged in is added to the "blacklist".
[0376] 7. When the client user uses the new function again, the client requests the target data from the business processing server again. The business processing server sends a conditional query request carrying the target data identifier to the conditional storage server. The conditional storage server returns the new operating conditions corresponding to the target data to the business processing server.
[0377] 8. The business processing server determines whether the client meets the new operating conditions. If the client no longer meets the new operating conditions, the business processing server will no longer send the target data.
[0378] Since the operating range determined by the operating condition is reduced, that is, the probability of hitting the operating condition is reduced, the client no longer hits the new operating condition. Or the attribute information of the client has been added to the "blacklist", so the client no longer hits the new operating condition. The client will not receive the target data and continue to execute the original logic, thereby avoiding abnormalities in the target data.
[0379] Fig.10 is a flowchart of another method of sending target data according to an exemplary embodiment. Fig.10 Taking updating the operating conditions to expand the operating range of the target data as an example, the method includes the following steps:
[0380] 1. When the client user needs to use a new function, the client requests the target data from the business processing server. The business processing server sends a conditional query request carrying the target data identifier to the conditional storage server. The conditional storage server returns the operating conditions corresponding to the target data to the business processing server. The business processing server determines whether the client meets the operating conditions. If so, it returns the target data and the target data identifier to the client. If not, the process ends.
[0381] In the disclosed embodiment, the client receives the target data and runs the target data normally, so the client does not report an abnormal notification to the operation management server.
[0382] 2. The operation management server receives an exception notification carrying a data identifier sent by at least one client, and counts the number of times the statistical exception occurs according to the data identifier in the exception notification.
[0383] The operation management server determines multiple exception notifications corresponding to each data identifier based on the data identifier as a dimension, and determines the number of exceptions that occur in the data indicated by each data identifier according to the number of exception notifications corresponding to the data identifier.
[0384] In the case where the exception notification corresponds to multiple exception types, the operation management server can also determine the multiple exception notifications corresponding to each exception type, and the number of exception notifications corresponding to each data identifier in the exception notification corresponding to each exception type. Therefore, the operation management server can manage the multiple exception notifications received based on the data identifier as a dimension or the exception type as a dimension.
[0385] 3. The conditional broadcast module in the conditional management server periodically queries the operation management server for the number of abnormalities of the target data. The operation management server returns the target data identifier of the target data and the number of abnormalities of the target data within a unit time, that is, the average number of abnormalities.
[0386] The condition management server may customize the time for periodically querying the number of exceptions, for example, the condition management server queries the number of exceptions once every 1 minute.
[0387] 4. The condition broadcast module in the condition management server queries the condition management module in the condition management server for the update condition corresponding to the target data identifier, and the condition management module returns the update condition corresponding to the target data identifier to the condition broadcast module. The condition broadcast module determines whether the average number of abnormalities of the target data hits the update condition. If not, the process ends.
[0388] 5. If the average number of abnormalities hits the update condition, the condition broadcast module sends the target data identifier and the hit update condition identifier to the condition management module. The condition management module determines the new operating condition corresponding to the target data based on the target data identifier and the update condition identifier, and returns the new operating condition. The condition broadcast module receives the new operating condition and notifies the condition storage server to update the operating condition corresponding to the target data. The condition storage server updates the locally stored operating condition and writes the new operating condition.
[0389] In the disclosed embodiment, the hit increment strategy is taken as an example, that is, when the average number of exceptions is small, the operating conditions are updated so that the number of clients allowed to run the target data determined by the updated operating conditions is increased, thereby expanding the operating range of the target data.
[0390] For example, the operating conditions include a device model, which refers to the model of the device where the client that is allowed to run the target data is located. When the average number of exceptions is less than a third threshold, at least one device model is added to the operating conditions so that the number of clients that meet the operating conditions increases by 10%.
[0391] For example, the running condition includes a user account, which refers to a user account that allows the client to log in to run the target data. For example, the user account in the running condition refers to a user account whose last three digits are between 0 and 300. If the average number of abnormal times is less than the third threshold, a part of the user accounts is added to the running condition, so that the number of clients that hit the running condition increases by 10%.
[0392] 6. When users of other clients need to use new functions, other clients request target data from the business processing server. The business processing server sends a conditional query request carrying the target data identifier to the conditional storage server. The conditional storage server returns the new operating conditions corresponding to the target data to the business processing server.
[0393] 7. The business processing server determines whether other clients meet the new operating conditions. If other clients meet the new operating conditions, the business processing server returns the target data and the target data identifier to the other clients.
[0394] Since the operating range determined by the operating condition is expanded, that is, the probability of hitting the operating condition is increased, other clients hit the new operating condition, so other clients can also run the target data, allowing more users to use the new function.
[0395] Fig.11 is a block diagram of a data management device according to an exemplary embodiment. Fig.11The device includes a data sending unit 1101, an information acquiring unit 1102 and a condition updating unit 1103.
[0396] The data sending unit 1101 is configured to send target data to at least one client that meets the running condition, where the running condition is a condition that needs to be met by the client to allow the running of the target data, the target data is used to implement a newly added function in the client, and the at least one client is used to run the target data;
[0397] An information acquisition unit 1102 is configured to determine operation information of the target data, where the operation information indicates the operation status of the target data in at least one client;
[0398] The condition updating unit 1103 is configured to update the operating condition to obtain the updated operating condition when the operating information meets the update condition. The update condition is a condition that the operating information needs to meet to trigger the update of the operating condition.
[0399] The device provided by the embodiment of the present disclosure uses operating conditions to control which clients are allowed to run target data, and uses update conditions to control whether to update the operating conditions. After the target data is sent to the client, the operating information of the target data in the client is automatically obtained, and whether the operating conditions need to be updated is determined based on whether the operating information meets the update conditions. In this way, the client that is allowed to run the target data is adaptively adjusted based on the operating status of the target data, without consuming manpower, and the reliability of managing the target data can be improved.
[0400] In one possible implementation, see Fig.12 , the data sending unit 1101 includes:
[0401] The condition acquisition subunit 1111 is configured to execute and obtain the operation condition in response to the operation request of the first client for the target data, where the first client is any client;
[0402] The data sending subunit 1121 is configured to send target data to the first client when the first client meets the operating conditions.
[0403] In one possible implementation, see Fig.12 , the condition acquisition subunit 1111 is configured to execute:
[0404] In response to the operation request, obtaining a target data identifier carried in the operation request, where the target data identifier indicates the target data;
[0405] Query the operating conditions corresponding to the target data identifier.
[0406] In one possible implementation, see Fig.12The running condition includes first attribute information, the first attribute information indicates attribute information of a client that is allowed to run the target data, and the data sending subunit 1121 is configured to execute:
[0407] Obtaining attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client;
[0408] When the attribute information belongs to the first attribute information, the target data is sent to the first client.
[0409] In one possible implementation, see Fig.12 The data sending subunit 1121 is configured to perform at least one of the following:
[0410] The attribute information includes device information, the first attribute information includes first device information, and when the device information matches the first device information, the target data is sent to the first client;
[0411] The attribute information includes state information, the first attribute information includes first state information, the first state information indicates a login state, and when the state information is the first state information, the target data is sent to the first client;
[0412] The attribute information includes a user account, the first attribute information includes a first user account, and when the user account belongs to the first user account, the target data is sent to the first client.
[0413] In one possible implementation, see Fig.12 The running condition includes second attribute information, the second attribute information indicates attribute information of a client that is not allowed to run the target data, and the data sending subunit 1121 is configured to execute:
[0414] Obtaining attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client;
[0415] When the attribute information does not belong to the second attribute information, the target data is sent to the first client.
[0416] In some embodiments, the data sending subunit 1121 is configured to perform at least one of the following:
[0417] The attribute information includes device information, the second attribute information includes second device information, and when the device information does not match the second device information, the target data is sent to the first client;
[0418] The attribute information includes state information, the second attribute information includes second state information, the second state information indicates a non-logged-in state, and when the state information is not the second state information, the target data is sent to the first client;
[0419] The attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
[0420] In one possible implementation, see Fig.12 , the data sending unit 1101 includes:
[0421] The data and identification sending subunit 1131 is configured to send target data and target data identification to at least one client, where the target data identification indicates the target data, and at least one client is used to return an exception notification carrying the target data identification when an exception occurs in the target data.
[0422] In one possible implementation, see Fig.12 The operation information includes the average number of abnormalities of the target data, which refers to the number of abnormalities of the target data within a unit time. The condition updating unit 1103 includes:
[0423] The condition updating subunit 1113 is configured to update the operating condition to obtain the updated operating condition when the average number of abnormalities meets the update condition, where the update condition is the condition that the average number of abnormalities needs to meet to trigger the update of the operating condition.
[0424] In one possible implementation, see Fig.12 The running condition includes first attribute information, where the first attribute information indicates attribute information of a client that is allowed to run the target data; the condition updating subunit 1113 is configured to execute:
[0425] When the average number of abnormalities is less than the first threshold, adding new first attribute information to the operating condition to obtain an updated operating condition;
[0426] When the average number of abnormal times is greater than the second threshold and less than the third threshold, at least one first attribute information is deleted from the operating condition to obtain an updated operating condition, where the second threshold is greater than the first threshold and the third threshold is greater than the second threshold;
[0427] When the average number of abnormalities is not less than the third threshold, the first attribute information in the operating condition is cleared to obtain an updated operating condition.
[0428] In one possible implementation, see Fig.12 The information acquisition unit 1102 includes:
[0429] The notification query subunit 1112 is configured to query at least one abnormal notification received within a first period before the current time point, the abnormal notification carrying a data identifier, and the abnormal notification indicating that an abnormality occurs in the data indicated by the data identifier;
[0430] The number determination subunit 1122 is configured to be executed in at least one abnormal notification to determine the number of abnormal notifications carrying a target data identifier, where the target data identifier indicates the target data;
[0431] The times determination subunit 1132 is configured to determine the average times of abnormalities according to the first duration and the number.
[0432] In one possible implementation, see Fig.12 There are multiple exception types corresponding to the exception notification, and the number determination subunit 1122 is configured to execute in at least one exception notification, and determine the number of exception notifications that carry the target data identifier and belong to the target exception type.
[0433] In one possible implementation, see Fig.12 The running condition includes second attribute information, and the second attribute information indicates attribute information of a client that is not allowed to run the target data; the condition updating unit 1103 includes:
[0434] The condition updating subunit 1113 is configured to determine the target attribute information as the second attribute information and add the second attribute information to the operating condition to obtain the updated operating condition when the operating information includes the target attribute information corresponding to the client where the target data has an exception.
[0435] In one possible implementation, see Fig.12 The information acquisition unit 1102 includes:
[0436] The notification query subunit 1112 is configured to query at least one abnormal notification received within a second time period before the current time point, the abnormal notification carrying a data identifier and attribute information, and the abnormal notification indicating that the data indicated by the data identifier has an abnormality in the client corresponding to the attribute information;
[0437] The information acquisition subunit 1142 is configured to execute, in at least one abnormal notification, acquiring target attribute information in the abnormal notification carrying a target data identifier, where the target data identifier indicates the target data.
[0438] In one possible implementation, see Fig.12 The condition updating subunit 1113 is further configured to delete any second attribute information whose survival time reaches a third time from the current operating condition, where the survival time refers to the time duration that the second attribute information exists in the operating condition.
[0439] In one possible implementation, see Fig.12 The data sending unit 1101 is further configured to execute:
[0440] In response to a second client's request for operation of the target data, obtaining an updated operation condition, the second client being any client;
[0441] When the second client meets the updated operating condition, the target data is sent to the second client.
[0442] Regarding the device in the above embodiment, the specific manner in which each unit performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.
[0443] An embodiment of the present disclosure provides an electronic device, which includes: a processor, and a memory for storing instructions executable by the processor, wherein the processor is configured to execute the instructions to implement the above-mentioned data management method.
[0444] In some embodiments, the electronic device includes a terminal. Fig.13 1 is a block diagram of a terminal 1300 according to an exemplary embodiment. The terminal 1300 may be a portable mobile terminal, such as a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 player (Moving Picture Experts Group Audio Layer IV), a laptop computer or a desktop computer. The terminal 1300 may also be referred to as a user device, a portable terminal, a laptop terminal, a desktop terminal or other names.
[0445] The terminal 1300 includes a processor 1301 and a memory 1302 .
[0446] The processor 1301 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 1301 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 1301 may also include a main processor and a coprocessor, the main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. The memory 1302 may include one or more computer-readable storage media, which may be non-transitory. The memory 1302 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 1302 is used to store at least one program code, which is used to be executed by the processor 1301 to implement the data management method provided in the method embodiment of the present disclosure.
[0447] In some embodiments, the terminal 1300 may also optionally include: a peripheral device interface 1303 and at least one peripheral device. The processor 1301, the memory 1302 and the peripheral device interface 1303 may be connected via a bus or a signal line. Each peripheral device may be connected to the peripheral device interface 1303 via a bus, a signal line or a circuit board. Specifically, the peripheral device includes: a radio frequency circuit 1304.
[0448] The peripheral device interface 1303 may be used to connect at least one peripheral device related to I / O (Input / Output) to the processor 1301 and the memory 1302. In some embodiments, the processor 1301, the memory 1302, and the peripheral device interface 1303 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1301, the memory 1302, and the peripheral device interface 1303 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.
[0449] The radio frequency circuit 1304 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 1304 communicates with the communication network and other communication devices through electromagnetic signals. The radio frequency circuit 1304 converts the electrical signal into an electromagnetic signal for transmission, or converts the received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1304 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, and the like. The radio frequency circuit 1304 can communicate with other terminals through at least one wireless communication protocol. The wireless communication protocol includes but is not limited to: the World Wide Web, a metropolitan area network, an intranet, various generations of mobile communication networks (2G, 3G, 4G and 5G), a wireless local area network and / or a WiFi (Wireless Fidelity) network. In some embodiments, the radio frequency circuit 1304 may also include circuits related to NFC (Near Field Communication), which is not limited in the present disclosure.
[0450] Those skilled in the art will understand that Fig.13 The structure shown in the figure does not constitute a limitation on the terminal 1300, and the terminal 1300 may include more or less components than those shown in the figure, or combine some components, or adopt a different component arrangement.
[0451] In some embodiments, the electronic device includes a server. Fig.14 This is a schematic diagram of the structure of a server according to an exemplary embodiment. The server 1400 may have relatively large differences due to different configurations or performances, and may include one or more processors (Central Processing Units, CPU) 1401 and one or more memories 1402, wherein the memory 1402 stores at least one computer program, and the at least one computer program is loaded and executed by the processor 1401 to implement the methods provided by the above-mentioned various method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input and output interface for input and output, and the server may also include other components for implementing device functions, which will not be described in detail here.
[0452] In an exemplary embodiment, a computer-readable storage medium is also provided, and when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can perform the steps in the above data management method. For example, the computer-readable storage medium can be a ROM (Read Only Memory), a RAM (Random Access Memory), a CD-ROM (Compact Disc Read-Only Memory), a magnetic tape, a floppy disk, an optical data storage device, etc.
[0453] In an exemplary embodiment, a computer program product is also provided, including a computer program, and when the computer program is executed by a processor of an electronic device, the steps in the above data management method are implemented.
[0454] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the disclosure herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0455] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A data management method, characterized in that: The data management method comprises: Sending target data to at least one client satisfying an operating condition, wherein the operating condition is a condition that needs to be satisfied by the client to allow the target data to be run, the target data is used to implement a newly added function in the client, and the at least one client is used to run the target data; the operating condition includes first attribute information, and the first attribute information indicates attribute information of the client that is allowed to run the target data; Determine operation information of the target data, wherein the operation information indicates the operation status of the target data in the at least one client; the operation information includes an average number of abnormalities of the target data, wherein the average number of abnormalities refers to the number of abnormalities of the target data within a unit time; When the average number of abnormalities is less than a first threshold, adding new first attribute information to the operating condition to obtain an updated operating condition; In a case where the average number of abnormal times is greater than a second threshold and less than a third threshold, deleting at least one first attribute information in the operating condition to obtain the updated operating condition, the second threshold is greater than the first threshold, and the third threshold is greater than the second threshold; When the average number of abnormalities is not less than the third threshold, the first attribute information in the operating condition is cleared to obtain the updated operating condition.
2. The data management method according to claim 1, characterized in that: The sending of target data to at least one client meeting the operating condition comprises: In response to a first client's request for running the target data, acquiring the running condition, the first client being any client; When the first client satisfies the operating condition, the target data is sent to the first client.
3. The data management method according to claim 2, characterized in that: The obtaining the operating condition in response to the first client's operating request for the target data includes: In response to the operation request, obtaining a target data identifier carried in the operation request, wherein the target data identifier indicates the target data; The operating condition corresponding to the target data identifier is queried.
4. The data management method according to claim 2, characterized in that: The sending the target data to the first client when the first client satisfies the operating condition includes: Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client; In a case where the attribute information belongs to the first attribute information, the target data is sent to the first client.
5. The data management method according to claim 4, characterized in that: When the attribute information belongs to the first attribute information, sending the target data to the first client includes at least one of the following: The attribute information includes the device information, the first attribute information includes first device information, and when the device information matches the first device information, the target data is sent to the first client; The attribute information includes the state information, the first attribute information includes first state information, the first state information indicates a login state, and when the state information is the first state information, the target data is sent to the first client; The attribute information includes a user account, the first attribute information includes a first user account, and when the user account belongs to the first user account, the target data is sent to the first client.
6. The method according to claim 2, characterized in that The operation condition further includes second attribute information, where the second attribute information indicates attribute information of a client that is not allowed to operate the target data. When the first client satisfies the operation condition, sending the target data to the first client includes: Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client; In a case where the attribute information does not belong to the second attribute information, the target data is sent to the first client.
7. The method according to claim 6, characterized in that When the attribute information does not belong to the second attribute information, sending the target data to the first client includes at least one of the following: The attribute information includes the device information, the second attribute information includes second device information, and when the device information does not match the second device information, sending the target data to the first client; The attribute information includes the state information, the second attribute information includes second state information, the second state information indicates a non-logged-in state, and when the state information is not the second state information, sending the target data to the first client; The attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
8. The data management method according to claim 1, characterized in that: The sending of target data to at least one client meeting the operating condition comprises: The target data and the target data identifier are sent to the at least one client, where the target data identifier indicates the target data, and the at least one client is used to return an exception notification carrying the target data identifier when an exception occurs to the target data.
9. The data management method according to claim 1, characterized in that: The determining the operation information of the target data includes: Querying at least one exception notification received within a first period of time before a current time point, the exception notification carrying a data identifier, the exception notification indicating that an exception occurs in the data indicated by the data identifier; Determining, in the at least one exception notification, the number of exception notifications carrying a target data identifier, wherein the target data identifier indicates the target data; The average number of abnormal times is determined according to the first duration and the number.
10. The data management method according to claim 9, characterized in that: The abnormal notification corresponds to multiple abnormal types, and determining the number of abnormal notifications carrying the target data identifier in the at least one abnormal notification includes: Among the at least one exception notification, the number of exception notifications that carry the target data identifier and belong to the target exception type is determined.
11. The data management method according to claim 1, characterized in that: The running condition further includes second attribute information, wherein the second attribute information indicates attribute information of a client that is not allowed to run the target data; and the method further includes: In the case where the operating information includes target attribute information corresponding to the client where the target data has an exception, the target attribute information is determined as the second attribute information, and the second attribute information is added to the operating condition to obtain the updated operating condition.
12. The data management method according to claim 11, characterized in that: The determining the operation information of the target data includes: Querying at least one exception notification received within a second time period before the current time point, the exception notification carrying a data identifier and attribute information, the exception notification indicating that an exception occurs in the data indicated by the data identifier in the client corresponding to the attribute information; In the at least one exception notification, the target attribute information in the exception notification carrying a target data identifier is obtained, and the target data identifier indicates the target data.
13. The data management method according to claim 11, characterized in that: After adding the second attribute information to the operating condition to obtain the updated operating condition, the data management method further includes: Any second attribute information whose survival time reaches a third time period is deleted from the current operating condition, where the survival time refers to the time period during which the second attribute information exists in the operating condition.
14. The data management method according to any one of claims 1 to 13, characterized in that: The data management method further includes: In response to a request from a second client for running the target data, acquiring the updated running condition, the second client being any client; When the second client satisfies the updated operating condition, the target data is sent to the second client.
15. A data management system, characterized in that: The data management system includes a business server and a management server; The business server is used to send target data to at least one client that meets the operating condition, the operating condition being a condition that needs to be met by the client that is allowed to run the target data, the target data is used to implement a newly added function in the client, and the at least one client is used to run the target data; the operating condition includes first attribute information, and the first attribute information represents attribute information of the client that is allowed to run the target data; The management server is used to determine the operation information of the target data, wherein the operation information indicates the operation status of the target data in the at least one client; the operation information includes the average number of abnormalities of the target data, wherein the average number of abnormalities refers to the number of abnormalities of the target data within a unit time; The management server is further configured to add new first attribute information to the operating condition to obtain an updated operating condition when the average number of abnormal times is less than a first threshold; In a case where the average number of abnormal times is greater than a second threshold and less than a third threshold, deleting at least one first attribute information in the operating condition to obtain the updated operating condition, the second threshold is greater than the first threshold, and the third threshold is greater than the second threshold; When the average number of abnormalities is not less than the third threshold, the first attribute information in the operating condition is cleared to obtain the updated operating condition.
16. The data management system according to claim 15, characterized in that: The business server is used for: In response to a first client's request for running the target data, acquiring the running condition, the first client being any client; When the first client satisfies the operating condition, the target data is sent to the first client.
17. The data management system according to claim 16, characterized in that: The business server includes a business processing server and a conditional storage server; The business processing server is used to respond to the operation request, obtain the target data identifier carried in the operation request, and send a conditional query request carrying the target data identifier to the conditional storage server, where the target data identifier indicates the target data; The condition storage server is used to query the operating condition corresponding to the target data identifier in response to the condition query request, and send the operating condition to the business processing server; The business processing server is used to receive the operating condition.
18. The data management system according to claim 17, characterized in that: The management server is configured to update the locally stored operating condition, obtain the updated operating condition, and send an update notification carrying the updated operating condition to the condition storage server when the operating information meets the update condition; The condition storage server is configured to replace the locally stored operating condition with the updated operating condition in response to the update notification.
19. The data management system according to claim 16, characterized in that: The business server is used for: Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client; In a case where the attribute information belongs to the first attribute information, the target data is sent to the first client.
20. The data management system according to claim 19, characterized in that: The business server is used to perform at least one of the following steps: The attribute information includes the device information, the first attribute information includes first device information, and when the device information matches the first device information, the target data is sent to the first client; The attribute information includes the state information, the first attribute information includes first state information, the first state information indicates a login state, and when the state information is the first state information, the target data is sent to the first client; The attribute information includes a user account, the first attribute information includes a first user account, and when the user account belongs to the first user account, the target data is sent to the first client.
21. The data management system according to claim 16, characterized in that: The operation condition further includes second attribute information, wherein the second attribute information indicates attribute information of a client that is not allowed to operate the target data, and the business server is used to: Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client; In a case where the attribute information does not belong to the second attribute information, the target data is sent to the first client.
22. The data management system according to claim 21, characterized in that: The business server is used to perform at least one of the following steps: The attribute information includes the device information, the second attribute information includes second device information, and when the device information does not match the second device information, sending the target data to the first client; The attribute information includes the state information, the second attribute information includes second state information, the second state information indicates a non-logged-in state, and when the state information is not the second state information, sending the target data to the first client; The attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
23. The data management system according to claim 15, characterized in that: The business server is used to send the target data and the target data identifier to the at least one client, the target data identifier indicates the target data, and the at least one client is used to return an exception notification carrying the target data identifier when an exception occurs to the target data.
24. The data management system according to claim 15, characterized in that: The management server includes a condition management server and an operation management server; The condition management server is used to send a first query request for the target data to the operation management server; The operation management server is used to query the average number of abnormalities of the target data in response to the first query request, and send the average number of abnormalities to the condition management server; The condition management server is used to receive the average number of abnormalities, and update the operating condition when the average number of abnormalities meets the update condition to obtain the updated operating condition.
25. The data management system according to claim 24, characterized in that: The operation management server is used to: In response to the first query request, query at least one exception notification received within a first period before the current time point, the exception notification carrying a data identifier, and the exception notification indicating that an exception occurs in the data indicated by the data identifier; Determining, in the at least one exception notification, the number of exception notifications carrying a target data identifier, wherein the target data identifier indicates the target data; The average number of abnormal times is determined according to the first duration and the number.
26. The data management system according to claim 25, characterized in that: The abnormal notification corresponds to multiple abnormal types, and the operation management server is used to: Obtaining the target exception type carried in the first query request; Among the at least one exception notification, the number of exception notifications that carry the target data identifier and belong to the target exception type is determined.
27. The data management system according to claim 15, characterized in that: The operation condition further includes second attribute information, wherein the second attribute information indicates attribute information of a client that is not allowed to operate the target data; The management server is used to determine the target attribute information as the second attribute information when the operating information includes the target attribute information corresponding to the client where the target data has an abnormality, and add the second attribute information to the operating condition to obtain the updated operating condition.
28. The data management system according to claim 27, characterized in that: The management server includes a condition management server and an operation management server; The condition management server is used to send a second query request for the target data to the operation management server; The operation management server is used to query the target attribute information corresponding to the client where the target data is abnormal in response to the second query request, and send the target attribute information to the condition management server; The condition management server is used to receive the target attribute information, determine the target attribute information as the second attribute information, add the second attribute information to the operating condition, and obtain the updated operating condition.
29. The data management system according to claim 28, characterized in that: The operation management server is used to: In response to the second query request, query at least one exception notification received within a second time period before the current time point, the exception notification carrying a data identifier and attribute information, the exception notification indicating that the data indicated by the data identifier has an exception in a client corresponding to the attribute information; In the at least one exception notification, the target attribute information in the exception notification carrying a target data identifier is obtained, and the target data identifier indicates the target data.
30. The data management system according to claim 27, characterized in that: The management server is further used to delete any second attribute information whose survival time reaches a third time period from the current operating conditions, where the survival time refers to the time period during which the second attribute information exists in the operating conditions.
31. The data management system according to any one of claims 15 to 30, characterized in that: The business server is also used for: In response to a request from a second client for running the target data, acquiring the updated running condition, the second client being any client; When the second client satisfies the updated operating condition, the target data is sent to the second client.
32. A data management device, characterized in that: The data management device comprises: a data sending unit, configured to send target data to at least one client satisfying an operating condition, wherein the operating condition is a condition that needs to be satisfied by a client that is allowed to run the target data, the target data is used to implement a newly added function in the client, and the at least one client is used to run the target data; the operating condition includes first attribute information, and the first attribute information indicates attribute information of the client that is allowed to run the target data; an information acquisition unit, configured to determine operation information of the target data, wherein the operation information indicates operation status of the target data in the at least one client; the operation information includes an average number of abnormalities of the target data, wherein the average number of abnormalities refers to the number of abnormalities of the target data within a unit time; The condition updating unit is configured to execute, when the average number of abnormalities is less than a first threshold, adding new first attribute information to the operating condition to obtain an updated operating condition; when the average number of abnormalities is greater than a second threshold and less than a third threshold, deleting at least one first attribute information from the operating condition to obtain the updated operating condition, the second threshold is greater than the first threshold, and the third threshold is greater than the second threshold; when the average number of abnormalities is not less than the third threshold, clearing the first attribute information in the operating condition to obtain the updated operating condition.
33. The data management device according to claim 32, characterized in that: The data sending unit comprises: a condition acquisition subunit, configured to execute and obtain the operation condition in response to an operation request of the first client for the target data, wherein the first client is any client; The data sending subunit is configured to send the target data to the first client when the first client meets the operating condition.
34. The data management device according to claim 33, characterized in that: The condition acquisition subunit is configured to execute: In response to the operation request, obtaining a target data identifier carried in the operation request, wherein the target data identifier indicates the target data; The operating condition corresponding to the target data identifier is queried.
35. The data management device according to claim 33, characterized in that: The data sending subunit is configured to execute: Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client; In a case where the attribute information belongs to the first attribute information, the target data is sent to the first client.
36. The data management device according to claim 35, characterized in that: The data sending subunit is configured to perform at least one of the following: The attribute information includes the device information, the first attribute information includes first device information, and when the device information matches the first device information, the target data is sent to the first client; The attribute information includes the state information, the first attribute information includes first state information, the first state information indicates a login state, and when the state information is the first state information, the target data is sent to the first client; The attribute information includes a user account, the first attribute information includes a first user account, and when the user account belongs to the first user account, the target data is sent to the first client.
37. The data management device according to claim 33, characterized in that: The operation condition further includes second attribute information, wherein the second attribute information indicates attribute information of a client that is not allowed to operate the target data, and the data sending subunit is configured to execute: Acquire attribute information carried in the run request, where the attribute information includes at least one of device information, status information, or a user account, where the device information is information about the device where the first client is located, the status information indicates whether the first client is logged in, and the user account is a user account logged in by the first client; In a case where the attribute information does not belong to the second attribute information, the target data is sent to the first client.
38. The data management device according to claim 37, characterized in that: The data sending subunit is configured to perform at least one of the following: The attribute information includes the device information, the second attribute information includes second device information, and when the device information does not match the second device information, sending the target data to the first client; The attribute information includes the state information, the second attribute information includes second state information, the second state information indicates a non-logged-in state, and when the state information is not the second state information, sending the target data to the first client; The attribute information includes a user account, the second attribute information includes a second user account, and when the user account does not belong to the second user account, the target data is sent to the first client.
39. The data management device according to claim 32, characterized in that: The data sending unit comprises: The data and identification sending subunit is configured to send the target data and target data identification to the at least one client, wherein the target data identification indicates the target data, and the at least one client is used to return an exception notification carrying the target data identification when an exception occurs in the target data.
40. The data management device according to claim 32, characterized in that: The information acquisition unit comprises: A notification query subunit is configured to query at least one abnormal notification received within a first time period before a current time point, wherein the abnormal notification carries a data identifier, and the abnormal notification indicates that an abnormality occurs in the data indicated by the data identifier; A number determination subunit is configured to determine the number of abnormal notifications carrying a target data identifier in the at least one abnormal notification, wherein the target data identifier indicates the target data; The number determination subunit is configured to determine the average number of abnormal times based on the first duration and the number.
41. The data management device according to claim 40, characterized in that: The exception notification corresponds to a plurality of exception types, and the number determination subunit is configured to execute in the at least one exception notification, and determine the number of exception notifications that carry the target data identifier and belong to the target exception type.
42. The data management device according to claim 32, characterized in that: The operation condition further includes second attribute information, wherein the second attribute information indicates attribute information of a client that is not allowed to operate the target data; The condition updating unit comprises: The condition updating subunit is configured to determine the target attribute information as the second attribute information when the operating information includes the target attribute information corresponding to the client where the target data has an exception, and add the second attribute information to the operating condition to obtain the updated operating condition.
43. The data management device according to claim 42, characterized in that: The information acquisition unit comprises: A notification query subunit is configured to query at least one abnormal notification received within a second time period before a current time point, wherein the abnormal notification carries a data identifier and attribute information, and the abnormal notification indicates that an abnormality occurs in the client corresponding to the attribute information and the data indicated by the data identifier; The information acquisition subunit is configured to execute, in the at least one abnormal notification, acquiring the target attribute information in the abnormal notification carrying the target data identifier, where the target data identifier indicates the target data.
44. The data management device according to claim 42, characterized in that: The condition updating subunit is further configured to delete any second attribute information whose survival time reaches a third time period from the current operating condition, where the survival time refers to the time period during which the second attribute information exists in the operating condition.
45. The data management device according to any one of claims 32 to 44, characterized in that: The data sending unit is further configured to execute: In response to a request from a second client for running the target data, acquiring the updated running condition, the second client being any client; When the second client satisfies the updated operating condition, the target data is sent to the second client.
46. An electronic device, characterized in that: The electronic device comprises: processor; a memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the data management method as described in any one of claims 1 to claim 14.
47. A computer-readable storage medium, characterized in that When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the data management method according to any one of claims 1 to 14.
48. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the data management method according to any one of claims 1 to 14 is implemented.
