Point scheduling processing method, device and edge computing controller

Abstract

This application relates to a point scheduling processing method, device, and edge computing controller, belonging to the field of point scheduling processing technology. This application includes: determining the service quality information configuration of the point under the specific process, wherein one monitoring object of a device corresponds to one point; based on the service quality information configuration of the point, using the thread under the specific process, to schedule the point. This application helps to solve the problem of points with high real-time response requirements not being prioritized for monitoring and processing.

Description

Technical Field

[0001] The present application belongs to the field of point scheduling processing technology, and specifically relates to a point scheduling processing method, device and edge computing controller. Background Art

[0002] In the related art, the controller monitors the points of each device under its control, wherein a monitoring object of a device corresponds to a point, such as: a monitored temperature of a device can be used as a point, a monitored humidity of a device can be used as a point, a switch status of a device can be used as a point, and so on.

[0003] Controllers typically use a time-slice polling method to monitor various points, executing corresponding processing operations based on a first-come, first-served basis. However, in real-time applications, some points, such as emergency alarms, require priority monitoring and processing. However, using a time-slice polling method, these points are not prioritized, thus failing to meet the need for prioritizing monitoring and processing for these points. Summary of the Invention

[0004] To this end, the present application provides a point scheduling processing method, device and edge computing controller, which helps to solve the problem that points with high real-time response requirements are not monitored and processed as a priority.

[0005] To achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, the present application provides a point scheduling processing method, the method comprising:

[0007] For a specific process, determining the service quality information configuration of a point under the specific process, wherein a monitoring object of a device corresponds to one of the points;

[0008] Based on the configuration of the quality of service information of the point, the point is scheduled using the thread under the specific process.

[0009] Furthermore, if the specific process is a downlink monitoring process, the downlink monitoring process is used to monitor the device;

[0010] The scheduling process for the point based on the configuration of the quality of service information of the point and using the thread under the specific process includes:

[0011] Determine a method for adding the point to the message queue based on whether the point is configured with the service quality information, wherein the adding method includes: stack addition or insertion addition;

[0012] Based on the adding method of the point, the point is added to the message queue through the scheduling thread under the downlink monitoring process;

[0013] The scheduling thread is used to push the points to the monitoring service thread under the downlink monitoring process based on the order of the points in the message queue, so that the monitoring service thread triggers the acquisition of corresponding point information each time it receives a push.

[0014] Furthermore, the determining of a method for adding the point to the message queue based on whether the point is configured with the service quality information includes:

[0015] If the point is not configured with the service quality information, determining that the point is added to the message queue in a stack addition mode;

[0016] If the point is configured with the service quality information, it is determined that the adding mode of the point in the message queue is insertion addition.

[0017] Furthermore, the adding method based on the point, adding the point to the message queue through the scheduling thread under the downlink monitoring process, includes:

[0018] If the point is added by insertion, the scheduling thread uses the service quality information of the point to determine the insertion position of the point in the message queue, and adds the point to the message queue based on the determined insertion position.

[0019] Furthermore, the method further comprises:

[0020] If the point exists and is added to the message queue by insertion, determine whether all the points in the message queue can be pushed out within the preset push cycle. If not, determine the points in the message queue that cannot be pushed out, and adjust the positions of the points that cannot be pushed out in the message queue forward.

[0021] Furthermore, the adding method based on the point, adding the point to the message queue through the scheduling thread under the downlink monitoring process, includes:

[0022] If the point is added in a stack manner, the point is added to the message queue in a stack manner through the scheduling thread.

[0023] Furthermore, if the specific process is an uplink service process, the uplink service process is used to interact with a host computer;

[0024] The scheduling process for the point based on the configuration of the quality of service information of the point and using the thread under the specific process includes:

[0025] The target thread under the uplink service process used by the point is determined by using whether the point is configured with the service quality information, and the point is scheduled through the determined target thread.

[0026] Furthermore, the step of determining a target thread under the uplink service process used by the point based on whether the point is configured with the service quality information, and performing scheduling processing on the point through the determined target thread, includes:

[0027] If the point is not configured with the service quality information, determining that the target thread used by the point is a request thread, and periodically obtaining the point information of the point from a database storing point information through the request thread;

[0028] If the point is configured with the service quality information, it is determined that the target thread used by the point is a control service thread, and the point is scheduled using the control service thread through the scheduling thread under the downlink monitoring process.

[0029] In a second aspect, the present application provides a point scheduling processing device, the device comprising:

[0030] A determination module, configured to determine, for a specific process, a configuration status of service quality information of a point under the specific process, wherein one monitoring object of one device corresponds to one of the points;

[0031] A processing module is used to schedule the point based on the service quality information configuration of the point and using the thread under the specific process.

[0032] In a third aspect, the present application provides an edge computing controller, comprising:

[0033] a memory having an executable program stored therein;

[0034] A processor is used to execute the executable program in the memory to implement the steps of any one of the above methods.

[0035] Furthermore, the edge computing controller is applied to the emergency management system of a mobile experimental vehicle.

[0036] This application adopts the above technical solution, which has at least the following beneficial effects:

[0037] This application determines the service quality information configuration of the point under a specific process. The service quality information configuration of the point can represent the real-time response requirements of the point. Therefore, based on the service quality information configuration of the point, the point is scheduled and processed using the thread under the specific process, which helps to give priority to monitoring and processing points with high real-time response requirements.

[0038] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0040] Figure 1 is a flow chart showing a method for point scheduling processing according to an exemplary embodiment;

[0041] Figure 2 This is a schematic diagram showing the relationship between thread data transmission in a downlink monitoring process and an uplink service process according to an exemplary embodiment;

[0042] Figure 3 1 is a flowchart illustrating a point scheduling process in a downlink monitoring process according to an exemplary embodiment;

[0043] Figure 4 is a schematic diagram showing a message queue insertion and adding point according to an exemplary embodiment;

[0044] Figure 5 is a schematic diagram showing a message queue insertion adding point according to another exemplary embodiment;

[0045] Figure 6 is a block diagram of a point scheduling processing device according to an exemplary embodiment;

[0046] Figure 7 The present invention is a block diagram of an edge computing controller according to an exemplary embodiment. DETAILED DESCRIPTION

[0047] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be described in detail below. Obviously, the embodiments described are only some of the embodiments of this application, rather than all of them. Based on the embodiments in this application, all other implementation methods obtained by ordinary technicians in this field without making any creative work are within the scope of protection of this application.

[0048] See also Figure 1 , Figure 1 FIG. 1 is a flow chart showing a method for point scheduling processing according to an exemplary embodiment, the method comprising the following steps:

[0049] Step S11: for a specific process, determining the configuration of the service quality information of the points under the specific process, wherein one monitoring object of one device corresponds to one point.

[0050] For specific processes, independent process tasks can be divided according to the interface functions of the controller. For example, when the controller has RS485-1, RS485-2, CAN-1 and CAN-2 interfaces, the four interfaces are each processed by an independent service process. The specific processes are independent of each other, and each specific process is processed by multiple threads.

[0051] Each monitored object on a device corresponds to a location. For example, a temperature monitoring location on the device can be a location, a humidity monitoring location can be a location, a switch status location can be a location, and so on. Locations can be represented by assigning them ID numbers. For example, a temperature monitoring location on the device can be a location and configured as location 1; a humidity monitoring location can be a location and configured as location 2; and a switch status location can be a location and configured as location 3.

[0052] For service quality information (Qos, Quality of Service), you can query the relevant technical content. In this application, for the service quality information configuration of each point, it can be that some points are configured with service quality information, while other points are not configured with service quality information. The service quality information configuration of the point can represent the real-time response demand of the point. For the point that is not configured with service quality information, it can be indicated that its real-time response demand is low or non-existent, and for the point that is configured with service quality information, it can be indicated that its real-time response demand is high and needs to be monitored and processed first.

[0053] Step S12: Based on the configuration of the quality of service information of the point, the thread under the specific process is used to schedule the point.

[0054] Multiple threads are created under each specific process, and point scheduling is handled by the thread process under the specific process.

[0055] The service quality information configuration of a point can represent the real-time response requirements of the point. Therefore, based on the service quality information configuration of the point, the points are scheduled using the threads under the specific process, which helps to prioritize the monitoring and processing of points with high real-time response requirements.

[0056] The specific process can be divided into downlink monitoring process and uplink service process. The downlink monitoring process is used to monitor the device, and the uplink service process is used to interact with the host computer. The downlink monitoring process and the uplink service process each have multiple threads. Figure 2 , Figure 2 The figure is a schematic diagram showing the relationship between thread data transmission between a downlink monitoring process and an uplink service process according to an exemplary embodiment.

[0057] In one embodiment, see Figure 3 , Figure 3 FIG. 1 is a flowchart of point scheduling processing in a downlink monitoring process according to an exemplary embodiment. In step S12, in the case of a downlink monitoring process, the following steps may be included:

[0058] Step S121: Determine a method for adding the point to the message queue based on whether the point is configured with the service quality information, wherein the adding method includes: stack addition or insertion addition;

[0059] Step S122: Based on the adding method of the point, the point is added to the message queue through the scheduling thread under the downlink monitoring process;

[0060] Step S123: Using the scheduling thread, based on the order of the points in the message queue, push the points to the monitoring service thread under the downlink monitoring process, so that the monitoring service thread triggers the acquisition of corresponding point information each time it receives a push.

[0061] In this application, the downlink monitoring process is divided into a scheduling thread and a monitoring service thread according to the function of the business thread. The scheduling thread determines how the point is scheduled and pushed, and the monitoring service thread triggers the execution to obtain the point information of the point through push, thereby achieving collaborative cooperation to improve processing efficiency.

[0062] In actual applications, the scheduling thread obtains the point configuration information from the Sqlite in the controller, including the point ID number and service quality information, and determines the method of adding the point in the message queue based on whether the point is configured with service quality information. The adding method includes stack addition or insertion addition. Specifically, if the point is not configured with the service quality information, it is determined that the point is added in the message queue in a stack addition manner, indicating that the point has a low or no real-time response requirement. For the point that is not configured with the service quality information, the stack addition method is used to add it to the message queue. If the point is configured with the service quality information, it is determined that the point is added in the message queue in an insertion addition manner, indicating that the point has a high real-time response requirement. Insertion addition is used to obtain scheduling priority so that it can be scheduled first.

[0063] In actual applications, a hash list is formed based on the location ID and QoS information, and used as a message queue. The scheduling thread pushes the locations to the monitoring service thread in order according to the order in the message queue. The monitoring service thread triggers the acquisition of the corresponding location information each time it receives a push from the scheduling thread. For example, if the scheduling thread pushes location 1 (monitoring temperature) to the monitoring service thread, the monitoring service thread receives the push and triggers the acquisition of the temperature information for the corresponding device location 1. The monitoring service thread can store the acquired location information in a Redis database.

[0064] In one embodiment, step S122 includes the following:

[0065] If the point is added in a stack manner, the point is added to the message queue in a stack manner through the scheduling thread.

[0066] Specifically, when the point is added in a stack manner, it indicates that the point has low or no real-time response requirement. For this point, the point is added to the message queue in a stack manner through the scheduling thread.

[0067] In one embodiment, step S122 further includes the following:

[0068] If the point is added by insertion, the scheduling thread uses the service quality information of the point to determine the insertion position of the point in the message queue, and adds the point to the message queue based on the determined insertion position.

[0069] Specifically, when the point is added by insertion, it indicates that the point has a high real-time response requirement. For this point, the scheduling thread uses the point's service quality information to determine the insertion position of the point in the message queue. The service quality information can be in the form of a service quality value. It can be stipulated that the larger the service quality value, the higher the point's real-time response requirement. Figure 4 , Figure 4 FIG. 1 is a schematic diagram showing a message queue insertion adding point according to an exemplary embodiment. Figure 4 In the example, 1101, 1010, 1001, and 1005 represent four points, respectively. The value corresponding to the key indicates the order in which the message queue is pushed, which is 1, 2, and 3. The value in the dotted box indicates the number of points pushed each time. Points 1101 and 1010 are not configured with quality of service information and are added to the message queue in a stacked manner. Points 1001 and 1005 are configured with quality of service information and are added to the message queue in an inserted manner. Figure 4 In the illustrated scenario, both are inserted at the head of the message queue, indicating that the service quality values ​​of point 1001 and point 1005 are the same. In actual applications, if the service quality values ​​of point 1001 and point 1005 are different, and if it is stipulated that the larger the service quality value, the higher the response time requirement of the point, then the point with the larger service quality value will be inserted at the head of the queue, and the point with the smaller service quality value will be inserted at the second position immediately after the head.

[0070] In one embodiment, the method further comprises:

[0071] If the point exists and is added to the message queue by insertion, determine whether all the points in the message queue can be pushed out within the preset push cycle. If not, determine the points in the message queue that cannot be pushed out, and adjust the positions of the points that cannot be pushed out in the message queue forward.

[0072] Specifically, within a push cycle, there is a set time interval between two point pushes. Please refer to Figure 4 If the two points 1001 and 1005 are not inserted, the scheduling thread can push points 1101 and 1010 twice in succession within one push cycle. However, when points 1001 and 1005 are inserted into the head of the message queue in parallel, three pushes are required in succession within the push cycle. It is possible that because points 1001 and 1005 are inserted into the head of the message queue, the push of 1101 cannot be completed within one push cycle, which leads to the failure of point 1101 to be monitored this time. The above solution of this application can solve this problem. Please refer to Figure 5 , Figure 5 FIG. 1 is a schematic diagram showing a message queue insertion adding point according to another exemplary embodiment, wherein: Figure 5 Please refer to the graphic symbols in Figure 4 By the solution of this application, when the two points 1001 and 1005 are inserted into the head of the message queue in parallel, if it is determined that the points in the message queue cannot be pushed out within the preset push cycle, Figure 5 It is shown that the point 1101 is determined to be a point that cannot be pushed out, and the point 1101 is adjusted forward one position in the message queue to the position of the point 1010, and pushed in parallel with the point 1010, so that the scheduling thread is for Figure 5 The message queue makes two pushes in one push cycle. First, points 1001 and 1005 are pushed in parallel, and then points 1101 and 1010 are pushed in parallel, ensuring that all points in the message queue are pushed out in the push cycle.

[0073] In one embodiment, for step S12, in the case of an uplink monitoring process, the uplink service process is used to interact with the host computer, and may include the following steps:

[0074] The target thread under the uplink service process used by the point is determined by using whether the point is configured with the service quality information, and the point is scheduled through the determined target thread.

[0075] For the controller, there may be a host computer. Through this solution, the host computer request data is provided by the upstream service process. Through this solution, according to whether the point is configured with the said service quality information, it is determined whether it has a corresponding target thread under the upstream service process. For two types of points, those with service quality information and those without service quality information, point scheduling can be carried out through their respective corresponding target threads under the upstream service process, so that points with high real-time response requirements can be monitored and processed separately with priority.

[0076] See also Figure 2 The uplink service process is provided with a request thread and a control service thread. Based on these two threads, the present application provides the following embodiment scheme, including:

[0077] If the point is not configured with the service quality information, determining that the target thread used by the point is a request thread, and periodically obtaining the point information of the point from a database storing point information through the request thread;

[0078] If the point is configured with the service quality information, it is determined that the target thread used by the point is a control service thread, and the point is scheduled using the control service thread through the scheduling thread under the downlink monitoring process.

[0079] In actual applications, the request thread corresponds to a point that is not configured with the service quality information. This type of point is a periodic business point and is not sensitive to latency. The request thread can periodically request data from the Redis database and return the data to the host computer.

[0080] The controller needs to coordinate with the host computer to issue control commands. The points corresponding to these control commands have high latency requirements and require priority processing. The control service thread corresponds to points configured with quality of service information. The points corresponding to the host computer's control commands fall into this category. In practical applications, these points can be configured with quality of service information. This is then handled by the control service thread, which prioritizes these points through the scheduling thread under the downlink monitoring process.

[0081] See also Figure 6 , Figure 6 : is a block diagram of a point scheduling processing device according to an exemplary embodiment. The point scheduling processing device 6 includes:

[0082] A determination module 61 is configured to determine, for a specific process, a configuration of service quality information of a point under the specific process, wherein a monitoring object of a device corresponds to one of the points;

[0083] The processing module 62 is configured to schedule the point based on the configuration of the quality of service information of the point and using the thread under the specific process.

[0084] Furthermore, the processing module 62 specifically includes:

[0085] A downlink processing unit is used for: if the specific process is a downlink monitoring process, the downlink monitoring process is used to monitor the device; using whether the point is configured with the service quality information, determining the adding method of the point in the message queue, the adding method including: stack addition or insertion addition; based on the adding method of the point, adding the point to the message queue through the scheduling thread under the downlink monitoring process; using the scheduling thread, based on the sorting of the points in the message queue, pushing the point to the monitoring service thread under the downlink monitoring process, so that the monitoring service thread triggers the acquisition of corresponding point information each time it receives a push.

[0086] Furthermore, in the downlink processing unit, if the point is not configured with the service quality information, the point is determined to be added to the message queue in a stack addition manner; if the point is configured with the service quality information, the point is determined to be added to the message queue in an insert addition manner.

[0087] Furthermore, in the downlink processing unit, if the point is added by insertion, the scheduling thread uses the service quality information of the point to determine the insertion position of the point in the message queue, and based on the determined insertion position, the point is added to the message queue.

[0088] Furthermore, the downlink processing unit is also used to: if the point exists and is added to the message queue by insertion, determine whether all the points in the message queue can be pushed out within the preset push cycle; if not, determine the points in the message queue that cannot be pushed out, and adjust the position of the points that cannot be pushed out in the message queue forward.

[0089] Furthermore, in the downlink processing unit, if the point is added in a stack manner, the point is added to the message queue in a stack manner through the scheduling thread.

[0090] Furthermore, the processing module 62 specifically includes:

[0091] An uplink processing unit is used for: if the specific process is an uplink service process, the uplink service process is used to interact with the host computer; based on whether the point is configured with the service quality information, determining the target thread under the uplink service process used by the point, and scheduling the point through the determined target thread.

[0092] Furthermore, the uplink processing unit is specifically configured to:

[0093] If the point is not configured with the service quality information, determining that the target thread used by the point is a request thread, and periodically obtaining the point information of the point from a database storing point information through the request thread;

[0094] If the point is configured with the service quality information, it is determined that the target thread used by the point is a control service thread, and the point is scheduled using the control service thread through the scheduling thread under the downlink monitoring process.

[0095] Regarding the point scheduling processing device 6 in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the above related method, and will not be elaborated here.

[0096] See also Figure 7 , Figure 7 FIG. 1 is a block diagram of an edge computing controller according to an exemplary embodiment. The edge computing controller 7 includes:

[0097] Memory 701, on which executable programs are stored;

[0098] The processor 702 is configured to execute the executable program in the memory 701 to implement the steps of any one of the above methods.

[0099] Regarding the edge computing controller 7 in the above embodiment, the specific manner in which its processor 702 executes the program in the memory 701 has been described in detail in the above embodiment of the relevant method and will not be elaborated here.

[0100] In one embodiment, the edge computing controller can be applied to a mobile experimental vehicle emergency management system.

[0101] In practical applications, the edge computing controller 7 can be applied to the emergency management system of mobile experimental vehicles. With the improvement of the medical system and the development of science and technology, the demand for mobile biomedical research experimental vehicles in various places is getting higher and higher. As the amount of device data that the intelligent system of mobile experimental vehicles needs to access is getting larger and larger, the centralized control platform can no longer meet the real-time requirements of the data. As an emerging controller mode, the edge computing controller can process data in a timely manner near the device end without going through the logical judgment of the centralized control platform, which can effectively reduce the bottleneck of network bandwidth and delay and the load pressure of the platform server. The mobile experimental vehicle emergency management system applies the edge computing controller solution of this application. In terms of point scheduling, for some points, emergency processing requires higher latency requirements and needs to have priority. These points can be scheduled and processed first.

[0102] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.

[0103] It should be noted that, in the description of this application, the terms "first," "second," etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. In addition, in the description of this application, unless otherwise specified, the meaning of "plurality" or "multiple" is at least two.

[0104] It should be understood that when an element is referred to as being "fixed to" or "disposed on" another element, it can be directly on the other element or there may be an intermediate element at the same time; when an element is referred to as being "connected to" another element, it can be directly connected to the other element or there may be an intermediate element at the same time. In addition, the "connection" used here may include wireless connection; the wording "and / or" used includes any unit and all combinations of one or more associated listed items.

[0105] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present application belong.

[0106] It should be understood that various parts of the present application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used to implement: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0107] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0108] In addition, the functional units in the various embodiments of the present application may be integrated into a processing module 62, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

[0109] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0110] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0111] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A point scheduling processing method, characterized in that: The method comprises: For a specific process, determining the service quality information configuration of a point under the specific process, wherein a monitoring object of a device corresponds to one of the points; Based on the configuration of the quality of service information of the point, the point is scheduled using the thread under the specific process; If the specific process is a downlink monitoring process, the downlink monitoring process is used to monitor the device; The scheduling process for the point based on the configuration of the quality of service information of the point and using the thread under the specific process includes: Determine a method for adding the point to the message queue based on whether the point is configured with the service quality information, wherein the adding method includes: stack addition or insertion addition; Based on the adding method of the point, the point is added to the message queue through the scheduling thread under the downlink monitoring process; Using the scheduling thread, based on the order of the points in the message queue, the points are pushed to the monitoring service thread under the downlink monitoring process, so that each time the monitoring service thread receives a push, it triggers the acquisition of corresponding point information; The determining a method of adding the point to the message queue by utilizing whether the point is configured with the service quality information includes: If the point is not configured with the service quality information, determining that the point is added to the message queue in a stack addition mode; If the point is configured with the service quality information, it is determined that the adding mode of the point in the message queue is insertion addition.

2. The method according to claim 1, characterized in that The adding method based on the point, adding the point to the message queue through the scheduling thread under the downlink monitoring process, includes: If the point is added by insertion, the scheduling thread uses the service quality information of the point to determine the insertion position of the point in the message queue, and adds the point to the message queue based on the determined insertion position.

3. The method according to claim 2, characterized in that The method further comprises: If the point exists and is added to the message queue by insertion, determine whether all the points in the message queue can be pushed out within the preset push cycle. If not, determine the points in the message queue that cannot be pushed out, and adjust the positions of the points that cannot be pushed out in the message queue forward.

4. The method according to any one of claims 1 to 3, characterized in that The adding method based on the point, adding the point to the message queue through the scheduling thread under the downlink monitoring process, includes: If the point is added in a stack manner, the point is added to the message queue in a stack manner through the scheduling thread.

5. The method according to claim 1, wherein If the specific process is an uplink service process, the uplink service process is used to interact with a host computer; The scheduling process for the point based on the configuration of the quality of service information of the point and using the thread under the specific process includes: The target thread under the uplink service process used by the point is determined by using whether the point is configured with the service quality information, and the point is scheduled through the determined target thread.

6. The method according to claim 5, characterized in that The determining a target thread under the uplink service process used by the point by utilizing whether the point is configured with the service quality information, and performing scheduling processing on the point by using the determined target thread, includes: If the point is not configured with the service quality information, determining that the target thread used by the point is a request thread, and periodically obtaining the point information of the point from a database storing point information through the request thread; If the point is configured with the service quality information, it is determined that the target thread used by the point is a control service thread, and the point is scheduled using the control service thread through the scheduling thread under the downlink monitoring process.

7. A point scheduling processing device, characterized in that: The device comprises: a determination module, configured to determine, for a specific process, a configuration status of service quality information at a point under the specific process, wherein one monitoring object of one device corresponds to one of the points; if the specific process is a downlink monitoring process, the downlink monitoring process is used to monitor the device; A processing module, configured to schedule the point based on the configuration of the quality of service information of the point and using the thread under the specific process; The scheduling process for the point based on the configuration of the quality of service information of the point and using the thread under the specific process includes: Determine a method for adding the point to the message queue based on whether the point is configured with the service quality information, wherein the adding method includes: stack addition or insertion addition; Based on the adding method of the point, the point is added to the message queue through the scheduling thread under the downlink monitoring process; Using the scheduling thread, based on the order of the points in the message queue, the points are pushed to the monitoring service thread under the downlink monitoring process, so that each time the monitoring service thread receives a push, it triggers the acquisition of corresponding point information; The determining a method of adding the point to the message queue by utilizing whether the point is configured with the service quality information includes: If the point is not configured with the service quality information, determining that the point is added to the message queue in a stack addition mode; If the point is configured with the service quality information, it is determined that the adding mode of the point in the message queue is insertion addition.

8. An edge computing controller, characterized in that: include: a memory having an executable program stored therein; A processor, configured to execute the executable program in the memory to implement the steps of the method according to any one of claims 1 to 6.

9. The edge computing controller according to claim 8, characterized in that: The edge computing controller is applied to the emergency management system of a mobile experimental vehicle.

Images