Display device and network media resource validity verification method

Abstract

The application provides a display device and a network media resource validity verification method. A candidate media resource address list is obtained in response to a target media search instruction input by a user. A streaming media protocol type corresponding to the candidate media resource address is identified and a verification channel is allocated. Protocol-level validity verification is performed based on the verification channel to obtain a first verification result. Content semantic matching and clarity quality joint verification are performed in the case where the first verification result is a verification pass to obtain a second verification result. Finally, a comprehensive ranking of the candidate media resource addresses is performed based on the content matching clarity and the clarity matching information to obtain a recommendation list. Through a two-layer progressive verification system, the actual validity of the network media resource can be actively verified. The authenticity and accuracy of the searched media resource are ensured from multiple dimensions of protocol-level castability, content semantic matching and clarity quality, the invalid resource misrecommendation rate is reduced, and the user media content search efficiency and experience are improved.

Description

Technical Field

[0001] This application relates to the field of display device technology, and in particular to a method for validating the validity of display devices and network media resources. Background Technology

[0002] Display devices are intelligent devices capable of presenting a user interface and supporting user interaction. Taking smart TVs as an example, smart TVs are television products based on Internet application technology, possessing an open operating system and chip, an open application platform, and enabling two-way human-computer interaction. They integrate multiple functions such as audio-visual entertainment and data to meet diverse and personalized user needs. Display devices can present different media asset recommendation interfaces, which may include multiple media asset options for users to select and play.

[0003] The display device has media resource search capabilities, allowing users to display desired media content through simple interactive commands. The device uses webpage metadata matching methods, such as keyword matching and semantic matching, to determine the webpage link corresponding to the interactive command. Users need to manually try playing each link to confirm the authenticity and validity of the media resource at that address.

[0004] However, since there is no necessary causal relationship between webpage metadata and the actual state of media resources, the media resources corresponding to the webpage metadata may not be the media content that users expect to search for. For example, different resolutions, different media content, or broken webpage links may cause users to have to repeatedly try clicking multiple webpage links to find the media content they actually want to watch, reducing the efficiency and accuracy of media content search and lowering the user experience. Summary of the Invention

[0005] This application provides a method for validating the validity of display devices and network media resources, in order to solve the problem that the media resource addresses obtained by existing display devices based on webpage metadata matching methods are incorrect, causing users to have to repeatedly try multiple webpage links to find media content.

[0006] In a first aspect, some embodiments of this application provide a display device, including: The monitor is configured to display the user interface; The controller is configured as follows: In response to a user-inputted target media asset search command, a list of candidate media resource addresses is obtained, wherein the list of candidate media resource addresses includes at least one candidate media resource address; Identify the streaming media protocol type corresponding to the candidate media resource address based on the address characteristics of the candidate media resource address; Based on the streaming media protocol type, a verification channel is assigned to the candidate media resource address; Based on the verification channel, protocol-level validity verification is performed on the candidate media resource addresses to obtain the first verification result. Different streaming media protocol types correspond to different protocol-level validity verification methods. If the first verification result is successful, a joint verification of content semantic matching and clarity quality is performed on the candidate media resource address to obtain a second verification result, which includes content matching confidence and clarity matching information. The control display shows a recommended list on the user interface, which is obtained by comprehensively ranking the candidate media resource addresses based on content matching confidence and resolution matching information.

[0007] The above technical solution has the following advantages or beneficial effects: By constructing a two-layer progressive verification system—one for protocol-level validity verification and the other for joint verification of content semantic matching and clarity quality—the system substantially verifies candidate media resource addresses from multiple dimensions, including protocol-level playability, content semantic matching, and clarity quality. This accurately identifies the true validity and content matching degree of media resources, significantly reduces the false recommendation rate of invalid resources, improves the accuracy and efficiency of media content search, and enhances user experience.

[0008] In some embodiments of this application, the controller executes a target media resource search command in response to user input to obtain a list of candidate media resource addresses, specifically configured as follows: By parsing the intent of the target media asset search command through a large language model, structured search elements are obtained. The structured search elements include content identifiers, clarity constraints, content types, and additional constraints. Based on content identifiers, clarity constraints, content types, and additional constraints, send differentiated query requests to multiple retrieval sources and receive webpage data returned by multiple retrieval sources based on the differentiated query requests; Perform multi-layer deep parsing on the webpage data to extract the media resource addresses of the webpage data; The media resource addresses are filtered, deduplicated, and aggregated to obtain a list of candidate media resource addresses.

[0009] The above technical solution has the following advantages or beneficial effects: by parsing the user's natural language input through a large language model, extracting structured search elements, and sending differentiated query requests to multiple search sources based on the search elements, it is possible to obtain more comprehensive web page data from multiple search sources. Furthermore, by extracting media resource addresses from the web page data through multi-layer deep parsing, the coverage and accuracy of candidate media resource addresses are improved.

[0010] In some embodiments of this application, the controller performs multi-layer deep parsing on the webpage data to extract the media resource address of the webpage data, specifically configured as follows: Traverse the document object model tree corresponding to the webpage data, locate the target tag in the document object model tree, obtain the source address attribute value of the target tag, and obtain the first address set; The system loads web page data using a preset browser engine and executes the page script contained in the web page data to extract the address of the first media resource based on the page script, and obtains the address of the second media resource after executing the page script. Perform regular expression pattern scanning on the script content and configuration data text embedded in the web page data to extract the third media resource addresses that match the preset media address pattern; The first address set, the first media resource address, the second media resource address, and the third media resource address are merged to obtain the media resource address.

[0011] The above technical solutions have the following beneficial effects or advantages: through multi-layer deep parsing using three methods—document object model tree traversal, page script execution interception, and regular expression pattern scanning—media resource addresses can be extracted from different levels of a webpage, improving the comprehensiveness and accuracy of media resource address extraction.

[0012] In some embodiments of this application, the controller loads web page data through a preset browser engine and executes the page script contained in the web page data to extract a first media resource address based on the page script, and obtains a second media resource address after executing the page script. Specifically, it is configured as follows: Load web page data using a preset browser engine and execute the page scripts contained in the web page data, while intercepting network requests generated during the execution of the page scripts; Extract the address of the first media resource from the network request; Read the global configuration object generated after the page script is executed, and extract the address of the second media resource from the global configuration object.

[0013] The above technical solutions have the following beneficial effects or advantages: by intercepting network requests generated during the execution of page scripts to extract media resource addresses, and by reading the global configuration object generated after the execution of page scripts to extract media resource addresses, it is possible to capture dynamically loaded and runtime generated media resource addresses, thereby improving the depth and coverage of media resource address extraction.

[0014] In some embodiments of this application, the controller performs the allocation of verification channels for candidate media resource addresses based on the streaming media protocol type, specifically configured as follows: When the native playback channel supports streaming media protocol types, the verification channel for candidate media resource addresses is assigned to the native playback channel. The native playback channel performs verification processing on the candidate media resource addresses through the display device's system native multimedia framework. When the native playback channel does not support streaming media protocol types, the verification channel for candidate media resource addresses is downgraded and assigned to the script-driven playback channel. The script-driven playback channel performs verification processing on candidate media resource addresses by loading a script-driven media playback component in a sandboxed processing environment.

[0015] The above technical solutions have the following beneficial effects or advantages: Based on the streaming media protocol type, candidate media resource addresses are preferentially allocated to the native playback channel for verification, and automatically downgraded to the script-driven playback channel when not supported, thus ensuring that media resources of different protocol types can be effectively verified, improving verification coverage and verification efficiency.

[0016] In some embodiments of this application, the controller performs protocol-level validity verification on candidate media resource addresses based on a verification channel to obtain a first verification result, specifically configured as follows: When the streaming media protocol type is a direct link protocol type, a range transmission request is initiated for the candidate media resource address to obtain the data content of the media resource file corresponding to the candidate media resource address with the first preset number of bytes, and a container format validity check is performed on the data content with the first preset number of bytes to obtain the container check result; When the streaming media protocol type is any one of the first adaptive bitrate protocol type, the second adaptive bitrate protocol type, or the third adaptive bitrate protocol type, a structural validity check is performed on the first manifest file corresponding to the candidate media resource address, and a sampling availability check is performed on the media segment corresponding to the candidate media resource address. A first verification result is generated based on at least one of the following: container inspection results, structural validity check, and sampling availability check.

[0017] The above technical solution has the following beneficial effects or advantages: This embodiment implements differentiated protocol-level validity verification processes for direct-link protocols and different types of adaptive bitrate protocols. Validity verification can be completed by acquiring only a small amount of data, without needing to download the complete media resource file, significantly reducing the amount of data transmitted and the verification time, and improving verification efficiency. It also improves the accuracy and reliability of protocol-level validity verification.

[0018] In some embodiments of this application, if the first verification result is successful, the controller performs joint verification of content semantic matching and clarity quality on the candidate media resource address to obtain a second verification result, specifically configured as follows: If the first verification result is successful, the manifest file and / or container file corresponding to the candidate media resource address are parsed to obtain the key image frames and resolution information of the media resource file corresponding to the candidate media resource address. Input the key image frame and the target media asset lookup instruction into the multimodal large model, and obtain the content matching confidence between the key image frame and the target media asset lookup instruction output by the multimodal large model; The resolution information is compared with the clarity requirements in the target media asset search command to obtain clarity matching information; A second verification result is generated based on the content matching confidence and clarity matching information.

[0019] The above technical solutions have the following beneficial effects or advantages: by inputting key image frames and user search instructions into a multimodal large model for content semantic matching verification, and by comparing and verifying resolution information with user clarity requirements, the content matching degree and clarity compliance of media resources are verified simultaneously, thereby improving the accuracy of finding media resources and the clarity compliance rate.

[0020] In some embodiments of this application, before the controller controls the display to show the recommended list obtained by performing a comprehensive ranking of candidate media resource addresses based on content matching confidence and clarity matching information on the user interface, it is further configured to: The first and second verification results are input into the large language model in a structured data format, so that the large language model can perform a comprehensive score on the candidate media resource addresses based on protocol-level validity, content semantic matching and clarity quality, and obtain the comprehensive score result. Based on the comprehensive scoring results, the candidate media resource addresses are sorted and filtered to obtain a recommended list.

[0021] The above technical solution has the following beneficial effects or advantages: by inputting the two-layer verification results into a large language model in a structured data format for comprehensive scoring and sorting filtering, the ranking rationality of the recommendation list and user satisfaction are improved.

[0022] In some embodiments of this application, if the first verification result is that the verification fails, the controller is further configured to: Record the search source corresponding to the candidate media resource address; The system sends an invalid address message to the corresponding search source and removes the candidate media resource address from the candidate media resource address list.

[0023] The above technical solution has the following beneficial effects or advantages: when the first verification result is that the verification fails, the retrieval source corresponding to the candidate media resource address is recorded and the corresponding retrieval source is fed back with the prompt message that the address is invalid. At the same time, the invalid address is removed from the candidate media resource address list to avoid repeated recommendation of invalid addresses in the future and improve the continuous optimization capability of the media resource recommendation system.

[0024] Secondly, some embodiments of this application provide a method for verifying the validity of network media resources, applied to the display device provided in the first aspect, the method comprising: In response to a user's input command to search for a target media resource, a list of candidate media resource addresses is obtained, wherein the list of candidate media resource addresses includes at least one candidate media resource address; Identify the streaming media protocol type corresponding to the candidate media resource address based on the address characteristics of the candidate media resource address; Based on the streaming media protocol type, a verification channel is assigned to the candidate media resource address; Based on the verification channel, protocol-level validity verification is performed on the candidate media resource addresses to obtain the first verification result. Different streaming media protocol types correspond to different protocol-level validity verification methods. If the first verification result is successful, a joint verification of content semantic matching and clarity quality is performed on the candidate media resource address to obtain a second verification result, which includes content matching confidence and clarity matching information. The control display shows a recommended list on the user interface, which is obtained by comprehensively ranking the candidate media resource addresses based on content matching confidence and resolution matching information.

[0025] As can be seen from the above technical solutions, some embodiments of this application provide a method for validating the validity of display devices and network media resources. This method obtains a list of candidate media resource addresses in response to a user-inputted target media resource search command, identifies the streaming media protocol type corresponding to the candidate media resource addresses and allocates a verification channel, performs protocol-level validity verification based on the verification channel to obtain a first verification result, and performs joint verification of content semantic matching and clarity quality to obtain a second verification result if the first verification result is successful. Finally, a comprehensive ranking of the candidate media resource addresses is performed based on content matching confidence and clarity matching information to obtain a recommendation list. This application, through a two-layer progressive verification system, ensures the authenticity and accuracy of the searched media resources from multiple dimensions, including protocol-level playability, content semantic matching, and clarity quality, reducing the false recommendation rate of invalid resources and improving the efficiency and experience of users searching for media content. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of this application 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 of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application; Figure 2 This is a schematic diagram of the hardware configuration of a display device provided in some embodiments of this application; Figure 3 This is a schematic diagram of the software configuration of a display device provided in some embodiments of this application; Figure 4 A flowchart illustrating a method for validating the validity of network media resources performed by a display device, provided in some embodiments of this application; Figure 5 Timing diagrams of a network media resource validity verification method performed by a display device according to some embodiments of this application; Figure 6 A flowchart illustrating how a display device obtains a list of candidate media resource addresses, provided in some embodiments of this application; Figure 7 A flowchart illustrating the multi-layer depth parsing process provided in some embodiments of this application for a display device. Figure 8 A flowchart illustrating the process of a display device executing page script parsing to extract media resource addresses, provided in some embodiments of this application; Figure 9 A flowchart illustrating the allocation of verification channels to a display device provided in some embodiments of this application; Figure 10 A flowchart illustrating the protocol-level validity verification performed by a display device, provided in some embodiments of this application; Figure 11 A flowchart illustrating the joint verification of content semantic matching and resolution quality performed by a display device, provided in some embodiments of this application; Figure 12 A flowchart illustrating the comprehensive scoring and ranking process for display devices provided in some embodiments of this application; Figure 13 This is a flowchart illustrating the process of handling invalid media resource addresses in a display device according to some embodiments of this application. Detailed Implementation

[0028] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application as detailed in the claims.

[0029] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0030] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.

[0031] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0032] The term "module" refers to any known or subsequently 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.

[0033] In this embodiment, the display device 200 generally refers to a device with screen display and data processing capabilities. For example, the display device 200 includes, but is not limited to, smart TVs, mobile terminals, computers, monitors, advertising screens, wearable devices, virtual reality devices, augmented reality devices, etc.

[0034] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application. For example... Figure 1 As shown, a user can operate the display device 200 via touch operation, a mobile terminal 300, and a control device 100. The control device 100 receives user input commands and converts them into control commands that the display device 200 can recognize and respond to. For example, the control device 100 can be a remote control, a stylus, a gamepad, etc.

[0035] The mobile terminal 300 can function as a control device for human-computer interaction between the user and the display device 200. It can also function as a communication device for establishing a communication connection with the display device 200 and exchanging data. In some embodiments, the mobile terminal 300 can have software applications installed on it and communicate with the display device 200 via network communication protocols to achieve one-to-one control and data communication. Furthermore, it can transmit audio and video content displayed on the mobile terminal 300 to the display device 200 for synchronized display.

[0036] 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 that controls the display device 200.

[0037] like Figure 1 The diagram also shows that the display device 200 communicates with the server 400 via various communication methods. This allows the display device 200 to communicate via a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0038] Display device 200 can provide broadcast television reception function, and can also be equipped with intelligent network television function that provides computer support function, including but not limited to network television, smart television, Internet Protocol television (IPTV), etc.

[0039] Figure 2 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of display device 200.

[0040] 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 280.

[0041] In some embodiments, detector 230 is used to acquire signals from the external environment or to interact with the outside world. For example, detector 230 includes a light receiver, a sensor for acquiring ambient light intensity; or, detector 230 includes an image acquisition device, such as a camera, which can be used to acquire external environmental scenes, user attributes, or user interaction gestures; or, detector 230 includes a sound acquisition device, such as a microphone, for receiving external sounds.

[0042] In some embodiments, the display 260 includes display function components for presenting images and driving components for driving image display. The display 260 is used to receive and display image signals output from the controller 250. For example, the display 260 can be used to display video content, image content, menu control interface components, and user control UI interfaces, etc.

[0043] In some embodiments, the communication device 220 is a component used to communicate with external devices or the server 400 according to various communication protocol types. The display device 200 may have multiple communication devices 220 depending on the supported communication methods. For example, when the display device 200 supports wireless network communication, it may have a communication device 220 with WiFi functionality. When the display device 200 supports Bluetooth connectivity, it needs to have a communication device 220 with Bluetooth functionality.

[0044] The communication device 220 enables the display device 200 to communicate with external devices or the server 400 via wireless or wired connections. Wired connections utilize data cables, interfaces, or other components to connect the display device 200 to external devices. Wireless connections utilize wireless signals or wireless networks. The display device 200 can directly establish a connection with external devices or indirectly through gateways, routers, or other connection devices.

[0045] 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 to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in memory. The controller 250 controls the overall operation of the display device 200.

[0046] In some embodiments, the controller 250 and the tuner 210 may be located in different separate devices, that is, the tuner 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.

[0047] In some embodiments, a user can input user commands through a graphical user interface (GUI) displayed on a display 260, and the user input interface 280 receives the user input commands through the graphical user interface (GUI).

[0048] In some embodiments, the audio output device 270 can be a built-in speaker of the display device 200 or an external audio output device connected to the display device 200. For the external audio output device connected to the display device 200, the display device 200 may also be provided with an external audio output terminal, through which the audio output device can be connected to the display device 200 to output sound from the display device 200.

[0049] In some embodiments, the user input interface 280 can be used to receive instructions from user input.

[0050] To enable user interaction, in some embodiments, the display device 200 may run an operating system. The operating system is a computer program used to manage and control the hardware and software resources of 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 it can provide a user interface by running an application. The operating system also allows users to interact with the display device 200.

[0051] It should be noted that the operating system can be a native operating system based on a specific operating platform, a third-party operating system that is deeply customized based on a specific operating platform, or an independent operating system specifically developed for display devices.

[0052] An operating system can be divided into different modules or levels based on the functions it implements, for example... Figure 3 As shown, in some embodiments, the system is divided into three layers, from top to bottom: the Applications layer (referred to as the "application layer"), the middleware layer, and the hardware layer.

[0053] In some embodiments, the application layer provides services and interfaces for applications, enabling the display device 200 to run applications and interact with the user based on the applications. The application layer may contain at least one application, which may be a built-in Windows program, system settings program, or clock program of the operating system; or it may be an application developed by a third-party developer. In specific implementations, the application packages in the application layer are not limited to the examples above.

[0054] The framework layer provides application programming interfaces (APIs) and a programming framework for applications. The application framework layer includes predefined functions. It acts as a central processing unit, determining the actions taken by applications within the application layer. Through the API, applications can access system resources and obtain system services during execution.

[0055] like Figure 3 As shown, Figure 3 Provided for some embodiments of this application Figure 1 The diagram shows the software configuration of the display device. In some embodiments, the system of the display device 200 can be divided into three layers, from top to bottom: the application layer, the middleware layer, and the hardware layer.

[0056] The application layer mainly includes commonly used applications on TVs, as well as the application framework. The commonly used applications are mainly browser-based applications, such as HTML5 apps, and native apps. An application framework is a complete program model that has all the basic functions required by standard application software, such as file access, data exchange, and the user interface for these functions (toolbar, status bar, menu, dialog box).

[0057] Native apps can support online or offline access, push notifications, or access to local resources.

[0058] The middleware layer includes various television protocols, multimedia protocols, and system components. Middleware can use the basic services (functions) provided by system software to connect different parts of application systems or different applications on the network, achieving resource sharing and function sharing.

[0059] 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, with the specific logic implemented by each individual chip. Drivers mainly include: audio drivers, display drivers, Bluetooth drivers, camera drivers, Wi-Fi drivers, USB drivers, HDMI drivers, sensor drivers (such as fingerprint sensors, temperature sensors, pressure sensors, etc.), and power drivers.

[0060] It should be noted that the above examples are merely a simple division of operating system functions and do not limit the specific form of the operating system of the display device 200 in this application embodiment. Depending on the function of the display device, the type of operating system, and other factors, the number of levels and the specific level type of the operating system may be expressed in other forms.

[0061] In some embodiments, the display device 200 can search for and display media resources to the user based on the user's input media resource search command, thereby satisfying the user's need to view media resources. However, in the scenario of searching for media resources, the display device 200 uses a matching method based on webpage metadata, such as keyword matching and semantic matching, to determine the webpage link corresponding to the interaction command in the media database, and then displays the webpage link on the user interface through the display 260 to provide it to the user.

[0062] Users need to manually click on webpage links and attempt playback to confirm the authenticity of the media resource corresponding to that address. Since there is no necessary causal relationship between webpage metadata and the actual state of the media resource, the media resource corresponding to the webpage metadata may not be the content the user expects to find. For example, different resolutions, different media content, or broken webpage links may cause users to repeatedly click on multiple webpage links to find the media content they actually want to watch, reducing the efficiency and accuracy of media content search and degrading the user experience.

[0063] Based on the above technical problems, some embodiments of this application provide a display device 200, which includes at least a display 260 and a controller 250, wherein the display 260 is configured to display a user interface, and the controller 250 is configured to perform the following network media resource validity verification method.

[0064] In some embodiments, the display device 200 integrates an AI Agent system. An AI Agent is an intelligent agent system capable of autonomously sensing the environment, understanding user intent, planning tasks, and scheduling multiple tools to collaboratively complete complex tasks. In media asset search scenarios, the AI ​​Agent can obtain a list of candidate media resource addresses through a search engine or media asset library.

[0065] In some embodiments, the AI ​​Agent system of the display device 200 adopts a layered architecture design, comprising the following core layers from top to bottom: a user interaction layer, an Agent core layer, a resource discovery module, a protocol identification and adaptation layer, an active verification engine, a dual-channel adaptation layer, and a result presentation layer. The user interaction layer receives media asset search instructions (voice or text) input by the user, understands the user's intent, parses key elements in the media resource search request (e.g., media asset name, resolution, preferences, etc.), and transmits the parsing results to the Agent core layer. The Agent core layer is the central scheduling and control unit of the AI ​​Agent, responsible for task decomposition, process orchestration, and coordinated scheduling of various modules, driving the execution of the entire verification process. After receiving the key elements of the media asset search instruction, the Agent core layer sends a search task to the media asset discovery module. The resource discovery module interfaces with search engines, media asset libraries, and third-party APIs, and executes the search process according to the search task sent by the Agent core layer to obtain a list of candidate media resource addresses. The protocol identification and adaptation layer automatically identifies the streaming media protocol type of each candidate media resource address and selects the most suitable verification channel for the candidate media resource address based on the streaming media protocol type and the device capabilities of the display device 200. The proactive verification engine performs a two-layer progressive verification process (protocol-level validity verification, content semantic matching, and clarity joint verification). A dual-channel adaptation layer unifies and abstracts the native playback channel and the script-driven playback channel, providing a unified verification interface for the proactive verification engine. The results presentation layer returns the final recommendation list to the user in natural language. Data is transferred between layers through standardized interfaces; upper layers send instructions to lower layers, and lower layers return verification results to upper layers, forming a complete closed-loop verification chain.

[0066] The following describes in detail, with reference to the accompanying drawings, the process by which the display device 200 provided in the embodiments of this application performs network media resource validity verification.

[0067] Figure 4 This is a flowchart illustrating a method for verifying the validity of network media resources performed by a display device according to some embodiments of this application. Figure 5 This is a timing diagram of a method for verifying the validity of network media resources performed by a display device according to some embodiments of this application.

[0068] See Figure 4 and Figure 5 The controller 250 is configured to perform the following steps: S401: In response to the user's input of a target media asset search command, obtain a list of candidate media resource addresses.

[0069] In some embodiments, the user initiates a target media asset search command to the AIAgent of the display device 200 via voice input or text input. The target media asset search command is a media resource search request expressed by the user in natural language. For example, if the user says to the voice assistant of the display device 200, "Find me the 4K source of ABC (media asset name)," this voice command is the target media asset search command.

[0070] Controller 250 can receive target media asset search instructions through the user interaction layer, and in response, parse key elements and transmit the parsing results to the Agent core layer. Upon receiving the parsing results, the Agent core layer issues a search task to the resource discovery module, thereby obtaining a list of candidate media resource addresses. The candidate media resource address list includes at least one candidate media resource address, each of which is a network address that may contain the media resource the user expects, including but not limited to a Uniform Resource Locator (URL).

[0071] S402: Identify the streaming media protocol type corresponding to the candidate media resource address based on the address characteristics of the candidate media resource address.

[0072] In some embodiments, the controller 250 receives a list of candidate media resource addresses through a protocol identification and adaptation layer, and identifies the streaming media protocol type for each candidate media resource address in the list. The streaming media protocol type refers to the protocol standard used for media resource transmission in the network; different streaming media protocol types have different manifest formats, fragmentation methods, and verification mechanisms. Address characteristics include at least one of the following: the Uniform Resource Locator (URL) suffix characteristic of the candidate media resource address, the Content-Type (CMT) response header characteristic, and the response body content characteristic.

[0073] For example, streaming media protocol types may include HLS (HTTP Live Streaming), DASH (Dynamic Adaptive Streaming over HTTP), MSS (Microsoft Smooth Streaming), and mp4 direct linking protocols, etc.

[0074] Different streaming media protocol types correspond to different address characteristics. For example, for the HLS protocol, candidate media resource addresses end with .m3u8, or the Content-Type in the response header is application / vnd.apple.mpegurl or application / x-mpegURL; for the DASH protocol, candidate media resource addresses end with .mpd, or the Content-Type in the response header is application / dash+xml; for the MSS protocol, the path of the candidate media resource address contains / Manifest and the Content-Type is text / xml or application / xml, and the response body contains the SmoothStreamingMedia tag; for the mp4 direct link protocol, candidate media resource addresses end with .mp4, or the Content-Type is video / mp4. The controller 250 identifies the protocol type of each candidate media resource address based on these address characteristics and labels each candidate media resource address with the corresponding streaming media protocol type.

[0075] S403: Assign a verification channel to the candidate media resource address based on the streaming media protocol type.

[0076] In some embodiments, the controller 250 assigns a corresponding verification channel to each candidate media resource address based on the identified streaming media protocol type. The verification channel is a processing channel used to perform validity verification on the candidate media resource addresses, including a native playback channel and a script-driven playback channel. The native playback channel performs verification processing on the candidate media resource addresses through the system's native multimedia framework of the display device 200, while the script-driven playback channel performs verification processing on the candidate media resource addresses by loading a script-driven media playback component in a sandboxed processing environment.

[0077] In one implementation, controller 250 first determines whether the native playback channel supports the streaming media protocol type corresponding to the candidate media resource address. Standard mp4 direct links and HLS / DASH addresses natively supported by the system are assigned to the native playback channel for verification; HLS / DASH / MSS addresses requiring playback in the MSE environment using JavaScript are assigned to the script-driven playback channel for verification. This dual-channel unified verification architecture ensures that media resources of different protocol types can be effectively verified.

[0078] S404: Based on the verification channel, perform protocol-level validity verification on the candidate media resource address to obtain the first verification result.

[0079] In some embodiments, the controller 250 performs protocol-level validity verification on candidate media resource addresses based on the allocated verification channel through an active verification engine, and obtains a first verification result.

[0080] Protocol-level validity verification is the first layer of verification, used to verify whether the media resource corresponding to the candidate media resource address actually exists and can be parsed and played. Different streaming media protocol types correspond to different protocol-level validity verification methods, and the controller 250 adopts the corresponding verification method according to the streaming media protocol type corresponding to the candidate media resource address.

[0081] S405: If the first verification result is successful, perform joint verification of content semantic matching and clarity quality on the candidate media resource address to obtain the second verification result.

[0082] In some embodiments, for candidate media resource addresses whose first verification result is successful, the controller 250 performs a second layer of verification through an active verification engine, namely, joint verification of content semantic matching and clarity quality, to obtain a second verification result. The second verification result includes content matching confidence and clarity matching information. The content semantic matching verification is used to determine whether the media resource content corresponding to the candidate media resource address is consistent with the content expected by the user's input target media asset search instruction. For example, whether the media resource content corresponding to the candidate media resource address corresponds to "ABC" in the target media asset search instruction.

[0083] The controller 250 can output a content matching confidence score based on the consistency between the media resource content and the content expected by the target media asset search instruction. The content matching confidence score is positively correlated with the degree of consistency; that is, the higher the confidence score, the higher the consistency, and vice versa. Clarity quality verification is used to determine whether the clarity of the media resource content meets the user's clarity requirements. For example, whether the clarity of the media resource content corresponding to the candidate media resource address corresponds to the "4K" clarity of the target media asset search instruction, thus obtaining clarity matching information, including both matching and non-matching results.

[0084] S406: Control the display to show a recommended list obtained by performing a comprehensive ranking of candidate media resource addresses based on content matching confidence and resolution matching information on the user interface.

[0085] In some embodiments, the controller 250 inputs the first and second verification results into a large language model in a structured data format. The large language model performs a comprehensive scoring on the candidate media resource addresses based on protocol-level validity, content semantic matching, and clarity quality, obtaining a comprehensive score result. The controller 250 sorts and filters the candidate media resource addresses according to the comprehensive score result, obtaining a recommendation list, and controls the display 260 to display the recommendation list on the user interface. Thus, media resource addresses with playable protocols, high content matching confidence, and matching clarity information are placed in a priority position in the recommendation list, allowing users to intuitively see the media resource addresses that best match the target media asset search instructions. Furthermore, each recommended item in the recommendation list includes information such as the media resource address, verification conclusion, clarity annotation, and playability description, for users to refer to when selecting playback.

[0086] Based on the above technical solution, a list of candidate media resource addresses is obtained in response to the user's input target media asset search command. The streaming media protocol type corresponding to the candidate media resource address is identified and a verification channel is allocated. Based on the verification channel, protocol-level validity verification is performed to obtain the first verification result. If the first verification result is successful, content semantic matching and clarity quality joint verification are performed to obtain the second verification result. Finally, the candidate media resource addresses are comprehensively ranked according to the content matching confidence and clarity matching information to obtain the recommendation list. This achieves the goal of ensuring the authenticity and accuracy of media resource search from multiple dimensions such as protocol-level playability, content semantic matching, and clarity quality, reducing the false recommendation rate of invalid resources, and improving the efficiency and experience of users in searching for media content.

[0087] Figure 6 This is a flowchart illustrating how a display device obtains a list of candidate media resource addresses, as provided in some embodiments of this application.

[0088] See Figure 6 In some embodiments, the controller 250 performing step S401 may include the following steps: S601: The intent of the target media asset search command is parsed through a large language model to obtain structured search elements.

[0089] In some embodiments, the controller 250 sends the user's input target media asset search instruction to a Large Language Model (LLM). The LLM uses its natural language understanding capabilities to parse the user's input and extract structured search elements. These structured search elements are key information elements contained in the user's search instruction, including content identifiers, resolution constraints, content type, and additional constraints. Content identifiers include film titles (e.g., "ABC"), alternative names (e.g., "abc"), series names (e.g., "ABC2"), etc. Resolution constraints include 4K (3840×2160), 1080P, 720P, etc. Content types include movies, TV series, documentaries, short videos, etc. Additional constraints include year, language (Chinese dubbing or original audio), director, and lead actors, etc.

[0090] In one implementation, the large language model further categorizes user query intent, distinguishing between exact search (known title) and discovery (browsing by genre or topic). The extraction of structured search elements enables subsequent search requests to be more precise and differentiated, providing a foundation for multi-source concurrent retrieval.

[0091] In some embodiments, the large language model can be deployed on the local storage of the display device 200, for example, in the memory of the display device 200, to improve the speed of calling the large language model and improve the efficiency of execution intent parsing; the large language model can also be deployed on a cloud server to provide more accurate structured retrieval elements through the powerful computing power of the cloud.

[0092] S602: Based on content identifiers, clarity constraints, content types, and additional constraints, send differentiated query requests to multiple retrieval sources and receive webpage data returned by multiple retrieval sources based on the differentiated query requests.

[0093] In some embodiments, the controller 250 constructs differentiated query strings for different retrieval sources based on content identifiers, clarity constraints, content types, and additional constraints extracted from a large language model, thereby sending differentiated query requests to multiple retrieval sources instead of using a unified query. The display device 200 may include multiple retrieval sources; for example, multiple retrieval sources may include general search engines, vertical video search platforms, the display device 200's local media asset library, and third-party video aggregation sites, etc.

[0094] For general search engines, controller 250 constructs natural language query strings, such as "{movie title} {resolution} online streaming source", and sends a query request to the general search engine using these natural language query strings. For vertical video search platforms, controller 250 constructs technology-oriented query strings, such as "{movie title} {resolution} m3u8 mp4 online", and sends a query request to the vertical video search platform using these technology-oriented query strings. For proprietary media asset libraries, controller 250 constructs structured API query parameters, such as {title:\"ABC (movie title)\", resolution:\"4K\", type:\"movie\"}, and sends a query request to the proprietary media asset library using these structured API query parameters. For third-party video aggregation sites, controller 250 constructs site-adaptive query strings, such as "{movie title}{year} free online viewing", and sends a query request to the third-party video aggregation site using these site-adaptive query strings.

[0095] The controller 250 sends the constructed query string concurrently to multiple search sources in a differentiated query request manner. The multiple search sources independently return the result page HTML (i.e., web page data). The controller 250 waits for all search sources to return web page data in parallel, instead of serial polling, thereby improving search efficiency.

[0096] S603: Perform multi-level deep parsing on the webpage data to extract the media resource addresses of the webpage data.

[0097] In some embodiments, the controller 250 performs multi-level deep parsing on web page data to extract media resource addresses from different levels of the web page data. Multi-level deep parsing includes a three-level parsing strategy: document object model tree traversal extraction, page script execution interception extraction, and regular expression pattern scanning extraction. This strategy enables the extraction of media resource addresses from different levels of web page data, such as HTML tags, dynamically loaded JavaScript, and embedded script configurations.

[0098] S604: Perform filtering, deduplication, and aggregation on the media resource addresses to obtain a list of candidate media resource addresses.

[0099] In some embodiments, the raw media resource address list extracted from multiple webpage data from multiple retrieval sources contains a large amount of noise. To improve the accuracy of candidate media resource addresses, the controller 250 performs fine-grained processing on the media resource addresses. Filtering includes excluding non-media URLs such as image URLs (.jpg / .png / .webp), CSS / JS files, and ad tracking URLs. Deduplication includes precise deduplication after URL standardization (unifying the protocol from HTTP to HTTPS, removing irrelevant query parameters, and unifying the domain name format), and fuzzy deduplication of CDN mirror URLs of the same domain. Aggregation includes classification and tagging by protocol type and source tracing records. The final output is a structured candidate media resource address list, where each entry includes the URL, protocol type (preliminary inference), source webpage, and confidence score.

[0100] By performing filtering, deduplication, and aggregation on media resource addresses, it is possible to reduce the number of media resource addresses in the original media resource addresses that are irrelevant to the target media resource search instruction, thereby obtaining a list of candidate media resource addresses.

[0101] The above technical solutions have the following beneficial effects or advantages: by parsing the user's natural language input through a large language model, extracting structured search elements, and sending differentiated query requests to multiple search sources based on the search elements, more comprehensive web page data can be obtained from multiple search sources. Furthermore, by extracting media resource addresses from the web page data through multi-layer deep parsing, the coverage and accuracy of candidate media resource addresses are improved.

[0102] Figure 7 A flowchart illustrating the multi-layer depth parsing process performed by a display device according to some embodiments of this application.

[0103] See Figure 7 In some embodiments, the controller 250 performing step S603 may include the following steps: S701: Traverse the document object model tree corresponding to the webpage data, locate the target tag in the document object model tree, obtain the source address attribute value of the target tag, and obtain the first address set.

[0104] In some embodiments, the controller 250 traverses the Document Object Model (DOM) tree corresponding to the webpage data. The DOM tree is a structured representation of the webpage's HTML document, organizing the various element nodes in the webpage data into a tree structure. The controller 250 traverses the DOM tree, locating target tags, including HTML tags related to media resources such as the video tag, the source sub-tag, and the iframe tag. For each located target tag, the controller 250 obtains its source address attribute value (such as the src attribute value) and summarizes the extracted source address attribute values ​​into a first address set.

[0105] The first address set is the set of media resource addresses extracted by traversing the document object model tree. It is the most direct extraction method. For some web page data, the URLs of media resource files may not be directly exposed in the HTML. Therefore, the first address set may only contain some media resource addresses.

[0106] S702: Load web page data using a preset browser engine and execute the page script contained in the web page data to extract the address of the first media resource based on the page script, and obtain the address of the second media resource after executing the page script.

[0107] In some embodiments, the controller 250 loads web page data using a preset browser engine (such as a headless browser) and executes the JavaScript page scripts contained in the web page data. The preset browser engine is a headless browser component capable of loading web pages in the background and executing the JavaScript code within them, simulating the rendering behavior of a user's browser. By executing the page scripts, the controller 250 can extract a first media resource address based on the page scripts, and obtain a second media resource address after executing the page scripts, such as a media resource address dynamically generated and loaded by JavaScript. The first media resource address extracted based on the page scripts refers to the media resource address obtained by intercepting network requests during the execution of the page scripts; the second media resource address obtained after executing the page scripts refers to the media resource address read from the global configuration object generated after the page scripts are executed.

[0108] S703: Perform regular expression pattern scanning on the script content and configuration data text embedded in the web page data to extract the third media resource address that matches the preset media address pattern.

[0109] In some embodiments, the controller 250 performs regular expression pattern scanning on the content of script tags embedded in the web page data and the JSON configuration data text. Regular expression pattern scanning uses a preset media address pattern (regular expression) to match the text content and extract address strings that match the media address pattern. The controller 250 uses the matched address strings as the address of a third media resource. The extracted address strings differ depending on the streaming media protocol type.

[0110] S704: Merge the first address set, the first media resource address, the second media resource address, and the third media resource address to obtain the media resource address.

[0111] In some embodiments, the controller 250 merges the first set of addresses extracted by traversing the document object model tree, the first media resource addresses extracted by intercepting page script execution, the second media resource addresses extracted by reading the global configuration object, and the third media resource addresses extracted by scanning the regular expression pattern to obtain a complete set of media resource addresses. The merged media resource addresses cover media resource addresses at different levels of web page data, including addresses directly exposed in HTML tags, dynamically generated addresses in JavaScript, and configuration addresses embedded in scripts.

[0112] In one implementation, the controller 250 also performs iframe recursive parsing on the merged media resource address, and recursively executes the above steps S701 to S703 on the page pointed to by the src attribute of the iframe tag, for example, recursively going deeper than 2 to 3 levels, until the media resource address is extracted or it is confirmed that it cannot be extracted.

[0113] The above technical solutions have the following beneficial effects or advantages: by performing multi-layer deep parsing through document object model tree traversal, page script execution interception, and regular expression pattern scanning, media resource addresses can be extracted from different levels of the webpage, including addresses directly exposed in HTML tags, dynamically generated addresses in JavaScript, and configuration addresses embedded in scripts, thereby improving the comprehensiveness and accuracy of media resource address extraction.

[0114] Figure 8 This is a flowchart illustrating the process of a display device executing page script parsing to extract media resource addresses, provided in some embodiments of this application.

[0115] See Figure 8 In some embodiments, the controller 250 performing step S702 may include the following steps: S801: Loads web page data using a preset browser engine and executes the page scripts contained in the web page data, and intercepts network requests generated during the execution of the page scripts.

[0116] In some embodiments, the controller 250 loads web page data through a preset browser engine. After the web page data is fully rendered, during the execution of the page script, the controller 250 intercepts all network requests generated during the execution of the page script through the network request interception function of the preset browser engine.

[0117] In one implementation, controller 250 sets network request filtering rules to filter out target network requests. The target network request refers to a request whose Uniform Resource Locator contains media resource identifiers such as m3u8, mp4, mpd, and Manifest.

[0118] S802: Extract the address of the first media resource from the network request.

[0119] In some embodiments, the controller 250 extracts a first media resource address from the intercepted target network request. The first media resource address is a media resource address dynamically requested and loaded during the execution of the page script; it does not appear directly in the HTML source code of the webpage, but is dynamically generated and requested by JavaScript code at runtime. The controller 250 extracts the media resource address from the request URL of each target network request and verifies the validity of the extracted address, excluding invalid or incomplete addresses.

[0120] In one implementation, controller 250 also listens for response data to XHR (XMLHttpRequest) and Fetch requests, capturing dynamically loaded playlist data. Playlist data refers to an HLS playlist in m3u8 format or a DASH media presentation description file in MPD format, which contains URLs of more media resource file segments. By listening to the response data, controller 250 can obtain more complete media resource address information.

[0121] S803: Read the global configuration object generated after the page script is executed, and extract the address of the second media resource from the global configuration object.

[0122] In some embodiments, after the page script has finished executing, the controller 250 reads the global configuration object generated after the page script execution. The global configuration object is a player configuration variable created under the browser's window object during the execution of the page script. For example, common player configuration variables include playerConfig, videoConfig, and JSON data objects embedded in the HTML page during server-side rendering or static generation by the Nuxt.js framework and the Next.js framework.

[0123] In some embodiments, the global configuration object contains information such as player initialization parameters, media resource addresses, and playlist configurations. Controller 250 parses and extracts the second media resource address from the global configuration object.

[0124] Based on the above technical solutions, by intercepting network requests generated during the execution of page scripts to extract the first media resource address, and reading the global configuration object generated after the execution of page scripts to extract the second media resource address, it is possible to capture media resource addresses that are dynamically loaded and generated at runtime, thereby improving the depth and coverage of media resource address extraction.

[0125] Figure 9 A flowchart illustrating the allocation of verification channels for display devices provided in some embodiments of this application.

[0126] See Figure 9 In some embodiments, the controller 250 performing step S403 may include the following steps: S901: When the native playback channel supports streaming media protocol types, the verification channel of the candidate media resource address will be assigned to the native playback channel.

[0127] In some embodiments, the controller 250 sends the streaming media protocol type of the candidate media resource address to the active verification engine through the protocol identification and adaptation layer. The active verification engine can verify the streaming media protocol type based on different verification channels, and perform subsequent protocol-level validity verification, content semantic matching, and joint verification of clarity and quality on the candidate media resource address through the verification channels.

[0128] When the native playback channel supports streaming media protocol types, the active verification engine assigns the verification channel for candidate media resource addresses to the native playback channel. The native playback channel performs verification processing on the candidate media resource addresses through the system's native multimedia framework of the display device 200. The system's native multimedia framework is a multimedia processing component built into the operating system of the display device 200. The native playback channel directly parses and plays media resources using the device's underlying multimedia framework, suitable for standard MP4 direct links and system-natively supported HLS / DASH addresses.

[0129] In one implementation, the verification process of the native playback channel includes: the protocol identification and adaptation layer determines whether the native playback channel supports the streaming media protocol type of the candidate media resource address; if it does, the candidate media resource address is passed to the system's native player framework; a timeout period (e.g., 10 seconds) is set, and the player status callback is listened for; if the player enters the PREPARED state, it indicates that the media stream can be parsed and played, and the video track information (resolution, bitrate, encoding format) is recorded; if the player calls back the ERROR state, the error code and error type (e.g., network unreachable, format not supported, decryption failed, etc.) are recorded.

[0130] S902: When the native playback channel does not support streaming media protocol types, the verification channel of the candidate media resource address will be downgraded and assigned to the script-driven playback channel.

[0131] In some embodiments, when the native playback channel does not support the streaming media protocol type corresponding to the candidate media resource address, the protocol identification and adaptation layer downgrades the verification channel of the candidate media resource address to the script-driven playback channel. The script-driven playback channel performs verification processing on the candidate media resource address by loading a script-driven media playback component in a sandboxed processing environment. The sandboxed processing environment is an isolated WebView or browser engine environment that loads a script-driven media playback component (such as hls.js, dash.js, or other JavaScript media playback libraries) to handle media resource files with HLS, DASH, and MSS protocols that require custom playback logic.

[0132] In one implementation, the verification process of the script-driven playback channel includes: loading the MSE player library (such as hls.js, dash.js) in a sandboxed WebView or browser engine; passing the candidate media resource address to the MSE player; listening to MSE's sourceopen, updateend, and other events; the MSE player requesting the first N segments of the media resource file (such as the first 3 TS segments or the first 5 seconds of data); verifying the integrity and decapsulation of the segment data; and recording the parameters of each track (video resolution, audio sampling rate, number of subtitle tracks, etc.), thus completing the process of verifying the candidate media resource address through the script-driven playback channel.

[0133] In one implementation, the dual-channel adaptation layer encapsulates the native playback channel and the script-driven playback channel into a unified verification interface, including three unified interfaces: probe (probe basic media resource information), validate (perform complete validity verification), and extractMetadata (extract media metadata). This dual-channel approach enables high-performance display devices to prioritize the native playback channel for verification, resulting in faster response times; protocols not supported by the native playback channel automatically downgrade to the script-driven playback channel; and both channels return unified verification results, eliminating the need for the upper layer to perceive any differences.

[0134] In some embodiments, the verification channel allocation process described above will also take into account the device capabilities of the display device 200 itself. For high-performance display devices 200, verification can be performed through the native playback channel. If it is found during the verification process that the native playback channel does not support the protocol, it can be downgraded to the script-driven playback channel for verification.

[0135] The above technical solutions have the following beneficial effects or advantages: Based on the streaming media protocol type and device capabilities, candidate media resource addresses are preferentially allocated to the native playback channel for verification. When the protocol is not supported, it automatically degrades to the script-driven playback channel. The dual-channel unified verification architecture ensures that media resources of different protocol types can be effectively verified. At the same time, the native channel is used first to improve verification efficiency, taking into account both verification coverage and verification performance.

[0136] Figure 10 This is a flowchart illustrating the protocol-level validity verification performed by a display device according to some embodiments of this application.

[0137] See Figure 10 In some embodiments, the controller 250 performing step S404 may include the following steps: S1001: When the streaming media protocol type is a direct link protocol type, initiate a range transmission request for the candidate media resource address, obtain the data content of the media resource file corresponding to the candidate media resource address with the first preset number of bytes, and perform a container format validity check on the data content with the first preset number of bytes to obtain the container check result.

[0138] In some embodiments, when the streaming media protocol type is a direct link protocol, the controller 250 initiates an HTTP Range request to the candidate media resource address to obtain the first preset number of bytes of data content of the media resource file. The HTTP Range request is a partial content request protocol that allows the client to request only a portion of the resource data instead of the entire file, thereby reducing data transfer volume and verification time.

[0139] In one implementation, the initial byte count can be set to 64KB (65536 bytes), which is sufficient to contain the container header information and initialization data of the media file.

[0140] For example, the direct link protocol type can be an mp4 direct link. For an mp4 direct link, the controller 250 initiates an HTTPRange request to request the first 64KB of data of the file, and checks whether the returned data contains a valid ftyp type box and a moov movie metadata box, etc., which are standard MP4 container header structures. If the MP4 container header structure is complete and compliant, it is initially determined that the MP4 direct link can be accessed normally and can be parsed and played.

[0141] In some embodiments, when the streaming media protocol type corresponding to the candidate media resource address is identified as a direct link protocol type (i.e., MP4 direct link) in step S1001, the controller 250 performs a container format validity check on the obtained data content of the first preset number of bytes based on the MP4 container format rules, and obtains the container check result. The controller 250 sequentially checks the integrity and validity of the ftypbox (file type box), checks the integrity of the moov box (movie header box), and checks whether the Content-Length field in the HTTP response header is greater than a preset threshold (e.g., 1MB).

[0142] The ftyp box is usually located at the beginning of an MP4 file. Controller 250 verifies whether the "ftyp" identifier exists in the first 8 bytes of the data content. If the ftyp box is missing, the output container check result is "invalid container format" and the failure type is recorded as "ftyp check failed".

[0143] The moov box contains metadata information about the media tracks, including timestamps for video and audio tracks, codec configurations, sample tables, and other key information. Controller 250 searches for the "moov" identifier in the first 64KB of data. If the moov box is missing or incompletely truncated, the output container check result is "invalid container format," and the failure type is recorded as "moov check failed."

[0144] If the Content-Length is less than the preset threshold, the output container check result will be "Invalid container format", and the failure type will be recorded as "This resource may be a placeholder page or an error response".

[0145] In one implementation, the three checks (ftyp box check, moov box check, and Content-Length check) are performed sequentially. If any check fails, the controller 250 records the corresponding failure type and terminates subsequent checks, generating a container check result. The container check result includes two states: "container format valid" and "container format invalid." When the container format is invalid, the container check result also includes specific failure type information for subsequent generation of a structured verification report. When all three checks pass, the controller 250 generates a "container format valid" container check result.

[0146] S1002: When the streaming media protocol type is any one of the first adaptive bitrate protocol type, the second adaptive bitrate protocol type, or the third adaptive bitrate protocol type, perform a structure validity check on the first manifest file corresponding to the candidate media resource address, and perform a sampling availability check on the media segment corresponding to the candidate media resource address.

[0147] When the streaming media protocol type is any one of the first adaptive bitrate protocol type, the second adaptive bitrate protocol type, or the third adaptive bitrate protocol type, the controller 250 performs a structural validity check on the first manifest file corresponding to the candidate media resource address and performs a sampling availability check on the media segment corresponding to the candidate media resource address.

[0148] The first adaptive bitrate protocol type is HLS, the second is DASH, and the third is MSS. Different adaptive bitrate protocol types correspond to different manifest file formats and fragmentation structures. Controller 250 executes differentiated inspection strategies for each protocol type. For the HLS protocol, controller 250 downloads and parses the m3u8 playlist file (the first playlist file), verifying the validity of the "#EXTM3U" tag in the m3u8 playlist file. If the EXTM3U tag is missing or the key tag field is formatted incorrectly, the playlist structure is deemed invalid. If the EXTM3U tag is complete, controller 250 extracts the TS fragment addresses from the m3u8 playlist, randomly samples 2 to 3 TS fragments to perform HTTP Range probes, verifying the service reachability of the fragment URLs and the validity of the fragment data, in order to perform a sampling accessibility check.

[0149] For the DASH protocol, controller 250 downloads and parses the MPD (Media Presentation Description) manifest XML file (the first manifest file), and performs validity checks on the MPD manifest XML file, such as whether the MPD manifest XML file was successfully parsed or whether the DASH protocol schema specification validation passed. If MPD XML parsing fails or schema specification validation fails, the manifest structure is deemed invalid. If the manifest structure is valid, controller 250 extracts the initial fragment address and media fragment address from the MPD file, and performs HTTPRange probing on the initial fragment and one or two randomly sampled media fragments to perform sampling availability checks.

[0150] For the MSS protocol, controller 250 downloads and parses the Manifest XML manifest file (first manifest file), performing the following structure validity checks: verifying that the SmoothStreamingMedia root element identifier exists and is valid. If the manifest structure is valid, random sampling fragments are used to perform HTTP Range probes to perform sampling availability checks.

[0151] In one implementation, the structural validity check and sampling availability check are executed sequentially. The controller 250 first performs a structural validity check on the manifest file, and only if the manifest structure is valid does it then perform a fragment sampling availability check. If the manifest structure is invalid, the controller 250 skips the fragment sampling check and directly generates a "manifest structure invalid" check result. In the sampling availability check, the number of fragments sampled can be adjusted according to actual needs; the default is to sample 2 to 3 fragments to balance verification coverage and verification time. The controller 250 initiates an HTTP Range request for each sampled fragment to obtain the first preset number of bytes of data content from the fragment, verifying the integrity and validity of the fragment data.

[0152] S1003: Generate a first verification result based on at least one of the container inspection results, structural validity checks, and sampling availability checks.

[0153] In some embodiments, the controller 250 aggregates at least one of the container check results for straight-link protocol types, and the structural validity check results and sampling availability check results for adaptive bitrate protocol types, to generate a first verification result. The first verification result is used to indicate the validity status of the candidate media resource address at the protocol level.

[0154] In one implementation, after generating the first verification result, the controller 250 passes the verified candidate media resource addresses to the second-level verification stage (joint verification of content semantic matching and clarity quality), marks the candidate media resource addresses that fail verification as invalid addresses and records them in the historical invalid address database, and at the same time feeds back the invalid address information to the retrieval source so that the retrieval source can update its index.

[0155] Based on the above technical solutions, this embodiment implements differentiated protocol-level validity verification processes for direct-link protocols and different types of adaptive bitrate protocols. Validity verification requires only a small amount of data, eliminating the need to download complete media resource files. This significantly reduces data transmission volume and verification time, improving verification efficiency and enhancing the accuracy and reliability of protocol-level validity verification.

[0156] Figure 11 This is a flowchart illustrating the joint verification of content semantic matching and resolution quality performed by a display device according to some embodiments of this application.

[0157] See Figure 11 In some embodiments, the controller 250 performing step S405 may include the following steps: S1101: If the first verification result is successful, the manifest file and / or container file corresponding to the candidate media resource address are parsed to obtain the key image frames and resolution information of the media resource file corresponding to the candidate media resource address.

[0158] In some embodiments, for candidate media resource addresses whose first verification result is successful, the controller 250 performs parsing on their corresponding manifest file and / or container file, simultaneously extracting keyframes and resolution information. For example, a key image frame is an I-frame (intra-coded frame) in the media resource file, which is a video frame capable of independent decoding and display. For mp4 direct links, the controller 250 locates the I-frame using the ffprobe tool; for HLS / DASH / MSS protocols, the controller 250 downloads the first complete GOP (Group of Pictures) fragment to extract the I-frame. In one implementation, this embodiment can extract 1 to 3 key image frames.

[0159] In one implementation, controller 250 also extracts text metadata information. For the HLS protocol, header information is extracted from the EXTINF tag of the m3u8 manifest; for the DASH protocol, header information is extracted from the title tag of the MPD file; for the MSS protocol, information is extracted from the stream name in the StreamIndex; and for mp4 direct links, metadata information is extracted from the tkhd / udta tag.

[0160] In one implementation, the method for extracting resolution information varies depending on the streaming media protocol type. For HLS, the resolution is extracted from the RESOLUTION attribute of the EXT-X-STREAM-INF tag in the m3u8 manifest; for DASH, it is extracted from the width and height attributes of the Representation element in the MPD; for MSS, it is extracted from the QualityLevel element; and for mp4 direct links, it is extracted from the width and height fields of the tkhd tag. If the resolution is specified in the manifest file, that value can be used directly; otherwise, the actual resolution is extracted from the SPS (Sequence Parameter Set) or VPS (Video Parameter Set) by decoding a small number of video frames.

[0161] S1102: Input the key image frame and the target media asset lookup instruction into the multimodal large model, and obtain the content matching confidence between the key image frame and the target media asset lookup instruction output by the multimodal large model.

[0162] In some embodiments, the controller 250 inputs the extracted key image frames and the user's target media search instruction into the multimodal big model. The multimodal big model is an artificial intelligence model capable of simultaneously processing image and text information. It analyzes the visual content in the key image frames through visual semantic understanding and performs semantic matching with the expected content described in the user's search instruction. The multimodal big model outputs a content matching confidence score, a value between 0 and 1, reflecting the degree of matching between the content of the key image frames and the user's expected content. In one implementation, the multimodal big model can be deployed locally on the display device 200 or deployed on a cloud server.

[0163] In one implementation, the controller 250 also performs semantic similarity calculation between the extracted text metadata and the user query as an auxiliary judgment criterion. The final content matching conclusion is derived by combining the visual semantic matching and text semantic matching results. If the content matching confidence is lower than a preset threshold (e.g., 0.6), it is marked as "content questionable" and its recommendation priority is reduced; if the content matching confidence is extremely low (e.g., below 0.2), it is marked as "content mismatch" and the candidate media resource address is excluded.

[0164] S1103: Compare the resolution information with the clarity requirements in the target media asset search instruction to obtain clarity matching information.

[0165] In some embodiments, the controller 250 compares the extracted resolution information with the resolution requirements in the user's target media asset search instruction to obtain resolution matching information. The comparison rules include: 4K requirements correspond to a resolution greater than or equal to 3840×2160; 1080P requirements correspond to a resolution greater than or equal to 1920×1080; HD requirements correspond to a resolution greater than or equal to 1280×720; when the user does not specify a resolution requirement, the AI ​​Agent automatically infers the minimum requirement. Resolution matching information includes three states: exact match (resolution fully meets user requirements), downgraded to available (resolution lower than user requirements but still watchable, such as user requiring 4K but the highest available resource is 1080P), and unsatisfactory (resolution too low to be worth watching).

[0166] S1104: Generate a second verification result based on the content matching confidence and clarity matching information.

[0167] In some embodiments, the controller 250 integrates content matching confidence and clarity matching information to generate a second verification result. The second verification result includes a content matching confidence value, clarity matching status information, and a comprehensive judgment conclusion. The comprehensive judgment conclusion includes: content matches and clarity meets the standard (highest recommendation priority), content matches but clarity is downgraded (as an alternative recommendation), content is questionable but clarity meets the standard (requires user confirmation), and content does not match (excluding recommendation). The second verification result is output in structured JSON format, containing fields such as content matching confidence, clarity matching status, content tags, and matching conclusion, serving as input data for subsequent comprehensive scoring and ranking.

[0168] Based on the above technical solutions, the content semantic matching verification is performed by inputting key image frames and user search instructions into a multimodal large model, and the resolution information is compared and verified with the user's clarity requirements. At the same time, the content matching degree and clarity compliance of media resources are verified, thereby improving the accuracy of finding media resources and the clarity compliance rate.

[0169] Figure 12 A flowchart illustrating the comprehensive scoring and ranking process performed by a display device according to some embodiments of this application.

[0170] See Figure 12 In some embodiments, the controller 250 is further configured to perform the following steps before executing step S406: S1201: Input the first and second verification results into the large language model in a structured data format so that the large language model can perform a comprehensive score on the candidate media resource addresses based on protocol-level validity, content semantic matching and clarity quality, and obtain the comprehensive score result.

[0171] In some embodiments, the controller 250 inputs the first and second verification results into the result presentation layer in structured JSON format via an active verification engine. The result presentation layer performs multi-condition reasoning based on the first and second verification results using a large language model: It determines whether a resource is playable based on the first-layer verification result; if not, it excludes it directly. It prioritizes high content matching confidence based on the content matching confidence of the second-layer verification result, downgrading confidence if the content is questionable. It prioritizes resources meeting the clarity requirements based on the clarity matching result of the second-layer verification, downgrading usable resources as alternatives. It also considers auxiliary factors such as resource source reputation and update freshness. The large language model performs a comprehensive score on each candidate media resource address; the comprehensive score is a numerical score reflecting the overall quality level of the candidate media resource address.

[0172] In one implementation, the large language model categorizes candidate media resource addresses based on a comprehensive scoring result. Resources that pass both layers of verification, have high content matching confidence, and meet the required clarity are rated "Best Match"; resources with matching content but reduced clarity are rated "Downgraded Alternative"; resources with questionable content but meeting the required clarity are rated "Requires User Confirmation"; and resources with mismatched content or that fail the first layer of verification are directly excluded. The large language model also generates user-oriented natural language feedback, such as "Found a 4K HDR resource from ABC, HLS protocol, verified playable" (both layers passed), "Found a 1080P resource from ABC, HLS protocol, playable, but clarity does not meet 4K requirements" (reduced clarity), or "The actual content of this link is another movie not from ABC, does not meet the requirements" (content mismatch), etc.

[0173] S1202: Sort and filter the candidate media resource addresses based on the comprehensive score results to obtain a recommended list.

[0174] In some embodiments, the controller 250 sorts and filters candidate media resource addresses based on the comprehensive score results. Sorting involves arranging the candidate media resource addresses in descending order of comprehensive score, with resources having higher scores appearing at the top of the recommendation list. Filtering excludes resources that do not meet the minimum criteria, including resources that failed the first-level verification, resources with extremely low content matching confidence, and resources with severely inadequate clarity. After sorting and filtering, the final recommendation list is obtained.

[0175] The above technical solution has the following beneficial effects or advantages: by inputting the two-layer verification results into a large language model in a structured data format for comprehensive scoring and ranking filtering, the multi-condition reasoning capability of the large language model is used to make intelligent decisions on candidate media resources. It can sort the resources based on multiple dimensions such as protocol-level validity, content semantic matching degree, and clarity quality, and exclude resources that do not meet the minimum conditions, thereby improving the ranking rationality of the recommendation list and user satisfaction.

[0176] Figure 13 This is a flowchart illustrating the process of handling invalid media resource addresses in a display device according to some embodiments of this application.

[0177] See Figure 13 In some embodiments, if the first verification result is that the verification fails, the controller 250 is further configured to perform the following steps: S1301: Record the search source corresponding to the candidate media resource address.

[0178] In some embodiments, when the first verification result of a candidate media resource address is verification failure, the controller 250 records the retrieval source corresponding to the candidate media resource address. It also records detailed information about the verification failure, including the reason for the failure (such as an invalid manifest file, incorrect container format, unreachable fragments, etc.), the verification time, and the error code.

[0179] S1302: Send a message to the corresponding search source indicating that the address is invalid, and remove the candidate media resource address from the candidate media resource address list.

[0180] In some embodiments, the controller 250 sends an invalid address notification to the retrieval source corresponding to the candidate media resource address. The notification includes the URL of the invalid address, the reason for verification failure, and the verification time, enabling the retrieval source to optimize its indexing and recommendation strategies based on the notification, reducing the re-recommendation of invalid addresses. Simultaneously, the controller 250 removes the invalid candidate media resource address from the candidate media resource address list, preventing it from entering subsequent verification processes and recommendation lists.

[0181] The above technical solution has the following beneficial effects or advantages: When the first verification result is that the verification fails, the retrieval source corresponding to the candidate media resource address is recorded and the corresponding retrieval source is fed back with the prompt message that the address is invalid. At the same time, the invalid address is removed from the candidate media resource address list. This can promptly clean up invalid resources and feed back to the retrieval source, avoiding repeated recommendation of invalid addresses in the future. It also provides feedback data for retrieval source optimization and improves the continuous optimization capability of the media resource recommendation system.

[0182] In some embodiments, this application introduces a user preference learning mechanism to record user acceptance or rejection of AI Agent recommendations, thus establishing a user preference model. In subsequent validation, the large language model incorporates user preference weights from the user preference model when making decisions; for example, a user might prefer HLS protocol resources or high bitrates. Through user preference learning, the recommendation list can better meet users' personalized needs, improving user satisfaction.

[0183] In some embodiments, multiple terminal devices (including display device 200) form a distributed collaborative verification network to share the validity information of verified resources. The resource URL verified by device A and its verification result are synchronized to the cloud cache. When device B searches for the same resource, it can directly reuse the verification result, avoiding duplicate verification. Distributed collaborative verification can significantly reduce the computational overhead of the entire verification network and improve verification efficiency, making it particularly suitable for scenarios where multiple devices simultaneously search for the same media resource.

[0184] Based on the above display device 200, some embodiments of this application also provide a method for verifying the validity of network media resources, including the following steps: S410: In response to a user-inputted target media resource search command, obtain a list of candidate media resource addresses, wherein the list of candidate media resource addresses includes at least one candidate media resource address.

[0185] S420: Identify the streaming media protocol type corresponding to the candidate media resource address based on the address characteristics of the candidate media resource address.

[0186] S430: Assign a verification channel to the candidate media resource address based on the streaming media protocol type.

[0187] S440: Based on the verification channel, perform protocol-level validity verification on the candidate media resource address to obtain the first verification result.

[0188] Different streaming media protocol types correspond to different protocol-level validity verification methods.

[0189] S450: If the first verification result is successful, perform joint verification of content semantic matching and clarity quality on the candidate media resource address to obtain the second verification result.

[0190] The second verification result includes content matching confidence and clarity matching information.

[0191] S460: Controls the display to show a recommended list on the user interface, which is obtained by performing a comprehensive ranking of candidate media resource addresses based on content matching confidence and resolution matching information.

[0192] As can be seen from the above technical solutions, some embodiments of this application provide a method for validating the validity of display devices and network media resources. This method obtains a list of candidate media resource addresses in response to a user-inputted target media resource search command, identifies the streaming media protocol type corresponding to the candidate media resource addresses and allocates a verification channel, performs protocol-level validity verification based on the verification channel to obtain a first verification result, and performs joint verification of content semantic matching and clarity quality to obtain a second verification result if the first verification result is successful. Finally, a comprehensive ranking of the candidate media resource addresses is performed based on content matching confidence and clarity matching information to obtain a recommendation list. This application, through a two-layer progressive verification system, ensures the authenticity and accuracy of the searched media resources from multiple dimensions, including protocol-level playability, content semantic matching, and clarity quality, reducing the false recommendation rate of invalid resources and improving the efficiency and experience of users searching for media content.

[0193] The same or similar parts among the various embodiments in this specification can be referred to mutually, and will not be repeated here.

[0194] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of various embodiments or certain parts of the embodiments of the present invention.

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

[0196] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Various modifications and variations can be obtained based on the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, thereby enabling those skilled in the art to better utilize the described embodiments and various different variations of embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that, include: The monitor is configured to display the user interface; The controller is configured as follows: In response to a user-inputted target media resource search command, a candidate media resource address list is obtained, wherein the candidate media resource address list includes at least one candidate media resource address; Based on the address characteristics of the candidate media resource addresses, identify the streaming media protocol type corresponding to the candidate media resource addresses; A verification channel is allocated to the candidate media resource address according to the streaming media protocol type; Based on the verification channel, protocol-level validity verification is performed on the candidate media resource address to obtain a first verification result, wherein different streaming media protocol types correspond to different protocol-level validity verification methods; If the first verification result is successful, a joint verification of content semantic matching and clarity quality is performed on the candidate media resource address to obtain a second verification result, wherein the second verification result includes content matching confidence and clarity matching information; The display is controlled to show a recommendation list on the user interface, which is obtained by performing a comprehensive ranking of the candidate media resource addresses based on the content matching confidence and the clarity matching information.

2. The display device according to claim 1, characterized in that, The controller executes a target media resource search command in response to user input, and obtains a list of candidate media resource addresses, specifically configured as follows: The intent of the target media asset search command is parsed using a large language model to obtain structured search elements, which include content identifiers, clarity constraints, content types, and additional constraints. Based on the content identifier, the clarity constraint, the content type, and the additional constraints, differentiated query requests are sent to multiple retrieval sources, and webpage data returned by the multiple retrieval sources based on the differentiated query requests are received. Perform multi-layer deep parsing on the webpage data to extract the media resource addresses of the webpage data; The media resource addresses are filtered, deduplicated, and aggregated to obtain the candidate media resource address list.

3. The display device according to claim 2, characterized in that, The controller performs multi-layer deep parsing on the webpage data to extract the media resource addresses of the webpage data, specifically configured as follows: Traverse the document object model tree corresponding to the webpage data, locate the target tag in the document object model tree, obtain the source address attribute value of the target tag, and obtain the first address set; The webpage data is loaded by a preset browser engine and the page script contained in the webpage data is executed to extract the first media resource address based on the page script, and to obtain the second media resource address after executing the page script; Perform a regular expression pattern scan on the script content and configuration data text embedded in the web page data to extract the third media resource address that conforms to the preset media address pattern; The first address set, the first media resource address, the second media resource address, and the third media resource address are merged to obtain the media resource address.

4. The display device according to claim 3, characterized in that, The controller loads the webpage data using a preset browser engine and executes the page script contained in the webpage data to extract a first media resource address based on the page script, and obtains a second media resource address after executing the page script. Specifically, it is configured as follows: The webpage data is loaded using a preset browser engine, and the page script contained in the webpage data is executed, while network requests generated during the execution of the page script are intercepted. Extract the address of the first media resource from the network request; Read the global configuration object generated after the page script is executed, and extract the address of the second media resource from the global configuration object.

5. The display device according to claim 1, characterized in that, The controller performs the allocation of verification channels for the candidate media resource addresses based on the streaming media protocol type, specifically configured as follows: When the native playback channel supports the streaming media protocol type, the verification channel of the candidate media resource address is assigned to the native playback channel, wherein the native playback channel performs verification processing on the candidate media resource address through the system native multimedia framework of the display device; If the native playback channel does not support the streaming media protocol type, the verification channel of the candidate media resource address is downgraded and assigned to the script-driven playback channel. The script-driven playback channel performs verification processing on the candidate media resource address by loading a script-driven media playback component in a sandboxed processing environment.

6. The display device according to claim 1, characterized in that, The controller performs protocol-level validity verification on the candidate media resource address based on the verification channel to obtain a first verification result, specifically configured as follows: When the streaming media protocol type is a direct link protocol type, a range transmission request is initiated for the candidate media resource address to obtain the data content of the media resource file corresponding to the candidate media resource address with the first preset number of bytes, and a container format validity check is performed on the data content with the first preset number of bytes to obtain the container check result; When the streaming media protocol type is any one of the first adaptive bitrate protocol type, the second adaptive bitrate protocol type, or the third adaptive bitrate protocol type, a structural validity check is performed on the first manifest file corresponding to the candidate media resource address, and a sampling availability check is performed on the media segment corresponding to the candidate media resource address. The first verification result is generated based on at least one of the container inspection result, the structural validity check, and the sampling availability check.

7. The display device according to claim 1, characterized in that, If the first verification result is successful, the controller performs joint verification of content semantic matching and clarity quality on the candidate media resource address to obtain a second verification result, specifically configured as follows: If the first verification result is successful, the manifest file and / or container file corresponding to the candidate media resource address are parsed to obtain the key image frames and resolution information of the media resource file corresponding to the candidate media resource address. Input the key image frame and the target media asset search instruction into the multimodal large model, and obtain the content matching confidence between the key image frame and the target media asset search instruction output by the multimodal large model; The resolution information is compared with the clarity requirement in the target media asset search instruction to obtain the clarity matching information; The second verification result is generated based on the content matching confidence level and the clarity matching information.

8. The display device according to claim 1, characterized in that, The controller, before displaying the recommended list obtained by comprehensively ranking the candidate media resource addresses based on the content matching confidence score and the clarity matching information on the user interface, is further configured to: The first verification result and the second verification result are input into the large language model in a structured data format, so that the large language model performs a comprehensive score on the candidate media resource address based on protocol-level validity, content semantic matching and clarity quality, and obtains a comprehensive score result; The candidate media resource addresses are sorted and filtered based on the comprehensive scoring results to obtain the recommendation list.

9. The display device according to claim 1, characterized in that, If the first verification result is that the verification fails, the controller is further configured to: Record the search source corresponding to the candidate media resource address; The system sends an invalid address message to the corresponding search source and removes the candidate media resource address from the candidate media resource address list.

10. A method for verifying the validity of online media resources, characterized in that, Applied to a display device, the display device including a display and a controller, the method includes: In response to a user-inputted target media resource search command, a candidate media resource address list is obtained, wherein the candidate media resource address list includes at least one candidate media resource address; Based on the address characteristics of the candidate media resource addresses, identify the streaming media protocol type corresponding to the candidate media resource addresses; A verification channel is allocated to the candidate media resource address according to the streaming media protocol type; Based on the verification channel, protocol-level validity verification is performed on the candidate media resource address to obtain a first verification result, wherein different streaming media protocol types correspond to different protocol-level validity verification methods; If the first verification result is successful, a joint verification of content semantic matching and clarity quality is performed on the candidate media resource address to obtain a second verification result, wherein the second verification result includes content matching confidence and clarity matching information; The display is controlled to show a recommendation list on the user interface, which is obtained by performing a comprehensive ranking of the candidate media resource addresses based on the content matching confidence and the clarity matching information.

Images