Intelligent control cloud system for pest control

Abstract

The invention belongs to the technical field of intelligent pest killing, and particularly relates to an intelligent control cloud system for pest control. Comprising a gateway service module, a registration service module, a user authentication service module, a management service module, a workflow service module, a cloud file service module, a structure configuration service module, a report service module, an automatic service module and a log service module. According to the intelligent control cloud system for pest control, through integration of a plurality of micro-service modules such as the gateway service module, the registration service module and the user authentication service module, high-degree modular design is realized, the system can be flexibly expanded and updated through the design, each module can be independently developed and deployed, and the system is convenient to use. According to the micro-service system, the complexity and the maintenance cost of the system are reduced, and meanwhile, the micro-services are mutually called through lightweight interfaces, so that the maintainability and the expandability of the system are improved, the system can quickly adapt to continuously changing requirements, and intelligent management and data integration and utilization are realized.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent pest disinfecting, and in particular to an intelligent control cloud system for pest control. Background Art

[0002] In the modern food industry, pest problems have always been a key factor affecting food safety and quality. Traditional pest management methods mainly rely on manual inspections and sampling surveys. This method is not only time-consuming and labor-intensive, but the monitoring results are often lagging, and it is easy to miss the best time for prevention and control. Therefore, there is an urgent need for a system that can efficiently and accurately monitor and control pests, report food safety, reduce production costs, and reduce negative impacts on the environment and society.

[0003] At present, existing products are lacking in business configuration and cannot adapt to a certain degree of customized service processes and service reports. At the same time, they lack intelligent management support and data integration and utilization of intelligent equipment for the overall pest control business. In view of this, the present invention proposes an intelligent control cloud system for pest control. Summary of the invention

[0004] The main purpose of the present invention is to provide an intelligent cloud control system for pest control, which can solve the problems raised in the above background technology.

[0005] To achieve the above objectives, the pest control intelligent control cloud system proposed in the present invention includes:

[0006] The gateway service module, as the entrance of the system, processes external requests and is responsible for forwarding requests to specific internal microservices, such as management services, workflow services, and cloud file services. The gateway service module obtains the location and status of each service through the integrated registration service;

[0007] Registration service module, which is responsible for maintaining the registration information of all microservice modules in the system, managing the discovery and communication of service modules. When all service modules communicate through the gateway service module and the user authentication service module, they will first perform service discovery through the registration service module;

[0008] User authentication service module, which is responsible for verifying the identity of the user and ensuring that the user has the correct permissions when accessing the system. The user authentication service module interacts with other service modules through the gateway service module and allows the user to use the system after ensuring that the user authentication is successful;

[0009] Management service module, which is responsible for the interface docking of the entire system, internal management process and data management process, and is responsible for data interaction and data scheduling with the data layer. The management service module provides service interface requirements for mini-programs and APPs.

[0010] A workflow service module that provides customized service flows, executes predetermined and user-defined service flows, and transmits and stores service data;

[0011] A cloud file service module, which is used to provide file storage and management functions, upload files to the cloud, and support file reading, modification and deletion. Other service modules can access and process files through the cloud file service module;

[0012] A structure configuration service module, which is responsible for the combination configuration of process nodes, the combination configuration of each section of the template and the combination configuration of each part of the notification. The structure configuration service module uses the data of other service modules to fill the configuration template to form a final data message;

[0013] Report service module, which is responsible for generating various reports in the system, service reports, and automatically generating and distributing reports;

[0014] The automation service module is responsible for executing automation tasks in the system, which may include scheduled tasks and batch processing. It interacts with the cloud file service and structure configuration service to complete data processing and task scheduling;

[0015] The log service module is responsible for recording the system's operation log, including all service calls, error messages, and execution status. The log service module provides support for system monitoring and debugging.

[0016] Preferably, the microservice workflow of the system includes request entry gateway, identity authentication, inter-service communication, data processing and cache acceleration, logging and monitoring, and asynchronous task processing.

[0017] Preferably, when a user request enters the gateway, it first passes through the gateway service module, and the gateway service module forwards it to the appropriate microservice according to the request routing. The gateway service module usually collaborates with the user authentication service to verify whether the identity of the requester is legal. The microservices usually communicate using REST API and gRPC. The microservices can independently handle different business functions, and they call each other through lightweight interfaces. The microservices read and write business data from the database to support the implementation of business logic. Some frequently accessed data or temporary calculation results can be stored in Redis to reduce frequent access to the database and improve the system response speed. Each of the microservices will generate logs, which will be collected in ELK for analysis, query and visualization. In addition, the performance and distributed tracking of the system can be monitored through tools such as SkyWalking to ensure the observability and troubleshooting capabilities of each service module. For tasks that need to be executed asynchronously, message queues are usually used to decouple services so that the sender can assign tasks to message queues, and the processor can consume these tasks asynchronously to improve the overall throughput of the system.

[0018] Preferably, the Redis is a high-performance in-memory database, which is often used to cache data, speed up read operations, and reduce direct queries to the database. Some data in the microservice that is frequently queried but infrequently changed can be stored in Redis to avoid reading from the database every time.

[0019] Preferably, the message queue is used to implement asynchronous communication between services. When a microservice needs to process a complex and time-consuming task, the task can be published to the message queue, and other services consume these tasks from the queue and process them.

[0020] Preferably, the database is divided into a master database and a slave database, the master database is responsible for write operations, and the slave database is responsible for read operations. Multiple slave databases can balance the read load and improve system performance.

[0021] Preferably, the ELK is a common solution for log management and analysis. When an abnormality occurs in the system, ELK can monitor the error information in the log in real time.

[0022] Preferably, SkyWalking will collect key performance indicators such as call information, response time, error rate, etc. of each service to help operation and maintenance personnel understand the health status of the system in real time.

[0023] Preferably, the gateway service module communicates with each microservice through API calls, usually using HTTP / HTTPS protocol. The microservice can connect to Redis through a Redis client to cache data or implement distributed locks. The microservice can communicate with the message queue through a message middleware client to send and consume messages.

[0024] Preferably, the microservices perform write operations with the main database and read operations with the slave database through the database connection pool. The microservices are integrated with SkyWalking's Agent, which sends the performance data and tracking information of the service to the SkyWalking server, which stores and analyzes the data.

[0025] The present invention provides an intelligent control cloud system for pest control, which has the following beneficial effects:

[0026] (1) The intelligent pest control cloud system achieves a highly modular design by integrating multiple microservice modules such as the gateway service module, registration service module, and user authentication service module. This design enables the system to be flexibly expanded and updated, and each module can be independently developed and deployed, reducing the complexity and maintenance cost of the system. At the same time, microservices call each other through lightweight interfaces, which improves the maintainability and scalability of the system, allowing the system to quickly adapt to changing needs and realize intelligent management and data integration and utilization.

[0027] (2) The intelligent pest control cloud system achieves comprehensive monitoring and log management through the log service module and performance monitoring tool. The log service module records the system's operation log, including all service calls, error information and execution status, providing strong support for system monitoring and debugging. The SkyWalking performance monitoring tool can collect key performance indicators such as call information, response time, error rate, etc. of each service, helping operation and maintenance personnel to understand the health status of the system in real time, discover and solve problems in a timely manner, thereby ensuring the stability and reliability of the system.

[0028] (3) The intelligent pest control cloud system introduces efficient data processing mechanisms such as Redis memory database and message queue. Redis is used to cache frequently accessed data, reducing the access pressure of the database and improving the response speed of the system. The message queue realizes asynchronous communication between services, allowing complex and time-consuming tasks to be executed asynchronously, improving the overall throughput and processing power of the system. In addition, through the master-slave separation and read-write separation of the database, the read-write load of the system is further balanced, improving the system performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] 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 the structures shown in these drawings without paying creative work.

[0030] Figure 1 is a flow chart of the computer program of the present invention;

[0031] Figure 2 It is a block diagram of each module in the system of the present invention;

[0032] Figure 3 FIG. 4 is a hardware schematic diagram of a computer device of the present invention.

[0033] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0034] 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.

[0035] See also Figure 1-Figure 3 The present invention proposes an intelligent control cloud system for pest control, including a gateway service module, a registration service module, a user authentication service module, a management service module, a workflow service module, a cloud file service module, a structure configuration service module, a report service module, an automation service module and a log service module.

[0036] In an embodiment of the present invention, the gateway service module serves as the entrance to the system, processes external requests, and is responsible for forwarding requests to specific internal microservices, such as management services, workflow services, and cloud file services. The gateway service module obtains the location and status of each service by integrating the registration service; the registration service module is responsible for maintaining the registration information of all microservice modules in the system, and the discovery and communication of the management service modules. When all service modules communicate through the gateway service module and the user authentication service module, they will first perform service discovery through the registration service module; the user authentication service module is responsible for verifying the identity of the user and ensuring that the user has the correct authority when accessing the system. The user authentication service module interacts with other service modules through the gateway service module, and allows the user to use it after ensuring that the user authentication is successful; the management service module is responsible for the interface docking interface of the entire system, as well as the internal management process and data management process, and is responsible for data interaction and data scheduling with the data layer. The management service module provides the service interface needs of the mini-program and APP end to the outside world; the workflow service module provides customized processes for service processes, executes scheduled and user-defined service processes, and transmits and stores service data; the cloud file service module is used to provide file storage and management functions, upload files to the cloud, and support file reading, modification and deletion. Other service modules can access and process files through the cloud file service module; the structure configuration service module is responsible for the combination configuration of process nodes, the combination configuration of template sections and the combination configuration of notification parts. The structure configuration service module uses the data of other service modules to fill in the configuration template to form the final data message; the report service module is responsible for generating various reports and service reports in the system, and automatically generating and distributing reports; through the integration of multiple microservice modules such as the gateway service module, the registration service module, and the user authentication service module, a highly modular design is achieved. This design enables the system to be flexibly expanded and updated, and each module can be independently developed and deployed, reducing the complexity and maintenance cost of the system. Microservices call each other through lightweight interfaces, which improves the maintainability and scalability of the system, allowing the system to quickly adapt to changing needs and realize intelligent management and data integration and utilization.

[0037] Furthermore, the first step of the microservice architecture is to decompose the traditional monolithic application into multiple independent services. Each service is divided around the business domain and has clear responsibility boundaries. They can be developed, deployed and expanded independently, reducing mutual dependence. Each microservice communicates through a lightweight API, usually using protocols such as RESTful and gRPC. The communication between services can be synchronous (such as HTTP requests) or asynchronous (such as message queues). The focus of API design is to define clear interface contracts so that services can interoperate. Among them, microservices need to know each other's existence and location. The service registry (Nacos) is used to record the address and status of the service. Microservices will register their information with the registry when they start. Other services discover available service instances through the registry. In addition, each microservice may have multiple instances. Load balancers (such as NGINX+Spring Cloud LoadBalancer) are used to distribute traffic to healthy service instances to ensure that traffic is evenly distributed and avoid overload.

[0038] Furthermore, in order to ensure the stability and reliability of the system, specifically, the automation service module is responsible for executing automation tasks in the system, which may include scheduled tasks and batch processing. It interacts with cloud file services and structure configuration services to complete data processing and task scheduling; it is responsible for recording the system's operation log, including all service calls, error information and execution status. The log service module provides support for system monitoring and debugging. ELK is a common solution for log management and analysis. When the system is abnormal, ELK can monitor the error information in the log in real time. SkyWalking will collect key performance indicators such as call information, response time, error rate, etc. of each service to help operation and maintenance personnel understand the health status of the system in real time. The gateway service module communicates with each microservice through API calls, usually using HTTP / HTTPS protocol. The microservice can connect to Redis through the Redis client , used to cache data or implement distributed locks. The microservices can communicate with the message queue through the message middleware client to send and consume messages. The microservices write to the main database through the database connection pool and read from the slave database. The microservices are integrated with SkyWalking's Agent. The Agent will send the service's performance data and tracking information to the SkyWalking server, which will store and analyze the data. The log service module records the system's operation log, including all service calls, error messages, and execution status, providing strong support for system monitoring and debugging. The SkyWalking performance monitoring tool can collect key performance indicators such as call information, response time, and error rate of each service, helping operation and maintenance personnel to understand the system's health status in real time, discover and solve problems in a timely manner, thereby ensuring the stability and reliability of the system.

[0039] Furthermore, each microservice often has its own independent database to maintain data isolation and avoid coupling between different services. Common data modes include "database partitioning" and "event-driven architecture". In some cases, services may use event buses or message queues (such as Kafka, RabbitMQ) for asynchronous data synchronization. These steps together constitute the workflow of the microservice architecture, from development to operation and maintenance, through tool chains and governance means to achieve high availability, scalability and stability of the system.

[0040] Furthermore, in order to improve the system performance, specifically, Redis is a high-performance in-memory database, which is often used to cache data, accelerate read operations, and reduce direct queries to the database. Some data in the microservice that are frequently queried but do not change frequently can be stored in Redis to avoid reading from the database every time. The message queue is used to realize asynchronous communication between services. When a microservice needs to process complex and time-consuming tasks, it can publish the tasks to the message queue, and other services consume these tasks from the queue and process them. The database is divided into a master database and a slave database. The master database is responsible for write operations, and the slave database is responsible for read operations. Multiple slave databases can balance the read load and improve system performance. By caching frequently accessed data through Redis, the access pressure of the database is reduced and the response speed of the system is improved. The message queue realizes asynchronous communication between services, so that complex and time-consuming tasks can be executed asynchronously, which improves the overall throughput and processing power of the system. Moreover, through the master-slave separation and read-write separation of the database, the read-write load of the system is further balanced and the system performance is improved.

[0041] The above description is only a preferred embodiment of the present invention, and does not limit the patent scope of the present invention. All equivalent structural changes made by using the contents of the present invention specification and drawings under the inventive concept of the present invention, or directly / indirectly applied in other related technical fields are included in the patent protection scope of the present invention.

Claims

1. An intelligent control cloud system for pest control, characterized in that: include: The gateway service module, as the entrance of the system, processes external requests and is responsible for forwarding requests to specific internal microservices, such as management services, workflow services, and cloud file services. The gateway service module obtains the location and status of each service through the integrated registration service; Registration service module, which is responsible for maintaining the registration information of all microservice modules in the system, managing the discovery and communication of service modules. When all service modules communicate through the gateway service module and the user authentication service module, they will first perform service discovery through the registration service module; User authentication service module, which is responsible for verifying the identity of the user and ensuring that the user has the correct permissions when accessing the system. The user authentication service module interacts with other service modules through the gateway service module and allows the user to use the system after ensuring that the user authentication is successful; Management service module, which is responsible for the interface docking of the entire system, internal management process and data management process, and is responsible for data interaction and data scheduling with the data layer. The management service module provides service interface requirements for mini-programs and APPs. A workflow service module that provides customized service flows, executes predetermined and user-defined service flows, and transmits and stores service data; A cloud file service module, which is used to provide file storage and management functions, upload files to the cloud, and support file reading, modification and deletion. Other service modules can access and process files through the cloud file service module; A structure configuration service module, which is responsible for the combination configuration of process nodes, the combination configuration of each section of the template and the combination configuration of each part of the notification. The structure configuration service module uses the data of other service modules to fill the configuration template to form a final data message; Report service module, which is responsible for generating various reports in the system, service reports, and automatically generating and distributing reports; The automation service module is responsible for executing automation tasks in the system, which may include scheduled tasks and batch processing. It interacts with the cloud file service and structure configuration service to complete data processing and task scheduling; The log service module is responsible for recording the system's operation log, including all service calls, error messages, and execution status. The log service module provides support for system monitoring and debugging.

2. The intelligent cloud control system for pest control according to claim 1, characterized in that: The system's microservice workflow includes request entry gateway, authentication, inter-service communication, data processing and cache acceleration, logging and monitoring, and asynchronous task processing.

3. The intelligent cloud control system for pest control according to claim 2, characterized in that: When a user request enters the gateway, it first passes through the gateway service module. The gateway service module forwards it to the appropriate microservice according to the request routing. The gateway service module usually collaborates with the user authentication service to verify whether the requester's identity is legal. The microservices usually communicate using REST API and gRPC. The microservices can independently handle different business functions. They call each other through lightweight interfaces. The microservices read and write business data from the database to support the implementation of business logic. Some frequently accessed data or temporary calculation results can be stored in Redis to reduce frequent access to the database and improve the system response speed. Each of the microservices will generate logs, which will be collected in ELK for analysis, query and visualization. In addition, the performance and distributed tracking of the system can be monitored through tools such as SkyWalking to ensure the observability and troubleshooting capabilities of each service module. For tasks that need to be executed asynchronously, message queues are usually used to decouple services so that the sender can hand over tasks to the message queue, and the processor can consume these tasks asynchronously to improve the overall throughput of the system.

4. The intelligent cloud control system for pest control according to claim 3, characterized in that: The Redis is a high-performance in-memory database, which is often used to cache data, speed up read operations, and reduce direct queries to the database. Some data in the microservice that is frequently queried but infrequently changed can be stored in Redis to avoid reading from the database every time.

5. The intelligent cloud control system for pest control according to claim 3, characterized in that: The message queue is used to implement asynchronous communication between services. When a microservice needs to process complex and time-consuming tasks, it can publish the tasks to the message queue, and other services consume these tasks from the queue and process them.

6. The intelligent cloud control system for pest control according to claim 3, characterized in that: The database is divided into a master database and a slave database. The master database is responsible for write operations, and the slave database is responsible for read operations. Multiple slave databases can balance the read load and improve system performance.

7. The intelligent cloud control system for pest control according to claim 3, characterized in that: The ELK is a common solution for log management and analysis. When an abnormality occurs in the system, ELK can monitor the error information in the log in real time.

8. The intelligent cloud control system for pest control according to claim 3, characterized in that: The SkyWalking will collect key performance indicators such as call information, response time, error rate, etc. of each service to help operation and maintenance personnel understand the health status of the system in real time.

9. The intelligent cloud control system for pest control according to claim 3, characterized in that: The gateway service module communicates with each microservice through API calls, usually using HTTP / HTTPS protocol. The microservice can connect to Redis through the Redis client to cache data or implement distributed locks. The microservice can communicate with the message queue through the message middleware client to send and consume messages.

10. The intelligent cloud control system for pest control according to claim 3, characterized in that: The microservices write to the master database and read from the slave database through the database connection pool. The microservices are integrated with SkyWalking's Agent, which sends the performance data and tracking information of the service to the SkyWalking server, which stores and analyzes the data.

Images