Method, system, electronic device and storage medium for collecting buried data

Abstract

The present application relates to the field of data processing, and provides a method, system, electronic device and storage medium for collecting buried point data. The method is applied to a first buried point tracking application; the first buried point tracking application can be installed in a first virtual machine corresponding to a first operating system; the first virtual machine also includes an internal integrated public software library, and the integrated public software library can be installed in the first virtual machine; the method includes: if the data collection request includes first identification information, the internal buried point data sent by the internal buried point application is collected through an internal transmission channel; if the data collection request includes second identification information, the external buried point data sent by the second buried point tracking application is collected through an external transmission channel; the second buried point tracking application can be installed in a second virtual machine corresponding to a second operating system. The data collection architecture of the present application has good portability and versatility, less external dependence, easy adaptation to different operating systems, high data collection efficiency and good system performance.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, system, electronic device and storage medium for collecting buried data. Background Art

[0002] With the continuous development of information and intelligent technologies, the functions of vehicle-mounted systems are becoming more and more abundant and complex, and the amount of vehicle-mounted data related to vehicle-mounted systems is also increasing dramatically, which makes traditional data collection methods face many challenges.

[0003] For example, the traditional data collection method uses a data collection architecture that is highly coupled to the system program, so it has poor portability and versatility, is highly dependent on external factors, and is difficult to adapt to various operating systems; in addition, the data collection efficiency is low and the system performance is poor.

[0004] Therefore, the existing technology still needs to be improved and developed. Summary of the invention

[0005] In view of this, the embodiments of the present application provide a method, system, electronic device and storage medium for collecting data of buried points, so as to solve the problems that the data collection architecture adopted by the traditional data collection method has poor portability and versatility, multiple external dependencies, difficulty in adapting to various operating systems, low data collection efficiency and poor system performance.

[0006] In a first aspect of an embodiment of the present application, a method for collecting buried point data is provided, which is applied to a first buried point tracking application; the first buried point tracking application can be installed in a first virtual machine corresponding to a first operating system; the first virtual machine also includes an internal buried point application and an internal integrated public software library, and the integrated public software library can be installed in the first virtual machine; the first buried point tracking application includes an internal buried point tracking class and an external buried point tracking class; the first buried point tracking application encapsulates a first buried point function program for collecting, processing and reporting internal buried point data and external buried point data;

[0007] The method comprises the following steps:

[0008] Get the data collection request sent by the data demand side;

[0009] If the data collection request includes first identification information corresponding to the first operating system, an internal transmission channel is established between the internal burying point tracking class and the internal burying point application, and the internal burying point data sent by the internal burying point application is collected through the internal transmission channel;

[0010] If the data collection request includes second identification information corresponding to the second operating system, an external transmission channel is established between the external tracking class and the second tracking application corresponding to the second operating system, and the external tracking data sent by the second tracking application is collected through the external transmission channel; wherein the second tracking application is portable and installed in a second virtual machine corresponding to the second operating system; the second tracking application is encapsulated with a second tracking function program for realizing the collection and reporting of external tracking data.

[0011] A second aspect of the embodiment of the present application provides a point-of-sale data collection system, including:

[0012] a first virtual machine corresponding to the first operating system, and a second virtual machine corresponding to the second operating system;

[0013] The first virtual machine includes an internal point tracking application, an internal integrated public software library and a first point tracking application; the first point tracking application includes an internal point tracking class and an external point tracking class; the first point tracking application can be portable and installed in the first virtual machine; the first point tracking application encapsulates a first point tracking function program for collecting, processing and reporting internal point data and external point data;

[0014] The second virtual machine includes a second burying point tracking application, which can be transplanted and installed in the second virtual machine; the second burying point tracking application encapsulates a second burying point function program for collecting and reporting external burying point data;

[0015] The first tracking application is configured as follows:

[0016] Get the data collection request sent by the data demand side;

[0017] If the data collection request includes first identification information corresponding to the first operating system, an internal transmission channel is established between the internal burying point tracking class and the internal burying point application, and the internal burying point data sent by the internal burying point application is collected through the internal transmission channel;

[0018] If the data collection request includes second identification information corresponding to the second operating system, an external transmission channel is established between the external tracking class and the second tracking application corresponding to the second operating system, and the external tracking data sent by the second tracking application is collected through the external transmission channel.

[0019] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0020] According to a fourth aspect of an embodiment of the present application, a readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0021] Compared with the prior art, the beneficial effects of the embodiments of the present application include at least the following: by encapsulating the first tracking point function program for realizing the core functions such as the collection, processing and reporting of internal tracking point data and external tracking point data in the first tracking point tracking application, the first tracking point function program in the first virtual machine corresponding to the first operating system can be decoupled from other system programs; and the first tracking point tracking application can be portable and installed in the first virtual machine corresponding to the first operating system, with good portability, good versatility and less external dependence, thereby greatly reducing the difficulty of adapting to various different operating systems. By encapsulating the second tracking point function program for realizing the core functions such as the collection and reporting of external tracking point data in the second tracking point tracking application, the second tracking point function program in the second virtual machine corresponding to the second operating system can be decoupled from other system programs; and the second tracking point tracking application can be portable and installed in the second virtual machine corresponding to the second operating system, with good portability, good versatility and less external dependence, thereby greatly reducing the difficulty of adapting to various different operating systems.

[0022] Through the first identification information carried in the data collection request, an internal transmission channel is established between the internal point tracking class and the internal point tracking application, and then the internal point data is collected through the internal transmission channel; through the second identification information carried in the data collection request, an external transmission channel is established between the external point tracking class and the second point tracking application, and then the point data is collected through the external transmission channel. This is conducive to improving the collection efficiency of internal and external point data, and improving the system performance of the point data collection architecture. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art 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 paying any creative work.

[0024] Figure 1 It is a schematic diagram of a data collection architecture of a buried point in an embodiment of the present application;

[0025] Figure 2 It is a flow chart of a method for collecting data of buried points provided in an embodiment of the present application;

[0026] Figure 3 This is a data flow diagram of a point-of-sale data collection architecture provided in an embodiment of the present application;

[0027] Figure 4 It is a schematic diagram of an internal point-of-sale data collection process in the point-of-sale data collection method provided in an embodiment of the present application;

[0028] Figure 5 This is a schematic diagram of an external point data collection process in the point data collection method provided in an embodiment of the present application;

[0029] Figure 6 It is a data queue processing timing diagram in the buried point data collection method provided in the embodiment of the present application;

[0030] Figure 7 This is a data flow diagram of another point-of-sale data collection architecture provided in an embodiment of the present application;

[0031] Figure 8 It is a structural diagram of a buried point data acquisition system provided in an embodiment of the present application;

[0032] Fig. 9 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0034] A method and system for collecting buried data according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0035] Figure 1 is a schematic diagram of a data collection architecture for tracking points provided in an embodiment of the present application. Figure 1 The tracking point data collection architecture includes a first operating system 101, a second operating system 102 and a hardware hypervisor 103.

[0036] Among them, the first operating system 101 can be an Android operating system (Android operating system). The second operating system 102 can be a QNX (Quick Unix) operating system. The QNX operating system can be applied to the vehicle-mounted system of a vehicle (such as a new energy vehicle, etc.). The vehicle-mounted system mainly includes: ① In-Vehicle Infotainment (IVI), which provides functions such as audio, video and navigation; ② In-Vehicle Communication System, including V2V communication between vehicles and V2I communication between vehicles and infrastructure; ③ Intelligent Driving Assistance System (ADAS), such as automatic parking, adaptive cruise control, lane keeping, collision warning, etc.; ④ On-Board Diagnostic System (OBD), used to monitor the operating status of the vehicle and diagnose faults; ⑤ In-Vehicle Network System, which realizes the connection and data exchange between various components inside the vehicle and the external network.

[0037] A first virtual machine corresponding to the first operating system 101 and a second virtual machine corresponding to the second operating system 102 can be virtualized through a hardware hypervisor 103 .

[0038] The first virtual machine includes but is not limited to: a first tracking application (such as Figure 1 Tracker APP in ), internal tracking applications (such as Figure 1 Other APP in ), internal integrated public software libraries (such as Figure 1 SDK (Software Development Kit) in the software development kit.

[0039] The first tracking application (Tracker APP) includes but is not limited to: data receiving class (such as Figure 1 DataRevice in), data processing classes (such as Figure 1 DataHandle in ), extended integration public software libraries (such as Figure 1 The ExtendSDK in the system (also called the third-party SDK), the system's network management tools (such as Figure 1 NetworkUtils in ), system file management classes (such as Figure 1 FileManager in ), data upload class (such as Figure 1 UploadTracker in ), global classes (such as Figure 1 Configuration in), interaction classes (such as Figure 1 in the Interaction section).

[0040] The data receiving class (DataRevice) is mainly used to receive the internal tracking data recorded by the internal tracking application of the first virtual machine and the external tracking data recorded by the second tracking application of the second virtual machine.

[0041] The data processing class (DataHandle) is mainly used to process the collected internal and external buried point data, for example, to classify, encrypt, and compress the data.

[0042] The system's network management tool class (NetworkUtils) is mainly used to manage the network of the second operating system to ensure the stability and reliability of the second operating system, thereby ensuring the reliability of uploading external tracking data. If the second operating system is the QNX operating system deployed in the vehicle system, the network of the second operating system includes WiFi, etc.

[0043] The data upload class (UploadTracker) is mainly used to upload the collected tracking point data to the data demand side (such as TSP cloud).

[0044] The data collection architecture of the embodiment of the present application can support docking with a third-party SDK (ExtendSDK), and the architecture has good compatibility and scalability.

[0045] The second virtual machine includes but is not limited to: the second tracking application (such as Figure 1 Tracker on the QNX side in ).

[0046] Figure 2 It is a flow chart of a method for collecting data from a buried point provided in an embodiment of the present application. Figure 2 The buried point data collection method can be Figure 1 The first point tracking application is executed in the first virtual machine corresponding to the first operating system 101.

[0047] The first burial point tracking application is portable and installable in the first virtual machine corresponding to the first operating system; the first virtual machine also includes an internal burial point application and an internal integrated public software library, and the integrated public software library is portable and installable in the first virtual machine; the first burial point tracking application includes an internal burial point tracking class and an external burial point tracking class; the first burial point tracking application encapsulates a first burial point function program for realizing the collection, processing and reporting of internal burial point data and external burial point data.

[0048] like Figure 2 As shown, the method for collecting buried point data includes the following steps:

[0049] Step S201, obtaining a data collection request sent by a data demand side.

[0050] The data demand side (such as TSP cloud) can communicate and interact with the first operating system 101 through a network (such as a wireless network or a wired network) and send a data collection request to the first operating system 101. The first tracking application (Tracker APP) of the first virtual machine corresponding to the first operating system 101 responds to the data collection request of the data demand side.

[0051] Step S202: If the data collection request includes first identification information corresponding to the first operating system, an internal transmission channel is established between the internal burying point tracking class and the internal burying point application, and the internal burying point data sent by the internal burying point application is collected through the internal transmission channel.

[0052] The first identification information may be numbers, words, letters or other symbols. For example, if the first operating system 101 is an Android operating system, the first identification information may be "Android".

[0053] Figure 3 It is a data flow diagram of a point-of-care data collection architecture provided in an embodiment of the present application.

[0054] See also Figure 3 If the data collection request sent by the data demand end includes the first identification information, the first tracking application (Tracker APP) establishes an internal tracking class (such as Figure 3 App TrackerService in the Figure 3 The internal transmission channel can be AIDL (Android Interface Definition Language). After that, the internal tracking application can report the internal tracking data to the internal tracking tracking class through the internal transmission channel (such as AIDL). Internal tracking data refers to the data tracking information of the application layer of the internal tracking application (including SystemUI, Map, Radio, BTControl, Media, etc.). SDKs are deployed in SystemUI, Map, Radio, BTControl, and Media. SystemUI, Map, Radio, BTControl, and Media can send internal tracking data to the internal tracking class (App TrackerService) in the first tracking application (Tracker APP) by calling the interface provided in the SDK (i.e. platform.jar).

[0055] Step S203, if the data collection request includes second identification information corresponding to the second operating system, an external transmission channel is established between the external tracking class and the second tracking application corresponding to the second operating system, and the external tracking data sent by the second tracking application is collected through the external transmission channel; wherein the second tracking application is portable and installed in a second virtual machine corresponding to the second operating system; the second tracking application is encapsulated with a second tracking function program for realizing the collection and reporting of external tracking data.

[0056] The second identification information may be numbers, words, letters or other symbols. For example, if the second operating system is a QNX operating system, the second identification information may be "QNX".

[0057] See also Figure 3 If the data collection request sent by the data demand end includes the second identification information, the first tracking application (Tracker APP) establishes an external tracking class (such as Figure 3 QNX TrackerService in the second operating system) and the second tracking application in the second virtual machine of the second operating system (such as Figure 3 The external transmission channel is an external transmission channel between the TrackerService on the QNX side of the second operating system. The external transmission channel can be a socket transmission channel that supports the TCP / IP protocol. Afterwards, the second tracking application can transmit the external tracking data to the external tracking class of the first tracking application through the external transmission channel. The external tracking data refers to the data tracking information collected by the second tracking application from the application layer (Application) of the second operating system.

[0058] The technical solution provided in the embodiment of the present application can realize the decoupling of the first burying point function program in the first virtual machine corresponding to the first operating system from other system programs by encapsulating the first burying point function program for realizing the core functions such as the collection, processing and reporting of internal burying point data and external burying point data in the first burying point tracking application; and the first burying point tracking application can be installed in the first virtual machine corresponding to the first operating system, with good portability, good versatility and less external dependence, thereby greatly reducing the difficulty of adapting to various different operating systems. By encapsulating the second burying point function program for realizing the core functions such as the collection and reporting of external burying point data in the second burying point tracking application, the decoupling of the second burying point function program in the second virtual machine corresponding to the second operating system from other system programs can be realized; and the second burying point tracking application can be installed in the second virtual machine corresponding to the second operating system, with good portability, good versatility and less external dependence, thereby greatly reducing the difficulty of adapting to various different operating systems.

[0059] Through the first identification information carried in the data collection request, an internal transmission channel is established between the internal point tracking class and the internal point tracking application, and then the internal point data is collected through the internal transmission channel; through the second identification information carried in the data collection request, an external transmission channel is established between the external point tracking class and the second point tracking application, and then the point data is collected through the external transmission channel. This is conducive to improving the collection efficiency of internal and external point data, and improving the system performance of the point data collection architecture.

[0060] In some embodiments, establishing an internal transmission channel between an internal tracking class and an internal tracking application includes:

[0061] Receive an internal connection request sent by the internal tracking application by calling the tracking management class, connection management class and tracking acceptance class in the internal integrated public software library;

[0062] In response to the internal connection request of the internal tracking application, an internal transmission channel is established between the internal tracking class and the internal tracking application.

[0063] Figure 4 It is a schematic diagram of an internal point-of-sale data collection process in the point-of-sale data collection method provided in an embodiment of the present application.

[0064] As an example, see Figure 3 and Figure 4, the internal tracking application (Other APP) integrates the jar package of SDK (internal integration public software library), calls the initialization init method, calls the tracking management class (TrackerManager) in the SDK; calls the connection management class (AidlConnectManger) through the tracking management class (TrackerManager), calls attemptToBindService to call onServiceConnect to call the tracking receiving class (TrackerReceiver); calls bindService through the tracking receiving class (TrackerReceiver) to try to bind the internal tracking class (AppTrackerService) in the first tracking application through AIDL, that is, send an internal connection request to the internal tracking class (AppTrackerService). When the internal tracking application (Other APP) and the tracking class (AppTrackerService) are successfully bound, an internal transmission channel between them is established. After successfully establishing the internal transmission channel between the internal tracking application (Other APP) and the internal tracking class (AppTrackerService), the internal tracking application (Other APP) can call the transfer interface (transfer) to pass the internal tracking data to the tracking management class (TrackerManager) of the SDK. The tracking management class (TrackerManager) verifies the internal tracking data. After the verification passes, it continues to call the transfer interface (transfer) to call the tracking receiving class (TrackerReceiver). The tracking receiving class (TrackerReceiver) calls transferMsg and calls the tracking service intelligent class (TrackerAgent) of the tracking service process. The tracking service intelligent class (TrackerAgent) calls the instance buffer class (bufferEvent) to process the received internal tracking data.

[0065] In some embodiments, establishing an external transmission channel between the external tracking class and the second tracking application corresponding to the second operating system includes:

[0066] Initialize the external tracking class;

[0067] Call the message management class through the external tracking class to start the datagram socket class and the message management thread class;

[0068] An external transmission channel is established between the external point tracking class and the second point tracking application corresponding to the second operating system through the message management class, the datagram socket class and the message management thread class.

[0069] Figure 5 It is a schematic diagram of an external point-of-sale data collection process in the point-of-sale data collection method provided in an embodiment of the present application.

[0070] As an example, see Figure 3 and Figure 5 The first tracking application (TrackerAPP) of the first operating system 101 initializes the external tracking class (QNX Tracker Service), and the external tracking class (QNX TrackerService) calls the initialization init method, initPManger method and initNetwork method, and calls the message management class (PpmsgManager); the message management class (PpmsgManager) starts the datagram socket class (DatagramSocket) and the message management thread class (PpmsgManagerTimerThread) to establish an external transmission channel between the external tracking class (QNX TrackerService) and the second tracking application (Tracker Service on the QNX side) corresponding to the second operating system.

[0071] In some embodiments, an external transmission channel between an external tracking class and a second tracking application corresponding to a second operating system is established through a message management class, a datagram socket class, and a message management thread class, including:

[0072] Calling the datagram socket class and the message management thread class through the message management class to forward the ready status message sent by the external tracking class to the second tracking application;

[0073] If a connection response message based on the feedback of the preparation status message from the second tracking application is received, the external transmission channel between the external tracking class and the second tracking application is established.

[0074] To make it easier to understand, continue using the above example, see Figure 3 and Figure 5, the external tracking point class (QNX Tracker Service on the first operating system 101 side) sends the preparation status message (i.e., preparation completion message) to the message management class (PpmsgManager) through the send method by calling the registerReceiver method; the message management class (PpmsgManager) passes the preparation status message sent by the external tracking point class (QNX TrackerService) to the second tracking point application (Tracker Service on the QNX side) through the external transmission channel (socket transmission channel). After receiving the preparation status message, the second tracking point application (Tracker Service on the QNX side) feeds back a connection response message (such as an ACK message) to the external tracking point class (QNX Tracker Service) to complete the establishment of an external transmission channel between the external tracking point class and the second tracking point application.

[0075] After successfully establishing the external transmission channel between the external tracking class and the second tracking application, the second tracking application (Tracker Service (.so) on the QNX side) collects the external tracking data (buffer data converted from json string) of the application layer of the second operating system (application on the QNX side); then, the second tracking application (Tracker Service (.so) on the QNX side) transmits the external tracking data to the message management thread class (PpmsgManagerTimerThread) through the external transmission channel; the message management thread class (PpmsgManagerTimerThread) receives the external tracking data sent by the second tracking application (Tracker Service (.so) on the QNX side) through the while loop recvRunnable thread, and passes it to the datagram socket class (DatagramSocket). The external tracking data is passed to the external tracking class (QNX Tracker Service) through the datagram socket class (DatagramSocket) and the message management class (PpmsgManager).

[0076] In some embodiments, the first tracking application further includes a tracking intelligent service class, a data processing class, a system file management class, and a data upload class;

[0077] After collecting the external tracking data sent by the second tracking application through the external transmission channel, it also includes:

[0078] The external tracking point class transfers the external tracking point data collected from the external transmission channel to the tracking point intelligent service class;

[0079] Call the tracking point intelligent service class to pass the external tracking point data to the data processing class;

[0080] Call the data processing class to process the external tracking data and obtain the tracking data to be uploaded;

[0081] Call the system file management class to write the buried data to be uploaded into the file to be uploaded;

[0082] Call the data upload class to upload the file to be uploaded to the data demand side.

[0083] As an example, see Figure 3 and Figure 5 , the external tracking point class (QNX Tracker Service) calls the transfer interface (transfer) to pass the received external tracking point data to the tracking point service intelligent class (TrakerAgent). The first tracking point application (Tracker APP) calls the tracking point intelligent service class (TrakerAgent) to pass the external tracking point data to the data processing class (DataHandle). The first tracking point application (Tracker APP) calls the data processing class (DataHandle) to process these external tracking point data (such as data classification, encryption, compression, etc.) to obtain the tracking point data to be uploaded. The first tracking point application (Tracker APP) calls the system file management class (FileManager) to write the tracking point data to be uploaded into the file to be uploaded. The first tracking point application (Tracker APP) calls the data upload class (Upload) to upload the file to be uploaded to the data demand side (such as TSP).

[0084] In some implementations, the data processing class (DataHandle) processes the collected external tracking data to obtain the tracking data to be uploaded, which may specifically include:

[0085] Extract the tracking point label information carried by the external tracking point data;

[0086] Determine the data queue corresponding to the tracking point label information;

[0087] Taking out the external buried point data from the data queue, and encrypting the external buried point data to obtain the encrypted external buried point data;

[0088] The encrypted external tracking data is compressed to obtain the tracking data to be uploaded.

[0089] Among them, the embedding tag information can be configured according to the business demand information in the data collection request sent by the data demand side. For example, if the business demand information is to collect driving-related data, then the embedding tag information can be configured as "Drive". For another example, if the business demand information is to collect entertainment, music, news, video playback and other related data, then the embedding tag information can be configured as "Media".

[0090] As an example, if the data demand side (such as the cloud) needs to analyze the driver behavior data, and its business demand information is to collect driving-related data, then the data demand side can send a data collection request to the first point tracking application, and the data collection request includes the business demand information and the first identification information. When the first point tracking application receives the data collection request, it determines that the point tag information corresponding to the business demand information is "Drive"; then, the first point tracking application calls the external point tracking class (QNX Tracker Service) to collect external point data carrying the point tag information "Drive" from the QNX side, and the external point tracking class (QNX Tracker Service) stores the collected external point data in the data queue with the "Drive" identification. The first point tracking application calls the data processing class (DataHandle) to encrypt the external point data in the data queue with the "Drive" identification to obtain encrypted external point data; then the encrypted external point data is compressed to obtain the point data to be uploaded. After receiving the buried data to be uploaded, the data demand side can directly analyze it based on the buried data to be uploaded, without having to filter external buried data related to the driver behavior data, which is conducive to improving the data analysis efficiency of the data demand side.

[0091] It can be understood that the collected internal burial point data can be processed by referring to the processing flow of the data processing class (DataHandle) for processing the collected external burial point data, which will not be repeated here.

[0092] Before uploading the file to be uploaded, the file to be uploaded can be compressed before uploading, so as to improve the efficiency of file uploading.

[0093] By calling the data processing class (DataHandle) to classify, encrypt, compress and process external buried data, the security and reliability of data transmission can be improved.

[0094] In some embodiments, calling a data processing class to process external tracking data to obtain tracking data to be uploaded includes:

[0095] Call the tracking point intelligent service class to pass the external tracking point data to the tracking point data buffer queue;

[0096] Call the data processing class, take out the external buried point data to be processed from the data buffer queue, and classify and encrypt it to obtain the buried point data to be uploaded.

[0097] Figure 6 It is a data queue processing timing diagram in the point-of-care data collection method provided in an embodiment of the present application.

[0098] As an example, see Figure 3 and Figure 6 , first, the tracking application (Tracker APP) calls the tracking intelligent service class (TrakerAgent); the tracking intelligent service class (TrakerAgent) calls the transferMsg, bufferevent, and offerevent methods to pass the external tracking data to the tracking data buffer queue. The tracking data buffer queue is managed by the queue controller (QueueController). The queue controller (QueueController) calls filterDurationEvent, joins the system data processing, and calls the LimitQueue class to maintain a Queue queue (i.e., the tracking data buffer queue). The queue size of the Queue queue can be set according to the actual situation (for example, the queue size is 200). When the data queue in the Queue queue exceeds the preset queue size (such as 200), the first data added to the Queue queue will be cleared. The tracking intelligent service class (TrakerAgent) can take out the external tracking data from the tracking data buffer queue and call the sendEmptyMessageDelayed method to upload (startUpload) to the data processing class (DataHandle) in a loop.

[0099] Next, the data processing class (DataHandle) classifies and encrypts the external buried point data to be processed from the data buffer queue to obtain the buried point data to be uploaded. Specifically, the data processing class (DataHandle) can classify the external buried point data taken out according to the preset data classification rules, and then use the encryption algorithm to encrypt the classified data to obtain the buried point data to be uploaded.

[0100] The preset data classification rule may be classified according to the point-of-use identifier or the collection object. For example, if the collection object includes the application layer of the second operating system and the application layer of the first operating system, the point-of-use data collected from the application layer of the second operating system may be classified into one category, and the point data collected from the application layer of the first operating system may be classified into another category.

[0101] The encryption algorithm may be MD5 encryption algorithm, DES encryption algorithm, AES encryption algorithm, etc.

[0102] In some embodiments, the first tracking application further includes an extended integrated public software library;

[0103] The method also includes:

[0104] If the data collection request includes third identification information corresponding to the external device, establishing a data transmission channel between the device application of the external device based on the extended integrated public software library;

[0105] The device tracking data sent by the device application of the external device is collected through the data transmission channel.

[0106] The third identification information may be numbers, words, letters or other symbols. For example, if the external device is ExendService, the third identification information may be "Exend".

[0107] Figure 7 It is a data flow diagram of another point-of-care data collection architecture provided in an embodiment of the present application.

[0108] See also Figure 7 , the first tracking application (Tracker APP) also includes an extended integrated public software library (ExendSDK). If the data collection request sent by the data demand side includes the third identification information (for example, "Exend"), then the first tracking application (Tracker APP) can use the various SDKs in the extended integrated public software library (Exend SDK) to establish a data transmission channel with each application of the external device. After successfully establishing the data transmission channel with each application of the external device, the device tracking data of each application of the external device is collected through each data transmission channel. The first tracking application (Tracker APP) calls the data processing class (DataHandle) to process the received device tracking data, and then calls the system file management class (FileManager) to write the processed device tracking data into the file to be uploaded, and then calls the data upload class (UploadTracker) to upload the file to be uploaded to the data demand side (such as TSP). Exemplarily, the data upload class (UploadTracker) can upload the file to be uploaded through https or mqtt request.

[0109] Among them, the extended integrated public software library can be a third-party SDK, such as Sensors SDK.

[0110] The data collection architecture provided by the embodiment of the present application can support and be compatible with third-party SDKs, and has good scalability, compatibility and system performance.

[0111] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0112] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0113] Figure 8 Schematic diagram of a data collection system for buried points provided in an embodiment of the present application. Figure 8 As shown, the buried point data acquisition system includes:

[0114] a first virtual machine corresponding to the first operating system, and a second virtual machine corresponding to the second operating system;

[0115] The first virtual machine includes an internal point tracking application, an internal integrated public software library and a first point tracking application; the first point tracking application includes an internal point tracking class and an external point tracking class; the first point tracking application can be portable and installed in the first virtual machine; the first point tracking application encapsulates a first point tracking function program for collecting, processing and reporting internal point data and external point data;

[0116] The second virtual machine includes a second burying point tracking application, which can be transplanted and installed in the second virtual machine; the second burying point tracking application encapsulates a second burying point function program for collecting and reporting external burying point data;

[0117] The first tracking application is configured as follows:

[0118] Get the data collection request sent by the data demand side;

[0119] If the data collection request includes first identification information corresponding to the first operating system, an internal transmission channel is established between the internal burying point tracking class and the internal burying point application, and the internal burying point data sent by the internal burying point application is collected through the internal transmission channel;

[0120] If the data collection request includes second identification information corresponding to the second operating system, an external transmission channel is established between the external tracking class and the second tracking application corresponding to the second operating system, and the external tracking data sent by the second tracking application is collected through the external transmission channel.

[0121] In some embodiments, establishing an internal transmission channel between an internal tracking class and an internal tracking application includes:

[0122] Receive an internal connection request sent by the internal tracking application by calling the tracking management class, connection management class and tracking acceptance class in the internal integrated public software library;

[0123] In response to the internal connection request of the internal tracking application, an internal transmission channel is established between the internal tracking class and the internal tracking application.

[0124] In some embodiments, establishing an external transmission channel between the external tracking class and the second tracking application corresponding to the second operating system includes:

[0125] Initialize the external tracking class;

[0126] Call the message management class through the external tracking class to start the datagram socket class and the message management thread class;

[0127] An external transmission channel is established between the external point tracking class and the second point tracking application corresponding to the second operating system through the message management class, the datagram socket class and the message management thread class.

[0128] In some embodiments, an external transmission channel between an external tracking class and a second tracking application corresponding to a second operating system is established through a message management class, a datagram socket class, and a message management thread class, including:

[0129] Calling the datagram socket class and the message management thread class through the message management class to forward the ready status message sent by the external tracking class to the second tracking application;

[0130] If a connection response message based on the feedback of the preparation status message from the second tracking application is received, the external transmission channel between the external tracking class and the second tracking application is established.

[0131] In some embodiments, the first tracking application further includes a tracking intelligent service class, a data processing class, a system file management class, and a data upload class;

[0132] After collecting the external tracking data sent by the second tracking application through the external transmission channel, it also includes:

[0133] The external tracking point class transfers the external tracking point data collected from the external transmission channel to the tracking point intelligent service class;

[0134] Call the tracking point intelligent service class to pass the external tracking point data to the data processing class;

[0135] Call the data processing class to process the external tracking data and obtain the tracking data to be uploaded;

[0136] Call the system file management class to write the buried data to be uploaded into the file to be uploaded;

[0137] Call the data upload class to upload the file to be uploaded to the data demand side.

[0138] In some embodiments, calling a data processing class to process external tracking data to obtain tracking data to be uploaded includes:

[0139] Call the tracking point intelligent service class to pass the external tracking point data to the tracking point data buffer queue;

[0140] Call the data processing class, take out the external embedded point data to be processed from the data buffer queue, and process it to obtain the embedded point data to be uploaded.

[0141] In some embodiments, the first tracking application further includes an extended integrated public software library;

[0142] The method also includes:

[0143] If the data collection request includes third identification information corresponding to the external device, establishing a data transmission channel between the device application of the external device based on the extended integrated public software library;

[0144] The device tracking data sent by the device application of the external device is collected through the data transmission channel.

[0145] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0146] Fig. 9 Schematic diagram of an electronic device 9 provided in an embodiment of the present application. Fig. 9 As shown, the electronic device 9 of this embodiment includes: a processor 901, a memory 902, and a computer program 903 stored in the memory 902 and executable on the processor 901. When the processor 901 executes the computer program 903, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 901 executes the computer program 903, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0147] The electronic device 9 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 9 may include, but is not limited to, a processor 901 and a memory 902. Those skilled in the art will appreciate that Fig. 9 The electronic device 9 is merely an example and does not limit the electronic device 9 , and may include more or less components than those shown in the figure, or different components.

[0148] The processor 901 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0149] The memory 902 may be an internal storage unit of the electronic device 9, for example, a hard disk or memory of the electronic device 9. The memory 902 may also be an external storage device of the electronic device 9, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 9. The memory 902 may also include both an internal storage unit of the electronic device 9 and an external storage device. The memory 902 is used to store computer programs and other programs and data required by the electronic device.

[0150] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0151] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium (such as a computer-readable storage medium). Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0152] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for collecting buried data, characterized in that: Applied to a first burial point tracking application; the first burial point tracking application can be installed in a first virtual machine corresponding to a first operating system; the first virtual machine also includes an internal burial point application and an internal integrated public software library, and the integrated public software library can be installed in the first virtual machine; the first burial point tracking application includes an internal burial point tracking class and an external burial point tracking class; the first burial point tracking application encapsulates a first burial point function program for realizing the collection, processing and reporting of internal burial point data and external burial point data; The method comprises the following steps: Get the data collection request sent by the data demand side; If the data collection request includes first identification information corresponding to the first operating system, an internal transmission channel is established between the internal burying point tracking class and the internal burying point application, and the internal burying point data sent by the internal burying point application is collected through the internal transmission channel; the internal transmission channel is AIDL; If the data collection request includes second identification information corresponding to the second operating system, an external transmission channel is established between the external tracking class and the second tracking application corresponding to the second operating system, and the external tracking data sent by the second tracking application is collected through the external transmission channel; wherein the second tracking application is portable and installable in a second virtual machine corresponding to the second operating system; the second tracking application encapsulates a second tracking function program for collecting and reporting external tracking data; and the external transmission channel is a socket transmission channel that supports the TCP / IP protocol.

2. The method according to claim 1, characterized in that Establishing an internal transmission channel between the internal tracking class and the internal tracking application includes: Receiving an internal connection request sent by the internal burying point application by calling a burying point management class, a connection management class and a burying point acceptance class in the internal integrated public software library; In response to an internal connection request of the internal burying point application, an internal transmission channel is established between the internal burying point tracking class and the internal burying point application.

3. The method according to claim 1, characterized in that Establishing an external transmission channel between the external tracking class and a second tracking application corresponding to the second operating system includes: Initialize the external tracking class; Call the message management class through the external tracking class to start the datagram socket class and the message management thread class; An external transmission channel is established between the external point tracking class and the second point tracking application corresponding to the second operating system through the message management class, datagram socket class and message management thread class.

4. The method according to claim 3, characterized in that An external transmission channel between the external tracking class and the second tracking application corresponding to the second operating system is established through the message management class, the datagram socket class and the message management thread class, including: Calling the datagram socket class and the message management thread class through the message management class to forward the ready status message sent by the external tracking class to the second tracking application; If a connection response message is received from the second tracking application based on the preparation status message feedback, the external transmission channel between the external tracking class and the second tracking application is established.

5. The method according to claim 1, characterized in that The first tracking application also includes tracking intelligent service, data processing, system file management and data upload. After collecting the external tracking data sent by the second tracking application through the external transmission channel, the method further includes: The external burying point data collected from the external transmission channel is transmitted to the burying point intelligent service class through the external burying point tracking class; Call the tracking point intelligent service class to pass the external tracking point data to the data processing class; Call the data processing class to process the external buried point data to obtain the buried point data to be uploaded; Call the system file management class to write the buried point data to be uploaded into the file to be uploaded; Call the data upload class to upload the file to be uploaded to the data demand end.

6. The method according to claim 5, characterized in that Calling the data processing class to process the external buried point data to obtain the buried point data to be uploaded includes: Call the burying point intelligent service class to transfer the external burying point data to the burying point data buffer queue; The data processing class is called to take out the external buried point data to be processed from the data buffer queue, and classify and encrypt the data to be uploaded.

7. The method according to claim 1, characterized in that The first point tracking application also includes an extended integrated public software library; The method further comprises: If the data collection request includes third identification information corresponding to the external device, establishing a data transmission channel between the device application of the external device based on the extended integrated public software library; The device buried point data sent by the device application of the external device is collected through the data transmission channel.

8. A buried point data collection system, characterized in that: include: a first virtual machine corresponding to the first operating system, and a second virtual machine corresponding to the second operating system; The first virtual machine includes an internal burying point application, an internal integrated public software library and a first burying point tracking application; the first burying point tracking application includes an internal burying point tracking class and an external burying point tracking class; the first burying point tracking application can be portable and installed in the first virtual machine; the first burying point tracking application encapsulates a first burying point function program for realizing the collection, processing and reporting of internal burying point data and external burying point data; The second virtual machine includes a second burrowing point tracking application, which can be transplanted and installed in the second virtual machine; the second burrowing point tracking application encapsulates a second burrowing point function program for collecting and reporting external burrowing point data; The first tracking application is configured as follows: Get the data collection request sent by the data demand side; If the data collection request includes first identification information corresponding to the first operating system, an internal transmission channel is established between the internal burying point tracking class and the internal burying point application, and the internal burying point data sent by the internal burying point application is collected through the internal transmission channel; the internal transmission channel is AIDL; If the data collection request includes second identification information corresponding to the second operating system, an external transmission channel is established between the external tracking class and the second tracking application corresponding to the second operating system, and the external tracking data sent by the second tracking application is collected through the external transmission channel; the external transmission channel is a socket transmission channel that supports the TCP / IP protocol.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images