Terminal display control system and method for cloud centralized management

Abstract

The invention provides a terminal display control system and method for cloud centralized management. Comprising a cloud management platform used for generating a playing task and a remote control instruction; the secure communication unit is used for establishing encrypted two-way communication connection between the cloud management platform and the terminal display equipment; the terminal control agent is used for receiving and analyzing the playing task to obtain a content resource identifier and a playing strategy parameter; the display rendering component is used for loading, rendering and outputting the content resources in the local cache according to the playing strategy parameters; the off-line continuous playing and synchronizing component is used for continuously executing content display based on the content resources in the local cache and the playing task when the two-way communication connection is interrupted; and after the two-way communication connection is recovered, requesting the cloud management platform to synchronize a playing task and a remote control instruction associated with the terminal display equipment. According to the invention, the cross-network centralized management and control efficiency is improved, the real-time performance of content issuing and updating is improved, and the display continuity and the operation and maintenance performance of an off-network scene are enhanced.

Description

Cloud-based centralized management terminal display control system and method Technical Field

[0001] This application relates to the field of intelligent technology, and in particular to a cloud-based centralized management terminal display control system and method. Background Technology

[0002] With the development of information technology and intelligent applications, large-screen display devices are widely used in scenarios such as industrial control, commercial advertising, conference presentations, security monitoring, and education and training to present various types of content, including real-time data, images, videos, reports, and web pages. In multi-point deployment environments, the number of terminals and content types continue to grow. The operation and maintenance side usually needs to perform unified management, remote control, resource scheduling, and content updates for distributed terminals to meet the needs of batch operation and maintenance across regions and networks.

[0003] In existing technologies, common solutions include: changing content locally on the terminal via mouse, keyboard, or storage media; distributing materials and playback schedules within a local area network (LAN) using playback control software; distributing, scheduling, and monitoring advertising screens via cloud-based platforms; and directly taking over the terminal desktop for operation using remote desktop. While these solutions have some applicability in different scenarios, they still have shortcomings: local control struggles to achieve remote batch operations; LAN distribution relies on the same network environment, making it difficult to support cross-network segments or public network remote access; cloud-based advertising delivery systems are typically geared towards specific business processes, making it difficult to cover unified scheduling and version management of multiple content types; remote desktop control has coarse granularity, higher security risks, and lacks access control and log auditing. With the increasing scale of terminals and the growing complexity of content, existing solutions also generally suffer from low content update efficiency, fragmented resources that are difficult to manage uniformly, insufficient status monitoring and anomaly feedback mechanisms, and limited compatibility and scalability. Summary of the Invention

[0004] In view of this, embodiments of this application provide a cloud-based centralized management terminal display control system and method to solve the problems of difficulty in cross-network centralized access management, low efficiency of remote distribution and synchronous update of playback tasks, and lack of offline resume playback and status feedback mechanisms in the prior art.

[0005] The first aspect of this application provides a cloud-based centralized management terminal display control system, comprising: a cloud management platform for centralized access management of terminal display devices, generating playback tasks based on content publishing configuration input by the management terminal, and generating remote control commands for the terminal display devices; a secure communication unit for establishing an encrypted bidirectional communication connection between the cloud management platform and the terminal display devices, enabling the cloud management platform to send playback tasks and remote control commands to the terminal display devices through the bidirectional communication connection, and receiving operating status and task execution information reported by the terminal display devices; and a terminal control agent for completing identity authentication with the cloud management platform and maintaining the connection through the bidirectional communication connection; receiving and parsing playback tasks to obtain content resource identifiers and playback strategy parameters, obtaining corresponding content resources according to the content resource identifiers and writing them to a local cache; and, upon meeting the following conditions... When the playback strategy parameters are triggered, the display rendering component loads content resources from the local cache for display. It receives and parses remote control commands and calls the terminal-side interface to execute the corresponding control operations. The display rendering component, deployed on the terminal display device, responds to the scheduling of the terminal control agent and loads and renders content resources from the local cache according to the playback strategy parameters. The offline playback and synchronization component, deployed on the terminal display device, continues content display based on the content resources and playback tasks in the local cache when the two-way communication connection is interrupted, and caches task execution records and exception information generated during the interruption. After the two-way communication connection is restored, it reports the task execution records and exception information to the cloud management platform and requests the synchronization of playback tasks and remote control commands associated with the terminal display device from the cloud management platform.

[0006] The second aspect of this application provides a cloud-based centralized management terminal display control method based on the system of the first aspect, comprising: receiving content publishing configuration input from a management terminal by a cloud management platform; generating a playback task associated with a target terminal display device based on the content publishing configuration; and generating remote control instructions for the target terminal display device; establishing an encrypted bidirectional communication connection between the cloud management platform and the target terminal display device; and sending the playback task and remote control instructions to the target terminal display device through the bidirectional communication connection; and having a terminal control agent of the target terminal display device complete identity authentication with the cloud management platform and maintain the connection through the bidirectional communication connection, and receive and parse the playback task to obtain content resource identifiers and playback strategy parameters. The system retrieves the corresponding content resource based on the content resource identifier and writes it to the local cache. When the triggering conditions defined by the playback strategy parameters are met, the system schedules the display rendering component to load the content resource in the local cache according to the playback strategy parameters and renders it. The system receives and parses remote control commands, calls the terminal-side interface to execute the control operation corresponding to the remote control command. When the two-way communication connection is interrupted, the system continues to display content based on the content resource and playback task in the local cache, and caches the task execution records and exception information generated during the two-way communication connection interruption. After the two-way communication connection is restored, the system reports the task execution records and exception information to the cloud management platform and requests the synchronization of the playback task and remote control command associated with the target terminal display device.

[0007] The at least one technical solution adopted in this application embodiment can achieve the following beneficial effects: A cloud management platform is used for centralized access management of terminal display devices, generating playback tasks based on content publishing configuration input from the management terminal, and generating remote control instructions for the terminal display devices; a secure communication unit is used to establish an encrypted bidirectional communication connection between the cloud management platform and the terminal display devices, enabling the cloud management platform to send playback tasks and remote control instructions to the terminal display devices through the bidirectional communication connection, and to receive the running status and task execution information reported by the terminal display devices; a terminal control agent is used to complete identity authentication with the cloud management platform and maintain the connection through the bidirectional communication connection; receiving and parsing playback tasks to obtain content resource identifiers and playback strategy parameters, obtaining corresponding content resources according to the content resource identifiers and writing them to the local cache; and meeting playback requirements. The strategy parameters define the trigger conditions for scheduling the display rendering component to load and display content resources from the local cache; receiving and parsing remote control commands and calling the terminal-side interface to execute control operations corresponding to the remote control commands; the display rendering component, deployed on the terminal display device, is used to respond to the scheduling of the terminal control agent and load and render content resources from the local cache according to the playback strategy parameters; the offline playback and synchronization component, deployed on the terminal display device, is used to continue content display based on content resources and playback tasks in the local cache when the two-way communication connection is interrupted, and to cache the task execution records and exception information generated during the two-way communication connection interruption; after the two-way communication connection is restored, the task execution records and exception information are reported to the cloud management platform, and the cloud management platform is requested to synchronize the playback tasks and remote control commands associated with the terminal display device. This application can improve the efficiency of cross-network centralized management and control, improve the real-time performance of content distribution and updates, and enhance the continuity and maintainability of display in network outage scenarios. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of this application, 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.

[0009] Figure 1 is a schematic diagram of the structure of the cloud-centralized terminal display control system provided in the embodiment of this application; Figure 2 is a schematic diagram of the cloud-centralized terminal display control method provided in the embodiment of this application. Detailed Implementation

[0010] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0011] With the development of informatization and intelligentization, large-screen display equipment is widely used in industrial control, commercial advertising, conference presentations, security monitoring, education and training, and other scenarios. These large-screen terminals typically need to display various types of content, including real-time data, images, videos, reports, and web pages. In multi-site deployment environments (such as multiple factories, branch offices, or advertising screen locations), how to uniformly manage, remotely control, schedule resources, and update content for these distributed large screens has become a core issue in system operation and maintenance.

[0012] Traditional solutions often rely on manual operation or local area network control, which cannot meet the needs of cross-network, cross-regional, batch management and real-time updates. As the number of devices and the complexity of content increase, the lack of an effective remote management mechanism will lead to resource waste, content lag, system maintenance difficulties, and even affect the timeliness and accuracy of production decisions or information dissemination.

[0013] Currently, there are several main solutions for controlling and managing content on large-screen display devices: 1. Local control method: directly change the displayed content via mouse and keyboard, USB flash drive, or local operating system interface.

[0014] 2. Local Area Network-based Content Distribution System: The management terminal and the display terminal are on the same network, and the media and playback schedules are distributed through playback control software under the local area network.

[0015] 3. Cloud-based advertising delivery system: Utilizing cloud platforms and IoT technology, this system enables remote distribution, scheduling, and monitoring of advertising materials on advertising screens, primarily used in the commercial advertising sector.

[0016] 4. Remote desktop-based control method: Control the large screen system directly by operating the desktop via remote desktop, VNC, etc.

[0017] However, existing technologies still have the following drawbacks: 1. Coarse control granularity and poor real-time performance: Local control methods cannot achieve remote batch operations; LAN solutions rely on the network environment and do not support remote operation across network segments or the public network.

[0018] 2. Low content update efficiency: A large amount of material needs to be manually transferred, and there is a lack of incremental update mechanism; content cannot be automatically updated according to task schedule or trigger conditions.

[0019] 3. Inconsistent resource management: Resources on different terminals are distributed across their respective systems, lacking centralized resource management; it is difficult to track the status, version, or playback history of the displayed content.

[0020] 4. Insufficient security and controllability: Remote desktop methods pose security risks; lack access control and log auditing mechanisms.

[0021] 5. Lack of scalability: Most solutions are adapted to a single platform or a specific brand, making it difficult to be compatible with multiple hardware devices and system versions.

[0022] In view of the problems existing in the prior art, this application provides a cloud-based terminal display control system and method to realize remote control and resource distribution of large-screen display devices. This application aims to solve the following technical problems: 1. Provide a method for remote control and resource management of large-screen display terminals that is cross-network, centralized, and real-time; 2. Achieve unified scheduling and synchronous updates for multiple terminals and multiple content types; 3. Improve the reliability, security, and scalability of content distribution and display; 4. Implement a mechanism for monitoring the operating status of display terminals, managing content versions, and providing anomaly feedback.

[0023] This system mainly consists of the following parts: 1. Cloud management platform, a web application located on the server side, including device management module, content configuration module, task scheduling module, remote control module and resource distribution module.

[0024] The device management module is responsible for device registration, grouping, and status monitoring; the content configuration module is used to upload and edit resources to be published (images, videos, HTML pages, etc.) and their playback strategies; the task scheduling module generates playback tasks according to preset plans and associates tasks with corresponding devices to achieve timed or real-time content publishing; the remote control module receives control commands initiated by the management terminal (such as adjusting screen brightness, restarting the device, etc.) and sends them to the target devices; the resource distribution module is responsible for pushing the content to be played to the terminal or allowing the terminal to actively retrieve it, and ensuring the integrity of the content. The cloud platform maintains two-way message interaction with each terminal through a secure communication channel.

[0025] 2. Terminal Display Devices: These include hardware such as large-screen displays and televisions running the Android system, as well as a pre-installed integrated control app. This app runs on the terminal display devices and consists of two main functional modules: 1) Control Agent Module: This module maintains the network connection with the cloud platform (supporting protocols such as MQTT / WebSocket), completes registration and authentication upon device startup, and periodically sends heartbeats to stay online; it also listens for and parses instructions and tasks sent from the cloud. Upon receiving a playback task, the agent module first retrieves the corresponding resources via HTTP or MQTT and stores them in a local cache to ensure subsequent playback needs; then, it triggers the display module to switch content at a specified time. The agent module also receives control commands and calls the underlying system interface to perform operations such as brightness adjustment and remote restart, and promptly reports the execution results and device status (such as online / offline status, playback status, error messages, etc.) to the cloud.

[0026] 2) Display Rendering Module: Based on the WebView component, this module displays cached or remote resources. It can load local or remote web pages and multimedia files, rendering images, videos, HTML pages, real-time data charts, flowcharts, and other content. Whenever the proxy module triggers a playback task, the display module loads the corresponding content resources through WebView and displays them in full-screen mode, ensuring the content is presented in the specified format and layout.

[0027] The interaction logic and communication of this system include the following: The cloud management platform and the terminal agent adopt a publish / subscribe and bidirectional communication mechanism, supporting both MQTT and WebSocket protocols.

[0028] The MQTT protocol is a lightweight publish / subscribe messaging protocol based on TCP / IP, which is well-suited for message distribution in IoT devices, primarily used for distributing playback tasks and control commands.

[0029] The WebSocket protocol allows for the establishment of persistent, full-duplex TCP connections between clients and servers, making it suitable for command push and status updates with high real-time requirements. After the terminal agent starts, it first completes a handshake authentication with the cloud and maintains a connection with the message server.

[0030] When the cloud issues commands to online devices, it sends them via MQTT or WebSocket channels. The Agent parses the commands and executes the corresponding operations. Simultaneously, the Agent feeds back the collected device status, operation logs, and anomaly information to the cloud through these channels. The cloud platform continuously monitors the received status data, summarizes and analyzes the device's operating status, and displays the results in a visual format on the management interface.

[0031] Furthermore, the data synchronization and offline support of this application include: to ensure continuous playback in the event of network instability or network outage, the terminal agent module is designed with local caching and a mechanism for resuming playback after network outage.

[0032] During normal communication, the Agent proactively downloads and caches the content resources to be played to local storage (using a file system or database) and keeps data synchronized with the cloud. When the network is interrupted, the Agent can still use the cached resources to continue playing as planned, without interrupting the display due to network outage; at the same time, the Agent will periodically attempt to re-establish the network connection and cache the logs and status during the network outage locally.

[0033] Once the network is restored, the Agent immediately reconnects to the cloud, reports cached logs and offline playback records to the cloud, and requests synchronization of the latest playback tasks and control commands.

[0034] Through this caching and recovery mechanism, the system can continue to operate in unreliable network environments, ensuring that critical content is displayed as planned.

[0035] Furthermore, the task scheduling process of this application includes: the task scheduling module of the cloud management platform is responsible for generating and issuing playback tasks, and the process is generally as follows: 1. Task creation: the administrator configures and publishes tasks on the platform, including selecting the target device, specifying the playback content, setting the playback time period and loop mode (such as single playback or loop playback).

[0036] 2. Task distribution: After the platform associates the created task with the device, it immediately or periodically sends the task notification to the corresponding device agent via MQTT / WebSocket.

[0037] 3. Resource caching: The Agent that receives the task downloads the corresponding resource file (or web address) in advance according to the task information and stores it locally to ensure that the resources are ready when the playback time arrives.

[0038] 4. Task Execution: When the specified playback time arrives, the Agent triggers the display module to load and display the locally cached content. After playback ends, if the task is set to loop, the next playback cycle will continue; if the task has subsequent tasks, the Agent will continue to parse and execute them.

[0039] 5. Feedback Reports: At the start and end of task execution, the Agent reports the execution results and playback status to the cloud. The platform records the task execution status for administrators to query or troubleshoot.

[0040] The above process not only supports scheduled content releases according to a fixed plan, but also supports high-priority instant updates: after the administrator releases an instant task through the platform, the cloud immediately pushes the command to the online device, and the Agent immediately pauses the current playback task and switches to the new task upon receiving it, thus achieving rapid content updates.

[0041] Furthermore, the anomaly handling mechanism of this application includes: the system is designed with a multi-level anomaly detection and handling strategy: 1. The terminal agent monitors its own operation status. When anomalies such as download failure or playback error occur, it will automatically retry (e.g., re-download the resource or revert to the previous valid content); if it fails repeatedly, it will record the error log and report it to the cloud.

[0042] 2. In case of device disconnection or serious failure, the cloud platform can mark the device as offline and notify the operation and maintenance personnel after monitoring the device for more than the preset heartbeat time limit.

[0043] 3. The platform also provides remote diagnostic functions, which can query device logs, remotely observe device status, or issue commands such as clearing cache and restarting the App to help quickly locate and recover from problems.

[0044] 4. Regarding terminal applications, the App integrates crash capture and automatic restart mechanisms. In the event of an unexpected crash, it can automatically restart critical modules or the entire application to ensure the continuous operation of the display business.

[0045] To ensure the safe and stable operation of the system, a number of security strategies have been implemented.

[0046] 1. Regarding communication security, all message transmissions between the cloud and the terminal are conducted through SSL / TLS encrypted channels to prevent man-in-the-middle eavesdropping or data tampering; 2. Devices must undergo identity verification upon initial registration (e.g., using a unique device ID, token, or digital certificate). The cloud implements strict authentication for device access to prevent unauthorized devices from accessing the network; 3. System-level access control is implemented for user operations and command issuance, authorizing only users and modules to perform sensitive operations, and recording all operation logs for auditing purposes.

[0047] 4. Regarding content security, the platform filters and checks uploaded resources to prevent malicious code injection; 5. The WebView module only loads trusted local or remote resources and disables unnecessary script functions when necessary.

[0048] The specific structure and function of the cloud-based centralized management terminal display control system provided in this application embodiment will be described in detail below with reference to the accompanying drawings and specific embodiments. Figure 1 is a schematic diagram of the structural composition of the cloud-based centralized management terminal display control system provided in this application embodiment. As shown in Figure 1, the system may specifically include the following modules: a cloud management platform 101, used for centralized access management of terminal display devices, generating playback tasks based on the content publishing configuration input by the management terminal, and generating remote control instructions for the terminal display devices; a secure communication unit 102, used to establish an encrypted bidirectional communication connection between the cloud management platform and the terminal display devices, enabling the cloud management platform to send playback tasks and remote control instructions to the terminal display devices through the bidirectional communication connection, and to receive the operating status and task execution information reported by the terminal display devices; a terminal control agent 103, used to complete identity authentication with the cloud management platform and maintain the connection through the bidirectional communication connection; receiving and parsing playback tasks to obtain content resource identifiers and playback strategy parameters, and obtaining corresponding content resources based on the content resource identifiers. The system receives and writes content resources to the local cache; when the triggering conditions defined by the playback strategy parameters are met, the display rendering component loads and displays the content resources in the local cache; it receives and parses remote control commands and calls the terminal-side interface to execute the control operations corresponding to the remote control commands; the display rendering component 104, deployed on the terminal display device, is used to respond to the scheduling of the terminal control agent and load and render the content resources in the local cache according to the playback strategy parameters; the offline playback and synchronization component 105, deployed on the terminal display device, is used to continue to execute content display based on the content resources in the local cache and the playback task when the two-way communication connection is interrupted, and caches the task execution records and exception information generated during the two-way communication connection interruption; after the two-way communication connection is restored, the task execution records and exception information are reported to the cloud management platform, and the cloud management platform is requested to synchronize the playback task and remote control commands associated with the terminal display device.

[0049] In some embodiments, the cloud management platform includes a device management module and a task scheduling module; wherein, the device management module is used to complete device registration and group management based on the device identifier of the terminal display device, and maintain online status and running status information associated with the device identifier; the task scheduling module is used to generate playback tasks based on content publishing configuration, and establish association between the playback tasks and the device identifier or device group; the task scheduling module is also used to issue playback tasks according to a preset publishing time, and to issue playback tasks when an immediate publishing request is received.

[0050] Specifically, the device management module predefines the rules for generating and verifying device identifiers. Device identifiers can be at least one of the following: a unique identifier written at the factory, an identifier generated and fixed by the terminal control agent, or an identifier assigned by the cloud. When a terminal display device connects for the first time, the terminal control agent initiates a registration request to the cloud management platform. The registration request carries the device identifier and authentication information associated with the device identifier. After receiving the registration request, the device management module verifies the legality and uniqueness of the device identifier and matches and verifies the authentication information. If the verification is successful, a device file is created for the terminal display device, and access credentials or session information bound to the device identifier are generated for subsequent identity recognition and permission verification in encrypted two-way communication connections. To ensure the operability of subsequent batch management, the device management module also associates device identifiers with configurable organizational structure information, including at least one of factory area identifiers, network identifiers, business domain identifiers, or geographical area identifiers, thereby forming device groups. The management terminal can group multiple terminal display devices into the same device group through filtering conditions or grouping strategies in the device management interface, enabling subsequent playback tasks to be distributed to device groups.

[0051] Regarding online status maintenance, the device management module and the terminal control agent employ a periodic reporting mechanism to maintain online status. Specifically, after completing identity authentication and establishing an encrypted two-way communication connection with the cloud management platform, the terminal control agent reports heartbeat information to the device management module according to a preset heartbeat cycle. The heartbeat information includes at least the device identifier, the reporting time, and the current connection status of the terminal control agent. The device management module updates the timestamp of the received heartbeat information and determines whether the terminal display device is online based on a preset heartbeat time limit. When the device management module does not receive heartbeat information corresponding to the device identifier within the heartbeat time limit, it updates the online status of the device identifier to the offline status and marks the offline alarm status in the management interface.

[0052] Meanwhile, the device management module is also used to maintain operational status information. The operational status information can be carried in the heartbeat information by the terminal control agent or reported in the form of an independent status packet. The operational status information includes at least one of the following: playback status, current playback task identifier, content resource identifier, abnormal type identifier, and storage occupancy status, so that the cloud side can continuously monitor the operation of the terminal side.

[0053] In some examples, the task scheduling module is used to generate playback tasks based on content publishing configuration and associate playback tasks with device identifiers or device groups. The task scheduling module is also used to distribute playback tasks according to preset publishing times and to distribute playback tasks upon receiving an immediate publishing request. Specifically, the management terminal submits content publishing configurations on the cloud management platform. These configurations include at least the target terminal display device identifier or device group, content resource identifiers, and playback strategy parameters.

[0054] After receiving the content publishing configuration, the task scheduling module generates a playback task object corresponding to the content publishing configuration and assigns a task identifier to the playback task object. The playback task object carries at least the task identifier, content resource identifier, target device identifier set or target device group identifier, playback strategy parameters, and publishing type identifier. The publishing type identifier is used to distinguish between scheduled publishing and instant publishing.

[0055] Furthermore, regarding the association processing of playback tasks, the task scheduling module performs device identifier parsing and expansion based on the target object specified in the content publishing configuration. Specifically, when the target object is a device group, the task scheduling module calls the group index provided by the device management module to parse out the set of device identifiers within the device group and binds the set of device identifiers to the playback task object; when the target object is a single device identifier, the task scheduling module directly binds that device identifier to the playback task object. Through the above binding relationship, the cloud management platform can accurately locate the target terminal display device based on the device identifier in the subsequent distribution stage, and can share the same playback task among multiple device identifiers, thereby supporting batch publishing.

[0056] Regarding scheduled delivery, the task scheduling module determines the preset release time based on the playback time period parameter in the playback strategy parameters. The preset release time can be the start time of the playback time period or the prefetch window time before the start time. The task scheduling module writes the playback task object into the delivery queue and triggers the delivery action when the preset release time is reached: on the one hand, the task scheduling module filters out the set of currently online device identifiers based on the online status maintained by the device management module; on the other hand, the task scheduling module encapsulates the playback task object into a task notification message and sends it to the terminal control agent corresponding to the filtered set of device identifiers through the secure communication unit, so that the terminal control agent can obtain the playback task in advance and complete the local caching of content resources, so as to directly call the local cache for display when the playback triggering conditions are met. For device identifiers in an offline state, the task scheduling module can mark the playback task object as pending re-delivery and trigger re-delivery when the device management module detects that the device identifier has come back online, so that the offline device can obtain the playback task associated with it after restoring the connection.

[0057] Regarding real-time delivery, when the task scheduling module receives a real-time release request submitted by the management terminal, it generates a real-time playback task object or updates the release type identifier of an existing playback task object to real-time release, and assigns a real-time delivery identifier to the playback task object. The task scheduling module then skips the timed queue waiting process and directly sends the task notification message to the terminal control agent corresponding to the target device identifier set through the secure communication unit.

[0058] To adapt to the business requirements of real-time updates, in some implementations, the playback task object corresponding to the real-time publishing request can also carry a priority parameter, so that the terminal control agent can pause or switch the currently executing playback task according to the priority parameter after receiving it; for example, when the priority of the real-time publishing request is higher than the priority of the current playback task, the terminal control agent can first cache the content resources of the real-time task after receiving the real-time playback task, and after the caching is completed, trigger the display rendering component to load the content resources corresponding to the real-time task for display, and at the same time record the task identifier and playback progress information of the paused task so as to resume the original task after the real-time task is completed.

[0059] This embodiment focuses on the implementation of the device management module and the task scheduling module, and discloses the specific implementation process and key technical features of the terminal display device, including registration and authentication based on device identifier, group management, online status and operation status maintenance, generation of playback tasks based on content publishing configuration, establishment of association between playback tasks and device identifiers or device groups, issuance of playback tasks according to preset publishing times, and issuance of playback tasks upon receiving an immediate publishing request.

[0060] In some embodiments, the content publishing configuration includes a target terminal display device identifier, a content resource identifier, a playback time period parameter, and a loop mode parameter; the playback task includes a task identifier, a content resource identifier, and playback strategy parameters corresponding to the content publishing configuration, and the playback strategy parameters are used to limit the triggering conditions for the terminal control agent to trigger the display rendering component to execute content display.

[0061] Specifically, the content publishing configuration describes the management's publishing intent regarding "where, what, when, and in what loop." It includes at least the target terminal display device identifier, content resource identifier, playback time period parameters, and looping method parameters. Specifically, the management terminal selects the target terminal display device identifier or the set of device identifiers corresponding to a device group as the publishing object in the content configuration interface of the cloud management platform, and selects the content resource identifier as the content to be published from the resource library. The content resource identifier can point to image files, video files, web pages, or page resources containing real-time data charts, etc.

[0062] The playback time period parameter limits the effective time range of content display, including at least start and end time information. Some implementations may also include extended fields such as date range, weekday rules, or holiday rules. The looping method parameter limits the repetition mechanism of the display, including at least single playback and looping playback. In looping playback scenarios, parameters such as loop period, loop order, or loop interval may also be included. After receiving the above content publishing configuration, the cloud management platform uses it as input to generate playback tasks, forming a deployable, recordable, and traceable task entity on the cloud side.

[0063] In this embodiment, the playback task is a distributed object obtained by the cloud management platform after structurally encapsulating the content publishing configuration. The playback task includes at least a task identifier corresponding to the content publishing configuration, a content resource identifier, and playback strategy parameters. Specifically, after receiving the content publishing configuration, the task scheduling module assigns a task identifier to the content publishing configuration and generates a playback task object. The task identifier is used to uniquely locate the playback task between the cloud and the terminal, and is used for association reference when the terminal reports task execution information.

[0064] The content resource identifier directly references the content resource identifier in the content publishing configuration, and is used to instruct the terminal control agent to obtain the corresponding content resource. The playback strategy parameters are abstracted from the playback time period parameters and the loop mode parameters, and are used on the terminal side to limit the triggering conditions for the display rendering component to execute content display. In some implementations, the playback strategy parameters may also include priority parameters or preemption flags to handle the switching relationship between immediate publishing tasks and the current task; however, in this embodiment, the playback time period and loop mode can be preferentially used as the core limiting factors for the triggering conditions.

[0065] Furthermore, regarding the construction of playback strategy parameters, the cloud management platform typically converts the time and loop information in the content publishing configuration into trigger rules that the terminal control agent can directly execute. Specifically, for playback time period parameters, the task scheduling module can convert start and end time information into trigger window parameters, enabling the terminal control agent to determine locally whether the current time is within the trigger window. For loop mode parameters, the task scheduling module can map "single playback" to a one-time trigger identifier and "looping" to a periodic trigger identifier, and further provide looping period or looping interval parameters in the looping scenario, so that the terminal control agent can continue triggering according to the periodic rules after one trigger ends. To ensure the consistency of task execution, the cloud management platform can also carry the distribution time information bound to the task identifier in the playback task, so that the terminal control agent can determine the validity of the task during reconnection synchronization or offline cache recovery.

[0066] After a playback task is generated, the cloud management platform sends the task to the terminal control agent corresponding to the device identifier on the target terminal via a secure communication unit. Upon receiving the task, the terminal control agent first parses it to extract the task identifier, content resource identifier, and playback strategy parameters. It then writes the task identifier and content resource identifier into the local task index to establish a "task identifier—content resource identifier—playback strategy parameters" association. Subsequently, the terminal control agent retrieves the corresponding content resource based on the content resource identifier and writes it to the local cache component.

[0067] In some examples, the terminal control agent can adopt a "task notification + resource download" approach: when the cloud management platform issues a playback task, it only carries the content resource identifier and its corresponding download information. The terminal control agent downloads the content resource over the network and caches it based on the resource download information. For web page resources, the content resource identifier can correspond to a remote page address or a page file package that can be loaded offline. The terminal control agent selects to download and cache the page file package, or cache the page address and its verification information, depending on the resource type. Through the above caching operations, the terminal control agent can prioritize reading content resources from the local cache component when playback is triggered, reducing its dependence on the real-time network.

[0068] Regarding triggering execution, the terminal control agent determines the triggering conditions based on playback strategy parameters and schedules the display rendering component to display content when the triggering conditions are met. Specifically, the terminal control agent periodically obtains the current time and compares it with the trigger window parameters. When it determines that the current time falls within the time range specified by the playback time period parameters, it confirms that the triggering condition is met. In scenarios where the loop mode is single playback, the terminal control agent marks the task as executed after the first trigger to avoid repeated triggering. In scenarios where the loop mode is looping, the terminal control agent recalculates the next trigger time based on the looping period or looping interval parameters after one display ends, and schedules the display rendering component again when the subsequent trigger time arrives. When scheduling the display rendering component, the terminal control agent outputs content resource loading information and playback strategy parameters corresponding to the content resource identifier to the display rendering component, enabling the display rendering component to complete full-screen rendering output according to the playback strategy parameters and maintain the display during the playback time period or switch content under the looping rules.

[0069] Regarding task status recording, to support traceable management of task execution in the cloud, the terminal control agent can generate task execution status information associated with the task identifier at the start and end of the trigger display, such as "start display", "end display", "display interrupted" and other statuses, and report them to the cloud management platform through the secure communication unit; the cloud management platform will associate and store the task identifier, content resource identifier, trigger time information and task execution status information for subsequent query and diagnosis.

[0070] This embodiment discloses the composition of content publishing configuration fields, the structured encapsulation method of playback tasks, and the triggering execution mechanism of playback strategy parameters on the terminal side. This enables the cloud management platform to uniformly orchestrate and distribute multi-terminal publishing configurations based on task identifiers. The terminal control agent can acquire resources and cache them locally based on content resource identifiers, and schedule the display rendering component to execute content display when the triggering conditions defined by the playback time period parameters and loop mode parameters are met. Through this implementation method, the manageability and consistency of content publishing and display control can be improved, the execution stability of timed publishing and carousel display can be enhanced, and the traceability and troubleshooting efficiency on the operation and maintenance side can be improved by recording and transmitting the task execution status.

[0071] In some embodiments, the cloud management platform generates remote control instructions for the terminal display device, including generating instruction payloads based on the control operation type and control parameters input by the management terminal, and establishing an association between the remote control instructions and the identifier of the target terminal display device; after the terminal control agent calls the terminal-side interface to execute the control operation corresponding to the remote control instructions, it reports the execution result of the control operation and the corresponding time information to the cloud management platform.

[0072] Specifically, the cloud management platform generates remote control commands for terminal display devices. This includes generating command payloads based on the control operation type and control parameters input from the management terminal, and associating the remote control commands with the target terminal display device identifier. Specifically, the cloud management platform provides a remote control entry point on the management terminal interface. Administrators can select the control operation type and fill in the control parameters through this entry point. The control operation type can include at least one of the following: screen brightness adjustment, terminal restart, application restart, clear cache, and switch network configuration. Control parameters can include brightness level, restart mode, cache clearing range, and operation effective time.

[0073] After receiving the control operation type and control parameters, the cloud management platform encapsulates the control request in a structured manner by the remote control module to generate a remote control instruction. The remote control instruction includes at least the instruction identifier, the target terminal display device identifier, the control operation type, the control parameters, and the issuance time information. The instruction identifier is used to track the life cycle of the instruction on the cloud side and to be used for association and reference on the terminal side when reporting the receipt.

[0074] Regarding the generation of command payloads, the cloud management platform selects the corresponding command template based on the control operation type and fills in the control parameters to obtain the command payload. Specifically, for brightness adjustment control operations, the command payload may include the target brightness value, brightness adjustment method, and effective time; for terminal restart control operations, the command payload may include the restart type, delay execution duration, and execution window; for cache clearing control operations, the command payload may include a cache clearing range identifier and a set of reserved resource identifiers; for application restart control operations, the command payload may include a restart target module identifier or application identifier. Through templated encapsulation, the cloud management platform can expand the control operation types without changing the overall parsing framework of the terminal control agent, ensuring the scalability and consistency of remote control commands.

[0075] Regarding the association between remote control commands and target terminal display device identifiers, the cloud management platform supports establishing associations by single device or by device group. Specifically, when the management end selects a device group, the cloud management platform calls the device management module to obtain the set of target terminal display device identifiers corresponding to that group, and establishes association records between the command identifier of the same remote control command and each target terminal display device identifier. When the management end selects a single device, the cloud management platform directly establishes an association record between the remote control command and the target terminal display device identifier. The cloud management platform can maintain command status fields in the association records, such as pending issuance, issued, executed, execution failed, and timeout without response, to facilitate management end querying and maintenance traceability.

[0076] Furthermore, after the remote control command is generated and associated, the cloud management platform sends the remote control command to the target terminal display device through the secure communication unit. The secure communication unit can push the command based on a publish-subscribe message channel or a full-duplex long-connection message channel. For online devices, the cloud management platform encapsulates the remote control command into a command message and pushes it to the receiving channel corresponding to the target terminal display device identifier when sending the command; for offline devices, the cloud management platform can keep the remote control command in a pending state and trigger a resend after the device management module detects that the target terminal display device identifier has returned to online, so as to ensure that the remote control command can still be executed after the device comes back online.

[0077] On the terminal side, the terminal control agent listens for and receives remote control commands issued by the cloud while establishing and maintaining an encrypted two-way communication connection with the cloud management platform. Upon receiving a remote control command, the terminal control agent first parses the command message to extract the command identifier, control operation type, and control parameters, and then selects the corresponding terminal-side interface call path based on the control operation type. Specifically, the terminal control agent pre-maintains a mapping relationship between "control operation type and terminal-side interface," which may include call entry points such as system settings interface, device management interface, application management interface, and local cache management interface.

[0078] Regarding the generation and reporting of execution results, the terminal control agent generates the execution result and corresponding time information of the control operation after completing the control operation, and reports it to the cloud management platform. Specifically, the terminal control agent uses the instruction identifier as the receipt association key to generate a receipt message. The receipt message includes at least the instruction identifier, device identifier, control operation type, execution result identifier, and time information. The time information includes at least one of the following: reception time, start execution time, and execution completion time. The execution result identifier includes at least one of the following: execution successful, execution failed, and failure reason code. In some implementations, the terminal control agent can also carry key status fields after execution in the receipt message, such as the current brightness value after brightness adjustment, the space occupied after cache clearing, and the application version number before restarting, so that the cloud management platform can form a more complete operation and maintenance record. After receiving the receipt message, the cloud management platform matches it with the previously established "remote control instruction - target terminal display device identifier" association record, updates the instruction status field, and records the receipt time information, thereby completing the closed-loop processing of the remote control instruction.

[0079] This embodiment discloses a mechanism for templated generation of remote control commands, association management of commands with target terminal display device identifiers, command issuance based on encrypted bidirectional communication connections, terminal control agents calling terminal-side interfaces to execute control operations, and reporting mechanisms for receipt messages carrying execution results and time information. This enables the cloud management platform to perform traceable remote control operations on distributed terminal display devices. Through this implementation, the response efficiency and batch operation efficiency of cross-regional terminal maintenance can be improved, the monitorability and traceability of the remote control execution process can be enhanced, and the maintenance costs and interruption risks associated with manual on-site operations can be reduced.

[0080] In some embodiments, the secure communication unit employs at least one of a publish-subscribe message channel and a full-duplex long-connection message channel to issue playback tasks and remote control instructions, and to transmit running status and task execution information back; wherein, the publish-subscribe message channel is used to publish playback tasks or remote control instructions to a message topic corresponding to the target terminal display device identifier or device group, and the terminal control agent subscribes to the message topic to receive playback tasks or remote control instructions.

[0081] Specifically, the secure communication unit uses at least one of a publish-subscribe message channel and a full-duplex long-connection message channel to issue playback tasks and remote control commands, and to transmit running status and task execution information back.

[0082] In some examples, the secure communication unit on the cloud side may include a message access service and a connection management service. The message access service is used to carry out message publishing, subscription and push, and the connection management service is used to maintain the connection status, authentication status and session information of the terminal control agent. On the terminal side, the terminal control agent has a built-in message client, which is used to complete handshake authentication, subscribe to message topics, receive and send messages, and send status feedback messages.

[0083] To ensure secure message transmission, the communication link between the cloud and the terminal is carried through an encrypted transmission channel. Before establishing a message channel, the terminal control agent completes identity authentication and obtains available subscription and publishing permissions based on the authentication results, thereby ensuring that only authorized terminals can access the corresponding message channel.

[0084] In some implementations, publish-subscribe messaging channels are used to distribute playback tasks and remote control commands to multiple terminals, which is particularly suitable for scenarios involving batch distribution to device groups. Specifically, after generating a playback task or remote control command, the cloud management platform encapsulates it into a message payload and delivers it to the secure communication unit for publication. The secure communication unit generates a corresponding message topic based on the target terminal's display device identifier or device group, where the message topic is used to logically divide the message reception scope.

[0085] To maintain the stability of topic naming and permission management, message topics can adopt a combination of "device identifier topic" and "group topic": when the target object is a single device, a device topic corresponding one-to-one with the device identifier is generated; when the target object is a device group, a group topic corresponding one-to-one with the device group is generated, and the device identifiers in the group are mapped to subscription relationships to the group topic.

[0086] After completing identity authentication, the terminal control agent initiates a subscription request to the secure communication unit. The subscription request carries its own device identifier and the identifier of the device group to which it belongs. Based on the subscription permission verification result, the secure communication unit binds the terminal control agent to the set of message topics that it can subscribe to, so that it can receive playback tasks or remote control instructions sent to the corresponding message topics.

[0087] In terms of the publishing process, the cloud management platform selects topics and publishes messages separately for playback tasks and remote control commands. Specifically, when the cloud management platform needs to issue a playback task to a group of devices, the secure communication unit publishes the playback task to the group topic. Each terminal control agent subscribed to that group topic receives the task, parses the task identifier, content resource identifier, and playback strategy parameters, and then performs resource caching and triggers display. When the cloud management platform needs to issue a remote control command to a single device, the secure communication unit publishes the remote control command to the corresponding device topic. The terminal control agent receives the command, parses the control operation type and control parameters, and calls the terminal-side interface to execute the control operation. Through topic segmentation, the cloud management platform can cover multiple terminal control agents with the same message publishing action, reducing the complexity of batch publishing.

[0088] In some implementations, full-duplex long-connection message channels are used to handle control and feedback scenarios with higher real-time requirements, such as playback task switching triggered by immediate release requests, instant push of remote control commands, and rapid updates to terminal operating status. Specifically, after startup, the terminal control agent establishes a persistent connection session with the cloud management platform and maintains full-duplex communication within the session. When the cloud management platform needs to issue playback tasks or remote control commands in real time, it can directly push messages to the terminal control agent through this persistent connection without waiting for the next polling or subscription refresh. During task execution, the terminal control agent can also report task execution status information, exception information, and operating status information in a timely manner through this persistent connection, enabling the cloud management platform to present the status changes of each terminal in a near real-time manner in the management interface.

[0089] Regarding message feedback, regardless of whether a publish-subscribe messaging channel or a full-duplex long-connection messaging channel is used, the terminal control agent can encapsulate the running status and task execution information into feedback messages and send them to the cloud management platform. Specifically, the terminal control agent generates and reports a heartbeat message when the heartbeat cycle arrives. The heartbeat message includes at least the device identifier and the reporting time information.

[0090] Upon receiving a playback task, triggering the start of a display, and triggering the end of a display, task execution information is generated and reported. This information includes at least one of the following: task identifier, content resource identifier, playback start time, playback end time, and playback status. When an anomaly is detected in content resource acquisition, content display, or control operation, exception information is generated and reported. This information includes at least the exception type, time information, and context information. On the cloud side, the secure communication unit forwards the returned messages to the device management module and task scheduling module of the cloud management platform. The device management module updates the device's online and operational status, while the task scheduling module records the task execution results and stores them in association with the task identifier for querying and tracing.

[0091] The following example scenario illustrates the collaborative mechanism of the dual-channel system. On the cloud management platform, administrators select a group of equipment in a specific factory area and issue a "Daily Routine Dashboard" playback task. After the task scheduling module generates the playback task, the secure communication unit publishes the task to the group topic. Each terminal control agent within the group subscribes to the topic and receives the task, then downloads and caches the corresponding content resources. If an emergency notification occurs at 15:00 that day requiring all terminals to immediately switch to displaying the "Emergency Notification Page," administrators initiate an immediate release request. The cloud management platform pushes the immediate task message to online terminals via a full-duplex long-connection message channel. Upon receiving the message, the terminal control agent immediately schedules the display rendering component to switch the display, and sends back task execution information at the start and completion of the switch. If some terminals temporarily go offline due to network fluctuations, the equipment management module marks them as offline based on a heartbeat timeout. Once the connection is restored, the terminal control agent re-establishes the session and re-subscribes to the message topic. The cloud management platform then reissues the unfinished tasks to the corresponding topic or pushes them via a long-connection, thus ensuring task consistency.

[0092] This embodiment discloses the topic segmentation and subscription authorization mechanism of the publish-subscribe messaging channel, the persistent session push mechanism of the full-duplex long-connection messaging channel, and the unified mechanism for transmitting operational status and task execution information. This enables scalable distribution of playback tasks and remote control commands to single devices and device groups, and allows terminal operational status and task execution information to be transmitted back to the cloud management platform periodically or in real time. This implementation improves the organizational efficiency of batch distribution across multiple terminals and the responsiveness of real-time command pushes, enhances the visualization and monitoring capabilities of terminal status and operational traceability, and improves the stability and scalability of message interaction across network environments.

[0093] In some embodiments, when a triggering condition defined by the playback strategy parameters is met, the display rendering component is scheduled to load and display content resources in the local cache, including: parsing the playback triggering condition associated with the playback task based on the playback strategy parameters, wherein the playback triggering condition includes a playback time period parameter and / or a loop mode parameter; when the playback triggering condition is met, determining the content resource loading information corresponding to the content resource identifier from the local cache, wherein the content resource loading information includes a local cache path or a loading entry parameter; outputting the content resource loading information and the playback strategy parameters to the display rendering component, so that the display rendering component performs loading and rendering output on the content resource indicated by the content resource loading information according to the playback strategy parameters; and generating task execution status information associated with the playback task during at least one stage of the display rendering component performing loading and rendering output.

[0094] Specifically, after receiving the playback task from the cloud management platform, the terminal control agent first parses the playback task to obtain the task identifier, content resource identifier, and playback strategy parameters associated with the playback task. Then, it downloads the content resource corresponding to the content resource identifier and writes it to the local cache component to ensure that the local cached resources can be directly called when the display is triggered in the future.

[0095] The playback strategy parameters are used to limit the triggering conditions for the terminal control agent to trigger the display rendering component to display content. The triggering conditions include at least one of the playback time period parameters and the loop mode parameters. In some implementations, the playback strategy parameters may also carry playback priority or preemption flags to handle the switching of immediate tasks to predetermined tasks, but this embodiment uses the time period and loop mode as the core triggering constraints for explanation.

[0096] In this embodiment, the terminal control agent parses the playback strategy parameters to obtain the playback triggering conditions associated with the playback task. Specifically, the terminal control agent parses the playback strategy parameters into a set of executable triggering rules, which includes at least trigger window rules and loop triggering rules.

[0097] The trigger window rules are derived from the playback time period parameters. The playback time period parameters include at least start time and end time information. The terminal control agent establishes a local trigger window based on this information to determine whether the current time is within the trigger window. In some implementations, if the playback time period parameters also include date range or workday rules, the terminal control agent further prunes the trigger window in the calendar dimension so that the task only enters the trigger window on dates that meet the date range or workday rules.

[0098] The loop triggering rule is derived from the loop mode parameter, which is used to indicate at least single playback or loop playback. For single playback, the terminal control agent sets a one-time trigger flag for the playback task and updates it to the executed state after the trigger is completed. For loop playback, the terminal control agent generates the calculation rule for the next trigger time based on the loop period or loop interval parameter, so that the playback task can be repeatedly triggered in the trigger window.

[0099] In this embodiment, when the playback trigger condition is met, the terminal control agent determines the content resource loading information corresponding to the content resource identifier from the local cache component. Specifically, the terminal control agent maintains a content resource index locally. This index is used to establish a mapping relationship between the content resource identifier and the local cache path, and may include content resource type information and verification information. After determining that the trigger condition is met, the terminal control agent queries the content resource index based on the content resource identifier to obtain the content resource loading information.

[0100] Content resource loading information includes at least a local cache path or loading entry parameters. The local cache path instructs the display rendering component to load the corresponding content resource from the terminal file system or application storage space. The loading entry parameters instruct the display rendering component to select the appropriate loading entry point. For example, for web page resources, the loading entry parameters may include the local page entry address or page file package entry; for image or video resources, the loading entry parameters may include the media resource access path and rendering mode parameters. By decoupling content resource loading information from "content resource identifier" to "directly loadable path or entry point," the terminal control agent can drive the display rendering component to load different types of content resources using a unified scheduling interface.

[0101] In this embodiment, the terminal control agent outputs content resource loading information and playback strategy parameters to the display rendering component, so that the display rendering component can load and render the content resources indicated by the content resource loading information according to the playback strategy parameters. Specifically, when the trigger time arrives or the trigger window is established, the terminal control agent sends a loading instruction to the display rendering component. The loading instruction carries at least the content resource loading information, task identifier, and playback strategy parameters.

[0102] After receiving the loading instruction, the display rendering component selects the corresponding loading entry point to load the content based on the content resource loading information, and completes the rendering output according to the layout parameters or full-screen parameters in the playback strategy parameters. In some implementations, if the playback strategy parameters include display duration or carousel interval parameters, the display rendering component can maintain the display after rendering output until the duration expires, and return a switchable signal to the terminal control agent after the expiration, or the terminal control agent can decide whether to continue carouseling and trigger the next content according to the triggering rules. The display rendering component can be based on WebView as a unified rendering container: for web page resources, the local page entry point is directly loaded and displayed in full screen; for image or video resources, rendering and display are performed through the local page container or media playback entry point, thereby realizing a unified display path for multiple types of content.

[0103] In this embodiment, the terminal control agent generates task execution status information associated with the playback task at least during at least one stage of the display rendering component's loading and rendering output. Specifically, using the task identifier as the association key, the terminal control agent generates a "Start Display" state when issuing a loading command, a "Displaying" state when receiving feedback from the display rendering component indicating loading completion or reaching a preset stable display time, and a "End Display" state when the playback time period ends, a single playback session is completed, or the carousel cycle switches. When content resource loading fails, rendering abnormalities occur, or the task is preempted by an immediate task, a "Display Abnormality" or "Interrupted by Switching" state is generated, and the corresponding abnormality type and time information are recorded. The task execution status information can be transmitted back to the cloud management platform as part of the task execution information through a secure communication unit for cloud-based recording and tracing of the task execution process.

[0104] This embodiment discloses the implementation method of generating trigger rules by parsing playback strategy parameters, determining and scheduling display rendering components based on trigger conditions, determining and outputting content resource loading information based on content resource identifiers, and generating task execution status information associated with task identifiers during the loading and rendering stages. This enables terminal display devices to stably trigger content display according to rules in timed publishing and loop playback scenarios, and records the task execution process status and transmits it back to the cloud management platform. Through this implementation method, the accuracy and consistency of task triggering and content switching can be improved, the monitorability and traceability of the task execution process can be enhanced, and the display stability under unified scheduling of multiple terminals can be improved.

[0105] In some embodiments, the terminal control agent performs abnormal handling of content resource acquisition and content display, including: when a content resource acquisition failure is detected, retrying to acquire the corresponding content resource a preset number of times; when a content display abnormality is detected, reloading the content or switching to a preset alternative content resource; and when the number of abnormalities reaches a threshold, generating abnormal reporting information containing the content resource identifier and the abnormality type and reporting it to the cloud management platform through a two-way communication connection.

[0106] Specifically, after receiving a playback task, the terminal control agent performs content resource acquisition and caching, and schedules the display rendering component to display the content resources when the triggering conditions are met. Due to uncertainties such as network jitter, incomplete resources, and terminal malfunctions in cross-network and multi-terminal deployment environments, the terminal control agent sets up anomaly detection points in both the content resource acquisition and content display stages to perform tiered handling and create traceable anomaly records when anomalies occur.

[0107] In this embodiment, during the process of obtaining the corresponding content resource based on the content resource identifier and writing it to the local cache component, the terminal control agent detects content resource acquisition failures and retryes the acquisition a preset number of times. Specifically, the terminal control agent can divide the content resource acquisition process into three stages: acquisition request, data transmission, and cache writing, and set failure judgment conditions for each stage.

[0108] For example, during the request retrieval phase, if the resource download information matching the content resource identifier cannot be obtained from the cloud management platform, or if the resource download information parsing fails, the retrieval is deemed to have failed. During the data transmission phase, if a connection interruption, timeout, or transmission interruption occurs during the download process, the retrieval is deemed to have failed. During the cache write-to-disk phase, if writing to the local cache component fails or insufficient space results in incomplete writing, the retrieval is deemed to have failed.

[0109] To achieve controllable retries, the terminal control agent maintains a retry count and retry window parameters for each content resource identifier. The preset number of attempts can be set to a fixed number or dynamically adjusted based on network conditions. The retry window parameters can include the retry interval and retry timeout threshold. After the first failure, the terminal control agent re-initiates the acquisition request according to the retry interval and updates the retry count after each retry. If the retry count has not reached the preset number, retries continue. If the retry count reaches the preset number and the attempt still fails, the terminal control agent marks the content resource identifier as an acquisition failure and records the failure stage, failure reason code, and the time of the most recent failure for subsequent processing and reporting. When a download fails, the terminal control agent can prioritize attempting to re-download the resource or delay retries during brief network fluctuations to improve the success rate of resource acquisition.

[0110] In this embodiment, when the terminal control agent detects an abnormal content display, it performs content reloading or switches to a preset alternative content resource. Specifically, abnormal content display may include at least one of the following: display rendering component loading failure, rendering timeout, playback interruption, page unresolved, media decoding error, etc. The terminal control agent can detect display abnormalities in two ways: one is based on callbacks or status feedback from the display rendering component, such as the display rendering component returning a loading failure flag, a rendering context abnormality flag, or a decoding abnormality flag; the other is based on the terminal control agent's monitoring rules, such as failing to enter a stable display state after a preset rendering completion time limit has elapsed after loading is triggered, or experiencing a continuous black screen duration exceeding a threshold during the display process.

[0111] Regarding the reloading strategy, upon detecting a display anomaly, the terminal control agent prioritizes reloading the content resources corresponding to the same content resource identifier. Specifically, the terminal control agent re-sends the content resource loading information corresponding to the content resource identifier to the display rendering component, and can release and rebuild the rendering context before reloading to avoid residual state affecting subsequent rendering. If reloading still fails, the terminal control agent can further trigger an integrity check on the content resource in the local cache component. If the check fails, it returns to the content resource acquisition stage to download and overwrite the cache, and then performs loading again.

[0112] Regarding alternative switching strategies, the terminal control agent configures a preset set of alternative content resource identifiers for playback tasks or content resource identifiers. This set can be specified by the cloud management platform during the content publishing configuration phase or pre-configured locally by the terminal control agent. Alternative content resources may include valid content resources from the previous version, simplified versions of similar content pages, or default prompt pages. When the terminal control agent determines that the content resource corresponding to the current content resource identifier cannot be displayed stably, it selects the highest-priority alternative content resource identifier or the most recently verified alternative content resource identifier from the alternative content resource identifier set and schedules the display rendering component to load the corresponding alternative content resource to ensure uninterrupted display. The terminal control agent can maintain a list of "most recently successfully displayed content resource identifiers" as fallback candidates, prioritizing switching to the content resource corresponding to that identifier when an anomaly occurs.

[0113] In this embodiment, when the number of anomalies reaches a threshold, the terminal control agent generates an anomaly reporting message containing the content resource identifier and the anomaly type, and reports it to the cloud management platform via a two-way communication connection. Specifically, the terminal control agent maintains an anomaly counter for each task identifier or content resource identifier. The anomaly counter counts the number of failed content resource acquisitions and the number of content display anomalies, and can perform sliding statistics by time window to avoid misjudgment due to occasional failures. The anomaly threshold can be configured with differentiated thresholds based on content type, terminal type, or network status. For example, a higher retry threshold can be set for video resources, and a lower threshold can be set for urgent notification tasks to quickly trigger reporting.

[0114] When the anomaly counter reaches a threshold, the terminal control agent generates an anomaly reporting information. This information includes at least the device identifier, task identifier, content resource identifier, anomaly type, anomaly stage, number of anomalies, the time of the most recent anomaly, and anomaly context information. The anomaly context information may include the failure reason code, download status, rendering status, number of retries executed, and rollback policy identifier, enabling the cloud management platform to quickly locate the cause of the fault. The terminal control agent sends the anomaly reporting information to the cloud management platform through an encrypted bidirectional communication connection maintained by the secure communication unit. Upon receiving the information, the cloud management platform can prompt maintenance personnel on the management interface and issue remote diagnostic commands when necessary, such as clearing the cache, restarting the application, or restarting the terminal, to achieve remote diagnostics and rapid recovery.

[0115] To facilitate understanding, this embodiment provides a set of example scenarios illustrating the closed-loop exception handling. After receiving a playback task, a terminal display device downloads a "promotional video file" according to the content resource identifier. Due to network jitter, the download is interrupted. The terminal control agent determines that the content resource acquisition has failed and retryes the download a preset number of times. After the third retry, the download succeeds and is written to the local cache component.

[0116] Subsequently, when the triggering conditions are met, the display rendering component is scheduled to play the video. If playback is interrupted due to a decoding error, the terminal control agent first performs a reload. If two consecutive reloads fail, the system switches to the "static promotional image" corresponding to the preset alternative content resource identifier to maintain the display. If the number of decoding errors reaches a threshold within the same time window, the terminal control agent generates an error reporting message containing the content resource identifier and the error type and reports it to the cloud management platform. Based on this, the cloud management platform marks the terminal as abnormal and issues a remote control command to "clear the cache and restart the application." After the terminal control agent executes the command, it retrieves the video resource again and resumes playback.

[0117] This embodiment discloses a phased detection and preset retry mechanism for content resource acquisition failures, a reloading and alternative switching mechanism for content display anomalies, and an anomaly reporting information generation and feedback mechanism triggered by an anomaly count threshold. This enables the terminal control agent to self-recover and handle the playback link in scenarios of network instability or terminal anomalies, and to report anomaly information in a structured manner to the cloud management platform to support remote diagnostics. Through this implementation, the stability and continuity of the content acquisition and display process can be improved, the efficiency of anomaly localization and maintenance response can be increased, and the costs of manual intervention and the risk of display interruption caused by repeated failures can be reduced.

[0118] In some embodiments, in response to the scheduling of the terminal control agent, the content resources in the local cache are loaded and rendered according to the playback strategy parameters, including: receiving content resource loading information corresponding to the content resource identifier and playback strategy parameters corresponding to the playback task output by the terminal control agent; determining whether the content resource is a local cache resource or a remote reference resource based on the content resource loading information, and selecting a loading entry point matching the content resource type to perform content loading; after the content loading is completed, rendering the content resource in a preset format on the display interface in full screen according to the playback strategy parameters, and maintaining the rendering output within the playback time period limited by the playback strategy parameters; when the playback time period limited by the playback strategy parameters ends or the terminal control agent triggers the switching condition, releasing the rendering context of the current content resource and switching to the content resource loading information associated with the next playback task to continue loading and rendering output.

[0119] Specifically, the display rendering component first receives content resource loading information corresponding to the content resource identifier and playback strategy parameters corresponding to the playback task from the terminal control agent. Specifically, the terminal control agent locally parses the playback task into a task identifier, a content resource identifier, and playback strategy parameters, and generates content resource loading information from the local cache component or resource index based on the content resource identifier.

[0120] Content resource loading information includes at least the local cache path or loading entry parameters. The local cache path indicates the location of the content resource in the terminal storage, while the loading entry parameters describe the loading method and entry type that the display rendering component should use. After receiving the above information, the display rendering component establishes a rendering session of "task identifier - content resource identifier - loading entry," and uses the playback strategy parameters as the display constraints for this rendering session to control the layout, full-screen mode, and display duration.

[0121] Regarding content resource type determination and loading entry point selection, the display rendering component determines whether a content resource is a local cached resource or a remotely referenced resource based on its loading information, and selects the loading entry point that matches the content resource type to perform content loading. Specifically, the display rendering component determines whether the content resource loading information contains a local cache path or a remote address identifier: when the content resource loading information contains a local cache path, it is determined to be a local cached resource, and the local loading entry point is called to read the corresponding file or page file package; when the content resource loading information contains a remote address or reference identifier, it is determined to be a remotely referenced resource, and the remote loading entry point is called to load the corresponding page or media resource.

[0122] In some implementations, the display rendering component can also determine the content resource type by combining the content resource identifier or the resource type field in the loading entry parameters. The content resource type includes at least one of images, videos, and web pages. For image content resources, the display rendering component can load a local image display page in the WebView or directly load the image path and enable adaptation mode; for video content resources, the display rendering component can load a local video file through the video playback page hosted in the WebView or the built-in media playback entry and play it in full-screen mode; for web page content resources, the display rendering component loads a local page entry or a remote page address through the WebView and renders real-time data charts or flowcharts according to the layout defined on the page.

[0123] In some examples, the display module loads the corresponding content resources through WebView and displays them in full screen. In this embodiment, the display rendering component prioritizes a unified WebView rendering path, thereby reducing the complexity of differentiating the display of multiple types of content.

[0124] After content loading is complete, the display rendering component renders the content resources in a preset layout on the display interface in full-screen mode according to the playback strategy parameters, and maintains the rendering output within the playback time period specified by the playback strategy parameters. In some examples, the playback strategy parameters may include full-screen display markers, layout markers, and display duration parameters. The display rendering component switches to full-screen display mode according to the full-screen display markers and selects a preset page template or rendering layout according to the layout markers, such as landscape adaptation, partitioned display, or single-page full-screen display. When the content resource is a web page, the display rendering component enters immersive full-screen mode after loading the page in the WebView and hides unnecessary system controls to ensure display consistency. When the playback time period specified by the playback strategy parameters is within the valid range, the display rendering component maintains the current rendering session without releasing it and periodically sends the loading completion status or rendering heartbeat status back to the terminal control agent, which is used by the terminal control agent to generate task execution status information and exception judgment criteria.

[0125] Regarding content switching, the display rendering component releases the rendering context of the current content resource and switches to the content resource loading information associated with the subsequent playback task when the playback time period specified by the playback strategy parameters ends or the switching condition triggered by the terminal control agent is met, so as to continue loading and rendering output. In some examples, the terminal control agent may trigger the switching condition based on the end time of the playback time period parameter, the expiration of the carousel interval of the loop mode parameter, or the preemption flag of the immediate release task; after receiving the switching instruction, the display rendering component first releases the rendering context of the current rendering session, including stopping media playback, clearing the temporary session state cached by WebView, and releasing page resource occupation, and then switches to the next rendering session and loads the new content resource loading information.

[0126] For looping carousel scenarios, the display rendering component performs the above release and rebuild process at the end of each display cycle to reduce the risk of memory accumulation and rendering anomalies caused by long-term operation. For real-time switching scenarios, the display rendering component can directly stop the current rendering session and quickly load the content resource loading information corresponding to the real-time task after receiving a high-priority switching instruction, so as to cooperate with the terminal control agent to realize the display switching of "pausing the current playback task and switching to the new task".

[0127] This embodiment illustrates the loading and rendering output process using a set of example scenarios. A terminal display device needs to rotate between a "Device Operation Status Dashboard" and a "Safety Tip Image" during the morning. When the trigger condition is met, the terminal control agent sends the content resource loading information and playback strategy parameters corresponding to the first content resource identifier to the display rendering component. The display rendering component determines that the resource is a local cached resource and that the resource type is a web page. It then calls the WebView to load the local page entry and renders it in full screen, continuously displaying it during the playback period. After reaching the rotation interval trigger point, the terminal control agent triggers a switch and sends the content resource loading information corresponding to the second content resource identifier. The display rendering component releases the current WebView rendering context and switches to the image display entry, loading the local image and displaying it in full screen. If an immediate task is received during the display process requiring the immediate display of an "Emergency Notification Page," the terminal control agent issues a high-priority switch command. The display rendering component suspends the current rendering session and quickly loads the immediate page resource to ensure timely completion of the display switch.

[0128] This embodiment discloses the implementation method of the display rendering component receiving content resource loading information and playback strategy parameters, determining local cached resources and remotely referenced resources and selecting the matching loading entry point, rendering and outputting in full screen according to a preset layout and maintaining the display during the playback period, and releasing the rendering context and switching to subsequent content when the switching conditions are met. This enables the terminal display device to use a unified rendering component to carry the display of multiple types of content and stably complete carousel and real-time switching under task scheduling. Through this implementation method, the adaptability and consistency of content loading and rendering output can be improved, the display stability under long-term operation can be enhanced, and the responsiveness and maintainability of multi-task switching scenarios can be improved.

[0129] In some embodiments, when the bidirectional communication connection is interrupted, content display continues based on the content resources and playback tasks in the local cache, and the task execution records and exception information generated during the bidirectional communication connection interruption are cached. This includes: when the bidirectional communication connection interruption is detected, switching the task execution mode of the terminal control agent to the offline playback mode, and reading the content resource identifier and playback strategy parameters associated with the playback task from the local cache; calling the display rendering component based on the content resource identifier to load the corresponding content resource in the local cache, and maintaining content display or performing content switching in the offline playback mode according to the playback strategy parameters; in the offline playback mode, generating and caching the task execution record associated with the playback task, the task execution record including at least one of the following: task identifier, content resource identifier, playback start time, playback end time, and playback status; in the offline playback mode, collecting and caching exception information, the exception information including at least one of the following exception types: content resource acquisition exception, content display exception, and control operation exception, as well as time information and context information corresponding to the exception type.

[0130] Specifically, in this embodiment, when a bidirectional communication connection interruption is detected, the terminal control agent switches the task execution mode to offline resume mode. Specifically, the terminal control agent can detect bidirectional communication connection interruptions through connection status callbacks, heartbeat receipt timeouts, or consecutive reconnection failures. For example, the terminal control agent sends heartbeat messages within a preset heartbeat period and waits for cloud receipts. If no receipt is received within several consecutive heartbeat periods, the bidirectional communication connection is determined to be interrupted; or an interruption is immediately determined when the connection management service returns a disconnection event. After determining an interruption, the terminal control agent updates the local connection status to offline and switches the task execution mode to offline resume mode. Simultaneously, it initiates a reconnection detection mechanism to periodically attempt to restore the connection, but the reconnection process does not affect the content display and execution in offline resume mode.

[0131] While switching to offline resume playback mode, the terminal control agent reads the content resource identifier and playback strategy parameters associated with the playback task from the local cache component. Specifically, under normal conditions, the terminal control agent has already written the task identifier, content resource identifier, and playback strategy parameters obtained from parsing the playback task into the local task index or task queue. In offline resume playback mode, the terminal control agent extracts the currently pending or executing playback task from the task index and obtains the associated content resource identifier and playback strategy parameters. If there are multiple pending playback tasks in the playback task queue, the terminal control agent can filter out the playback task that should be executed at the current moment according to a preset order or according to the trigger window determined by the playback strategy parameters, so as to ensure that the playback is still displayed according to the established plan during offline resume playback.

[0132] In this embodiment, the terminal control agent calls the display rendering component to load the corresponding content resource from the local cache based on the content resource identifier, and maintains the content display or performs content switching in offline playback mode according to the playback strategy parameters. Specifically, in offline playback mode, the terminal control agent prioritizes the local cached resource as the display source, that is, it queries the local cache path or loading entry parameters according to the content resource identifier, and sends it to the display rendering component along with the playback strategy parameters. The display rendering component loads the local resource through WebView and displays it in full screen.

[0133] In some examples, if the playback time period specified by the playback strategy parameters is still within the valid range, the terminal control agent continues to maintain the current content display without switching; if the playback strategy parameters indicate loop playback and the loop interval trigger point is reached, the terminal control agent switches to the local cached resource corresponding to the next content resource identifier according to the loop rules and drives the display rendering component to complete the content switching.

[0134] This embodiment employs a network interruption resume playback mechanism. In offline resume playback mode, the terminal control agent can still perform timed triggering and loop playback, but its triggering determination is based on the terminal's local clock, and it primarily displays locally cached resources to avoid interruptions in display due to network outages preventing resource retrieval. When a content resource identifier corresponding to a certain resource is missing from the local cache, the terminal control agent can mark that content resource identifier as missing and switch to alternative content resources according to the aforementioned exception handling mechanism to maintain display continuity as much as possible.

[0135] In this embodiment, in offline playback mode, the terminal control agent generates and caches task execution records associated with the playback task. Specifically, the terminal control agent uses the task identifier as the association key to generate task execution record entries each time content display starts, ends, or switches, and writes the task execution record entries to the local cache component or local log storage area. The task execution record includes at least one of the following: task identifier, content resource identifier, playback start time, playback end time, and playback status. The playback status may include status types such as started display, displaying, finished display, and interrupted by switching.

[0136] In some examples, for looping scenarios, the terminal control agent can generate one or more task execution records in each loop cycle to reflect the actual display sequence during offline playback; for single playback scenarios, the terminal control agent can mark the task as executed and generate the corresponding end record after a single display is completed to prevent repeated triggering during offline periods.

[0137] To ensure that records are traceable and not lost during offline periods, the terminal control agent in this embodiment can cache task execution records using an append-only method, and include the local sequence number or record generation timestamp in the records so that they can be reported in batches according to the generation order after the network is restored. If local storage space is limited, the terminal control agent can perform rolling storage or archive by time window according to a preset strategy for task execution records, while still ensuring that the association fields between task identifier and content resource identifier are not missing.

[0138] In this embodiment, in offline playback mode, the terminal control agent collects and caches exception information. The exception information includes at least one exception type among content resource acquisition exception, content display exception, and control operation exception, as well as corresponding time and context information. Specifically, content resource acquisition exceptions may occur in offline playback mode due to failure to read locally cached resources, cache file verification failure, or insufficient local cache space; content display exceptions may occur due to display rendering component loading failure, rendering exception, or media playback interruption; control operation exceptions may occur when local control operations are still performed offline and calls to terminal-side interfaces fail, such as brightness adjustment interface rejection or application restart failure. The terminal control agent records the exception information in a structured manner, including at least the exception type, exception occurrence stage, exception occurrence time information, and exception context information. The exception context information may include relevant task identifiers, content resource identifiers, failure reason codes, the number of retries performed, and whether a fallback switch was triggered, for subsequent cloud-based diagnostics.

[0139] In some implementations, the terminal control agent will still periodically attempt to reconnect in offline resume mode, and record a connection exception each time a reconnection fails. However, these connection exceptions can be stored independently of playback task exceptions to avoid confusing task execution records with communication exception records. After the offline resume mode ends, these exception information will be reported as part of the offline log along with the task execution records.

[0140] This embodiment discloses mechanisms for detecting bidirectional communication connection interruptions and switching offline playback modes, maintaining display based on local cache resources and switching content according to playback strategy parameters, structured generation and caching of task execution records during offline periods, and collection and caching of abnormal information. This enables terminal display devices to continuously execute predetermined playback tasks and fully retain execution traces and abnormal contexts even in network outage or unstable network scenarios. Through this implementation, the continuity and stability of display services in network outage scenarios can be improved, the traceability of task execution processes during offline periods can be enhanced, and the efficiency of operation and maintenance diagnosis and task synchronization consistency after network recovery can be improved.

[0141] The above embodiments have described in detail the specific composition and functions of the cloud-centralized terminal display control system of this application. The implementation process of the cloud-centralized terminal display control method of this application will be described in detail below with reference to specific embodiments. Figure 2 is a flowchart illustrating the cloud-centralized terminal display control method provided in this application embodiment. As shown in Figure 2, the method may specifically include the following steps: S201, the cloud management platform receives the content publishing configuration input by the management terminal, generates a playback task associated with the target terminal display device based on the content publishing configuration, and generates a remote control command for the target terminal display device; S202, an encrypted bidirectional communication connection is established between the cloud management platform and the target terminal display device, and the playback task and remote control command are sent to the target terminal display device through the bidirectional communication connection; S203, the terminal control agent of the target terminal display device completes identity authentication with the cloud management platform through the bidirectional communication connection and maintains the connection, receives and parses the playback task to obtain the content resource identifier and... The playback strategy parameters are used to retrieve the corresponding content resources based on the content resource identifier and write them to the local cache; S204, when the triggering conditions defined by the playback strategy parameters are met, the display rendering component is scheduled to load the content resources in the local cache according to the playback strategy parameters and perform rendering output; S205, remote control commands are received and parsed, and the terminal-side interface is called to execute the control operation corresponding to the remote control command; S206, when the two-way communication connection is interrupted, the content display continues to be executed based on the content resources and playback tasks in the local cache, and the task execution records and exception information generated during the two-way communication connection interruption are cached; after the two-way communication connection is restored, the task execution records and exception information are reported to the cloud management platform, and the playback tasks and remote control commands associated with the target terminal display device are requested to be synchronized.

[0142] It should be understood that the sequence number of each step in the above method embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

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

Claims

1. A cloud-based centralized management terminal display control system, characterized in that, include: The cloud management platform is used for centralized access management of terminal display devices. It generates playback tasks based on the content publishing configuration input by the management terminal and generates remote control commands for the terminal display devices. A secure communication unit is used to establish an encrypted two-way communication connection between the cloud management platform and the terminal display device, enabling the cloud management platform to send playback tasks and remote control instructions to the terminal display device through the two-way communication connection, and to receive the running status and task execution information reported by the terminal display device. The terminal control agent is used to complete identity authentication with the cloud management platform and maintain the connection through the bidirectional communication connection; receive and parse the playback task to obtain the content resource identifier and playback strategy parameters, obtain the corresponding content resource according to the content resource identifier and write it to the local cache; when the triggering conditions defined by the playback strategy parameters are met, schedule the display rendering component to load the content resource in the local cache for display; receive and parse the remote control command and call the terminal side interface to execute the control operation corresponding to the remote control command; A display rendering component, deployed on the terminal display device, is used to respond to the scheduling of the terminal control agent and load and render the content resources in the local cache according to the playback strategy parameters. An offline playback continuation and synchronization component, deployed on the terminal display device, is used to continue content display based on the content resources and playback tasks in the local cache when the bidirectional communication connection is interrupted, and to cache the task execution records and exception information generated during the bidirectional communication connection interruption. After the bidirectional communication connection is restored, the task execution records and exception information are reported to the cloud management platform, and the cloud management platform is requested to synchronize the playback tasks and remote control commands associated with the terminal display device.

2. The system according to claim 1, characterized in that, The cloud management platform includes a device management module and a task scheduling module. The device management module is used to complete device registration and group management based on the device identifier of the terminal display device, and maintain online and operational status information associated with the device identifier. The task scheduling module is used to generate the playback task based on the content publishing configuration, and associate the playback task with the device identifier or device group. The task scheduling module is also used to issue the playback task according to a preset publishing time, and to issue the playback task upon receiving an immediate publishing request.

3. The system according to claim 2, characterized in that, The content publishing configuration includes a target terminal display device identifier, a content resource identifier, a playback time period parameter, and a loop mode parameter; the playback task includes a task identifier, a content resource identifier, and playback strategy parameters corresponding to the content publishing configuration, wherein the playback strategy parameters are used to limit the triggering conditions for the terminal control agent to trigger the display rendering component to execute content display.

4. The system according to claim 1, characterized in that, The cloud management platform generates remote control commands for terminal display devices, including generating command payloads based on the control operation type and control parameters input by the management terminal, and establishing an association between the remote control commands and the target terminal display device identifier; after the terminal control agent calls the terminal-side interface to execute the control operation corresponding to the remote control command, it reports the execution result of the control operation and the corresponding time information to the cloud management platform.

5. The system according to claim 1, characterized in that, The secure communication unit employs at least one of a publish-subscribe message channel and a full-duplex long-connection message channel to issue the playback task and the remote control command, and to transmit back the running status and the task execution information; wherein, the publish-subscribe message channel is used to publish the playback task or the remote control command to a message topic corresponding to the target terminal display device identifier or device group, and the terminal control agent subscribes to the message topic to receive the playback task or the remote control command.

6. The system according to claim 1, characterized in that, The step of scheduling the display rendering component to load and display content resources in the local cache when the triggering conditions defined by the playback strategy parameters are met includes: parsing the playback triggering conditions associated with the playback task based on the playback strategy parameters, wherein the playback triggering conditions include playback time period parameters and / or loop mode parameters; when the playback triggering conditions are met, determining the content resource loading information corresponding to the content resource identifier from the local cache, wherein the content resource loading information includes the local cache path or loading entry parameters; outputting the content resource loading information and the playback strategy parameters to the display rendering component, so that the display rendering component performs loading and rendering output on the content resource indicated by the content resource loading information according to the playback strategy parameters; and generating task execution status information associated with the playback task during at least one stage of the display rendering component performing loading and rendering output.

7. The system according to claim 1, characterized in that, The terminal control agent performs anomaly handling for the acquisition and display of the content resources, including: when a failure to acquire the content resources is detected, retrying to acquire the corresponding content resources a preset number of times; when an anomaly in the display of the content is detected, reloading the content or switching to a preset alternative content resource; and when the number of anomalies reaches a threshold, generating an anomaly reporting information containing the content resource identifier and the anomaly type and reporting it to the cloud management platform through the bidirectional communication connection.

8. The system according to claim 1, characterized in that, The step of responding to the scheduling of the terminal control agent and loading and rendering the content resources in the local cache according to the playback strategy parameters includes: receiving content resource loading information corresponding to the content resource identifier and playback strategy parameters corresponding to the playback task output by the terminal control agent; determining whether the content resource is a local cache resource or a remote reference resource based on the content resource loading information, and selecting a loading entry point matching the content resource type to perform content loading; after the content loading is completed, rendering the content resource in a preset format on the display interface in full screen according to the playback strategy parameters, and maintaining the rendering output within the playback time period limited by the playback strategy parameters; when the playback time period limited by the playback strategy parameters ends or the terminal control agent triggers a switching condition, releasing the rendering context of the current content resource and switching to the content resource loading information associated with the next playback task to continue loading and rendering output.

9. The system according to claim 1, characterized in that, When the bidirectional communication connection is interrupted, the method of continuing content display based on the content resources and playback tasks in the local cache, and caching the task execution records and exception information generated during the interruption of the bidirectional communication connection, includes: when the bidirectional communication connection interruption is detected, switching the task execution mode of the terminal control agent to the offline playback mode, and reading the content resource identifier and playback strategy parameters associated with the playback task from the local cache; calling the display rendering component to load the corresponding content resource in the local cache based on the content resource identifier, and maintaining content display or performing content switching in the offline playback mode according to the playback strategy parameters; in the offline playback mode, generating and caching the task execution record associated with the playback task, the task execution record including at least one of the following: task identifier, content resource identifier, playback start time, playback end time, and playback status; in the offline playback mode, collecting and caching exception information, the exception information including at least one of the following exception types: content resource acquisition exception, content display exception, and control operation exception, as well as time information and context information corresponding to the exception type.

10. A terminal display control method based on cloud-based centralized management of the system as described in any one of claims 1 to 9, characterized in that, include: The cloud management platform receives content publishing configuration input from the management terminal, generates a playback task associated with the target terminal display device based on the content publishing configuration, and generates remote control instructions for the target terminal display device. An encrypted bidirectional communication connection is established between the cloud management platform and the target terminal display device, and the playback task and remote control instructions are sent to the target terminal display device through this bidirectional communication connection. The terminal control agent of the target terminal display device completes authentication with the cloud management platform through the bidirectional communication connection and maintains the connection. It receives and parses the playback task to obtain content resource identifiers and playback strategy parameters, retrieves the corresponding content resources according to the content resource identifiers, and writes them locally. The system caches content resources. When the triggering conditions defined by the playback strategy parameters are met, the system schedules the display rendering component to load the content resources in the local cache according to the playback strategy parameters and renders them. It receives and parses the remote control command, calls the terminal-side interface to execute the control operation corresponding to the remote control command. When the bidirectional communication connection is interrupted, the system continues to display content based on the content resources in the local cache and the playback task, and caches the task execution records and exception information generated during the bidirectional communication connection interruption. After the bidirectional communication connection is restored, the system reports the task execution records and exception information to the cloud management platform and requests synchronization of the playback task and remote control command associated with the target terminal display device.

Images