Unified industrial brain industrial data management system and method
Through a unified industrial brain industrial data management system and methods, the problem of tight coupling between data services and calls and complicated interfaces is solved, efficient and secure data service management and calls are achieved, and the quality and user experience of data services are improved.
Patent Information
- Application Number
- CN202411361551.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2025-01-17
AI Technical Summary
In the field of industrial Internet of Things, data services are tightly coupled with calls, the newly released data service interface process is complicated and complex, and the data service management and access methods are diverse, resulting in low efficiency, poor scalability, and difficult to guarantee security, which makes it difficult to meet the data of enterprises. Service demand.
Provide a unified industrial brain industrial data management system and method, including data service integration module, registration center module, gateway module and management backend module. Through these modules, data services are unified management and call data services, and unified interface and permission management of data services are realized. , uses a visual web interface and front-end portal module to simplify user operations, and uses RSA algorithms and responsibility chain mode to ensure security and load balancing.
It improves the efficiency and quality of data services, reduces operating costs, improves user experience, solves the diversity and security issues of data service management and call methods, and provides a more flexible and reliable data service platform.
Smart Images
Figure CN119322898A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of industrial Internet of Things data management, and specifically relates to a unified industrial brain industrial data management system and method. Background Art
[0002] With the rapid development of the Internet and big data, data resources have become an important support for the development of enterprises and even industries. In the industrial field, there are more and more equipment collection data, industrial map data, industrial analysis data, etc., and their role is getting bigger and bigger. Digital resource, data service, and data asset have become a trend. The traditional data service method is to provide data access and sharing through specific services. However, with the continuous expansion of enterprise business, the rapid growth of data has led to a linear increase in the number of specific data services. Due to the coding style and technology stack of developers, each data service access and calling method will have its own characteristics. For the caller, it is necessary to adapt to various calling methods. For existing services, if several data service interfaces are to be developed, it is necessary to tightly couple its specific business with the caller for access.
[0003] In summary, the current data management in the Industrial Internet of Things has the following problems: data services are tightly coupled with calls, the process of newly released data service interfaces is cumbersome and complicated, and data service management and access methods are diverse, resulting in low data service efficiency, poor scalability, and difficulty in ensuring security, which ultimately makes it difficult to meet the needs of enterprises for data services.
[0004] This is the shortcoming of the existing technology. Therefore, it is very necessary to provide a unified industrial brain industrial data management system and method to address the above-mentioned defects in the existing technology. Summary of the invention
[0005] In view of the defects that the above-mentioned data services and calls in the prior art are tightly coupled, the newly released data service interface process is cumbersome and complicated, and the data service management and access methods are diverse, resulting in low data service efficiency, poor scalability, and difficulty in ensuring security, which ultimately makes it difficult to meet the needs of enterprises for data services. The present invention provides a unified industrial brain industrial data management system and method to solve the above-mentioned technical problems.
[0006] In a first aspect, the present invention provides a unified industrial brain industrial data management system, comprising: The data service integration module is used to generate data services, integrate various industry indicator data, and generate and save data service instances based on industry indicator data; The registration center module is used to register data service instances released by various industries and manage the registered data service instances; The gateway module is used to sense the online and offline data service instances of various industries, update the data service instances, serve as the interface for the client to call the data service instances, and cooperate with the registration center module to complete the call of the data service instances.
[0007] Furthermore, it also includes: The management backend module is used by administrators to manage data service instances of various industries through a visual web interface; The front-end portal module is used to respond to user requests to view the interface directory of data service instances in various industries, create applications, subscribe to the interfaces of corresponding data service instances, and call the interfaces of data service instances in the set manner after subscription.
[0008] Furthermore, the various types of industry indicator data in the data service integration module include data graphs and time series indicator data of various industries; Data services include data analysis services and data processing services; The management backend module manages the online and offline data service instances of each industry through a visual web interface, and allocates permissions to data service instances corresponding to the same data service; When performing routing forwarding, the gateway module performs load balancing according to the permissions allocated to the required data service instance. In a second aspect, the present invention provides a unified industrial brain industrial data management method, comprising the following steps: S1. Generate data services, combining various industry indicator data to generate data service instances; S2. The administrator user manages the data service instance status through the visual web interface; S3. The registration center module registers the data service instances released by various industries and manages the registered data service instances; S4. After the gateway module is started, it requests the registration center module to obtain the data service instance interface, pull the routing information, and generate the gateway routing configuration; S5. The user logs in to the front-end portal through the client to subscribe to the data service instance, and calls the data service instance through the routing configuration of the gateway module.
[0009] Furthermore, the specific steps of step S1 are as follows: S11. Generate data services, including data analysis services and data processing services; S12. Obtain various industry indicator data, wherein the industry indicator data includes data maps and time series indicator data of corresponding industries; S13. Generate data service instances based on various industry indicator data.
[0010] Furthermore, the specific steps of step S2 are as follows: S21. The administrator user publishes the generated data service instance and controls the online and offline of the data service instance; S22. The administrator user identifies the same data service instance and assigns permissions to the same data service instance.
[0011] Furthermore, the specific steps of step S3 are as follows: S31. The registration center module detects whether there is a newly released data service instance; If yes, go to step S32; If not, wait for a set period of time and return to step S31; S32. The registration center module registers the newly released data service instance and saves the address of each data service instance.
[0012] Furthermore, the specific steps of step S4 are as follows: S41. The gateway module starts to generate a heartbeat signal and sends the heartbeat signal to the registration center module; S42. The gateway module receives the currently available data service instance information returned by the registration center module; S43. The gateway module generates a data service directory by identifying the data service instance that needs to be opened through annotations, and obtains the address of the data service instance that needs to be opened as routing data through the registration center module; S44. The gateway module generates and updates the gateway routing configuration through the acquired routing data.
[0013] Furthermore, the specific steps of step S5 are as follows: S51. The user registers and logs in through the client on the front-end portal, and after logging in, views the directory of data services obtained through the gateway module; S52. The user creates an application on the front-end portal through the client and subscribes to the required data service; S53. The user selects a predetermined method from the client according to the created application and pulls the routing configuration of the gateway module, identifies the routing path of the subscribed required data service, and calls the corresponding data service.
[0014] Furthermore, the specific steps of step S53 are as follows: S531. The user generates a signature using the RSA algorithm based on the interface parameters of the subscribed data service instance through the client; S532. The client uses the fiter responsibility chain mode to send a request with a signature to the gateway module; S533. The gateway module performs interface verification and parameter format verification; If there is an abnormality, go to step S534; If there is no abnormality, go to step S535; S534. The gateway module returns an exception to the client and ends; S535. After the gateway module performs current limiting processing, it performs load balancing according to the subscribed data service instance and the pre-set permissions, and then performs routing forwarding of the corresponding data service instance according to the gateway routing configuration; S536. After receiving the request, the data service instance performs business logic processing; If the processing is normal, proceed to step S537; If the processing is abnormal, return to step S534; S537. The data service instance returns the processing result to the gateway module; S538. The gateway module will sign the processing result on the server side and return it to the client.
[0015] The beneficial effects of the present invention are: The unified industrial brain industrial data management method and system provided by the present invention unifies the management of various data services, unifies the data service calling method, and flexibly opens data services to the industrial brain industrial data management platform, avoiding a series of problems in the prior art such as diverse data service management and calling methods, low data service efficiency, poor scalability, and difficulty in ensuring security; it improves the efficiency and quality of data services, reduces operating costs, and enhances user experience, providing strong support for enterprise and social development.
[0016] In addition, the invention has a reliable design principle, a simple structure and a very broad application prospect.
[0017] It can be seen that compared with the prior art, the present invention has outstanding substantive features and significant progress, and the beneficial effects of its implementation are also obvious. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] 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, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0019] Figure 1 It is a schematic diagram of the unified industrial brain industrial data management system of the present invention.
[0020] Figure 2 It is a flow chart of the unified industrial brain industrial data management method of the present invention.
[0021] Figure 3 It is a schematic diagram of the process of registering a data service instance of the present invention.
[0022] Figure 4 It is a flowchart of calling a data service instance of the present invention. DETAILED DESCRIPTION
[0023] 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 should fall within the scope of protection of the present invention.
[0024] See also Figure 1 The following is a unified industrial brain industrial data management system in a specific implementation, including: The data service integration module is used to generate data services, integrate various industry indicator data, and generate and save data service instances based on industry indicator data; The registration center module is used to register data service instances released by various industries and manage the registered data service instances; The gateway module is used to sense the online and offline data service instances of various industries, update the data service instances, serve as the interface for the client to call the data service instances, and cooperate with the registration center module to complete the call of the data service instances.
[0025] In this embodiment, it also includes: The management backend module is used by administrators to manage data service instances of various industries through a visual web interface; The front-end portal module is used to respond to user requests to view the interface directory of data service instances of various industries, create applications, subscribe to the interface of the corresponding data service instance, and call the interface of the data service instance in the set method after subscription; The various industry indicator data in the data service integration module include data maps and time series indicator data of various industries; for example, steel map data, rubber map data, time series indicator data and supply chain order data; Data services include data analysis services and data processing services; The management backend module manages the online and offline data service instances of each industry through a visual web interface, and allocates permissions to data service instances corresponding to the same data service; When performing routing forwarding, the gateway module performs load balancing according to the permissions allocated to the required data service instances.
[0026] The following is an embodiment of the unified industrial brain industrial data management method provided in the embodiments of the present disclosure. This method and the unified industrial brain industrial data management system of the above-mentioned embodiments belong to the same inventive concept. For details not described in detail in the embodiment of the unified industrial brain industrial data management method, please refer to the embodiment of the above-mentioned unified industrial brain industrial data management system.
[0027] like Figure 2 As shown, the method comprises the following steps: S1. Generate data services, combining various industry indicator data to generate data service instances; S2. The administrator user manages the data service instance status through the visual web interface; S3. The registration center module registers the data service instances released by various industries and manages the registered data service instances; S4. After the gateway module is started, it requests the registration center module to obtain the data service instance interface, pull the routing information, and generate the gateway routing configuration; S5. The user logs in to the front-end portal through the client to subscribe to the data service instance and calls the data service instance through the routing configuration of the gateway module; It should be noted that the registration center module in the present invention is implemented using nacos, and the gateway module is implemented using gateway.
[0028] In this embodiment, the specific steps of step S1 are as follows: S11. Generate data services, including data analysis services and data processing services; S12. Obtain various industry indicator data, wherein the industry indicator data includes data maps and time series indicator data of corresponding industries; S13. Generate data service instances based on various industry indicator data; The specific steps of step S2 are as follows: S21. The administrator user publishes the generated data service instance and controls the online and offline of the data service instance; S22. The administrator user identifies the same data service instance and assigns permissions to the same data service instance; like Figure 3 As shown, the specific steps of step S3 are as follows: S31. The registration center module detects whether there is a newly released data service instance; If yes, go to step S32; If not, wait for a set period of time and return to step S31; S32. The registration center module registers the newly released data service instance and saves the address of each data service instance; The specific steps of step S4 are as follows: S41. The gateway module starts to generate a heartbeat signal and sends the heartbeat signal to the registration center module; S42. The gateway module receives the currently available data service instance information returned by the registration center module; S43. The gateway module generates a data service directory by identifying the data service instance that needs to be opened through annotations, and obtains the address of the data service instance that needs to be opened as routing data through the registration center module; S44. The gateway module generates and updates the gateway routing configuration by acquiring the routing data; The specific steps of step S5 are as follows: S51. The user registers and logs in through the client on the front-end portal, and after logging in, views the directory of data services obtained through the gateway module; S52. The user creates an application on the front-end portal through the client and subscribes to the required data service; S53. The user selects a predetermined method by the client according to the application created and pulls the routing configuration of the gateway module, identifies the routing path of the required data service subscribed to and calls the corresponding data service; like Figure 4 As shown, the specific steps of step S53 are as follows: S531. The user generates a signature using the RSA algorithm based on the interface parameters of the subscribed data service instance through the client; S532. The client uses the fiter responsibility chain mode to send a request with a signature to the gateway module; S533. The gateway module performs interface verification and parameter format verification; If there is an abnormality, go to step S534; If there is no abnormality, go to step S535; The interface verification includes blacklist verification, route verification, app application verification, signature verification, permission verification, token verification, and subscription verification; after successful interface verification, the next fiter is entered, and if the verification fails, an error message is returned to the client; The parameter format check can ensure the uniformity of the request. If the check fails, an abnormal error message is returned to the client. If it succeeds, the client enters the current limiting process. S534. The gateway module returns an exception to the client and ends; S535. After the gateway module performs current limiting processing, it performs load balancing according to the subscribed data service instance and the pre-set permissions, and then performs routing forwarding of the corresponding data service instance according to the gateway routing configuration; It should be noted that the current limiting configuration is mainly completed in the background management module; S536. After receiving the request, the data service instance performs business logic processing; If the processing is normal, proceed to step S537; If the processing is abnormal, return to step S534; S537. The data service instance returns the processing result to the gateway module; S538. The gateway module will sign the processing result on the server side and return it to the client.
[0029] It should be understood that the order of execution of the steps in the above embodiment does not mean that the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.
[0030] Although the present invention has been described in detail with reference to the accompanying drawings and in combination with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions shall be within the scope of the present invention. Any person of ordinary skill in the art may easily think of changes or substitutions within the technical scope disclosed by the present invention, and these shall be within the scope of protection of the present invention.
Claims
1. A unified industrial brain industrial data management system, characterized in that: include: The data service integration module is used to generate data services, integrate various industry indicator data, and generate and save data service instances based on industry indicator data; The registration center module is used to register data service instances released by various industries and manage the registered data service instances; The gateway module is used to sense the online and offline data service instances of various industries, update the data service instances, serve as the interface for the client to call the data service instances, and cooperate with the registration center module to complete the call of the data service instances.
2. The unified industrial brain industrial data management system as claimed in claim 1, characterized in that: Also includes: The management backend module is used by administrators to manage data service instances of various industries through a visual web interface; The front-end portal module is used to respond to user requests to view the interface directory of data service instances in various industries, create applications, subscribe to the interfaces of corresponding data service instances, and call the interfaces of data service instances in the set manner after subscription.
3. The unified industrial brain industrial data management system as claimed in claim 2, characterized in that: The various industry indicator data in the data service integration module include data maps and time series indicator data of various industries; Data services include data analysis services and data processing services; The management backend module manages the online and offline data service instances of each industry through a visual web interface, and allocates permissions to data service instances corresponding to the same data service; When performing routing forwarding, the gateway module performs load balancing according to the permissions allocated to the required data service instances.
4. A unified industrial brain industrial data management method, characterized in that: The steps include: S1. Generate data services, combining various industry indicator data to generate data service instances; S2. The administrator user manages the data service instance status through the visual web interface; S3. The registration center module registers the data service instances released by various industries and manages the registered data service instances; S4. After the gateway module is started, it requests the registration center module to obtain the data service instance interface, pull the routing information, and generate the gateway routing configuration; S5. The user logs in to the front-end portal through the client to subscribe to the data service instance, and calls the data service instance through the routing configuration of the gateway module.
5. The unified industrial brain industrial data management method as claimed in claim 4, characterized in that: The specific steps of step S1 are as follows: S11. Generate data services, including data analysis services and data processing services; S12. Obtain various industry indicator data, wherein the industry indicator data includes data maps and time series indicator data of corresponding industries; S13. Generate data service instances based on various industry indicator data.
6. The unified industrial brain industrial data management method as claimed in claim 5, characterized in that: The specific steps of step S2 are as follows: S21. The administrator user publishes the generated data service instance and controls the online and offline of the data service instance; S22. The administrator user identifies the same data service instance and assigns permissions to the same data service instance.
7. The unified industrial brain industrial data management method as claimed in claim 6, characterized in that: The specific steps of step S3 are as follows: S31. The registration center module detects whether there is a newly released data service instance; If yes, go to step S32; If not, wait for a set period of time and return to step S31; S32. The registration center module registers the newly released data service instance and saves the address of each data service instance.
8. The unified industrial brain industrial data management method as claimed in claim 7, characterized in that: The specific steps of step S4 are as follows: S41. The gateway module starts to generate a heartbeat signal and sends the heartbeat signal to the registration center module; S42. The gateway module receives the currently available data service instance information returned by the registration center module; S43. The gateway module generates a data service directory by identifying the data service instance that needs to be opened through annotations, and obtains the address of the data service instance that needs to be opened as routing data through the registration center module; S44. The gateway module generates and updates the gateway routing configuration through the acquired routing data.
9. The unified industrial brain industrial data management method as claimed in claim 8, characterized in that: The specific steps of step S5 are as follows: S51. The user registers and logs in through the client on the front-end portal, and after logging in, views the directory of data services obtained through the gateway module; S52. The user creates an application on the front-end portal through the client and subscribes to the required data service; S53. The user selects a predetermined method from the client according to the created application and pulls the routing configuration of the gateway module, identifies the routing path of the subscribed required data service, and calls the corresponding data service.
10. The unified industrial brain industrial data management method according to claim 9, characterized in that: The specific steps of step S53 are as follows: S531. The user generates a signature using the RSA algorithm based on the interface parameters of the subscribed data service instance through the client; S532. The client uses the fiter responsibility chain mode to send a request with a signature to the gateway module; S533. The gateway module performs interface verification and parameter format verification; If there is an abnormality, go to step S534; If there is no abnormality, go to step S535; S534. The gateway module returns an exception to the client and ends; S535. After the gateway module performs current limiting processing, it performs load balancing according to the subscribed data service instance and the pre-set permissions, and then performs routing forwarding of the corresponding data service instance according to the gateway routing configuration; S536. After receiving the request, the data service instance performs business logic processing; If the processing is normal, proceed to step S537; If the processing is abnormal, return to step S534; S537. The data service instance returns the processing result to the gateway module; S538. The gateway module will sign the processing result on the server side and return it to the client.