Data recovery method and device, electronic equipment and storage medium

Abstract

The invention discloses a data recovery method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining a plurality of pieces of first operation data of a target application, and obtaining to-be-recovered operation data in the first operation data, the to-be-recovered operation data being operation data of which a user identifier is a null identifier; reference operation data corresponding to the to-be-repaired operation data is determined from the first operation data based on the operation time of the to-be-repaired operation data and the device identifier, and the user identifier in the reference operation data is not an empty identifier; and replacing the empty identifier in the to-be-repaired operation data with the user identifier in the reference operation data to obtain repaired operation data corresponding to the to-be-repaired operation data. According to the technical scheme provided by the embodiment of the invention, which operation data is triggered by which users does not need to be determined through manual observation, so that the user tracking process is greatly simplified, and the application analysis efficiency is improved.

Description

Technical Field

[0001] The present disclosure belongs to the field of information processing technology, and in particular relates to a data repair method, device, electronic device and storage medium. Background Art

[0002] In the related art, when analyzing an application, a salesperson can analyze the application based on the application's operation data to obtain analysis results, which mainly include the number of users using the application, the average number of times the application is used, etc. When analyzing the application's operation data, the obtained application's operation data not only includes the operation data generated when a user logs into the application account, but also includes the operation data generated when no user logs into the application account. For the operation data generated when the application is operated when no user logs into the application account, it is impossible to determine which user operations generated the operation data, and it can only be determined through manual observation, which takes a lot of time and has low efficiency in analyzing applications. Summary of the invention

[0003] The embodiments of the present disclosure provide a solution to solve the problem in the related art that, for operation data generated by operating an application when no user has logged into the application account, it is impossible to determine which user operations generated the operation data, and the operation data can only be determined through manual observation, which takes a lot of time and has low efficiency in analyzing the application.

[0004] In a first aspect, the present disclosure provides a data repair method, the method comprising:

[0005] Acquire a plurality of first operation data of the target application, each of the first operation data at least including: a device identifier of an operating device, an operation time, and a user identifier of an operating user;

[0006] Acquire the operation data to be repaired in the first operation data, wherein the operation data to be repaired refers to the operation data whose user identifier is a null identifier;

[0007] Based on the operation time and the device identifier of the operation data to be repaired, determining reference operation data corresponding to the operation data to be repaired from the first operation data, wherein the user identifier in the reference operation data is not an empty identifier;

[0008] The user identifier in the operation data to be repaired is generated by using the user identifier in the reference operation data to obtain the repaired operation data corresponding to the operation data to be repaired.

[0009] In a second aspect, the present disclosure provides a data repair device, the device comprising:

[0010] an acquisition unit, configured to acquire a plurality of first operation data of a target application, each of the first operation data at least including: a device identifier of an operation device, an operation time, and a user identifier of an operation user;

[0011] The acquisition unit is further used to acquire the operation data to be repaired in the first operation data, wherein the operation data to be repaired refers to the operation data whose user identifier is a null identifier;

[0012] a determining unit, configured to determine, from the first operation data, reference operation data corresponding to the operation data to be repaired based on the operation time and the device identifier of the operation data to be repaired, wherein the user identifier in the reference operation data is not an empty identifier;

[0013] The replacement unit is used to generate the user identifier in the operation data to be repaired according to the user identifier in the reference operation data, and obtain the repaired operation data corresponding to the operation data to be repaired.

[0014] In a third aspect, the present disclosure provides an electronic device, including:

[0015] Processor; and

[0016] A memory, configured to store executable instructions of the processor;

[0017] The processor is configured to execute any method in the first aspect or any possible implementation of the first aspect by executing the executable instructions.

[0018] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements any method in the first aspect or any possible implementation of the first aspect.

[0019] The technical solution provided by the present disclosure is to obtain multiple first operation data of the target application, each of which at least includes: the device identification of the operating device, the operation time and the user identification of the operating user; obtain the operation data to be repaired in the first operation data, wherein the operation data to be repaired refers to the operation data with a null identification; based on the operation time and device identification of the operation data to be repaired, determine the reference operation data corresponding to the operation data to be repaired from the first operation data, and the user identification in the reference operation data is not a null identification; generate the user identification in the operation data to be repaired according to the user identification in the reference operation data, and obtain the repaired operation data corresponding to the operation data to be repaired. The technical solution provided by each embodiment of the present disclosure does not need to be manually observed to determine which operation data is determined by which users, but repairs the operation data to be repaired in the multiple first operation data of the acquired target application, and then changes the user identification in the operation data to be repaired with a null identification to the corresponding user identification, and then determines which operation data is triggered by which users, realizes user tracking analysis, greatly saves time, improves the efficiency of analyzing applications, and improves the accuracy of application analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0021] Figure 1 A flowchart of a data repair method provided by an embodiment of the present disclosure;

[0022] Figure 2 A schematic diagram of the structure of a data repair device provided by an embodiment of the present disclosure;

[0023] Figure 3 A schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0024] Embodiments of the present disclosure are described in detail below, and examples of the embodiments are shown in the accompanying drawings. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, but should not be understood as limiting the present disclosure.

[0025] The terms "first" and "second" and the like in the specification, claims, and drawings of the disclosed embodiments 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 disclosed embodiments described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0026] The data repair method provided in the embodiments of the present disclosure may be run on a terminal device or a server. The terminal device may be a local terminal device. The server may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0027] In the related art, when analyzing the usage of an application, a salesperson can analyze the application based on the application's operation data to obtain analysis results, which mainly include the number of users using the application, the average number of times the application is used, etc. When analyzing the application's operation data, the obtained application's operation data not only includes the operation data generated when a user logs into the application account, but also includes the operation data generated when no user logs into the application account. For the operation data generated when the application is operated when no user logs into the application account, it is impossible to determine which user operations generated the operation data, and it can only be determined through manual observation, which takes a lot of time and has low efficiency in analyzing applications.

[0028] Taking the data repair method applied to a server as an example, multiple first operation data of a target application can be obtained, and the operation data to be repaired in the multiple first operations can be determined, wherein each first operation data at least includes the device identification of the operating device, the operation time, and the user identification of the operating user, and then the reference operation data corresponding to the operation data to be repaired is determined from the first operation data, and finally the user identification in the reference operation data is replaced with the user identification in the operation data to be repaired. This process does not require manual determination, which greatly saves time and improves the efficiency of analyzing the target application.

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

[0030] Figure 1 A flowchart of a data repair method provided by an exemplary embodiment of the present disclosure is provided. The method can be applied to various devices with data processing functions. Taking the method applied to a server as an example, the solution at least includes the following steps S101-S104:

[0031] S101, obtaining a plurality of first operation data of a target application.

[0032] In some embodiments, each first operation data includes at least: a device identifier of the operation device, an operation time, and a user identifier of the operation user. It is understandable that one operation data corresponds to an event operation performed by an operation user on a target application installed on an operation device.

[0033] Specifically, the operating device refers to a device used by an operating user to perform an event operation in a target application, and the device identifier of the operating device refers to data information used to represent the operating device. For example, an operating user performs an event operation in a target application in mobile phone A, that is, the operating device is mobile phone A.

[0034] In some embodiments, the operating user refers to the user account of the event operation currently being performed in the target application, and the user identifier refers to data information representing the operating user.

[0035] In some embodiments, the operation time refers to the time information when the operating user performs an event operation on the target application in the operating device.

[0036] In some embodiments, the target application is configured with a corresponding background server. When the target application on any operating device is operated, the relevant data generated will be stored in the background server, and multiple first operation data of the target application in the first time period corresponding to the preset time window can be obtained from the background server. The preset time window can be a time window of 12 hours, 24 hours or 3 days, etc., which is limited here.

[0037] Furthermore, considering that the operation data has temporal continuity, in order to reduce the amount of subsequent data processing, obtaining multiple first operation data of the target application can specifically include: obtaining the original operation data of the target application, and based on the user identifier and device identifier in the original operation data, compressing the original operation data according to the time axis corresponding to the operation time to generate first operation data.

[0038] The original operation data includes the device identification of the operating device, the operation time, and the user identification of the operating user. The operation time in the original operation data is the time point when the operating user performs an event operation on the target application in the operating device. For example, the original operation data is shown in the following table (1):

[0039] Raw operational data Equipment identification User ID Operation time 1 A a 1 2 A # 2 3 A b 3 4 A b 4 5 A # 5 6 A c 6 7 B # 1 8 C # 2

[0040] Table 1

[0041] Among them, "#" indicates that the user ID in the corresponding original operation data is an empty ID.

[0042] Specifically, the original operation data in a time window of a certain length can be obtained, and then the original operations can be grouped according to the device identifier, and each original operation data can be sorted according to the order of occurrence of the corresponding operation event according to the operation time in the original operation data, and then the sorted original operation data can be compressed according to the time axis according to the device identifier and user identifier in the original operation information, so as to construct the first operation data in the time window according to the original operation data corresponding to the same device identifier and the same user identifier at continuous operation time, wherein the operation time in the first operation data includes the time point information of the start time and the end time of the operation user's operation of the target application. For example, the first operation data is shown in the following table (2), wherein the end timestamp refers to the end time point in the corresponding time window:

[0043]

[0044]

[0045] Table 2

[0046] It is understandable that the first operation data may indicate an operating user on a certain operating device in a certain time period within a preset time window, and the first operation data may display a switching process of operating users on a certain operating device in different time periods within the preset time window.

[0047] Further, in some implementations, obtaining a plurality of first operation data of the target application includes steps S11-S12:

[0048] S11, obtaining a plurality of original operation data of the target application.

[0049] Specifically, all relevant operation data of the target application, that is, a plurality of original operation data, may be acquired from the background server.

[0050] S12, deleting original operation data whose user identification does not conform to a second preset rule from among the multiple original operation data, to obtain multiple first operation data of the target application.

[0051] Among them, the second preset rule can be used to indicate the identification rule of the user identification, and the original operation data with the user identification as the violation identification can be screened out through the second preset rule, that is, invalid user data in the original operation data is filtered out. Specifically, in the process of the operating user operating the target application, there are some operating users who illegally register the account of the target application, thereby generating a violation identification. In order to ensure the accuracy of the first operation data obtained, it is necessary to delete these operation data containing the user identification as the violation identification.

[0052] The second preset rule can also be used to indicate the identification rule of the device identification. The second preset rule can be used to filter out the original operation data whose device identification is a violation identification, that is, to filter out the dirty device data in the original operation data. Specifically, when the operating user operates the target application, the operating device used is not a regular device but a violation device. Therefore, in order to ensure the accuracy of the first operation data obtained, it is necessary to delete the operation data containing the device identification as a violation identification.

[0053] S102: Acquire the operation data to be repaired in the first operation data.

[0054] The operation data to be repaired refers to the operation data whose user identifier is a null identifier.

[0055] Specifically, after acquiring a plurality of first operation data, the user identifiers contained in all the first operation data are traversed, and the first operation data in which the user identifier is a null identifier is taken as the operation data to be repaired.

[0056] S103: Determine, from the first operation data, reference operation data corresponding to the operation data to be repaired based on the operation time and the device identifier of the operation data to be repaired.

[0057] In some embodiments, the user identifier in the reference operation data is not an empty identifier. Specifically, operation data whose operation time is close to the operation time of the operation data to be repaired and whose device identifier is consistent with the device identifier of the operation data to be repaired can be selected from the first operation data as the reference operation data.

[0058] In some embodiments, based on the operation time and device identification of the operation data to be repaired, determining reference operation data corresponding to the operation data to be repaired from the first operation data includes steps S21-S24:

[0059] S21, grouping a plurality of first operation data according to device identifiers to obtain a plurality of first operation data groups.

[0060] Specifically, the first operation data with the same device identifier are grouped into the same group, thereby obtaining multiple first operation data groups, and the multiple first operation data groups are displayed in the form of windows. For example, taking the above Table 2 as an example, a first operation data group that can be obtained is specifically as shown in the following figure:

[0061] First operation data Equipment identification User ID Start time End Time 1 A a 1 2 2 A # 2 3 3 A b 3 5 4 A # 5 6 5 A c 6 End timestamp

[0062] Table 3

[0063] For example, as shown in the above-mentioned Figure 2, the multiple first operation data include seven first operation data, namely first operation data 1, first operation data 2, first operation data 3, first operation data 4, first operation data 5, first operation data 6, and first operation data 7. The first operation data with the same device identification are regarded as a first operation data group, the five first operation data (first operation data 1 to first operation data 5) corresponding to the device identification A are regarded as a first operation data group, the one first operation data (first operation data 6) corresponding to the device identification B is regarded as a first operation data group, and the one first operation data (first operation data 7) corresponding to the device identification C is regarded as a first operation data group.

[0064] S22: Determine, according to the device identifier of the operation data to be repaired, a target operation data group where the operation data to be repaired is located from a plurality of first operation data groups.

[0065] Specifically, after the first operation data group is determined, a target operation data group whose device identifier is consistent with the device identifier of the operation data to be repaired can be screened from the first operation data group according to the device identifier of the operation data to be repaired.

[0066] Continuing with the multiple first operation data groups shown in the above chart as an example, the first operation data with the user identifier being an empty identifier are the first operation data 2 and the first operation data 4, so the first operation data group where the first operation data 2 and the first operation data 4 are located is the target operation data group.

[0067] S23, sorting the first operation data included in the target operation data group according to the operation time, to obtain a first sorting result of each first operation data in the target operation data group.

[0068] Specifically, continuing to take the first operation data group shown in the above Figure 3 as an example, the first operation data group where the first operation data 2 and the first operation data 4 are located is the target operation data group, and the five first operation data in the target operation data group are sorted according to the operation time, namely, first operation data 1, first operation data 2, first operation data 3, first operation data 4, and first operation data 5.

[0069] S24, based on the first sorting results of each first operation data in the target operation data group and the operation time of the operation data to be repaired, query the first operation data whose operation time is closest to the operation time of the operation data to be repaired and whose user identifier is not an empty identifier as the reference operation data corresponding to the operation data to be repaired.

[0070] Specifically, continuing to take the first operation data group shown in the above Figure 3 as an example, the operation time of the first operation data 1 and the first operation data 2 is the closest, and the user identifier contained in the first operation data 1 is not an empty identifier, the first operation data 1 can be used as the reference operation data corresponding to the operation data to be repaired.

[0071] In some embodiments, if there are two first operation data whose operation time is closest to the operation time of the operation data to be repaired and whose user identifier is not an empty identifier, such as there are first operation data whose user identifier is not an empty identifier in the previous and next time sequences of the operation data to be repaired on the time axis, the previous first operation data is determined to be the reference operation data corresponding to the operation data to be repaired, or the subsequent first operation data is determined to be the reference operation data corresponding to the operation data to be repaired.

[0072] Continuing with the first operation data group shown in the above-mentioned Figure 3 as an example, there are first operation data in the previous and next time sequences of the operation time of the first operation data 2 on the time axis, namely, the first operation data 1 and the first operation data 3. The time interval between the end time in the operation time of the first operation data 1 and the start time in the operation time of the first operation data 2 is equal to the time interval between the start time in the operation time of the first operation data 3 and the end time in the operation time of the first operation data 2. The preceding first operation data can be used as reference operation data, that is, the first operation data 1 can be used as the reference operation data corresponding to the first operation data 2.

[0073] Furthermore, in order to improve the user tracking accuracy of the operation data to be repaired, if the first operation data whose operation time is closest to the operation time of the operation data to be repaired and whose user identifier is not an empty identifier includes first candidate operation data and second candidate operation data, and the user identifiers corresponding to the first candidate operation data and the second candidate operation data are different, the event data corresponding to the first candidate operation data, the second candidate operation data and the operation data to be repaired can be obtained, and the first event operation graph can be obtained according to the user identifier corresponding to the first candidate operation data, and the second event operation graph can be obtained according to the user identifier corresponding to the second candidate operation data, so as to determine the path matching rate in the first event operation graph according to the event data corresponding to the first candidate operation data and the operation data to be repaired, and determine the path matching rate in the second event operation graph according to the event data corresponding to the second candidate operation data and the operation data to be repaired; finally, the reference operation data is determined from the first candidate operation data and the second candidate operation data according to the path matching rate corresponding to the first candidate operation data and the second path matching rate corresponding to the second candidate operation data.

[0074] Among them, the first candidate operation data can be the preceding operation data corresponding to the operation data to be repaired, and the second candidate operation data can be the succeeding operation data corresponding to the operation data to be repaired; taking the first operation data group shown in the above Figure 3 as an example, the first candidate operation data corresponding to the first operation data 2 can include the first operation data 1, and the second candidate operation data corresponding to the first operation data 2 can include the first operation data 3.

[0075] Among them, event data refers to relevant information of the event operation corresponding to the operation data, such as the event operation path, etc.; it can be understood that, as mentioned above, the first operation data is obtained by compressing the original operation data based on the time axis. Therefore, the first operation data can correspond to the operation data of at least one event operation, and these event operations can constitute the corresponding event operation path. For example, in a continuous time period, after the operation user corresponding to a certain user identifier logs in to the target application on a certain device, enters the first function page to trigger the first function operation and the second function operation in sequence, and then enters the second function page to trigger the third function operation. For this, the original operation data that can be generated include: login operation data, first function operation data, second function operation data and third function operation data. After compressing these original operation data based on the time axis, the first operation data corresponding to the device information and / or user identifier of all event operations in the continuous time period can be obtained, and the corresponding event operation path can be expressed as follows: [e1, e2, e3, e4], wherein e1, e2, e3, e4 respectively represent the identification information corresponding to the login operation, the first function operation, the second function operation and the third function operation. The event operation graph refers to the set of paths of event operations performed by the user in the target application corresponding to the user identifier. Specifically, the event operation graph can be expressed as: G = [e i ,e j ,r ij ], where e i 、e j Represents two event operations triggered continuously, r ij It can be expressed as e i With e j The trigger probability of continuous triggering in the historical event operation path corresponding to the operation user, i, j are positive integers greater than 1.

[0076] After obtaining the event operation paths corresponding to the first candidate operation data, the second candidate operation data, and the operation data to be repaired, the event operation paths of the first candidate operation data and the operation data to be repaired can be spliced ​​to obtain the first event operation path, and the event operation paths of the second candidate operation data and the operation data to be repaired can be spliced ​​to obtain the second event operation path; according to the first event operation path and the first event operation graph, the matching probability of the first event operation path in the first event operation graph is obtained; specifically, the path matching rate of the first event operation path in the first event operation graph can be calculated by the following formula (1):

[0077]

[0078] in, Indicates the two event operations e that are triggered consecutively in the (l-1)th order in the first event operation path i and ej The connection probability of , l is greater than or equal to 2.

[0079] Similarly, based on the second event operation path and the second event operation map, the path matching rate of the second event operation path is obtained; finally, among the first event operation path and the second operation path, the event operation path with the highest matching probability is used to determine the target event operation path, so as to determine the corresponding candidate operation data from the target event operation path as reference operation data.

[0080] By constructing a corresponding event operation path for the operation data to be repaired and the candidate operation data within the time window, and then matching the operation path with the event operation graph of the user identifier corresponding to the first candidate operation data or the second candidate operation data, the candidate operation data corresponding to the event operation path with the highest matching probability is determined as the reference operation data of the operation data to be repaired, thereby improving the accuracy of user tracking and analysis. Subsequently, the user identifier of the operation data to be repaired is determined based on the user identifier of the reference operation data, thereby ensuring the accuracy of subsequent data analysis of the operation data of the target application.

[0081] In some embodiments, based on the first sorting results of each first operation data in the target operation data group and the operation time of the operation data to be repaired, the step of querying the first operation data whose operation time is closest to the operation time of the operation data to be repaired and whose user identifier is not an empty identifier includes: taking the operation data to be repaired as the starting point, and preferentially searching backward along the direction of the time axis within a first time period corresponding to a preset time window for the first operation data whose user identifier is not an empty identifier; if the first first operation data whose user identifier is not an empty identifier is found, the search is stopped, and the first operation data is used as the reference operation data corresponding to the operation data to be repaired; if the first operation data whose user identifier is not an empty identifier is not found backward along the direction of the time axis within the first time period, the operation data to be repaired is continued to be the starting point, and within the first time period corresponding to the preset time window, the first operation data whose user identifier is not an empty identifier is searched forward along the direction of the time axis; if the first first operation data whose user identifier is not an empty identifier is found, the search is stopped, and the first operation data is used as the reference operation data corresponding to the operation data to be repaired.

[0082] Continuing with the example of the first operation data group shown in the above-mentioned chart 3, where the operation data to be repaired is the first operation data 2, the first operation data 2 can be used as the starting point, and the first operation data whose user identifier is not an empty identifier can be searched backwards in the first operation data group in the direction of the time axis. If the first first operation data whose user identifier is not an empty identifier is found, such as the first operation data 3, the search is stopped, and the first operation data 3 is used as the reference operation data corresponding to the operation data to be repaired (i.e., the first operation data 2). It can be understood that if the first operation data whose user identifier is not an empty identifier is not found in the first operation data group in the direction of the time axis, the first operation data 2 can be used as the starting point, and the first operation data whose user identifier is not an empty identifier can be searched forward in the direction of the time axis.

[0083] It is understandable that the reference operation data can be used as a reference for subsequent repair of the user identifier in the operation data to be repaired, so as to implement user tracking analysis of the operation data to be repaired and locate the user identifier of the operating user corresponding to the operation data to be repaired.

[0084] Furthermore, in some embodiments, the method further includes steps S241-S243:

[0085] S241, if the first operation data whose user identifier is not a null identifier is not found in the target operation data group, the historical cross-sectional data is obtained.

[0086] In some embodiments, the historical cross-sectional data includes the mapping relationship between the latest device identification and user identification in the historical time period.

[0087] S242, obtaining the target user identifier mapped to the device identifier corresponding to the operation data to be repaired from the historical cross-section data.

[0088] In other embodiments, if the target user identifier mapped to the device identifier corresponding to the operation data to be repaired does not exist in the historical cross-sectional data, the user identifier in the first operation data whose operation time is closest to the operation time of the operation data to be repaired and whose user identifier is not empty is queried from the historical cross-sectional data as the target user identifier.

[0089] S243, replacing the empty identifier in the operation data to be repaired with the target user identifier, to obtain the repaired operation data corresponding to the operation data to be repaired.

[0090] Specifically, when the first operation data whose user identifier is not an empty identifier is not queried in the target operation data group, the latest mapping relationship between the device identifier and the user identifier can be found from the historical cross-sectional data to determine the target user identifier mapped to the device identifier corresponding to the operation data to be repaired, and then the target user identifier corresponding to the operation data to be repaired is constructed based on the target user identifier to obtain the user identifier corresponding to the operation data to be repaired, thereby realizing user tracking analysis of the operation data to be repaired and obtaining the repaired operation data.

[0091] In some embodiments, the plurality of first operation data are data within a first time period; the method further comprises steps S31-S32:

[0092] S31, if the first operation data whose user identifier is not a null identifier is not found in the first sorting result of the target operation data group, the historical operation data of the target application in the historical time period before the first time period is obtained.

[0093] S32, determining reference operation data corresponding to the operation data to be repaired from the historical operation data.

[0094] Among them, the time window corresponding to the historical time period is the previous time window that is continuous with the time window corresponding to the first time period; for example, taking the time window as 24 hours, the first time period is the time point corresponding to June 28, and the historical time period is the time period corresponding to June 27.

[0095] In some embodiments, when the first operation data whose user identifier is not an empty identifier is not found in the target operation data group, the historical time period corresponding to the first time period can also be determined, and the reference operation data corresponding to the operation data to be repaired can be determined from each second operation data in the historical operation data corresponding to the historical time period.

[0096] Specifically, the second operation data whose user identifier is not an empty identifier can be searched backwards in the direction of the time axis within the historical time period, and the second operation data is directly used as the reference operation data corresponding to the operation data to be repaired. For example, within the historical time period, the second operation data whose user identifier is not an empty identifier is searched backwards in the direction of the time axis first, if the first second operation data whose user identifier is not an empty identifier is found, the search is stopped, and the second operation data is used as the reference operation data corresponding to the operation data to be repaired, if the second operation data whose user identifier is not an empty identifier is not found, the second operation data whose user identifier is corresponding to the relevant device identifier is searched backwards in the direction of the time axis first, and the second operation time is used as the reference operation data corresponding to the operation data to be repaired.

[0097] In some embodiments, based on the first sorting results of the first operation data in the target operation data group and the operation time of the operation data to be repaired, querying the first operation data whose operation time is closest to the operation time of the operation data to be repaired and whose user identifier is not a null identifier as the reference operation data corresponding to the operation data to be repaired further includes:

[0098] If the first operation data whose user identifier is not a null identifier is not found in the first sorting result of the target operation data group, reference operation data corresponding to the operation data to be repaired is generated based on the first preset rule.

[0099] In this embodiment, if the first operation data whose user identifier is not an empty identifier is not found from the first sorting result of the target operation data group, it means that the first operation data existing in the target operation data group are all operation data to be repaired. In order to repair the first operation data in the target operation data group, it is necessary to generate reference operation data corresponding to the above-mentioned operation data to be repaired based on the first preset rule.

[0100] Specifically, generating reference operation data corresponding to the operation data to be repaired based on the first preset rule includes steps S41-S43:

[0101] S41, obtaining the device identification in the operation data to be repaired and the operation time in the operation data to be repaired.

[0102] S42, obtaining a default identifier.

[0103] In some embodiments, the default identifier may be the user identifier corresponding to the operating user who has used the target application for the longest time, or the user identifier corresponding to the operating user who has used the target application the most times, or other user identifiers, which may be set according to actual conditions.

[0104] S43, generating reference operation data corresponding to the operation data to be repaired based on the device identifier in the operation data to be repaired, the operation time in the operation data to be repaired, and the default identifier.

[0105] In an embodiment, the device identifier in the operation data to be repaired, the operation time in the operation data to be repaired, and the default identifier are used as reference operation data corresponding to the operation data to be repaired.

[0106] S104, generating the user identifier in the operation data to be repaired according to the user identifier in the reference operation data, and obtaining the repaired operation data corresponding to the operation data to be repaired.

[0107] After obtaining the reference operation data, the user identifier in the reference operation data can be determined as the user identifier in the operation data to be modified, so as to replace the user identifier in the operation data to be repaired (i.e., an empty identifier) ​​with the user identifier in the reference operation data, and obtain the repaired operation data corresponding to the operation data to be repaired, thereby realizing user tracking and analysis of the operation data to be repaired with an empty user identifier, so as to determine the corresponding operation user and improve the accuracy of subsequent application analysis.

[0108] Furthermore, for the original operation data in which the user identifier is empty, the corresponding target operation data can be matched in the first operation data through the device identifier and operation time in the original operation data, and then the user identifier corresponding to the original operation data in which the user identifier is empty can be determined according to the user identifier in the target operation data, thereby realizing user tracking and analysis of the original operation data in which the user identifier is empty.

[0109] Specifically, continuing to take the multiple first operation data groups shown in the above chart as an example, the first operation data after repair is shown in the following chart 4:

[0110] First operation data Equipment identification User ID Start time End Time 1 A a 1 2 2 A b 2 3 3 A b 3 5 4 A c 5 6 5 A c 6 End timestamp 6 B d 1 End timestamp 7 C e 2 End timestamp

[0111] Table 4

[0112] In this embodiment, taking the first operation data 2 as the operation data to be repaired as an example, the user identifier of the first operation data 2 is a blank identifier, and the user identifier a in the first operation data 1 is used as the user identifier of the operation data to be repaired. Or taking the first operation data 4 as the operation data to be repaired as an example, the user identifier of the first operation data 4 is a blank identifier, and the user identifier b in the first operation data 3 is used as the user identifier of the operation data to be repaired.

[0113] Furthermore, in order to ensure the integrity of the original information in the operation data, a user object identifier can also be constructed for the operation data, and the user object identifier can be used to identify a unified operation user; specifically, after obtaining the first operation data, the user object identifier in the operation data to be repaired can be generated based on the user identifier in the first operation data, wherein, when the user identifier is an empty identifier, the user object identifier in the first operation data is generated based on the empty identifier.

[0114] After obtaining the operation data to be repaired in the first operation data and the reference operation data corresponding to the operation data to be repaired, the user object identifier in the operation data to be repaired can be generated according to the user object identifier corresponding to the reference operation data; after obtaining the user object identifiers in all the operation data to be repaired, that is, after all the first operation data are constructed with corresponding user object identifiers, the user object identifier of the original operation data can be generated based on the user object identifier of the first operation data, so that any operation data in the original operation data has an identifier for representing the user object, which is convenient for subsequent tracking of the event operations of the operating user, and the comprehensiveness and accuracy of data analysis using the original operation data.

[0115] Specifically, the device identifier and operation time in each original operation data may be used to match the corresponding target operation data in the first operation data, so as to generate the user object identifier in the original operation data according to the user object identifier in the target operation data.

[0116] Continuing to take the multiple first operation data groups shown in the above chart as an example, the first operation data after repair is shown in the following chart 5:

[0117]

[0118] Table 5

[0119] Based on the first operation data shown in Figure 5, for each original operation data shown in Table 2 above, the corresponding target operation data can be matched in the first operation data according to the device identifier and operation time in each original operation, so as to generate the user object identifier in the original operation data according to the user object identifier in the target operation data, and obtain the original operation data that can be used for subsequent application analysis. It can be understood that in addition to retaining the complete original information, the user object identifier of the original operation data is used to identify the operating user of the corresponding original data, which can be used in subsequent application analysis processes such as user tracking, thereby greatly improving the accuracy of application analysis.

[0120] In some embodiments, the repair process of the operation data to be repaired may be an offline repair process.

[0121] In some embodiments, the core of offline repair is to find the mapping relationship between the user and the device, and repair it to the user object identifier of the unlogged data. For example, the unlogged data refers to the operation data whose user identifier is a null identifier. According to Table 3 and Table 5, the user object identifier of the first operation data 2 before repair can be a null value, and the user object identifier of the first operation data 2 after repair can be Ub.

[0122] In some embodiments, the method further includes: sorting the plurality of first operation data according to the order of operation time to obtain a second sorting result.

[0123] In some implementations, determining reference operation data corresponding to the operation data to be repaired from the first operation data based on the operation time and the device identifier of the operation data to be repaired includes:

[0124] From the second sorting result, search for the first operation data whose operation time is closest to the operation time of the operation data to be repaired, whose user identifier is not an empty identifier, and whose device identifier is the same as the device identifier of the operation data to be repaired; and use the first operation data as the reference operation data corresponding to the operation data to be repaired.

[0125] Specifically, the target application generates tens of millions of operation data to be repaired every day. Therefore, in order to ensure the efficiency of repair, multiple first operation data do not need to be grouped. Instead, the multiple first operation data are directly sorted according to the order of operation time to obtain a second sorting result, and then from the second sorting result, the first operation data whose operation time is closest to the operation time of the operation data to be repaired, the user identifier is not an empty identifier, and the device identifier is the same as the device identifier of the operation data to be repaired is searched. The first operation data found is the reference operation data corresponding to the operation data to be repaired.

[0126] The technical solution provided by the present disclosure obtains multiple first operation data of the target application, each of which at least includes: the device identification of the operating device, the operation time, and the user identification of the operating user; obtains the operation data to be repaired in the first operation data, wherein the operation data to be repaired refers to the operation data with a null identification; based on the operation time and device identification of the operation data to be repaired, determines the reference operation data corresponding to the operation data to be repaired from the first operation data, wherein the user identification in the reference operation data is not a null identification; generates the user identification in the operation data to be repaired by using the user identification in the reference operation data, and obtains the repaired operation data corresponding to the operation data to be repaired. The technical solution provided by each embodiment of the present disclosure does not need to manually observe to determine which operation data is determined by which users, but repairs the operation data to be repaired in the multiple first operation data of the acquired target application, and then modifies the user identification in the operation data to be repaired with a null identification to the corresponding user identification, and then determines which operation data is triggered by which users, which greatly simplifies the user tracking process, saves time, and improves the efficiency of analyzing applications.

[0127] Figure 2 A schematic diagram of the structure of a data repair device provided by an exemplary embodiment of the present disclosure;

[0128] The device includes: an acquisition unit 201, a determination unit 202, and a replacement unit 203;

[0129] An acquisition unit 201 is used to acquire a plurality of first operation data of a target application, each of which includes at least: a device identifier of an operation device, an operation time, and a user identifier of an operation user;

[0130] The acquisition unit 202 is further configured to acquire the operation data to be repaired in the first operation data, wherein the operation data to be repaired refers to the operation data whose user identifier is a null identifier;

[0131] A determining unit 203 is configured to determine, from the first operation data, reference operation data corresponding to the operation data to be repaired based on the operation time and the device identifier of the operation data to be repaired, wherein the user identifier in the reference operation data is not an empty identifier;

[0132] The replacing unit 204 is configured to generate the user identifier in the operation data to be repaired according to the user identifier in the reference operation data, and obtain the repaired operation data corresponding to the operation data to be repaired.

[0133] In some embodiments, when the apparatus is used to determine the reference operation data corresponding to the operation data to be repaired from the first operation data based on the operation time and the device identifier of the operation data to be repaired, it is specifically used to:

[0134] Grouping the plurality of first operation data according to the device identifier to obtain a plurality of first operation data groups;

[0135] Determining, according to the device identifier of the operation data to be repaired, a target operation data group in which the operation data to be repaired is located from a plurality of first operation data groups;

[0136] Sorting the first operation data included in the target operation data group according to the operation time to obtain a first sorting result of each first operation data in the target operation data group;

[0137] Based on the first sorting results of each first operation data in the target operation data group and the operation time of the operation data to be repaired, the first operation data whose operation time is closest to the operation time of the operation data to be repaired and whose user identifier is not an empty identifier is queried as the reference operation data corresponding to the operation data to be repaired.

[0138] In some embodiments, the device is further configured to:

[0139] If the first operation data whose user identifier is not a null identifier is not found in the target operation data group, then historical cross-sectional data is acquired, the cross-sectional data including a mapping relationship between device identifiers and user identifiers within a historical time period;

[0140] Obtaining a target user ID mapped to a device ID corresponding to the operation data to be repaired from the historical cross-section data;

[0141] The target user identifier replaces the empty identifier in the operation data to be repaired, and the repaired operation data corresponding to the operation data to be repaired is obtained.

[0142] In some embodiments, the device is further configured to:

[0143] If the first operation data whose user identifier is not a null identifier is not found in the first sorting result of the target operation data group, then the historical operation data of the target application in the historical time period before the first time period is obtained;

[0144] From the historical operation data, reference operation data corresponding to the operation data to be repaired is determined.

[0145] In some embodiments, the device is further configured to:

[0146] If the first operation data whose user identifier is not a null identifier is not found in the first sorting result of the target operation data group, reference operation data corresponding to the operation data to be repaired is generated based on the first preset rule.

[0147] In some embodiments, when the device is used to generate reference operation data corresponding to the operation data to be repaired based on the first preset rule, it is specifically used to:

[0148] Obtaining the device identification in the operation data to be repaired and the operation time in the operation data to be repaired;

[0149] Get the default identifier;

[0150] Reference operation data corresponding to the operation data to be repaired is generated based on the device identifier in the operation data to be repaired, the operation time in the operation data to be repaired, and the default identifier.

[0151] In some embodiments, the device is further configured to:

[0152] Sorting the plurality of first operation data according to the order of operation time to obtain a second sorting result;

[0153] When the apparatus is used to determine the reference operation data corresponding to the operation data to be repaired from the first operation data based on the operation time and the device identifier of the operation data to be repaired, it is specifically used to:

[0154] From the second sorting result, searching for the first operation data whose operation time is closest to the operation time of the operation data to be repaired, whose user identifier is not a null identifier, and whose device identifier is the same as the device identifier of the operation data to be repaired;

[0155] The first operation data is used as reference operation data corresponding to the operation data to be repaired.

[0156] In some embodiments, when the device is used to obtain a plurality of first operation data of a target application, it is specifically used to:

[0157] Obtain multiple original operation data of the target application;

[0158] The original operation data whose user identification does not conform to the second preset rule is deleted from the plurality of original operation data to obtain a plurality of first operation data of the target application.

[0159] In some embodiments, in order to facilitate understanding of this solution, taking the entire day of July 8th in region A as an example, all first operation data within the time period are obtained, and then the operation data to be repaired among the multiple first operation data are determined. Based on the operation time and device identification of the operation data to be repaired, the reference operation data corresponding to the operation data to be repaired is determined from the first operation data. Finally, the user identification in the operation data to be repaired is generated based on the user identification in the reference operation data, and the repaired operation data corresponding to the operation data to be repaired is obtained. In this embodiment, multiple first operation data after repair can be saved to form new historical cross-sectional data.

[0160] In other embodiments, the relevant data of the above-mentioned repair process may be stored in a local database.

[0161] The technical solution provided by the present disclosure obtains multiple first operation data of the target application, each of which at least includes: the device identification of the operating device, the operation time, and the user identification of the operating user; obtains the operation data to be repaired in the first operation data, wherein the operation data to be repaired refers to the operation data whose user identification is an empty identification; based on the operation time and device identification of the operation data to be repaired, the reference operation data corresponding to the operation data to be repaired is determined from the first operation data, and the user identification in the reference operation data is not an empty identification; according to the user identification in the reference operation data, the user identification in the operation data to be repaired is generated, and the repaired operation data corresponding to the operation data to be repaired is obtained. The technical solution provided by each embodiment of the present disclosure does not need to manually observe to determine which operation data is determined by which users, but repairs the operation data to be repaired in the multiple first operation data of the acquired target application, and then modifies the user identification in the operation data to be repaired as an empty identification to the corresponding user identification, and then determines which operation data is determined by which users, which greatly saves time and improves the efficiency of analyzing applications.

[0162] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, no further description is given here. Specifically, the device may perform the above method embodiment, and the above and other operations and / or functions of each module in the device are the corresponding processes in each method in the above method embodiment, respectively, and no further description is given here for the sake of brevity.

[0163] The above describes the device of the embodiment of the present disclosure from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present disclosure can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in conjunction with the embodiment of the present disclosure can be directly embodied as a hardware decoding processor to execute, or a combination of hardware and software modules in the decoding processor to execute. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps in the above method embodiment in conjunction with its hardware.

[0164] Figure 3 is a schematic block diagram of an electronic device provided by an embodiment of the present disclosure, and the electronic device may include:

[0165] The memory 301 and the processor 302, the memory 301 is used to store the computer program and transmit the program code to the processor 302. In other words, the processor 302 can call and run the computer program from the memory 301 to implement the method in the embodiment of the present disclosure.

[0166] For example, the processor 302 may be configured to execute the above method embodiments according to instructions in the computer program.

[0167] In some embodiments of the present disclosure, the processor 302 may include but is not limited to:

[0168] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0169] In some embodiments of the present disclosure, the memory 301 includes but is not limited to:

[0170] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0171] In some embodiments of the present disclosure, the computer program may be divided into one or more modules, which are stored in the memory 301 and executed by the processor 302 to complete the method provided by the present disclosure. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0172] like Figure 3 As shown, the electronic device may also include:

[0173] The transceiver 303 may be connected to the processor 302 or the memory 301 .

[0174] The processor 302 may control the transceiver 303 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 303 may include a transmitter and a receiver. The transceiver 303 may further include an antenna, and the number of antennas may be one or more.

[0175] It should be understood that the various components in the electronic device are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0176] The present disclosure also provides a computer storage medium on which a computer program is stored, and when the computer program is executed by a computer, the computer can perform the method of the above method embodiment. In other words, the present disclosure embodiment also provides a computer program product containing instructions, and when the instructions are executed by a computer, the computer can perform the method of the above method embodiment.

[0177] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid state disk (solid state disk, SSD)), etc.

[0178] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this disclosure.

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

[0180] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. For example, each functional module in each embodiment of the present disclosure may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0181] The above are only specific embodiments of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure, which should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A data repair method, characterized in that: The method comprises: Acquire a plurality of first operation data of the target application, each of the first operation data at least including: a device identifier of an operating device, an operation time, and a user identifier of an operating user; Acquire the operation data to be repaired in the first operation data, wherein the operation data to be repaired refers to the operation data whose user identifier is a null identifier; Based on the operation time and the device identifier of the operation data to be repaired, determining reference operation data corresponding to the operation data to be repaired from the first operation data, wherein the user identifier in the reference operation data is not an empty identifier; The user identifier in the operation data to be repaired is generated by using the user identifier in the reference operation data to obtain the repaired operation data corresponding to the operation data to be repaired.

2. The method according to claim 1, characterized in that: The determining, from the first operation data, reference operation data corresponding to the operation data to be repaired based on the operation time and the device identifier of the operation data to be repaired, comprises: Grouping the plurality of first operation data according to the device identifier to obtain a plurality of first operation data groups; Determining, according to the device identifier of the operation data to be repaired, a target operation data group where the operation data to be repaired is located from the plurality of first operation data groups; Sorting the first operation data included in the target operation data group according to the operation time to obtain a first sorting result of each first operation data in the target operation data group; Based on the first sorting results of each first operation data in the target operation data group and the operation time of the operation data to be repaired, the first operation data whose operation time is closest to the operation time of the operation data to be repaired and whose user identifier is not an empty identifier is queried as the reference operation data corresponding to the operation data to be repaired.

3. The method according to claim 2, characterized in that The method further comprises: If the first operation data whose user identifier is not a null identifier is not found in the target operation data group, acquiring historical cross-sectional data, the cross-sectional data including a mapping relationship between device identifiers and user identifiers within a historical time period; Acquire a target user identifier mapped to the device identifier corresponding to the operation data to be repaired from the historical cross-sectional data; The target user identifier replaces the empty identifier in the operation data to be repaired, and obtains the repaired operation data corresponding to the operation data to be repaired.

4. The method according to claim 2, characterized in that: The plurality of first operation data are data within a first time period, and the method further includes: If the first operation data whose user identifier is not a null identifier is not found in the first sorting result of the target operation data group, acquiring the historical operation data of the target application in the historical time period before the first time period; From the historical operation data, reference operation data corresponding to the operation data to be repaired is determined.

5. The method according to claim 2, characterized in that: The method further comprises: If the first operation data whose user identifier is not a null identifier is not found in the first sorting result of the target operation data group, reference operation data corresponding to the operation data to be repaired is generated based on a first preset rule.

6. The method according to claim 5, characterized in that Generating reference operation data corresponding to the operation data to be repaired based on the first preset rule includes: Acquire the device identification in the operation data to be repaired and the operation time in the operation data to be repaired; Get the default identifier; Reference operation data corresponding to the operation data to be repaired is generated based on the device identifier in the operation data to be repaired, the operation time in the operation data to be repaired, and the default identifier.

7. The method according to claim 1, characterized in that The method further comprises: Sorting the plurality of first operation data according to the order of operation time to obtain a second sorting result; Determining reference operation data corresponding to the operation data to be repaired from the first operation data based on the operation time and the device identifier of the operation data to be repaired includes: From the second sorting result, searching for the first operation data whose operation time is closest to the operation time of the operation data to be repaired, whose user identifier is not an empty identifier, and whose device identifier is the same as the device identifier of the operation data to be repaired; The first operation data is used as reference operation data corresponding to the operation data to be repaired.

8. The method according to claim 1, characterized in that The obtaining of a plurality of first operation data of the target application includes: Acquire a plurality of original operation data of the target application; The original operation data whose user identification does not conform to the second preset rule is deleted from the plurality of original operation data to obtain a plurality of first operation data of the target application.

9. A data processing device, characterized in that: The device comprises: an acquisition unit, configured to acquire a plurality of first operation data of a target application, each of the first operation data at least including: a device identifier of an operation device, an operation time, and a user identifier of an operation user; The acquisition unit is further configured to acquire the operation data to be repaired in the first operation data, wherein the operation data to be repaired refers to the operation data whose user identifier is a null identifier; a determining unit, configured to determine, from the first operation data, reference operation data corresponding to the operation data to be repaired, based on the operation time and the device identifier of the operation data to be repaired, wherein the user identifier in the reference operation data is not an empty identifier; The replacement unit is used to generate the user identifier in the operation data to be repaired according to the user identifier in the reference operation data, and obtain the repaired operation data corresponding to the operation data to be repaired.

10. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to perform the method of any one of claims 1 to 8 by executing the executable instructions.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images