Display device and browser play thread optimization method

Abstract

The embodiment of the invention provides a display device and a browser play thread optimization method, and the method comprises the steps: responding to a play quit instruction of a media asset, and removing a media asset label corresponding to the media asset; generating a play thread release instruction according to the removal result of the media asset label; in response to the play thread release instruction, releasing a first resource, a second resource and a third resource; the first resource is a resource corresponding to a media player playing the media asset; the second resource is a resource corresponding to a thread for processing calling and event processing of a media resource playing interface; the third resource is a resource corresponding to a platform player of the display equipment. According to the method, the system consumption can be reduced, the system performance of the display equipment can be improved and the problem that the system performance is influenced due to continuous occupation of the playing thread in the browser can be solved through a mechanism of releasing the resource and actively recycling the media playing thread resource by the browser.

Description

Technical Field

[0001] The present application relates to the technical field of display devices, and in particular to a method for optimizing a display device and a browser playback thread. Background Art

[0002] Display devices are intelligent devices that can present user interfaces and support user interaction. Taking smart TVs as an example, smart TVs are based on Internet application technology, have open operating systems and chips, have open application platforms, can realize two-way human-computer interaction functions, and are TV products that integrate multiple functions such as audio and video, entertainment, and data to meet the diverse and personalized needs of users. Display devices can present different media recommendation interfaces, which can include multiple media options for users to select and play.

[0003] In smart TVs, taking digital TV platforms as an example, users can obtain media resources, such as video resources, through third-party applications. Third-party applications include but are not limited to apps and web content provided by media service providers. Video content from third-party sources is one of the important resources provided by TV to users. However, the video playback function of these applications depends on the support of browsers and TV platforms. Since different third-party applications are developed by different manufacturers, their implementation methods vary, which leads to a lack of uniformity in the management of playback behavior. In particular, the behavior of different applications may be inconsistent in terms of resource acquisition and resource release.

[0004] On the TV platform, thread resource availability is limited. When an application fails to actively release resources when exiting media playback, the playback threads created by the browser, such as media thread resources, will continue to occupy system resources. For scenarios that require long-term or repeated playback of media assets, if media thread resources continue to increase and are not released, it may eventually cause system performance to degrade. When thread resources are exhausted, the application may not be able to obtain the required platform resources. At this time, it may be necessary to restart the application or the entire TV system to resume normal operation, affecting the user experience. Summary of the invention

[0005] The present application provides a method for optimizing a display device and a browser playback thread to solve the problem that the continuous occupancy of the playback thread in the browser affects system performance.

[0006] In a first aspect, some embodiments of the present application provide a display device, including.

[0007] a display configured to display a user interface;

[0008] A controller is coupled to the display and is configured to:

[0009] In response to the media asset's exit playback instruction, remove the media asset tag corresponding to the media asset;

[0010] Generate a playback thread release instruction according to the removal result of the media asset tag;

[0011] In response to the playback thread release instruction, the first resource, the second resource and the third resource are released; the first resource is the resource corresponding to the media player that plays the media asset; the second resource is the resource corresponding to the thread used to process the call of the media asset playback interface and event processing; the third resource is the resource corresponding to the platform player of the display device.

[0012] The above technical solution has the following advantages or beneficial effects: by releasing the first resource, the second resource and the third resource, the display device can ensure that the system can thoroughly clean up the media playback related resources that are no longer needed. After releasing the resources, the display device will have more resources to process other tasks, thereby improving the overall performance and response speed.

[0013] In some embodiments, before removing the media asset tag corresponding to the media asset, the controller is further configured to:

[0014] Detect the tag type of the media asset tag; the tag type includes a media asset element tag and a media asset parent element tag; in response to the media asset tag being the media asset element itself, determine that the tag type is a media asset element tag; the media asset element is an element tag corresponding to when the media asset is embedded in the browser; in response to the media asset tag being the parent element of the media asset element, determine that the tag type is a media asset parent element tag; the parent element is a parent element tag corresponding to when the media asset is embedded in the browser.

[0015] The above technical solution has the following advantages or beneficial effects: determining the tag type as a media asset parent element tag. By distinguishing between media asset element tags and media asset parent element tags, the television system can more accurately identify and process media asset content, thereby achieving more effective management and optimization of media assets.

[0016] In some embodiments, the controller executes the release of the first resource, the second resource, and the third resource in response to the playback thread release instruction, and is specifically configured as follows:

[0017] In response to the tag type being the media asset element tag, a first removal instruction is generated; the media asset element is removed according to the first removal instruction; a first playback thread release instruction is generated according to the removal result of the media asset element; the first playback thread release instruction is sent to a browser module; the browser module is used to manage the playback thread of the browser; the browser module releases the first resource, the second resource and the third resource according to the first playback thread release instruction.

[0018] The above technical solution has the following advantages or beneficial effects: the display device can send the first playback thread release instruction to the browser module, and after receiving the first playback thread release instruction, the browser module can manage the playback thread according to the instruction to ensure that the playback thread related to the media asset element is released. In this way, by timely removing the media asset elements that are no longer needed and releasing related resources, it is possible to avoid resource waste, ensure that other applications or user operations can obtain necessary resources, and improve the response speed and efficiency of the system.

[0019] In some embodiments, the controller executes the release of the first resource, the second resource, and the third resource in response to the playback thread release instruction, and is specifically configured as follows:

[0020] In response to the tag type being the media asset parent element tag, a second removal instruction is generated; the parent element of the media asset element is removed according to the second removal instruction; a second playback thread release instruction is generated according to the removal result of the parent element; the second playback thread release instruction is sent to a browser module; the browser module is used to manage the browser's playback thread; through the browser module, the first resource, the second resource and the third resource are released according to the second playback thread release instruction.

[0021] The above technical solution has the following advantages or beneficial effects: by timely removing the media asset parent elements that are no longer needed and releasing the related resources, it can ensure that the resources that are no longer used can be recycled by the system for use by other applications or operations, reducing unnecessary resource occupation and improving the response speed and efficiency of the system.

[0022] In some embodiments, before releasing the first resource, the second resource, and the third resource, the controller is further configured to:

[0023] Record the playback status of the media asset; after releasing the first resource, the second resource and the third resource in response to the playback thread release instruction, the controller is further configured to: obtain the playback status; after the first resource, the second resource and the third resource are released, keep the playback status unchanged.

[0024] The above technical solution has the following advantages or beneficial effects: even if the resources are released, the playback experience of the media assets (such as playback progress, volume, etc.) can still maintain continuity and will not be interrupted or reset due to the release of resources, thereby providing users with a smooth and continuous playback experience and improving the stability and reliability of the system.

[0025] In some embodiments, after releasing the first resource, the second resource, and the third resource, the controller is further configured to:

[0026] In response to an instruction to play the media asset again, determine whether to re-add the removed media asset element or the parent element; if the media asset element or the parent element is not added, reload the playback thread of the media asset to be played through the application module, and start playing the media asset to be played by calling the playback interface through the application module; if the media asset element or the parent element is added, determine the playback status of the media asset before exiting the playback of the media asset, and determine the playback form of the media asset according to the playback status.

[0027] The above technical solution has the following advantages or beneficial effects: by responding to the user's replay instruction, the system can quickly resume playback, reduce the user's waiting time, and improve the continuity and fluency of playback. At the same time, the use of resources can be optimized according to whether to re-add elements to avoid unnecessary waste of resources.

[0028] In some embodiments, the playback state includes a playing state, and the controller determines the playback form of the media asset according to the playback state, and is specifically configured as follows:

[0029] In response to the playback status of the media asset being the playing status before exiting the playback of the media asset, the media player and the media playback thread are recreated through the browser; the platform player is loaded, and a first start instruction is generated based on the media player, the media playback thread and the platform player; in response to the first start instruction, the media asset is controlled to be restored to the playback position before the media asset is exited; and the media asset is played at the playback position.

[0030] The above technical solution has the following advantages or beneficial effects: by restoring to the playback position before exiting, the display device can maintain the continuity of media playback and avoid users starting to watch from the beginning; by recreating the playback environment, the system can manage resources more efficiently.

[0031] In some embodiments, the playing state includes a pause state, and the controller determines the playing form of the media asset according to the playing state, and is specifically configured as follows:

[0032] In response to the playback state of the media asset being the paused state before exiting the playback of the media asset, it is determined whether the application module executes a playback start process; and the playback form of the media asset is determined according to the result of the application module executing the playback start process.

[0033] The above technical solution has the following advantages or beneficial effects: the display device can execute different processes according to whether the application is actively started, so as to achieve effective resource management and avoid unnecessary resource consumption.

[0034] In some embodiments, the controller determines the playing form of the media asset according to the execution result of the application module on the start-up process, and is specifically configured as follows:

[0035] When the application module executes the start-up process, the media player and the media playback thread are recreated through the browser, the platform player is loaded, and a first start-up instruction is generated based on the media player, the media playback thread and the platform player; in response to the first start-up instruction, the media asset is controlled to be restored to the playback position before the media asset is exited, and the media asset is played at the playback position; when the application module does not execute the start-up process, the first resource, the second resource and the third resource are kept in a released state.

[0036] The above technical solution has the following advantages or beneficial effects: the display device can decide whether to recreate the playback environment according to the execution result of the application module, and can manage resources more effectively to avoid unnecessary resource occupation and waste.

[0037] In a second aspect, some embodiments of the present application provide a method for optimizing a browser playback thread.

[0038] In response to the media asset's exit playback instruction, remove the media asset tag corresponding to the media asset;

[0039] Generate a playback thread release instruction according to the removal result of the media asset tag;

[0040] In response to the playback thread release instruction, the first resource, the second resource and the third resource are released; the first resource is the resource corresponding to the media player that plays the media asset; the second resource is the resource corresponding to the thread used to process the call of the media asset playback interface and event processing; the third resource is the resource corresponding to the platform player of the display device.

[0041] The above technical solution has the following advantages or beneficial effects: by releasing the first resource, the second resource and the third resource, the display device can ensure that the system can thoroughly clean up the media playback related resources that are no longer needed. After releasing the resources, the display device will have more resources to process other tasks, thereby improving the overall performance and response speed.

[0042] It can be seen from the above technical solutions that some embodiments of the present application provide a method for optimizing the display device and browser playback thread, the method comprising: in response to a media asset exit playback instruction, removing the media asset tag corresponding to the media asset; generating a playback thread release instruction according to the removal result of the media asset tag; in response to the playback thread release instruction, releasing the first resource, the second resource and the third resource; the first resource is a resource corresponding to the media player that plays the media asset; the second resource is a resource corresponding to the thread for processing the call of the media asset playback interface and event processing; the third resource is a resource corresponding to the platform player of the display device. The method can reduce system consumption, improve the system performance of the display device, and solve the problem of continuous occupation of the playback thread in the browser affecting system performance through the mechanism of releasing resources and actively recovering media playback thread resources in the browser. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1 A schematic diagram of an operation scenario between a display device and a control device provided in some embodiments of the present application;

[0045] Figure 2 A schematic diagram of the hardware configuration of a display device provided in some embodiments of the present application;

[0046] Figure 3 A schematic diagram of software configuration of a display device provided in some embodiments of the present application;

[0047] Figure 4 A schematic diagram of an application video loading scenario shown in some embodiments of the present application;

[0048] Figure 5 A schematic diagram of a scenario in which an application video exits playback, shown in some embodiments of the present application;

[0049] Figure 6 Another schematic diagram of a scenario of exiting the application video playback scenario shown in some embodiments of the present application;

[0050] Figure 7 A schematic flow chart of an optimization method for a display device to execute a browser playback thread provided in some embodiments of the present application;

[0051] Figure 8 A schematic diagram of a process of releasing resources of a display device provided in some embodiments of the present application;

[0052] Fig. 9 Another schematic diagram of a process of releasing resources of a display device provided in some embodiments of the present application;

[0053] Fig.10 A schematic diagram of a scenario for releasing media asset playback resources provided in some embodiments of the present application;

[0054] Fig.11 A timing diagram of media asset playback resource release and resource recovery provided in some embodiments of the present application. DETAILED DESCRIPTION

[0055] The following embodiments are described in detail, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following embodiments do not represent all implementations consistent with the present application. They are only examples of systems and methods consistent with some aspects of the present application as detailed in the claims.

[0056] It should be noted that the brief description of terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their ordinary and common meanings.

[0057] The terms "first", "second", "third", etc. in the specification and claims of this application and the above drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances.

[0058] The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

[0059] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.

[0060] In the embodiment of the present application, the display device 200 generally refers to a device with image display and data processing capabilities. For example, the display device 200 includes but is not limited to a smart TV, a mobile terminal, a computer, a monitor, an advertising screen, a wearable device, a virtual reality device, an augmented reality device, etc.

[0061] Figure 1This is a schematic diagram of an operation scenario between a display device and a control device provided in some embodiments of the present application. Figure 1 As shown in FIG. 1 , a user can operate the display device 200 through touch operation, the mobile terminal 300 and the control device 100. The control device 100 is used to receive operation instructions input by the user and convert the operation instructions into control instructions that can be recognized and responded to by the display device 200. For example, the control device 100 can be a remote controller, a stylus pen, a handle, etc.

[0062] The mobile terminal 300 can be used as a control device for performing human-computer interaction between the user and the display device 200. The mobile terminal 300 can also be used as a communication device for establishing a communication connection with the display device 200 and performing data interaction. In some embodiments, the mobile terminal 300 can install software applications with the display device 200, and achieve connection and communication through a network communication protocol to achieve the purpose of one-to-one control operation and data communication. The audio and video content displayed on the mobile terminal 300 can also be transmitted to the display device 200 to achieve a synchronous display function.

[0063] In some embodiments, the mobile terminal 300 or other electronic devices may also simulate the functions of the control device 100 by running an application program for controlling the display device 200 .

[0064] like Figure 1 As also shown in FIG. 4 , the display device 200 also communicates data with the server 400 through various communication methods. The display device 200 may be allowed to communicate and connect through a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0065] The display device 200 may provide a broadcast receiving television function, and may also additionally provide an intelligent network television function with a computer support function, including but not limited to network television, smart television, Internet Protocol television (IPTV), and the like.

[0066] Figure 2 Some embodiments of the present application provide Figure 1 2 is a block diagram of the hardware configuration of the display device 200.

[0067] In some embodiments, the display device 200 may include at least one of a tuner 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.

[0068] In some embodiments, the detector 230 is used to collect signals of the external environment or external interaction. For example, the detector 230 includes a light receiver, a sensor for collecting the intensity of ambient light; or, the detector 230 includes an image collector, such as a camera, which can be used to collect external environment scenes, user attributes or user interaction gestures; or, the detector 230 includes a sound collector, such as a microphone, etc., for receiving external sounds.

[0069] In some embodiments, the display 260 includes a display function component for presenting a picture, and a driving component for driving an image display. The display 260 is used to receive an image signal output from the controller 250 for display. For example, the display 260 can be used to display video content, image content, and components of a menu control interface and a user control UI interface.

[0070] In some embodiments, the communication device 220 is a component for communicating with an external device or server 400 according to various communication protocol types. The display device 200 may be provided with a plurality of communication devices 220 according to different supported communication modes. For example, when the display device 200 supports wireless network communication, the display device 200 may be provided with a communication device 220 including a WiFi function. When the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 including a Bluetooth function.

[0071] The communication device 220 can enable the display device 200 to communicate with the external device or server 400 by wireless or wired connection. Among them, the wired connection can connect the display device 200 with the external device through components such as data cables and interfaces. The wireless connection can connect the display device 200 with the external device through wireless signals or wireless networks. The display device 200 can establish a connection relationship with the external device directly, or indirectly establish a connection relationship through a gateway, a router, a connection device, etc.

[0072] In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and a first interface to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to the user's operation through various software control programs stored in the memory. The controller 250 controls the overall operation of the display device 200.

[0073] In some embodiments, the controller 250 and the tuner-demodulator 210 may be located in different separate devices, that is, the tuner-demodulator 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.

[0074] In some embodiments, the user may input a user command through a graphical user interface (GUI) displayed on the display 260 , and the user input interface receives the user input command through the graphical user interface (GUI).

[0075] In some embodiments, the audio output device 270 may be a local speaker of the display device 200, or may be an external audio output device of the display device 200. In particular, for the external audio output device of the display device 200, the display device 200 may also be provided with an external audio output terminal, and the audio output device may be connected to the display device 200 through the external audio output terminal to output the sound of the display device 200.

[0076] In some embodiments, the user input interface 280 may be used to receive instructions from a user.

[0077] In order to perform user interaction, in some embodiments, the display device 200 may run an operating system. The operating system is a computer program for managing and controlling hardware resources and software resources in the display device 200. The operating system can control the display device to provide a user interface, for example, the operating system can directly control the display device to provide a user interface, or can provide a user interface by running an application program. The operating system also allows the user to interact with the display device 200.

[0078] It should be noted that the operating system may be a native operating system based on a specific operating platform, or a third-party operating system deeply customized based on a specific operating platform, or an independent operating system specially developed for the display device.

[0079] The operating system can be divided into different modules or layers according to the functions implemented, such as Figure 3 As shown, in some embodiments, the system is divided into four layers, from top to bottom, namely, the application layer (Applications layer for short), the middleware layer, and the hardware layer.

[0080] In some embodiments, the application layer is used to provide services and interfaces for applications so that the display device 200 can run applications and interact with users based on the applications. At least one application can be run in the application layer, and these applications can be window programs, system settings programs, clock programs, etc. that come with the operating system; they can also be applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the above examples.

[0081] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications. The application framework layer includes some predefined functions. The application framework layer is equivalent to a processing center that determines the actions that applications in the application layer take. Through the API interface, applications can access system resources and obtain system services during execution.

[0082] like Figure 3 As shown, Figure 3 Some embodiments of the present application provide Figure 1 Schematic diagram of software configuration in the display device. In some embodiments, the system of the display device 200 can be divided into three layers, namely, application layer, middleware layer and hardware layer from top to bottom.

[0083] The application layer mainly includes commonly used applications on TV and application frameworks. Common applications are mainly applications developed based on browsers, such as HTML5 APPs and native APPs.

[0084] The Application Framework is a complete program model that has all the basic functions required by standard application software, such as file access, data exchange, etc., as well as the user interfaces of these functions (toolbars, status bars, menus, dialog boxes).

[0085] Native apps can support online or offline, message push or local resource access.

[0086] The middleware layer includes various TV protocols, multimedia protocols, system components and other middleware. The middleware can use the basic services (functions) provided by the system software to connect various parts of the application system or different applications on the network, and can achieve the purpose of resource sharing and function sharing.

[0087] The hardware layer mainly includes the hardware abstraction layer (HAL) interface, hardware and drivers. The HAL interface is a unified interface for all TV chips to connect, and the specific logic is implemented by each chip. Drivers mainly include: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver.

[0088] It should be noted that the above example is only a simple division of the operating system functions and does not constitute a limitation on the specific operating system form of the display device 200 in the embodiment of the present application. Depending on factors such as the function of the display device and the type of operating system, the number of levels and specific level types contained in the operating system may be expressed in other forms.

[0089] The display device 200 is an intelligent device that can present a user interface and support user interaction. Taking a smart TV as an example, a smart TV is based on Internet application technology, has an open operating system and chip, has an open application platform, can realize a two-way human-computer interaction function, and is a TV product that integrates multiple functions such as audio and video, entertainment, and data to meet the diverse and personalized needs of users.

[0090] In smart TVs, taking digital TV platforms as an example, users can obtain media resources, such as video resources, etc. through third-party applications (hereinafter, the media resources will be explained as video). Among them, third-party applications include but are not limited to APPs provided by video service providers and web content, etc. These third-party video content is one of the important resources provided by TV to users. However, the video playback function of these applications depends on the support of browsers and TV platforms (such as TV chips and the systems running on them). Since different third-party applications are developed by different manufacturers, their implementation methods are different, which leads to a lack of uniformity in the management of playback behavior.

[0091] In particular, different applications may behave inconsistently in terms of resource acquisition and resource release. For example, when applications acquire resources through the browser, they release the resources in different ways after use. If an application fails to actively release the resources it has acquired, these resources may continue to be occupied. For TV platforms with limited resources, this resource occupation problem may seriously affect the performance of the entire system.

[0092] The above situation is described in detail below in combination with actual scenarios.

[0093] Figure 4 This is a schematic diagram of an application video loading scenario shown in some embodiments of the present application, such as Figure 4 As shown, in some embodiments, on a TV platform, the loading and playing of video content involves the collaborative work of an application module, a browser, and a TV platform (such as a platform chip). For example, whether it is a TV browser or a browser on a computer, loading a video using an application or a page is done through the browser, and on a TV platform it depends on the support of the chip platform. Figure 4In the application video loading scenario shown, when the user selects a video to play, such as when the user selects to play a video through an application or web page, the application or web page will pass the address of the video resource to the browser. After the browser receives the video resource address, it starts to perform resource loading operations. This process depends on the chip support of the TV platform. After the resource loading is completed, the browser can send the loading completion information back to the application or web page through the event notification mechanism. After the application or web page receives the resource loading completion event, it will perform subsequent operations, such as starting video playback.

[0094] Exemplary, combined Figure 4 The detailed process is as follows: when the user selects a video to play in the application, the application module passes the path of the video resource to the browser. After receiving the video resource path, the browser creates a media player instance inside it and initializes a media thread resource, which is used to process the call of the playback interface and the processing of related events. After that, the browser can request the video playback resource from the TV platform and start a platform player, such as the player built into the platform. After the platform player receives the resource, it is ready to play the video. When the application calls the start-up interface, the browser can send a start-up instruction to the platform player, and the platform player starts playing the video content after receiving the instruction. During the whole process, the browser is responsible for coordinating the communication between the application, the media thread resource and the platform player, so that users can watch the video content smoothly on the TV.

[0095] Regarding the scenario of resource release, when the user exits the video playback, resource release can be divided into two different situations.

[0096] Figure 5 This is a schematic diagram of a scenario in which an application video exits playback, shown in some embodiments of the present application. Figure 5 As shown, in some embodiments, on a TV platform, when a user finishes playing a video, a series of resource release operations can be actively triggered to ensure that the system resources are effectively managed.

[0097] For example, when the application exits video playback, it can actively release previously loaded video resources to avoid unnecessary occupation of resources. At the same time, the application will also actively release previously created media player instances and media thread resources, such as resources related to the platform player, so that when the user no longer needs to watch the video, the TV system can release related resources in time, thereby improving the resource utilization efficiency and overall performance of the TV platform. However, this method is not suitable for all types of applications. Some applications will not actively release video resources when exiting video playback, which will cause resources to continue to be occupied, thereby affecting system performance.

[0098] Figure 6Another schematic diagram of a scenario in which an application video exits playback in some embodiments of the present application is shown, such as Figure 6 As shown, in some embodiments, during the video playback process of the TV platform, when the application chooses to save instead of releasing resources after playing the video, these resources will continue to be occupied. Therefore, even if the user has exited the video playback, the relevant media video resources are still kept in the memory. If the application does not actively release these resources when exiting the playback, then these resources will be saved until the application is completely exited or the TV is restarted. In this case, if the user plays other videos again, the application will create a new media player and thread resources instead of reusing existing resources. As the number of plays increases, thread resources will continue to accumulate because old resources are not released and new resources are constantly created. Long-term accumulated thread resources may cause system performance to degrade, or even cause problems with thread resource exhaustion.

[0099] That is to say, on the TV platform, the availability of thread resources is limited. When the application fails to actively release resources when exiting video playback, such as Figure 6 As shown, the media thread resources created by the browser will continue to occupy system resources. The application may use these playback resources again in the future, or may not use these playback resources in the future. For scenarios that require long-term or repeated video playback, if the media thread resources continue to increase and are not released, it may eventually cause system performance to degrade. When thread resources are exhausted, the application may not be able to obtain the required platform resources. At this time, it may be necessary to restart the application or the entire TV system to resume normal operation, affecting the user experience.

[0100] Therefore, based on the above scenario, in order to maintain the performance of the TV platform and provide a good user experience, some embodiments of the present application provide a display device 200, wherein the display device 200 includes a display 260 and a controller 250 coupled to the display 260. The display 260 is configured to display a user interface, and the controller 250 enables the display device 200 to execute a method for optimizing the browser playback thread by running a specific computer execution instruction. The display device 200 can achieve effective control of the playback thread resources in the browser, saving the occupation of the playback thread resources and platform thread resources in the browser.

[0101] In order to facilitate the understanding of the technical solutions in some embodiments of the present application, each step is described in detail below in conjunction with some specific embodiments and drawings. Figure 7 A flowchart of an optimization method for executing a browser playback thread on a display device provided in some embodiments of the present application is shown in FIG. Figure 7 As shown, in some embodiments, when the display device 200 executes the optimization method of the browser playback thread, the following steps may be included, and the specific contents include:

[0102] Step S1: in response to an instruction to exit playing of a media asset, the display device 200 removes a media asset tag corresponding to the media asset.

[0103] During the process of user interaction with the display device 200, when the user decides to stop watching the current media such as video, audio, etc., the exit playback instruction can be triggered through the corresponding control on the user interface (UI), such as the "Stop", "Exit" and other buttons. After receiving the exit playback instruction, the television system can first identify the unique identifier of the media currently being played (such as the media ID), and based on the identifier, find and remove the media tag associated with it. The media tag can include basic information of the media (such as title, type, playback progress, etc.) and playback status (such as whether it is playing, whether it is paused, etc.). In this way, by removing the media tag, it can ensure that system resources are not occupied by the media that has stopped playing, so as to help improve the resource utilization of the overall system.

[0104] In some embodiments, before removing the media asset tag corresponding to the media asset, the display device 200 may detect the tag type of the media asset tag, wherein the tag type includes a media asset element tag and a media asset parent element tag. In response to the media asset tag being the media asset element itself, the display device 200 may determine that the tag type is a media asset element tag, and the media asset element is the element tag corresponding to when the media asset is embedded in the browser. In response to the media asset tag being the parent element of the media asset element, the display device 200 may determine that the tag type is a media asset parent element tag, and the parent element is the parent element tag corresponding to when the media asset is embedded in the browser.

[0105] Exemplarily, the display device 200 can divide the types of media asset tags into media asset element tags and media asset parent element tags. Among them, the media asset element tag is the element tag corresponding to when the media asset is embedded in the browser, and the media asset parent element tag is the parent element tag corresponding to when the media asset is embedded in the browser. If the media asset tag is the media asset element itself, the display device 200 will determine that its tag type is a media asset element tag. If the media asset tag is the parent element of the media asset element, the display device 200 will determine that its tag type is a media asset parent element tag. By distinguishing between media asset element tags and media asset parent element tags, the television system can more accurately identify and process media asset content, thereby achieving more effective management and optimization of media assets.

[0106] In an embodiment of the present application, the overall optimization strategy for the browser playback thread is that when the media asset tag or the media asset parent element tag in the page does not participate in the layout and rendering in the page, the browser executes the following process: save the playback status of the media asset, and on the premise of saving the media asset playback status, actively release the media playback thread associated with the media asset tag, and then release the platform player resources created by the TV platform. When the media asset tag or the media asset parent element participates in the layout of the page again, the browser actively recreates the media playback thread, pulls up the platform player, and restarts the broadcast. In this way, by releasing related resources when the media asset is not visible, the resource occupation of the browser can be reduced. When the media asset becomes visible again, the playback can be quickly resumed to improve the user experience. In the scenario of playing multiple videos for a long time, this strategy helps to maintain the overall performance of the platform, avoid performance degradation caused by excessive resource occupation, and thus solve the problem of continuous occupation of the playback thread in the browser affecting system performance. After step S1 is executed, the following step S2 can be executed.

[0107] Step S2: the display device 200 generates a playback thread release instruction according to the removal result of the media asset tag.

[0108] After the media asset tag corresponding to the media asset is successfully removed, the display device 200 can automatically generate a playback thread release instruction according to the result of the removal. In some embodiments, the playback thread release instruction can include the resource type to be released and the corresponding media asset identifier, so as to accurately locate the playback thread to be released and its related resources. In this way, by accurately controlling the release of the playback thread, unnecessary resource occupation can be effectively reduced and resource recovery efficiency can be improved. By timely releasing the playback thread that is no longer needed, the system load can be reduced and the performance of the television system can be improved. After step S2 is executed, the following step S3 can be executed.

[0109] Step S3: In response to the playback thread release instruction, the display device 200 releases the first resource, the second resource, and the third resource.

[0110] After generating the playback thread release instruction, the display device 200 releases the first resource, the second resource and the third resource in response to the playback thread release instruction. The first resource is a resource corresponding to the media player that plays the media asset; the second resource is a resource corresponding to the thread for processing the call of the media asset playback interface and event processing; the third resource is a resource corresponding to the platform player of the display device.

[0111] Exemplarily, the first resource may be the resource occupied by a media player for playing media assets, such as a video player, an audio player, etc. The first resource may include memory, CPU time slices, etc. The display device 200 may release instructions according to the playback thread, call the relevant API of the media player, and release all the resources occupied by it. The second resource may be the resource occupied by the thread that processes the media asset playback interface call and event processing. These threads are responsible for monitoring user operations (such as play, pause, fast forward, etc.), and processing various events that may occur during media playback (such as buffering, errors, end of playback, etc.). The display device 200 will also terminate these threads and release the resources occupied by them according to the playback thread release instructions. The third resource may be the resource occupied by the platform player of the display device 200. The platform player is used to provide underlying playback capabilities and interact with specific media formats and codecs. The display device 200 can notify the platform player to release the resources occupied by the current media asset through a specific interface or API.

[0112] By releasing the first resource, the second resource and the third resource, the display device 200 can ensure that the system can completely clean up the media playback related resources that are no longer needed. After releasing the resources, the display device 200 will have more resources to process other tasks, thereby improving the overall performance and response speed.

[0113] Figure 8 A schematic diagram of a process of releasing resources of a display device provided in some embodiments of the present application, such as Figure 8 As shown, in some embodiments, when the display device 200 releases the first resource, the second resource, and the third resource, in response to the tag type being a media asset element tag, it can generate a first removal instruction, then remove the media asset element according to the first removal instruction, and then generate a first playback thread release instruction according to the removal result of the media asset element, and send the first playback thread release instruction to the browser module, wherein the browser module is used to manage the playback thread of the browser, and finally, the browser module releases the first resource, the second resource, and the third resource according to the first playback thread release instruction.

[0114] Exemplarily, the display device 200 may first detect the tag type of the media asset tag. After determining that the tag type is a media asset element tag, the display device 200 may generate an instruction, the purpose of which is to remove the media asset element. The display device 200 may remove the media asset element from the current display or play list by performing a removal operation. After the media asset element is removed, the display device 200 may generate a new instruction based on the result of the removal, and the instruction is used to release the playback thread associated with the media asset element. In order to realize the function of managing the browser playback process, a browser module may be provided in the display device 200, and the module may be a component responsible for managing the browser playback thread. The display device 200 may send a first playback thread release instruction to the browser module. After the browser module receives the first playback thread release instruction, it may manage the playback thread according to the instruction to ensure that the playback thread related to the media asset element is released. In this way, by timely removing the media asset elements that are no longer needed and releasing related resources, it is possible to avoid waste of resources, ensure that other applications or user operations can obtain necessary resources, and improve the response speed and efficiency of the system.

[0115] Fig. 9 Another schematic diagram of a process of releasing resources of a display device provided in some embodiments of the present application is as follows: Fig. 9 As shown, in some embodiments, when the display device 200 releases the first resource, the second resource, and the third resource, in response to the tag type being a media asset parent element tag, a second removal instruction can be generated, and then the parent element of the media asset element is removed according to the second removal instruction, and then a second playback thread release instruction is generated according to the removal result of the parent element, and the second playback thread release instruction is sent to the browser module, and the browser module is used to manage the playback thread of the browser. Finally, through the browser module, the first resource, the second resource, and the third resource are released according to the second playback thread release instruction.

[0116] Exemplarily, the display device 200 can first detect the tag type of the media asset tag, and after determining that the tag type is a media asset parent element tag, a second removal instruction can be generated, the purpose of which is to remove the parent element of the media asset element. According to the second removal instruction, the display device 200 can perform a removal operation to remove the parent element of the media asset element. After the parent element of the media asset element is removed, the display device 200 can generate a new instruction based on the result of the removal, and the instruction is used to release the playback thread associated with the parent element. The generated second playback thread release instruction can also be sent to the browser module. After the browser module receives the second playback thread release instruction, it can manage the playback thread according to the instruction to ensure that the playback thread related to the media asset parent element is released. In this way, by promptly removing the media asset parent element that is no longer needed and releasing related resources, it can be ensured that resources that are no longer used can be recycled by the system for use by other applications or operations, thereby reducing unnecessary resource occupation and improving the response speed and efficiency of the system.

[0117] In some embodiments, the display device 200 may further record the playback status of the media asset before releasing the first resource, the second resource, and the third resource. After releasing the first resource, the second resource, and the third resource, the display device 200 may obtain the playback status and keep the playback status unchanged after the first resource, the second resource, and the third resource are released.

[0118] Exemplarily, before releasing the first resource, the second resource, and the third resource, the display device 200 records the playback status of the current media asset, and the playback status may include but is not limited to information such as playback progress, volume, playback speed, and whether to pause. The display device 200 then releases the first resource, the second resource, and the third resource. After releasing the resources, the display device 200 will reacquire the previously recorded playback status to ensure that the playback status of the media asset will not be lost after the resources are released. In this way, even if the resources are released, the playback experience of the media asset (such as playback progress, volume, etc.) can still maintain continuity and will not be interrupted or reset due to the release of resources, thereby providing users with a smooth and continuous playback experience and improving the stability and reliability of the system.

[0119] Fig.10 A schematic diagram of a scenario for releasing media asset playback resources provided in some embodiments of the present application. Fig.11 A timing diagram of media resource release and resource recovery provided in some embodiments of the present application, combined with Fig.10 and Fig.11In some embodiments, for the scenario where the media asset exits playback, taking the media asset as a video as an example, in response to the exit playback instruction of the media asset, the application module can parse and remove the tag corresponding to the video. If the application module removes the video element, the video element will no longer participate in the page layout, and the browser will notify the video element object, that is, the browser notifies that the video element is removed. After that, the browser can release all the media player and media thread resources, and notify the TV platform to release the platform player resources, while keeping the playback state of the video unchanged. If the application module removes the parent element containing the video element, the parent element will no longer participate in the page layout, and the browser can notify each element object under the parent element, that is, the browser notifies that each element object under the parent element is removed. Similarly, the browser can release all the media player and media thread resources, and notify the TV platform to release the platform player resources, while keeping the playback state of the video unchanged. Therefore, the browser can reduce the consumption of the system through the mechanism of releasing resources and actively recovering the media playback thread resources, thereby improving the system performance of the display device 200.

[0120] In some embodiments, after releasing the first resource, the second resource, and the third resource, the display device 200 responds to an instruction to play the media asset again and determines whether the application module re-adds the removed media asset element or parent element. If the media asset element or parent element is not added, the playback thread of the media asset to be played is reloaded through the application module, and the playback interface is called through the application module to start playing the media asset to be played. If the media asset element or parent element is added, the playback status of the media asset before exiting the playback of the media asset is determined, and the playback form of the media asset is determined according to the playback status.

[0121] Exemplary, combined Fig.11When the user issues an instruction to play the media asset again, it can first be determined whether the application module needs to re-add the previously removed media asset element or its parent element to the current playback environment. If the application module does not add the media asset element or parent element, for example, the application module uses a new video element to participate in the page layout, the browser will not automatically load the video resource, and the television system reloads the playback thread of the media asset to be played through the application module. For example, the application module can re-initialize the playback environment, such as re-acquiring media asset data, setting playback parameters, etc., and the application module calls the playback interface to start the playback of the media asset to be played. At the same time, when the new video element starts to play, the system will keep the media thread resources associated with the old video element released, so that the playback thread and resources related to the old video element will be cleared to ensure that the old resources are effectively released. If the application module re-adds the media asset element or parent element, the display device 200 can determine what the playback status of the media asset is before exiting the playback of the media asset, such as playback progress, volume, playback speed, whether to pause, etc., and then determine the playback form of the media asset according to the playback status. By responding to the user's replay command, the system can quickly resume playback, reduce the user's waiting time, and improve the continuity and smoothness of playback. At the same time, it can optimize resource usage based on whether to re-add elements to avoid unnecessary resource waste.

[0122] In some embodiments, the play state includes a playing state, and when the display device 200 determines the play form of the media asset according to the play state, in response to the play state of the media asset being the playing state before exiting the play of the media asset, the media player and the media play thread are recreated through the browser, and the platform player is loaded, and a first play start instruction is generated based on the media player, the media play thread and the platform player. In response to the first play start instruction, the media asset is controlled to be restored to the play position before the media asset is exited, and the media asset is played at the play position.

[0123] Exemplarily, if the application module uses old video elements to participate in page layout, before exiting the media asset playback, if the playback status of the media asset is in the playing status, it means that the user is watching the media asset before exiting, and the display device 200 can recreate the playback environment. The display device 200 can recreate the media player and the media playback thread through the browser, wherein the media player can be used to control the media asset playback, and the media playback thread can be used to process the background process of the media asset playback. In addition, the display device 200 can also load the platform player, and based on the recreated media player, the media playback thread and the loaded platform player, generate the first start instruction to notify the platform to start, and control the media asset to return to the playback position before exiting. In this way, by returning to the playback position before exiting, the display device 200 can maintain the continuity of the media asset playback and avoid the user starting to watch first. By recreating the playback environment, the system can manage resources more effectively.

[0124] In some embodiments, the playback status includes a pause status. When the display device 200 determines the playback form of the media asset based on the playback status, in response to exiting the playback of the media asset, the playback state of the media asset is a pause state. It can be determined whether the application module executes the start-up process, and the playback form of the media asset is determined based on the execution result of the start-up process by the application module.

[0125] For example, if the application module uses the old video element to participate in page layout, before exiting the playing of the media asset, the playing state of the media asset is not the playing state, such as the paused state, it can be determined whether the application module actively starts playing the media asset to be played, and further analyzes the playing form of the media asset according to the execution result of the application module on the starting process. In this way, the display device 200 can execute different processes according to whether the application actively starts playing, so as to achieve effective resource management and avoid unnecessary resource consumption.

[0126] In some embodiments, when the display device 200 determines the playback form of the media asset based on the execution result of the start-up process by the application module, it can be divided into the following two situations: when the application module executes the start-up process, the media player and the media playback thread are recreated through the browser, the platform player is loaded, and a first start-up instruction is generated based on the media player, the media playback thread and the platform player; in response to the first start-up instruction, the media asset is controlled to be restored to the playback position before the media asset is exited, and the media asset is played at the playback position; when the application module does not execute the start-up process, the first resource, the second resource and the third resource are kept in a released state.

[0127] For example, if the application module uses the old video element to participate in page layout, before exiting the playback of the media asset, when its playback state is paused, if the application module actively starts the playback, the application module can re-notify the browser to execute the playback process, re-create the media player and media playback thread through the browser, notify the platform to start the playback, and control the media asset to resume the playback position before exiting. Fig.11 , that is, the subsequent process of the playing state before the execution exits. When the application module does not actively execute the start-up process, the browser does not need to recreate the media player, media resources and media playback thread, and only needs to release the media thread resources associated with the old video element. In this way, the display device 200 can decide whether to recreate the playback environment according to the execution result of the application module, which can manage resources more effectively and avoid unnecessary resource occupation and waste.

[0128] That is to say, in the embodiment of the present application, in addition to solving the problem of continuous occupation of the playback thread in the browser affecting system performance, a quick playback resumption function can also be provided to ensure that when playing again, the playback state before exiting can be quickly and accurately restored, while ensuring that media thread resources are reasonably occupied, avoiding the creation and occupation of invalid media thread resources. For low-performance platforms, even after playing multiple videos for a long time, there will be no problem of insufficient playback thread resources.

[0129] It can be seen from the above technical solution that the above embodiment provides a display device 200. In response to the media asset exit playback instruction, the display device 200 removes the media asset tag corresponding to the media asset; generates a playback thread release instruction according to the removal result of the media asset tag; and releases the first resource, the second resource, and the third resource in response to the playback thread release instruction; the first resource is the resource corresponding to the media player that plays the media asset; the second resource is the resource corresponding to the thread for processing the call of the media asset playback interface and event processing; the third resource is the resource corresponding to the platform player of the display device. The display device 200 can release resources through the browser and actively recycle the media playback thread resources to reduce system consumption, improve the system performance of the display device 200, and solve the problem of continuous occupation of the playback thread in the browser affecting system performance.

[0130] Based on the above display device 200, some embodiments of the present application also provide a method for optimizing a browser playback thread, which can be applied to the display device 200 in the above embodiment. In some embodiments, the method may include the following content:

[0131] In response to the media asset's exit playback instruction, remove the media asset tag corresponding to the media asset;

[0132] Generate a playback thread release instruction according to the removal result of the media asset tag;

[0133] In response to the playback thread release instruction, the first resource, the second resource and the third resource are released; the first resource is the resource corresponding to the media player that plays the media asset; the second resource is the resource corresponding to the thread used to process the call of the media asset playback interface and event processing; the third resource is the resource corresponding to the platform player of the display device.

[0134] It can be seen from the above technical solution that the above embodiment provides a method for optimizing the browser playback thread. The method can reduce system consumption and improve the system performance of the display device 200 through the mechanism of releasing resources and actively recovering media playback thread resources through the browser, thereby solving the problem of continuous occupation of the playback thread in the browser affecting system performance.

[0135] The same and similar parts between the various embodiments in this specification can be referenced to each other and will not be described again here.

[0136] Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution in the embodiments of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., and includes a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of various embodiments of the present invention or certain parts of the embodiments.

[0137] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

[0138] For the convenience of explanation, the above description has been made in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the embodiments to the specific forms disclosed above. Based on the above teachings, various modifications and variations can be obtained. The selection and description of the above embodiments are to better explain the principles and practical applications, so that those skilled in the art can better use the embodiments and various different variations of the embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that: include: a display configured to display a user interface; A controller is coupled to the display and is configured to: In response to the media asset's exit playback instruction, remove the media asset tag corresponding to the media asset; Generate a playback thread release instruction according to the removal result of the media asset tag; In response to the playback thread release instruction, releasing the first resource, the second resource and the third resource; The first resource is a resource corresponding to a media player that plays the media asset; the second resource is a resource corresponding to a thread for processing calls to a media asset playback interface and event processing; and the third resource is a resource corresponding to a platform player of a display device.

2. The display device according to claim 1, characterized in that Before removing the media asset tag corresponding to the media asset, the controller is further configured to: Detecting the tag type of the media asset tag; the tag type includes a media asset element tag and a media asset parent element tag; In response to the media asset tag being a media asset element itself, determining that the tag type is a media asset element tag; the media asset element is an element tag corresponding to when the media asset is embedded in a browser; In response to the media asset tag being a parent element of a media asset element, the tag type is determined to be a media asset parent element tag; the parent element is a parent element tag corresponding to when the media asset is embedded in a browser.

3. The display device according to claim 2, characterized in that The controller executes the release of the first resource, the second resource and the third resource in response to the playback thread release instruction, and is specifically configured as follows: In response to the tag type being the media asset element tag, generating a first removal instruction; Removing the media asset element according to the first removal instruction; Generating a first playback thread release instruction according to the removal result of the media asset element; Sending the first playback thread release instruction to a browser module; the browser module is used to manage the playback thread of the browser; The browser module releases the first resource, the second resource and the third resource according to the first playback thread release instruction.

4. The display device according to claim 3, characterized in that The controller executes the release instruction of the playback thread to release the first resource, the second resource and the third resource, and is specifically configured as follows: In response to the tag type being the media asset parent element tag, generating a second removal instruction; Removing the parent element of the media asset element according to the second removal instruction; Generate a second playback thread release instruction according to the removal result of the parent element; Sending the second playback thread release instruction to the browser module; the browser module is used to manage the playback thread of the browser; Through the browser module, the first resource, the second resource and the third resource are released according to the second playback thread release instruction.

5. The display device according to claim 3 or 4, characterized in that: Before releasing the first resource, the second resource and the third resource, the controller is further configured to: Recording the playback status of the media asset; After releasing the first resource, the second resource and the third resource, the controller is further configured to: Obtaining the playback status; After the first resource, the second resource, and the third resource are released, the playback state is kept unchanged.

6. The display device according to claim 2, characterized in that After releasing the first resource, the second resource and the third resource, the controller is further configured to: In response to a replay instruction of the media asset, determining whether the application module re-adds the removed media asset element or the parent element; If the media asset element or the parent element is not added, the playback thread of the media asset to be played is reloaded through the application module, and the playback interface is called through the application module to start playing the media asset to be played; If the media asset element or the parent element is added, the playing state of the media asset before exiting the playing of the media asset is determined, and the playing form of the media asset is determined according to the playing state.

7. The display device according to claim 6, characterized in that The playing state includes a playing state, and the controller determines the playing form of the media asset according to the playing state, and is specifically configured as follows: In response to the playback state of the media asset being the playing state before exiting the playback of the media asset, recreating the media player and the media playback thread through the browser; Loading a platform player, and generating a first start-play instruction based on the media player, the media play thread and the platform player; In response to the first start-play instruction, controlling the media asset to resume the play position before the media asset is exited; The media asset is played at the playback position.

8. The display device according to claim 6, characterized in that The playing state includes a pause state, and the controller determines the playing mode of the media asset according to the playing state, and is specifically configured as follows: In response to the playback state of the media asset being the paused state before exiting the playback of the media asset, determining whether the application module executes the playback start process; The playing form of the media asset is determined according to the execution result of the application module on the starting process.

9. The display device according to claim 6, characterized in that The controller determines the playing mode of the media asset according to the execution result of the application module on the starting process, and is specifically configured as follows: When the application module executes the start-up process, the media player and the media play thread are recreated through the browser, the platform player is loaded, and a first start-up instruction is generated based on the media player, the media play thread and the platform player; In response to the first start-play instruction, controlling the media asset to be restored to the play position before the media asset is exited, and playing the media asset at the play position; When the application module does not execute the start-up process, the first resource, the second resource and the third resource are kept in a released state.

10. A method for optimizing a browser playback thread, applied to a display device according to any one of claims 1 to 9, characterized in that: The method comprises: In response to the media asset's exit playback instruction, remove the media asset tag corresponding to the media asset; Generate a playback thread release instruction according to the removal result of the media asset tag; In response to the playback thread release instruction, the first resource, the second resource and the third resource are released; the first resource is the resource corresponding to the media player that plays the media asset; the second resource is the resource corresponding to the thread used to process the call of the media asset playback interface and event processing; the third resource is the resource corresponding to the platform player of the display device.

Images