Data processing method and device, electronic equipment and storage medium

Abstract

Embodiments of the present application provide a data processing method and device, electronic equipment and storage medium. The data processing method is executed on a client, and includes: obtaining user behavior data during running of the client; determining whether a target feedback event exists in a pre-embedded feedback event, the target feedback event being a feedback event triggered based on a user behavior corresponding to the user behavior data; and if the target feedback event exists, triggering the target feedback event. In the embodiments of the present application, during running of the client, the user behavior data can be analyzed in real time locally on the client, and a corresponding target feedback event can be triggered for the current user behavior data, so that a real-time feedback effect is generated locally on the client.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to a data processing method and device, electronic equipment and storage medium. BACKGROUND

[0002] With the rapid development of Internet technology, more and more client applications (i.e. application programs) are applied to mobile terminals, and the functions of the client applications are becoming more and more rich. Users can obtain various information through the client applications, such as watching videos and listening to music through the client applications, etc.

[0003] Currently, in various client applications, in order to analyze the behaviors of users in using the client applications, understand the user preferences and user characteristics, the behaviors of users in using the client applications are usually counted and reported to a background server, and the reported user behavior data is analyzed by the background server.

[0004] However, the current data analysis is performed on the server, which is an analysis of historical user behavior data, and cannot perform real-time analysis on current user behavior data, and cannot produce real-time feedback effects for current user behavior data. SUMMARY

[0005] The purpose of the embodiments of the present application is to provide a data processing method and device, electronic equipment and storage medium, so as to realize real-time analysis of current user behavior data on the client, and produce real-time feedback effects for current user behavior data. The specific technical solutions are as follows:

[0006] In the first aspect of the present application, a data processing method is first provided, which is executed on a client, and the method comprises:

[0007] obtaining user behavior data during the running of the client;

[0008] determining whether a target feedback event exists in a pre-embedded feedback event, the target feedback event being a feedback event triggered based on a user behavior corresponding to the user behavior data;

[0009] if the target feedback event exists, triggering the target feedback event.

[0010] Optionally, after obtaining the user behavior data, the method further comprises: reporting the user behavior data to a server.

[0011] Optionally, the judging whether the target feedback event exists in the pre-embedded feedback events comprises: reading a preset configuration file; the configuration file comprises reference user behavior data required for triggering each feedback event; for each feedback event, matching the user behavior data with the reference user behavior data required for triggering the current feedback event, and taking the feedback event with a successful matching as the target feedback event.

[0012] Optionally, the user behavior data comprises an identifier and an occurrence time of the user behavior, and the reference user behavior data comprises an identifier, an occurrence serial number and a valid time interval between a previous reference user behavior of at least one reference user behavior; the matching the user behavior data with the reference user behavior data required for triggering the current feedback event comprises: when no reference user behavior has occurred for the current feedback event, first matching the identifier of the user behavior with the identifier of the reference user behavior with the occurrence serial number of 1; when a reference user behavior has occurred for the current feedback event, second matching the identifier of the user behavior with the identifier of a next reference user behavior of the last occurred reference user behavior; when the second matching is successful, obtaining a time interval between the occurrence time of the user behavior and the occurrence time of the last occurred reference user behavior, and judging whether the time interval is less than or equal to the valid time interval of the next reference user behavior; when the first matching is successful or the time interval is less than or equal to the valid time interval, judging whether the user behavior is the last reference user behavior required for triggering the current feedback event; when the user behavior is not the last reference user behavior, recording the user behavior as the occurred reference user behavior; and when the user behavior is the last reference user behavior, determining that the current feedback event is successfully matched.

[0013] Optionally, before the user behavior data is obtained, the method further comprises: obtaining the configuration file from a server and storing the configuration file to a local; and the reading the preset configuration file comprises: reading the configuration file from the local.

[0014] Optionally, the configuration file further comprises an identifier and parameters of each feedback event; and the triggering the target feedback event comprises: reading the identifier and the parameters of the target feedback event from the configuration file, calling the target feedback event based on the identifier, and executing the target feedback event after the target feedback event is assigned according to the parameters.

[0015] In a second aspect of the embodiments of the present application, a data processing apparatus applied to a client is further provided, and the apparatus comprises:

[0016] a data obtaining module, configured to obtain user behavior data during running of the client.

[0017] a judging module configured to judge whether a target feedback event exists in the pre-embedded feedback events, the target feedback event being a feedback event triggered based on a user behavior corresponding to the user behavior data;

[0018] a triggering module configured to trigger the target feedback event if the judging module judges that the target feedback event exists.

[0019] Optionally, the apparatus further comprises a reporting module configured to report the user behavior data to a server.

[0020] Optionally, the judging module comprises: a reading unit configured to read a preset configuration file; the configuration file comprising reference user behavior data required for triggering each feedback event; and a matching unit configured to, for each feedback event, match the user behavior data with the reference user behavior data required for triggering a current feedback event, and take a feedback event for which the matching is successful as the target feedback event.

[0021] Optionally, the user behavior data comprises an identifier and an occurrence time of the user behavior, and the reference user behavior data comprises an identifier, an occurrence serial number and a valid time interval with a previous reference user behavior of at least one reference user behavior; the matching unit comprises: a first matching sub-unit configured to, when no reference user behavior has occurred for the current feedback event, perform first matching of the identifier of the user behavior with the identifier of a reference user behavior with the occurrence serial number 1; a second matching sub-unit configured to, when a reference user behavior has occurred for the current feedback event, perform second matching of the identifier of the user behavior with the identifier of a next reference user behavior of a last occurred reference user behavior; a time judging sub-unit configured to, when the second matching is successful, acquire a time interval between the occurrence time of the user behavior and the occurrence time of the last occurred reference user behavior, and judge whether the time interval is less than or equal to the valid time interval of the next reference user behavior; a behavior judging sub-unit configured to, when the first matching is successful or the time interval is less than or equal to the valid time interval, judge whether the user behavior is the last reference user behavior required for triggering the current feedback event; and a recording sub-unit configured to, when the user behavior is not the last reference user behavior, record the user behavior as the occurred reference user behavior; and a determining sub-unit configured to, when the user behavior is the last reference user behavior, determine that the current feedback event is matched successfully.

[0022] Optionally, the apparatus further comprises a file acquiring module configured to acquire the configuration file from a server and store the configuration file to a local; and the reading unit is specifically configured to read the configuration file from the local.

[0023] Optionally, the configuration file further comprises an identifier and parameters of each feedback event; the triggering module is specifically configured to read the identifier and parameters of the target feedback event from the configuration file, invoke the target feedback event based on the identifier, and execute the target feedback event after assigning values to the target feedback event according to the parameters.

[0024] In yet another aspect of the embodiments of the present application, an electronic device is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; the memory is configured to store a computer program; and the processor is configured to execute the program stored in the memory to implement the data processing method described above.

[0025] In yet another aspect of the embodiments of the present application, a computer readable storage medium is provided, which stores instructions, and when the instructions are executed on a computer, the computer implements the data processing method described above.

[0026] In yet another aspect of the embodiments of the present application, a computer program product comprising instructions is provided, and when the instructions are executed on a computer, the computer implements the data processing method described above.

[0027] The data processing method, device, electronic device and storage medium provided by the embodiments of the present application can pre-embed feedback events in a client, acquire user behavior data in a running process of the client, determine whether there is a target feedback event triggered by user behavior data corresponding to the user behavior in the pre-embedded feedback events, and trigger the target feedback event if there is. Therefore, in the embodiments of the present application, user behavior data can be analyzed in real time locally in the client in a running process of the client, and a corresponding target feedback event can be triggered according to the current user behavior data, so that a real-time feedback effect is generated locally in the client. BRIEF DESCRIPTION OF DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced.

[0029] Figure 1 A step flowchart of a data processing method in the embodiments of the present application.

[0030] Figure 2 A step flowchart of another data processing method in the embodiments of the present application.

[0031] Figure 3 A step flowchart of a data matching process in the embodiments of the present application.

[0032] Figure 4 A structural block diagram of a data processing device in an embodiment of the present application.

[0033] Figure 5 A structural block diagram of another data processing device in an embodiment of the present application.

[0034] Figure 6 A structural block diagram of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0036] In order to analyze the behavior of a user in the process of using a client, various behavior data of the user will be counted in the process of using the client, and the counted behavior data of the user will be reported to a background server. The behavior data of the user reported is analyzed by the background server, so as to guide product operation and product design.

[0037] In the embodiments of the present application, in order to further utilize the counted behavior data of the user, expand the range of the behavior data of the user, and provide better use experience for the user, real-time analysis is performed on the behavior data of the user locally in the client, and a corresponding feedback event is triggered in real time according to the analysis result, so that the user can execute a corresponding operation more conveniently based on the feedback event.

[0038] The application scenarios of the data processing method in the embodiments of the present application are as follows:

[0039] 1. When a user plays a video, the video is continuously stuttered n times, that is, the counting of the behavior data of continuous n times of stuttering is triggered, and in this case, the display of the stuttering feedback button as a feedback event can be triggered. n is a positive integer.

[0040] 2. When the user quickly enters and exits m different pages, that is, the counting of the behavior data of continuous m times of page exit is triggered, and in this case, the display of the customer service assistant portal as a feedback event can be triggered. m is a positive integer.

[0041] The data processing method and device in the embodiments of the present application can be applied to a client. The client can be various application programs and the like installed on a terminal. The terminal can be a mobile phone, a tablet computer, a notebook computer, a wearable device, and the like.

[0042] Figure 1 A step flowchart of a data processing method in an embodiment of the present application. Figure 1 The data processing method is executed in a client.

[0043] As Figure 1As shown, the data processing method can include the following steps:

[0044] Step 101, during the running of the client, obtaining user behavior data.

[0045] In an optional embodiment, the user behavior data can be obtained through a burying point technology.

[0046] The burying point technology refers to a process of capturing, processing and sending for a specific user behavior or event. The essence of the burying point technology is to listen to events during the running of the client and judge and capture when the event to be concerned occurs. The burying point can be for code, program, etc.

[0047] In the implementation, according to actual needs, related burying points can be added in the client for each user behavior event in advance. The user behavior can include but is not limited to at least one of the following: playing, liking, commenting, downloading, searching, entering a page, exiting a page, page lag, etc. When a user performs a certain user behavior, the burying point corresponding to the user behavior is triggered in advance, and the user behavior data can be obtained according to the burying point. The user behavior data can include but is not limited to at least one of the following: an identifier of the user behavior, a time of occurrence of the user behavior, a type of the user behavior, an identifier of the user, a platform where the user is located, a region where the user is located, etc.

[0048] After obtaining the user behavior data, the client can perform real-time analysis on the user behavior data locally, and perform real-time feedback according to the analysis result locally in the client.

[0049] Step 102, judging whether there is a target feedback event in the pre-buried feedback events.

[0050] A plurality of feedback events are pre-buried in the client, and each feedback event can be triggered based on one or more user behaviors. The feedback event can include but is not limited to at least one of the following: button display, entry display, page display, pop-up window display, page exit, page jump, etc.

[0051] After obtaining the user behavior data, the client judges whether the user behavior corresponding to the user behavior data can trigger a pre-buried feedback event, so as to judge whether there is a target feedback event in the pre-buried feedback events. Therefore, the target feedback event is a feedback event triggered based on the user behavior corresponding to the user behavior data.

[0052] Step 103, if there is, triggering the target feedback event.

[0053] If the target feedback event exists in the pre-embedded feedback event, the client triggers the target feedback event, thereby generating a real-time feedback effect locally on the client. For example, the acquired user behavior data includes a behavior of exiting a page for m times in succession, if the feedback event corresponding to the behavior of exiting a page for m times in succession is displaying a customer service assistant portal, and the feedback event of displaying the customer service assistant portal is a pre-embedded feedback event, it can be determined based on the acquired user behavior data that the feedback event of displaying the customer service assistant portal is a target feedback event, at this time, the client can trigger the feedback event of displaying the customer service assistant portal, so as to display the customer service assistant portal to the user, so that the user can seek help from the customer service assistant in time. If the target feedback event does not exist in the pre-embedded feedback event, the client does not process.

[0054] In the embodiment of the application, during the running of the client, the user behavior data can be analyzed locally and in real time, and the corresponding target feedback event can be triggered according to the current user behavior data, thereby generating a real-time feedback effect locally on the client.

[0055] Figure 2 The step flowchart of another data processing method in the embodiment of the application. Figure 2 The data processing method is executed on the client.

[0056] As shown in the figure, Figure 2 The data processing method can include the following steps:

[0057] Step 201, during the running of the client, acquiring user behavior data.

[0058] Step 202, reporting the user behavior data to a server.

[0059] After the client acquires the user behavior data, the client can write the user behavior data into a user behavior log, and report the user behavior log to a background server according to a preset rule. The process of reporting the user behavior log to the background server according to the preset rule can be reporting the user behavior log to the background server at a time, reporting the user behavior log to the background server in real time, reporting the user behavior log to the background server at a preset time point, etc. The background server analyzes the reported user behavior data, so as to guide product operation, product design, etc.

[0060] Step 203, reading a preset configuration file.

[0061] The client can also analyze the user behavior data locally in real time while reporting the user behavior data to the server, thereby generating a real-time feedback effect locally on the client.

[0062] In the embodiment of the present application, a configuration file is set in advance. The configuration file can include, but is not limited to, the identification and parameters of each feedback event, the reference user behavior data required for triggering each feedback event, and the like. Optionally, the configuration file can be in the form of a table or the like. If it is a table, each item in the table can store the identification and parameters of a feedback event, and the reference user behavior data required for triggering the feedback event.

[0063] The identification of a feedback event can uniquely represent a feedback event. The parameters of a feedback event can include the description information of the feedback event. The description information can include, but is not limited to, at least one of the following: style, content, type, and the like. For example, if the feedback event is a pop-up window display, the parameters of the pop-up window display can include, but are not limited to, the type of the pop-up window, the style of the pop-up window, the content (such as pictures, characters, links, and the like) contained in the pop-up window, and the like.

[0064] The reference user behavior data required for triggering a feedback event can include, but is not limited to, the identification of at least one reference user behavior, the occurrence sequence number of the reference user behavior, and the effective time interval between the reference user behavior and the previous reference user behavior.

[0065] The identification of a reference user behavior can uniquely represent a reference user behavior. The occurrence sequence number of a reference user behavior can indicate that the reference user behavior is effective when it occurs for the first time in all the reference user behaviors required for triggering the feedback event. For example, if the occurrence sequence number of a reference user behavior is 1, it indicates that the reference user behavior needs to occur for the first time in all the reference user behaviors required for triggering the feedback event. The effective time interval between the reference user behavior and the previous reference user behavior can indicate how long the reference user behavior is effective from the previous reference user behavior.

[0066] In an optional embodiment, the configuration file can be saved in a server. During the startup of the client, or when the startup of the client is successful, the client can obtain the configuration file from the server and store the configuration file locally. Therefore, after the client obtains the user behavior data during the running process, the client can read the configuration file from the local, so that the client does not need to read the configuration file from the server every time, the number of interactions between the client and the server is reduced, and resources are saved.

[0067] In step 204, it is judged whether there is a target feedback event in the pre-embedded feedback events based on the configuration file.

[0068] After reading the configuration file, the client can determine whether the user behavior corresponding to the obtained user behavior data can trigger a certain pre-embedded feedback event, so as to determine whether there is a target feedback event in the pre-embedded feedback event. The target feedback event is a feedback event triggered based on the user behavior corresponding to the user behavior data.

[0069] Optionally, in the process of determining whether there is a target feedback event in the pre-embedded feedback event, the client matches the obtained user behavior data with reference user behavior data required for triggering the current feedback event for each feedback event in the configuration file, determines whether there is a feedback event with a successful match, if there is a feedback event with a successful match, determines that there is a target feedback event in the pre-embedded feedback event, and takes the feedback event with a successful match as the target feedback event, and if there is no feedback event with a successful match, determines that there is no target feedback event in the pre-embedded feedback event.

[0070] Reference Figure 3 A step flowchart of a data matching process in an embodiment of the application is shown.

[0071] As shown in Figure 3 , the process of matching the user behavior data with reference user behavior data required for triggering the current feedback event can include the following steps A1-A8:

[0072] A1, determine whether the reference user behavior that has occurred is recorded for the current feedback event. If not, step A2 is performed; if yes, step A3 is performed.

[0073] The client can create corresponding occurred behavior information for the current feedback event. Each time the reference user behavior required for triggering the current feedback event occurs and the reference user behavior meets the corresponding occurrence serial number and valid time interval recorded in the reference user behavior data required for triggering the current feedback event, the client can take the reference user behavior as the occurred reference user behavior corresponding to the current feedback event, and the client records the occurred reference user behavior in the occurred behavior information corresponding to the current feedback event. Optionally, the client can record the occurrence serial number of the occurred reference user behavior, the occurrence time of the occurred reference user behavior, etc.

[0074] Therefore, in the process of matching the currently obtained user behavior data with the reference user behavior data required for triggering the current feedback event, the occurred behavior information corresponding to the current feedback event can be obtained first, and then it is determined whether the occurred reference user behavior is recorded in the occurred behavior information corresponding to the current feedback event. If yes, it is determined that the occurred reference user behavior is recorded for the current feedback event; if not, it is determined that the occurred reference user behavior is not recorded for the current feedback event.

[0075] A2, if no reference user behavior has occurred for the current feedback event, match the identity of the user behavior with the identity of the reference user behavior with occurrence sequence number 1. If the first match is successful, execute step A5; if the first match fails, execute step A8.

[0076] If no reference user behavior has occurred for the current feedback event, match the identity of the user behavior contained in the user behavior data with the identity of the reference user behavior with occurrence sequence number 1, so as to determine whether the user behavior in the user behavior data is the first user behavior required to trigger the current feedback event.

[0077] If the identity of the user behavior contained in the user behavior data is the same as the identity of the reference user behavior with occurrence sequence number 1, it is determined that the first match is successful; if the identity of the user behavior contained in the user behavior data is different from the identity of the reference user behavior with occurrence sequence number 1, it is determined that the first match fails.

[0078] A3, if a reference user behavior has occurred for the current feedback event, match the identity of the user behavior with the identity of the next reference user behavior of the last occurred reference user behavior. If the second match is successful, execute step A4; if the second match fails, execute step A8.

[0079] If a reference user behavior has occurred for the current feedback event, obtain the last occurrence sequence number of the occurred reference user behavior, the reference behavior corresponding to the occurrence sequence number is the last occurred reference user behavior, obtain the identity of the next reference user behavior of the occurrence sequence number from the configuration file, and match the identity of the user behavior contained in the user behavior data with the identity of the next reference user behavior.

[0080] For example, the last occurrence sequence number of the occurred reference user behavior is n, the identity of the reference user behavior with occurrence sequence number n+1 required to trigger the current feedback event is obtained from the configuration file, and the identity of the user behavior contained in the user behavior data is matched with the identity of the reference user behavior with occurrence sequence number n+1.

[0081] If the identity of the user behavior contained in the user behavior data is the same as the identity of the next reference user behavior, it is determined that the second match is successful; if the identity of the user behavior contained in the user behavior data is different from the identity of the next reference user behavior, it is determined that the second match fails.

[0082] A4, obtaining a time interval between the occurrence time of the user behavior and the occurrence time of the last occurred reference user behavior, and determining whether the time interval is less than or equal to the valid time interval of the next reference user behavior. If yes, step A5 is performed; if no, step A8 is performed.

[0083] If the second match is successful in step A3, the time interval between the occurrence time of the user behavior and the occurrence time of the last occurred reference user behavior is further obtained, and it is determined whether the time interval is less than or equal to the valid time interval of the next reference user behavior. If the time interval is less than or equal to the valid time interval of the next reference user behavior, it can be indicated that the user behavior is valid.

[0084] A5, determining whether the user behavior is the last reference user behavior required to trigger the current feedback event. If no, step A6 is performed; if yes, step A7 is performed.

[0085] If the first match is successful in step A2, or it is determined in step A4 that the time interval is less than or equal to the valid time interval of the next reference user behavior, it is determined that the user behavior is the valid user behavior triggering the current feedback event. Therefore, it can be further determined whether the user behavior is the last reference user behavior required to trigger the current feedback event.

[0086] A6, when the user behavior is not the last reference user behavior, the user behavior is recorded as an occurred reference user behavior. Then, step A8 is performed.

[0087] If it is determined in step A5 that the user behavior is the last reference user behavior required to trigger the current feedback event, it indicates that the reference user behavior required to trigger the current feedback event has not been completely validly occurred. Therefore, the user behavior can be recorded as an occurred reference user behavior, and the occurred reference user behavior is recorded into the occurred behavior information corresponding to the current feedback event. Specifically, the occurrence serial number and the occurrence time of the occurred reference user behavior can be recorded. This is used as a basis for matching the subsequently obtained user behavior data with the reference user behavior data required to trigger the current feedback event.

[0088] A7, when the user behavior is the last reference user behavior, it is determined that the current feedback event is matched successfully.

[0089] If it is determined in step A5 that the user behavior is the last reference user behavior required to trigger the current feedback event, it indicates that the reference user behavior required to trigger the current feedback event has been validly occurred. Therefore, it is determined that the current feedback event is matched successfully.

[0090] A8, if the current feedback event matching fails, determining that the target feedback event does not exist.

[0091] Step 205, if the target feedback event exists, triggering the target feedback event.

[0092] If it is determined in step 204 that the target feedback event exists in the pre-embedded feedback event, the target feedback event can be triggered.

[0093] Optionally, the client can read the identifier and parameters of the target feedback event from the configuration file, call the target feedback event based on the identifier, execute the target feedback event after assigning values to the target feedback event according to the parameters. The parameters of the target feedback event can include but are not limited to at least one of the following: style, content, type, etc. For example, if the target feedback event is a pop-up window display, the parameters of the pop-up window display can include but are not limited to: the type of the pop-up window, the style of the pop-up window, the content (such as pictures, characters, links, etc.) contained in the pop-up window, etc.

[0094] If it is determined in step 204 that the target feedback event does not exist in the pre-embedded feedback event, the target feedback event is not triggered, and the client can continue to obtain subsequent user behavior data and repeat the above process.

[0095] Figure 4 A structural block diagram of a data processing device in an embodiment of the present application. Figure 3 The data processing device shown is applied to a client.

[0096] As shown in Figure 4 The data processing device can include the following modules:

[0097] A data acquisition module 301, configured to acquire user behavior data during running of the client;

[0098] A judgment module 302, configured to determine whether a target feedback event exists in pre-embedded feedback events, the target feedback event being a feedback event triggered based on a user behavior corresponding to the user behavior data;

[0099] A triggering module 303, configured to trigger the target feedback event if the judgment module determines that the target feedback event exists.

[0100] Figure 5 A structural block diagram of another data processing device in an embodiment of the present application. Figure 4 The data processing device shown is applied to a client.

[0101] As shown in Figure 5 The data processing device can include the following modules:

[0102] The data acquisition module 401 is configured to acquire user behavior data during running of the client;

[0103] The judgment module 402 is configured to judge whether a target feedback event exists in the pre-embedded feedback events, the target feedback event being a feedback event triggered based on a user behavior corresponding to the user behavior data;

[0104] The trigger module 403 is configured to trigger the target feedback event if the judgment module judges that the target feedback event exists.

[0105] Optionally, the apparatus further comprises a reporting module 404 configured to report the user behavior data to a server.

[0106] Optionally, the judgment module 402 comprises a reading unit 4021 configured to read a preset configuration file, the configuration file comprising reference user behavior data required for triggering each feedback event; and a matching unit 4022 configured to match, for each feedback event, the user behavior data with the reference user behavior data required for triggering a current feedback event, and take a feedback event for which the matching is successful as the target feedback event.

[0107] Optionally, the user behavior data comprises an identifier and an occurrence time of the user behavior, and the reference user behavior data comprises an identifier, an occurrence serial number and a valid time interval between a previous reference user behavior of at least one reference user behavior; the matching unit 4022 comprises a first matching sub-unit configured to perform first matching of the identifier of the user behavior with an identifier of a reference user behavior with an occurrence serial number of 1 when no reference user behavior has occurred for the current feedback event; a second matching sub-unit configured to perform second matching of the identifier of the user behavior with an identifier of a next reference user behavior of a last occurred reference user behavior when a reference user behavior has occurred for the current feedback event; a time judgment sub-unit configured to, when the second matching is successful, acquire a time interval between the occurrence time of the user behavior and an occurrence time of the last occurred reference user behavior, and judge whether the time interval is less than or equal to a valid time interval of the next reference user behavior; a behavior judgment sub-unit configured to, when the first matching is successful or the time interval is less than or equal to the valid time interval, judge whether the user behavior is a last reference user behavior required for triggering the current feedback event; a recording sub-unit configured to, when the user behavior is not the last reference user behavior, record the user behavior as an occurred reference user behavior; and a determination sub-unit configured to, when the user behavior is the last reference user behavior, determine that the current feedback event is matched successfully.

[0108] Optionally, the apparatus further comprises a file acquisition module 405, configured to acquire the configuration file from a server and store the configuration file locally; and the reading unit 4021 is specifically configured to read the configuration file from the local storage.

[0109] Optionally, the configuration file further comprises an identifier and parameters of each feedback event; and the triggering module 403 is specifically configured to read the identifier and parameters of the target feedback event from the configuration file, invoke the target feedback event based on the identifier, and execute the target feedback event after assigning values to the target feedback event according to the parameters.

[0110] In the embodiment of the application, during the running of the client, the user behavior data can be analyzed in real time locally on the client, and the corresponding target feedback event can be triggered according to the current user behavior data, so that a real-time feedback effect is generated locally on the client.

[0111] The embodiment of the application further provides an electronic device, as shown in the figure, comprising a processor 501, a communication interface 502, a memory 503 and a communication bus 504, wherein the processor 501, the communication interface 502 and the memory 503 complete mutual communication through the communication bus 504. Figure 6

[0112] The memory 503 is used for storing a computer program.

[0113] The processor 501 is used for executing the program stored in the memory 503, and the following steps are realized:

[0114] During the running of the client, user behavior data is acquired.

[0115] It is judged whether a target feedback event exists in the pre-embedded feedback events, the target feedback event being a feedback event triggered based on a user behavior corresponding to the user behavior data.

[0116] If the target feedback event exists, the target feedback event is triggered.

[0117] Optionally, after the user behavior data is acquired, the method further comprises the following step: reporting the user behavior data to a server.

[0118] Optionally, the step of judging whether the target feedback event exists in the pre-embedded feedback events comprises the following steps: reading a preset configuration file; the configuration file comprises reference user behavior data required for triggering each feedback event; for each feedback event, the user behavior data is matched with the reference user behavior data required for triggering the current feedback event, and the feedback event with which the matching succeeds is taken as the target feedback event.

[0119] ​Optionally, the user behavior data comprises an identifier and a time of occurrence of the user behavior, and the reference user behavior data comprises an identifier, an occurrence sequence number and a valid time interval with a previous reference user behavior of at least one reference user behavior; the matching of the user behavior data with the reference user behavior data required for triggering the current feedback event comprises: when no reference user behavior has occurred for the current feedback event, first matching the identifier of the user behavior with the identifier of the reference user behavior with the occurrence sequence number of 1; when a reference user behavior has occurred for the current feedback event, second matching the identifier of the user behavior with the identifier of a next reference user behavior of the last occurred reference user behavior; when the second matching is successful, obtaining a time interval between the time of occurrence of the user behavior and the time of occurrence of the last occurred reference user behavior, and judging whether the time interval is less than or equal to the valid time interval of the next reference user behavior; when the first matching is successful or the time interval is less than or equal to the valid time interval, judging whether the user behavior is the last reference user behavior required for triggering the current feedback event; when the user behavior is not the last reference user behavior, recording the user behavior as the reference user behavior that has occurred; and when the user behavior is the last reference user behavior, determining that the current feedback event is matched successfully.

[0120] Optionally, before obtaining the user behavior data, the method further comprises: obtaining the configuration file from the server and storing the configuration file locally; and the reading of the preset configuration file comprises: reading the configuration file from the local.

[0121] Optionally, the configuration file further comprises an identifier and parameters of each feedback event; and the triggering of the target feedback event comprises: reading the identifier and the parameters of the target feedback event from the configuration file, calling the target feedback event based on the identifier, and executing the target feedback event after assigning values to the target feedback event according to the parameters.

[0122] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0123] The communication interface is used for communication between the terminal and other devices.

[0124] The memory can include a random access memory (RAM) and can also include a non-volatile memory such as at least one disk memory. Optionally, the memory can also be at least one storage device located remotely from the aforementioned processor.

[0125] The aforementioned processor can be a general-purpose processor including a central processing unit (CPU), a network processor (NP), etc., and can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components.

[0126] In yet another embodiment provided by the present application, a computer readable storage medium is also provided, which stores instructions therein, and when the instructions are run on a computer, the computer is caused to implement the data processing method according to any one of the above embodiments.

[0127] In yet another embodiment provided by the present application, a computer program product containing instructions is also provided, and when the instructions are run on a computer, the computer is caused to implement the data processing method according to any one of the above embodiments.

[0128] In the embodiments described above, all or some of the steps can be implemented by software, hardware, firmware or any combination thereof. When implemented in software, all or some of the steps can be implemented in the form of one or more computer programs which are stored in a computer readable storage medium. The computer readable storage medium can be located in a computing device which is in operation. These computer programs (which may

[0129] It is to be noted that, in the present document, the terms such as first and second, etc. are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between such entities or operations. Moreover, the terms "comprising", "including", or any other variant are intended to cover a non-exclusive inclusion, such that processes, methods, articles, or apparatuses that comprise a list of elements are not required to include only those elements in the list, but can include other elements not expressly listed, or also include elements inherent in such processes, methods, articles, or apparatuses. Without more limitations, an element defined by the statement "comprising a..." does not exclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0130] Each of the embodiments in the present document is described in a related manner, and the same or similar parts among the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, for the system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the description of the method embodiments.

[0131] The above merely provides the preferred embodiments of the application, and not intended to limit the protection scope of the application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the application shall fall within the protection scope of the application.

Claims

1. A data processing method, characterized by, The method executed on a client comprises: acquiring user behavior data during running of the client; judging whether a target feedback event exists in pre-embedded feedback events, the target feedback event being a feedback event triggered based on a user behavior corresponding to the user behavior data; if the target feedback event exists, triggering the target feedback event; wherein the judging whether the target feedback event exists in the pre-embedded feedback events comprises: for each feedback event, matching the user behavior data with reference user behavior data required for triggering a current feedback event; if the current feedback event has not recorded the reference user behavior that has occurred, matching an identifier of the user behavior with an identifier of a reference user behavior with an occurrence serial number of 1; if the current feedback event has recorded the reference user behavior that has occurred, matching the identifier of the user behavior with an identifier of a next reference user behavior of a last occurred reference user behavior, and judging whether a time interval between an occurrence time of the user behavior and an occurrence time of the last occurred reference user behavior is less than or equal to an effective time interval of the next reference user behavior; if the matching is successful and the time interval meets the condition, judging whether the user behavior is the last reference user behavior, and if yes, determining that the current feedback event is the target feedback event.

2. The method of claim 1, wherein, After acquiring the user behavior data, the method further comprises: reporting the user behavior data to a server.

3. The method of claim 1, wherein, Before the matching the user behavior data with the reference user behavior data required for triggering the current feedback event, the method comprises: reading a preset configuration file, the configuration file comprising reference user behavior data required for triggering each feedback event.

4. The method of claim 3, wherein, The user behavior data comprises an identifier and an occurrence time of the user behavior, and the reference user behavior data comprises an identifier, an occurrence serial number and an effective time interval with a previous reference user behavior of at least one reference user behavior.

5. The method according to claim 3, wherein, before acquiring the user behavior data during running of the client, the method further comprises: acquiring the configuration file from the server and storing the configuration file to a local; the reading the preset configuration file comprises: reading the configuration file from the local.

6. The method of claim 3, wherein, The configuration file further comprises an identifier and parameters of each feedback event, and the triggering the target feedback event comprises: reading the identifier and the parameters of the target feedback event from the configuration file; based on the identifier, calling the target feedback event, and executing the target feedback event after assigning values to the target feedback event according to the parameters.

7. A data processing apparatus, characterized by, The apparatus applied to a client comprises: a data acquisition module configured to acquire user behavior data during running of the client; a judging module configured to judge whether a target feedback event exists in pre-embedded feedback events, the target feedback event being a feedback event triggered based on a user behavior corresponding to the user behavior data; a triggering module configured to trigger the target feedback event if the judging module judges that the target feedback event exists; wherein the judging module comprises: The matching unit is configured to match, for each feedback event, the user behavior data with reference user behavior data required to trigger the current feedback event; The matching unit comprises: A first matching subunit configured to, when no reference user behavior has occurred for the current feedback event, first match the identification of the user behavior with the identification of reference user behavior with an occurrence serial number of 1; A second matching subunit configured to, when reference user behavior has occurred for the current feedback event, second match the identification of the user behavior with the identification of a next reference user behavior of the last occurred reference user behavior; A time judging subunit configured to, when the second matching is successful, acquire a time interval between the occurrence time of the user behavior and the occurrence time of the last occurred reference user behavior, and judge whether the time interval is less than or equal to the valid time interval of the next reference user behavior; A behavior judging subunit configured to, when the first matching is successful or the time interval is less than or equal to the valid time interval, judge whether the user behavior is the last reference user behavior required to trigger the current feedback event; A determining subunit configured to, when the user behavior is the last reference user behavior, determine that the current feedback event is matched successfully.

8. The apparatus of claim 7, wherein, The device further comprises: A reporting module configured to report the user behavior data to a server.

9. An electronic device, comprising: The device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus; The memory is configured to store a computer program; The processor is configured to execute the program stored on the memory, and realize the method according to any one of claims 1-6.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to realize the method according to any one of claims 1-6.

Images