A service scheduling method, device and equipment

Abstract

The present invention provides a service scheduling method, device and equipment, in which each sub-service in a high-availability service unit periodically registers with a message middleware, and a scheduling service subscribes to the registration information of each sub-service from the message middleware, and a preset scheduling method is used to determine a sub-service for completing the task based on the registration information, and a corresponding scheduling result is generated, and the scheduling result is sent to the sub-service through the message middleware unit. After obtaining the scheduling result, the sub-service determines whether to execute the business logic based on the scheduling result. This solution arranges multiple sub-services on the high-availability service unit end, making the high-availability deployment of edge computing industrial process data management and control services flexible, efficient and easy to expand, thereby reducing the number of high-availability service units on the edge side and increasing the utilization rate of high-availability service units on the edge side.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a service scheduling method, device and equipment based on edge computing industrial process data management and control services. Background Art

[0002] In the era of cloud computing, with the increase of applications, centralized clouds can no longer meet the resource requirements of "large connections, low latency, and large bandwidth" on the terminal side. Cloud computing will inevitably develop to the next technical stage: expanding the capabilities of cloud computing to the edge side, which is closer to the edge, and building an edge computing industrial process data management and control service platform on the edge side. At present, in order to reduce the development cost of users, the edge side uses a unified architecture and unified interface with the central cloud to the maximum extent. When building a cloud computing platform, the high availability solution of the Internet is adopted. This high availability solution is suitable for large-scale service high availability scenarios. High availability deployment and high availability management are relatively complex. Building a high availability platform requires 2n+1 machines. If more than half of the abnormal services in the high availability service list are unavailable, the entire high availability environment will be unavailable, which reduces the utilization rate of normal services. Each service high availability deployment requires 2n+1 machines, which will occupy too many resources. Summary of the invention

[0003] In view of this, an embodiment of the present invention provides a service scheduling method, apparatus and device to improve the utilization efficiency of edge devices.

[0004] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0005] A service scheduling device, comprising:

[0006] A high-availability service unit, wherein N sub-services are configured in the high-availability service unit, where N is a positive integer, and when the sub-service obtains the scheduling result, it determines whether to execute the business logic based on the scheduling result;

[0007] A message middleware unit, wherein the message middleware unit is pre-set with a first subscription topic and a second subscription topic adapted to the high-availability service unit, the first subscription topic is used to obtain registration information of each sub-service in the high-availability service based on a preset period, and the second subscription topic is used to obtain a scheduling result and send the scheduling result to the sub-service in the high-availability service corresponding to the second subscription topic;

[0008] A service scheduling unit, wherein the scheduling unit obtains registration information of each sub-service, generates a scheduling result based on a preset scheduling algorithm and the registration information of each sub-service, and sends the scheduling result to the second subscription topic, wherein the scheduling result at least includes a selected master node.

[0009] Optionally, in the above service scheduling device, the number of the high-availability service units is M, and M is a positive integer not less than 1.

[0010] Optionally, in the above service scheduling device, the message middleware unit is configured with M groups of first subscription topics and second subscription topics, and each group of first subscription topics and second subscription topics corresponds one-to-one to the high-availability service unit.

[0011] Optionally, in the above service scheduling device, the number of sub-services in each high-availability service unit is the same or different.

[0012] Optionally, in the above service scheduling device, the N sub-services in the high-availability service unit are respectively one main sub-service and N-1 backup sub-services, wherein the number of the backup sub-services is at least one.

[0013] Optionally, in the above service scheduling device, when the subservice determines whether to execute the service logic based on the scheduling result, it is specifically used to:

[0014] Extract the main node in the scheduling result, determine whether the main node is consistent with the node of the sub-service itself, and if they are consistent, use the sub-service as the main sub-service and execute the business logic corresponding to the high-availability service unit.

[0015] Optionally, in the above-mentioned service scheduling device, the service scheduling unit is also used to obtain a sub-service stop and start instruction, and stop and start the sub-service in the high-availability service unit based on the sub-service stop and start instruction. When the stopped sub-service is the main sub-service, a backup sub-service is selected from the N-1 backup sub-services in the turned-on state as the main sub-service.

[0016] Optionally, in the above-mentioned service scheduling device, when the service scheduling unit generates a scheduling result based on a preset scheduling algorithm and the registration information of each sub-service, it preferentially determines whether to adopt the main sub-service to execute the business logic. If the main sub-service is unavailable, it determines whether the backup sub-service executes the business logic, and generates a scheduling result based on the determination result.

[0017] A service scheduling method, comprising:

[0018] Acquire registration information of each sub-service in the high-availability service based on a preset period through the first subscription topic;

[0019] Sending the acquired registration information to a service scheduling module through the first subscription topic;

[0020] Obtaining a scheduling result of the service scheduling module through a second subscription topic adapted to the first subscription topic, the scheduling result at least including a master node selected by the service scheduling module based on a preset scheduling algorithm and registration information of each sub-service;

[0021] The obtained scheduling result is sent to a sub-service in the high-availability service corresponding to the second subscription topic through the second subscription topic, and the sub-service is used to determine whether to execute the business logic based on the scheduling result.

[0022] A service scheduling device, comprising a memory and a processor;

[0023] The memory is used to store programs;

[0024] The processor is used to execute the program to implement:

[0025] Acquire registration information of each sub-service in the high-availability service based on a preset period through the first subscription topic;

[0026] Sending the acquired registration information to a service scheduling module through the first subscription topic;

[0027] Obtaining a scheduling result of the service scheduling module through a second subscription topic adapted to the first subscription topic, the scheduling result at least including a master node selected by the service scheduling module based on a preset scheduling algorithm and registration information of each sub-service;

[0028] The obtained scheduling result is sent to a sub-service in the high-availability service corresponding to the second subscription topic through the second subscription topic, and the sub-service is used to determine whether to execute the business logic based on the scheduling result.

[0029] Based on the above technical solution, in the above solution provided by the embodiment of the present invention, each sub-service in the high-availability service unit periodically registers with the message middleware, the scheduling service subscribes to the registration information of each sub-service from the message middleware, and uses a preset scheduling method to determine a sub-service for completing this task based on the registration information, and generates a corresponding scheduling result, and sends the scheduling result to the sub-service through the message middleware unit. After obtaining the scheduling result, the sub-service determines whether to execute the business logic based on the scheduling result. This solution arranges multiple sub-services on the high-availability service unit end, making the high-availability deployment of edge computing industrial process data management and control services flexible, efficient, and easy to expand, thereby reducing the number of high-availability service units on the edge side and increasing the utilization rate of high-availability service units on the edge side. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] 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 embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0031] Figure 1 A schematic diagram of the structure of a service scheduling device disclosed in an embodiment of the present application;

[0032] Figure 2 A schematic diagram of the structure of a service scheduling device disclosed in another embodiment of the present application;

[0033] Figure 3 A flow chart of the service scheduling method disclosed in the embodiment of the present application;

[0034] Figure 4 This is a schematic diagram of the structure of the service scheduling device disclosed in the embodiment of the present application. DETAILED DESCRIPTION

[0035] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0036] According to the present invention, a service scheduling method, device and equipment based on edge computing industrial process data management and control service are provided. The scheme includes: the edge service (which can be considered as a sub-service in the high-availability service in this application) regularly registers the service status to the message middleware, and the registration content includes service name information, service type information, node name information, and current service status information. The scheduling service subscribes to the registration information from the message middleware, and then groups the registered information according to the service name information and service status information, selects a sub-service from a healthy (here, the so-called health refers to available) service list, and pushes the registration content of the sub-service to the message middleware. The sub-service corresponding to the service name subscribes to the message from the message middleware, parses the message content to determine whether the node where the sub-service is located is equal to the node in the message, if equal, the sub-service at the node is the main sub-service, if not equal, it is a backup sub-service, and the backup sub-service does not process business during operation. This setting method makes the high-availability deployment of the edge computing industrial process data management and control service flexible, efficient, and easy to expand, thereby reducing the number of services on the edge side and increasing the utilization rate of edge side services.

[0037] For details, see Figure 1 The service scheduling device disclosed in the embodiment of the present application may include:

[0038] High availability service unit A, message middleware unit B and service scheduling unit C;

[0039] A high-availability service unit A, which is used to provide the high-availability service mentioned in the background technology. The high-availability service unit is configured with N sub-services, where N is a positive integer. When the sub-service obtains the scheduling result, it determines whether to execute the business logic based on the scheduling result;

[0040] A message middleware unit B, in which a first subscription topic and a second subscription topic adapted to the high-availability service unit are pre-set, each group of the first subscription topic and the second subscription topic matches a high-availability service unit A, the first subscription topic is used to obtain registration information of each sub-service in the high-availability service based on a preset period, and upload the registration information to a service scheduling unit, the second subscription topic is used to obtain a scheduling result obtained by analysis of the service scheduling unit, and send the scheduling result to each sub-service in the high-availability service corresponding to the second subscription topic, so that the sub-service determines whether to execute the business logic;

[0041] Service scheduling unit C, service scheduling unit C is used to execute scheduling services, specifically, to select scheduling targets based on the acquired registration information and built-in logical judgment logic. Specifically, after acquiring the registration information of each sub-service, the scheduling unit generates a scheduling result based on a preset scheduling algorithm and the registration information of each sub-service, and sends the scheduling result to the second subscription topic, so as to send the scheduling result to each sub-service in the high-availability service unit A through the second subscription topic, wherein the scheduling result includes at least a selected master node, which is a node of the sub-service used to execute business logic.

[0042] In the above-mentioned scheme provided by the present invention, each sub-service in the high-availability service unit A periodically registers with the message middleware, and the scheduling service subscribes to the registration information of each sub-service from the message middleware, and uses a preset scheduling method to determine a sub-service for completing this task based on the registration information, and generates a corresponding scheduling result, and sends the scheduling result to the sub-service through the message middleware unit. After obtaining the scheduling result, the sub-service determines whether to execute the business logic based on the scheduling result. This scheme arranges multiple sub-services at the end of the high-availability service unit A, making the high-availability deployment of the edge computing industrial process data management and control service flexible, efficient, and easy to expand, thereby reducing the number of high-availability service units on the edge side and increasing the utilization rate of high-availability service units on the edge side.

[0043] See also Figure 2 In the technical solution disclosed in this embodiment, each service scheduling device can be configured with M high-availability service units at the same time, where M is a positive integer not less than 1. The number of sub-services in each high-availability service unit can be set according to demand, and the number of sub-services in each high-availability service unit can be the same or different. For example, see Figure 2 In the service scheduling device, there are three high-availability service units, wherein the number of sub-services in one high-availability service unit can be one, the number of sub-services in one high-availability service unit can be two, and the number of sub-services in one high-availability service unit can be three. When there are two or more sub-services in the high-availability service unit, one of the sub-services is used as the main sub-service, and the other sub-services are used as backup sub-services. When scheduling, the sub-service is scheduled first. When the sub-service is unavailable, a sub-service is selected from the remaining backup sub-services to replace the main sub-service for use.

[0044] When M high-availability service units are configured in the service scheduling device, M groups of first subscription topics and second subscription topics need to be configured in the message middleware unit. One first subscription topic and one second subscription topic form a group, and each group of first subscription topics and second subscription topics correspond one-to-one to the high-availability service unit, that is, each group of first subscription topics and second subscription topics corresponds to one high-availability service unit, and each high-availability service unit corresponds to a group of first subscription topics and second subscription topics. The first subscription topic in each group is used to obtain the registration information of each sub-service in the high-availability service unit corresponding to the group, and upload it to the service scheduling unit. The second subscription topic in each group is used to obtain the scheduling result of the service scheduling unit based on the registration information of the first subscription topic, and send the scheduling result to each sub-service in the corresponding high-availability service unit.

[0045] In the technical solution disclosed in the embodiment of the present application, during the design process, the number of sub-services in each high-availability service unit can be set according to the design requirements. When the number of sub-services in the high-availability service unit is greater than 1, one of the sub-services can be used as the main sub-service, and the remaining N-1 sub-services are used as backup sub-services, wherein the number of the backup sub-services is at least one, and the main sub-service has the highest priority. When performing scheduling, the service scheduling unit first determines whether it can be called based on the registration content of the main sub-service. If it can be called, the main sub-service is used as the target sub-service to generate a scheduling result. If the main sub-service is not available, it determines whether the backup sub-service can be called and generates a corresponding scheduling result. That is, when the service scheduling unit generates a scheduling result based on the preset scheduling algorithm and the registration information of each sub-service, it gives priority to determining whether to use the main sub-service to execute the business logic. If the main sub-service is not available, it determines whether the backup sub-service executes the business logic and generates a scheduling result based on the judgment result.

[0046] In the technical solution disclosed in another embodiment of the present application, the scheduling result at least includes the node of the target sub-service determined in the service scheduling process, and the node is recorded as the main node. When the sub-service determines whether to execute the business logic based on the scheduling result, it is specifically used to: extract the main node from the scheduling result obtained through the second subscription topic, and determine whether the main node is consistent with the node of the sub-service itself. If the two are consistent, the sub-service is used as the main sub-service, and the business logic corresponding to the high-availability service unit is executed through the sub-service. If the main node is inconsistent with the node of the sub-service itself, the sub-service is used as a backup sub-service, and its corresponding node is recorded as a backup node. The sub-service does not execute business logic, but is only responsible for monitoring the results of the business execution logic.

[0047] In the technical solution disclosed in this embodiment, when it is necessary to reduce the number of sub-services, it is only necessary to directly stop the sub-service interface corresponding to a certain node. If the sub-service to be stopped is a sub-service that has been selected as the main service, the scheduling service unit will select a healthy sub-service as the new main sub-service from the remaining backup sub-services according to the preset scheduling algorithm. The whole process is non-interfering to the execution of business logic. That is, in the above-mentioned solution, the high-availability service unit is also used to obtain the sub-service stop and start instruction, and stop and start the sub-services in the high-availability service unit based on the sub-service stop and start instruction. When the stopped sub-service is the main sub-service, a backup sub-service is selected from the N-1 backup sub-services in the open state as the main sub-service. In the subsequent scheduling process, the main sub-service is preferentially used as the target scheduling object.

[0048] This embodiment discloses a service scheduling method. For the specific work content of each step in the method, please refer to the content of the above method embodiment.

[0049] The following describes a service scheduling method provided by an embodiment of the present invention. The service scheduling method described below and the service scheduling device described above can be referenced to each other.

[0050] This method can be applied to the message middleware unit, see Figure 3 , the method may include:

[0051] Step S101: obtaining registration information of each sub-service in the high-availability service based on a preset period through the first subscription topic;

[0052] Step S102: sending the acquired registration information to a service scheduling module through the first subscription topic;

[0053] Step S103: obtaining a scheduling result of the service scheduling module through a second subscription topic adapted to the first subscription topic, wherein the scheduling result at least includes a master node selected by the service scheduling module based on a preset scheduling algorithm and registration information of each sub-service;

[0054] Step S104: sending the acquired scheduling result to a sub-service in the high-availability service corresponding to the second subscription topic through the second subscription topic, and the sub-service is used to determine whether to execute the business logic based on the scheduling result.

[0055] Figure 4 For a hardware structure diagram of the service scheduling device provided in an embodiment of the present invention, see Figure 4 As shown, it may include: at least one processor 100, at least one communication interface 200, at least one memory 300 and at least one communication bus 400;

[0056] In the embodiment of the present invention, the number of the processor 100, the communication interface 200, the memory 300, and the communication bus 400 is at least one, and the processor 100, the communication interface 200, and the memory 300 communicate with each other through the communication bus 400; obviously, Figure 4 The communication connections shown for the processor 100, the communication interface 200, the memory 300, and the communication bus 400 are merely optional;

[0057] Optionally, the communication interface 200 may be an interface of a communication module, such as an interface of a GSM module;

[0058] The processor 100 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.

[0059] The memory 300 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0060] The processor 100 is specifically configured to:

[0061] Acquire registration information of each sub-service in the high-availability service based on a preset period through the first subscription topic;

[0062] Sending the acquired registration information to a service scheduling module through the first subscription topic;

[0063] Obtaining a scheduling result of the service scheduling module through a second subscription topic adapted to the first subscription topic, the scheduling result at least including a master node selected by the service scheduling module based on a preset scheduling algorithm and registration information of each sub-service;

[0064] The obtained scheduling result is sent to a sub-service in the high-availability service corresponding to the second subscription topic through the second subscription topic, and the sub-service is used to determine whether to execute the business logic based on the scheduling result.

[0065] For the convenience of description, the above system is described as being divided into various modules according to their functions. Of course, when implementing the present invention, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0066] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.

[0067] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0068] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0069] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0070] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A service scheduling device, characterized in that: include: A high-availability service unit, wherein N sub-services are configured in the high-availability service unit, wherein N is a positive integer. When the sub-service obtains a scheduling result, the sub-service determines whether to execute the business logic based on the scheduling result, including extracting the main node in the scheduling result, and determining whether the main node is consistent with the node of the sub-service itself. If they are consistent, the sub-service is used as the main sub-service, and the business logic corresponding to the high-availability service unit is executed; A message middleware unit, wherein the message middleware unit is pre-set with a first subscription topic and a second subscription topic adapted to the high-availability service unit, the first subscription topic is used to obtain registration information of each sub-service in the high-availability service unit based on a preset period, and the second subscription topic is used to obtain a scheduling result, and send the scheduling result to the sub-service in the high-availability service unit corresponding to the second subscription topic; the registration information of the sub-service includes current service status information, and the current service status can represent the health status of the sub-service; A service scheduling unit, wherein the scheduling unit obtains registration information of each sub-service, generates a scheduling result based on a preset scheduling algorithm and the registration information of each sub-service, and sends the scheduling result to the second subscription topic, wherein the scheduling result at least includes a selected master node.

2. The service scheduling device according to claim 1, characterized in that: The number of the high-availability service units is M, and M is a positive integer not less than 1.

3. The service scheduling device according to claim 2, characterized in that: The message middleware unit is configured with M groups of first subscription topics and second subscription topics, and each group of first subscription topics and second subscription topics corresponds one-to-one to the high-availability service unit.

4. The service scheduling device according to claim 2, characterized in that: The number of sub-services in each high-availability service unit is the same or different.

5. The service scheduling device according to claim 2, characterized in that: The N sub-services in the high-availability service unit are respectively one main sub-service and N-1 backup sub-services, wherein the number of the backup sub-services is at least one.

6. The service scheduling device according to claim 5, characterized in that: The service scheduling unit is further used for: Obtain a subservice stop and start instruction, and stop and start a subservice in the high-availability service unit based on the subservice stop and start instruction. When the stopped subservice is a primary subservice, select a backup subservice from the N-1 backup subservices in the enabled state as the primary subservice.

7. The service scheduling device according to claim 5, characterized in that: When the service scheduling unit generates a scheduling result based on the preset scheduling algorithm and the registration information of each sub-service, it is specifically used to: It is first determined whether to use the main sub-service to execute the business logic. If the main sub-service is unavailable, it is determined whether the backup sub-service executes the business logic, and a scheduling result is generated based on the determination result.

8. A service scheduling method, characterized in that: include: Obtaining registration information of each sub-service in the high-availability service unit based on a preset period through the first subscription topic; Sending the acquired registration information to a service scheduling module through the first subscription topic; Obtaining a scheduling result of the service scheduling module through a second subscription topic adapted to the first subscription topic, the scheduling result at least including a master node selected by the service scheduling module based on a preset scheduling algorithm and registration information of each sub-service; The registration information of the sub-service includes current service status information, and the current service status can represent the health status of the sub-service; The obtained scheduling result is sent to the sub-service in the high-availability service unit corresponding to the second subscription topic through the second subscription topic. The sub-service is used to determine whether to execute the business logic based on the scheduling result, including extracting the main node in the scheduling result, and determining whether the main node is consistent with the node of the sub-service itself. If they are consistent, the sub-service is used as the main sub-service and the business logic corresponding to the high-availability service unit is executed.

9. A service scheduling device, comprising a memory and a processor; The memory is used to store programs; The processor is used to execute the program to implement: Obtaining registration information of each sub-service in the high-availability service unit based on a preset period through the first subscription topic; Sending the acquired registration information to a service scheduling module through the first subscription topic; Obtaining a scheduling result of the service scheduling module through a second subscription topic adapted to the first subscription topic, the scheduling result at least including a master node selected by the service scheduling module based on a preset scheduling algorithm and registration information of each sub-service; The registration information of the sub-service includes current service status information, and the current service status can represent the health status of the sub-service; The obtained scheduling result is sent to the sub-service in the high-availability service unit corresponding to the second subscription topic through the second subscription topic. The sub-service is used to determine whether to execute the business logic based on the scheduling result, including extracting the main node in the scheduling result, and determining whether the main node is consistent with the node of the sub-service itself. If they are consistent, the sub-service is used as the main sub-service and the business logic corresponding to the high-availability service unit is executed.

Images