Methods, devices, electronic equipment, and media for determining business data paths

Abstract

This application discloses a method, apparatus, electronic device, and medium for determining business data paths, belonging to the field of computer technology. The method includes: acquiring multiple first business data sets, where the first business data are data generated during application runtime; dividing the multiple first business data sets into business data sets corresponding to each version information based on the application version information contained in each first business data set, wherein any business data set corresponding to a version information set includes multiple first business data sets with the same version information; and determining the business data path corresponding to each version information set based on the business data sets corresponding to each version information set. This application can accurately determine the business data path corresponding to the version information of the actually running application, which is beneficial for the analysis and processing of application runtime.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, electronic device, and medium for determining business data paths. Background Technology

[0002] With the development of computer technology, the types and number of applications are increasing. An application can support at least one business function, and each business function has a corresponding business process. For example, the business process of facial recognition includes: entering the facial recognition page - detecting the face - outputting the facial recognition result. Each business process can be described using a business data path. Furthermore, different versions of the application support different business processes; that is, different versions correspond to different business data paths.

[0003] In related technologies, the business data paths corresponding to each version of the application are determined by analyzing the application code corresponding to each version. However, since only a portion of the application corresponding to each version is actually running, the above technologies cannot accurately determine the business data paths corresponding to the actual running application version, thus affecting the analysis and processing of application operation. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and medium for determining business data paths, which can be used to solve the problem that related technologies cannot accurately determine the business data path corresponding to the version information of the actually running application, thereby affecting the analysis and processing of the application's operation. The technical solution includes the following contents.

[0005] On one hand, embodiments of this application provide a method for determining a business data path, the method comprising:

[0006] Obtain multiple first business data, which are data generated during application runtime;

[0007] Based on the application version information contained in each first business data, the multiple first business data are divided into business data sets corresponding to each version information, and any business data set corresponding to a version information includes multiple first business data with the same version information.

[0008] Based on the business data sets corresponding to each version information, the business data paths corresponding to each version information are determined respectively.

[0009] On the other hand, embodiments of this application provide a device for determining a business data path, the device comprising:

[0010] The acquisition module is used to acquire multiple first business data, which are data generated during application runtime.

[0011] The partitioning module is used to partition the multiple first business data into business data sets corresponding to each version information based on the version information of the application contained in each first business data. Each business data set corresponding to a version information includes multiple first business data with the same version information.

[0012] The determination module is used to determine the business data path corresponding to each version information based on the business data set corresponding to each version information.

[0013] In one possible implementation, the acquisition module is used to extract multiple second business data from the database, the second business data being data generated by the application during the previous time period; and to clean the multiple second business data to obtain the multiple first business data.

[0014] In one possible implementation, the plurality of first business data are stored in at least two data tables; the partitioning module is used to aggregate each of the first business data in the at least two data tables into a wide table; based on the application version information contained in each of the first business data in the wide table, the plurality of first business data are partitioned into business data sets corresponding to each version information.

[0015] In one possible implementation, the partitioning module is used to perform deduplication processing on each of the first business data to obtain multiple data nodes. Each data node includes multiple first business data with the same specified information, which includes the version information of the application. Based on the version information of the application contained in each data node, the multiple data nodes are divided into business data sets corresponding to each version information. Each business data set corresponding to any version information includes at least two data nodes with the same version information.

[0016] The determining module is used to connect each data node in the business data set corresponding to any version information to obtain the business data path corresponding to the any version information.

[0017] In one possible implementation, the device further includes:

[0018] The first display module is used to display each data node and the first business data contained in each data node;

[0019] The first adjustment module is configured to adjust the data node in response to receiving an adjustment operation on the data node based on the first service data contained in the data node.

[0020] In one possible implementation, the device further includes:

[0021] The second display module is used to display the business data path corresponding to any of the version information;

[0022] The second adjustment module is used to adjust the business data path corresponding to any version information in response to receiving an adjustment operation on the business data path corresponding to any version information.

[0023] In one possible implementation, the determining module is further configured to determine the information of each data node on the business data path corresponding to the any version information based on the quantity of first business data contained in each data node on the business data path corresponding to the any version information, wherein the information of the data node includes at least one of the conversion rate or churn rate of the data node.

[0024] In one possible implementation, the determining module is further configured to determine the path coverage corresponding to any version information based on the number of business data paths corresponding to any version information.

[0025] In one possible implementation, the device further includes:

[0026] The merging module is used to determine at least two specified business data paths from the business data paths corresponding to each version information, and to merge the at least two specified business data paths to obtain a business data path diagram.

[0027] The third display module is used to display the business data path diagram.

[0028] In one possible implementation, the device further includes:

[0029] The determining module is further configured to determine the specified version information selected by the target object from the various version information;

[0030] The filtering and display module is used to filter out target business data paths whose version information is not lower than the specified version information from the business data paths corresponding to each version information, and display the target business data paths.

[0031] On the other hand, embodiments of this application provide an electronic device, which includes a processor and a memory. The memory stores at least one piece of program code, which is loaded and executed by the processor to enable the electronic device to implement any of the above-described methods for determining the business data path.

[0032] On the other hand, a computer-readable storage medium is also provided, wherein at least one piece of program code is stored in the computer-readable storage medium, the at least one piece of program code being loaded and executed by a processor to enable a computer to implement any of the above-described methods for determining business data paths.

[0033] On the other hand, a computer program or computer program product is also provided, wherein the computer program or computer program product stores at least one computer instruction, which is loaded and executed by a processor to enable the computer to implement any of the above-mentioned methods for determining business data paths.

[0034] The technical solution provided in this application has at least the following beneficial effects:

[0035] The technical solution provided in this application embodiment is based on the application version information contained in each first business data generated during application runtime, and determines the business data path corresponding to each version information. This achieves accurate determination of the business data path corresponding to the version information of the actually running application, which is beneficial for the analysis and processing of application runtime. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 This is a schematic diagram illustrating the implementation environment of a method for determining a business data path provided in an embodiment of this application;

[0038] Figure 2 This is a flowchart illustrating a method for determining a business data path provided in an embodiment of this application;

[0039] Figure 3 This is a schematic diagram of a display page provided in an embodiment of this application;

[0040] Figure 4 This is a schematic diagram of another display page provided in an embodiment of this application;

[0041] Figure 5This is a schematic diagram of another display page provided in an embodiment of this application;

[0042] Figure 6 This is a schematic diagram illustrating the merging of business data paths provided in an embodiment of this application;

[0043] Figure 7 This is a schematic diagram of a business data path provided in an embodiment of this application;

[0044] Figure 8 This is a schematic diagram illustrating the determination of a business data path provided in an embodiment of this application;

[0045] Figure 9 This is a schematic diagram illustrating the establishment of a business data path diagram provided in an embodiment of this application;

[0046] Figure 10 This is a schematic diagram of the structure of a business data path determination device provided in an embodiment of this application;

[0047] Figure 11 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0048] Figure 12 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of this application clearer, the terms involved in the embodiments of this application will first be explained and described.

[0050] Business data: Specific data collected through event tracking code. Typically, the terminal device transmits business data to the backend server, which then stores the business data in its database. Business data is a string containing accompanying information.

[0051] Data node: An entity node obtained by standardizing and normalizing business data.

[0052] Business data path: A directed path consisting of data nodes.

[0053] Business data path graph: A directed acyclic graph formed by merging at least two business data paths.

[0054] The embodiments of this application will now be described in further detail with reference to the accompanying drawings.

[0055] Figure 1 This is a schematic diagram illustrating the implementation environment of a method for determining a business data path provided in an embodiment of this application, such as... Figure 1The implementation environment shown includes an electronic device 11, and the method for determining the business data path in this embodiment can be executed by the electronic device 11. Exemplarily, the electronic device 11 may include at least one of a terminal device or a server.

[0056] The terminal device can be at least one of a smartphone, game console, desktop computer, tablet computer, e-book reader, MP3 (Moving Picture Experts Group Audio Layer III) player, MP4 (Moving Picture Experts Group Audio Layer IV) player, and laptop computer.

[0057] The server can be a single server, a server cluster consisting of multiple servers, or any of the following: a cloud computing platform or a virtualization center. This application embodiment does not limit this. The server can communicate with terminal devices via a wired or wireless network. The server can have functions such as data processing, data storage, and data transmission and reception, which are not limited in this application embodiment.

[0058] The various optional embodiments of this application can be implemented based on cloud technology, which refers to a hosting technology that unifies a series of resources such as hardware, software, and networks within a wide area network or local area network to realize the computation, storage, processing, and sharing of data.

[0059] Cloud technology is a collective term for network technologies, information technologies, integration technologies, management platform technologies, and application technologies applied to the cloud computing business model. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will all require robust system support, which can only be achieved through cloud computing.

[0060] Based on the above implementation environment, this application provides a method for determining business data paths, in order to Figure 2 The flowchart shown in this embodiment of the present application illustrates a method for determining a business data path. This method can be implemented by... Figure 1 The electronic device 11 in the middle performs the operation. For example... Figure 2 As shown, the method includes steps 201 to 203.

[0061] Step 201: Obtain multiple first business data. The first business data is data generated during application runtime.

[0062] In this embodiment, tracking code is included in the application code. Tracking code, also known as monitoring code, is a piece of code added to the application code where business data needs to be monitored. During the execution of the application code, business data is collected through the tracking code.

[0063] Running an application is the process of executing its code. For any given application, there is at least one version, and any application with any version can be installed on any terminal device. During operation, an application on any terminal device continuously generates business data in real time; this business data is used to record the application's running status.

[0064] Any terminal device can report business data generated by its application during runtime to a backend server. The backend server stores the reported business data in a database in real time, or it stores the business data reported by each terminal device at regular intervals. This database, referred to as the reporting database, is used to store the business data reported by the terminal devices. This application does not limit the time interval; for example, the time interval is one minute.

[0065] In this embodiment of the application, any business data generated during the application runtime can be first business data, or any business data generated during the application runtime can be second business data. The first business data is business data obtained after cleaning the second business data, which will be described in detail below.

[0066] In one possible implementation, obtaining multiple first business data includes: extracting multiple second business data from a database, the second business data being data generated by the application during the previous time period; and cleaning the multiple second business data to obtain multiple first business data.

[0067] Applications generate business data continuously in real time during runtime. Numerous terminal devices report this data to the backend server, which then stores this data in a database. Consequently, the amount of business data in the database is enormous, typically in the hundreds of millions. Due to computational speed bottlenecks, processing hundreds of millions of data points is extremely time-consuming and prone to crashes.

[0068] To address the aforementioned issue, business data generated by the application during the previous time period is extracted from the database, resulting in multiple sets of second business data. By reducing the amount of business data acquired in the current time period, the computation time is reduced. This application does not limit the time period; for example, a time period may be several hours, several days, several weeks, several months, etc.

[0069] In this embodiment of the application, multiple second business data can be directly used as multiple first business data, or multiple second business data can be cleaned to remove non-compliant business data and obtain multiple first business data.

[0070] Optionally, for any one of the multiple second business data, if the second business data complies with the data compliance rules, it is retained and used as a first business data; if the second business data does not comply with the data compliance rules, it is deleted. This application embodiment does not limit the data compliance rules.

[0071] In this embodiment of the application, the first business data includes error codes, application version information, data source protocol identifier (Identity Document, ID), page location, browser / server architecture error codes (BS Error Code), and other information.

[0072] It should be noted that for each time period, business data generated by the application during the previous time period can be extracted from the database to obtain multiple sets of second business data. These second sets of business data can then be used as first sets of business data, or the multiple sets of second business data can be cleaned to obtain multiple sets of first business data.

[0073] Step 202: Based on the application version information contained in each first business data, the multiple first business data are divided into business data sets corresponding to each version information. Each business data set corresponding to a version information includes multiple first business data with the same version information.

[0074] In this embodiment of the application, the first business data is data generated during the runtime of the application, and any first business data contains the version information of the application.

[0075] For any two pieces of first business data from a plurality of first business data, if the application version information contained in these two pieces of first business data is the same, then these two pieces of first business data are grouped into one business data set. If the application version information contained in these two pieces of first business data is different, then these two pieces of first business data are grouped into two different business data sets. In this way, the plurality of first business data is divided to obtain at least two business data sets, and each business data set contains all the first business data with the same version information.

[0076] In this context, the version information corresponding to any business data set is the version information of the application contained in the first business data within that business data set. In other words, the version information of each piece of first business data within any given business data set is the version information corresponding to that entire business data set.

[0077] In one possible implementation, multiple first business data are stored in at least two data tables; based on the application version information contained in each first business data, the multiple first business data are divided into business data sets corresponding to each version information, including: aggregating each first business data in the at least two data tables into a wide table; based on the application version information contained in each first business data in the wide table, the multiple first business data are divided into business data sets corresponding to each version information.

[0078] In this embodiment of the application, any one of the first service data is stored in a data table. A data table can store at least one first service data. Therefore, multiple first service data can be stored in the same data table or in different data tables.

[0079] When multiple primary business data are stored in at least two tables, to facilitate calculations, the primary business data from these tables can be aggregated into a single table, called a wide table. A wide table, literally meaning a table with many fields, typically refers to a table that links business-related metrics, dimensions, and attributes together. Because wide tables store different content in the same table, they do not conform to the third normal form model design specifications and have the disadvantage of significant data redundancy. However, the corresponding advantage is improved query performance and convenience.

[0080] Alternatively, the Join operation in MySQL (My Structured Query Language, a relational database management system) can be used to aggregate the first business data from at least two data tables into a wide table.

[0081] The wide table in this embodiment includes multiple first service data. For any two first service data in the wide table, if the application version information contained in these two first service data is the same, then these two first service data are divided into one service data set. If the application version information contained in these two first service data is different, then these two first service data are divided into two different service data sets. In this way, multiple first service data are divided into service data sets corresponding to various version information.

[0082] Step 203: Based on the business data set corresponding to each version information, determine the business data path corresponding to each version information.

[0083] In this embodiment of the application, for any set of business data corresponding to version information, the business data path corresponding to the version information can be determined based on each first business data in the set of business data. The number of business data paths corresponding to the version information is at least one.

[0084] In one possible implementation, based on the application version information contained in each first business data, multiple first business data are divided into business data sets corresponding to each version information, including: deduplicating each first business data to obtain multiple data nodes, each data node including multiple first business data with the same specified information, the specified information including application version information; based on the application version information contained in each data node, the multiple data nodes are divided into business data sets corresponding to each version information, each business data set corresponding to any version information includes at least two data nodes with the same version information; based on the business data sets corresponding to each version information, the business data paths corresponding to each version information are determined, including: for any version information, connecting each data node in the business data set corresponding to any version information to obtain the business data path corresponding to any version information.

[0085] In this embodiment, a data node is an entity obtained by abstracting the first business data. This entity can represent an event; for example, a data node can be "facial recognition". It is understood that a data node can include various types of information. For example, a data node may include, but is not limited to, event name (Action), event identifier, business process node, event level, application version information, etc., where the event name can be "facial recognition".

[0086] Optionally, a mapping table between the first business data and data nodes is pre-configured. The mapping table includes multiple mapping relationships, where each mapping relationship is a mapping between specified information in the first business data and a data node. The specified information in the first business data includes, but is not limited to, application version information. For example, the specified information in the first business data includes application version information, data source protocol identifier, and error code.

[0087] For any first business data, match the specified information in the first business data with the mapping relationship table to determine the target mapping relationship corresponding to the specified information in the first business data, and determine the data node in the target mapping relationship as the data node corresponding to the first business data.

[0088] It is understandable that one piece of primary business data corresponds to one data node, and one data node corresponds to at least one piece of primary business data. By determining the data node corresponding to each piece of primary business data through a mapping relationship table, multiple pieces of primary business data can be deduplicated to obtain multiple data nodes.

[0089] Optionally, after deduplicating each set of first business data to obtain multiple data nodes, for any two data nodes, if the application version information contained in these two data nodes is the same, then these two data nodes are assigned to the same business data set. If the application version information contained in these two data nodes is different, then these two data nodes are assigned to two different business data sets. In this way, multiple data nodes are divided to obtain at least two business data sets, and each business data set contains data nodes with the same version information.

[0090] In this context, the version information corresponding to any business data set is the version information of the application contained in the data nodes of that business data set. In other words, the version information of each data node in any business data set corresponding to a given version information is the version information of that business data set.

[0091] Next, for any set of business data corresponding to any version information, determine the order of each data node in the set of business data, and connect each data node in the set of business data according to the order of the data nodes in the set of business data to obtain the business data path corresponding to any version information.

[0092] For example, a business data set corresponding to a version information includes data nodes A to D. After determining the order of the data nodes in the business data set as data node A, data node C, data node D, and data node B, data nodes A, C, D, and B are connected in sequence to obtain the business data path corresponding to the version information, that is, the business data path data node A-data node C-data node D-data node B.

[0093] Optionally, after deduplicating each first business data to obtain multiple data nodes, the method further includes: displaying each data node and the first business data contained in each data node; and adjusting any data node in response to receiving an adjustment operation on any data node based on the first business data contained in any data node.

[0094] In this embodiment, each data node and the first service data contained in each data node can be displayed on a designated terminal device. When the designated terminal device displays a data node, it can display all or part of the information contained in the data node. Similarly, when the designated terminal device displays the first service data contained in the data node, it can display all or part of the information contained in the first service data.

[0095] Please see Figure 3 , Figure 3 This is a schematic diagram of a display page provided in an embodiment of this application. The display page shows an information table, which includes data nodes and first business data contained in the data nodes.

[0096] Data nodes include an event identifier, event name, business process node, event level, and application version information. For example, for the data node shown in the second row, the event identifier is "1661", the event name is "Entering Facial Recognition Page", the business process node is "Page", the event level is "Normal", and the application version information is "Long Term Support (LTS) Version". Here, "Long Term Support (LTS) Version" represents all versions of the application.

[0097] The first business data contained in the data node includes behavior, BS error code, error code, data source protocol identifier, page, and page position. For example, for the first business data contained in the data node shown in the second row, the behavior of the first business data is "page turning", the BS error code of the first business data is "-", where "-" indicates that the display page does not display the BS error code, the error code of the first business data is "-", the data source protocol identifier of the first business data is "18771", the page of the first business data is "display page", and the page position of the first business data is "-".

[0098] In addition, the display page also shows operations for data nodes and / or the first business data contained in the data nodes. These operations can be modification or deletion. Optionally, the display page displays modification controls and deletion controls, where modification is performed using the modification controls and deletion is performed using the deletion controls. For example, for the data node shown in the second row, the display page displays modification controls for that data node.

[0099] Understandably, for Figure 3 Any line from the third to the last line in this embodiment will not be described in detail in this application, including the data node shown in that line, the first business data contained in the data node, and the operation. This information is related to... Figure 3 The information in the second line is similar, so I will not repeat it here.

[0100] In this embodiment of the application, the designated terminal device can receive an adjustment operation performed by the target object on any one of the displayed data nodes based on the first service data contained in any one of the data nodes, and adjust the data node based on the adjustment operation. Specifically, if the adjustment operation is a modification operation, the data node is modified, such as by modifying the event name of the data node; if the adjustment operation is a deletion operation, the data node is deleted; and if the adjustment operation is a addition operation, a new data node is added.

[0101] like Figure 4 As shown, Figure 4 This is a schematic diagram of another display page provided in an embodiment of this application. The upper left corner of this display page displays "Add," indicating that this display page is for adding a new data node. An information table is displayed on this page, in which data nodes can be set, including event identifiers, event names, business process nodes, event levels, and application version information. However, the first business data contained in the data node cannot be set; that is, actions, BS error codes, error codes, data source protocol identifiers, pages, and page positions cannot be set. Furthermore, operations targeting the data node cannot be set.

[0102] The display page also shows a cancel control, an add row control, a reset control, and a add control. Optionally, clicking the cancel control returns the user to the previous page. Clicking the add row control adds a new row to the information table on the display page. Clicking the reset control resets the information table on the display page. Clicking the add control adds a new column to the information table on the display page, or loads and displays a new page with a newly added data node.

[0103] The preceding text described how to connect the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to that version information. Optionally, after connecting the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to that version information, the process further includes: displaying the business data path corresponding to that version information; and adjusting the business data path corresponding to that version information in response to receiving an adjustment operation.

[0104] This application embodiment can also display the business data path corresponding to any version information on a designated terminal device. The designated terminal device can receive adjustment operations performed by the target object on the business data path corresponding to any version information, and adjust the business data path corresponding to the any version information based on the adjustment operation. Specifically, if the adjustment operation is a modification operation, the business data path corresponding to the any version information is modified, for example, by deleting data nodes on the business data path, adding new data nodes to the business data path, or modifying the data nodes on the business data path.

[0105] Please see Figure 5 , Figure 5 This is a schematic diagram of another display page provided in an embodiment of this application. On this display page, clicking the "Node Configuration" control will take you to the display page for configuring data nodes, clicking the "Path Configuration" control will take you to the display page for configuring business data paths, and clicking the "Path Graph" control will take you to the display page for the business data path graph.

[0106] Figure 5 The displayed page is for configuring business data paths. Users can select paths on this page; that is, they can input information about the business data path to select it. For example, if a user inputs "facial recognition payment," the corresponding business data path for "facial recognition payment" will be selected. Users can also select nodes on this page; that is, they can input data nodes to select them. For example, if a user inputs "detect face," the corresponding data node for "detect face" will be selected.

[0107] The display page shows the user's selected business data path: "Enter Facial Recognition Page - Detect Face - Output Facial Recognition Result - Issue Code - Pay - Receive Payment Voucher". On this display page, controls can be adjusted to set read-only or edit mode. Figure 5 In read-only mode, users cannot adjust the business data path. In edit mode, users can adjust the business data path.

[0108] In edit mode, users can click the "Save" control to save the adjustments made to the business data path, click the "Add" control to add a data node or business data path, click the "Clear" control to delete a data node or business data path, click the "Copy" control to copy a data node or business data path, click the "Paste" control to paste a data node or business data path, click the "Rearrange" control to adjust the order of data nodes on the business data path (e.g., move "Code Output" before "Face Detection"), and click the "View Details" control to view detailed information about the business data path.

[0109] In one possible implementation, after connecting the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to any version information, the method further includes: determining the information of each data node on the business data path corresponding to any version information based on the number of first business data contained in each data node on the business data path corresponding to any version information, wherein the information of the data node includes at least one of the conversion rate or churn rate of the data node.

[0110] For any data node on the business data path corresponding to any version information, the data node contains at least one first business data, and the number of first business data contained in the data node can be counted.

[0111] Optionally, during the operation of the application on the terminal device, each time the application starts to execute a business function, the terminal device generates a session ID corresponding to that business function. Every piece of business data generated during the execution of that business function carries this session ID, and the session ID is unique.

[0112] For example, the business process of facial recognition includes: entering the facial recognition page - detecting the face - outputting the facial recognition result. When the facial recognition business begins, i.e., "entering the facial recognition page", a session identifier is generated. Throughout the entire facial recognition process, the business data corresponding to "entering the facial recognition page", "detecting the face", and "outputting the facial recognition result" all contain this session identifier.

[0113] For any data node on the business data path corresponding to any version information, the number of session identifiers contained in that data node can be counted, which is used as the number of first business data contained in that data node.

[0114] It should be noted that the embodiments of this application do not limit the session identifier. For example, the session identifier consists of at least one element selected from numbers, special characters (such as @, #, etc.), and English characters.

[0115] Using the above method, the quantity of first business data contained in each data node on the business data path corresponding to any version information can be determined. Then, based on the quantity of first business data contained in each data node on the business data path, information such as conversion rate and churn rate of each data node on the business data path can be determined.

[0116] Specifically, the conversion rate of any data node on the business data path is the ratio of the amount of first business data contained in that data node to the amount of first business data contained in the previous data node on the business data path. The sum of the churn rate and the conversion rate of any data node on the business data path equals 1.

[0117] The above method can be used to calculate the information of each data node in the business data path corresponding to each version information, and store the information of each data node in the business data path corresponding to each version information in the database.

[0118] In another possible implementation, after determining the business data path corresponding to each version information based on the business data set corresponding to each version information, it also includes: determining the path coverage corresponding to any version information based on the number of business data paths corresponding to any version information.

[0119] In this embodiment, the number of business data paths corresponding to any version information is at least one. Since the business data path corresponding to any version information is determined based on the first business data generated during application runtime, the business data path corresponding to any version information is a business data path that has already been executed.

[0120] It is understandable that during the operation of an application, there may be business data paths that have not been executed, and the total number of business data paths is the sum of the number of executed business data paths and the number of unexecuted business data paths.

[0121] In this embodiment of the application, the total number of paths corresponding to any version information can be obtained, and the ratio of the number of business data paths corresponding to any version information to the total number of paths can be used as the path coverage rate corresponding to any version information.

[0122] In another possible implementation, after determining the business data path corresponding to each version information based on the business data set corresponding to each version information, the method further includes: determining at least two specified business data paths from the business data paths corresponding to each version information, merging the at least two specified business data paths to obtain a business data path diagram; and displaying the business data path diagram.

[0123] In this embodiment, the target object can determine at least two specified business data paths from the business data paths corresponding to various version information through a specified terminal device. Any two specified business data paths can correspond to the same version information or different version information. Then, the identical data nodes on each pair of specified business data paths are merged into one, thereby merging at least two specified business data paths into a single business data path graph. This business data path graph reflects the application's operational status, facilitating the analysis and processing of the application's operational status.

[0124] Please see Figure 6 , Figure 6 This is a schematic diagram illustrating the merging of business data paths provided in an embodiment of this application. Figure 6 (1) shows two business data paths, one named "ABCD" and the other named "ABEF", where A, B, C, D, E, and F represent data nodes. These two business data paths contain the same data nodes A and B. Merging data node A in both business data paths into one, and merging data node B in both business data paths into one, yields the following result: Figure 6 The business data path diagram shown in (2) is as follows.

[0125] In this embodiment of the application, a business data path diagram can be displayed on a designated terminal device. It is understood that when displaying the business data path diagram, information about each data node on each business data path in the diagram can also be displayed, i.e., information about each data node on the business data path diagram.

[0126] Next, please see Figure 7 , Figure 7This is a schematic diagram of a business data path diagram provided in an embodiment of this application. The business data path diagram includes five data nodes: "Resource Exposure," "Click to Claim Resource," "Successful Claim," "Failed Claim," and "Claiming Exceeded Limit." This business data path diagram is derived from the merging of three business data paths: "Resource Exposure - Click to Claim Resource - Successful Claim," "Resource Exposure - Click to Claim Resource - Failed Claim," and "Resource Exposure - Click to Claim Resource - Claim Exceeded Limit."

[0127] Each data node includes information such as the number of sessions, the week-on-week comparison of session counts, and an indicator of the week-on-week comparison (e.g., a decrease indicator "↓" or an increase indicator "↑"). For example, the information for the data node "Resource Exposure" includes "Number of Sessions: 20329", "Week-on-Week Comparison: -58.29%" (i.e., the week-on-week comparison of session counts), and a decrease indicator "↓" for the week-on-week comparison. For information on other data nodes, please refer to [link to other data nodes]. Figure 7 This will not be elaborated upon further here. Some data nodes also include conversion rates and their week-over-week comparisons. For example, the data node "Click to Claim Resources" includes "Conversion Rate: 83.03%" and "Week-over-week: 0.32%" (i.e., the week-over-week conversion rate). For information on other data nodes, please refer to [link to relevant documentation]. Figure 7 This will not be elaborated upon here.

[0128] In one possible implementation, after determining the business data path corresponding to each version information based on the business data set corresponding to each version information, the method further includes: determining the specified version information selected by the target object from each version information; filtering out the target business data path whose version information is not lower than the specified version information from the business data paths corresponding to each version information, and displaying the target business data path.

[0129] In this embodiment, the target object can select a specified version information from various version information through a designated terminal device. For any business data path among the business data paths corresponding to each version information, if the version information of the business data path is not lower than the specified version information, then the business data path is the target business data path; if the version information of the business data path is lower than the specified version information, then the business data path is not the target business data path.

[0130] After selecting the target business data path, it is displayed on the designated terminal device. It is understood that when displaying the target business data path, information about each data node along that path can also be shown. There is at least one target business data path.

[0131] When there are at least two target business data paths, these two paths can be merged into a business data path diagram before being displayed on the designated terminal device. For details on how to merge at least two target business data paths into a business data path diagram, please refer to the description above regarding merging at least two specified business data paths to obtain the business data path diagram; it will not be repeated here.

[0132] The above mainly describes the method for determining the business data path provided in the embodiments of this application from the perspective of method steps. The following is a detailed embodiment to further illustrate the method for determining the business data path in the embodiments of this application.

[0133] Please see Figure 8 , Figure 8 This is a schematic diagram illustrating the determination of a business data path according to an embodiment of this application. Any terminal device can report business data to the reporting database; for example, terminal devices 1 to 5 all report business data to the reporting database. The business data refers to the data generated by the application on the terminal device during runtime.

[0134] The business data processing tool can periodically extract business data from the reporting database. For example, every hour, the tool can extract newly added business data from the database. The business data processing tool is an application on an electronic device used to process the business data.

[0135] Optionally, the business data processing tools include a business data processing layer, a data node processing layer, a business data path processing layer, and a business data path graph processing layer.

[0136] The business data processing layer cleanses the business data extracted from the reporting database (i.e., the second business data mentioned above) to obtain cleaned business data (i.e., the first business data mentioned above). Furthermore, the business data processing layer can deduplicate the cleaned business data, resulting in multiple data nodes. Each data node contains multiple cleaned business data entries, and the cleaned business data contained in each data node are stored in at least two data tables. In other words, multiple data nodes are stored in at least two data tables.

[0137] The data node processing layer can associate at least two data tables into a wide table. In other words, the data node processing layer can aggregate the data nodes from at least two data tables into a wide table, thereby enabling the aggregation of various cleaned business data into a wide table.

[0138] Next, the business data path processing layer groups data nodes according to version information. Based on the application version information contained in each data node, multiple data nodes are divided into business data sets corresponding to each version. Then, the data nodes in each business data set corresponding to any given version are connected to obtain the business data path for that given version. Finally, for each business data path corresponding to any given version, the information of each data node on that business data path is determined.

[0139] Subsequently, the business data path graph processing layer generates a business data path graph based on the business data paths corresponding to each version information, and displays the business data path graph on the designated terminal device. The business data path graph processing layer can determine the path coverage corresponding to any version information based on the number of business data paths corresponding to any given version information.

[0140] Next, please see Figure 9 , Figure 9 This is a schematic diagram illustrating the establishment of a business data path diagram according to an embodiment of this application. In this embodiment, establishing a business data path diagram includes three steps: establishing data nodes, establishing data paths, and establishing the business data path diagram.

[0141] The process of establishing data nodes involves several steps. First, business data is extracted from the reporting database. Next, version information is determined, identifying the application version information contained within the business data. Then, data nodes are generated by deduplicating each piece of business data (or each piece of cleaned business data) to obtain multiple data nodes. Finally, the data nodes are stored in the database.

[0142] When establishing data paths, the data nodes are first grouped according to version information to obtain the business data set corresponding to each version. Next, the data node order is determined; for any given version, the order of the data nodes within that business data set is established. Then, the data nodes are connected to obtain the business data path; that is, the data nodes in the business data set corresponding to any given version are connected according to their original order to obtain the business data path for that version. Finally, the business data paths corresponding to each version are stored in the database.

[0143] When creating the business data path diagram, the first step is to filter the business data paths, selecting at least two specified business data paths from those corresponding to each version. Next, data nodes are merged to obtain the business data path diagram; that is, identical data nodes on any two specified business data paths are merged into one, thus combining at least two specified business data paths into a single business data path diagram. Finally, the business data path diagram is stored in the database.

[0144] The above method is based on the application version information contained in each first business data generated during application runtime, and determines the business data path corresponding to each version information. This achieves accurate determination of the business data path corresponding to the actual running application version information, which is beneficial for the analysis and processing of application runtime.

[0145] Figure 10 The diagram shown is a structural schematic of a device for determining a business data path according to an embodiment of this application. Figure 10 As shown, the device includes:

[0146] The acquisition module 1001 is used to acquire multiple first business data, which are data generated during application runtime.

[0147] The partitioning module 1002 is used to partition multiple first business data into business data sets corresponding to each version information based on the application version information contained in each first business data. Each business data set corresponding to a version information includes multiple first business data with the same version information.

[0148] The determination module 1003 is used to determine the business data path corresponding to each version information based on the business data set corresponding to each version information.

[0149] In one possible implementation, the acquisition module 1001 is used to extract multiple second business data from the database. The second business data is data generated by the application during the previous time period. The multiple second business data are cleaned to obtain multiple first business data.

[0150] In one possible implementation, multiple first business data are stored in at least two data tables; a partitioning module 1002 is used to aggregate each first business data in the at least two data tables into a wide table; based on the application version information contained in each first business data in the wide table, the multiple first business data are partitioned into business data sets corresponding to each version information.

[0151] In one possible implementation, the partitioning module 1002 is used to perform deduplication processing on each first business data to obtain multiple data nodes. Each data node includes multiple first business data with the same specified information, which includes application version information. Based on the application version information contained in each data node, the multiple data nodes are divided into business data sets corresponding to each version information. Each business data set corresponding to any version information includes at least two data nodes with the same version information.

[0152] The determination module 1003 is used to connect the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to any version information.

[0153] In one possible implementation, the device further includes:

[0154] The first display module is used to display each data node and the first business data contained in each data node;

[0155] The first adjustment module is used to adjust any data node in response to receiving an adjustment operation on any data node based on the first service data contained in any data node.

[0156] In one possible implementation, the device further includes:

[0157] The second display module is used to display the business data path corresponding to any version information;

[0158] The second adjustment module is used to respond to receiving an adjustment operation on the business data path corresponding to any version information, and to adjust the business data path corresponding to any version information.

[0159] In one possible implementation, the determining module 1003 is further configured to determine the information of each data node on the business data path corresponding to any version information based on the number of first business data contained in each data node on the business data path corresponding to any version information. The information of the data node includes at least one of the conversion rate or churn rate of the data node.

[0160] In one possible implementation, the determining module 1003 is further used to determine the path coverage corresponding to any version information based on the number of business data paths corresponding to any version information.

[0161] In one possible implementation, the device further includes:

[0162] The merging module is used to determine at least two specified business data paths from the business data paths corresponding to each version information, and to merge the at least two specified business data paths to obtain a business data path diagram.

[0163] The third display module is used to display the business data path diagram.

[0164] In one possible implementation, the device further includes:

[0165] The determination module 1003 is also used to determine the specified version information selected by the target object from various version information;

[0166] The filtering and display module is used to filter out target business data paths with version information no lower than the specified version information from the business data paths corresponding to each version information, and then display the target business data paths.

[0167] The aforementioned device determines the business data path corresponding to each version information based on the application version information contained in each first business data generated during application runtime. This enables accurate determination of the business data path corresponding to the actual running application version information, which is beneficial for the analysis and processing of application runtime.

[0168] It should be understood that the above Figure 10 The provided device, in implementing its functions, is only illustrated by the division of the above-described functional modules. In practical applications, the functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the device and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation processes are detailed in the method embodiments, and will not be repeated here.

[0169] Figure 11 A structural block diagram of a terminal device 1100 provided in an exemplary embodiment of this application is shown. The terminal device 1100 may be a portable mobile terminal, such as a smartphone, tablet computer, MP3 (Moving Picture Experts Group Audio Layer III) player, MP4 (Moving Picture Experts Group Audio Layer IV) player, laptop computer, or desktop computer. The terminal device 1100 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, or other names.

[0170] Typically, terminal device 1100 includes a processor 1101 and a memory 1102.

[0171] Processor 1101 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1101 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1101 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1101 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 1101 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0172] The memory 1102 may include one or more computer-readable storage media, which may be non-transitory. The memory 1102 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1102 is used to store at least one instruction, which is executed by the processor 1101 to implement the method for determining the business data path provided in the method embodiments of this application.

[0173] In some embodiments, the terminal device 1100 may also optionally include: a peripheral device interface 1103 and at least one peripheral device. The processor 1101, memory 1102, and peripheral device interface 1103 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1103 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of: a radio frequency circuit 1104, a display screen 1105, a camera assembly 1106, an audio circuit 1107, and a power supply 1109.

[0174] Peripheral device interface 1103 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 1101 and memory 1102. In some embodiments, processor 1101, memory 1102 and peripheral device interface 1103 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1101, memory 1102 and peripheral device interface 1103 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0175] The radio frequency (RF) circuit 1104 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1104 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1104 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1104 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 1104 can communicate with other terminals via at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 1104 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0176] Display screen 1105 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 1105 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1101 for processing. In this case, display screen 1105 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 1105, disposed on the front panel of terminal device 1100; in other embodiments, there may be at least two display screens, disposed on different surfaces of terminal device 1100 or in a folded design; in still other embodiments, display screen 1105 may be a flexible display screen, disposed on a curved or folded surface of terminal device 1100. Furthermore, display screen 1105 may be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen 1105 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0177] The camera assembly 1106 is used to acquire images or videos. Optionally, the camera assembly 1106 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 1106 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cool light flash, which can be used for light compensation at different color temperatures.

[0178] The audio circuit 1107 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting the sound waves into electrical signals that are input to the processor 1101 for processing, or input to the radio frequency circuit 1104 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each located at a different part of the terminal device 1100. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 1101 or the radio frequency circuit 1104 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 1107 may also include a headphone jack.

[0179] Power supply 1109 is used to supply power to the various components in terminal device 1100. Power supply 1109 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 1109 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, and a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0180] In some embodiments, the terminal device 1100 further includes one or more sensors 1110. The one or more sensors 1110 include, but are not limited to: an acceleration sensor 1111, a gyroscope sensor 1112, a pressure sensor 1113, an optical sensor 1115, and a proximity sensor 1116.

[0181] Accelerometer 1111 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by terminal device 1100. For example, accelerometer 1111 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 1101 can control display screen 1105 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 1111. Accelerometer 1111 can also be used for games or for acquiring user motion data.

[0182] The gyroscope sensor 1112 can detect the orientation and rotation angle of the terminal device 1100. The gyroscope sensor 1112 can work in conjunction with the accelerometer sensor 1111 to collect the user's 3D movements on the terminal device 1100. Based on the data collected by the gyroscope sensor 1112, the processor 1101 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0183] The pressure sensor 1113 can be disposed on the side bezel of the terminal device 1100 and / or on the lower layer of the display screen 1105. When the pressure sensor 1113 is disposed on the side bezel of the terminal device 1100, it can detect the user's grip signal on the terminal device 1100, and the processor 1101 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1113. When the pressure sensor 1113 is disposed on the lower layer of the display screen 1105, the processor 1101 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 1105. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0184] An optical sensor 1115 is used to collect ambient light intensity. In one embodiment, the processor 1101 can control the display brightness of the display screen 1105 based on the ambient light intensity collected by the optical sensor 1115. Specifically, when the ambient light intensity is high, the display brightness of the display screen 1105 is increased; when the ambient light intensity is low, the display brightness of the display screen 1105 is decreased. In another embodiment, the processor 1101 can also dynamically adjust the shooting parameters of the camera assembly 1106 based on the ambient light intensity collected by the optical sensor 1115.

[0185] The proximity sensor 1116, also known as a distance sensor, is typically located on the front panel of the terminal device 1100. The proximity sensor 1116 is used to detect the distance between the user and the front of the terminal device 1100. In one embodiment, when the proximity sensor 1116 detects that the distance between the user and the front of the terminal device 1100 is gradually decreasing, the processor 1101 controls the display screen 1105 to switch from a screen-on state to a screen-off state; when the proximity sensor 1116 detects that the distance between the user and the front of the terminal device 1100 is gradually increasing, the processor 1101 controls the display screen 1105 to switch from a screen-off state to a screen-on state.

[0186] Those skilled in the art will understand that Figure 11 The structure shown does not constitute a limitation on the terminal device 1100, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0187] Figure 12This is a schematic diagram of the server structure provided in the embodiments of this application. The server 1200 can vary considerably due to different configurations or performance. It may include one or more processors 1201 and one or more memories 1202. The one or more memories 1202 store at least one piece of program code, which is loaded and executed by the one or more processors 1201 to implement the method for determining the business data path provided in the various method embodiments described above. For example, the processor 1201 is a CPU. Of course, the server 1200 may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server 1200 may also include other components for implementing device functions, which will not be elaborated here.

[0188] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one piece of program code that is loaded and executed by a processor to enable an electronic device to implement any of the above-described methods for determining a business data path.

[0189] Optionally, the aforementioned computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0190] In an exemplary embodiment, a computer program or computer program product is also provided, which stores at least one computer instruction, which is loaded and executed by a processor to enable the computer to implement any of the above-described methods for determining business data paths.

[0191] It should be understood that "multiple" as used in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0192] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0193] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for determining a business data path, characterized in that, The method includes: Obtain multiple first business data, which are data generated during application runtime; Obtain a mapping relationship table, which includes multiple mapping relationships. Each mapping relationship is a mapping relationship between specified information in the first business data and a data node. The specified information includes the version information of the application. The data node is an entity obtained after abstracting the first business data. The entity represents at least one of the following: event name, event identifier, business process node, event level, or version information. By removing duplicate first business data from the mapping table, multiple data nodes are obtained, and each data node includes each first business data with the same specified information. Based on the version information contained in each data node, the multiple data nodes are divided into business data sets corresponding to each version information. Any business data set corresponding to a version information includes all data nodes with the same version information. Connect the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to any version information.

2. The method according to claim 1, characterized in that, The acquisition of multiple first business data includes: Extract multiple second business data from the database, the second business data being data generated by the application during the previous time period; The plurality of second business data are cleaned to obtain the plurality of first business data.

3. The method according to claim 1, characterized in that, The multiple first business data are stored in at least two data tables; The method further includes: Aggregate the first business data from the at least two data tables into a wide table; Based on the application version information contained in each first business data in the wide table, the multiple first business data are divided into business data sets corresponding to each version information.

4. The method according to claim 1, characterized in that, After deduplicating the multiple first business data through the mapping table to obtain multiple data nodes, the process further includes: Display each data node and the first business data contained in each data node; In response to receiving an adjustment operation on any data node based on first service data contained in any data node, the any data node is adjusted.

5. The method according to claim 1, characterized in that, After connecting the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to any version information, the method further includes: Displays the business data path corresponding to any of the aforementioned version information; In response to receiving an adjustment operation on the business data path corresponding to any of the version information, the business data path corresponding to any of the version information is adjusted.

6. The method according to claim 1, characterized in that, After connecting the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to any version information, the method further includes: Based on the number of first business data contained in each data node on the business data path corresponding to any version information, the information of each data node on the business data path corresponding to any version information is determined, and the information of the data node includes at least one of the conversion rate or churn rate of the data node.

7. The method according to any one of claims 1 to 6, characterized in that, After connecting the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to any version information, the method further includes: The path coverage rate corresponding to any version information is determined based on the number of business data paths corresponding to any version information.

8. The method according to any one of claims 1 to 6, characterized in that, The step of connecting the data nodes in the business data set corresponding to any version information to obtain the business data path corresponding to any version information further includes: Determine at least two specified business data paths from the business data paths corresponding to each version information, and merge the at least two specified business data paths to obtain a business data path diagram. Display the business data path diagram.

9. The method according to any one of claims 1 to 6, characterized in that, After determining the business data path corresponding to each version information based on the business data set corresponding to each version information, the process further includes: Determine the specific version information selected by the target object from the various version information; Filter out target business data paths whose version information is not lower than the specified version information from the business data paths corresponding to each version information, and display the target business data paths.

10. A device for determining a business data path, characterized in that, The device includes: The acquisition module is used to acquire multiple first business data, which are data generated during application runtime. The acquisition module is further configured to acquire a mapping relationship table, which includes multiple mapping relationships. Each mapping relationship is a mapping relationship between specified information in the first business data and a data node. The specified information includes the version information of the application. The data node is an entity obtained after abstracting the first business data. The entity represents at least one of the following: event name, event identifier, business process node, event level, or version information. The partitioning module is used to deduplicate the multiple first business data through the mapping relationship table to obtain multiple data nodes, wherein each data node includes each first business data with the same specified information; based on the version information contained in each data node, the multiple data nodes are partitioned into business data sets corresponding to each version information, wherein any business data set corresponding to a version information includes each data node with the same version information. The determination module is used to connect each data node in the business data set corresponding to any version information to obtain the business data path corresponding to any version information.

11. The apparatus according to claim 10, characterized in that, The acquisition module is used to extract multiple second business data from the database. The second business data is data generated by the application during the previous time period. The plurality of second business data are cleaned to obtain the plurality of first business data.

12. The apparatus according to claim 10, characterized in that, The multiple first business data are stored in at least two data tables; The partitioning module is used to aggregate each of the first business data in the at least two data tables into a wide table; Based on the application version information contained in each first business data in the wide table, the multiple first business data are divided into business data sets corresponding to each version information.

13. The apparatus according to claim 10, characterized in that, The device further includes: The first display module is used to display each data node and the first business data contained in each data node; The first adjustment module is configured to adjust the data node in response to receiving an adjustment operation on the data node based on the first service data contained in the data node.

14. The apparatus according to claim 10, characterized in that, The device further includes: The second display module is used to display the business data path corresponding to any of the version information; The second adjustment module is used to adjust the business data path corresponding to any version information in response to receiving an adjustment operation on the business data path corresponding to any version information.

15. The apparatus according to claim 10, characterized in that, The determining module is further configured to determine the information of each data node on the business data path corresponding to the any version information based on the number of first business data contained in each data node on the business data path corresponding to the any version information, wherein the information of the data node includes at least one of the conversion rate or churn rate of the data node.

16. The apparatus according to any one of claims 10 to 15, characterized in that, The determining module is further configured to determine the path coverage rate corresponding to any version information based on the number of business data paths corresponding to any version information.

17. The apparatus according to any one of claims 10 to 15, characterized in that, The device further includes: The merging module is used to determine at least two specified business data paths from the business data paths corresponding to each version information, and to merge the at least two specified business data paths to obtain a business data path diagram. The third display module is used to display the business data path diagram.

18. The apparatus according to any one of claims 10 to 15, characterized in that, The device further includes: The determining module is further configured to determine the specified version information selected by the target object from the various version information; The filtering and display module is used to filter out target business data paths whose version information is not lower than the specified version information from the business data paths corresponding to each version information, and display the target business data paths.

19. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing at least one piece of program code, which is loaded and executed by the processor to enable the electronic device to implement the method for determining the business data path as described in any one of claims 1 to 9.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to enable the computer to implement the method for determining the business data path as described in any one of claims 1 to 9.

21. A computer program product, characterized in that, The computer program product stores at least one computer instruction, which is loaded and executed by a processor to enable the computer to implement the method for determining the business data path as described in any one of claims 1 to 9.

Images