Acquisition and verification method of buried point data, related device and computer program product

Abstract

The invention provides a buried point data acquisition and verification method, a related device and a computer program product, and the method comprises the steps: obtaining to-be-verified buried point data from a target distributed stream processing platform in a buried point test process, the first identifier represents a data source of the to-be-verified buried point data, the second identifier represents a buried point type corresponding to the to-be-verified buried point data, and the target distributed stream processing platform is a distributed stream processing platform corresponding to the second identifier, acquiring a buried point data verification rule corresponding to the second identifier, and verifying the buried point data according to the buried point data verification rule. And then verifying the to-be-verified buried point data based on the buried point data verification rule to obtain a buried point data verification result, so that the to-be-verified buried point data can be verified according to the first identifier and the second identifier based on an actual buried point test requirement. And the burying point data of which the source and the type both meet the verification requirements are selectively and directionally acquired from the target distributed stream processing platform for verification, so that the timeliness and the accuracy of the burying point test are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software testing, and in particular to a method and device for collecting and verifying embedded point data, a system, an electronic device, a computer readable medium and a computer program product. BACKGROUND

[0002] This section is intended to provide background information to facilitate a better understanding of embodiments of the present application recited in the claims. The description herein does not constitute admission of prior art.

[0003] With the rapid development of Internet technology, user behavior analysis has become a key means to improve product experience and optimize services. By collecting user behavior data (such as clicks, browsing, form submission, etc.), software developers can analyze user behavior patterns, evaluate application performance, and make data-driven decisions. In this process, the embedded point technology is widely used, which collects user behavior and system event data by implanting code (manual embedding) or using automatic embedding tools at key nodes of the application program (such as button clicks, page loading, etc.), and the collected data is called embedded point data.

[0004] In order to ensure the effectiveness and usability of embedded point data, embedded point testing is needed, which mainly verifies and detects the embedded points set in advance in the software system to verify whether the embedded points are triggered as expected and correctly report user behavior data. Embedded point testing mainly includes collection and verification of embedded point data.

[0005] In the prior art, the embedded point testing platform obtains embedded point data from the embedded point data service platform for verification, but with the diversification and precision development of testing needs, and the diversification and development of embedded point data sources and types, the explosive growth of massive non-important embedded point data may cause the embedded point testing platform to be unable to obtain the required embedded point data in time and perform targeted verification, which seriously restricts the timeliness and accuracy of embedded point testing.

[0006] In view of the above problems, there is an urgent need for a technical solution that can improve the timeliness and accuracy of embedded point testing. SUMMARY

[0007] Aspects of the present application provide a method and device for collecting and verifying embedded point data, a system, an electronic device, a computer readable medium and a computer program product to improve the timeliness and accuracy of embedded point testing.

[0008] In one aspect of the present application, a method for verifying embedded point data is provided, wherein the method is applied to an embedded point testing platform, and the method comprises: Obtain the buried data to be verified from the target distributed stream processing platform; wherein the buried data to be verified is buried data including a first identifier and a second identifier, the first identifier represents the data source of the buried data to be verified, the second identifier represents the buried type corresponding to the buried data to be verified, and the target distributed stream processing platform is the distributed stream processing platform corresponding to the second identifier; Obtaining a data verification rule corresponding to the second identifier; Based on the buried point data verification rules, the buried point data to be verified is verified to obtain the buried point data verification result.

[0009] Another aspect of the present application provides a method for collecting buried data, wherein the method is applied to a buried data service platform, and the method includes: Receive tracking data reported by user terminals; If the buried point data includes a first identifier, the buried point data is determined as the buried point data to be verified; wherein the first identifier represents the data source of the buried point data to be verified; The buried point data to be verified is written into a distributed stream processing platform corresponding to a second identifier in the buried point data; wherein the second identifier represents the buried point type corresponding to the buried point data.

[0010] Another aspect of the present application provides a device for verifying buried data, which is provided on a buried test platform and includes: A buried point data acquisition module is used to obtain the buried point data to be verified from the target distributed stream processing platform; wherein the buried point data to be verified is the buried point data containing a first identifier and a second identifier, the first identifier represents the data source of the buried point data to be verified, the second identifier represents the buried point type corresponding to the buried point data to be verified, and the target distributed stream processing platform is the distributed stream processing platform corresponding to the second identifier; A verification rule acquisition module, configured to acquire a verification rule for the buried data corresponding to the second identifier; The buried point data verification module is used to verify the buried point data to be verified based on the buried point data verification rules to obtain the buried point data verification results.

[0011] Another aspect of the present application provides a device for collecting buried data, which is provided on a buried data service platform, and includes: The tracking data receiving module is used to receive the tracking data reported by the user terminal; A buried point data filtering module, configured to determine the buried point data as buried point data to be verified if the buried point data includes a first identifier; wherein the first identifier indicates a data source of the buried point data to be verified; The burying point data writing module is configured to write the to-be-verified burying point data into a distributed stream processing platform corresponding to a second identifier in the burying point data, wherein the second identifier represents a burying point type corresponding to the burying point data.

[0012] In another aspect of the present application, a system for verifying burying point data is provided, wherein the system comprises a user terminal, a burying point data service platform, a plurality of distributed stream processing platforms, and a burying point test platform. The user terminal is configured to report burying point data to the burying point data service platform. The burying point data service platform is configured to receive the burying point data, determine the burying point data as to-be-verified burying point data if the burying point data comprises a first identifier, and write the to-be-verified burying point data into a distributed stream processing platform corresponding to a second identifier in the burying point data, wherein the first identifier represents a data source of the to-be-verified burying point data, and the second identifier represents a burying point type corresponding to the to-be-verified burying point data. The distributed stream processing platform is configured to store the to-be-verified burying point data. The burying point test platform is configured to acquire the to-be-verified burying point data from a target distributed stream processing platform, verify the to-be-verified burying point data based on a burying point data verification rule corresponding to the second identifier, and obtain a burying point data verification result.

[0013] In another aspect of the present application, an electronic device is provided, and the electronic device comprises: at least one processor; and a memory in communication connection with the at least one processor; wherein The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the verification method or the collection method of the burying point data.

[0014] In another aspect of the present application, a computer readable storage medium is provided, and the computer readable storage medium stores computer program instructions executable by a processor to implement the verification method or the collection method of the burying point data.

[0015] In another aspect of the present application, a computer program product is provided, and the computer program product comprises a computer program executable by a processor to implement the verification method or the collection method of the burying point data.

[0016] In the scheme provided by the embodiments of the present application, the to-be-verified embedded point data is obtained from a target distributed stream processing platform, wherein the to-be-verified embedded point data is embedded point data containing a first identifier and a second identifier, the first identifier represents the data source of the to-be-verified embedded point data, the second identifier represents the embedded point type corresponding to the to-be-verified embedded point data, the target distributed stream processing platform is a distributed stream processing platform corresponding to the second identifier, the embedded point data verification rule corresponding to the second identifier is obtained, and the to-be-verified embedded point data is verified based on the embedded point data verification rule to obtain an embedded point data verification result, so that the to-be-verified embedded point data that meets the verification requirements in terms of source and type can be selectively obtained from the target distributed stream processing platform based on actual embedded point test requirements, the problem that the timeliness and accuracy of verification are damaged due to the inability to effectively obtain embedded point data from massive embedded point data is avoided, and the first identifier and the second identifier are used to filter embedded point data, accurately locate the source of the embedded point data to be verified, avoid the influence of unnecessary embedded point data and the redundant processing overhead caused by full data scanning, and improve the timeliness of embedded point testing. On this basis, the to-be-verified embedded point data is verified by using the embedded point data verification rule corresponding to the second identifier, the dynamic matching of the verification rule can be realized, so that appropriate verification rules can be used for verification to improve the accuracy of the verification result. In addition, since the to-be-verified embedded point data is distributed to different distributed stream processing platforms according to the second identifier, the to-be-verified embedded point data is obtained from the target distributed stream processing platform, the to-be-verified embedded point data can be obtained in a targeted manner according to the second identifier, the partitioning and filtering capabilities of the distributed stream processing platform are fully utilized to improve the efficiency and accuracy of obtaining the to-be-verified embedded point data of the required type, and the real-time stream processing capability of the distributed stream processing platform is fully utilized to further improve the efficiency and timeliness of obtaining the to-be-verified embedded point data, so that the timeliness and accuracy of embedded point testing are further improved as a whole. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative labor.

[0018] Other features, objects and advantages of the present application will become more apparent from the following detailed description of the non-limiting embodiments, with reference to the following drawings: Figure 1A first implementation principle schematic diagram of the verification system of the embedded point data provided by an embodiment of the present application is provided; Figure 2 A second implementation principle schematic diagram of the verification system of the embedded point data provided by an embodiment of the present application is provided; Figure 3 A flow schematic diagram of the verification method of the embedded point data provided by an embodiment of the present application is provided; Figure 4 A flow schematic diagram of the collection method of the embedded point data provided by an embodiment of the present application is provided; Figure 5 A structure schematic diagram of the verification device of the embedded point data provided by an embodiment of the present application is provided; Figure 6 A structure schematic diagram of the collection device of the embedded point data provided by an embodiment of the present application is provided; Figure 7 A structure schematic diagram of an electronic device suitable for implementing the scheme in the embodiments of the present application is provided; The same or similar reference signs in the drawings represent the same or similar components. DETAILED DESCRIPTION

[0019] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0020] In a typical configuration of the present application, the devices of the terminal and the service network each include one or more processors (CPU), input / output interfaces, network interfaces and memories.

[0021] The memory can include a non-permanent memory in a computer readable medium, random access memory (RAM) and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of a computer readable medium.

[0022] Computer-readable media includes permanent and non-permanent, removable and non-removable media, which can be implemented by any method or technology to store information. Information can be computer program instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact discs (CD-ROM), digital versatile discs (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device.

[0023] The embodiment of the present application provides a kind of acquisition, verification method, device, system, electronic equipment, computer readable medium and computer program product of burying point data, one aspect, first identification in burying point data service platform is filtered out to be verified burying point data based on burying point data, so that in the case where the system architecture of original burying point data reporting is not changed, it is realized that the burying point test platform is transmitted to the burying point data to be verified with pertinence;Second aspect, since target distributed stream processing platform is the distributed stream processing platform corresponding to the second identification in the burying point data to be verified, second identification represents the burying point type corresponding to the burying point data to be verified, therefore, the burying point data collected for different burying point types can be written into different distributed stream processing platforms, i.e. the burying point data corresponding to different burying point types is written into the respective corresponding distributed stream processing platform, to ensure that the burying point data corresponding to different burying point types do not affect each other, and then ensure the verification timeliness of the burying point data corresponding to burying point type with high priority.

[0024] The acquisition, verification method, device, system, electronic equipment, computer readable medium and computer program product of burying point data provided by the present application are described below.

[0025] For ease of understanding, some technical terms, related terms and concepts related to some embodiments provided by the present application are explained as follows.

[0026] Code burying, a kind of burying mode, refers to that developer adds data collection logic in the key position (such as button click event, page loading is completed, etc.) of application program, to trigger the collection of user behavior data, etc., and send these data to specified business end for subsequent analysis. In addition to this, burying mode also includes: visual burying, full burying, etc.

[0027] The buried point code is an implementation code of a data collection function, and refers to a code segment inserted in an application program and specifically used for recording user behaviors or system events.

[0028] The buried point data refers to data about user behaviors or system performance collected through preset nodes (such as event nodes of user clicking a button, browsing a page, etc.) in an application program.

[0029] The buried point type refers to a classification of buried points divided from preset dimensions, for example, the buried point type can include mobile terminal buried points, Web terminal buried points, and server buried points according to deployment environments; for another example, the buried point type can include domestic version application buried points and international version application buried points according to application versions; for yet another example, the buried point type can include live broadcast buried points and video buried points according to business function modules.

[0030] The distributed stream processing platform is a system for high-throughput real-time data pipelines and event stream processing, and in the buried point test, mainly serves as a data transfer station and a real-time stream processing platform, for example, it can be a Kafka cluster or a RabbitMQ message queue, wherein the Kafka cluster can include multiple Kaffas, and Kafka is a high-throughput distributed publish / subscribe message system with the characteristics of high throughput, low delay, and high reliability.

[0031] Next, the specific implementation process of some embodiments provided by the present application is described in detail.

[0032] Figure 1 A specific implementation process of a buried point data verification system provided by an embodiment of the present application is shown, as shown in Figure 1 The buried point data verification system at least includes: a plurality of user terminals, a buried point data service platform, a plurality of distributed stream processing platforms, and a buried point test platform; wherein the plurality of distributed stream processing platforms include distributed stream processing platform 1 to distributed stream processing platform n, and n is an integer greater than 1.

[0033] The user terminal acquires buried point data based on a preset data collection logic of buried points, and reports the buried point data to the buried point data service platform.

[0034] The buried point data service platform receives the above-mentioned buried point data; if the buried point data includes a first identifier, the buried point data is determined as to-be-verified buried point data; wherein the first identifier represents the data source of the buried point data.

[0035] The buried point data service platform writes the to-be-verified buried point data into a distributed stream processing platform corresponding to a second identifier in the buried point data; wherein the second identifier represents a buried point type corresponding to the buried point data.

[0036] The distributed stream processing platform is used for storing the to-be-verified embedded point data; wherein, different embedded point types are allocated with corresponding distributed stream processing platforms in advance, and each distributed stream processing platform can include multiple Kaffas, and each Kafka is used as a transfer message queue of the to-be-verified embedded point data.

[0037] The embedded point test platform obtains the to-be-verified embedded point data from the target distributed stream processing platform; the target distributed stream processing platform is the distributed stream processing platform corresponding to the second identifier; wherein, the embedded point test platform obtains the configuration information of the distributed stream processing platform corresponding to each embedded point type in advance, and the distributed stream processing platform corresponding to each embedded point type can be regarded as a target distributed stream processing platform; and the to-be-verified embedded point data in the distributed stream processing platform is consumed based on the configuration information.

[0038] The embedded point test platform verifies the to-be-verified embedded point data based on the embedded point data verification rule corresponding to the second identifier, and obtains an embedded point data verification result; wherein, the embedded point data collected by embedded points of different embedded point types can include at least one different attribute field, and since the compliance constraint conditions corresponding to different attribute fields can be different, the embedded point data verification rule corresponding to each embedded point type is established in advance, that is, the corresponding relationship between the second identifier and the embedded point data verification rule is established.

[0039] It can be understood that the above-mentioned embedded point data service platform can be regarded as a message producer, and the to-be-verified embedded point data is written into the target distributed stream processing platform, and the above-mentioned embedded point test platform can be regarded as a message consumer, and the embedded point data in the target distributed stream processing platform is consumed.

[0040] Further, considering that the embedded point deployment of different embedded point types can be increased or decreased as the business demand changes, the corresponding distributed stream processing platform needs to be allocated for the newly added embedded point type, and the corresponding embedded point data verification rule needs to be created for the newly added embedded point type; based on this, in order to more flexibly adjust the embedded point data verification rule and the configuration information of the distributed stream processing platform, the embedded point test platform can obtain the embedded point data verification rule of the newly added embedded point type and the configuration information of the distributed stream processing platform from the third-party service platform according to a preset triggering condition. Wherein, Figure 2 Another specific implementation process of the embedded point data verification system provided by the embodiment of the application is shown in the figure Figure 2 Based on the above Figure 1 , the embedded point data verification system further includes: a third-party service platform; and the third-party service platform is in communication connection with the embedded point test platform. In addition, in the above Figure 1Based on the above, some platforms have been refined. User terminals can include mobile terminals, web terminals, and server terminals. User terminals can transmit tracking data to the tracking data service platform through software development kits (SDKs). Different terminals correspond to different software development kits (SDKs). For example, mobile terminals and web terminals correspond to SDK1 (such as bfe-agent), and the server corresponds to SDK2 (such as log-agent). The buried point data service platform may include a buried point data acquisition module and a buried point data distribution module; the buried point data acquisition module is used to receive buried point data uploaded by the user terminal; the buried point data distribution module is used to determine the buried point data containing the first identifier as the buried point data to be verified, and write the buried point data to be verified into the distributed stream processing platform corresponding to the second identifier; The distributed stream processing platform may include Kafka cluster 1, Kafka cluster 2, and Kafka cluster 3. Different Kafka clusters are used to store tracking data of different tracking types. For example, Kafka cluster 1 is used to store tracking data to be verified from the mobile terminal, that is, tracking data corresponding to the tracking data of the mobile terminal. Similarly, Kafka cluster 2 is used to store tracking data to be verified from the web terminal, and Kafka cluster 3 is used to store tracking data to be verified from the server. The tracking test platform may include a tracking test platform backend and a tracking test platform frontend; the tracking test platform backend is used to read the tracking data to be verified from the target distributed stream processing platform and verify the tracking data; the tracking test platform frontend is used to display the verification results of the tracking data.

[0041] The third-party service platform generates the point-of-sale data verification rules for each newly added point-of-sale type in response to the verification rule pre-defined request of the first terminal device.

[0042] Among them, the first terminal device can be a user terminal of the tester responsible for setting the verification rules. In the case where a new burial point type needs to be added based on business needs, the first terminal device sends a verification rule pre-definition request to the third-party service platform to trigger the third-party service platform to establish a first correspondence between the second identifier of the newly added burial point type and the burial point data verification rule based on the verification rule pre-definition request; therefore, the burial point testing platform can obtain the first correspondence from the third-party service platform, and then, based on the burial point data verification rule corresponding to the second identifier, verify the burial point data containing the second identifier.

[0043] The third-party service platform generates configuration information of the newly added distributed stream processing platform in response to the second terminal device's request for registering a point, and returns a second identifier corresponding to the newly added distributed stream processing platform to the second terminal device; the second identifier is added to the point code corresponding to the newly added point type, and the point data generated when the data collection logic of the point code is triggered includes the second identifier.

[0044] The second identifier can be a point type associated identifier carried in at least one of the request for defining a verification rule and the request for registering a point, or a point type associated identifier allocated by the third-party service platform for the newly added point type, and the second identifier corresponds to the point type one-to-one.

[0045] The second terminal device can be a user terminal of a developer responsible for point deployment. When a point type needs to be added based on business requirements, the second terminal device sends a request for registering a point to the third-party service platform to trigger the third-party service platform to establish a second corresponding relationship between the second identifier of the newly added point type and the configuration information of the distributed stream processing platform based on the request for registering a point. Therefore, the point test platform can obtain the second corresponding relationship from the third-party service platform, and then obtain the point data to be verified from the distributed stream processing platform corresponding to the newly added point type based on the configuration information in the second corresponding relationship.

[0046] In addition, the third-party service platform also needs to return the second identifier corresponding to the newly added point type to the second terminal device, which can be a second identifier carried in the request for defining a verification rule initiated for the newly added point type. In this way, the developer can write the second identifier into the data collection logic of the point of the newly added point type, so that the point data generated when the data collection logic is triggered includes the second identifier. Based on this, on the one hand, after the point data service platform receives the point data (i.e. the point data to be verified) containing the first identifier, it can store the point data to be verified to the corresponding distributed stream processing platform based on the second identifier in the point data to be verified; on the other hand, after the point test platform obtains the point data to be verified from the target distributed stream processing platform, it can verify the point data to be verified based on the point data verification rule corresponding to the second identifier in the point data to be verified, and obtain a point data verification result.

[0047] It can be understood that the point data service platform needs to store the point data to be verified to the distributed stream processing platform corresponding to the second identifier, so the point data service platform is in communication connection with the third-party service platform, and the point data service platform obtains the configuration information of the distributed stream processing platform corresponding to the second identifier of each newly added point type from the third-party service platform according to a preset trigger condition; and then stores the point data to be verified to the distributed stream processing platform corresponding to the second identifier based on the configuration information.

[0048] In an embodiment of the present application, with the help of a third-party service platform, the third-party service platform generates a point-of-sale data verification rule for each newly added point-of-sale type in response to a verification rule pre-defined request from the first terminal device, and stores the correspondence between the second identifier corresponding to the newly added point-of-sale type and the point-of-sale data verification rule (referred to as the first correspondence); and the third-party service platform generates configuration information of the distributed stream processing platform assigned to the newly added point-of-sale type in response to a point-of-sale registration request from the second terminal device, and stores the correspondence between the second identifier corresponding to the newly added point-of-sale type and the configuration information of the distributed stream processing platform (referred to as the second correspondence); that is, the third-party service platform establishes a correspondence between the second identifier, the point-of-sale data verification rule, and the configuration information of the distributed stream processing platform for each newly added point-of-sale type.

[0049] Based on this, after obtaining the above-mentioned second correspondence from the third-party service platform, the burying point data service platform determines the configuration information of the distributed stream processing platform corresponding to the second identifier in the burying point data to be verified based on the second correspondence; and then writes the burying point data to be verified into the target distributed stream processing platform based on the configuration information. After obtaining the above-mentioned first correspondence and second correspondence from the third-party service platform, the burying point test platform obtains the burying point data to be verified from the target distributed stream processing platform based on the configuration information in the second correspondence; and verifies the burying point data to be verified based on the burying point data verification rules in the first correspondence to obtain the burying point data verification results.

[0050] Figure 3 The processing flow of a method for verifying buried data provided by an embodiment of the present application is shown, which is applied to a buried test platform, such as Figure 3 As shown, the verification method of buried point data includes at least the following processing steps: S301, obtain the buried data to be verified from the target distributed stream processing platform; wherein, the buried data to be verified is the buried data including a first identifier and a second identifier, the first identifier represents the data source of the buried data to be verified, the second identifier represents the buried type corresponding to the buried data to be verified, and the target distributed stream processing platform is the distributed stream processing platform corresponding to the second identifier.

[0051] The first identifier can be returned by the front-end of the buried point test platform to the tester's user terminal under the tester's trigger operation; in the process of generating buried point data, the user terminal can use the first identifier as the field value of an attribute field, so that the buried point data from the tester's user terminal contains the first identifier. The first identifier can not only be used to distinguish whether the buried point data is reported to the buried point test platform as the buried point data to be verified, but also can be used as a display basis to display the verification results of the buried point data on the corresponding buried point test platform front-end page.

[0052] That is to say, based on the first identifier, double-layer filtering of the buried point data can be achieved. On the one hand, based on the first identifier, it is determined which buried point data are to be verified. On the other hand, based on the first identifier, it is determined on which front-end pages of the buried point test platform the buried point data verification results will be displayed.

[0053] Among them, the second identifier is an identifier for distinguishing the type of buried point, and the second identifier can be added to the buried point code corresponding to the buried point type. Similar to the first identifier, the user terminal will also use the second identifier as the field value of an attribute field in the process of generating buried point data, that is, the buried point data generated by the data collection logic of the buried point code is triggered includes the second identifier, so that the buried point data from the tester's user terminal includes not only the first identifier, but also the second identifier. In addition, the second identifier can not only be used to determine the buried point data verification rules corresponding to different buried point types, but also can be used as a distribution basis to decide which distributed stream processing platform to write the buried point data to.

[0054] That is to say, based on the second identifier, it is possible to distinguish between different types of buried point data. On the one hand, based on the second identifier, the corresponding buried point data verification rules can be matched. On the other hand, based on the second identifier, the corresponding distributed stream processing platform can be matched.

[0055] S302, obtain the point data verification rule corresponding to the second identifier.

[0056] In some example embodiments, the burial point data verification rules can be directly deployed on the burial point testing platform; in other example embodiments, the burial point data verification rules corresponding to different burial point types can be managed with the help of a third-party service platform. After the third-party service platform generates the corresponding burial point data verification rules for the newly added burial point types, the burial point testing platform obtains the burial point data verification rules corresponding to the newly added burial point types, and then directly verifies the burial point data containing the corresponding second identifier based on the burial point data verification rules.

[0057] S303: Based on the above-mentioned buried point data verification rules, the buried point data to be verified is verified to obtain the buried point data verification result.

[0058] In the scheme provided by the embodiments of the present application, the to-be-verified embedded point data is obtained from a target distributed stream processing platform, wherein the to-be-verified embedded point data is embedded point data containing a first identifier and a second identifier, the first identifier represents the data source of the to-be-verified embedded point data, the second identifier represents the embedded point type corresponding to the to-be-verified embedded point data, the target distributed stream processing platform is a distributed stream processing platform corresponding to the second identifier, the embedded point data verification rule corresponding to the second identifier is obtained, and the to-be-verified embedded point data is verified based on the embedded point data verification rule to obtain an embedded point data verification result, so that the to-be-verified embedded point data that meets the verification requirements in terms of source and type can be selectively obtained from the target distributed stream processing platform based on actual embedded point test requirements according to the first identifier and the second identifier, and the problem that the timeliness and accuracy of verification are damaged due to the inability to effectively obtain embedded point data from massive embedded point data is avoided. Moreover, the embodiments of the present application only need to verify the embedded point data with the first identifier as the to-be-verified embedded point data, so that the first identifier can be used to filter the embedded point data and accurately locate the source of the embedded point data to be verified, thereby avoiding the influence of unnecessary embedded point data and the redundant processing overhead caused by full data scanning, and improving the timeliness of embedded point testing. On this basis, the to-be-verified embedded point data is verified by using the embedded point data verification rule corresponding to the second identifier, so that the dynamic matching of the verification rule can be realized, and thus appropriate verification rules can be used for verification to improve the accuracy of the verification result. In addition, since the to-be-verified embedded point data is distributed to different distributed stream processing platforms according to the second identifier, the to-be-verified embedded point data is obtained from the target distributed stream processing platform, which can realize the directional acquisition of the to-be-verified embedded point data according to the second identifier, fully utilize the partitioning and filtering capabilities of the distributed stream processing platform to improve the acquisition efficiency and accuracy of the to-be-verified embedded point data of the required type, and further improve the acquisition efficiency and timeliness of the to-be-verified embedded point data by fully utilizing the real-time stream processing capability of the distributed stream processing platform, so as to further improve the timeliness and accuracy of the embedded point testing as a whole. In addition, the embodiments of the present application can solve the problem of balancing the efficiency and accuracy of embedded point testing under massive embedded point data by filtering unnecessary embedded point data by using the first identifier and realizing the dynamic matching of the verification rule and the distributed stream processing platform in combination with the second identifier.

[0059] In view of the fact that in the prior art, in the case of a large amount of buried point data, the buried point test mainly checks whether there is a missing report or a data format problem, and does not check whether a certain field attribute meets the requirements, otherwise it will greatly increase the system overhead and seriously affect the checking efficiency and real-time performance, and based on the foregoing embodiment, only the buried point data to be checked with the first identifier is selected for testing, so that in the case of improved buried point data acquisition efficiency and reduced amount of data to be checked, the attribute granularity-based buried point test is provided with feasibility, and therefore, the embodiment of the present application can also check the buried point data to be checked more comprehensively from the attribute granularity.

[0060] Specifically, in some embodiments, for different types of buried points, the collected buried point data can include different attribute fields, for example, for a buried point of type a, the collected buried point data can include attribute field 1, attribute field 2, and attribute field 3; and for a buried point of type b, the collected buried point data can include attribute field 4, attribute field 5, and attribute field 6, or can also include attribute field 2, attribute field 3, and attribute field 4. Based on this, it is considered that the required compliance constraint conditions of the field values of different attribute fields can be different, so that the buried point data checking rules corresponding to different types of buried points can be different, and therefore, the corresponding buried point data checking rules are established for each type of buried point in advance, that is, the correspondence between the second identifier and the buried point data checking rule is established. Based on this, in the buried point data checking process, for each buried point data to be checked, the buried point data is checked based on the buried point data checking rule corresponding to the second identifier in the buried point data.

[0061] Further, in order to improve the checking accuracy of the buried point data and enable fine-grained checking of the buried point data from the attribute field granularity, the buried point data checking rule includes a plurality of attribute fields and compliance constraint conditions of the attribute fields. Correspondingly, the above S303, based on the above buried point data checking rule, checks the buried point data to be checked to obtain a buried point data checking result, which can include: Based on the plurality of attribute fields in the above buried point data checking rule, the buried point data to be checked is structurally processed to obtain structured buried point data; wherein the structured buried point data includes a plurality of attribute fields and field values corresponding to the attribute fields; For each attribute field, the field value of the attribute field is checked based on the compliance constraint condition of the attribute field to obtain a buried point data checking result.

[0062] The aforementioned compliance constraints refer to the conditions for performing field validation on attribute fields, including but not limited to non-empty validation, enumeration validation, and regular expression validation. Non-empty validation verifies whether a field contains a valid value rather than an empty value or null, and can be used to verify the existence of necessary information. Enumeration validation checks whether a field's value belongs to a predefined set of finite values ​​and can be used to maintain data consistency. Regular expressions are a powerful text matching tool that can be used to define complex pattern matching rules. They are suitable for detailed validation of string-type fields and can be used to ensure the accuracy of data in a specific format.

[0063] For example, the buried data to be verified can be data in the form of a string, and the string is obtained by concatenating the field values ​​of multiple attribute fields. Therefore, the buried data to be verified includes not only the first identifier and the second identifier, but also the field values ​​of multiple attribute fields, and the field values ​​of different attribute fields are separated by a preset delimiter. The structuring process of buried data is essentially to convert the string into formatted data. The buried data to be verified can be segmented based on the preset delimiter to obtain multiple substrings, and then a correspondence between the attribute fields and the substrings is established. For example, structured buried data includes multiple key-value pairs.

[0064] After obtaining structured buried data, the field values ​​of each attribute field in the structured buried data can be verified in combination with the compliance constraints of each attribute field in the buried data verification rules. In one example, taking the attribute field as user age as an example, compliance constraint 1 of user age can include that the field value is a numeric type and the field value is within a preset range; correspondingly, it is determined whether the field value of user age meets compliance constraint 1; in another example, taking the attribute field as application version as an example, compliance constraint 2 of the application version can include that the field value contains a specified string; correspondingly, it is determined whether the field value of the application version meets compliance constraint 2.

[0065] The implementation method of the present application, by performing structured processing on the buried point data to be verified, can convert unstructured data into identifiable and operable structured data, providing a basis for subsequent fine-grained verification at the field level; and then by verifying the field values ​​of each attribute field one by one according to its compliance constraints, it can improve the overall verification accuracy of the buried point data and reduce the occurrence of misjudgments caused by abnormalities in individual fields. When faced with complex and diverse buried point types and attribute field combinations, it can effectively support a flexible, accurate, and efficient buried point data verification process, ensuring that the overall buried point test process has high timeliness and accuracy.

[0066] Further, for the configuration process of the trace data check rule, in order to more flexibly adjust the trace data check rule. Wherein, the S302 described above, obtaining the trace data check rule corresponding to the second identifier, can include: obtaining the trace data check rule corresponding to the second identifier from the third-party service platform; the trace data check rule is generated by the third-party service platform in response to the check rule predefinition request of the first terminal device under the condition of adding the trace type.

[0067] Wherein, the third-party service platform can be a centralized system for managing trace type registration, check rule and distributed platform configuration.

[0068] For example, under the triggering operation of the first user, the first terminal device sends a check rule predefinition request to the third-party service platform; the third-party service platform generates the trace data check rule of each newly added trace type in response to the check rule predefinition request of the first terminal device. In this way, the trace test platform can obtain the trace data check rule of the newly added trace type from the third-party service platform.

[0069] Further, for the process of configuring the distributed stream processing platform for the newly added trace type, in order to more flexibly adjust the configuration information of the distributed stream processing platform. Wherein, the above can further include: obtaining the configuration information of the newly added distributed stream processing platform from the third-party service platform; wherein, the configuration information is generated by the third-party service platform in response to the trace registration request of the second terminal device under the condition of adding the trace type, and the second identifier corresponding to the newly added distributed stream processing platform is returned to the second terminal device, the second identifier is used to be added to the trace code corresponding to the newly added trace type, and the trace data generated by triggering the data collection logic of the trace code includes the second identifier.

[0070] Correspondingly, the S301 described above, obtaining the trace data to be checked from the target distributed stream processing platform, can include: obtaining the trace data to be checked from the target distributed stream processing platform based on the configuration information.

[0071] For example, under the triggering operation of the second user, the second terminal device sends a trace registration request to the third-party service platform; the third-party service platform generates the configuration information of the newly added distributed stream processing platform in response to the trace registration request of the second terminal device. In this way, the trace test platform and the trace data service platform can obtain the configuration information of the distributed stream processing platform corresponding to the newly added trace type from the third-party service platform.

[0072] It should be noted that the specific implementation process between the tracking data service platform, tracking test platform and third-party service platform is detailed in the above Figure 2 The detailed description will not be repeated here.

[0073] Furthermore, in order for the testers to quickly view the verification results of the buried data uploaded by their respective user terminals, in S303, based on the above buried data verification rules, the buried data to be verified is verified, and after obtaining the buried data verification results, the following steps may also be included: The result of the tracking data verification is displayed on the front-end page of the tracking test platform corresponding to the first identifier.

[0074] For example, the tracking test platform can be divided into the tracking test platform backend and the tracking test platform frontend. The tracking test platform backend is connected to the third-party service platform and the distributed stream processing platform for consuming the tracking data to be verified from the target distributed stream processing platform and verifying the tracking data to be verified; then, based on the first identifier in the tracking data, the tracking data verification result is displayed on the front-end page of the corresponding tracking test platform. In this way, since the first identifier is returned by the tracking test platform in response to the request of the tester's user terminal, the correspondence between the tester's user terminal and the front-end of the tracking test platform can be established, so that the tester can view the verification results of the tracking data reported by their respective user terminals in a targeted manner.

[0075] Specifically, the front end of the burying point test platform returns a first identifier to the tester's user terminal under the tester's triggering operation; the first identifier is used to distinguish whether the burying point data uploaded to the burying point data service platform comes from the tester's terminal device. Therefore, after receiving the burying point data uploaded by the user terminal, the burying point data service platform identifies whether the burying point data contains the first identifier, so that the burying point data service platform will use the burying point data containing the first identifier as the burying point data to be verified, and transmit the burying point data to be verified to the burying point test platform through the distributed stream processing platform.

[0076] Furthermore, in order to effectively control the delayed display of the verification result of the buried point data, in the above S303, based on the above buried point data verification rules, the buried point data to be verified is verified, and after obtaining the buried point data verification result, the following steps may also be included: Obtain the reporting timestamp of the tracking data to be verified and the display timestamp of the tracking data verification result; Based on the reporting timestamp and display timestamp, the verification delay judgment result of the tracking data to be verified is generated.

[0077] For example, if the difference between the display timestamp and the reporting timestamp is greater than the preset threshold, it means that there is a problem of delayed display of the verification results of the buried data. Therefore, it is necessary to analyze and deal with the reasons for the delayed display of the verification results of the buried data.

[0078] In the solution provided by the embodiment of the present application, when the burial point data service platform writes the burial point data containing the first identifier as the burial point data to be verified into the target distributed stream processing platform, the burial point testing platform obtains the burial point data to be verified from the target distributed stream processing platform; and, based on the burial point data verification rules corresponding to the second identifier in the burial point data to be verified, the burial point data to be verified is verified to obtain the burial point data verification result. In this way, on the one hand, the buried point data service platform filters out the buried point data to be verified based on the first identifier in the buried point data, so that the buried point data to be verified can be transmitted to the buried point test platform in a targeted manner without changing the original system architecture for reporting the buried point data; on the other hand, since the target distributed stream processing platform is a distributed stream processing platform corresponding to the second identifier in the buried point data to be verified, the second identifier represents the buried point type corresponding to the buried point data to be verified. Therefore, the buried point data collected for buried point types of different buried point types can be written into different distributed stream processing platforms, that is, the buried point data corresponding to different buried point types are written into their respective corresponding distributed stream processing platforms, thereby ensuring that the buried point data corresponding to different buried point types do not affect each other, and further ensuring the verification timeliness of the buried point data corresponding to the buried point type with high priority.

[0079] Based on the same inventive concept, a method for collecting buried point data is also provided in the embodiments of the present application. The method is applied to a buried point data service platform and is used to write the buried point data to be verified into a target distributed stream processing platform to provide basic data for the above-mentioned buried point testing platform. The specific implementation process of the method for collecting buried point data can refer to the specific implementation process of the buried point data service platform in the aforementioned embodiment, and the principle of solving the problem is similar to that of the above-mentioned method for verifying buried point data. No further details will be given here.

[0080] Figure 4 The processing flow of a method for collecting buried data provided by an embodiment of the present application is shown, which is applied to a buried data service platform, such as Figure 4 As shown, the method for collecting buried data includes at least the following processing steps: S401, receiving the tracking data reported by the user terminal.

[0081] Among them, the user terminal can be a user terminal of the tester, and the user terminal can include at least one of the tester's mobile terminal, the Web terminal, and the server corresponding to the Web terminal.

[0082] S402: If the buried point data includes a first identifier, the buried point data is determined as buried point data to be verified; wherein the first identifier represents the data source of the buried point data to be verified.

[0083] The first identifier is returned by the front-end of the tracking test platform to the tester's user terminal under the tester's trigger operation. Specifically, when generating tracking data, the user terminal uses the first identifier as the field value of an attribute field, so that the tracking data from the tester's user terminal contains the first identifier. In addition, the first identifier can not only be used to distinguish whether the tracking data is reported to the tracking test platform as tracking data to be verified, but also can display the verification results of the tracking data on the corresponding tracking test platform front-end page based on the first identifier.

[0084] That is to say, based on the first identifier, double-layer filtering of the buried point data can be achieved. On the one hand, based on the first identifier, it is determined which buried point data are to be verified. On the other hand, based on the first identifier, the buried point data verification results are displayed on the corresponding buried point test platform front-end page.

[0085] S403, writing the buried point data to be verified into the distributed stream processing platform corresponding to the second identifier in the buried point data; wherein the second identifier represents the buried point type corresponding to the buried point data.

[0086] Among them, the second identifier is an identifier for distinguishing the type of buried point, and the second identifier is added to the buried point code corresponding to the newly added buried point type. Specifically, similar to the first identifier, the user terminal will also use the second identifier as the field value of an attribute field in the process of generating buried point data, that is, the buried point data generated by the data collection logic of the buried point code is triggered includes the second identifier, so that the buried point data from the tester's user terminal includes not only the first identifier, but also the second identifier. Moreover, the second identifier can not only be used for the buried point data verification rules corresponding to different buried point types, but also can decide which distributed stream processing platform to write the buried point data to based on the first identifier.

[0087] That is to say, based on the second identifier, it is possible to distinguish the buried point data of different buried point types. On the one hand, the corresponding buried point data verification rules are matched based on the second identifier, and on the other hand, the corresponding distributed stream processing platform is matched based on the second identifier.

[0088] Specifically, after the burial point data service platform writes the burial point data to be verified into the target distributed stream processing platform, the burial point test platform obtains the burial point data to be verified from the target distributed stream processing platform through message consumption. Therefore, it is possible to filter out the burial point data to be verified from the burial point data reported by the user terminal based on the first identifier without changing the original system architecture for reporting the burial point data, and then upload the burial point data to be verified to the burial point test platform.

[0089] In addition, considering that different types of burying points have different priorities, if the burying point data of different types of burying points is not distinguished and is uniformly stored in a same distributed stream processing platform, the burying point data of different types of burying points may affect each other, for example, due to excessive load of the single distributed stream processing platform, the burying point test platform preferentially consumes burying point data of a burying point type with low priority, and the burying point test platform fails to timely consume burying point data of a burying point type with high priority, thereby causing poor timeliness of verification of the burying point data of the burying point type with high priority. Based on this problem, different distributed stream processing platforms are allocated for burying point data of each type of burying point, so that the burying point data service platform writes the to-be-verified burying point data into the distributed stream processing platform corresponding to the second identifier, so as to ensure that the burying point data of different types of burying points do not affect each other, thereby ensuring the timeliness of verification of the burying point data of the burying point type with high priority.

[0090] Specifically, the burying point data service platform obtains, for each newly added type of burying point, configuration information of a distributed stream processing platform corresponding to the newly added type of burying point from a third-party service platform; next, based on the configuration information, the to-be-verified burying point data is written into the target distributed stream processing platform.

[0091] It should be noted that the specific implementation process between the burying point data service platform and the third-party service platform is specifically described in the above Figure 2 detailed description, which will not be described here.

[0092] Further, considering that for the application scenario of cross-platform burying point data collection, the burying point deployment environment can be diversified, and the burying point data can come from a mobile terminal, a web terminal, and a server; and considering that for the mobile terminal, it is impossible to know whether it is a test environment or an online environment, therefore, a specific way is needed to make the burying point data reported by the mobile terminal contain the first identifier, so that the burying point data service platform can identify which burying point data belongs to the to-be-verified burying point data. Based on this, the user terminal includes at least one of a mobile terminal of a test personnel, a web terminal, and a server corresponding to the web terminal; In the case where the user terminal is the mobile terminal of the test personnel, the first identifier is obtained by performing a scanning operation on a two-dimensional code on a front-end page of the burying point test platform; In the case where the user terminal is the web terminal or the server, the first identifier is used to represent that the burying point data comes from a test environment.

[0093] Specifically, for the tester's mobile terminal, it is impossible to know whether it is a test environment or an online environment based on the data packet, and the tester needs to use the mobile terminal to scan the specified QR code on the front-end page of the buried point test platform; correspondingly, the buried point test platform responds to the scanning operation of the tester's mobile terminal and sends a first identifier to the user terminal; therefore, the tester's user terminal contains the first identifier for the buried point data generated by the buried point to be tested; based on this, on the one hand, the buried point data service platform can filter out the buried point data to be verified from a large amount of buried point data by identifying whether the buried point data contains the first identifier; on the other hand, based on the first identifier, the buried point data verification result can be displayed on the front-end page corresponding to the tester.

[0094] For the tester's web terminal and the server corresponding to the web terminal, it can be known whether it is a test environment or an online environment based on the data packet. Therefore, if it is currently in a test environment, the tracking data generated by the web terminal or the server corresponding to the web terminal contains a first identifier, which indicates that the tracking data is generated in a test environment. In addition, the tracking test platform can also be triggered to return the first identifier through specific operations. The first identifier can be the front-end page association identifier returned by the tracking test platform in response to the tester's triggering operation on a specified control on the front-end page of the tracking test platform.

[0095] In some example embodiments, the triggering operation includes a click operation on a designated control, and the designated control is used to indicate that the user terminal is the tester's Web terminal or the server corresponding to the Web terminal; correspondingly, the buried point test platform sends a first identifier to the user terminal in response to the tester's click operation on the designated control; in this way, the tester's user terminal, the buried point data generated for the buried point to be tested contains the first identifier, and the buried point data service platform can also filter out the buried point data to be verified from a large amount of buried point data by identifying whether the buried point data contains the first identifier. In addition, the buried point data verification result can also be displayed on the front-end page corresponding to the tester based on the first identifier. The first identifier can be the front-end page association identifier returned by the buried point test platform in response to the tester's click operation on the designated control on the front-end page.

[0096] In an embodiment of the present application, by distinguishing the burying point deployment environment, for the tester's mobile terminal, by scanning the code, the burying point data generated contains a first identifier, so that the tester's user terminal is associated with the front-end page of the burying point test platform; and for the tester's Web terminal and the server corresponding to the Web terminal, the first identifier is used to identify whether the burying point data is generated in the test environment to filter out the target data to be verified; and based on the first identifier in the burying point data to be verified, the tester's user terminal can be associated with the front-end page of the burying point test platform.

[0097] It can be understood that whether it is a mobile terminal, a web terminal or a server terminal, the tester's user terminal can be associated with the front-end page of the tracking test platform through the first identifier, so that the tracking data verification results can be displayed on the front-end page corresponding to the tester, so that the tester can quickly view the verification results of the tracking data uploaded by his user terminal.

[0098] In the solution provided by the embodiment of the present application, when the burial point data service platform writes the burial point data containing the first identifier as the burial point data to be verified into the target distributed stream processing platform, the burial point testing platform obtains the burial point data to be verified from the target distributed stream processing platform; and, based on the burial point data verification rules corresponding to the second identifier in the burial point data to be verified, the burial point data to be verified is verified to obtain the burial point data verification result. In this way, on the one hand, the buried point data service platform filters out the buried point data to be verified based on the first identifier in the buried point data, so that the buried point data to be verified can be transmitted to the buried point test platform in a targeted manner without changing the original system architecture for reporting the buried point data; on the other hand, since the target distributed stream processing platform is a distributed stream processing platform corresponding to the second identifier in the buried point data to be verified, the second identifier represents the buried point type corresponding to the buried point data to be verified. Therefore, the buried point data collected for buried point types of different buried point types can be written into different distributed stream processing platforms, that is, the buried point data corresponding to different buried point types are written into their respective corresponding distributed stream processing platforms, thereby ensuring that the buried point data corresponding to different buried point types do not affect each other, and further ensuring the verification timeliness of the buried point data corresponding to the buried point type with high priority.

[0099] The collection of buried point data provided in the embodiment of the present application is based on the same inventive concept as the verification method of buried point data provided in the aforementioned embodiment of the present application and has the same beneficial effects.

[0100] Based on the same inventive concept, a device for verifying buried point data is also provided in an embodiment of the present application. The method corresponding to the device may be the method for verifying buried point data in the aforementioned embodiment, and its principle of solving the problem is similar to that of the method. The device for verifying buried point data provided in an embodiment of the present application may implement the aforementioned method for verifying buried point data, and the device for verifying buried point data may be implemented through software, hardware, or a combination of software and hardware. For example, the device for verifying buried point data is provided on a buried point test platform, and may include integrated or separate functional modules or units to execute the corresponding steps in the aforementioned methods. Since the device embodiment is basically similar to the method embodiment, the description is relatively simple, and the relevant parts may refer to the partial description of the method embodiment. The device embodiment described below is merely illustrative. As Figure 5 As shown, the verification device of the buried data may include: The buried point data acquisition module 501 is configured to acquire to-be-verified buried point data from a target distributed stream processing platform; the to-be-verified buried point data is buried point data containing a first identifier and a second identifier, the first identifier represents a data source of the to-be-verified buried point data, the second identifier represents a buried point type corresponding to the to-be-verified buried point data, and the target distributed stream processing platform is a distributed stream processing platform corresponding to the second identifier; The verification rule acquisition module 502 is configured to acquire a buried point data verification rule corresponding to the second identifier; The buried point data verification module 503 is configured to verify the to-be-verified buried point data based on the buried point data verification rule to obtain a buried point data verification result.

[0101] In some changed embodiments, the buried point data verification rule includes a plurality of attribute fields and compliance constraint conditions of each attribute field; and the buried point data verification module 503 is specifically configured to: perform structural processing on the to-be-verified buried point data based on the plurality of attribute fields to obtain structured buried point data; the structured buried point data includes the plurality of attribute fields and field values corresponding to the attribute fields; For each attribute field, the field value of the attribute field is verified based on the compliance constraint condition of the attribute field to obtain a buried point data verification result.

[0102] In some changed embodiments, the verification rule acquisition module 502 is specifically configured to: acquire the buried point data verification rule corresponding to the second identifier from a third-party service platform; the buried point data verification rule is generated by the third-party service platform in response to a verification rule predefinition request of a first terminal device in the case of adding a buried point type.

[0103] In some changed embodiments, the apparatus further includes a configuration information acquisition module configured to: acquire configuration information of an added distributed stream processing platform from a third-party service platform; the configuration information is generated by the third-party service platform in response to a buried point registration request of a second terminal device in the case of adding a buried point type, and the second identifier corresponding to the added distributed stream processing platform is returned to the second terminal device, the second identifier is used to be added to a buried point code corresponding to the added buried point type, and buried point data generated by triggering a data collection logic of the buried point code includes the second identifier; The buried point data acquisition module 501 is specifically configured to: acquire to-be-verified buried point data from a target distributed stream processing platform based on the configuration information.

[0104] In some modified implementations, the device further includes a verification result display module configured to: The result of the burying point data verification is displayed on the front-end page of the burying point test platform corresponding to the first identifier.

[0105] In some variations of the embodiment, the apparatus further comprises: a verification delay determination module configured to: Obtaining a reporting timestamp of the buried data to be verified and a display timestamp of a verification result of the buried data; Based on the reporting timestamp and the display timestamp, a verification delay judgment result of the buried data to be verified is generated.

[0106] The verification device for buried point data provided in the embodiment of the present application is based on the same inventive concept as the verification method for buried point data provided in the aforementioned embodiment of the present application and has the same beneficial effects.

[0107] Based on the same inventive concept, a device for collecting buried data is also provided in an embodiment of the present application. The method corresponding to the device may be the method for collecting buried data in the aforementioned embodiment, and its principle of solving the problem is similar to that of the method. The device for collecting buried data provided in an embodiment of the present application can implement the aforementioned method for collecting buried data, and the device for collecting buried data can be implemented through software, hardware, or a combination of software and hardware. For example, the device for collecting buried data is provided on a buried data service platform, and may include integrated or separate functional modules or units to execute the corresponding steps in the aforementioned methods. Since the device embodiment is basically similar to the method embodiment, the description is relatively simple, and the relevant parts may refer to the partial description of the method embodiment. The device embodiment described below is merely illustrative. As Figure 6 As shown, the device for collecting buried data may include: The tracking data receiving module 601 is used to receive tracking data reported by the user terminal; The buried point data filtering module 602 is configured to determine the buried point data as the buried point data to be verified if the buried point data includes a first identifier; wherein the first identifier indicates a data source of the buried point data to be verified; The buried point data writing module 603 is used to write the buried point data to be verified into the distributed stream processing platform corresponding to the second identifier in the buried point data; wherein, the second identifier represents the buried point type corresponding to the buried point data.

[0108] In some modified implementations, the user terminal includes at least one of a tester's mobile terminal, a web terminal, and a server corresponding to the web terminal; In the case where the user terminal is a mobile terminal of the tester, the first identifier is obtained by scanning a QR code on a front-end page of the embedded point testing platform; When the user terminal is the Web terminal or the server terminal, the first identifier is used to indicate that the tracking data comes from the test environment.

[0109] The device for collecting buried point data provided in the embodiment of the present application is based on the same inventive concept as the method for collecting buried point data provided in the aforementioned embodiment of the present application and has the same beneficial effects.

[0110] Based on the same inventive concept, the present application also provides a verification system for buried data. The corresponding method of the system can be the verification method and collection method of buried data in the aforementioned embodiment, and the principle of solving the problem is similar to that of the method. Among them, the verification system for buried data, wherein the system includes: a user terminal, a buried data service platform, multiple distributed stream processing platforms, and a buried test platform; The user terminal is used to report the tracking data to the tracking data service platform; The buried point data service platform is used to receive the buried point data; if the buried point data includes a first identifier, the buried point data is determined to be buried point data to be verified, and the buried point data to be verified is written into a distributed stream processing platform corresponding to a second identifier in the buried point data; wherein the first identifier represents the data source of the buried point data to be verified, and the second identifier represents the buried point type corresponding to the buried point data to be verified; The distributed stream processing platform is used to store the buried point data to be verified; The buried point testing platform is used to obtain the buried point data to be verified from the target distributed stream processing platform, and verify the buried point data to be verified based on the buried point data verification rules corresponding to the second identifier to obtain the buried point data verification results; the target distributed stream processing platform is the distributed stream processing platform corresponding to the second identifier.

[0111] In some modified implementations, the system further includes: a third-party service platform; The third-party service platform is used to generate the burying point data verification rules for each newly added burying point type in response to the verification rule pre-defined request of the first terminal device.

[0112] In some altered embodiments, the third-party service platform is further configured to, in response to a registration request for the embedded point of the second terminal device, generate configuration information of the newly added distributed stream processing platform, and return a second identifier corresponding to the newly added distributed stream processing platform to the second terminal device; the second identifier is used to be added to the embedded point code corresponding to the newly added embedded point type, and the embedded point data generated by triggering the data collection logic of the embedded point code includes the second identifier.

[0113] The verification system for embedded point data provided in the embodiments of the present application has the same inventive concept and beneficial effects as the verification method and collection method for embedded point data provided in the foregoing embodiments of the present application.

[0114] Based on the same inventive concept, the embodiments of the present application further provide an electronic device, the method corresponding to the electronic device can be the verification method or collection method for embedded point data in the foregoing embodiments, and the problem solving principle is similar to the method. The electronic device provided in the embodiments of the present application comprises at least one processor and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the verification method and / or technical solution for embedded point data or the collection method and / or technical solution for embedded point data of the foregoing embodiments of the present application.

[0115] The electronic device can be a user device, or a device integrated by a user device and a network device through a network, or can also be an application program running on the above device, the user device includes but is not limited to computers, mobile phones, tablet computers, smart watches, wristbands and various terminal devices, and the network device includes but is not limited to network hosts, single network servers, multiple network server sets or computer sets based on cloud computing, which can be used to realize part of the processing function when setting an alarm. Here, the cloud is composed of a large number of hosts or network servers based on cloud computing, wherein cloud computing is a kind of distributed computing, which is composed of a virtual computer formed by a group of loosely coupled computer sets.

[0116] Figure 7 The structure of an electronic device suitable for implementing the method and / or technical solution in the embodiments of the present application is shown as follows: Figure 7As illustrated, the electronic device 700 includes a central processing unit (CPU) 701 that can perform various appropriate actions and processes in accordance with a program stored in a read only memory (ROM) 702 or a program loaded from a storage section 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for system operation are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0117] Connected to the I / O interface 705 are an input section 706 including a keyboard, a mouse, a touch panel, a microphone, an infrared sensor, and the like; an output section 707 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), an LED display, an OLED display, and the like, and a speaker, and the like; a storage section 708 including one or more computer readable media such as a hard disk, a compact disk, a magnetic disk, a semiconductor memory, and the like; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card, a modem, and the like. The communication section 709 performs communication processing via a network such as the Internet.

[0118] In particular, the methods and / or embodiments in the embodiments of the present application can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product including a computer program carried on a computer readable medium, the computer program containing program codes for executing the methods illustrated in the flowcharts. When the computer program is executed by the central processing unit (CPU) 701, the above-mentioned functions defined in the methods of the present application are executed.

[0119] Another embodiment of the present application also provides a computer readable storage medium having stored thereon computer program instructions, which can be executed by a processor to implement the method and / or technical solutions of any one or more embodiments of the present application.

[0120] In particular embodiments, one or more computer programs can be employed to implement the methods and techniques described herein. In particular embodiments, the programs comprise code segments that are executed by one or more processors to perform the techniques described herein. In particular embodiments, the programs can be written in any combination of one or more programming languages, including an object- oriented programming language such as Java, Smalltalk, C++, or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0121] The computer readable medium can include a computer-readable signal medium and / or computer-readable storage medium. A computer-readable signal medium can include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal can take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium that is not a computer-readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0122] Program code embodied on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0123] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0124] The flow diagrams and block diagrams in the drawings are presented to illustrate the architecture, functionality, and operation of possible implementations of devices, methods and computer program products according to various embodiments disclosed. In this regard, each block in the flow diagrams and block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flow diagrams, and combinations thereof, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or combinations of special purpose hardware and

[0125] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0126] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are merely schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or page components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0127] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0128] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of hardware plus software functional unit.

[0129] The integrated unit implemented in the form of software function unit can be stored in a computer readable storage medium. The software function unit is stored in a storage medium, and includes a plurality of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute part of steps of the method described in various embodiments of the present application. The storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various storage media that can store program codes.

[0130] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements for some technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

[0131] In addition, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. The plurality of units or devices stated in the device claim can also be implemented by one unit or device through software or hardware. The words first, second, etc. are used to indicate names, and not to indicate any particular order.

Claims

1. A method for verifying buried point data, wherein: Applied to a tracking test platform, the method includes: Obtain the buried data to be verified from the target distributed stream processing platform; wherein the buried data to be verified is buried data including a first identifier and a second identifier, the first identifier represents the data source of the buried data to be verified, the second identifier represents the buried type corresponding to the buried data to be verified, and the target distributed stream processing platform is the distributed stream processing platform corresponding to the second identifier; Obtaining a data verification rule corresponding to the second identifier; Based on the buried point data verification rules, the buried point data to be verified is verified to obtain the buried point data verification result.

2. The method for verifying buried point data according to claim 1, wherein: The embedded data verification rules include multiple attribute fields and compliance constraints of each attribute field; The step of verifying the buried point data to be verified based on the buried point data verification rule to obtain the buried point data verification result includes: Based on the multiple attribute fields, the to-be-verified buried point data is structured to obtain structured buried point data; wherein the structured buried point data includes the multiple attribute fields and the field values ​​corresponding to each of the attribute fields; For each of the attribute fields, based on the compliance constraints of the attribute field, the field value of the attribute field is verified to obtain the buried data verification result.

3. The method for verifying buried point data according to claim 2, wherein: The obtaining of the buried data verification rule corresponding to the second identifier includes: Obtain the buried point data verification rules corresponding to the second identifier from the third-party service platform; the buried point data verification rules are generated by the third-party service platform in response to the verification rule predefined request of the first terminal device when a new buried point type is added.

4. The method for verifying buried point data according to claim 1, wherein: The method further comprises: Obtain configuration information of a newly added distributed stream processing platform from a third-party service platform; wherein, in the case of a newly added burying point type, the configuration information is generated by the third-party service platform in response to a burying point registration request of a second terminal device, and a second identifier corresponding to the newly added distributed stream processing platform is returned to the second terminal device, and the second identifier is used to be added to the burying point code corresponding to the newly added burying point type, and the burying point data generated by the data collection logic of the burying point code being triggered includes the second identifier; The step of obtaining the tracking data to be verified from the target distributed stream processing platform includes: Based on the configuration information, the embedded data to be verified is obtained from the target distributed stream processing platform.

5. The method for verifying buried point data according to claim 1, wherein: After verifying the buried point data to be verified and obtaining the buried point data verification result, the method further includes: The result of the burying point data verification is displayed on the front-end page of the burying point test platform corresponding to the first identifier.

6. The method for verifying buried point data according to claim 1, wherein: The method further comprises: Obtaining a reporting timestamp of the buried data to be verified and a display timestamp of a verification result of the buried data; Based on the reporting timestamp and the display timestamp, a verification delay judgment result of the buried data to be verified is generated.

7. A method for collecting buried data, wherein: Applied to a tracking data service platform, the method includes: Receive tracking data reported by user terminals; If the buried point data includes a first identifier, the buried point data is determined as the buried point data to be verified; wherein the first identifier represents the data source of the buried point data to be verified; The buried point data to be verified is written into a distributed stream processing platform corresponding to a second identifier in the buried point data; wherein the second identifier represents the buried point type corresponding to the buried point data.

8. The method for collecting buried point data according to claim 7, wherein: The user terminal includes at least one of a tester's mobile terminal, a web terminal, and a server corresponding to the web terminal; In the case where the user terminal is a mobile terminal of the tester, the first identifier is obtained by scanning a QR code on a front-end page of the embedded point testing platform; When the user terminal is the Web terminal or the server terminal, the first identifier is used to indicate that the tracking data comes from the test environment.

9. A device for verifying buried point data, wherein: Set up on the buried point test platform, the device includes: A buried point data acquisition module is used to obtain the buried point data to be verified from the target distributed stream processing platform; wherein the buried point data to be verified is the buried point data containing a first identifier and a second identifier, the first identifier represents the data source of the buried point data to be verified, the second identifier represents the buried point type corresponding to the buried point data to be verified, and the target distributed stream processing platform is the distributed stream processing platform corresponding to the second identifier; A verification rule acquisition module, configured to acquire a verification rule for the buried data corresponding to the second identifier; The buried point data verification module is used to verify the buried point data to be verified based on the buried point data verification rules to obtain the buried point data verification results.

10. A device for collecting buried data, wherein: Set up on the tracking data service platform, the device includes: The tracking data receiving module is used to receive the tracking data reported by the user terminal; A buried point data filtering module, configured to determine the buried point data as buried point data to be verified if the buried point data includes a first identifier; wherein the first identifier indicates a data source of the buried point data to be verified; A buried point data writing module is used to write the buried point data to be verified into a distributed stream processing platform corresponding to a second identifier in the buried point data; wherein, the second identifier represents the buried point type corresponding to the buried point data.

11. A verification system for buried point data, wherein: The system includes: a user terminal, a tracking data service platform, multiple distributed stream processing platforms, and a tracking test platform; The user terminal is used to report the tracking data to the tracking data service platform; The buried point data service platform is used to receive the buried point data; if the buried point data includes a first identifier, the buried point data is determined to be buried point data to be verified, and the buried point data to be verified is written into a distributed stream processing platform corresponding to a second identifier in the buried point data; wherein the first identifier represents the data source of the buried point data to be verified, and the second identifier represents the buried point type corresponding to the buried point data to be verified; The distributed stream processing platform is used to store the buried point data to be verified; The buried point testing platform is used to obtain the buried point data to be verified from the target distributed stream processing platform, and verify the buried point data to be verified based on the buried point data verification rules corresponding to the second identifier to obtain the buried point data verification results; the target distributed stream processing platform is the distributed stream processing platform corresponding to the second identifier.

12. The verification system for buried point data according to claim 11, wherein: The system also includes: a third-party service platform; The third-party service platform is used to generate the burying point data verification rules for each newly added burying point type in response to the verification rule pre-defined request of the first terminal device.

13. According to the verification system of the burial point data in claim 12, the third-party service platform is also used to generate configuration information of the newly added distributed stream processing platform in response to the burial point registration request of the second terminal device, and return the second identifier corresponding to the newly added distributed stream processing platform to the second terminal device; the second identifier is used to be added to the burial point code corresponding to the newly added burial point type, and the burial point data generated when the data collection logic of the burial point code is triggered includes the second identifier.

14. An electronic device, comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 6 or any one of claims 7 to 8.

15. A computer-readable medium having computer program instructions stored thereon, wherein the computer program instructions can be executed by a processor to implement the method according to any one of claims 1 to 6 or any one of claims 7 to 8.

16. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 6 or any one of claims 7 to 8.

Images