Data processing system and method

Abstract

The application discloses a data processing system and method, relates to the technical field of monitoring, and utilizes a network connection protocol to collect target images at a high frequency according to a preset period and send the target images to a platform end without supporting a standard video stream transmission protocol, so that the target images collected at the high frequency by a target monitoring end are continuously received by a client end, real-time push streaming is realized, the target images are collected and sent, the target images do not need to be sent after reaching a certain quantity, resource consumption is reduced, and bandwidth utilization is improved.

Description

Technical Field

[0001] This application relates to the field of surveillance technology, and in particular to a data processing system and method. Background Technology

[0002] In equipment monitoring systems for fields such as Industrial Internet of Things (IIoT) and smart buildings, standard video streaming protocols (such as RTMP (Real-Time Messaging Protocol), RTSP (Real-Time Streaming Protocol), and WebRTC (Web Real-Time Communication)) are typically used to achieve real-time video monitoring.

[0003] In related technologies, in specific scenarios, such as when an equipment monitoring system is deployed in a private environment, the client functionality is limited, making it impossible to use standard video streaming protocols to achieve real-time video monitoring. Therefore, when the equipment monitoring system cannot use standard video streaming protocols for real-time video monitoring, how to achieve real-time video monitoring becomes a problem that needs to be solved. Summary of the Invention

[0004] This application provides a data processing system and method that enables near real-time video monitoring when the equipment monitoring system cannot use standard video streaming protocols.

[0005] Firstly, a data processing system is provided, comprising: a target monitoring terminal, a platform terminal, and a client terminal. The target monitoring terminal establishes a connection with the platform terminal via a first network connection protocol, and the platform terminal establishes a connection with the client terminal via a second network connection protocol. The target monitoring terminal is configured to take screenshots according to a preset period, obtain target images, and report the target images to the platform. The preset period is any value within 1 second to 10 seconds. On the platform side, it is configured to receive the target image and send indication information to the client to indicate the target image; The client is configured to obtain indication information of the target image, obtain the target image according to the indication information, and update the client's interface according to the target image.

[0006] In this embodiment of the application, in the absence of support for standard video streaming protocols, a network connection protocol is used to collect target images at high frequency according to a preset period and send the target images to the platform. The client then receives the images and updates its interface based on them. In this way, the client can continuously receive target images collected at high frequency by the target monitoring terminal according to a preset period, achieving near real-time streaming. Furthermore, the target images are sent immediately upon collection, without waiting for a certain number of target images to be collected before sending, thus reducing resource consumption and improving bandwidth utilization.

[0007] In one possible implementation of the first aspect, the target monitoring terminal performs screenshots according to a preset period to obtain the target image. Specifically, it is configured to: receive a screenshot instruction, which instructs the target monitoring terminal to perform screenshots according to a preset period. The screenshot instruction is sent by the platform terminal when it receives a viewing request, which is sent by the client to the platform terminal; and perform screenshots according to the preset period to obtain the target image.

[0008] In this embodiment of the application, a screenshot is taken when a screenshot instruction is received, that is, a screenshot is taken when there is a need for monitoring from the client, so as to avoid wasting resources.

[0009] In one possible implementation of the first aspect, the platform receives the target image and sends indication information to the client to indicate the target image. Specifically, the platform is configured to: receive the target image; store the target image on the platform and determine the storage information of the target image; and send the indication information to the client, the indication information including the storage information of the target image. Correspondingly, the client executes the process of acquiring the target image based on the indication information of the target image, specifically configured as follows: Obtain the target image based on the stored information of the target image.

[0010] In this embodiment, the target image is stored on the platform and the storage information of the target image is sent to the client. This method has high transmission efficiency and can avoid transmission failure due to the large size of the target image, thus ensuring the stability of data transmission between the platform and the client.

[0011] In one possible implementation of the first aspect, the platform is also configured to: delete the target image stored on the platform.

[0012] In this embodiment of the application, due to the need for real-time monitoring, the data sent to the client is no longer real-time. Therefore, the target image stored on the platform can be deleted to avoid data redundancy.

[0013] In one possible implementation of the first aspect, the platform side performs the deletion of the target image stored on the platform side, specifically configured to delete the target image stored on the platform side when it is confirmed that the client updates the client interface based on the target image.

[0014] In this embodiment of the application, the situation where the client has not fully read the target image when deleting the target image is avoided, which would cause the interface update to fail, thereby ensuring the integrity of the client's updated interface.

[0015] In one possible implementation of the first aspect, the indication information includes the target image.

[0016] In this embodiment, the target image itself is directly pushed, avoiding cumbersome data processing and improving data transmission efficiency.

[0017] In one possible implementation of the first aspect, the first network connection protocol is a long-lived connection protocol.

[0018] In one possible implementation of the first aspect, the second network connection protocol is a long-lived connection protocol.

[0019] Secondly, a data processing method is provided, applied to the platform side of a data processing system. The data processing method includes: receiving a target image and sending indication information for indicating the target image to a client; the platform side establishes a connection with the client through a second network connection protocol, so that the client obtains the target image according to the indication information of the target image and updates the client's interface according to the target image; the target image is a screenshot taken by the target monitoring terminal according to a preset period and reported to the platform side; the preset period is any value greater than or equal to 1 second and less than or equal to 10 seconds; the target monitoring terminal establishes a connection with the platform side through a first network connection protocol.

[0020] In one possible implementation of the first aspect, the data processing method further includes: receiving a target image, storing the target image on a platform, determining the storage information of the target image, and sending indication information of the target image to a client, wherein the indication information of the target image includes the storage information of the target image, so that the client can obtain the target image according to the storage information of the target image.

[0021] Thirdly, a data processing apparatus is provided, including a unit for performing any of the methods in the second aspect. This data processing apparatus may be a platform-side component or a chip within the platform-side component.

[0022] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a data processing apparatus, causes the data processing apparatus to perform any of the data processing methods described in the second aspect.

[0023] Fifthly, a computer program product is provided, comprising: a computer program that, when run by a data processing apparatus, causes the data processing apparatus to perform any of the data processing methods described in the second aspect. Attached Figure Description

[0024] Figure 1 This is a schematic diagram of the structure of a data processing system provided in an embodiment of this application; Figure 2 This is a flowchart illustrating a data processing system provided in an embodiment of this application; Figure 3 This is a flowchart illustrating another data processing system provided in an embodiment of this application; Figure 4 This is a flowchart illustrating another data processing system provided in an embodiment of this application; Figure 5 This is a flowchart illustrating another data processing system provided in an embodiment of this application; Figure 6 This is a flowchart illustrating another data processing system provided in an embodiment of this application; Figure 7 This is a flowchart illustrating another data processing system provided in an embodiment of this application; Figure 8 This is a flowchart illustrating another data processing system provided in an embodiment of this application; Figure 9 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application. Detailed Implementation

[0025] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0026] Hereinafter, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include one or more of that feature.

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

[0028] The relevant technologies involved in the embodiments of this application will be described below.

[0029] In equipment monitoring systems in fields such as Industrial Internet of Things (IIoT) and smart buildings, standard video streaming protocols are typically used (such as Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and WebRTC (Web Real-Time Communication)). These are streaming media protocols primarily used for audio and video streaming to achieve real-time video monitoring.

[0030] However, in specific scenarios, such as when a device monitoring system is deployed in a private environment, client functionality is limited, making it impossible to use standard video streaming protocols for real-time video monitoring. In such private environments, a common network channel can be used to transmit video screenshots to meet video monitoring needs. Related technologies offer two solutions for using common network channels to transmit video screenshots for monitoring. One is to significantly reduce the frequency of screenshot reporting from the monitoring end (e.g., reporting a screenshot every minute) to check the device status. While this method avoids using standard video streaming protocols, the low reporting frequency completely sacrifices the "real-time" aspect of video monitoring, failing to meet the need for continuous and timely monitoring of device status. The other method involves the monitoring end continuously taking screenshots (e.g., one or more per second) and saving them locally, then periodically uploading them to the platform (e.g., uploading every 20 screenshots saved). However, this method generates a large amount of redundant data, consuming significant transmission bandwidth and cloud storage space, and the platform cannot view the data in real-time, resulting in severe data value delays. Therefore, there is an urgent need for a device monitoring solution that can still achieve high timeliness and low resource consumption even without supporting the use of standard video streaming protocols.

[0031] In view of this, embodiments of this application provide a data processing system and method. The data processing system includes: a target monitoring terminal, a platform terminal, and a client terminal. The target monitoring terminal establishes a connection with the platform terminal through a first network connection protocol, and the platform terminal establishes a connection with the client terminal through a second network connection protocol. The target monitoring terminal is configured to take screenshots according to a preset period to obtain target images and report the target images to the platform terminal. The preset period is any value greater than or equal to 1 second and less than or equal to 10 seconds. The platform terminal is configured to receive target images and send indication information for indicating target images to the client terminal. The client terminal is configured to obtain the indication information of the target images, obtain the target images according to the indication information of the target images, and update the client interface according to the target images. Thus, even without supporting standard video streaming protocols, network connection protocols are used to collect target images at high frequency according to a preset period and send them to the platform. The client then receives the images and updates its interface based on them. This allows the client to continuously receive high-frequency target images from the monitoring terminal, achieving near real-time streaming. Furthermore, the target images are sent immediately upon collection, eliminating the need to wait for a certain number of images to be collected before sending, thus reducing resource consumption and improving bandwidth utilization.

[0032] To facilitate a further understanding of the technical solutions in some embodiments of this application, the technical solutions of the data processing system and method, and how these solutions solve the aforementioned technical problems, are described in detail below with reference to specific embodiments and accompanying drawings. The embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of this application.

[0033] Figure 1 A schematic diagram of the structure of a data processing system provided in an embodiment of this application is shown, such as... Figure 1 As shown, the data processing system 100 includes: multiple monitoring terminals (monitoring terminal 1, monitoring terminal 2, ..., monitoring terminal n), a platform terminal, and a client terminal. Each monitoring terminal establishes a connection with the platform terminal through a first network connection protocol, and the target monitoring terminal is one of the multiple monitoring terminals. The platform terminal establishes a connection with the client terminal through a second network connection protocol.

[0034] In some embodiments, the first network connection protocol is not a standard video streaming protocol. Unlike standard video streaming protocols, which are used to transmit continuous streaming media, the first network connection protocol is a general data protocol that transmits data independently of the media encoding format. It can be a protocol for transmitting control signaling or media description information, or a request-response based transmission protocol. The first network connection protocol can be a short-connection protocol or a long-connection protocol. A short connection refers to establishing a connection only while transmitting data and immediately closing it after the service is completed; each connection handles only a single service. Short-connection protocols include HTTP / 1.0, where each request requires a new TCP connection, and the TCP connection is closed immediately after the request is completed. A long connection is a communication method that allows multiple data packets to be sent continuously over a single network connection. If no data is transmitted during the connection maintenance period, the state is maintained through link detection packets. Compared to short connections (which close after each communication), long connections avoid the overhead of frequently establishing connections. Long-connection protocols can be bidirectional streaming protocols. Long-connection protocols can include HTTP / 1.1, HTTP / 2, and higher versions, allowing multiple requests and responses to be sent over the same connection until one party requests to close the connection. Long-connection protocols may also include: WebSocket, MQTT, HTTP long polling, WebTransport, etc. The description of the second network connection protocol is similar to that of the first network connection protocol, and will not be repeated here. It should also be noted that the second network connection protocol can be the same as or different from the first network connection protocol. For example, the first network connection protocol may be a short-connection protocol (e.g., HTTP 1.0), and the second network connection protocol may be a long-connection protocol (e.g., WebSocket). Alternatively, both the first and second network connection protocols may be long-connection protocols (e.g., both may be WebSocket).

[0035] The above explains the connections between the various parts of the data processing system. The following describes the specific steps performed by each part.

[0036] Figure 2 A flowchart of the data processing system provided in an embodiment of this application is shown, as follows: Figure 2 As shown, where: S210, the target monitoring terminal is configured to take screenshots according to a preset period, obtain target images, and report the target images to the platform.

[0037] The preset period is any value between 1 second and 10 seconds. Preferably, the preset period is 5 seconds.

[0038] Specifically, the target monitoring terminal performs periodic data collection and reporting locally. For example, it takes screenshots of the screen or video source according to a preset period to obtain the target image, and immediately encapsulates the target image data into a reporting message and sends it to the platform through the first network link. The first network link is established between the target monitoring terminal and the client based on the first network connection protocol.

[0039] In some embodiments, the aforementioned preset period can be pre-set on the target monitoring terminal. When the preset period is pre-set on the target monitoring terminal, when the target monitoring terminal receives a screenshot instruction, it directly performs a screenshot according to the preset period. A screenshot is performed every time the preset period is reached, obtaining the target image, and the target image is reported to the platform, or screenshot data is reported to the platform. The screenshot data includes the identifier of the target monitoring terminal and the data of the target image. The preset period can also be pre-configured on the platform according to business needs.

[0040] In other embodiments, the aforementioned preset period can also be set by the user. When the preset period is set by the user, such as... Figure 3 As shown, Figure 3 This is a timing flowchart of another data processing system provided in an embodiment of this application. Specifically, the execution of S210 by the target monitoring terminal is configured to execute S2101 to S2103, wherein: S2101, the target monitoring terminal received a screenshot command.

[0041] The screenshot command is used to instruct the target monitoring terminal to take screenshots according to a preset period. The screenshot command is sent by the platform when it receives a viewing request, which is sent by the client to the platform.

[0042] In some embodiments, a client (such as a mobile app, web browser, or PC client) sends a viewing request to the platform to view the real-time feed from the target monitoring device. The platform acts as an intermediary service node, responsible for authentication, routing, and command forwarding. When the platform parses the viewing request and confirms that the target monitoring device is online and accessible, it constructs a screenshot command and sends it to the target monitoring device. Understandably, the client dynamically specifies the screenshot period for the target monitoring device in the viewing request. The platform can encapsulate the screenshot period in the viewing request within a screenshot command and send it to the target monitoring device, allowing the target monitoring device to use that screenshot period as a preset period for taking screenshots. Additionally, the screenshot command includes parameters such as the target monitoring device identifier, image resolution, and image format (e.g., JPEG, PNG).

[0043] S2102, take a screenshot according to the preset period to obtain the target image.

[0044] The target monitoring terminal parses the received screenshot command, obtains the preset period from the command, and configures the local screenshot task based on the preset period. Specifically, the target monitoring terminal can create a periodic thread to trigger the camera to capture images at regular intervals according to the parsed preset period. Additionally, the target monitoring terminal can process the captured images according to parameters such as image resolution and image format indicated in the screenshot command to obtain the target image. Understandably, if the screenshot command does not include parameters such as image resolution or image format, the target monitoring terminal's default image configuration will be used to determine the target image.

[0045] In this embodiment, the target monitoring terminal initiates periodic screenshots upon receiving a screenshot instruction, meaning that screenshots are taken only when the client has monitoring needs. This reduces the resource waste caused by continuous screenshots and can flexibly meet the client's viewing needs.

[0046] S2103, report the target image to the platform.

[0047] S220, the platform is configured to receive the target image and send indication information to the client to indicate the target image.

[0048] In some embodiments, the indication information of the target image may include the target image itself, or the storage information of the target image.

[0049] For example, when the indication information of the target image includes the storage information of the target image, such as... Figure 4 As shown, Figure 4 This is a timing flowchart of another data processing system provided in an embodiment of this application. The platform receives the target image and sends indication information to the client to indicate the target image. Specifically, it is configured as follows: S2201, Receive target image.

[0050] The platform periodically receives target images. The platform can also receive screenshot data and extract the target image from it.

[0051] S2202, Store the target image on the platform and determine the storage information of the target image.

[0052] For example, the platform integrates data storage functionality. When a target image is acquired, the platform performs local storage operations on the target image. After the target image is successfully stored, the platform determines the storage information of the target image.

[0053] Storage information includes the storage path of the target image or a database record identifier. Specifically, if a file system is used to store the target image, that is, the target image is written as a file into a file system directly accessible to the platform, the storage information is the complete storage path of the target image. When constructing the storage path, the platform can generate a unique path based on metadata such as the target monitoring terminal identifier and timestamp, and record this path as storage information. Alternatively, a database can be used to store the target image, that is, the target image data is stored in a database connected to the platform. The storage information can be the index value generated by the database for the storage record of the target image, i.e., the database record identifier.

[0054] For example, the platform can be coupled to a caching engine to store the target image. Specifically, the platform transmits the target image and its associated metadata (such as device identifier, timestamp, image format, etc.) to an independent caching engine through a predefined storage interface. The caching engine is responsible for persistently writing the data, building the index, and managing the subsequent storage. It then generates storage information and returns it to the platform. The platform receives this storage information so that when the client reads the target image, it can initiate a read request to the caching engine based on this storage information to obtain the target image.

[0055] For example, such as Figure 5 As shown, the data processing system may also include a caching engine. The caching engine has a subscription relationship with the platform. The target monitoring end can directly send the target image to the caching engine. When the target image is stored in the caching engine, the caching engine sends a caching notification to the platform. The caching notification is used to notify the platform that the target monitoring end's cache has been updated. The caching notification includes the storage information of the target image.

[0056] Understandably, on the platform itself or in the caching engine, a separate, limited-capacity temporary cache space can be maintained for each month's monitoring terminals that have a connection with the platform, and the received target images can be stored in the cache space of the corresponding target monitoring terminal.

[0057] S2203 sends an instruction message to the client.

[0058] The indication information includes the storage information of the target image.

[0059] The stored information serves as the access credential for the client to subsequently acquire or manipulate the target image. Upon receiving the instruction, the client can, based on the stored information of the target image included in the instruction, initiate a request to the platform to obtain image data or perform further processing.

[0060] S230, the client is configured to obtain indication information of the target image, obtain the target image according to the indication information of the target image, and update the client's interface according to the target image.

[0061] In some embodiments, the client executes the action of obtaining the target image based on the indication information of the target image, specifically configured to: obtain the target image based on the storage information of the target image. For example, based on the storage information of the target image, the target image can be obtained locally on the platform or from a caching engine.

[0062] In some embodiments, the client can also directly obtain the target image.

[0063] Optional, Figure 6 A timing flowchart of another data processing system provided in this application embodiment is shown below. Figure 6 As shown, the platform is also configured to delete the target image stored on the platform.

[0064] For example, delete the target image stored locally on the platform, or delete the target image stored in a cache engine coupled to the platform.

[0065] In some embodiments, if it is confirmed that the client has updated its interface according to the target image, the target image stored on the platform is deleted. It should be noted that when the client updates its interface according to the target image, it can send an update completion notification to the platform. The update completion notification informs the platform that the client has completed the interface update. Upon receiving the update completion notification from the client, the platform can confirm that the client has updated its interface according to the target image. Deleting the target image stored on the platform at this point prevents the client's interface update from failing because the platform has deleted the target image before the client has fully read it.

[0066] Figure 7 This is a timing flowchart of another data processing system provided in the embodiments of this application. The following is in conjunction with... Figure 7 The specific implementation methods provided in this application are described. The timing flow of the data processing system includes the following four main steps: periodic data collection and reporting at the monitoring end, cache management and association at the platform end, on-demand push and cleanup at the platform end, and cyclic execution and status synchronization, wherein: S1. Periodic Data Acquisition and Reporting from the Monitoring Terminal: The platform sends high-frequency screenshot commands to the monitoring terminal. The monitoring terminal, i.e., the monitoring device, takes screenshots of the screen or video source locally at preset intervals (e.g., every 5 seconds) and immediately encapsulates the target image (i.e., the current screenshot data) into a reporting message, which is then sent to the platform terminal via the first network link. Figure 7 As shown, a WebSocket connection is used between the monitoring terminal D1 and the platform terminal, and a WebSocket connection is used between the platform terminal and the client terminal.

[0067] S2. Platform-side Cache Management and Association: The platform (i.e., the cloud platform) receives the reported message, parses out the target image and the device identifier D1 of the monitoring terminal that acquired the target image; the platform maintains an independent, limited-capacity temporary cache in memory for each online monitoring terminal device; and stores the received target image into the cache of the corresponding monitoring terminal device. For example... Figure 7 As shown, monitoring terminal D1 stores the screenshot data in the cache engine and updates the screenshot in the cache engine of monitoring terminal D1 to the latest screenshot, which is the target image in the screenshot data reported this time. Since the platform has registered the subscription message of monitoring terminal D1 in the cache engine, after the cache engine stores the latest screenshot of monitoring terminal D1, it notifies the platform that the cache corresponding to monitoring terminal D1 has been updated, and includes the storage information of the target image in the notification.

[0068] S3. Platform-side on-demand push and cleanup: When a client requests to view the real-time video of the target monitoring terminal (i.e., the device specified by the client, i.e., the specified device: monitoring terminal D1), the platform establishes a long network connection with the client. Through this long network connection, the screenshot data in the corresponding cache of the specified device monitoring terminal D1 is pushed to the client for display in real time. At the same time, after the platform successfully pushes the target image, or confirms that the client has successfully received and displayed the target image, the target image is immediately deleted from the cache of monitoring terminal D1.

[0069] Cyclic execution and status synchronization: Repeatedly executing steps S1 to S3, so that the periodic screenshots from the monitoring end, the instantaneous caching and push from the platform end, and the real-time display from the client end form a continuous data stream, thereby achieving near real-time device status monitoring even without a continuous video stream.

[0070] Figure 8 This is a flowchart illustrating another data processing system provided in an embodiment of this application, as shown below. Figure 8 As shown, the data processing system performs the following steps: In the S801 monitoring terminal, the program triggers a screenshot operation every 5 seconds, encodes the captured JPEG image using Base64 (or directly as a binary stream), and sends it along with the monitoring terminal's device identifier ID to the specified API interface on the platform via a lightweight HTTP POST request.

[0071] S802, the platform processes the HTTP POST request and, based on the device ID, locates the screenshot cache information in the monitoring terminal's in-memory Redis. New screenshot data is then placed into the cache.

[0072] When an administrator logs into the management client via a browser and clicks to view the real-time monitoring of a device, the client establishes a persistent connection with the long-connection management unit on the platform via WebSocket and sends a subscription command containing the device ID.

[0073] After receiving the subscription command, the S804 platform will immediately poll (or detect) the cached images corresponding to the device ID. Once a cached image is found in the list, it will be pushed to the client browser via a WebSocket connection.

[0074] In S805, after the client browser receives the image data, it renders it in HTML5. The image is tagged and replaced with the previous one to create a dynamic display effect. Meanwhile, the platform considers a successful push as a successful display. After a successful push, the platform immediately deletes the previously pushed image data from the cache.

[0075] This process repeats continuously, providing the administrator with a continuous feed that refreshes approximately every 5 seconds, achieving near real-time monitoring. The platform itself only temporarily stores one image for each viewed device, consuming minimal resources.

[0076] This application provides a data processing system comprising: a target monitoring terminal, a platform terminal, and a client terminal. The target monitoring terminal establishes a connection with the platform terminal via a first network connection protocol, and the platform terminal establishes a connection with the client terminal via a second network connection protocol. The target monitoring terminal is configured to take screenshots at preset intervals to obtain target images and report these images to the platform terminal. The preset interval is any value greater than or equal to 1 second and less than or equal to 10 seconds. The platform terminal is configured to receive the target images and send indication information to the client to indicate the target images. The client is configured to acquire the indication information of the target images, obtain the target images based on the indication information, and update the client interface based on the target images. Thus, even without supporting standard video streaming protocols, this system utilizes network connection protocols to frequently collect target images at preset intervals, send the images to the platform terminal, and then receive and update the client interface based on the target images. This allows the client to continuously receive frequently collected target images from the target monitoring terminal, achieving near real-time streaming. Furthermore, the system sends target images immediately upon acquisition, without waiting for a certain number of target images to be collected, reducing resource consumption and improving bandwidth utilization. Furthermore, the aforementioned data processing system achieves near real-time monitoring in extremely constrained environments: it completely bypasses reliance on standard video streaming protocols, utilizing only basic HTTP / WebSocket and other common network capabilities and image processing technologies to successfully restore highly timely monitoring functions in scenarios where traditional solutions fail. The system load and resource consumption of this data processing system are extremely low: through a "push-and-delete" caching strategy, the platform only maintains instantaneous data for a few seconds, avoiding long-term storage of massive amounts of images and greatly reducing server storage I / O pressure and database burden. At the transmission level, it also avoids continuous peak bandwidth usage caused by continuous video streams. The aforementioned data processing system has high compatibility and flexibility: the solution is entirely based on application-layer logic, with extremely low requirements for device hardware, operating systems, and client-side underlying capabilities, resulting in strong compatibility. Acquisition frequency, caching strategies, etc., can be dynamically adjusted to adapt to different network environments and monitoring needs. The aforementioned data processing system enhances data security: because the data exists in the form of discrete images and is not persistent on the platform, the risk of data theft in bulk is reduced. It also facilitates encrypted transmission of individual images.

[0077] The above text combined Figures 1 to 8 The data processing system of the embodiments of this application has been described in detail. The data processing method provided by the embodiments of this application will be described below. The data processing method is applied to the platform side of the data processing system and includes: The platform receives the target image and sends indication information to the client to indicate the target image. The platform establishes a connection with the client through a second network connection protocol so that the client can obtain the target image according to the indication information and update the client's interface according to the target image. The target image is a screenshot taken by the target monitoring terminal according to a preset period and reported to the platform. The preset period is any value greater than or equal to 1 second and less than or equal to 10 seconds. The target monitoring terminal establishes a connection with the platform through a first network connection protocol.

[0078] This data processing method also includes: The system receives the target image, stores it on the platform, determines the storage information of the target image, and sends the target image indication information to the client. The target image indication information includes the storage information of the target image, so that the client can obtain the target image according to the storage information.

[0079] It should be understood that the steps of the data processing method in the embodiments of this application can refer to the corresponding processes in the foregoing data processing system embodiments.

[0080] The data processing apparatus provided in the embodiments of this application will now be described. Figure 9 This is a schematic diagram of the data processing apparatus provided in an embodiment of this application. Figure 9 As shown, the data processing device 900 includes a receiving unit 910 and a pushing unit 920, wherein, The receiving unit 910 is used to receive the target image; The push unit 920 is used to send indication information to the client to indicate the target image. The platform establishes a connection with the client through a second network connection protocol, so that the client can obtain the target image according to the indication information and update the client's interface according to the target image. The target image is a screenshot taken by the target monitoring terminal according to a preset period and reported to the platform. The preset period is any value greater than or equal to 1 second and less than or equal to 10 seconds. The target monitoring terminal establishes a connection with the platform through a first network connection protocol.

[0081] It should be understood that the data processing device in the embodiments of this application can execute the data processing method described in the embodiments of this application. That is, the specific working process of the various products below can be referred to the corresponding process in the aforementioned method embodiments.

[0082] It should be understood that each unit module of the data processing device 900 can execute the corresponding steps in the above method embodiments, so the details of each unit module will not be elaborated here. Please refer to the description of the corresponding steps above for details.

[0083] It should be noted that the aforementioned data processing device 900 is embodied in the form of a functional unit. The term "unit" here can be implemented in software and / or hardware, without any specific limitation.

[0084] For example, a “unit” can be a software program, a hardware circuit, or a combination of both that implements the above functions. The hardware circuit may include an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor) and memory for executing one or more software or firmware programs, combined logic circuitry, and / or other suitable components that support the described functions.

[0085] Therefore, the units of the various examples described in the embodiments of this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0086] This application also provides a computer program product that, when executed by a platform in a data processing system, implements the data processing method of any method embodiment in this application.

[0087] The computer program product can be stored in memory, for example, it is a program, which is eventually converted into an executable object file after processes such as preprocessing, compilation, assembly and linking.

[0088] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer, implements the data processing method of any of the method embodiments of this application. The computer program may be a high-level language program or an executable object program.

[0089] The computer-readable storage medium is, for example, memory. Memory can be volatile or non-volatile, or it can include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0090] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0091] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes 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.

[0092] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0093] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0094] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and there may be other division methods in actual implementation; for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0095] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0096] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0097] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data processing system, characterized in that, The data processing system includes: a target monitoring terminal, a platform terminal, and a client terminal. The target monitoring terminal establishes a connection with the platform terminal via a first network connection protocol, and the platform terminal establishes a connection with the client terminal via a second network connection protocol. The target monitoring terminal is configured to take screenshots according to a preset period, obtain target images, and report the target images to the platform terminal. The preset period is any value within 1 second to 10 seconds. The platform is configured to receive the target image and send indication information to the client to indicate the target image. The client is configured to obtain indication information of the target image, obtain the target image according to the indication information of the target image, and update the client's interface according to the target image.

2. The data processing system according to claim 1, characterized in that, The target monitoring terminal executes the step of taking screenshots according to a preset period to obtain target images, specifically configured as follows: Upon receiving a screenshot instruction, the screenshot instruction is used to instruct the target monitoring terminal to take a screenshot according to a preset period. The screenshot instruction is sent by the platform terminal when it receives a viewing request, and the viewing request is sent by the client to the platform terminal. The target image is obtained by taking a screenshot according to the preset period.

3. The data processing system according to claim 1, characterized in that, The platform terminal executes the process of receiving the target image and sending indication information to the client to indicate the target image, specifically configured as follows: Receive the target image; The target image is stored on the platform, and the storage information of the target image is determined; The instruction information is sent to the client, and the instruction information includes the storage information of the target image; Correspondingly, the client executes the process of obtaining the target image based on the indication information of the target image, specifically configured as follows: The target image is obtained based on the storage information of the target image.

4. The data processing system according to claim 3, characterized in that, The platform is also configured as follows: Delete the target image stored in the platform.

5. The data processing system according to claim 4, characterized in that, The platform is configured to delete the target image stored on the platform. If it is confirmed that the client updates the client's interface based on the target image, the target image stored in the platform is deleted.

6. The data processing system according to claim 1, characterized in that, The indication information includes the target image.

7. The data processing system according to claim 1, characterized in that, The first network connection protocol is a long-lived connection protocol.

8. The data processing system according to claim 1, characterized in that, The second network connection protocol is a long-lived connection protocol.

9. A data processing method, characterized in that, The method, applied to the platform side of a data processing system, includes: The platform receives a target image and sends indication information to the client to indicate the target image. The platform establishes a connection with the client through a second network connection protocol, so that the client can obtain the target image according to the indication information and update the client's interface according to the target image. The target image is a screenshot taken by the target monitoring terminal according to a preset period and reported to the platform. The preset period is any value greater than or equal to 1 second and less than or equal to 10 seconds. The target monitoring terminal establishes a connection with the platform through a first network connection protocol.

10. The data processing method according to claim 9, characterized in that, The method further includes: The system receives the target image, stores the target image on the platform, determines the storage information of the target image, and sends the target image indication information to the client. The target image indication information includes the storage information of the target image, so that the client can obtain the target image according to the storage information of the target image.

Images