Play exception repair method and device, electronic equipment and storage medium

Abstract

The application relates to the audio and video technical field, in particular to a playing exception repairing method and device, electronic equipment and storage medium. In the playing exception repairing method, system data is acquired when an exception occurs in a media playing process; then, an exception root cause of the exception is determined based on the system data; finally, playing exception repairing is performed on the currently played media content based on the exception root cause. Thus, automatic repairing of the playing exception can be realized, the influence of the exception such as lagging, black screen and the like on the user experience is reduced, and the stability of the media playing is improved.

Description

Technical Field

[0001] This application relates to the field of audio and video technology, specifically to a method, apparatus, electronic device, and storage medium for repairing playback anomalies. Background Technology

[0002] With the widespread adoption of 5G networks, users have higher demands for the smoothness and stability of media playback on electronic devices. However, in actual use, playback anomalies such as stuttering and black screens occur frequently. Current technologies struggle to address these issues, mostly relying on log reporting, simple retries, or error code prompts to report problems. Furthermore, the lack of targeted recovery mechanisms allows small problems to accumulate, eventually leading to frequent device crashes and even the inability to play subsequent content. Summary of the Invention

[0003] This application provides a method, apparatus, electronic device, and storage medium for repairing playback anomalies, which can resolve abnormal situations during media playback and improve the stability of playback functions.

[0004] In a first aspect, embodiments of this application provide a playback anomaly repair method, the playback anomaly repair method comprising: acquiring system data when an anomaly occurs during media playback; determining the root cause of the anomaly based on the system data; and repairing the playback anomaly of the currently playing media content based on the root cause.

[0005] In some embodiments, before the step of obtaining system data when an abnormal situation occurs during media playback, the playback abnormality repair method further includes: detecting whether there is a stuttering abnormality during media playback; detecting whether there is a black screen abnormality during media playback; and if the stuttering abnormality and / or the black screen abnormality exist, determining that an abnormal situation exists during media playback.

[0006] In some embodiments, detecting whether there is a stuttering abnormality during media playback includes: monitoring data input capability, decoding output capability, and rendering capability; and determining that the stuttering abnormality exists when any one of the data input capability, the decoding output capability, and the rendering capability is abnormal.

[0007] In some embodiments, detecting whether a black screen error exists during media playback includes: determining that the black screen error exists upon receiving a black screen error notification; and / or,

[0008] Monitor the playback status and screen status; if the playback status is normal and the screen status is no screen output, determine that the black screen anomaly exists.

[0009] In some embodiments, the system data includes current resource data, and determining the root cause of the abnormal situation based on the system data includes: when the current resource data reaches a lag threshold, determining that the root cause of the abnormal situation includes a resource root cause; The method of repairing playback anomalies of currently playing media content based on the root cause of the anomaly includes: determining the target resource data required to resolve the anomaly based on historical resource data; and allocating resources to the currently playing media content based on the target resource data and the current resource data.

[0010] In some embodiments, the system data includes network status information, and determining the root cause of the abnormal situation based on the system data includes: when the network status information includes information about network unavailability or poor network status, determining that the root cause of the abnormal situation includes a network root cause; The method of repairing playback anomalies of the currently playing media content based on the root cause of the anomaly includes: activating a network repair mechanism and / or a domain name repair mechanism to repair the network status when the media content is playing.

[0011] In some embodiments, the system data includes audio and video bitstreams during bitstream parsing, and determining the root cause of the abnormal situation based on the system data includes: comparing the parameters in the audio and video bitstreams with preset encoding parameters; when the parameters in the audio and video bitstreams are inconsistent with the preset encoding parameters, determining that the root cause of the abnormal situation includes a bitstream root cause; The playback anomaly repair based on the root cause of the anomaly includes: determining missing parameters in the audio and video bitstream based on the parameters in the audio and video bitstream and the preset encoding parameters; and supplementing the missing parameters in the audio and video bitstream.

[0012] Secondly, embodiments of this application provide a playback anomaly repair device, which includes: a data acquisition module for acquiring system data when an anomaly occurs during media playback; a root cause determination module for determining the root cause of the anomaly based on the system data; and an anomaly repair module for repairing the playback anomaly of the currently playing media content based on the root cause.

[0013] Thirdly, embodiments of this application also provide an electronic device, the electronic device including: one or more processors, a memory, and one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the playback anomaly repair method as described above.

[0014] Fourthly, embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon, the computer program being loaded by a processor to perform the steps in the playback anomaly repair method described above.

[0015] This application provides a method, apparatus, electronic device, and storage medium for repairing playback anomalies. By acquiring system data when anomalies occur during media playback and determining the root cause based on this data, targeted playback anomaly repair is performed. This solves the problem of the lack of automatic diagnosis and accurate recovery mechanisms for media playback anomalies in existing technologies. Therefore, automatic repair of playback anomalies can be achieved, reducing the impact of anomalies such as stuttering and black screens on user experience, and improving the stability of media playback. Attached Figure Description

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

[0017] Figure 1 This is a schematic flowchart of a playback anomaly repair method provided in an embodiment of the present invention; Figure 2 This is a flowchart illustrating the detection of abnormal situations in a playback anomaly repair method provided in an embodiment of the present invention; Figure 3 This is a flowchart illustrating the specific method of step S5 provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the playback anomaly repair device provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0018] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0019] In the description of this application, the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first," "second," "third," etc., may explicitly or implicitly include one or more features.

[0020] In this application, the term "exemplary" is used to mean "used as an example, illustration, or description." Any embodiment described as "exemplary" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use this application. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be made without using these specific details. In other instances, well-known structures and processes are not described in detail to avoid obscuring the description of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0021] It should be noted that since the method in this application embodiment is executed in a computer device, the processing objects of each computer device exist in the form of data or information, such as time, which is essentially time information. It is understood that if size, quantity, position, etc. are mentioned in subsequent embodiments, they are all corresponding data that exist so that the computer device can process them. Specific details will not be elaborated here.

[0022] Traditional media playback technologies often experience playback errors due to various reasons such as file or stream corruption, network issues, system resource contention, hardware limitations, or system incompatibility. These errors can manifest as stuttering or black screens. Existing solutions can only alert users through log reporting, simple retries, and error code displays, lacking effective automatic diagnostic and recovery mechanisms. They cannot implement precise recovery strategies based on the type of error, leading to a poor user experience and even frequent crashes or inability to play subsequent content.

[0023] Therefore, this application provides a method for repairing playback anomalies. This method is typically executed in a media playback system or electronic device, such as a smart TV, set-top box, streaming media player, or mobile device. Figure 1 As shown, the playback error repair method includes the following steps S1 to S3: Step S1: Obtain system data when abnormal situations occur during media playback.

[0024] Abnormal situations refer to deviations from normal expectations during media content playback, such as video stuttering or black screens.

[0025] System data refers to a collection of information collected from electronic devices during media playback, reflecting resource usage status, network conditions, and media content characteristics. For example, system data may include CPU (Central Processing Unit) utilization, GPU (Graphics Processing Unit) utilization, memory usage, network status information, and audio / video bitrate. This system data is used to analyze and diagnose the causes of playback anomalies.

[0026] Specifically, system data can be obtained in several ways. For example, system data (including CPU, memory, network bandwidth, and other resource usage) can be obtained by periodically polling the system status interface. Alternatively, log points can be set in key playback modules (such as decoders and renderers), and when an anomaly is detected, relevant system data can be written to a log file for later retrieval. Furthermore, user-triggered feedback can be submitted via the user interface when a playback anomaly is detected, and the system will then collect the current system data.

[0027] Step S2: Determine the root cause of the abnormal situation based on system data.

[0028] The root cause of an anomaly is the reason why media playback malfunctions. For example, root causes may include insufficient resources, network connection problems, corrupted media files, decoder failures, system compatibility issues, etc.

[0029] Specifically, an anomaly pattern library can be used to match the root cause of anomalies based on system data. For example, the system can maintain an anomaly pattern library, which contains mappings between various anomalies and corresponding system data characteristics. When system data is acquired, it is compared with entries in the anomaly pattern library. If a match is found, the corresponding root cause of the anomaly is determined. For example, if system data shows a network connection interruption, it can be preliminarily determined that the root cause of the anomaly is a network problem.

[0030] Step S3: Repair the playback anomaly of the currently playing media content based on the root cause of the anomaly.

[0031] Playback anomaly repair refers to taking corresponding technical measures to resolve playback anomalies based on identified root causes, thereby restoring normal playback of media content. Repair measures may include, but are not limited to, system resource allocation, network connection optimization, bitrate switching, decoder restart, and driver updates.

[0032] Specifically, a series of repair strategies can be predefined for different root causes of anomalies. For example, if the root cause is determined to be insufficient system resources, some non-core background applications can be closed to free up resources, or the video quality or bitrate of media playback can be reduced. If the root cause is determined to be a corrupted media file, the media file can be reloaded, or the user can be prompted to try a different media source. After these repair strategies are executed, the aim is to restore the media content to normal playback.

[0033] The playback anomaly repair method provided in this embodiment acquires system data when anomalies occur during media playback, determines the root cause of the anomaly based on the system data, and then performs targeted playback anomaly repair. This solves the problem of the lack of automatic diagnosis and accurate recovery mechanisms for media playback anomalies in existing technologies. Therefore, this method can achieve automatic repair of playback anomalies, reduce the impact of anomalies such as stuttering and black screens on user experience, and improve the stability of media playback.

[0034] In some embodiments, such as Figure 2 As shown, before executing step S1 and obtaining system data when an abnormal situation occurs during media playback, the playback abnormality repair method further includes the following steps S5 to S7: Step S5: Check for any stuttering or abnormalities during media playback.

[0035] Among them, stuttering refers to anomalies that users can perceive, such as video frame freezes, audio interruptions, non-linear jumps in the playback progress bar, or decoding frame rates that are significantly lower than the target frame rate (e.g., below 15fps for more than 300ms).

[0036] In some embodiments, such as Figure 3 As shown, step S5 above, detecting whether there is any stuttering or abnormality during media playback, includes the following steps S51 and S52: Step S51: Monitor the data input capability, decoding output capability, and rendering capability.

[0037] Among them, data input capability refers to the ability of the media playback link to obtain the original audio and video bitstream from the network or local storage, and to complete protocol parsing, encapsulation format demultiplexing (Demux), and to continuously supply valid data frames to the decoder.

[0038] In some embodiments, the data input capability can be monitored by: real-time counting of the number of bytes input to the demultiplexing module (Demux) per unit time; if the number of bytes input to the demultiplexing module per unit time is lower than a preset byte threshold, the data input capability is determined to be abnormal; otherwise, the data input capability is determined to be normal. The unit time and the preset byte threshold can be set according to the video resolution, encoding method, and actual needs; for example, the unit time can be set to 1 second, and the preset byte threshold can be set to 600,000 bytes.

[0039] Decoding output capability refers to the decoder's ability to decode audio and video frames and output the original data frames after receiving valid data frames. Decoders can include audio decoders and video decoders.

[0040] In some embodiments, the decoding output capability can be monitored by: monitoring the decoding time of a single frame; if the decoding time of a single frame exceeds a preset decoding time threshold (e.g., 120ms), it is determined that the decoding output capability is abnormal; otherwise, it is determined that the decoding output capability is normal.

[0041] In some embodiments, the decoding output capability can be monitored by: monitoring the number of decoding failure callbacks of the decoder; if the number of decoding failure callbacks per unit time (e.g., within 3 seconds) is greater than or equal to a preset callback threshold (e.g., 3 times), it is determined that the decoding output capability is abnormal; otherwise, it is determined that the decoding output capability is normal.

[0042] Rendering capability refers to the ability of the raw data frames output by the decoder to be processed by graphics compositing services (such as SurfaceFlinger and HwComposer on the Android platform) and finally displayed on the screen.

[0043] In some embodiments, the rendering capability can be monitored by: monitoring the callback information after rendering; calculating the missing rate of the callback information; when the missing rate of the callback information is greater than or equal to a preset missing rate threshold (e.g., 5%), it is determined that the rendering capability is abnormal; otherwise, it is determined that the rendering capability is normal.

[0044] Step S52: If any of the data input capability, decoding output capability, or rendering capability is abnormal, it is determined that there is a stuttering abnormality.

[0045] Specifically, a stuttering issue is identified when any of the data input capability, decoding output capability, or rendering capability is abnormal. This embodiment monitors the data input capability, decoding output capability, and rendering capability during media playback, reducing missed detections caused by inaccurate judgment of a single indicator.

[0046] Step S6: Check if there is a black screen abnormality during media playback.

[0047] A black screen error occurs when the player has entered playback mode, but there is no valid image output on the screen. This black screen error differs from the initial black screen before normal startup, and also from the black screen that occurs when the user manually pauses the playback.

[0048] In some embodiments, step S6, detecting whether a black screen abnormality exists during media playback, includes: upon receiving a black screen abnormality prompt, determining that a black screen abnormality exists; and / or, monitoring the playback status and screen status; if the playback status is normal and the screen status is no screen output, determining that a black screen abnormality exists.

[0049] Among them, black screen error messages refer to error signals or status events with clear semantic identification that are actively reported by the underlying media subsystem. Black screen error messages include, but are not limited to: explicit black screen error messages, warning events, or log prompts actively issued by the media playback system or its related components (e.g., decoders, renderers, operating systems) during operation.

[0050] Specifically, detecting a black screen error during media playback can be done by confirming its existence upon receiving a black screen error message. When the media playback system or its related components (e.g., decoder, renderer, operating system) actively issue explicit black screen error messages, warning events, or log messages during operation, a black screen error is immediately confirmed. For example, a black screen error message is triggered when the video rendering path is interrupted, thus confirming the existence of a black screen error; similarly, a decoder error message is triggered when the decoder malfunctions, thus confirming the existence of a black screen error.

[0051] Playback status refers to the operating state of the media player. For example, playback status can include, but is not limited to, normal (playing), paused, buffering, and stopped states. Playback status can be obtained by querying the application programming interface (API) provided by the media player.

[0052] The screen status refers to the actual screen output on the display device. Screen status can include, but is not limited to, a screen output state and a screen no output state. Screen status can be monitored in various ways. For example, the frame rate output by the rendering module can be monitored; if the frame rate is zero or significantly lower than expected for an extended period, it may indicate no screen output. Alternatively, pixel sampling can be performed on the rendering buffer or screen area to detect whether the pixel values ​​in a specific area remain completely black or nearly completely black for an extended period, etc.

[0053] Specifically, another way to detect black screen anomalies during media playback is to monitor the playback status and the screen display status. If the playback status is normal and the screen display status is "no video output," then a black screen anomaly is confirmed. Specifically, a normal playback status indicates that the player is playing media content normally; simultaneously, a "no video output" status indicates that no video frames are being rendered or displayed; therefore, a black screen anomaly can be confirmed.

[0054] This embodiment, on the one hand, can respond to explicit errors directly reported by the system or components by receiving black screen anomaly prompts; on the other hand, by actively monitoring the playback status and screen status and combining this with judgment, it can identify those abnormal situations where a black screen has actually occurred without explicit error prompts. This strategy of combining passive prompts and active monitoring improves the accuracy and robustness of black screen anomaly detection.

[0055] Step S7: If there is a stuttering or black screen, it indicates that there is an abnormal situation during media playback.

[0056] Specifically, once a lag, black screen, or both are detected, an abnormal situation is confirmed.

[0057] This embodiment identifies two types of playback issues—stuttering and black screen—by explicitly detecting them, thus recognizing abnormal situations during media playback. This detection method improves the response speed and effectiveness of playback anomaly repair methods, reduces the time users experience unpleasant experiences during media playback, and enhances overall playback stability.

[0058] In some embodiments, system data includes current resource data. Step S2, determining the root cause of the abnormal situation based on system data, includes: when the current resource data reaches the stuttering threshold, determining that the root cause includes a resource root cause. Step S3, repairing playback anomalies of the currently playing media content based on the root cause, includes: determining the target resource data needed to resolve the anomaly based on historical resource data; and allocating resources to the currently playing media content based on the target resource data and the current resource data.

[0059] Current resource data refers to the data on various system resources currently occupied or available by the media playback system, such as CPU utilization, memory utilization, and GPU utilization. Current resource data reflects the real-time status of system resources and is the basis for assessing whether system resources are sufficient and determining whether playback abnormalities are caused by resource issues.

[0060] A stuttering threshold is a critical value used to determine whether current resource data has reached a level that causes playback stuttering. For example, the stuttering threshold for CPU utilization is 90%, for memory utilization it is 70%, and for GPU utilization it is 80%, and so on. This stuttering threshold can be preset based on device performance, media content type, user experience standards, etc., or it can be dynamically adjusted based on historical playback data using a machine learning model.

[0061] Resource root cause refers to abnormal media playback caused by abnormal resource conditions.

[0062] Historical resource data records resource usage, playback performance data, and corresponding repair effect data over a period of time (e.g., within a week).

[0063] Target resource data refers to the ideal resource configuration data required to resolve current playback anomalies and ensure smooth playback. Target resource data is not a fixed value, but rather dynamically calculated based on the current anomaly, media content characteristics, device capabilities, and historical data analysis. For example, if current CPU resources are insufficient, target resource data may indicate how much additional CPU resources need to be allocated.

[0064] Resource allocation refers to the reconfiguration and scheduling of system resources required for the currently playing media content based on target resource data. This may include, but is not limited to: adjusting CPU / GPU frequencies, releasing memory for non-critical processes, dynamically adjusting network bandwidth priority, switching to low-bitrate media streams, and adjusting the number of decoder threads. The purpose of resource allocation is to prioritize the smoothness of media playback within limited system resources.

[0065] In some embodiments, system data includes network status information. Step S2, determining the root cause of the abnormal situation based on system data, includes: when the network status information includes information about network unavailability or poor network status, determining that the root cause includes a network root cause. Step S3, repairing playback anomalies of the currently playing media content based on the root cause, includes: activating a network repair mechanism and / or a domain name repair mechanism to repair the network status during media content playback.

[0066] Network status information refers to data describing the current network connectivity of a device, which may include, but is not limited to, information such as network unavailable, poor network status, and good network status. Network unavailable typically means the device is completely disconnected from the network and cannot access the internet. Poor and good network status are related to data such as signal strength, network latency, and packet loss rate, which can be determined by continuously monitoring network performance indicators and comparing them with preset thresholds.

[0067] Network status information can be obtained through the operating system's application programming interface or network library. For example, you can periodically query the network connection status or receive system broadcasts or notifications when the network status changes.

[0068] Network root causes refer to abnormal media playback caused by network anomalies.

[0069] Specifically, network repair mechanisms can include various strategies, such as trying to switch network connections (from Wi-Fi to cellular data, or vice versa), or trying to reconnect to the current network. At the application level, it can also try refreshing the network connection, or adjust the media player's caching strategy to adapt to the current network conditions, such as increasing the preload cache size to cope with short-term network fluctuations.

[0070] Specifically, the domain name repair mechanism primarily targets network issues that may be related to Domain Name System (DNS) resolution. This can include attempting to refresh the DNS cache or switching to an alternative DNS server. In some cases, it can also attempt to connect directly using the media server's IP address, bypassing the DNS resolution process, to verify whether the problem is indeed a domain name resolution issue.

[0071] This embodiment can identify playback anomalies caused by network unavailability or poor network conditions, thus clearly attributing the root cause to a network problem. Based on this, targeted network repair mechanisms and / or domain name repair mechanisms are activated, directly addressing the network connection layer to resolve media playback stuttering, interruptions, or black screens caused by network issues. This targeted repair strategy improves the efficiency and success rate of anomaly repair, enhances the user's media viewing experience in poor network conditions, and improves the smoothness of media content playback.

[0072] In some embodiments, system data includes audio and video bitstreams during bitstream parsing. Step S2, determining the root cause of the anomaly based on system data, includes: comparing parameters in the audio and video bitstreams with preset encoding parameters; when the parameters in the audio and video bitstreams are inconsistent with the preset encoding parameters, determining the root cause includes a bitstream root cause. Step S3, repairing playback anomalies of the currently playing media content based on the root cause, includes: determining missing bitstream parameters based on parameters in the audio and video bitstreams and preset encoding parameters; and supplementing the missing bitstream parameters in the audio and video bitstreams.

[0073] Audio and video streams refer to encoded and compressed digital audio and video data streams, forming the foundation for media content playback. When a media player parses the stream, it extracts the audio and video streams from the received data and decodes them. The audio and video streams contain a series of parameters (encoding parameters), such as SPS (Sequence Parameter Set) information, PPS (Picture Parameter Set) information, resolution, frame rate, bitrate, encoding format, GOP structure, sampling rate, and number of channels. These parameters determine the playback characteristics and decoding method of the media content.

[0074] Preset encoding parameters are typically the standards or expected parameters that media content follows during encoding, or the parameters required by a player to play a certain type of media correctly. Preset encoding parameters include a series of parameters such as SPS information, PPS information, resolution, frame rate, bitrate, encoding format, GOP structure, sampling rate, and number of channels.

[0075] Specifically, comparing the parameters in the audio / video stream with the preset encoding parameters involves comparing each parameter one by one. By comparing the actually parsed audio / video stream parameters with these preset parameters, it's possible to detect whether the audio / video stream meets expectations. For example, if the audio / video stream lacks SPS or PPS information, or if parameters such as resolution and frame rate do not match the preset encoding parameters, it indicates a stream anomaly. When inconsistencies are detected between the parameters in the audio / video stream and the preset encoding parameters, the root cause of the anomaly, including the stream itself, can be determined. This comparison can be performed during the initialization of the stream parser or decoder, or periodically during playback.

[0076] The missing bitstream parameter refers to the missing or erroneous information in the audio / video bitstream identified based on the differences between the parameters in the audio / video bitstream and the preset encoding parameters. For example, if the preset encoding parameters require a video stream to contain SPS and PPS information, but these are missing in the actual audio / video bitstream, then the missing bitstream parameter includes SPS and PPS information.

[0077] Specifically, padding missing parameters in audio and video streams refers to re-injecting these missing parameters into the audio and video streams. This can be achieved in various ways, such as retrieving the missing parameters from the cache, local storage, or network and inserting them into the appropriate positions in the audio and video streams. For some non-critical but missing parameters, industry standards or player default values ​​can be used to fill them in, ensuring the continuity of the decoding process. In some cases, it may be necessary to partially reassemble the audio and video streams to ensure that the padded parameters can be correctly recognized and used by the decoder.

[0078] This embodiment detects and repairs anomalies directly targeting the integrity and correctness of the media content itself. When inconsistencies are detected between parameters in the audio / video bitstream and preset encoding parameters, the root cause of the playback anomaly can be determined to be the bitstream itself. Based on this, specific missing bitstream parameters are further identified through comparison and added to the audio / video bitstream, thereby repairing playback anomalies caused by incomplete or erroneous bitstreams. This targeted repair mechanism improves the accuracy and efficiency of anomaly repair and enhances the smoothness of media content playback.

[0079] In summary, the playback anomaly repair method provided in this embodiment acquires system data when anomalies occur during media playback, determines the root cause of the anomaly based on this data, and then performs targeted playback anomaly repair. This solves the problem of the lack of automatic diagnosis and accurate recovery mechanisms for media playback anomalies in existing technologies. Therefore, this method can achieve automatic repair of playback anomalies, reduce the impact of anomalies such as stuttering and black screens on user experience, and improve the stability of media playback.

[0080] like Figure 4 As shown, in order to better implement the playback error repair method of this application embodiment, based on the playback error repair method, this application embodiment also provides a playback error repair device 400, which includes: The data acquisition module 401 is used to acquire system data when abnormal situations occur during media playback; The root cause determination module 402 is used to determine the root cause of the abnormal situation based on system data; The anomaly repair module 403 is used to repair playback anomalies of the currently playing media content based on the root cause of the anomaly.

[0081] In some embodiments, prior to the step of acquiring system data when an anomaly occurs during media playback, the playback anomaly repair device 400 further includes: The stuttering detection module is used to detect whether there are any stuttering or abnormalities during media playback; The black screen detection module is used to detect whether there is a black screen abnormality during media playback; The anomaly detection module is used to determine if there are any abnormalities during media playback, such as stuttering or black screen.

[0082] In some embodiments, the stuttering detection module is also used to: monitor data input capability, decoding output capability, and rendering capability; and determine that a stuttering abnormality exists when any of the data input capability, decoding output capability, and rendering capability is abnormal.

[0083] In some embodiments, the black screen detection module is further configured to: determine that a black screen abnormality exists upon receiving a black screen abnormality prompt; and / or, Monitor playback status and screen status; if the playback status is normal but the screen status shows no output, a black screen anomaly is confirmed.

[0084] In some embodiments, system data includes current resource data, and the root cause determination module 402 is further configured to: determine that when the current resource data reaches the lag threshold, the abnormal root cause includes the resource root cause; The anomaly repair module 403 is also used to: determine the target resource data required to resolve the anomaly based on historical resource data; and allocate resources to the currently playing media content based on the target resource data and the current resource data.

[0085] In some embodiments, the system data includes network status information, and the root cause determination module 402 is further configured to: determine that the abnormal root cause includes a network root cause when the network status information includes information about network unavailability or poor network status. The anomaly repair module 403 is also used to: initiate a network repair mechanism and / or a domain name repair mechanism to repair the network status when media content is played.

[0086] In some embodiments, the system data includes audio and video bitstreams during bitstream parsing, and the root cause determination module 402 is further configured to: compare the parameters in the audio and video bitstreams with preset encoding parameters; when the parameters in the audio and video bitstreams are inconsistent with the preset encoding parameters, determine the abnormal root cause, including the bitstream root cause; The anomaly repair module 403 is also used to: determine the missing parameters of the bitstream based on the parameters in the audio and video bitstream and the preset encoding parameters; and fill in the missing parameters in the audio and video bitstream.

[0087] This application provides an electronic device, which includes one or more processors, a memory, and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the playback anomaly repair method in any of the above embodiments.

[0088] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention.

[0089] This application also provides a computer device that integrates any of the playback error repair devices provided in this application. For example... Figure 5 As shown, it illustrates a structural schematic diagram of the computer device involved in the embodiments of this application, specifically: The computer device may include components such as a processor 801 with one or more processing cores, a memory 802 with one or more computer-readable storage media, a power supply 803, and an input unit 804. Those skilled in the art will understand that... Figure 5 The computer device structure shown does not constitute a limitation on the computer device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein: The processor 801 is the control center of the computer device. It connects various parts of the computer device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 802, and by calling data stored in the memory 802, it performs various functions of the computer device and processes data, thereby providing overall monitoring of the computer device. Optionally, the processor 801 may include one or more processing cores; preferably, the processor 801 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 801.

[0090] The memory 802 can be used to store software programs and modules. The processor 801 executes various functional applications and data processing by running the software programs and modules stored in the memory 802. The memory 802 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 802 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 802 may also include a memory controller to provide the processor 801 with access to the memory 802.

[0091] The computer device also includes a power supply 803 that supplies power to the various components. Preferably, the power supply 803 can be logically connected to the processor 801 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 803 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0092] The computer device may also include an input unit 804, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0093] Although not shown, the computer device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 801 in the computer device loads the executable files corresponding to the processes of one or more application programs into the memory 802 according to the following instructions, and the processor 801 runs the application programs stored in the memory 802 to realize various functions, as follows: Acquire system data when abnormal situations occur during media playback; The root cause of the anomaly was determined based on system data; Repair playback issues of the currently playing media content based on the root cause of the anomaly.

[0094] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0095] Therefore, embodiments of this application provide a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a disk, or an optical disk, etc. A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in any of the playback anomaly repair methods provided in embodiments of this application. For example, the computer program loaded by the processor can execute the following steps: Acquire system data when abnormal situations occur during media playback; The root cause of the anomaly was determined based on system data; Repair playback issues of the currently playing media content based on the root cause of the anomaly.

[0096] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the detailed descriptions of other embodiments above, which will not be repeated here.

[0097] In practice, each of the above units or structures can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units or structures, please refer to the previous method embodiments, which will not be repeated here.

[0098] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0099] The above provides a detailed description of a playback anomaly repair method, apparatus, electronic device, and storage medium provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for repairing playback anomalies, characterized in that, The playback error repair method includes: Acquire system data when abnormal situations occur during media playback; The root cause of the abnormal situation is determined based on the system data. Based on the root cause of the anomaly, playback anomalies are repaired for the currently playing media content.

2. The playback anomaly repair method according to claim 1, characterized in that, Prior to the step of acquiring system data when an anomaly occurs during media playback, the playback anomaly repair method further includes: Detect any stuttering or other abnormalities during media playback; Detect whether there is a black screen error during media playback; If the aforementioned stuttering and / or black screen issues occur, it is determined that an abnormal situation exists during media playback.

3. The playback anomaly repair method according to claim 2, characterized in that, The detection of whether there are stuttering or abnormalities during media playback includes: Monitor data input capabilities, decoding output capabilities, and rendering capabilities; If any of the data input capability, the decoding output capability, or the rendering capability is abnormal, the stuttering abnormality is determined to exist.

4. The playback anomaly repair method according to claim 2, characterized in that, The detection of whether there is a black screen abnormality during media playback includes: Upon receiving a black screen error message, confirm that the black screen error exists; and / or, Monitor playback status and screen status; If the playback status is normal and the screen status is no screen output, then the black screen anomaly is confirmed.

5. The playback anomaly repair method according to claim 1, characterized in that, The system data includes current resource data, and determining the root cause of the abnormal situation based on the system data includes: when the current resource data reaches the lag threshold, determining that the root cause of the abnormal situation includes a resource root cause; The method of repairing playback anomalies of currently playing media content based on the root cause of the anomaly includes: determining the target resource data required to resolve the anomaly based on historical resource data; and allocating resources to the currently playing media content based on the target resource data and the current resource data.

6. The playback anomaly repair method according to claim 1, characterized in that, The system data includes network status information, and determining the root cause of the abnormal situation based on the system data includes: when the network status information includes information about network unavailability or poor network status, determining that the root cause of the abnormal situation includes a network root cause; The method of repairing playback anomalies of the currently playing media content based on the root cause of the anomaly includes: activating a network repair mechanism and / or a domain name repair mechanism to repair the network status when the media content is playing.

7. The playback anomaly repair method according to claim 1, characterized in that, The system data includes the audio and video bitstreams during bitstream parsing. Determining the root cause of the abnormal situation based on the system data includes: comparing the parameters in the audio and video bitstreams with preset encoding parameters; when the parameters in the audio and video bitstreams are inconsistent with the preset encoding parameters, determining that the root cause of the abnormal situation includes the bitstream root cause. The playback anomaly repair based on the root cause of the anomaly includes: determining missing parameters in the audio and video bitstream based on the parameters in the audio and video bitstream and the preset encoding parameters; and supplementing the missing parameters in the audio and video bitstream.

8. A playback anomaly repair device, characterized in that, The playback error repair device includes: The data acquisition module is used to acquire system data when abnormal situations occur during media playback; The root cause determination module is used to determine the root cause of the abnormal situation based on the system data. The anomaly repair module is used to repair playback anomalies of the currently playing media content based on the root cause of the anomaly.

9. An electronic device, characterized in that, The electronic device includes: one or more processors, a memory, and one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the playback anomaly repair method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, It stores a computer program, which is loaded by a processor to perform the steps in the playback anomaly repair method according to any one of claims 1 to 7.

Images