A method and device for reporting buried point information, a storage medium and a terminal device

Abstract

The application discloses a method and device for reporting buried point information, a storage medium and a terminal device. The method comprises the following steps: a terminal device is preconfigured with a plurality of buried points; the terminal device acquires log data of the terminal device; and the terminal device selects buried point information corresponding to each buried point in the log data, so as to report the buried point information to a server. The server can perform performance analysis on the terminal device based on the received buried point information, thereby improving the efficiency of performance analysis of the terminal device.

Description

Technical Field

[0001] This application relates to the field of streaming media, and in particular to a method, apparatus, storage medium, and terminal device for reporting embedded information. Background Technology

[0002] With the widespread adoption of terminal devices, online video playback has become a core task for these devices. Key performance metrics for terminal devices include stability, speed of playback startup, smoothness of playback, and low probability of buffering. However, current terminal devices only send back a single complete log, which the server uses to analyze device performance and faults, resulting in low analysis efficiency. Summary of the Invention

[0003] The technical problem to be solved by this application is to provide a method, apparatus, storage medium and terminal equipment for reporting embedded information, in order to address the shortcomings of the existing technology.

[0004] To address the aforementioned technical problems, the first aspect of this application provides a method for reporting embedded information, the method comprising:

[0005] Obtain log data from the terminal device;

[0006] Obtain the event tracking log information from the log data and report the determined event tracking log information to the server. The event tracking log information is generated when the event tracking configured on the terminal device is triggered, and the event tracking log information includes the event tracking information corresponding to the event tracking.

[0007] The method for reporting the embedded information includes a terminal device configured with a number of embedded points, each of which corresponds to a different embedded point category.

[0008] The method for reporting the event tracking information includes, wherein the event tracking categories include one or more of the following: decoding problem event tracking, playback performance event tracking, playback anomaly event tracking, network performance event tracking, and resource anomaly event tracking.

[0009] The method for reporting the tracking information, wherein the process of generating the tracking log information specifically includes:

[0010] When at least one of the several tracking data points is triggered, log information corresponding to the trigger time is generated, and this log information is used as the tracking log information corresponding to that tracking point.

[0011] The method for reporting the tracking information, wherein obtaining the tracking log information from the log data specifically includes:

[0012] Read the log identifier of each log entry in the log data;

[0013] Based on the log identifier of each log entry, the corresponding embedded log information of the terminal device is selected from the log data.

[0014] The method for reporting the event tracking information, wherein selecting the event tracking log information corresponding to the terminal device based on the log identifier of each log entry specifically includes:

[0015] The log identifier of each log is matched with the set of event log identifiers corresponding to the terminal device. The set of event log identifiers includes the event log identifiers corresponding to each event point and is stored in XML format.

[0016] Retrieve all logs that match a number of event log identifier sets, and use all the retrieved logs as the event log information corresponding to the terminal device.

[0017] The method for reporting event tracking information, after obtaining the event tracking log information from the log data and reporting the event tracking log information to the server, further includes:

[0018] The system receives a data tracking report from the server, which is generated by the server based on the data tracking log information reported by each terminal device connected to it.

[0019] A second aspect of this application provides a device for reporting embedded data, the device comprising:

[0020] The acquisition module is used to acquire log data from the terminal device;

[0021] The reporting module is used to obtain the event tracking log information in the log data and report the determined event tracking log information to the server. The event tracking log information is generated when the event tracking configured on the terminal device is triggered, and the event tracking log information includes the event tracking information corresponding to the event tracking.

[0022] A third aspect of this application provides a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the steps in the above-described method for reporting embedded information.

[0023] A fourth aspect of this application provides a terminal device, which includes: a processor, a memory, and a communication bus; the memory stores a computer-readable program that can be executed by the processor;

[0024] The communication bus enables communication between the processor and the memory;

[0025] When the processor executes the computer-readable program, it implements the steps in the above-described method for reporting embedded information.

[0026] Beneficial effects: Compared with the prior art, this application provides a method, apparatus, storage medium and terminal device for reporting tracking information. The method includes the terminal device pre-configuring several tracking points, and the terminal device obtaining its own log data and selecting the tracking information corresponding to each tracking point in the log data, so as to report the tracking information to the server. In this way, the server can perform performance analysis on the terminal device based on the received tracking information, thereby improving the efficiency of terminal device performance analysis. Attached Figure Description

[0027] 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.

[0028] Figure 1 A flowchart illustrating the method for reporting tracking information provided in this application.

[0029] Figure 2 A schematic diagram of a terminal device in the method for reporting embedded information provided in this application.

[0030] Figure 3 A schematic diagram of the structure of the device for reporting embedded information provided in this application.

[0031] Figure 4 A schematic diagram of the terminal device provided in this application. Detailed Implementation

[0032] This application provides a method, apparatus, storage medium, and terminal device for reporting embedded data. To make the purpose, technical solution, and effects of this application clearer and more explicit, the following detailed description is provided with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only for explaining this application and are not intended to limit this application.

[0033] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0034] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0035] In specific implementations, the terminal devices described in the embodiments of this application include, but are not limited to, other portable devices such as mobile phones, laptops, or tablets with touch-sensitive surfaces (e.g., touch displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touch displays and / or touchpads).

[0036] The following discussion describes terminal devices that include displays and touch-sensitive surfaces. However, it should be understood that terminal devices may also include one or more other physical user interface devices such as physical keyboards, mice, and / or joysticks.

[0037] The terminal device supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, video conferencing applications, disc burning applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, exercise support applications, photo management applications, digital camera applications, digital camcorder applications, web browsing applications, digital music player applications, and / or digital video playback applications, etc.

[0038] Various applications that can run on a terminal device can use at least one common physical user interface device, such as a touch-sensitive surface. First or more functions of the touch-sensitive surface and the corresponding information displayed on the terminal can be adjusted and / or changed between and / or within applications. In this way, the terminal's common physical framework (e.g., the touch-sensitive surface) can support various applications with user interfaces that are intuitive and transparent to the user.

[0039] It should be understood that the sequence number and size of each step in this embodiment do not imply the order of execution. The execution order of each process is determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application embodiment.

[0040] The application content will be further explained below with reference to the accompanying drawings and the description of the embodiments.

[0041] This implementation provides a method for reporting tracking information, such as... Figure 1 As shown, the method includes:

[0042] S10. Obtain log data from the terminal device.

[0043] Specifically, the terminal device is pre-configured with several tracking points. These tracking points are used to collect information within the terminal device to track its usage. The terminal device can be a smart TV, an audio / video player, or a mobile terminal, etc. Each tracking point has a different function, thus allowing for the configuration of different tracking point categories. The function of each tracking point is reflected by its corresponding category. Therefore, in this embodiment, each tracking point has a different category. For example, if the tracking points include tracking point A and tracking point B, then the tracking point category corresponding to tracking point A is different from that corresponding to tracking point B. For instance, assuming the terminal device is an Android player, the tracking points include decoding performance tracking points, decoding error tracking points, and process error tracking points. These tracking points can be set in files such as ACodec, GenericSource, and MediaHTTP within the NuPlayer framework of the Android player, used to collect tracking point information related to the Android player's decoding performance, decoding errors, and process errors.

[0044] In one implementation of this embodiment, the tracking point categories include one or more of decoding problem tracking points, playback performance tracking points, playback anomaly tracking points, network performance tracking points, and resource anomaly tracking points. Specifically, the decoding problem tracking points are used to determine which audio and video formats require additional support and to clarify the reasons for playback failures. The playback performance tracking points can be used to statistically analyze playback performance and assist in analyzing potential design anomalies in the program (e.g., a CPU utilization rate of 100% indicates the program is stuck in an infinite loop). Playback anomaly tracking points are used to report playback anomalies in the source material, focusing on fixing problems in the demultiplexing / decoding stages of the source material or its format. The network performance tracking points are used to monitor the overall performance of the network module and assist in analyzing playback failures and frequent buffering. The resource anomaly tracking points are used to investigate whether anomalies are caused by the inability to obtain decoder, layer, or audio hardware resources.

[0045] In one implementation of this embodiment, the log data is logs generated during the operation of the terminal device. The log data can be logs within a certain time period, or all logs generated during the operation of the terminal device. In another implementation of this embodiment, the log data is logs within a certain time period, where the end time of this time period can be the acquisition time corresponding to the log data, and the start time of this time period can be the acquisition time corresponding to the previous log data. Therefore, acquiring the terminal device's log data specifically involves: when a control command for triggering the acquisition of the terminal device's log data is received, acquiring the first received data corresponding to the previous control command and the second received time corresponding to the control command; determining the target time period corresponding to the control command based on the first received time and the second received time; and acquiring the log data corresponding to this time period to obtain the log data corresponding to the terminal device. This approach allows for the acquisition of all log data generated during the terminal device's operation while avoiding the acquisition of duplicate log data, thus improving log data acquisition efficiency while ensuring log data integrity.

[0046] Furthermore, the control command used to trigger the acquisition of log data from the terminal device can be sent by an external device or generated by the terminal device itself. When the control command is generated by the terminal device itself, the generation process can involve the terminal device setting a timer, which generates the control command to trigger the acquisition of log data each time the timer expires; or, the terminal device monitoring the triggering status of several tracking points, generating the control command to trigger the acquisition of log data when one of the tracking points is triggered. Of course, in practical applications, this control command can also be generated in other ways, as long as it can form a control command. For example, the terminal device can generate a control command to trigger the acquisition of log data at preset time intervals, or generate the control command to trigger the acquisition of log data when the number of triggered tracking point data reaches a preset number, etc.; these will not be elaborated on here.

[0047] In one implementation of this embodiment, the log data may include event log information generated when the event is triggered. The event log information includes event information corresponding to the event, which reflects the triggering reason for the event. It is understood that each of the several event points corresponds to event information. When one event point is triggered, the event information corresponding to that event point is stored in the log information generated at the trigger time. Based on this, the generation process of the event log information specifically includes:

[0048] When at least one of the several tracking data points is triggered, log information corresponding to the trigger time is generated, and this log information is used as the tracking log information corresponding to that tracking point.

[0049] Specifically, the tracking information is used to trigger the reason for the tracking point. The tracking information corresponds to the tracking point category, and the tracking information corresponding to different tracking point categories is different. For example, the tracking information corresponding to the decoding problem tracking point is different from the tracking information corresponding to the playback performance tracking point. In this embodiment, the correspondence between each tracking point category and the tracking information can be as follows: the tracking information corresponding to the decoding problem tracking point includes unsupported formats and decoding failure reasons; the tracking information corresponding to the playback performance tracking point includes first frame decoding speed, synchronization speed, and CPU and memory anomaly monitoring; the tracking information corresponding to the playback anomaly tracking point includes playback unsmoothness caused by PTS skipping, video pauses caused by Video PTS not updating, and audio-video asynchrony; the tracking information corresponding to the network performance tracking point includes network status and the overall performance of the network module; the tracking information corresponding to the resource anomaly tracking point includes Video Surface resources and Audio device resources. In a specific implementation of this embodiment, the terminal device can pre-encapsulate the trigger interface corresponding to each tracking point, and trigger the tracking point through the trigger interface. The trigger interface can be encapsulated using the singleton pattern.

[0050] In one implementation of this embodiment, in order to store the tracking information in the tracking log information, an extended function logp can be added to the Android log system. The extended function logp is used to save the tracking information in log form and add it to the corresponding log data of the terminal device. In this way, after obtaining the log data of the terminal device, the tracking information can be obtained from the log data.

[0051] For example, extend the logging functionality in Android by adding a `logp` function. The `logp` function is used to retrieve and save event tracking information. The `logp` function can be defined as follows:

[0052] void logp(PROJECT_TYPE type,int count,char*content)

[0053] Among them, PROJECT_TYPE is used to determine the tracking information, content is the tracking information stored in key-value format, and count indicates the number of key-value pairs in content.

[0054] S20. Obtain the event tracking log information from the log data and report the determined event tracking log information to the server.

[0055] Specifically, the event tracking log information is included within the log data, and the log data may include one or more event tracking log entries. It is understood that when retrieving event tracking log information from the log data, one or more event tracking log entries may be obtained, and each event tracking log entry is a log generated when the event tracking is triggered, used to store event tracking information. The server is connected to the terminal device. After obtaining the event tracking log information, the terminal device reports the event tracking log information to the server, so that the server can obtain the event tracking log information reported by each terminal device connected to it.

[0056] In one implementation of this embodiment, since the log data includes several log entries, which include both event tracking log information and non-event event tracking log information, it is necessary to filter the log data after obtaining it to obtain the event tracking log information corresponding to the terminal device. Accordingly, obtaining the event tracking log information from the log data specifically includes:

[0057] Read the log identifier of each log entry in the log data;

[0058] Based on the log identifier of each log entry, the corresponding embedded log information of the terminal device is selected from the log data.

[0059] Specifically, the log identifier reflects the log formation method; different log formation methods correspond to different log identifiers. The log data carries the log identifier corresponding to each log entry, which determines the formation method of that log entry. In this embodiment, the log identifier can be a log storage format; different log formation methods correspond to different log storage formats, and the formation method of the log entry can be determined based on the log storage format. Therefore, after obtaining the log data, the log storage format of each log entry can be read to obtain the log identifier corresponding to each log entry.

[0060] Furthermore, since each log entry has its own corresponding log identifier, once the log identifier of each log entry is obtained, the corresponding event log information for the terminal device can be selected from the log data based on the log identifier of each log entry. The log data can include a single log entry triggered by event tracking, or multiple log entries triggered by event tracking. Of course, if the log data does not include any log entries triggered by event tracking, the event log information corresponding to the terminal device is empty.

[0061] In one implementation of this embodiment, the selection of the embedded log information corresponding to the terminal device based on the log identifier of each log entry specifically includes:

[0062] Match the log identifier of each log with the corresponding set of event log identifiers for the terminal device;

[0063] Retrieve all logs that match a number of event log identifier sets, and use all the retrieved logs as the event log information corresponding to the terminal device.

[0064] Specifically, the event tracking log identifier set includes event tracking log identifiers corresponding to each event tracking point. Each event tracking log information is configured with an event tracking log identifier, which indicates that the log was generated by an event tracking point trigger. This log stores the event tracking information corresponding to the event tracking point. In one implementation of this embodiment, to facilitate differentiation of event tracking log information corresponding to different event tracking point categories, the event tracking identifiers corresponding to each event tracking point category are different. For example, event tracking categories include decoding problem event tracking and playback performance event tracking; the event tracking log identifier corresponding to the decoding problem event tracking is different from the event tracking log identifier corresponding to the playback performance event tracking.

[0065] Based on this, after obtaining the log identifiers of each log, for each log, the log identifier can be matched with the set of event tracking log identifiers. If a matching event tracking log identifier exists in the set, it indicates that the log was triggered by event tracking, and thus it is considered an event tracking log message for the terminal device. Conversely, if no matching event tracking log identifier exists in the set, it indicates that the log was not triggered by event tracking. Therefore, all logs whose log identifiers match the set of event tracking log identifiers can be obtained, and all obtained logs can be used as the event tracking log message for the terminal device.

[0066] In one implementation of this embodiment, the terminal device can be configured with a log parsing service for analyzing log data. This log parsing service can be an Android Service, used to analyze log data to obtain the corresponding event tracking log information for the terminal device. Specifically, the log parsing service can parse the event tracking log information collected via logp in real time, and after collecting the event tracking log information, it converts the event tracking information in the log information to a data format that can be processed by the server (e.g., a cloud server), so that the event tracking log information can be reported to the server. Thus, after receiving the event tracking log information, the server can store and analyze the event tracking information in the log information.

[0067] In one implementation of this embodiment, after obtaining the event tracking log information, the terminal reports the event tracking log information to the server. The event tracking log information can be reported in log format. It is understood that the terminal device can report the event tracking log information to the server in log format so that the server can obtain the event tracking log information. In a specific implementation, after parsing the event tracking log information, the log parsing service can use an integrated cloud server data reporting tool to transmit the processed event tracking information to the cloud server through a local cloud server proxy, thereby enabling the event tracking data to be accessed to the cloud.

[0068] In one implementation of this embodiment, after obtaining the event tracking log information from the log data and reporting the event tracking log information to the server, the method further includes:

[0069] The system receives a data tracking report from the server, which is generated by the server based on the data tracking log information reported by each terminal device connected to it.

[0070] Specifically, the server is connected to several terminal devices, each of which is configured with the method for reporting event tracking information provided in this embodiment. Each terminal device reports its corresponding event tracking information to the server, allowing the server to analyze the performance (e.g., network performance) and existing problems (e.g., decoding issues) of each terminal device based on the received event tracking information. In this embodiment, the device types or models of the terminal devices can be the same, allowing the server to analyze common problems of that type of device based on the event tracking information reported by each terminal device.

[0071] In one implementation of this embodiment, the tracking report may include the trigger count for each tracking point category and the priority for each category. The priority indicates the level at which the performance or problem reflected by the tracking point needs to be addressed. A higher priority indicates a higher priority level for the performance or problem reflected by the tracking point, and vice versa. For example, if the decoding problem tracking point has the highest priority and the tracking information corresponding to the program problem tracking point indicates that it does not support A format files, then the tracking report can determine that the file formats supported by the terminal device need to be adjusted to support A format files. This allows for quick location and resolution of problems with the terminal device.

[0072] In a specific application scenario of this embodiment, such as Figure 2As shown, the terminal device can be configured with a player EEPlayer. The event tracking points are used to collect information from the player EEPlayer, which is configured with event tracking point 1, event tracking point 2, ..., event tracking point n. The terminal device is configured with an EEMonitor module, which is used to receive event tracking trigger information and obtain the event tracking information formed when the event tracking points are triggered. The terminal device's Android log system has an extension with the logp function, which saves the event tracking information in log format. A log parsing service logParserServic is configured in the Android Service to extract and parse the event tracking information saved by the logp function. The terminal device communicates with the server and reports the obtained event tracking information to the server.

[0073] In summary, this embodiment provides a method, apparatus, storage medium, and terminal device for reporting event tracking information. The method includes the terminal device pre-configuring several event tracking points, and the terminal device acquiring its own log data and selecting the event tracking information corresponding to each event tracking point from the log data, so as to report the event tracking information to the server. In this way, the server can perform performance analysis on the terminal device based on the received event tracking information, thereby improving the efficiency of terminal device performance analysis.

[0074] Based on the above-described method for reporting tracking information, this embodiment provides a device for reporting tracking information, such as... Figure 3 As shown, the device includes:

[0075] Module 100 is used to acquire log data from the terminal device;

[0076] The reporting module 200 is used to obtain the event tracking log information in the log data and report the determined event tracking log information to the server. The event tracking log information is generated when the event tracking configured by the terminal device is triggered, and the event tracking log information includes the event tracking information corresponding to the event tracking.

[0077] In one implementation, the terminal device is configured with a number of embedded points, and each of the embedded points corresponds to a different embedded point category.

[0078] In one implementation, the tracking point category includes one or more of the following: decoding problem tracking points, playback performance tracking points, playback anomaly tracking points, network performance tracking points, and resource anomaly tracking points.

[0079] In one implementation, the device for reporting the embedded information further includes:

[0080] The generation module is used to generate log information corresponding to the trigger time when at least one of the several tracking data points is triggered, and to use this log information as the tracking log information corresponding to that tracking point.

[0081] In one implementation, the reporting module includes:

[0082] The reading unit is used to read the log identifier of each log entry in the log data;

[0083] The selection unit is used to select the corresponding embedded log information of the terminal device from the log data based on the log identifier of each log.

[0084] In one implementation, the selection unit includes:

[0085] The matching subunit is used to match the log identifier of each log with the set of event log identifiers corresponding to the terminal device. The set of event log identifiers includes the event log identifiers corresponding to each event point, and the set of event log identifiers is stored in XML format.

[0086] The acquisition sub-unit is used to acquire all logs that match several sets of event log identifiers, and to use all the acquired logs as the event log information corresponding to the terminal device.

[0087] In one implementation, the device for reporting the embedded information further includes:

[0088] The receiving module is used to receive the event tracking report fed back by the server, wherein the event tracking report is generated by the server based on the event tracking log information reported by each terminal device connected to it.

[0089] Based on the above-described method for reporting embedded information, this embodiment provides a computer-readable storage medium that stores one or more programs. These programs can be executed by one or more processors to implement the steps in the method for reporting embedded information as described in the above embodiment.

[0090] Based on the above-mentioned method for reporting embedded information, this application also provides a terminal device, such as... Figure 4As shown, it includes at least one processor 20; a display screen 21; and a memory 22, and may also include a communications interface 23 and a bus 24. The processor 20, display screen 21, memory 22, and communications interface 23 can communicate with each other via the bus 24. The display screen 21 is configured to display a preset user guide interface in the initial setup mode. The communications interface 23 can transmit information. The processor 20 can invoke logical instructions in the memory 22 to execute the methods described in the above embodiments.

[0091] Furthermore, the logical instructions in the aforementioned memory 22 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium.

[0092] The memory 22, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, such as program instructions or modules corresponding to the methods in the embodiments of this disclosure. The processor 20 executes functional applications and data processing by running the software programs, instructions, or modules stored in the memory 22, thereby implementing the methods in the above embodiments.

[0093] The memory 22 may include a program storage area and a data storage area. The program storage area may store the operating system and application programs required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 22 may include high-speed random access memory (RAM) and non-volatile memory. Examples include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, as well as transient storage media.

[0094] Furthermore, the specific process of loading and executing multiple instruction processors in the aforementioned storage medium and terminal device has been described in detail in the above method, and will not be repeated here.

[0095] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for reporting embedded data information, characterized in that, The method includes: Obtain log data from the terminal device; Obtain the event tracking log information from the log data and report the determined event tracking log information to the server. The event tracking log information is generated when the event tracking configured on the terminal device is triggered. The event tracking log information includes the event tracking information corresponding to the event tracking. The process of generating the event log information specifically includes: When at least one of the several data points is triggered, log information corresponding to the trigger time is generated and used as the log information of the data point. The terminal device is an Android player. The log function is extended in Android by adding the logp function. The data tracking information is obtained and stored based on the logp function.

2. The method for reporting embedded information according to claim 1, characterized in that, The terminal device is configured with a number of embedded points, and each of the embedded points corresponds to a different embedded point category.

3. The method for reporting embedded information according to claim 2, characterized in that, The data tracking categories include one or more of the following: decoding problem tracking, playback performance tracking, playback anomaly tracking, network performance tracking, and resource anomaly tracking.

4. The method for reporting embedded information according to claim 1, characterized in that, The specific steps of obtaining the tracking log information from the log data include: Read the log identifier of each log entry in the log data; Based on the log identifier of each log entry, the corresponding embedded log information of the terminal device is selected from the log data.

5. The method for reporting embedded information according to claim 4, characterized in that, Based on the log identifier of each log entry, the specific data entry log information corresponding to the terminal device selected in the log data selection includes: The log identifier of each log is matched with the set of event log identifiers corresponding to the terminal device. The set of event log identifiers includes the event log identifiers corresponding to each event point and is stored in XML format. Retrieve all logs that match a number of event log identifier sets, and use all the retrieved logs as the event log information corresponding to the terminal device.

6. The method for reporting embedded information according to any one of claims 1-5, characterized in that, After obtaining the event tracking log information from the log data and reporting the event tracking log information to the server, the method further includes: The system receives a data tracking report from the server, which is generated by the server based on the data tracking log information reported by each terminal device connected to it.

7. A device for reporting embedded information, used to implement the steps of the method for reporting embedded information as described in any one of claims 1-6, characterized in that, The device includes: The acquisition module is used to acquire log data from the terminal device; The reporting module is used to obtain the event tracking log information in the log data and report the determined event tracking log information to the server. The event tracking log information is generated when the event tracking configured on the terminal device is triggered, and the event tracking log information includes the event tracking information corresponding to the event tracking.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the steps in the method for reporting embedded information as described in any one of claims 1-6.

9. A terminal device, characterized in that, include: Processor, memory, and communication bus; the memory stores a computer-readable program that can be executed by the processor; The communication bus enables communication between the processor and the memory; When the processor executes the computer-readable program, it implements the steps in the method for reporting embedded information as described in any one of claims 1-6.

Images