Efficient thread scheduling method for access service request of video monitoring platform equipment

Abstract

The invention relates to the technical field of video monitoring platform equipment access service request processing, in particular to an efficient thread scheduling method for a video monitoring platform equipment access service request. Comprising a request classification processing step: receiving an equipment access service request, and judging the type of the request; an asking weight distribution step: distributing different weights to different types of requests; an equipment off-line processing step: before processing an equipment access service request, checking the state of equipment related to the request; according to the method, through request classification, weight distribution and equipment state check, the response speed and stability of the system are effectively improved, resource distribution is optimized, the method is suitable for video monitoring platforms in multiple scenes such as a monitoring system and an intelligent home system, requests of different priorities can be efficiently processed, stable operation of the system is guaranteed, and user experience is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of video surveillance platform device access service request processing, and in particular to the request processing and thread scheduling of device access services in a video surveillance platform; specifically, to an efficient thread scheduling method for video surveillance platform device access service requests. Background Art

[0002] In the field of modern video surveillance technology, with the continuous growth of surveillance needs and the widespread deployment of surveillance equipment, the scale and complexity of video surveillance systems are increasing. A typical video surveillance system usually contains many cameras and other related equipment, which continuously generate a large amount of real-time video stream data, accompanied by various control operation requests, such as pan / tilt control (adjusting camera direction, focal length, etc.), image capture, video playback, download, and real-time video transmission.

[0003] In order to ensure that the system can operate normally and respond to various requests in a timely and effective manner, the background service system needs to have strong request management and scheduling capabilities. At present, the main technical means for request processing and thread scheduling is load balancing technology. The core principle of load balancing technology is to dynamically allocate tasks so that all threads can receive a roughly similar number of tasks, thereby avoiding some threads from being overloaded with tasks and preventing other threads from being idle, so as to achieve reasonable utilization of system resources.

[0004] However, this traditional load balancing technology has gradually exposed many shortcomings when it is actually applied to video surveillance platforms. On the one hand, there are many requests with strict timing requirements in video surveillance platforms, such as pan / tilt control operations. In actual usage scenarios, a series of pan / tilt operations (such as focusing before turning, starting before stopping, etc.) must be performed in a specific order, otherwise it may cause inconsistent device status or unexpected behavior, affecting the monitoring effect or even damaging the device. However, load balancing technology does not take this timing characteristic of requests into account when allocating tasks, and cannot ensure that these requests with strict order requirements are processed in the correct order.

[0005] On the other hand, the requests received by the video surveillance platform often have different priorities. For example, in some emergency situations, quickly obtaining images of a specific location (image grabbing request) may be more important than general video playback requests; or in real-time monitoring scenarios, real-time video transmission requests should have higher priority than some non-real-time operation requests. However, load balancing technology mainly focuses on the balanced distribution of requests, and does not perform fine processing based on the priority or weight of the requests. It is difficult to ensure that important requests can be processed first, which affects the overall performance and response speed of the system to a certain extent, and cannot meet the strict requirements of video surveillance systems for efficient operation and fast response.

[0006] In view of the above situation, it is necessary for those skilled in the art to seek a more effective request processing and thread scheduling solution to overcome the limitations of the prior art and meet the growing efficiency and stability requirements of the video surveillance platform. The present invention proposes an innovative and efficient thread scheduling method for access service requests of video surveillance platform devices in response to these problems, aiming to solve the problems of unreasonable request processing order and imprecise priority division in the prior art, thereby improving the overall performance and user experience of the video surveillance system. Summary of the invention

[0007] In view of the shortcomings of the current relevant existing technologies, the present invention aims to provide an efficient thread scheduling method for video surveillance platform device access service requests for various requests received by video surveillance platform device access services (including camera control operation requests, image capture requests, streaming media requests, etc.), so as to overcome the shortcomings of existing load balancing technologies. By optimizing the thread scheduling strategy and setting dynamic weights, the processing priority of requests can be more finely controlled, and the system's processing efficiency and response speed for these requests can be improved, so as to ensure the efficient and stable operation of the video surveillance system.

[0008] To achieve the above object, the technical solution adopted by the present invention is: an efficient thread scheduling method for video monitoring platform device access service request, comprising the following steps: S1. Request classification processing step: receiving a device access service request and determining the request type; The method comprises the steps of: determining whether the request needs to be processed in an orderly manner by checking the character string of the device access service request; adding the request for orderly processing to an orderly request queue; and Asynchronous processing of other request steps: In addition to the orderly processing of ordered requests, other requests are processed asynchronously using new threads; S2, request weight allocation step: Different weights are allocated to different types of requests; the weight mechanism can help the scheduling system better manage the priority of requests so that high-priority requests can be processed in a timely manner; S3, device offline processing step: before processing the device access service request, check the status of the device related to the request; if the device is online, execute step S1; if the device is offline, for any request received, construct an error response and push it to the response queue without actually processing the request.

[0009] Furthermore, the device access service request type includes at least a control operation request, an image capture request, and a streaming media request; If it is identified as a control operation request, the request will be added to the ordered queue, which will be processed first before other requests to ensure timely response to the control operation; If it is identified as a screenshot request, a weight is set and the request is added to the status task queue to ensure that the system gives priority to other requests; If it is identified as a streaming media request, the weight is set and the request is added to the status task queue to ensure timely processing of the streaming media request.

[0010] Furthermore, the ordered request processing step at least includes: S11. Extract a request from the request queue and check the device status related to the request; if the device is offline, construct an error response and push it to the response queue, and then skip the current request.

[0011] S12, check whether the request string contains a predetermined PTZ control command. If the request is an ordered request, add the request information to the ordered task list and continue to process the next request.

[0012] Furthermore, the asynchronous processing of other request steps at least includes: S111, if the request is not an ordered request, check whether the request string contains a screenshot instruction string; if it does, perform subsequent processing, including weight setting; S112: If the request string does not contain a capture instruction string, an asynchronous processing method is adopted to enable a new thread for processing operations, that is, to then check whether the request string contains an identifier related to streaming media push to identify requests related to playback, downloading, real-time video or intercom.

[0013] Furthermore, in the request weight allocation step: it also at least includes: S21. The weight setting can play a role in priority management in the scheduling system. When processing a capture request, its weight is set to the highest. In this way, the capture request will be processed by the system first, ensuring that important image acquisition requests will not be delayed in high-load or multi-request scenarios. S22. For other types of requests, including playback, download, real-time video and intercom requests, whether these requests need to be weighted is determined by checking whether the request string contains an identifier related to streaming media push; if it is found that the request string contains an identifier related to streaming media push, the weight of this type of request is increased and set to the highest; When processing requests, the priority of the request is determined according to its weight, with high-weight requests being processed first. The system dynamically adjusts the processing strategy for different requests to ensure that when multiple requests arrive at the same time, the system can reasonably allocate resources to improve response speed and processing efficiency. Flexible weight allocation strategies can optimize the scheduling and processing of requests based on actual conditions.

[0014] The present invention adopts the above technical solution, which has at least the following beneficial effects: 1. Improve system response speed: Different types of requests (such as control operations, image capture, and streaming media requests) can be processed according to their priorities and weights, allowing the system to effectively cope with diverse tasks and loads. By classifying requests into ordered requests and other requests, and setting different processing mechanisms for different types of requests, the ordered request queue ensures that operations such as pan / tilt control that have strict order requirements can be executed in sequence, avoiding device operation conflicts and delays caused by disordered request order, and reducing processing time. Other requests are processed asynchronously, and the activation of new threads greatly improves the system's concurrent processing capabilities, allowing the system to quickly respond to various requests when faced with a large influx of requests, especially in high-load or multi-request scenarios, effectively shortening the overall waiting time for request processing and significantly improving the system's response speed.

[0015] A dynamic weight allocation mechanism with different weights is set according to the request type and characteristics, so that the system can accurately identify high-priority requests and give priority to them, avoiding the blocking of key request processing by low-priority requests, ensuring that important information can be obtained or key operations can be performed in a timely manner, further improving the timeliness of the system's response to key tasks, and optimizing the system's response performance as a whole.

[0016] 2. Enhanced system stability: The mechanism for checking the device status before processing a request effectively prevents requests from being sent to offline devices. When a device is offline, the system promptly constructs an error response and pushes it to the response queue, and does not process invalid requests, thus avoiding request failures due to device unavailability and possible system errors and resource waste, ensuring the stability of system operation, and reducing the probability of system crashes or abnormal situations caused by device failures, allowing the system to operate stably in a complex and changing device environment.

[0017] The ordered request processing mechanism ensures the sequence and accuracy of device control operations, avoiding unstable equipment states or abnormal behaviors caused by disordered operation sequences. Problems such as zoom failure caused by improper sequence in pan / tilt control are effectively solved, enhancing the stability and reliability of the system from the device operation level, providing a solid guarantee for the continuous and stable operation of the video surveillance system.

[0018] 3. Optimize system resource allocation: Dynamic weight setting enables the system to reasonably allocate resources according to the importance and urgency of the request. High-weight requests are given priority in resource allocation. For example, processing power, bandwidth and other resources are prioritized to important screenshot requests or real-time video streaming push requests to ensure that key requests are processed efficiently under sufficient resources. At the same time, for low-priority requests, processing can be appropriately delayed when system resources are relatively tight to avoid affecting the processing efficiency of high-priority requests due to a large number of low-priority requests occupying too many resources, thus achieving refined management and optimized configuration of system resources and improving resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 1 It is a flow chart of the thread scheduling method of the present invention; Figure 2 It is a schematic diagram of an embodiment of the monitoring and scheduling system of the present invention. DETAILED DESCRIPTION

[0021] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0022] Embodiment 1

[0023] See also Figure 1 This embodiment provides an efficient thread scheduling method for video surveillance platform device access service request, including the following steps: S1. Request classification processing step: receiving a device access service request and determining the request type; The method comprises the steps of: determining whether the request needs to be processed in an orderly manner by checking the character string of the device access service request; adding the request for orderly processing to an orderly request queue; and Asynchronous processing of other request steps: In addition to the orderly processing of ordered requests, other requests are processed asynchronously using new threads; S2, request weight allocation step: Different weights are allocated to different types of requests; the weight mechanism can help the scheduling system better manage the priority of requests so that high-priority requests can be processed in a timely manner; S3, device offline processing step: before processing the device access service request, check the status of the device related to the request; if the device is online, execute step S1; if the device is offline, for any request received, construct an error response and push it to the response queue without actually processing the request.

[0024] As an implementation mode, the device access service request type in this embodiment at least includes a control operation request, an image capture request and a streaming media request; If it is identified as a control operation request, the request will be added to the ordered queue, which will be processed first before other requests to ensure timely response to the control operation; If it is identified as a screenshot request, a weight is set and the request is added to the status task queue to ensure that the system gives priority to other requests; If it is identified as a streaming media request, the weight is set and the request is added to the status task queue to ensure timely processing of the streaming media request.

[0025] As an implementation mode, in this embodiment, the ordered request processing step at least includes: S11. Extract a request from the request queue and check the device status related to the request; if the device is offline, construct an error response and push it to the response queue, and then skip the current request.

[0026] S12, check whether the request string contains a predetermined PTZ control command. If the request is an ordered request, add the request information to the ordered task list and continue to process the next request.

[0027] As an implementation mode, in this embodiment, the asynchronous processing of other requests step at least includes: S111, if the request is not an ordered request, check whether the request string contains a screenshot instruction string; if it does, perform subsequent processing, including weight setting; S112: If the request string does not contain a capture instruction string, an asynchronous processing method is adopted to enable a new thread for processing operations, that is, to then check whether the request string contains an identifier related to streaming media push to identify requests related to playback, downloading, real-time video or intercom.

[0028] As an implementation mode, in this embodiment, the request weight allocation step also includes at least: S21. The weight setting can play a role in priority management in the scheduling system. When processing a capture request, its weight is set to the highest. In this way, the capture request will be processed by the system first, ensuring that important image acquisition requests will not be delayed in high-load or multi-request scenarios. S22. For other types of requests, including playback, download, real-time video and intercom requests, whether these requests need to be weighted is determined by checking whether the request string contains identifiers related to streaming media push; if it is found that the request string contains identifiers related to streaming media push (including but not limited to query recording control commands), the weight of this type of request is increased and set to the highest; When processing requests, the priority of the request is determined according to its weight, with high-weight requests being processed first. The system dynamically adjusts the processing strategy for different requests to ensure that when multiple requests arrive at the same time, the system can reasonably allocate resources to improve response speed and processing efficiency. Flexible weight allocation strategies can optimize the scheduling and processing of requests based on actual conditions.

[0029] The present invention provides a comprehensive request processing and thread scheduling method, which optimizes the response time and reliability of the system through effective request classification, priority management, and device status inspection. The system can handle ordered requests and other requests, and improve the priority of requests through weight management to ensure the stable operation of the system.

[0030] Embodiment 2

[0031] 1. Request processing in monitoring and scheduling system: like Figure 2 As shown, in the monitoring and scheduling system, three key request types are defined, namely, control operation request, image capture request and streaming media request. This embodiment will elaborate on the processing flow and weight allocation for these three request types.

[0032] (I) Control operation request (taking PTZ control as an example) Sample request: C_PTZ_Start (start PTZ control command); Processing steps: a. Check the request type and identify it as a control operation request.

[0033] b. Call the function to add it to the ordered queue.

[0034] c. The processing of the ordered queue takes precedence over other requests to ensure timely response of control operations.

[0035] When receiving the sample request C_PTZ_Start (start PTZ control command): First, the request type is checked and the request is analyzed through a specific string matching algorithm. Once the request is identified as a control operation request type,

[0036] Then call a function (for example, call the function add_order_task) to add this request to the ordered processing queue. Since the ordered processing queue has the highest priority in the entire request processing system, its processing order takes precedence over all other types of request queues. This ensures that control operations such as PTZ control, which have extremely high requirements for real-time and sequentiality, can be processed in a timely and orderly manner, and the user's PTZ operation instructions can be quickly responded to and executed in the video surveillance system, effectively avoiding abnormal PTZ control caused by request processing delays or disordered sequences, such as PTZ rotation delays caused by untimely instruction processing or conflicts between PTZ focus and rotation operations caused by incorrect sequences.

[0037] (II) Image crawling request Sample request: C_IV_GetThumbnail (capture control command); Processing steps: a. Check the request type and identify it as a screenshot request.

[0038] b. Set weights.

[0039] c. Add the request to the status task queue to ensure that the system takes priority when processing other requests The system uses the request analysis module to check the request type and accurately identifies it as an image capture request.

[0040] According to the pre-set weight allocation rule, a specific weight value (such as 5) is set for the screenshot request. This weight value indicates the high priority attribute of the request in the entire request scheduling system.

[0041] The request is then added to the status task queue, which is mainly used to store and manage pending tasks. Tasks (such as snapshot requests) are scheduled according to their priority or weight to ensure that important tasks can be executed in time. When a new request (such as a snapshot request) arrives, it will be placed in the status task queue. At this time, the task is in the "pending" state, waiting for system scheduling. Since the snapshot request has a higher weight in the status task queue, the system will give priority to processing the snapshot request. Once the snapshot request is scheduled and assigned to the processing unit, it will enter the status processing queue, which means that the task is in the processing stage of the task life cycle, resources have been allocated, and the task is waiting to be executed. In this way, in actual application scenarios, when the user has the need to quickly obtain the monitoring screen at a specific moment, the system can quickly respond and execute the snapshot operation, and provide the user with the required image information in time, which greatly improves the efficiency of users in obtaining key image data. Especially in some monitoring scenarios with high requirements for the timeliness of image information, such as the rapid image capture of suspicious persons or events in security monitoring, this mechanism plays an extremely important role.

[0042] Streaming media request Sample request: C_SG_DownloadByTime_PushMode (query recording control command) Processing steps: a. Check whether the request contains the streaming media request identifier PushMode (streaming media push related type request).

[0043] b. If it is a streaming media request, set the weight.

[0044] c. Add the request to the status task queue to ensure timely processing of streaming media requests.

[0045] The system first checks whether the request contains a specific streaming request identification string "_PushMode" and uses an efficient string search algorithm to detect it.

[0046] If it is detected that the request belongs to the streaming media request type, a corresponding weight (such as 5) is set for it according to the weight allocation strategy, giving it a higher processing priority.

[0047] Finally, the request is added to the status task queue to ensure that the streaming media request can be processed promptly and effectively. In actual video surveillance applications, whether it is the stable push of real-time monitoring video streams or the query and download of historical recordings, this streaming media request processing mechanism can ensure the smooth transmission and acquisition of video data, avoid video freezes, interruptions or delays caused by untimely request processing, and provide users with a high-quality video surveillance experience.

[0048] 2. Application scenario display 1. Monitoring system scenario In a typical monitoring system application scenario, users may initiate multiple different types of requests at the same time, such as PTZ control commands, image capture requests, and video stream requests.

[0049] For PTZ control requests, since they are added to an ordered queue and have priority processing, the system can quickly capture and execute the user's operating instructions, ensuring that the PTZ can rotate, focus and perform other operations in real time according to the user's wishes, thereby achieving flexible adjustment and precise control of the monitoring scene.

[0050] With its high weight, the capture request occupies an advantageous position in the allocation of system resources and the order of request processing. When a user needs to quickly obtain the monitoring screen at a certain moment, the system can give priority to the capture request among many concurrent requests, and provide the user with clear and accurate image data in a timely manner to meet the user's demand for rapid acquisition of key image information. For example, when a suspicious event is monitored, the relevant screen can be quickly captured for subsequent analysis and processing.

[0051] Streaming media requests are also given priority in the system processing process because of their high weight. Whether it is the push of real-time monitoring video streams or the video query and download operations, they can remain smooth and stable, and will not cause video freezes or interruptions due to interference from other requests, which will affect the monitoring effect. This ensures the continuous and stable transmission of monitoring video information, provides monitoring personnel with uninterrupted video monitoring data, and ensures the efficient conduct of monitoring work.

[0052] 2. Smart Home System Scenario In a smart home environment, users may simultaneously issue multiple different types of requests, such as adjusting lights, adjusting camera angles, and viewing current surveillance images.

[0053] Control operation requests such as camera angle adjustment will be processed as control operation requests, added to an ordered queue and given priority, so that users can quickly and accurately adjust the camera's viewing angle, meeting their needs for flexible control over the viewing angle of their home environment monitoring.

[0054] The request to view the current monitoring screen is similar to an image capture request or a streaming media request. It is assigned a corresponding weight according to its type and added to the status task queue for priority processing, ensuring that the user can obtain clear and smooth monitoring video or image information in a timely manner, making it convenient for the user to understand the real-time status of the home environment at any time.

[0055] Through this thread scheduling mechanism that processes requests in an orderly manner and allocates dynamic weights, the smart home system can effectively manage and coordinate the processing of various different types of requests, avoiding system response delays or functional abnormalities caused by request conflicts or unreasonable resource allocation, thereby providing users with a smooth and convenient smart home experience and improving user satisfaction and trust in the smart home system.

[0056] In summary, by implementing refined request classification, dynamic weight setting, and orderly request management in actual application scenarios such as monitoring and scheduling systems and smart home systems, the entire scheduling system can efficiently and accurately handle requests of different priorities, ensuring that all types of key operations can be responded to and executed in a timely and effective manner. This innovative strategy has shown significant advantages in actual application. It not only greatly improves the stability of the system, effectively reduces the probability of system failures and abnormal situations caused by improper request processing, but also greatly improves the response speed of the system, and can more quickly meet the diverse needs of users for video surveillance systems in different scenarios, providing solid and reliable technical support and guarantee for the widespread application of video surveillance technology in various fields.

[0057] Although the embodiments of the present invention have been shown and described above, it will be appreciated that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, substitute and vary the above embodiments within the scope of the present invention.

Claims

1. An efficient thread scheduling method for video surveillance platform device access service request, characterized in that: The steps include: S1. Request classification processing step: receiving a device access service request and determining the request type; The method comprises the steps of orderly request processing: determining whether the request needs to be processed in an orderly manner by checking a character string of a device access service request; Add the ordered processing request to the ordered request queue; and Asynchronous processing of other request steps: In addition to the orderly processing of ordered requests, other requests are processed asynchronously using new threads; S2, request weight assignment step: different weights are assigned to different types of requests; The weight mechanism can help the scheduling system better manage the priority of requests so that high-priority requests can be processed in a timely manner; S3, device offline processing step: before processing the device access service request, check the status of the device related to the request; if the device is online, execute step S1; if the device is offline, for any request received, construct an error response and push it to the response queue without actually processing the request.

2. The method according to claim 1, characterized in that: The device access service request types include at least control operation requests, image capture requests and streaming media requests; If it is identified as a control operation request, the request will be added to the ordered queue, which will be processed first before other requests to ensure timely response to the control operation; If it is identified as a screenshot request, a weight is set and the request is added to the status task queue to ensure that the system gives priority to other requests; If it is identified as a streaming media request, the weight is set and the request is added to the status task queue to ensure timely processing of the streaming media request.

3. The method according to claim 2, characterized in that: The steps in the ordered request processing include at least: S11, extract a request from the request queue and check the device status related to the request; if the device is offline, construct an error response and push it to the response queue, and then skip the current request; S12, checking whether the request character string contains a predetermined PTZ control command; if the request is an ordered request, adding the request information to the ordered task list, and continuing to process the next request.

4. The method according to claim 3, characterized in that: The asynchronous processing of other request steps includes at least: S111, if the request is not an ordered request, check whether the request string contains a screenshot instruction string; if it does, perform subsequent processing, including weight setting; S112: If the request string does not contain a capture instruction string, an asynchronous processing method is adopted to enable a new thread for processing operations, that is, to then check whether the request string contains an identifier related to streaming media push to identify requests related to playback, downloading, real-time video or intercom.

5. The method according to claim 4, characterized in that: The request weight allocation step also includes at least: S21. The weight setting can play a role in priority management in the scheduling system. When processing a capture request, its weight is set to the highest. In this way, the capture request will be processed by the system first, ensuring that important image acquisition requests will not be delayed in high-load or multi-request scenarios. S22. For other types of requests, including playback, download, real-time video and intercom requests, whether these requests need to be weighted is determined by checking whether the request string contains an identifier related to streaming media push; if it is found that the request string contains an identifier related to streaming media push, the weight of this type of request is increased and set to the highest; When processing requests, the priority of the request is determined according to its weight, with high-weight requests being processed first. The system dynamically adjusts the processing strategy for different requests to ensure that when multiple requests arrive at the same time, the system can reasonably allocate resources to improve response speed and processing efficiency. Flexible weight allocation strategies can optimize the scheduling and processing of requests based on actual conditions.

Images