User behavior data reporting method and system, electronic equipment and medium

Abstract

The embodiment of the invention provides a user behavior data reporting method and system, electronic equipment and a medium, and the method comprises the steps: receiving user behavior data collected by each application program through inter-process communication between applications; carrying out attribute addition on the received user behavior data to obtain target behavior data; determining a corresponding target reporting strategy based on the data type in the attribute information of the target behavior data; and reporting the target behavior data to a cloud through the target reporting strategy. The invention aims to uniformly manage and report user behavior data of all vehicle-mounted terminal applications and save resources.

Description

Technical Field

[0001] The present application relates to the technical field of user behavior data reporting, and in particular to a method, system, electronic device and medium for reporting user behavior data. Background Art

[0002] At present, when existing car-mounted applications collect user behavior data, the SDK directly connects to the cloud and uploads the collected data to the cloud based on the current network channel status and time conditions. However, when uploading data based on time conditions, within the same time conditions, due to user usage frequency and other reasons, a large amount of data may be uploaded at one time, or when the time conditions are met, a small amount of data may be uploaded, resulting in a waste of resources. In addition, the SDKs of multiple apps may perform the same function at the same time, resulting in a waste of resources. Summary of the invention

[0003] In view of this, the embodiments of the present application provide a method, system, electronic device and medium for reporting user behavior data, aiming to uniformly manage and report user behavior data of all vehicle-mounted applications to save resources.

[0004] A first aspect of an embodiment of the present application provides a method for reporting user behavior data, which is applied to a data acquisition engine in a vehicle system, and the method includes:

[0005] Receive user behavior data collected by each application through cross-process communication between applications;

[0006] Add attributes to the received user behavior data to obtain target behavior data;

[0007] Determine the corresponding target reporting strategy based on the data type in the attribute information of the target behavior data;

[0008] The target behavior data is reported to the cloud through the target reporting strategy.

[0009] Optionally, the method further includes:

[0010] Receive reporting policy configuration information sent by the cloud;

[0011] According to the reporting strategy configuration information, a target mapping relationship between the data type of the user behavior data and various reporting strategies is created or updated.

[0012] Optionally, based on the data type in the attribute information of the target behavior data, a corresponding target reporting strategy is determined, including:

[0013] Determine the data type in the attribute information of the target behavior data;

[0014] According to the data type of the target behavior data and the target mapping relationship, a target reporting strategy corresponding to the data type of the target behavior data in the target mapping relationship is determined.

[0015] Optionally, attributes are added to the received user behavior data to obtain target behavior data, including:

[0016] Adding attributes to the received user behavior data to obtain first behavior data;

[0017] Target behavior data is obtained by encrypting the first behavior data.

[0018] Optionally, reporting the target behavior data to the cloud through the target reporting strategy includes:

[0019] Determine whether the target behavior data meets the reporting conditions of its corresponding target reporting strategy;

[0020] If the corresponding reporting conditions are met, determine whether normal communication with the cloud is successfully established;

[0021] When normal communication with the cloud is successfully established, the target behavior data is reported to the cloud.

[0022] Optionally, the method further includes:

[0023] Cache target behavior data;

[0024] Determining whether the target behavior data is reported to the cloud;

[0025] When the target behavior data is uploaded to the cloud, deleting the cached target behavior data;

[0026] When the target behavior data is not uploaded to the cloud, the cached target behavior data is retained.

[0027] Optionally, determining whether the target behavior data is reported to the cloud includes:

[0028] Determine a corresponding reporting duration based on the data volume of the target behavior data;

[0029] Receiving feedback information from the cloud on receiving and obtaining the target behavior data within the reporting time period;

[0030] If the feedback information is not received within the reporting time, it is determined that the target behavior data has not been reported to the cloud, and a report of the target behavior data is retried;

[0031] When the feedback information is received within the reporting time period, it is determined that the target behavior data is reported to the cloud.

[0032] A second aspect of an embodiment of the present application provides a system for reporting user behavior data, the system comprising: a data acquisition engine in a vehicle system, the data acquisition engine comprising a processing module, a processing module and a reporting module;

[0033] The data acquisition engine is used to receive user behavior data collected by various applications through cross-process communication between applications;

[0034] A processing module, used to add attributes to the received user behavior data to obtain target behavior data;

[0035] A configuration module, used to determine a corresponding target reporting strategy based on the data type in the attribute information of the target behavior data;

[0036] The reporting module is used to report the target behavior data to the cloud through the target reporting strategy.

[0037] A third aspect of an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and running on the processor, wherein when the computer program is executed by the processor, the steps in a method for reporting user behavior data as described in the first aspect of the present application are implemented.

[0038] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps in the method for reporting user behavior data as described in the first aspect of the present application are implemented.

[0039] The method for reporting user behavior data provided by this application has the following advantages:

[0040] A method for reporting user behavior data provided by an embodiment of the present application is applied to a data acquisition engine in a car system. First, the data acquisition engine receives user behavior data collected by each application through cross-process communication between applications to uniformly manage the user behavior data of all applications in the car system; then, attributes are added to each received user behavior data to obtain the target behavior data corresponding to each user behavior data; based on the data type of each target behavior data, the corresponding target reporting strategy is determined; finally, the corresponding target behavior data is reported to the cloud through the target reporting strategy. Thus, the present application constructs a data acquisition engine in a car system at the application layer, and then the user behavior data of each application is uploaded to the cloud, and the data acquisition engine uniformly manages and uploads the user behavior data of all applications, so as to effectively avoid the waste of resources caused by the data acquisition SDKs of each application performing the collection of user behavior data and uploading the collected user behavior data to the cloud, and the data acquisition SDKs of multiple applications performing the reporting of user behavior data at the same time, and at the same time, it can avoid the large amount of data uploaded at one time, and avoid the waste of resources caused by the small amount of uploaded data when the time condition is reached. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor.

[0042] Figure 1 A flowchart of a method for reporting user behavior data according to an embodiment of the present application;

[0043] Figure 2 Another flow chart of a method for reporting user behavior data according to an embodiment of the present application;

[0044] Figure 3 A schematic diagram of a system for reporting user behavior data according to an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0046] refer to Figure 1 , Figure 1 This is a schematic diagram of a method for reporting user behavior data according to an embodiment of the present application. Figure 1 As shown, a method for reporting user behavior data provided by the present application is applied to a data acquisition engine in a vehicle system, comprising:

[0047] Step S1: Receive user behavior data collected by each application program through inter-process communication between applications.

[0048] In this embodiment, if Figure 2 As shown, the present application sets up a data acquisition engine at the application layer on the vehicle system side. Each application in the vehicle system has a corresponding user behavior data acquisition SDK. The user behavior data acquisition SDK is used to collect the user behavior data generated by the application corresponding to itself, and then all user behavior data acquisition SDKs send the user behavior data generated by their respective corresponding applications to the data acquisition engine through cross-process communication between applications. Therefore, before the user behavior data generated by all applications in the vehicle system are uploaded to the cloud, the data acquisition engine in the vehicle system uniformly manages and uploads the user behavior data generated by all applications.

[0049] Step S2: Add attributes to the received user behavior data to obtain target behavior data.

[0050] In this embodiment, for all received user behavior data, the data acquisition engine will add attributes to each user behavior data, so that when the cloud receives the user behavior data reported by each data acquisition engine, it can know the source of the user behavior data. Among them, the attributes include but are not limited to vehicle model attributes, SDK version attributes, and VIN attributes. After the user behavior data is added with unified attributes, the user behavior data is the target behavior data, and the target behavior data will be used for subsequent direct reporting.

[0051] Step S3: Determine the corresponding target reporting strategy based on the data type in the attribute information of the target behavior data.

[0052] In this embodiment, in order to adapt to different reporting scenarios, for different types of user behavior data, the data acquisition engine can adopt different reporting strategies to report the corresponding types of user behavior data. For example, for the user behavior data that is more concerned and more important in the cloud, a real-time reporting reporting strategy can be adopted, and for the user behavior data that is not so concerned and not so important in the cloud, a sampling reporting reporting strategy can be adopted. The present application pre-constructs the correspondence between the data type and the reporting strategy of various user behavior data in the data acquisition engine, and then determines the reporting strategy corresponding to the data type based on the data type recorded in the attribute information of the target behavior data. The reporting strategy is the target reporting strategy corresponding to the target behavior data. The data type of the target behavior data includes but is not limited to the data type of click behavior, the data type of browsing behavior, and the data type of search behavior. Reporting strategies include but are not limited to periodic reporting strategies, event-based reporting strategies, and data volume-based reporting strategies. The periodic type reports user behavior data according to the set reporting period, and the reporting period can be configured by yourself; the event type reports user behavior data in real time; the data volume type reports when the amount of collected user behavior data reaches a certain amount, and the size of the data volume can be configured.

[0053] Step S4: Report the target behavior data to the cloud through the target reporting strategy.

[0054] In this embodiment, after the target reporting strategies corresponding to the target behavior data of various data types are determined in step S3, the target behavior data of each data type is reported to the cloud using its corresponding target reporting strategy.

[0055] A method for reporting user behavior data provided in an embodiment of the present application is applied to a data acquisition engine in a vehicle system. First, the data acquisition engine receives user behavior data collected by each application through cross-process communication between applications, so as to uniformly manage the user behavior data of all applications in the vehicle system; then, attributes are added to each received user behavior data to obtain target behavior data corresponding to each user behavior data; based on the data type of each target behavior data, the corresponding target reporting strategy is determined; finally, the corresponding target behavior data is reported to the cloud through the target reporting strategy. Therefore, the present application constructs a data acquisition engine in the vehicle system at the application layer, and then the data acquisition engine uniformly manages and uploads the user behavior data of all applications before the user behavior data of each application is uploaded to the cloud, thereby effectively avoiding the waste of resources caused by the data collection SDKs of each application separately collecting user behavior data and uploading the collected user behavior data to the cloud, and the data collection SDKs of multiple applications reporting user behavior data at the same time. At the same time, it can avoid uploading a large amount of data at one time (because the user behavior data collection SDK of each application reports data independently, and may report data at a certain moment or a certain period of time, resulting in a large amount of data uploaded at one time), and avoid the waste of resources caused by a small amount of uploaded data when the time condition is met.

[0056] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for reporting user behavior data. In the method for reporting user behavior data, the method further includes steps S01 to S02:

[0057] Step S01: Receive reporting strategy configuration information sent by the cloud.

[0058] In this embodiment, since the data is reported to the cloud and given to the cloud for downstream applications, and the cloud is the backend that receives the user behavior data of all vehicle systems, the cloud can know the downstream application requirements and the cloud can control all vehicle systems. Therefore, this application configures the reporting strategy by the cloud, and then sends the reporting strategy configuration information configured by the cloud to the data acquisition engine of each vehicle system for configuration of the reporting strategy. At the same time, since the vehicle systems managed by the cloud involve many vehicle models, the reporting strategies required for different vehicle models or different types of vehicle models may be different. Therefore, when the cloud sends the reporting strategy configuration information to each vehicle system, it can send the corresponding reporting strategy configuration information according to the vehicle model. Among them, the reporting strategy configuration information sent by the cloud includes the corresponding relationship between user behavior data of various data types and various reporting strategies, as well as the configuration information of various reporting strategies, such as the period size can be configured for the periodic reporting strategy (such as reporting every 5 minutes or 10 minutes), and the amount of data reported each time can be configured for the data volume reporting strategy.

[0059] For example, the cloud is configured with corresponding reporting strategy configuration information a1 for vehicle types A and B, and with corresponding reporting strategy configuration information a2 for vehicle type C. The cloud sends the reporting strategy configuration information a1 to the data acquisition engine on the vehicle system of vehicle types A and B, and sends the reporting strategy configuration information a2 to the data acquisition engine on the vehicle system of vehicle type C.

[0060] Step S02: creating or updating a target mapping relationship between the data type of the user behavior data and various reporting strategies according to the reporting strategy configuration information.

[0061] In this embodiment, when the data engine has not established a target mapping relationship between the data type of user behavior data and various reporting strategies, the data acquisition engine creates the initial target mapping relationship between the data type of user behavior data and various reporting strategies based on the reporting strategy configuration information sent by the cloud and received by itself. In the case where the data engine has already established a target mapping relationship between the data type of user behavior data and various reporting strategies, the data acquisition engine updates the target mapping relationship between the data type of user behavior data currently possessed by itself and various reporting strategies based on the reporting strategy configuration information sent by the cloud and received by itself.

[0062] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for reporting user behavior data. In the method for reporting user behavior data, step S3 may include steps S31 to S32:

[0063] Step S31: Determine the data type in the attribute information of the target behavior data.

[0064] In this embodiment, corresponding identification information is set in the attribute information of the user behavior data for different data types. There is a one-to-one correspondence between the data type and the identification information, that is, the identification information of a data type is unique. Based on the identification information in the attribute information of the user behavior data, the data type to which the user behavior data belongs can be determined. The target behavior data is the behavior data obtained after adding attributes to the user behavior data. The identification information set in the attribute information of the user behavior data will be retained in the behavior data. Therefore, the data type of the target behavior data can be determined based on the identification information recorded in the attribute information of the target behavior data.

[0065] Step S32: According to the data type of the target behavior data and the target mapping relationship, determine a target reporting strategy corresponding to the data type of the target behavior data in the target mapping relationship.

[0066] In this embodiment, based on the data type of the target behavior data and the latest target mapping relationship in the data acquisition engine, a reporting strategy corresponding to the data type of the target behavior data can be determined, and the reporting strategy is the target reporting strategy corresponding to the target behavior data.

[0067] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for reporting user behavior data. In the method for reporting user behavior data, step S2 may include steps S21 to S22:

[0068] Step S21: adding attributes to the received user behavior data to obtain first behavior data.

[0069] In this embodiment, in order to improve the reporting security of user behavior data, the data acquisition engine of this application encrypts the user behavior data with added attributes before uploading while adding attributes to the received user behavior data. Specifically: the data acquisition engine will add attributes to each user behavior data, so that when the cloud receives the user behavior data reported by each data acquisition engine, it can know the source of the user behavior data, etc., so as to obtain the first behavior data with added attributes.

[0070] Step S22: Obtain target behavior data by encrypting the first behavior data.

[0071] In this embodiment, the first behavior data with added attributes is encrypted to obtain target behavior data that is ultimately used to be reported to the cloud.

[0072] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for reporting user behavior data. In the method for reporting user behavior data, step S4 may include steps S41 to S43:

[0073] Step S41: Determine whether the target behavior data meets the reporting conditions of the target reporting strategy corresponding to itself.

[0074] In this embodiment, after the data acquisition engine receives and processes a large amount of target behavior data, it is determined whether the target behavior data of various data types meet the reporting conditions of the target reporting strategy corresponding to itself. For example, when the target reporting strategy corresponding to the data type of the target behavior data is a periodic reporting strategy, the time of the last report is determined, and it is determined whether the current cycle duration has been reached. If it has not been reached, it is waited, and when it has been reached, it is determined that the reporting conditions are met. For example, the cycle duration of the periodic reporting strategy is 5 minutes. When the time of the last report is exactly 5 minutes away from the current time, it is determined that the target behavior data of the current data type meets the reporting conditions. For example, when the target reporting strategy corresponding to the data type of the target behavior data is a data volume reporting strategy, the data volume of the current target behavior data of the data type is determined. When the data volume reaches the reported data volume, it is determined that the reporting conditions are met. For example, when the reported data volume of the data volume reporting strategy is 1M, when the current data volume of the data type is greater than or equal to the reported data volume, it is determined that the current target behavior data of the data type meets the reporting conditions.

[0075] Step S42: When the corresponding reporting conditions are met, determine whether normal communication with the cloud is successfully established.

[0076] In this embodiment, when it is determined that the target behavior data of the corresponding data type meets the reporting conditions of the corresponding target reporting strategy, the data acquisition engine further determines whether the vehicle system has successfully established normal communication with the cloud.

[0077] Step S43: When normal communication with the cloud is successfully established, the target behavior data is reported to the cloud.

[0078] In this embodiment, when it is determined that the vehicle system has successfully established normal communication with the cloud, the target behavior data of the corresponding data type is reported to the cloud. For example, when the target behavior data of data type x meets the reporting conditions of the corresponding target reporting strategy, the target behavior data of data type x in the data acquisition engine is reported to the cloud.

[0079] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for reporting user behavior data. In the method for reporting user behavior data, the method further includes steps S5 to S8:

[0080] Step S5: Cache target behavior data.

[0081] In this embodiment, the target behavior data is cached in a designated non-volatile storage space before being reported.

[0082] Step S6: Determine whether the target behavior data is reported to the cloud.

[0083] In this embodiment, the data acquisition engine monitors and determines whether each target behavior data is reported to the cloud.

[0084] Step S7: When the target behavior data is uploaded to the cloud, the cached target behavior data is deleted.

[0085] In this embodiment, when the data acquisition engine monitors and determines that the target behavior data is uploaded to the cloud, the data acquisition engine will delete the target behavior data cached in the non-volatile storage space.

[0086] Step S8: When the target behavior data is not uploaded to the cloud, retain the cached target behavior data.

[0087] In this embodiment, when the data acquisition engine monitors and determines that the target behavior data has not been uploaded to the cloud, the data acquisition engine will continue to retain the target behavior data cached in the non-volatile storage space.

[0088] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for reporting user behavior data. In the method for reporting user behavior data, step S6 may include steps S61 to S64:

[0089] Step S61: Determine the corresponding reporting duration based on the data volume of the target behavior data.

[0090] In this embodiment, the time required to report the target behavior data to the cloud is related to the data volume of the target behavior data. The larger the data volume of a target behavior data, the longer it takes from reporting the target behavior data to completing the reporting. Therefore, this application presets the correspondence between the data volume and the reporting time in advance, and determines the reporting time corresponding to the target behavior data based on the data volume of a single target behavior data and the correspondence between the data volume and the reporting time. For example, for target behavior data with a data volume of 10, the normal reporting time of each target behavior data with a data volume of 10 is statistically analyzed in history, and then the reporting time corresponding to the data volume of 10 is calculated by the corresponding algorithm. The simplest algorithm is to take the maximum value.

[0091] Step S62: receiving feedback information from the cloud on receiving and obtaining the target behavior data within the reporting time period.

[0092] In this embodiment, each target behavior data has unique ID information. When the target behavior data is received in the cloud, the ID information of the target behavior data will be fed back to the data acquisition engine. When the data acquisition engine reports a certain target behavior data, based on the reporting time corresponding to the target behavior data, it is determined whether the ID information of the target behavior data fed back by the cloud is received within the reporting time.

[0093] Step S63: when the feedback information is not received within the reporting time period, it is determined that the target behavior data has not been reported to the cloud, and a retry is performed to report the target behavior data.

[0094] In this embodiment, if the ID information of the target behavior data fed back by the cloud is not received within the reporting time, it is determined that the target behavior data has not been reported to the cloud, and the data acquisition engine re-reports the target behavior data until the preset number of attempts are unsuccessful, then the reporting retry of the target behavior data is terminated. If a set number of target behavior data are not successfully reported to the cloud, and the set number of target behavior data eventually reach the step of terminating the reporting retry of these target behavior data, the data acquisition engine will feedback the abnormal user behavior data reporting to the cloud.

[0095] Step S64: When the feedback information is received within the reporting time period, it is determined that the target behavior data is reported to the cloud.

[0096] In this embodiment, when the ID information of the target behavior data fed back by the cloud is received within the reporting period, it is determined that the target behavior data has been reported to the cloud, and the target behavior data in the non-volatile storage space will be deleted.

[0097] Based on the same inventive concept, an embodiment of the present application provides a system for reporting user behavior data, such as Figure 3 As shown, the system 300 includes: a data acquisition engine 301 in the vehicle system, and the data acquisition engine 301 includes a processing module 3011, a processing module 3012 and a reporting module 3013;

[0098] The data collection engine 301 is used to receive user behavior data collected by various application programs through inter-process communication between applications;

[0099] The processing module 3011 is used to add attributes to the received user behavior data to obtain target behavior data;

[0100] Configuration module 3012, used to determine the corresponding target reporting strategy based on the data type in the attribute information of the target behavior data;

[0101] The reporting module 3013 is used to report the target behavior data to the cloud through the target reporting strategy.

[0102] Optionally, the data acquisition engine includes:

[0103] A receiving module, used to receive reporting policy configuration information sent by the cloud;

[0104] The target mapping relationship creation and update module is used to create or update the target mapping relationship between the data type of the user behavior data and various reporting strategies according to the reporting strategy configuration information.

[0105] Optionally, configuration module 3012 includes:

[0106] A data type determination module, used to determine the data type in the attribute information of the target behavior data;

[0107] The target reporting strategy determination module is used to determine the target reporting strategy corresponding to the data type of the target behavior data in the target mapping relationship according to the data type of the target behavior data and the target mapping relationship.

[0108] Optionally, the processing module 3011 includes:

[0109] An attribute adding module, used for adding attributes to the received user behavior data to obtain first behavior data;

[0110] The encryption module is used to obtain target behavior data by encrypting the first behavior data.

[0111] Optionally, the reporting module 3013 includes:

[0112] A reporting condition determination module is used to determine whether the target behavior data meets the reporting conditions of the target reporting strategy corresponding to itself;

[0113] The communication connection determination module is used to determine whether normal communication with the cloud is successfully established when the corresponding reporting conditions are met;

[0114] The reporting submodule is used to report the target behavior data to the cloud when normal communication with the cloud is successfully established.

[0115] Optionally, the system 300 further includes:

[0116] A storage module, used to cache target behavior data;

[0117] A reporting determination module, used to determine whether the target behavior data is reported to the cloud;

[0118] A data deletion module, used to delete the cached target behavior data when the target behavior data is uploaded to the cloud;

[0119] The data retention module is used to retain the cached target behavior data when the target behavior data is not uploaded to the cloud.

[0120] Optionally, the reporting confirmation module includes:

[0121] A reporting duration determination module, used to determine a corresponding reporting duration based on the data volume of the target behavior data;

[0122] A feedback information receiving module, used for receiving feedback information from the cloud on receiving and obtaining the target behavior data within the reporting time period;

[0123] A reporting retry module, configured to determine that the target behavior data has not been reported to the cloud if the feedback information is not received within the reporting time, and to retry reporting the target behavior data;

[0124] The reporting determination submodule is used to determine that the target behavior data is reported to the cloud when the feedback information is received within the reporting time period.

[0125] Based on the same inventive concept, an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and running on the processor. When the computer program is executed by the processor, it implements the steps in a method for reporting user behavior data as described in the first aspect of the present application.

[0126] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps in a method for reporting user behavior data as described in the first aspect of the present application are implemented.

[0127] As for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the system embodiment.

[0128] It should be noted that, for the method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present application.

[0129] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

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

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

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

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

[0134] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.

[0135] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0136] The above is a detailed introduction to a method, system, electronic device and medium for reporting user behavior data provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for reporting user behavior data, characterized in that: A data acquisition engine applied to a vehicle system, the method comprising: Receive user behavior data collected by each application through cross-process communication between applications; Add attributes to the received user behavior data to obtain target behavior data; Determine the corresponding target reporting strategy based on the data type in the attribute information of the target behavior data; The target behavior data is reported to the cloud through the target reporting strategy.

2. A method for reporting user behavior data according to claim 1, characterized in that: The method further comprises: Receive reporting policy configuration information sent by the cloud; According to the reporting strategy configuration information, a target mapping relationship between the data type of the user behavior data and various reporting strategies is created or updated.

3. A method for reporting user behavior data according to claim 2, characterized in that: Based on the data type in the attribute information of the target behavior data, determine the corresponding target reporting strategy, including: Determine the data type in the attribute information of the target behavior data; According to the data type of the target behavior data and the target mapping relationship, a target reporting strategy corresponding to the data type of the target behavior data in the target mapping relationship is determined.

4. A method for reporting user behavior data according to claim 1, characterized in that: Add attributes to the received user behavior data to obtain target behavior data, including: Adding attributes to the received user behavior data to obtain first behavior data; Target behavior data is obtained by encrypting the first behavior data.

5. A method for reporting user behavior data according to claim 1, characterized in that: Reporting the target behavior data to the cloud through the target reporting strategy includes: Determine whether the target behavior data meets the reporting conditions of its corresponding target reporting strategy; If the corresponding reporting conditions are met, determine whether normal communication with the cloud is successfully established; When normal communication with the cloud is successfully established, the target behavior data is reported to the cloud.

6. A method for reporting user behavior data according to claim 1, characterized in that: The method further comprises: Cache target behavior data; Determining whether the target behavior data is reported to the cloud; When the target behavior data is uploaded to the cloud, deleting the cached target behavior data; When the target behavior data is not uploaded to the cloud, the cached target behavior data is retained.

7. A method for reporting user behavior data according to claim 6, characterized in that: Determining whether the target behavior data is reported to the cloud includes: Determine a corresponding reporting duration based on the data volume of the target behavior data; Receiving feedback information from the cloud on receiving and obtaining the target behavior data within the reporting time period; If the feedback information is not received within the reporting time, it is determined that the target behavior data has not been reported to the cloud, and a report of the target behavior data is retried; When the feedback information is received within the reporting time period, it is determined that the target behavior data is reported to the cloud.

8. A system for reporting user behavior data, characterized in that: The system comprises: a data acquisition engine in a vehicle system, the data acquisition engine comprising a processing module, a processing module and a reporting module; The data acquisition engine is used to receive user behavior data collected by various applications through cross-process communication between applications; A processing module, used to add attributes to the received user behavior data to obtain target behavior data; A configuration module, used to determine a corresponding target reporting strategy based on the data type in the attribute information of the target behavior data; The reporting module is used to report the target behavior data to the cloud through the target reporting strategy.

9. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and running on the processor, wherein the computer program, when executed by the processor, implements the steps in a method for reporting user behavior data as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the method for reporting user behavior data as described in any one of claims 1 to 7 are implemented.

Images