Display device and content loading method thereof

Abstract

The invention relates to a display device and a content loading method thereof. The display apparatus includes: a display configured to display target content data; the controller is connected with the display and is configured to obtain a content loading request and determine a target protocol type of a communication protocol corresponding to the content loading request; under the condition that the target protocol type is the user-defined protocol type, determining an operation context of an application program which is currently operated in the display equipment; determining a matching result of the target protocol type and the operation context according to a preset matching relationship; performing security detection on the content loading request; under the condition that the matching result indicates that the target protocol type is matched with the running context and the content loading request passes the security detection, obtaining target content data corresponding to the content loading request; and rendering and displaying the target content data in a display. By adopting the display equipment, the compatibility of the display equipment is improved, so that the use experience of a user is improved.

Description

Technical Field

[0001] This application relates to the field of display technology, and in particular to a display device and a method for loading its content. Background Technology

[0002] With the development of display technology, users have gained richer and more diverse visual experiences. However, in the crucial step of content loading, current display devices typically have certain limitations, namely, they usually only support content loading using standard or internal protocols. This singular content loading method, to some extent, restricts the compatibility of display devices with diverse data sources.

[0003] From the user's perspective, when users try to watch live cable TV, access TV services based on the DVB (Digital Video Broadcasting) protocol, or use interactive applications customized by operators through their browsers, compatibility limitations prevent the browser from natively parsing DVB streaming media data and interacting with the operator's backend system, thus affecting the user experience. Summary of the Invention

[0004] Therefore, it is necessary to provide a display device and its content loading method to address the aforementioned technical problems, so as to improve the compatibility of the display device and thus enhance the user experience.

[0005] In a first aspect, some embodiments provide a display device, including:

[0006] The display is configured to show the target content data;

[0007] The controller, connected to the display, is configured as follows:

[0008] Obtain the content loading request and determine the target protocol type of the communication protocol corresponding to the content loading request;

[0009] If the target protocol type is a custom protocol type, determine the runtime context of the currently running application on the display device;

[0010] Based on the first preset matching relationship, determine the matching result between the target protocol type and the runtime context; and perform security checks on the content loading request;

[0011] If the matching result indicates that the target protocol type matches the runtime context, and the content loading request passes the security check, then obtain the target content data corresponding to the content loading request.

[0012] The target content data is rendered and displayed on the monitor.

[0013] In the above embodiments, by acquiring the content loading request and determining the target protocol type of the communication protocol corresponding to the content loading request, a data foundation is provided for subsequently determining the loading method corresponding to different target protocol types. When the target protocol type is a custom protocol type, the running context of the currently running application on the display device is determined, and the matching result between the target protocol type and the running context is determined according to the first preset matching relationship. This associates the target protocol type with the running environment of a specific application scenario, and the compatibility between the target protocol type and the running context can be verified through the matching result. By performing security checks on the content loading request, a dual verification mechanism of protocol compatibility verification and security verification is constructed, which can effectively prevent malicious protocol attacks or illegal data injection. When the matching result indicates that the target protocol type matches the running context, and the content loading request passes the security check, the target content data corresponding to the content loading request is acquired, and the target content data is rendered and displayed on the display. This achieves the loading and visualization of custom protocol type content while ensuring protocol compatibility and security, solving the problems of insufficient support for custom protocols and weak security protection in traditional content loading methods, and improving the compatibility of the display device with diverse data sources and the user experience.

[0014] Secondly, some embodiments also provide a content loading method, including:

[0015] Obtain the content loading request and determine the target protocol type of the communication protocol corresponding to the content loading request;

[0016] If the target protocol type is a custom protocol type, determine the runtime context of the currently running application on the display device;

[0017] Based on the first preset matching relationship, determine the matching result between the target protocol type and the runtime context; and perform security checks on the content loading request;

[0018] If the matching result indicates that the target protocol type matches the runtime context, and the content loading request passes the security check, then obtain the target content data corresponding to the content loading request.

[0019] The target content data is rendered and displayed on the monitor of the display device.

[0020] In the above embodiments, by acquiring the content loading request and determining the target protocol type of the communication protocol corresponding to the content loading request, a data foundation is provided for subsequently determining the loading method corresponding to different target protocol types. When the target protocol type is a custom protocol type, the running context of the currently running application on the display device is determined, and the matching result between the target protocol type and the running context is determined according to the first preset matching relationship. This associates the target protocol type with the running environment of a specific application scenario, and the compatibility between the target protocol type and the running context can be verified through the matching result. By performing security checks on the content loading request, a dual verification mechanism of protocol compatibility verification and security verification is constructed, which can effectively prevent malicious protocol attacks or illegal data injection. When the matching result indicates that the target protocol type matches the running context, and the content loading request passes the security check, the target content data corresponding to the content loading request is acquired, and the target content data is rendered and displayed on the display. This achieves the loading and visualization of custom protocol type content while ensuring protocol compatibility and security, solving the problems of insufficient support for custom protocols and weak security protection in traditional content loading methods, and improving the compatibility of the display device with diverse data sources and the user experience.

[0021] Thirdly, some embodiments also provide a content loading device, including:

[0022] The first acquisition module is used to acquire the content loading request and determine the target protocol type of the communication protocol corresponding to the content loading request;

[0023] The first determining module is used to determine the running context of the currently running application in the display device when the target protocol type is a custom protocol type;

[0024] The second determining module is used to determine the matching result between the target protocol type and the runtime context based on the first preset matching relationship; and to perform security checks on the content loading request;

[0025] The second acquisition module is used to acquire the target content data corresponding to the content loading request when the matching result indicates that the target protocol type matches the runtime context and the content loading request passes the security check.

[0026] The display module is used to render and display the target content data on the monitor of the display device.

[0027] In the above embodiments, by acquiring the content loading request and determining the target protocol type of the communication protocol corresponding to the content loading request, a data foundation is provided for subsequently determining the loading method corresponding to different target protocol types. When the target protocol type is a custom protocol type, the running context of the currently running application on the display device is determined, and the matching result between the target protocol type and the running context is determined according to the first preset matching relationship. This associates the target protocol type with the running environment of a specific application scenario, and the compatibility between the target protocol type and the running context can be verified through the matching result. By performing security checks on the content loading request, a dual verification mechanism of protocol compatibility verification and security verification is constructed, which can effectively prevent malicious protocol attacks or illegal data injection. When the matching result indicates that the target protocol type matches the running context, and the content loading request passes the security check, the target content data corresponding to the content loading request is acquired, and the target content data is rendered and displayed on the display. This achieves the loading and visualization of custom protocol type content while ensuring protocol compatibility and security, solving the problems of insufficient support for custom protocols and weak security protection in traditional content loading methods, and improving the compatibility of the display device with diverse data sources and the user experience.

[0028] Fourthly, some embodiments also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method of the second aspect described above in various possible ways.

[0029] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the method of the second aspect described above in various possible ways. Attached Figure Description

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

[0031] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device, provided in some embodiments.

[0032] Figure 2 A schematic diagram of the hardware configuration of a display device provided for some embodiments;

[0033] Figure 3 A schematic diagram of the hardware configuration of the control device provided for some embodiments;

[0034] Figure 4 A schematic diagram of the software configuration of a display device provided for some embodiments;

[0035] Figure 5A A flowchart illustrating a content loading method provided in some embodiments;

[0036] Figure 5B A flowchart illustrating a content loading method provided for other embodiments;

[0037] Figure 5C A flowchart illustrating the steps for acquiring target content data provided in some embodiments;

[0038] Figure 5D A schematic diagram of the structure of a network service provided in some embodiments;

[0039] Figure 6A A flowchart illustrating the security detection steps for content loading requests provided in some embodiments;

[0040] Figure 6B Other embodiments provide flowcharts of the security detection process;

[0041] Figure 7A A timing diagram of a content loading method provided in some embodiments;

[0042] Figure 7B A schematic diagram illustrating the writing process of target content data for some embodiments;

[0043] Figure 8 A flowchart illustrating a content loading method provided in some embodiments;

[0044] Figure 9 Schematic diagrams of the content loading apparatus provided in some embodiments;

[0045] Figure 10 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

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

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

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

[0049] The terms “include” and “have”, and any variations thereof, are intended to cover but not exclusively include, 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.

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

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

[0052] 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, users can operate the display device 200 via touch operation, mobile terminal 300, and control device 100. For example, control device 100 can be a remote control, stylus, gamepad, etc.

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

[0054] like Figure 1The 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.

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

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

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

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

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

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

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

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

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

[0064] 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 receives user input commands through the graphical user interface (GUI).

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

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

[0067] Figure 3 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of the central control device. (Example) Figure 3 As shown, the control device 100 may include: a controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply.

[0068] The control device 100 is configured to control the display device 200, and to receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to, thus acting as an intermediary for interaction between the user and the display device 200.

[0069] In some embodiments, the control device 100 may be an intelligent device. For example, the control device 100 may be equipped with various applications for controlling the display device 200 according to user needs.

[0070] In some embodiments, such as Figure 1 As shown, the mobile terminal 300 or other smart electronic devices can perform similar functions to the control device 100 after installing the application of the control display device 200.

[0071] The controller 110 includes a processor 112, RAM 113, ROM 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation of the control device 100, as well as the communication and cooperation between internal components and the external and internal data processing functions.

[0072] Under the control of the controller 110, the communication interface 130 enables communication of control signals and data signals with the display device 200. The communication interface 130 may include at least one of other near-field communication modules such as WiFi chip 131, Bluetooth module 132, and NFC module 133.

[0073] User input / output interface 140, wherein the input interface includes at least one of other input interfaces such as microphone 141, touchpad 142, sensor 143, and button 144.

[0074] In some embodiments, the control device 100 includes at least one of a communication interface 130 and an input / output interface 140. The control device 100 is configured with the communication interface 130, such as a WiFi, Bluetooth, or NFC module, which can encode user input commands via WiFi, Bluetooth, or NFC protocols and send them to the display device 200.

[0075] The memory 190 is used to store various operating programs, data, and applications for driving and controlling the control device 100 under the control of the controller. The memory 190 can also store various control signal instructions input by the user.

[0076] The power supply 180 is used to provide operating power support for the various components of the control device 100 under the control of the controller.

[0077] In some embodiments, to enable user interaction, 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) provide a user interface, allowing users to interact with the display device 200 and supporting the running of various applications.

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

[0079] Operating systems can be divided into different modules or levels based on the functions they implement.

[0080] like Figure 4 As shown, Figure 4 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.

[0081] The application layer mainly includes commonly used applications on TV, as well as the application framework. The commonly used applications are mainly browser-based applications, such as HTML5 apps (HyperTextMarkupLanguage 5 Applications, applications based on web technologies such as the fifth edition of Hypertext Markup Language); and native apps.

[0082] 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).

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

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

[0085] The hardware layer mainly includes the Hardware Abstraction Layer (HAL) interface, hardware, and drivers. The HAL interface serves as a unified interface for all TV chips, with the specific logic implemented by each individual chip. Drivers primarily include: audio drivers, display drivers, Bluetooth drivers, camera drivers, Wi-Fi drivers, USB drivers, HDMI drivers, sensor drivers (such as fingerprint sensors, temperature sensors, and pressure sensors), and power drivers.

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

[0087] Currently, most browsers on display devices are built on a widely adopted open-source engine. However, this engine has limitations in its support for network protocols, typically only covering standard protocols such as HTTP (Hypertext Transfer Protocol), HTTPS (Hypertext Transfer Protocol Secure), and FILE (File Transfer Protocol), as well as its own internally defined protocols. It does not support protocols such as digital video broadcasting protocols or carrier application protocols.

[0088] From the user's perspective, when users try to watch live cable TV, access TV services based on the DVB (Digital Video Broadcasting) protocol, or use interactive applications customized by operators through their browsers, compatibility limitations prevent the browser from natively parsing DVB streaming media data and interacting with the operator's backend system, thus affecting the user experience.

[0089] In some embodiments, see Figure 5A A content loading method is provided, applied to the controller 250 of a display device 200, including:

[0090] S510. Obtain the content loading request and determine the target protocol type of the communication protocol corresponding to the content loading request.

[0091] Here, a content loading request can be understood as a request to load target content data into the display page of a monitor, i.e., a network request. For example, the display page may include at least one of an application page and a browser page.

[0092] For example, a content loading request can be generated when the display device is turned on; for example, a content loading request for a display page can be generated when navigating to a display page. This application does not limit the specific process for generating the content loading request.

[0093] The target protocol type can be understood as the protocol category used to characterize the communication protocol corresponding to the content loading request.

[0094] For example, the target protocol type may include standard protocol types such as HTTP, HTTPS, and FILE, internal protocol types, or custom protocol types. Custom protocol types can be understood as protocol types other than the pre-determined standard and internal protocol types. It should be noted that the pre-determined standard and internal protocol types can be the standard and internal protocol types supported by default by the browser engine of the display device. Optionally, custom protocol types may include at least one of broadcast protocols (DVB) and carrier application protocols.

[0095] In some embodiments, the corresponding target protocol type can be extracted or parsed from the content loading request. Optionally, a target field can be extracted from the content loading request; based on the target field, the target protocol type of the communication protocol corresponding to the content loading request can be determined.

[0096] S520. If the target protocol type is a custom protocol type, determine the running context of the currently running application on the display device.

[0097] The application's runtime context can be understood as a collection of at least one of the following data: state information, environment variables, resource access permissions, and execution state, which the currently running application depends on for the correct execution.

[0098] For example, the type of runtime context may include at least one of the following: HbbTV Context (Hybrid BroadcastBroadband TV Context), OpApp Context (Operator Application Runtime Context), and Normal Context (Normal Runtime Context).

[0099] Optionally, the HbbTV Context type only allows the execution of custom broadcast protocols, i.e., custom "dvb: / / protocol".

[0100] Optionally, the OpApp Context type only allows the execution of carrier application protocols, i.e., "opapp: / / protocol".

[0101] Optionally, the Normal Context type corresponds to an open Browser application, which allows you to enter any URL in the address bar, does not allow the execution of custom protocols, and prevents malicious attacks from the source.

[0102] S530. Based on the first preset matching relationship, determine the matching result between the target protocol type and the runtime context; and perform security checks on the content loading request.

[0103] The matching results may include a first matching result and a second matching result. The first matching result indicates that the target protocol type matches the runtime context, and the second matching result indicates that the target protocol type does not match the runtime context.

[0104] In some embodiments, a reference protocol type matching the runtime context can be determined based on a first preset matching relationship. If the reference protocol type includes the target protocol type, the matching result is determined as a first matching result, which indicates that the target protocol type matches the runtime context. If the reference protocol type does not include the target protocol type, the matching result is determined as a second matching result, which indicates that the target protocol type does not match the runtime context.

[0105] The reference protocol type can be understood as the protocol type predefined for the runtime context. For example, the reference protocol type corresponding to the HbbTVContext type is a custom broadcast protocol; the reference protocol type corresponding to the OpApp Context type is a carrier application protocol.

[0106] For example, a first preset matching relationship can be pre-constructed, thereby determining a reference protocol type that matches the runtime context based on the first preset matching relationship; then, the reference protocol type is compared with the target protocol type to determine the matching result.

[0107] Security checks can be understood as security verification processes performed on content loading requests to ensure that resource requests and access behaviors comply with predetermined security policies.

[0108] In some embodiments, the security detection methods for content loading requests may include at least one of the following: security detection conforming to the H5 (HyperTextMarkup Language 5) cross-domain standard, security detection conforming to the cross-domain standard of a proprietary protocol, and whitelist security detection. Optionally, if the content loading request passes the security detection by any of the above security detection methods, it can be determined that the content loading request has passed the security detection.

[0109] In some embodiments, the regional CORS (Cross-Origin Resource Sharing) rules corresponding to the target protocol type can be obtained according to the target protocol type; and the content loading request can be security checked according to the regional CORS rules corresponding to the target protocol type.

[0110] For example, if the matching result is the first matching result, a custom factory instance can be created, independent of the native loader in the browser kernel. The custom factory instance corresponds to the target protocol type; the regionalized CORS rules matching the target protocol type are loaded for the custom class instance. Optionally, the custom class instance can be a ZenixURLLoaderFactory instance.

[0111] S540. If the matching result indicates that the target protocol type matches the runtime context, and the content loading request passes the security check, obtain the target content data corresponding to the content loading request.

[0112] In some embodiments, a target processing process matching the target protocol type can be determined; the target processing process can be invoked to obtain the original content data matching the content loading request, and the original content data can be converted into a preset data format to obtain the target content data.

[0113] The process of determining the target processing process is essentially the process of dynamic routing of the processing process. For example, different processing processes can be pre-defined, with each processing process corresponding to a different target protocol type, resulting in a preset mapping relationship; based on the preset mapping relationship, the target processing process that matches the target protocol type is determined.

[0114] Understandably, by identifying target processing processes that match the target protocol type, secure isolation between different processing processes can be achieved. Furthermore, since different processing processes correspond to different target protocol types—meaning each process handles data processing tasks specific to a particular protocol type—the generalization performance overhead of processing processes can be reduced, thus improving data processing efficiency.

[0115] Optionally, different target processing processes have standardized interfaces, so that different target processing processes only need to complete data acquisition and transmission according to fixed interfaces and parameters, without having to pay attention to the upper-layer implementation logic, which is conducive to improving data processing efficiency and enabling extensions for custom protocols.

[0116] Optionally, a registration request for a custom type of communication protocol can be obtained; in response to the registration request, a preset mapping relationship can be established between the protocol identifier corresponding to the custom type and the processing process to be assigned, thereby enabling rapid expansion of the custom protocol.

[0117] Optionally, a target protocol identifier corresponding to the target protocol type can be determined; and a target processing process matching the target protocol identifier can be determined according to a preset mapping relationship. The preset mapping relationship can be understood as the mapping rules between the target protocol identifier and the processing process instance. For example, the target processing process can be bound to a data return module and transmit target content data through the data return module. For example, the target protocol identifier may include at least one of "dvb" and "opapp". This application does not limit the specific content of the target protocol identifier.

[0118] Optionally, the target processing process can be invoked, and the original content data matching the content loading request can be obtained based on the protocol header of the URL (Uniform Resource Locator) corresponding to the content loading request. The original content data can then be converted into a preset data format to obtain the target content data.

[0119] Optionally, the default data format can be a "mojom::URLResponse" structure compatible with NetworkService. Here, "mojom" can be understood as the Mojo interface definition language, used to standardize inter-process communication interfaces; "URLResponse" can be understood as a Uniform Resource Locator (URL) response, a standardized structure used to encapsulate network response data. "::" represents a namespace resolver. It should be noted that the default data format can be determined by technical personnel as needed, and this application does not impose any limitations on it.

[0120] In some embodiments, a target processing process may be invoked to determine the data storage path of the original content data, wherein the storage unit corresponding to the data storage path stores the data to be loaded corresponding to the target protocol type; the data to be loaded is obtained from the server by a data acquisition process that matches the target protocol type; and, based on the data storage path, the original content data that matches the content loading request is obtained from the data to be loaded.

[0121] Optionally, different data acquisition processes correspond to different target protocol types, and the data acquisition process is used to retrieve the data to be loaded corresponding to the target protocol type from the server. In one implementation, the data acquisition process can retrieve the data to be loaded corresponding to the target protocol type from the server in advance before retrieving the content loading request. In another implementation, the data acquisition process can retrieve the data to be loaded corresponding to the target protocol type from the server after retrieving the content loading request.

[0122] Optionally, the target processing process can parse the required data request path from the URL corresponding to the content loading request; initiate a data request to the data acquisition process corresponding to the target protocol type, the data request including the data request path; the data acquisition process of the target protocol type responds to the data request by returning the data storage path of the original content data to the target processing process; the target processing process reads the original content data, its length, and data type from the corresponding storage unit according to the data storage path; and creates a return value of type "mojom::URLResponse" based on the type and other information in the data request. If the reading is successful, the return value can be set to "200"; if the reading fails, the return value can be set to "404". The return value is the status code, such as an HTTP code. For example, the original content data can be read and converted into target content data in a preset data format, then stored in a buffer for the rendering process to render and display.

[0123] S550: Render and display the target content data on the display device's monitor.

[0124] In some embodiments, a rendering process can be invoked to render and display the target content data on the display device's screen.

[0125] Optionally, the description information of the target content data can be sent to the rendering process; a cross-process data channel can be established between the rendering process and the target content data; the target content data can be written to the write end of the cross-process data channel, and the rendering process can read the target content data from the read end of the cross-process data channel according to the description information; the rendering process can be invoked to render and display the target content data on the monitor.

[0126] For example, the "network::mojom::URLResponse" interface can be bound to pass the Mojo communication file descriptor to the rendering process based on the Mojo communication architecture. The file descriptor may include descriptive information such as the target protocol type and data length corresponding to the target content data.

[0127] For example, a watcher can be created and bound to a cross-process data channel to monitor whether the cross-process data channel is writable. For example, the channel status of the cross-process data channel can be monitored, and if the channel status indicates that the cross-process data channel is full or has reached a preset capacity threshold, it can be determined that the cross-process data channel is not writable, thus preventing data loss from continuing to write at this time.

[0128] In an optional embodiment, if the target protocol type is not a custom protocol type, that is, if the target protocol type is a standard protocol type or a preset content protocol type, the target content data can be loaded through the network stack. The network stack can be a traditional network stack, and this embodiment does not impose any limitations on it.

[0129] In the above embodiments, by acquiring the content loading request and determining the target protocol type of the communication protocol corresponding to the content loading request, a data foundation is provided for subsequently determining the loading method corresponding to different target protocol types. When the target protocol type is a custom protocol type, the running context of the currently running application on the display device is determined, and the matching result between the target protocol type and the running context is determined according to the first preset matching relationship. This associates the target protocol type with the running environment of a specific application scenario, and the compatibility between the target protocol type and the running context can be verified through the matching result. By performing security checks on the content loading request, a dual verification mechanism of protocol compatibility verification and security verification is constructed, which can effectively prevent malicious protocol attacks or illegal data injection. When the matching result indicates that the target protocol type matches the running context, and the content loading request passes the security check, the target content data corresponding to the content loading request is acquired, and the target content data is rendered and displayed on the display. This achieves the loading and visualization of custom protocol type content while ensuring protocol compatibility and security, solving the problems of insufficient support for custom protocols and weak security protection in traditional content loading methods, and improving the compatibility of the display device with diverse data sources and the user experience.

[0130] For ease of understanding, the following illustrative explanation is provided in conjunction with the accompanying drawings. It should be noted that this should not be construed as a limitation on specific content loading methods.

[0131] refer to Figure 5BThe diagram illustrates a flowchart of a content loading method provided in some other embodiments, including: obtaining a content loading request, i.e., obtaining a network request; determining the target protocol type corresponding to the content loading request; if the target protocol type is a standard protocol type, loading the target content data corresponding to the content loading request through the network stack. If the target protocol type is a custom protocol type, the following steps are performed based on the processing engine: determining the running context of the currently running application on the display device through the NetworkService module; determining the matching result between the target protocol type and the running context according to a first preset matching relationship; and performing security checks on the content loading request. The security policy corresponding to the security checks includes cross-domain conditions. If the cross-domain conditions are met, obtaining the original content data corresponding to the content loading request and processing the original content data to obtain the target content data; transmitting the target content data to the rendering process based on the data communication method, and generating a request status. If the cross-domain conditions are not met, access is denied, and a network status response is returned.

[0132] refer to Figure 5C The diagram illustrates the steps for acquiring target content data. Specifically, a Uniform Resource Locator (URI) is obtained by parsing the communication protocol corresponding to the content loading request. After successful URI verification, the request path corresponding to the content loading request is extracted, and an asynchronous request task is created, i.e., an asynchronous request is initiated to the data acquisition process corresponding to the target protocol type. If the asynchronous request times out, a timeout response is generated. If the asynchronous request does not time out, the data status of the original content data in the data generation module is checked based on the data generation module interface (i.e., the data acquisition process interface).

[0133] If the original content data is not ready, wait for a response; if the response times out, generate a timeout response.

[0134] If the original content data is ready, obtain the data storage path of the original content data; if the data storage path does not exist, generate a "404" error message; if the data storage path exists, determine the read permissions; if read permissions are granted, read the original content data, create a response header, return a URIResponse (Uniform Resource Locator Response), and send a data read notification (i.e., callback notification) to the NetworkService, so that the NetworkService reads the original content data in batches, and then performs data transformation on the original content data to obtain the target content data.

[0135] refer to Figure 5DThe diagram illustrates the structure of a network service. The logical architecture of the network service module may include a protocol processing controller 501, a factory creation module 502, a dynamic routing module 503, and a management module 504. The protocol processing controller 501 determines the runtime context of the currently running application on the display device; determines the matching result between the target protocol type and the runtime context based on a first preset matching relationship; and performs security checks on content loading requests. The factory creation module 502 creates a custom factory instance independent of the native loader in the browser kernel, with the custom factory instance corresponding to the target protocol type; and loads regionalized CORS rules matching the target protocol type for the custom class instance. The dynamic routing module 503 determines the target processing process matching the target protocol type to facilitate data transmission via the cross-process return mechanism 505. The management module 504 obtains registration requests for custom type communication protocols; and in response to registration requests, establishes a preset mapping relationship between the protocol identifier corresponding to the custom type and the processing process to be assigned, thereby enabling rapid expansion of custom protocols. It should be noted that this embodiment does not limit the specific logical architecture of the network service module. For example, the protocol processing controller can configure security detection policies and perform security detection on content loading requests through a separate security detection module.

[0136] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment in which the security detection steps for content loading requests are refined.

[0137] See Figure 6A The security detection steps for the content loading request shown include:

[0138] S610. Perform cross-domain security checks on content loading requests using standard protocols.

[0139] Cross-domain security detection of standard protocols can include cross-domain security detection based on H5 standard protocols.

[0140] In some embodiments, when the content loading request type is a subpage request type for the target subpage, the target domain name corresponding to the content loading request is obtained; and the main page domain name of the main page to which the target subpage belongs is determined; if the main page domain name matches the target domain name, the content loading request is determined to pass the security check.

[0141] The request type can include main page request type and subpage request type; the main page request type can be understood as requesting to load the main page content in the main page, and the subpage request type can be understood as requesting to load the subpage content in the subpage under the main page.

[0142] For example, a content loading request can be sent to the server to obtain the server's response; the target domain name corresponding to the content loading request can then be extracted from the response. Optionally, the origin field can be parsed from the header data of the response; the target domain name corresponding to the content loading request can then be extracted from the origin field.

[0143] It is understandable that the communication protocols used by the main page content loaded by the main page and the subpage content loaded by the subpage may be different. Therefore, it is necessary to determine whether the target domain name and the main page domain name match when loading the subpage content, thereby improving the security of data loading.

[0144] Optionally, a preset domain matching table can be used to determine whether the main page domain matches the target domain. For example, if the main page domain does not match the target domain, a cross-domain error message can be displayed.

[0145] For ease of understanding, the following example illustrates the process. It's important to note that this should not be interpreted as a limitation on the specific detection steps. Taking the main page using the DVB protocol as an example, when loading resource files of other protocols (such as HTTPS) via XML (Extensible Markup Language) on the main page, the `origin` field can be parsed from the header returned during the content loading request. Based on the `origin` field and the main page's domain name, it can be determined whether cross-origin requests are allowed. If the `origin` does not match expectations, a cross-origin error is returned.

[0146] S620. Perform cross-domain security checks on content loading requests using private protocols.

[0147] In some embodiments, the target domain name corresponding to the content loading request can be obtained; and the Uniform Resource Locator (URL) corresponding to the content loading request can be extracted; a security domain name matching the URL can be determined according to a second preset matching relationship; and if the security domain name includes the target domain name, the content loading request can be determined to pass the security check.

[0148] For example, the aforementioned secure domain name can be understood as the domain name allowed for loading target content data (i.e., loading the current program).

[0149] Optionally, parsing modules corresponding to different protocol types can be pre-set. When playing target content data, the parsing module of the corresponding protocol type is called to parse a list of secure domain names for the current interface from the bitstream. The list of secure domain names includes at least one secure domain name.

[0150] For ease of understanding, the following example is provided. It is important to note that this should not be interpreted as a limitation on specific detection steps. Taking the dvb: / / extended protocol as an example, the "hbbtv module" can be called to parse the list of secure domains for the current interface from the playing broadcast stream; that is, the list of secure domains matching the Uniform Resource Locator (URL). It then determines whether the target domain is within the allowed list of secure domains. If it is not within the list, data loading is refused, and an error code "403" is returned. If it is within the list, the content loading request passes the security check. The "hbbtv module" is the parsing module corresponding to the hbbtv (Hybrid Broadcast Broadband TV) type.

[0151] S630: Perform whitelist security checks on content loading requests.

[0152] In some embodiments, the target domain name corresponding to the content loading request can be obtained; if the target domain name is included in the preset domain name whitelist, it can be determined that the content loading request passes the security check.

[0153] In some embodiments, the final detection result for the content loading request can be determined based on at least one of the cross-domain security detection results of standard protocols, cross-domain security detection results of proprietary protocols, and whitelist security detection results.

[0154] The security detection steps for the content loading request mentioned above may include at least one of S610, S620, and S630. Furthermore, this embodiment does not impose any limitation on the execution order of S610, S620, and S630.

[0155] refer to Figure 6B The diagram shows a flowchart of the security detection process in some other embodiments. Cross-domain security detection for standard protocols, cross-domain security detection for proprietary protocols, and whitelist security detection can be performed separately; the security detection results are determined by a decision center. Specifically, if any one of the cross-domain security detections for standard protocols, proprietary protocols, and whitelist security detections is passed, the security detection step for the content loading request is approved, and the subsequent loading process is executed; if none of the cross-domain security detections for standard protocols, proprietary protocols, and whitelist security detections are passed, the content loading request is blocked.

[0156] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment in which the above content loading method can be implemented through the interaction between different processes.

[0157] See Figure 7A The following is a timing diagram of the content loading method in some embodiments, including:

[0158] S701, The protocol processing process obtains the content loading request and determines the target protocol type of the communication protocol corresponding to the content loading request.

[0159] S702. When the target protocol type is determined to be a custom protocol type, the protocol processing process obtains the runtime context of the currently running application on the display device.

[0160] S703, The protocol processing process determines the matching result between the target protocol type and the runtime context based on the first preset matching relationship; and performs security checks on the content loading request.

[0161] S704. If the protocol processing process determines that the matching result indicates that the target protocol type matches the runtime context, and the content loading request passes the security check, it determines the target processing process that matches the target protocol type.

[0162] S705, The protocol processing process calls the target processing process and sends a data acquisition request to the data acquisition process corresponding to the target protocol type.

[0163] For example, the protocol processing process can send a call request to the target processing process, so that the target processing process responds to the call request by sending a data acquisition request to the data acquisition process corresponding to the target protocol type.

[0164] S706. In response to a data acquisition request, the data acquisition process sends the data storage path corresponding to the data acquisition request to the protocol processing process or the target processing process.

[0165] S707: The protocol processing process calls the target processing process, reads the original content data from the storage unit according to the data storage path, and converts the original content data into target content data in a preset data format.

[0166] S708, The protocol processing process sends description information of the target content data to the rendering process.

[0167] S709, The protocol processing process establishes a cross-process data channel between the rendering process and the target content data is written to the write end of the cross-process data channel.

[0168] S710: The rendering process reads the target content data from the read end of the cross-process data channel based on the description information.

[0169] refer to Figure 7BThe diagram illustrates the process of writing target content data. The protocol processing process can pass a buffer to the target processing process (browser side). The target processing process writes the target content data into the buffer and, through its corresponding processing engine (browser side), writes the target content data to the write end of the cross-process data channel based on mojO communication. This allows the rendering process to read the target content data from the read end of the cross-process data channel. The rendering process is the renderer on the Render side.

[0170] S711, the rendering process renders the target content data and displays it on the monitor.

[0171] Based on the technical solutions of the above embodiments, the content loading method is described in detail.

[0172] refer to Figure 8 The diagram shown is a flowchart of a content loading method in some other embodiments, including:

[0173] S801. Obtain the content loading request and determine the target protocol type of the communication protocol corresponding to the content loading request.

[0174] S802. If the target protocol type is a custom protocol type, determine the running context of the currently running application in the display device.

[0175] S803. Determine the reference protocol type that matches the runtime context based on the first preset matching relationship.

[0176] S804. If the reference protocol type includes the target protocol type, determine the matching result as the first matching result. The first matching result is used to indicate that the target protocol type matches the runtime context.

[0177] S805. Perform security checks on content loading requests.

[0178] S806. If the matching result indicates that the target protocol type matches the runtime context, and the content loading request passes the security check, determine the target processing process that matches the target protocol type.

[0179] S807. Invoke the target processing process to determine the data storage path of the original content data. The storage unit corresponding to the data storage path stores the data to be loaded that corresponds to the target protocol type. The data to be loaded is obtained from the server by the data acquisition process that matches the target protocol type.

[0180] S808. Based on the data storage path, retrieve the original content data that matches the content loading request from the data to be loaded.

[0181] S809. Convert the original content data into a preset data format to obtain the target content data.

[0182] S810: Send the description information of the target content data to the rendering process; establish a cross-process data channel with the rendering process.

[0183] S811. Write the target content data to the write end of the cross-process data channel, and read the target content data from the read end of the cross-process data channel by the rendering process according to the description information.

[0184] S812, Invoke the rendering process to render and display the target content data on the monitor.

[0185] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0186] Based on the same inventive concept, this application also provides a content loading apparatus for implementing the content loading method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more content loading apparatus embodiments provided below can be found in the limitations of the content loading method described above, and will not be repeated here.

[0187] In one exemplary embodiment, such as Figure 9 As shown, a content loading device is provided, including: a first acquisition module 910, a first determination module 920, a second determination module 930, a second acquisition module 940, and a display module 950, wherein:

[0188] The first acquisition module 910 is used to acquire the content loading request and determine the target protocol type of the communication protocol corresponding to the content loading request;

[0189] The first determining module 920 is used to determine the running context of the currently running application in the display device when the target protocol type is a custom protocol type;

[0190] The second determining module 930 is used to determine the matching result between the target protocol type and the runtime context based on the first preset matching relationship; and to perform security checks on the content loading request;

[0191] The second acquisition module 940 is used to acquire the target content data corresponding to the content loading request when the matching result indicates that the target protocol type matches the runtime context and the content loading request passes the security check.

[0192] Display module 950 is used to render and display target content data on the monitor of a display device.

[0193] In one embodiment, the second determining module 930 includes: a first determining unit, configured to determine a reference protocol type that matches the runtime context according to a first preset matching relationship; a second determining unit, configured to determine the matching result as a first matching result when the reference protocol type includes the target protocol type, the first matching result indicating that the target protocol type matches the runtime context; and a third determining unit, configured to determine the matching result as a second matching result when the reference protocol type does not include the target protocol type, the second matching result indicating that the target protocol type does not match the runtime context.

[0194] In one embodiment, the second acquisition module 940 includes: a fourth determining unit, used to determine a target processing process that matches the target protocol type; and a first acquisition unit, used to call the target processing process, acquire the original content data that matches the content loading request, and convert the original content data into a preset data format to obtain the target content data.

[0195] In one embodiment, the first acquisition unit includes: a first determining subunit, configured to invoke a target processing process to determine the data storage path of the original content data, wherein the storage unit corresponding to the data storage path stores data to be loaded corresponding to the target protocol type; the data to be loaded is obtained from the server by a data acquisition process matching the target protocol type; and the first acquisition subunit is configured to obtain the original content data matching the content loading request from the data to be loaded according to the data storage path.

[0196] In one embodiment, the fourth determining unit includes: a second determining subunit, used to determine a target protocol identifier corresponding to a target protocol type; and a third determining subunit, used to determine a target processing process that matches the target protocol identifier according to a preset mapping relationship.

[0197] In one embodiment, the above apparatus further includes: a third acquisition module, configured to acquire a registration request for a custom type of communication protocol; and a processing module, configured to, in response to the registration request, establish a preset mapping relationship between the protocol identifier corresponding to the custom type and the processing process to be assigned.

[0198] In one embodiment, the display module 950 includes: a sending unit for sending description information of target content data to the rendering process; a first processing unit for establishing a cross-process data channel with the rendering process; a second processing unit for writing target content data to the write end of the cross-process data channel, and reading target content data from the read end of the cross-process data channel by the rendering process according to the description information; and a display unit for calling the rendering process to render and display the target content data on the display.

[0199] In one embodiment, the second determining module 930 includes: a second obtaining unit, configured to obtain the target domain name corresponding to the content loading request; a third processing unit, configured to extract the Uniform Resource Locator (URL) corresponding to the content loading request; a fifth determining unit, configured to determine the security domain name matching the URL according to a second preset matching relationship; and a sixth determining unit, configured to determine that the content loading request passes the security detection if the security domain name includes the target domain name.

[0200] In one embodiment, the second determining module 930 includes a seventh determining unit and / or an eighth determining unit; the seventh determining unit is used to obtain the target domain name corresponding to the content loading request when the request type of the content loading request is a subpage request type for the target subpage; and to determine the main page domain name of the main page to which the target subpage belongs; and to determine that the content loading request passes the security test when the main page domain name matches the target domain name; the eighth determining unit is used to obtain the target domain name corresponding to the content loading request; and to determine that the content loading request passes the security test when the target domain name is included in the preset domain name whitelist.

[0201] Each module in the aforementioned content loading device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0202] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 10As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a content loading method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0203] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0204] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0205] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0206] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0207] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0208] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0209] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A display device, characterized in that, include: The display is configured to show the target content data; The controller, connected to the display, is configured to: Obtain the content loading request and determine the target protocol type of the communication protocol corresponding to the content loading request; If the target protocol type is a custom protocol type, determine the running context of the currently running application in the display device; Based on the first preset matching relationship, determine the matching result between the target protocol type and the runtime context; And perform security checks on the content loading requests; If the matching result indicates that the target protocol type matches the runtime context, and the content loading request passes the security check, the target content data corresponding to the content loading request is obtained; The target content data is rendered and displayed on the monitor.

2. The display device according to claim 1, characterized in that, When the controller executes the step of determining the matching result between the target protocol type and the runtime context based on the first preset matching relationship, it is configured to: Based on the first preset matching relationship, determine the reference protocol type that matches the running context; If the reference protocol type includes the target protocol type, the matching result is determined to be a first matching result, which is used to indicate that the target protocol type matches the runtime context; If the target protocol type is not included in the reference protocol type, the matching result is determined to be a second matching result, which indicates that the target protocol type does not match the runtime context.

3. The display device according to claim 1, characterized in that, When the controller executes the process of obtaining the target content data corresponding to the content loading request, it is configured to: Determine the target processing process that matches the target protocol type; The target processing process is invoked to obtain the original content data that matches the content loading request, and the original content data is converted into a preset data format to obtain the target content data.

4. The display device according to claim 3, characterized in that, When the controller executes the call to the target processing process to obtain the original content data matching the content loading request, it is configured to: The target processing process is invoked to determine the data storage path of the original content data. The storage unit corresponding to the data storage path stores the data to be loaded that corresponds to the target protocol type. The data to be loaded is obtained from the server by a data acquisition process that matches the target protocol type; and, Based on the data storage path, the original content data matching the content loading request is obtained from the data to be loaded.

5. The display device according to claim 3, characterized in that, When executing a target processing process that matches the target protocol type, the controller is configured to: Determine the target protocol identifier corresponding to the target protocol type; Based on the preset mapping relationship, the target processing process that matches the target protocol identifier is determined.

6. The display device according to claim 5, characterized in that, The controller is also configured to: Retrieve registration requests for custom communication protocols; In response to the registration request, a preset mapping relationship is established between the protocol identifier corresponding to the custom type and the processing process to be assigned.

7. The display device according to any one of claims 1-6, characterized in that, When the controller executes the step of rendering and displaying the target content data on the display, it is configured to: Send the description information of the target content data to the rendering process; and Establish a cross-process data channel with the rendering process; The target content data is written to the write end of the cross-process data channel, and the rendering process reads the target content data from the read end of the cross-process data channel according to the description information. The rendering process is invoked to render and display the target content data on the monitor.

8. The display device according to any one of claims 1-6, characterized in that, When performing the security check on the content loading request, the controller is configured to: Obtain the target domain name corresponding to the content loading request; and, Extract the Uniform Resource Locator (URL) corresponding to the content loading request; Based on the second preset matching relationship, determine the security domain name that matches the Uniform Resource Locator; If the security domain includes the target domain, the content loading request is determined to have passed the security check.

9. The display device according to any one of claims 1-6, characterized in that, When performing the security check on the content loading request, the controller is configured to perform at least one of the following: If the content loading request type is a subpage request type for the target subpage, obtain the target domain name corresponding to the content loading request; and determine the main page domain name of the main page to which the target subpage belongs. If the main page domain name matches the target domain name, the content loading request is determined to have passed the security check. Obtain the target domain name corresponding to the content loading request; If the target domain name is included in the preset domain name whitelist, the content loading request is determined to pass the security check.

10. A content loading method, characterized in that, include: Obtain the content loading request and determine the target protocol type of the communication protocol corresponding to the content loading request; If the target protocol type is a custom protocol type, determine the running context of the currently running application on the display device; Based on the first preset matching relationship, determine the matching result between the target protocol type and the runtime context; And perform security checks on the content loading requests; If the matching result indicates that the target protocol type matches the runtime context, and the content loading request passes the security check, the target content data corresponding to the content loading request is obtained; The target content data is rendered and displayed on the monitor of the display device.

Images