Data recognition method and apparatus

Abstract

This application relates to the field of Internet technology and provides a data identification method and apparatus. The method includes: pre-configuring a data structure, which includes at least one non-expandable data item and at least one expandable data item. Then, after a terminal collects data generated during the operation of an application, it sends the collected data to a server according to the data structure. The server then identifies the data content corresponding to each data item in the received data to be identified based on the data structure. Using this implementation, each tracking point of the terminal application reports data according to the data structure, which not only provides good flexibility but also good applicability and scalability. Furthermore, it enables the server to identify data reported by any tracking point based on the data structure, thereby improving the efficiency of server identification of tracking point data and reducing identification costs.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a data identification method and apparatus. Background Technology

[0002] The analysis of user behavior data plays a crucial role in understanding user needs and optimizing applications. Typically, user behavior data is captured by deploying event tracking points within the application. The server then retrieves, identifies, and analyzes the data captured by these event tracking points.

[0003] Among them, event tracking is usually deployed in a customized manner based on demand scenarios. However, since the application supports many scenarios, the types of data reported by each event tracking point in the application are complex and diverse, resulting in long server time and high cost for identifying event tracking data. Summary of the Invention

[0004] This application provides a data identification method and apparatus to solve the problems of long data identification time and high cost caused by the complexity and diversity of existing data types.

[0005] In a first aspect, embodiments of this application provide a data identification method, the method comprising:

[0006] Receive data to be identified from the terminal, the data to be identified including at least one non-expandable data item and at least one expandable data item;

[0007] Based on the pre-configured data structure, identify the data content corresponding to each data item in the data to be identified.

[0008] Secondly, embodiments of this application provide a data identification method, the method comprising:

[0009] Collect data generated during application execution;

[0010] The collected data is sent to the server according to a pre-configured data structure, so that the server can identify the data content corresponding to at least one non-expandable data item and at least one expandable data item in the collected data according to the pre-configured data structure.

[0011] Thirdly, embodiments of this application also provide a data identification device, the device comprising:

[0012] A receiving module is used to receive data to be identified from a terminal, the data to be identified including at least one non-expandable data item and at least one expandable data item;

[0013] The recognition module is used to identify the data content corresponding to each data item in the data to be recognized based on the pre-configured data structure.

[0014] In a possible implementation, the identification module is further configured to identify, according to the preconfigured data structure, the name of at least one non-extensible data item, the name of at least one extensible data item, and the field type of the data content corresponding to each data item name included in the to-be-identified data.

[0015] In a possible implementation, the identification module is further configured to identify, according to the name of at least one non-extensible data item, the name of at least one extensible data item, and the field type of the data content corresponding to each data item name, the data content corresponding to each data item name in the to-be-identified data.

[0016] In a possible implementation, the extensible data item includes at least one extensible label and a value corresponding to each extensible label, and the at least one extensible label respectively indicates variable data of different attributes.

[0017] In a possible implementation, the non-extensible data item includes at least one of the following:

[0018] an application ID, an event ID, a data type, a start date, a collection type, a point-in-time event creation time, a point-in-time event modification time, and a point-in-time event status.

[0019] In a fourth aspect, an embodiment of the present application further provides a data identification apparatus, and the apparatus includes:

[0020] a collection module configured to collect data generated in a running process of an application program;

[0021] a sending module configured to send the collected data to a server according to a preconfigured data structure, so that the server identifies data content corresponding to at least one non-extensible data item and at least one extensible data item in the collected data according to the preconfigured data structure.

[0022] In a fifth aspect, an embodiment of the present application provides a server, and the server includes a processor and a memory, the memory stores instructions or programs, and the instructions or programs are executed by the processor to perform the data identification method in the first aspect.

[0023] In a sixth aspect, an embodiment of the present application provides a terminal, and the terminal includes a processor and a memory, the memory stores instructions or programs, and the instructions or programs are executed by the processor to perform the data identification method in the second aspect.

[0024] In a seventh aspect, an embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores instructions or programs, and the instructions or programs are executed by the processor to perform the data identification method in the first aspect or the second aspect.

[0025] In an eighth aspect, an embodiment of the present application provides a computer program product, which comprises computer program codes. When the computer program codes are run on a computer, the computer program codes make the computer implement the data recognition method in the first aspect or the second aspect.

[0026] To sum up, the technical scheme of the embodiment of the present application pre-configures a data structure with an extensible data item, so that each buried point of the terminal application program reports data according to the data structure. The flexibility is good, and the applicability and the extensibility are also good. Further, since the data reported by each buried point of the application program adopts a unified data structure, the server can identify the data reported by any buried point based on the data structure, so as to improve the efficiency of identifying the buried point data and reduce the cost of identification. BRIEF DESCRIPTION OF DRAWINGS

[0027] In order to more clearly illustrate the technical scheme in the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly introduced. It should be understood that other drawings can also be obtained by those of ordinary skill in the art without creative labor on the basis of these drawings.

[0028] Figure 1 A system architecture schematic diagram of the data reporting system provided by the embodiment of the present application;

[0029] Figure 2 A flowchart of the data recognition method provided by the embodiment of the present application;

[0030] Figure 3 Another flowchart of the data recognition method provided by the embodiment of the present application;

[0031] Figure 4 An exemplary structure schematic diagram of the pre-configured data structure provided by the embodiment of the present application;

[0032] Figure 5A An exemplary composition schematic diagram of the data recognition device provided by the embodiment of the present application;

[0033] Figure 5B An exemplary composition schematic diagram of the data recognition device provided by the embodiment of the present application;

[0034] Figure 6 A structure schematic diagram of the electronic device provided by the embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical scheme of the embodiments of the present application will be described below in combination with the drawings in the embodiments of the present application.

[0036] The terms used in the following embodiments of the present application are for the purpose of describing specific embodiments and are not intended to be limiting of the technical solutions of the present application. As used in the specification and the appended claims of the present application, the singular forms "a," "an" and "the" are intended to include plural forms as well, unless the context clearly indicates otherwise.

[0037] The related art involved in the embodiments of the present application is described below.

[0038] The collection of user behavior data can be obtained by using the method of buried point reporting. "Buried point" refers to the pre-deployed program code for capturing user behavior data in the application program, and "reporting" refers to the process of transmitting the captured behavior data from the application program to the server.

[0039] Reference is made to Figure 1 , Figure 1 The system architecture of an example data reporting system of the present application is shown, which includes a server 10 and a terminal 20. The terminal 20 reports data to the server 10 through a network 30. The network 30 can be a wired network or a wireless network, and the embodiments of the present application do not limit this.

[0040] It can be understood that Figure 1 This is only a schematic description, and does not constitute a limitation on the data reporting system involved in the embodiments of the present application. In actual implementation, the data reporting system involved in the embodiments of the present application can also include more or less devices. The embodiments of the present application do not limit this.

[0041] The server 10 can be a service device or a cloud platform that provides computing resources for the application program. The server 10 can be used to receive, identify and maintain the running data of the application program reported by the terminal 20, process the logic related to the configuration and parameters of the application program, such as providing the parameters of the computing reporting data for the application program, storing the data reported by the application program, network services, security services, and big data and artificial intelligence platforms, etc. For example, the server 10 can identify the data content of the reported data, maintain the execution logic of the statistical reporting rate, etc. The server 10 can be a standalone physical server, or a server cluster or distributed system composed of multiple physical servers.

[0042] Terminal 20 can be an electronic device such as a mobile phone, tablet computer, game console, wearable device, or PC (Personal Computer). Optionally, terminal 20 supports the execution of applications. Optionally, applications may depend on the operating system of terminal 20 and achieve specific application purposes by running a series of pre-configured computer data and instructions. Applications include mobile apps, such as game apps, instant messaging apps, and browser apps. Optionally, when an application runs on terminal 20, terminal 20 can report the data generated during the application's execution to server 10 via network 30.

[0043] Optionally, data generated during application runtime can also be referred to as logs or events. This data can include application runtime data (e.g., data on the application calling a function, data on the application loading a user's game scene, etc.) and user operation data (e.g., data on a user clicking to play a video, data on displaying the application's interface in response to user actions, etc.). Optionally, each piece of data can include an application identifier (AppID) to identify the business identity and a device identifier (uniqueID) to identify the terminal identity. Clearly, data generated during application runtime reflects user behavior and can be considered user behavior data. Based on this, the application can report this data to server 10 through pre-configured event tracking points, allowing server 10 to analyze this data and optimize the application to meet more user needs.

[0044] Understandable Figure 1 This illustration depicts a data reporting system at the logical function level. In actual implementation, terminal 20 may include at least one terminal device entity, server 12 may also include at least one server device entity, and network 13 may include at least one communication link. There are no restrictions here.

[0045] The technical solutions of the embodiments of this application and the technical effects produced by the technical solutions of this application will be explained below through the description of several exemplary implementation methods.

[0046] Please refer to Figure 2 , Figure 2 This illustration demonstrates a data recognition method. This embodiment uses the application of this data recognition method to a server as an example; the server can be, for instance, as shown below. Figure 1 Server 10 is shown. This data identification method includes the following steps:

[0047] Step S101: Receive data to be identified from the terminal. The data to be identified includes at least one non-expandable data item and at least one expandable data item.

[0048] The to-be-identified data can be captured and reported by any of the embedded points of an application running on the terminal.

[0049] The data structure of the to-be-identified data can be a preconfigured data structure. The preconfigured data structure, for example, as shown in Figure 4 includes a fixed data part and an extensible data part. The fixed data part can be used to deploy at least one non-extensible data item, for example, initialization, login, logout, cancellation, event status (start, success, failure, cancellation), and the like. The extensible data part can be used to deploy at least one extensible data item. The at least one extensible data item includes at least one extensible tag and a value corresponding to each extensible tag, and the at least one extensible tag respectively indicates variable data of different attributes.

[0050] In actual implementation scenarios, the non-extensible data item involved in the embodiments of the present application includes at least one of the following: application ID, event ID, data type, start date, collection type, embedded point event creation time, embedded point event modification time, and embedded point event status. The extensible data item involved in the embodiments of the present application can contain different numbers of extensible tags and corresponding tag values in different implementation scenarios. For example, in a game scenario, four extensible tags are included: the number of levels in which a character is located, the user level, the energy value, and the current coin value, wherein the data content corresponding to the number of levels in which the character is located, the user level, the energy value, and the current coin value is respectively the tag value corresponding to each of the four extensible tags. For another example, in another implementation scenario, five extensible tags are included: user ID, gender, age, acting age, and number of representative works, wherein the data content corresponding to the user ID, gender, age, acting age, and number of representative works is respectively the tag value corresponding to each of the five extensible tags.

[0051] In step S102, the data content corresponding to each data item in the to-be-identified data is identified according to the preconfigured data structure.

[0052] The server can identify the data content corresponding to each data item name in the to-be-identified data according to the name of the at least one non-extensible data item, the name of the at least one extensible data item, and the field type of the data content corresponding to each data item name in the data structure.

[0053] As described above with respect to the preconfigured data structure, the data item in the preconfigured data structure can include a data item name and specific data content of the data item, and the data item name is data describing the specific data content. Based on this, in the embodiments of the present application, the data item name in the preconfigured data structure is referred to as metadata of the data structure.

[0054] Based on this, optionally, after receiving the to-be-identified data, the server can identify the metadata contained in the to-be-identified data, i.e., the name of at least one non-extensible data item, the name of at least one extensible data item, and the field type of the data content corresponding to each data item name, according to the preconfigured data structure, and then identify the data content corresponding to each data item in the to-be-identified data based on the identified metadata.

[0055] It can be seen that, by using the implementation manner, the to-be-identified data reported by the terminal is a preconfigured data structure, i.e., the to-be-identified data includes at least one non-extensible data item and at least one extensible data item. That is, in the embodiment of the application, each buried point of the application program reports data by using a preconfigured data structure, so that the formats of the data reported by each buried point in the application program are the same. Further, the server identifies the data content corresponding to each data item in the to-be-identified data according to the preconfigured data structure, which can improve the efficiency of the server in identifying the buried point data and reduce the cost of identification.

[0056] Figure 2 The illustrative embodiment is a description of the data identification method of the embodiment of the application from the perspective of the operation performed by the server. The data identification method of the embodiment of the application is described from the perspective of the operation performed by the terminal.

[0057] Reference is made to Figure 3 , Figure 3 Another data identification method is illustrated. The embodiment takes the application of the data identification method to a terminal as an example, and the terminal can be the terminal 20 as shown in Figure 1 It should be noted that Figure 3 The illustrative embodiment corresponds to the Figure 2 Therefore, Figure 3 In the illustrative embodiment, the technical features that are the same as or similar to those in the Figure 2 In the illustrative embodiment, the technical features that are the same as or similar to those in the Figure 2 The embodiment is not repeatedly described.

[0058] The data identification method includes the following steps:

[0059] In step S201, data generated during the running of an application program is collected.

[0060] A plurality of buried points can be pre-deployed in the application program, and the plurality of buried points collect running-related data during the running of the application program.

[0061] In step S202, the collected data is sent to a server according to a preconfigured data structure.

[0062] The application program is configured in advance, and the collected data is reported to the server according to the data structure, so that the server identifies the data content corresponding to at least one non-extensible data item and at least one extensible data item in the collected data according to the data structure Figure 2 The implementation of the server and the implementation of the preconfigured data structure are described above, and will not be described here.

[0063] Optionally, the data structure related to the embodiments of the application can be preconfigured, and then presented in the form of an SDK (Software Development Kit), so that the application program is based on the data structure defined by the SDK to report data.

[0064] In summary, the technical scheme of the embodiments of the application preconfigures a data structure with extensible data items, so that each application program of the terminal reports data according to the data structure, which is not only flexible, but also has good applicability and extensibility. Further, since the data reported by each application program is based on a unified data structure, the server can identify the data reported by any application program based on the data structure, thereby improving the efficiency of identifying the application program data and reducing the cost of identification.

[0065] The technical scheme of the embodiments of the application is introduced below by taking a game application program as an example.

[0066] The data structure can be preconfigured, so that each application program of the game reports data according to the data structure. The data structure, for example, as shown in Figure 4 includes a fixed data part and an extensible data part.

[0067] The data items contained in the data structure and the field types of the data content corresponding to each data item are shown in Table 1.

[0068] Table 1

[0069]

[0070] The appID is used to identify the game application program in this example. The eventID is used to identify the event of each application program. The tagKey is used to identify the extensible label of the event. The begDate is used to indicate the start date of the event. The getType is used to indicate the type of the data captured by the event. The createTime is used to indicate the creation time of the event. The updateTime is used to indicate the update time of the event. The status is used to indicate the status of the event, for example, 0 indicates that the event is normal, and 1 indicates that the event is deleted.

[0071] The extensible data item tagKey identifies the content of the eventValue in the buried point data, and the content of the eventValue is different in different scenarios. Based on this, according to the actual implementation scenario, the tagKey can include at least one, and correspondingly, each tagKey corresponds to a tagvalue. For example, a piece of data is: "eventID":"user registration","eventValue":{"gender":"M","name":"Q"}", the tagKey in the data includes tagKey 1 "gender" and tagKey 2 "name", the tagvalue corresponding to tagKey 1 is "M", and the tagvalue corresponding to tagKey 2 is "Q". The data items AppID and eventID come from the game application, colType is defined when the data structure is configured, and begDate, getType, createTime, updateTime and status are all system parameters, that is, in addition to the data item tagKey, the other data items in Table 1 are all non-extensible data items (i.e. fixed data items) in the data structure.

[0072] It can be understood that Table 1 is only a schematic description, and the data items of the embodiments of the present application and the field types of the data items do not constitute a limitation. In actual implementation, depending on different application programs, the data structure can include more or fewer data items, and the number of extensible data items and non-extensible data items therein can also be different from the schematic embodiments shown in Table 1.

[0073] Optionally, the foregoing data structure can be defined by an SDK. Each buried point of the game application captures the running data of the game application, and uses the data structure to report the captured data to the server.

[0074] According to the foregoing description of the meanings of the data items in Table 1, it can be known that the number of the extensible data items tagKey in the data reported by different buried points can be different, and the attributes of the data corresponding to each tagKey can also be different, while the data attributes corresponding to the non-extensible data items are the same. Based on this, the following describes the data reported by the buried point and the identification of each data in combination with examples for the extensible data item tagKey. In the following examples, only the data of the extensible data items is shown, and the data of the non-extensible data items is not shown.

[0075] The data A sent by the buried point A, for example, includes the following extensible data:

[0076]

[0077]

[0078] The eventID in Data A is a non-extensible data item, and eventvalue is an extensible data item. Under the eventvalue corresponding to this eventID, there are items with 4 tagkeys, namely "Level Number", "Player Level", "Player Combat Power", and "Resurrection Times", as well as the corresponding tag values (tagvalue) for each tagkey item.

[0079] Optionally, if Data A is the first data sent by the buried point A received by the server, the server can identify the metadata of this data structure as shown in Table 1 based on the data structure of Data A. And the server can identify the specific data content in Data A based on the metadata shown in Table 1. The specific data content of Data A is shown in Table 2 for example.

[0080] Table 2

[0081] appID eventID tagKey tagvalue XXXX barrier number of levels 100 XXXX barrier player level 100 XXXX barrier player power 100 XXXX barrier number of revives 100

[0082] In Table 2, "XXXX" corresponding to appID indicates the name of the game application. Here, "X" does not represent an English letter but any character, such as the character "Wang". Each row in Table 2 represents a corresponding relationship. For example, the tagvalue "100" in the same row as the tagKey "Level Number" indicates that the level number is 100. The same applies to other rows and will not be elaborated here.

[0083] It can be understood that Table 2 is only a schematic description. In actual implementation, Table 2 also includes other relative data shown in Table 1, which are not shown here.

[0084] It should be noted that the server can first identify the metadata shown in Table 1 based on Data A, and then identify the specific data content shown in Table 2 based on the metadata shown in Table 1. The server can also simultaneously identify the metadata shown in Table 1 and the specific data content shown in Table 2 based on Data A.

[0085] Furthermore, for example, the server receives Data B sent by the buried point A. Data B includes the following extensible data for example:

[0086]

[0087] After that, the server can identify the specific data content in Data B based on the previously identified metadata of the data structure (i.e., Table 1), and for example, obtain the data content shown in Table 3.

[0088] Table 3

[0089] appID eventID tagKey tagvalue XXXX barrier number of levels 100 XXXX barrier player level 100 XXXX barrier player power 100 XXXX barrier number of revives 100 XXXX barrier number of levels 89 XXXX barrier player level 222 XXXX barrier player power 333 XXXX barrier number of revives 4

[0090] Table 3 is a data table after adding the specific data content of data B on the basis of Table 2. When the server receives more data reported by the buried point A, the identified data content can be sequentially added in Table 3, and details are not described herein.

[0091] It can be understood that the above is only a schematic description taking the game application as an example, and in actual implementation, the data identification method of the application is not limited to this application scenario, and in other embodiments, the data identification method of the application is also applied to, for example, an online shopping application, and correspondingly, in other application scenarios, the tagKey can contain more items or fewer items, for example, in the scenario corresponding to the online shopping application, the tagKey includes "browsing times", "adding shopping cart times", and "payment times".

[0092] In summary, the technical solution of the embodiment of the application pre-configures a data structure with extensible data items, so that each buried point of the terminal application reports data according to the data structure, which is not only good in flexibility, but also good in applicability and expansibility. Further, since the data reported by each buried point of the application adopts a unified data structure, the server can identify the data reported by any buried point based on the data structure, thereby improving the efficiency of the server in identifying the buried point data and reducing the cost of identification.

[0093] The above embodiments introduce each embodiment of the data identification method provided by the embodiment of the application from the perspective of the actions performed by each device in data collection and identification of to-be-identified data based on a data structure. It should be understood that, corresponding to the processing steps of data collection and identification of to-be-identified data based on a data structure, the embodiment of the application can realize the above functions in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the application.

[0094] For example, if the above implementation steps realize the corresponding functions through software modules, as shown in Figure 5A The embodiment of the application provides a data identification device, which includes a receiving module 501 and an identification module 502. The data identification device can be used to perform part or all of the operations of the server in the above Figure 2 and Figure 3 .

[0095] For example, the receiving module 501 can be configured to receive the to-be-identified data from the terminal, the to-be-identified data including at least one non-extensible data item and at least one extensible data item. The identifying module 502 can be configured to identify, according to the preconfigured data structure, the data content corresponding to each data item in the to-be-identified data.

[0096] It can be seen that, since the to-be-identified data is the preconfigured data structure, that is, the to-be-identified data includes at least one non-extensible data item and at least one extensible data item. That is, in the embodiment of the present application, each buried point of the application program reports data on the preconfigured data structure, so that the formats of the data reported by each buried point in the application program are the same. Further, the data identifying apparatus identifies, according to the preconfigured data structure, the data content corresponding to each data item in the to-be-identified data, which can improve the efficiency of identifying the buried point data and reduce the cost of identification.

[0097] Optionally, the identifying module 502 is further configured to identify, according to the preconfigured data structure, the name of the at least one non-extensible data item, the name of the at least one extensible data item, and the field type of the data content corresponding to each data item name included in the to-be-identified data.

[0098] Optionally, the identifying module 502 is further configured to identify, according to the name of the at least one non-extensible data item, the name of the at least one extensible data item, and the field type of the data content corresponding to each data item name, the data content corresponding to each data item name in the to-be-identified data.

[0099] Optionally, the extensible data item includes at least one extensible label and a value corresponding to each extensible label, and the at least one extensible label respectively indicates variable data of different attributes.

[0100] Optionally, the non-extensible data item includes at least one of the following:

[0101] application ID, event ID, data type, start date, collection type, buried point event creation time, buried point event modification time, and buried point event status.

[0102] As shown in Figure 5B , the present application further provides a data identifying apparatus, which can be configured to perform part or all of the operations of the terminal in the above Figure 2 and Figure 3 , including a collection module 511 and a sending module 512.

[0103] For example, the collection module 511 can be configured to collect data generated during the running of the application. The sending module 512 can be configured to send the collected data to the server according to the preconfigured data structure, so that the server identifies the data content corresponding to at least one non-extensible data item and at least one extensible data item in the collected data according to the preconfigured data structure.

[0104] It can be understood that the division of the above modules is only a logical functional division. In actual implementation, the functions of the above modules can be integrated into a hardware entity for implementation, for example, the functions of the receiving module 501 and the sending module 502 in the server 1000 can be integrated into a transceiver for implementation. Figure 5A The functions of the collection module 511 and the sending module 512 in the terminal 2000 can be integrated into a processor for implementation. Figure 5B The functions of the collection module 511 and the sending module 512 in the terminal 2000 can be integrated into a processor for implementation.

[0105] As shown in Figure 6 , an electronic device 4000 is shown, which can be used as the server or the terminal. Figure 6 The electronic device 4000 shown in the figure includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 can also include a transceiver 4004. It should be noted that in actual application, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present application. Figure 6 The processor 4001 can be a CPU (Central Processing Unit, central processor), a general-purpose processor, a DSP (Digital Signal Processor, data signal processor), an ASIC (Application Specific Integrated Circuit, application specific integrated circuit), an FPGA (Field Programmable Gate Array, field programmable gate array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in combination with the disclosure content of the present application. The processor 4001 can also be a combination of computing functions, such as one or more microprocessor combinations, combinations of DSP and microprocessor, etc.

[0106]

[0107] ​The bus 4002 can include a path that transmits information between the above components. The bus 4002 can be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 4002 can be divided into an address bus, a data bus, a control bus, and the like. For convenience of representation, Figure 6 Only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0108] The memory 4003 can be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this.

[0109] The memory 4003 is used to store application program codes for implementing the scheme of the present application, and is controlled by the processor 4001 to perform. The processor 4001 is used to execute the application program codes stored in the memory 4003 to realize the content shown in the foregoing method embodiments. In the embodiments of the present application, a computer readable storage medium is also provided, which stores the instructions related to the technical scheme of the present application, and when the computer readable storage medium is run on the computer, the computer executes part or all of the steps of the method described in the foregoing Figure 2 and Figure 3 Embodiments.

[0110] In the embodiments of the present application, a computer program product is also provided, which, when run on the computer, causes the computer to execute part or all of the steps of the method described in the foregoing Figure 2 and Figure 3 Embodiments.

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

[0112] In several embodiments provided in the present application, the disclosed system, device and method can be implemented in other manners. For example, the described device embodiments are merely schematic, and the division of the units is merely a logical function division, and there can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or in other forms.

[0113] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., 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 purposes of the embodiments.

[0114] In addition, each functional unit in the embodiments of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be implemented in the form of hardware, or in the form of software functional units.

[0115] When the integrated unit is implemented in the form of software functional units and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on such an understanding, the technical solutions of the present application essentially or substantially, or all or part of the technical solutions, can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a game console, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and various other media that can store program codes.

[0116] The above merely provides the specific implementation of the present application, and is not used to limit the protection scope of the present application, and any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the present application shall be included in the protection scope of the present application.

Claims

1. A data recognition method characterized by, The method comprises: receiving data to be identified from a terminal, the data to be identified comprising at least one non-extensible data item and at least one extensible data item; identifying, according to a preconfigured data structure, data content corresponding to each data item in the data to be identified; identifying, according to the preconfigured data structure, a name of the at least one non-extensible data item, a name of the at least one extensible data item, and a field type of data content corresponding to each data item name included in the data to be identified; the identifying, according to the preconfigured data structure, data content corresponding to each data item in the data to be identified comprises: identifying, according to the name of the at least one non-extensible data item, the name of the at least one extensible data item, and the field type of data content corresponding to each data item name, data content corresponding to each data item name in the data to be identified.

2. The method of claim 1, wherein: the extensible data item comprises at least one extensible tag and a value corresponding to each extensible tag, and the at least one extensible tag respectively indicates variable data of different attributes.

3. The method of claim 1, wherein, the non-extensible data item comprises at least one of: an application ID, an event ID, a data type, a start date, a collection type, a buried point event creation time, a buried point event modification time, and a buried point event state.

4. A data recognition method characterized by, The method comprises: collecting data generated during application program running; sending the collected data to a server according to a preconfigured data structure, so that the server identifies, according to the preconfigured data structure, data content corresponding to at least one non-extensible data item and at least one extensible data item in the collected data, and identifies, according to the preconfigured data structure, a name of the at least one non-extensible data item, a name of the at least one extensible data item, and a field type of data content corresponding to each data item name included in the data to be identified; the sending the collected data to a server according to a preconfigured data structure, so that the server identifies, according to the preconfigured data structure, data content corresponding to at least one non-extensible data item and at least one extensible data item in the collected data comprises: identifying, according to the name of the at least one non-extensible data item, the name of the at least one extensible data item, and the field type of data content corresponding to each data item name, data content corresponding to each data item name in the data to be identified.

5. A data recognition apparatus characterized by comprising: The apparatus comprises: a receiving module configured to receive data to be identified from a terminal, the data to be identified comprising at least one non-extensible data item and at least one extensible data item; an identifying module configured to identify, according to a preconfigured data structure, data content corresponding to each data item in the data to be identified; the identifying module is further configured to: identify, according to the preconfigured data structure, a name of the at least one non-extensible data item, a name of the at least one extensible data item, and a field type of data content corresponding to each data item name included in the data to be identified; the identifying module is specifically configured to: According to the name of the at least one non-extensible data item, the name of the at least one extensible data item, and the field type of the data content corresponding to each data item name, the data content corresponding to each data item name in the data to be identified is identified.

6. A data recognition apparatus characterized by comprising: The device comprises: The acquisition module is configured to acquire data generated during application running. The sending module is configured to send the acquired data to the server according to a preconfigured data structure, so that the server identifies the data content corresponding to each data item name in the data to be identified according to the name of the at least one non-extensible data item, the name of the at least one extensible data item, and the field type of the data content corresponding to each data item name, and identifies the name of the at least one non-extensible data item, the name of the at least one extensible data item, and the field type of the data content corresponding to each data item name included in the data to be identified according to the preconfigured data structure.

7. A server, characterized by The server comprises a processor and a memory, and the memory stores instructions or programs which are executed by the processor to implement the data identification method according to any one of claims 1 to 3.

8. A terminal, characterized by comprising: The terminal comprises a processor and a memory, and the memory stores instructions or programs which are executed by the processor to implement the data identification method according to claim 4.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the data identification method according to any one of claims 1 to 4.

Images