CN113657774A - Internet of things cloud platform system for textile printing and dyeing - Google Patents
Internet of things cloud platform system for textile printing and dyeing Download PDFInfo
- Publication number
- CN113657774A CN113657774A CN202110955780.5A CN202110955780A CN113657774A CN 113657774 A CN113657774 A CN 113657774A CN 202110955780 A CN202110955780 A CN 202110955780A CN 113657774 A CN113657774 A CN 113657774A
- Authority
- CN
- China
- Prior art keywords
- service
- layer
- micro
- data
- cloud platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004043 dyeing Methods 0.000 title claims abstract description 26
- 238000007639 printing Methods 0.000 title claims abstract description 22
- 239000004753 textile Substances 0.000 title claims abstract description 21
- 238000004519 manufacturing process Methods 0.000 claims abstract description 36
- 238000012545 processing Methods 0.000 claims abstract description 26
- 230000005540 biological transmission Effects 0.000 claims abstract description 11
- 238000004891 communication Methods 0.000 claims abstract description 10
- 238000007405 data analysis Methods 0.000 claims abstract description 7
- 238000003860 storage Methods 0.000 claims abstract description 5
- 238000012800 visualization Methods 0.000 claims abstract description 5
- 238000004364 calculation method Methods 0.000 claims abstract description 4
- 238000007726 management method Methods 0.000 claims description 67
- 238000000034 method Methods 0.000 claims description 22
- 230000008569 process Effects 0.000 claims description 17
- 238000012423 maintenance Methods 0.000 claims description 14
- 238000012384 transportation and delivery Methods 0.000 claims description 11
- 230000007246 mechanism Effects 0.000 claims description 7
- 238000005096 rolling process Methods 0.000 claims description 6
- 238000001914 filtration Methods 0.000 claims description 5
- 238000000586 desensitisation Methods 0.000 claims description 4
- 230000035515 penetration Effects 0.000 claims description 3
- 238000009941 weaving Methods 0.000 claims description 3
- 230000006855 networking Effects 0.000 claims 1
- 238000005516 engineering process Methods 0.000 description 11
- 238000011161 development Methods 0.000 description 9
- 238000004422 calculation algorithm Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000012544 monitoring process Methods 0.000 description 6
- 238000013475 authorization Methods 0.000 description 5
- 238000004458 analytical method Methods 0.000 description 4
- 238000007689 inspection Methods 0.000 description 4
- 239000012141 concentrate Substances 0.000 description 2
- 239000004744 fabric Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000002955 isolation Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 238000009987 spinning Methods 0.000 description 2
- 238000007619 statistical method Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004061 bleaching Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 238000013481 data capture Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 239000006185 dispersion Substances 0.000 description 1
- 238000001035 drying Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000000149 penetrating effect Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000003908 quality control method Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000009991 scouring Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000009999 singeing Methods 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
- 238000005303 weighing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Development Economics (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Manufacturing & Machinery (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
An Internet of things cloud platform system for textile printing and dyeing comprises a field display layer, an access layer, a service layer, an edge processing layer and a field device layer which are sequentially in communication connection; the field display layer is used for the client to negotiate communication with the server and visually display the cloud platform system on the client; the access layer is used for identifying the caller identity of the client and verifying the authority; the service layer comprises a component service layer and a business service layer, wherein the component service layer is used for distributed storage and application of factory data, calculation and data processing, and provides interface resources and basic data services for the business service layer; the business service layer is used for providing a plurality of application subsystems, and performing real-time data analysis, visualization service and user-defined service on data of each application subsystem; the edge processing layer is used for realizing data transmission between the service layer and the field device layer; and the field device layer is used for acquiring the production data of various devices in the factory workshop.
Description
Technical Field
The invention relates to the technical field of textile printing and dyeing, in particular to an Internet of things cloud platform system for textile printing and dyeing.
Background
With the continuous development of the internet of things in the textile printing and dyeing industry, the form and the links of the industrial chain of the textile industry are basically formed, and the market main body of the spinning, weaving and dyeing process is mainly a medium-sized and small-sized enterprise, but the problems that technical equipment falls behind, the informatization degree is not high, head enterprises are insufficient, the labor cost is continuously and soarly raised and the like are generally faced at present.
In a traditional information management system of a printing and dyeing enterprise, the system is generally divided into several functional systems such as ERP, MES and PCS, each system operates independently, and generated data form a data island, so that the relevance and the fusion of the data are insufficient, and the lean production and the rapid development of the printing and dyeing enterprise are difficult to promote.
Disclosure of Invention
The invention aims to provide an Internet of things cloud platform system for textile printing and dyeing aiming at the defects in the background technology, which combines enterprise management, decision, market information and field monitoring information to form a set of plan management, equipment management, energy management, quality management, process management, warehousing management and intelligent scheduling, personnel management, big data analysis, independently study etc. many functional module's many tenants management wisdom weaving cloud platform system, enterprise's managers can all manage and control each link of mill through channels such as cell-phone, computer, billboard, big screen anytime and anywhere, help the enterprise effectively to improve work efficiency, reduce extra communication, the data transfer cost that the system brought across, promote the operational efficiency of enterprise, platform system has adopted the four-layer structure to constitute from bottom to top, and the structure science, well-defined and scalability is strong.
In order to achieve the purpose, the invention adopts the following technical scheme:
an Internet of things cloud platform system for textile printing and dyeing comprises a field display layer, an access layer, a service layer, an edge processing layer and a field device layer which are sequentially in communication connection;
the field display layer is used for a client to negotiate communication with a server and visually display the cloud platform system on the client;
the access layer is used for identifying and verifying the caller identity of the client;
the service layer comprises a component service layer and a business service layer, wherein the component service layer is used for distributed storage and application of factory data, calculation and data processing, and provides interface resources and basic data services for the business service layer; the business service layer is used for providing a plurality of application subsystems, and performing real-time data analysis, visualization service and user-defined service on data of each application subsystem;
the edge processing layer is used for realizing data transmission between the service layer and the field device layer;
and the field device layer is used for acquiring production data of various devices in a factory workshop.
Preferably, the access layer is further configured to expose only the API gateway to the outside, where the API gateway has a black and white list and a current limiting function to identify the identity of the caller at the client, determine whether the caller has a call authority and whether the number of calls of the caller reaches an upper limit, and determine whether the API reaches the upper limit of the calls.
Preferably, the component service layer is further configured to provide interface resources and basic data services, including a rule engine, data permissions, a data warehouse, scheduling management, log service, dictionary management, shift management, timing service, a process engine, form service, authentication service, interface management, workflow, and tenant management, for the plurality of application subsystems of the business service layer.
Preferably, the business service layer comprises an MES manufacturing execution subsystem, an EMS energy management subsystem, an EAM equipment asset subsystem, a QMS quality management subsystem, an RMS process management subsystem, a WMS warehouse management subsystem, an HRMS personnel management subsystem and a DMS terminal operation and maintenance subsystem, and the application subsystem of the business service layer is visually displayed on the client through the field display layer.
Preferably, the application subsystems of the service layer adopt a micro-service architecture, including micro-service modularization among the application subsystems, each micro-service is provided with an independent database, each micro-service is provided with an API module, and each micro-service calls an interface through the API module.
Preferably, the field display layer calls the API module of each microservice through the back end, and specifically includes:
the field display layer directly penetrates and calls the API module of each micro service through a route penetration interface at the rear end and/or the field display layer creates a custom API module at the rear end and calls the API module of each micro service through the custom API module.
Preferably, the calling between the micro-services comprises:
when each micro service is started, the IP and the port of the micro service are stored in the registration center, each micro service can pull the IP and the port of all other micro services from the registration center, and the API module of the corresponding micro service is called through the pulled IP and port;
the current micro service can only call API modules of other micro services, and cannot directly access databases of other micro services.
Preferably, when the API module of the microservice needs to be exposed to the network, the access layer performs authentication through the API gateway, and counts the request amount of the system.
Preferably, the microservice is equipped with a distributed transaction mechanism, and when the microservice delivers a non-transaction message, the microservice performs the following operations:
the microservice updates the database of the microservice, and if the updating fails, the delivery is terminated; if the delivery is successful, delivering the message to the message queue, and rolling back the database when the delivery is failed;
when the micro service delivers the transaction message, the following operations are executed:
delivering a Prepared message by the micro service, updating a database of the micro service, and rolling back the Prepared message if the updating of the database of the micro service fails; if the message is successful, the micro-service updates the state of the Prepared message to be the sent state;
if the state of the Prepared message fails to be updated, the message queue regularly confirms whether the database is successfully updated or not to the micro service, if the database is successfully updated, the state of the Prepared message is updated to be a sent state, and if the database is unsuccessfully updated, the Prepared message is rolled back.
Preferably, the edge processing layer comprises an intelligent controller, an edge gateway and an edge server, and the plant shop equipment of the field device layer is connected to the edge processing layer through an industrial protocol;
the intelligent controller is used for acquiring the production data of the factory workshop equipment acquired by the field equipment layer and controlling the production flow of the factory workshop equipment;
the edge gateway is used for collecting the production data of each factory workshop device, performing filtering statistics and desensitization treatment, and summarizing and transmitting the treated production data to the edge server;
and the edge server is used for integrating and centralizing the production data of the workshop equipment of the factory and transmitting the production data to the cloud database.
The beneficial effect that this application's technical scheme produced:
the invention combines enterprise management, decision, market information and field monitoring information to form a multi-tenant management intelligent textile cloud platform system which integrates a plurality of functional modules such as plan management, equipment management, energy management, quality management, process management, warehousing management, intelligent scheduling, personnel management, big data analysis, autonomous learning and the like.
Drawings
Fig. 1 is a frame diagram of an internet of things cloud platform system for textile printing and dyeing according to an embodiment of the invention;
FIG. 2 is a block diagram of microservice 1 and microservice 2 of one embodiment of the present invention;
FIG. 3 is a front and rear end split frame view of one embodiment of the present invention;
FIG. 4 is a framework diagram of microservice 1 invoking microservice 2 of one embodiment of the invention;
FIG. 5 is a cache structure diagram of microservice 1 and microservice 2 of one embodiment of the invention;
FIG. 6 is a framework diagram of distributed transaction messaging for microservice 1, microservice 2, and microservice 3 of one embodiment of the present invention;
FIG. 7 is a cloud-native framework diagram of one embodiment of the invention.
Detailed Description
The technical scheme of the invention is further explained by the specific implementation mode in combination with the attached drawings.
The invention provides an Internet of things cloud platform system for textile printing and dyeing, which comprises a field display layer, an access layer, a service layer, an edge processing layer and a field device layer which are sequentially in communication connection, wherein the access layer, the service layer, the edge processing layer and the field device layer are sequentially arranged on the field display layer;
the system adopts the cloud native technology and the micro-service architecture to ensure that the expansibility, the portability and the usability of the whole platform are better, and the method specifically comprises the following steps:
the field display layer is used for a client to negotiate communication with a server and visually display the cloud platform system on the client;
in the application, a user can use any client of a mobile terminal and a PC terminal to negotiate communication with the server terminal, the system adopts a B/S architecture and supports access of an HTTPS protocol, the HTTPS protocol is a network protocol which is constructed by HTTP and TLS/SSL protocol and can carry out encryption transmission and identity authentication, and the encryption of internet data transmission is completed mainly through technologies such as digital certificates, encryption algorithms, asymmetric keys and the like, so that the security protection of internet transmission is realized;
in this embodiment, the client and the server may negotiate an encryption algorithm that needs to be used in the transmission process before starting to transmit data. The client sends a negotiation request to the server, wherein the negotiation request comprises a self-supported asymmetric encryption key exchange algorithm, a data signature digest algorithm, a symmetric encryption algorithm for encrypting transmission data and the length of an encryption key. After receiving the message, the server selects the algorithm with the highest security, and sends the selected algorithm to the client to complete the negotiation.
The access layer is used for identifying and verifying the caller identity of the client;
preferably, the access layer is further configured to expose only the API gateway to the outside, where the API gateway has a black and white list and a current limiting function to identify the identity of the caller at the client, determine whether the caller has a call authority and whether the number of calls of the caller reaches an upper limit, and determine whether the API reaches the upper limit of the calls.
In this embodiment, the system only exposes the API gateway to the outside, and the API gateway has a black-and-white list and a current limiting function, and can identify the identity of the caller, determine whether the caller has an authority and has reached the upper limit of the number of calls, and also determine whether the API has reached the upper limit of the number of calls, so as to prevent malicious data capture and further limit abnormal ip login access. The request of error or abnormity can be directly processed at the access layer, and the API gateway of the access layer adopts a fusing or service degradation mechanism to prevent the avalanche effect, thereby ensuring the safety and stability of the whole platform. The authority control is mainly divided into two blocks, Authentication (Authentication) and Authorization (Authorization). After the identity is confirmed to be correct after authentication, the service system can carry out authorization, the system adopts an RBAC model, and the RBAC model comprises the following four elements: user, role, authority, resource. The user is the source, the resource is the target, the user is bound to the role, the resource is associated with the authority, and finally the role is associated with the authority, so that a relatively complete and flexible authority control model is formed. The system is visually displayed at a client, displayed menus and interface elements are generally realized by matching front-end codes with stored data, and URL access resource control is realized by adopting SpringSecurity and Shiro mechanisms; and (3) data authority control: realizing (cutting surface and spinning in) a DataScopeInnerInterreceptor interceptor based on Mybatis, and replacing and adding a filtering condition when analyzing the bottom SQL by adopting a plugin mechanism of Mybatis; and the authority verification of scheduling between services is strengthened by a JWT mode, and the safety of internal services is ensured.
Furthermore, the system adopts a software architecture technology of a multi-tenant technology, and the multi-tenant technology is realized by sharing the same system or program components under a multi-user environment and can still ensure the isolation of data among users. Many organizations use an application that must be able to allow their users access to the application, but the application must only allow each organization's own members to access its organization's data. The multi-tenant technology can realize sharing of application services among multiple tenants, and can ensure that parts with system commonality are shared and parts with strong privacy, such as data, are isolated independently.
Furthermore, when the system is actually deployed, each tenant has an independent data source, and when the system is executed, the data source can be dynamically switched, so that the data isolation is good, the expansibility is high, and the fault influence is small. In the process that a user logs in a system through a visual client, when a back-end request is called, a token needs to be carried in a request header, after an API gateway analyzes and verifies the token and decodes the token, basic information such as a user ID, a user account number, a name and a decoded tend is packaged into the request header, the request is forwarded to specific business services, and each business service is provided with a context interceptor used for packaging information such as the user ID and a tenant code in the request header into LocalThread. Thus, when the request reaches the Controller- > Service- > Mapper layer, the program can acquire the information of the current login person and the tenant code through LocalThread for switching the data source and the Service processing.
The service layer comprises a component service layer and a business service layer;
the component service layer is used for distributed storage and application of factory data, calculation and data processing, and provides interface resources and basic data services for the business service layer;
specifically, the component service layer is further configured to provide interface resources and basic data services for the multiple application subsystems of the business service layer, including a rule engine, a data authority, a data warehouse, scheduling management, log service, dictionary management, shift management, timing service, a process engine, form service, authentication service, interface management, workflow and tenant management, and may be deployed in a private cloud, a public cloud, or a hybrid cloud.
The business service layer is used for providing a plurality of application subsystems, and performing real-time data analysis, visualization service and user-defined service on data of each application subsystem;
preferably, the business service layer comprises an MES manufacturing execution subsystem, an EMS energy management subsystem, an EAM equipment asset subsystem, a QMS quality management subsystem, an RMS process management subsystem, a WMS warehouse management subsystem, an HRMS personnel management subsystem and a DMS terminal operation and maintenance subsystem, and the application subsystem of the business service layer is visually displayed on the client through the field display layer;
in this embodiment, the business Application layer may perform real-time data analysis, visualization service, and user-defined service on data, where the data is acquired from the data center layer through an Application Programming Interface (API);
the functions of the subsystems of the business service layer are as follows:
the MES manufacturing execution subsystem comprises production progress tracking, production operation planning, production performance statistics and production abnormity warning;
the EMS energy management subsystem comprises energy instrument management, energy data acquisition, energy statistical analysis and energy abnormity warning;
the EAM equipment asset subsystem comprises equipment centralized monitoring, equipment fault maintenance, equipment planned maintenance, equipment inspection plan and equipment comprehensive efficiency analysis;
the QMS quality management subsystem comprises grey cloth incoming inspection, finished product warehousing inspection, dyeing completion inspection, quality standard management, a light security system and quality tracing analysis;
the RMS process management subsystem comprises process data management, order process binding, process parameter synchronization and process analysis optimization;
the WMS storage management subsystem comprises warehouse entry and exit management, work-in-process management and control, material statistical analysis and warehouse inventory;
the HRMS personnel management subsystem comprises personnel file management, piece counting and work reporting, performance statistics and post skill management;
the DMS terminal operation and maintenance subsystem comprises terminal operation monitoring, terminal remote monitoring, remote operation and maintenance and OTA (over the air) upgrading.
Preferably, as shown in fig. 2, a micro-service architecture is adopted between application subsystems of the service layer, including micro-service modularization between application subsystems, each micro-service is provided with an independent database, each micro-service is provided with an API module, and each micro-service calls an interface through the API module.
In this embodiment, each microservice uses an independent database, and calls among services provide a relevant interface, so that an API module and a management terminal are separated, the API module serves other modules, the management terminal manages data of the module, and the API module has higher performance, stability and security requirements than the management terminal; meanwhile, the functional boundary can be clearer, the production operation and the service decoupling are facilitated, a service resource pool is formed, dispersion or combination can be carried out according to the customer requirements, and the iterative development of products is quickly adapted.
Preferably, as shown in fig. 3, the calling, by the field display layer, the API module of each microservice by the back end specifically includes:
the field display layer directly penetrates and calls the API module of each micro service through a route penetration interface at the rear end and/or the field display layer creates a custom API module at the rear end and calls the API module of each micro service through the custom API module.
In this embodiment, if the field display layer directly calls the API module of the micro service, the problem that the micro service needs to perform user authentication and authorization is caused, the service backend is invoked, the user authentication and authorization are uniformly performed, the field display layer calls the micro service API through the backend, and the two modes can be divided into:
firstly, the API module of the micro-service can well meet the requirement of the front end, and then the API module of the micro-service is directly penetrated through a route penetrating interface of the rear end;
secondly, the API module of the micro-service can not meet the requirement of the front end, the API module of the micro-service needs to be customized at the back end, for example, the user detail function is checked, and a plurality of micro-service interfaces need to be called in the customized interface.
Through the separation of the front end and the back end, the development, the deployment and the operation and maintenance can be carried out independently, the team development efficiency is improved, the coupling degree of software design is reduced, the front end and the back end can be used for different ends, some standardized development can be realized, and the two teams do not influence each other. Meanwhile, the capability of processing complex services is improved, the back end can only concentrate on the back-end services, and the front end can concentrate on the services of the front end.
Preferably, as shown in fig. 4, the call between the microservice and the microservice includes:
when each micro service is started, the IP and the port of the micro service are stored in the registration center, each micro service can pull the IP and the port of all other micro services from the registration center, and the API module of the corresponding micro service is called through the pulled IP and port;
the current micro service can only call API modules of other micro services, and cannot directly access databases of other micro services.
Specifically, taking micro service 1 and micro service 2 as examples, the method specifically includes the following steps:
step S1: when the micro services 1 and 2 are started, the self IP and the port are told to the registration center;
step S2: the microservices 1 and 2 pull the IP and ports of all microservices from the registry;
step S3: the micro service 1 directly calls the micro service 2 through an IP and a port;
when microservice 1 needs to obtain data for microservice 2, the API of microservice 2 should be called and the database of microservice 2 cannot be accessed directly. When the API call fails, the specified number of times is automatically retried, and the default is 3 times.
Preferably, as shown in fig. 5, when the API module of the micro service needs to be exposed to the network, the access layer performs authentication through the API gateway to count the request amount of the system.
Further, if the request amount of the system is large, an EhCache and J2Cache memory caching scheme and Redis/MemCache caching service can be introduced; because the hardware cost is lower and lower, some cache data are reserved in the memory and can be quickly obtained when access is needed, the service response speed is improved, and the user experience is better. The memory reading speed is faster than the hard disk IO operation, the performance is stronger, and the pressure of reading and writing the database data is greatly reduced.
Preferably, as shown in fig. 6, the microservice is equipped with a distributed transaction mechanism, and when delivering a non-transaction message, the microservice performs the following operations:
step H1: the microservice updates the database of the microservice, and if the updating fails, the delivery is terminated;
step H2: if the delivery is successful, delivering the message to the message queue, and rolling back the database when the delivery is failed;
when the micro service delivers the transaction message, the following operations are executed:
delivering a Prepared message by the micro service, updating a database of the micro service, and rolling back the Prepared message if the updating of the database of the micro service fails; if the message is successful, the micro-service updates the state of the Prepared message to be the sent state;
if the state of the Prepared message fails to be updated, the message queue regularly confirms whether the database is successfully updated or not to the micro service, if the database is successfully updated, the state of the Prepared message is updated to be a sent state, and if the database is unsuccessfully updated, the Prepared message is rolled back.
The system adopts a distributed architecture, and the server is completed by the cooperation of a large number of services and database instances. In a scenario with a high requirement for consistency, the problem of consistency between multiple independent operations is particularly troublesome. The distributed system is different from a single system, and simultaneously meets Consistency, Availability and Partition fault Tolerance in CAP law, which cannot be realized, and most scenes need to sacrifice strong Consistency to replace high Availability of the system to ensure final Consistency. The distributed transaction is to ensure the final consistency of the transaction in a large-scale distributed environment.
Meanwhile, idempotent verification, anti-suspension processing and step-by-step revocation operation of the service are guaranteed by a distributed transaction mechanism.
Further, as shown in fig. 7, the business service layer further includes using a cloud native technology;
with the advent of K8S and open source technologies supporting microservices, the operation, maintenance, deployment and use of the whole platform are more efficient. The standardization of development, test, production and the like is ensured through the mirroring technology of the container, various faults and problems caused by inconsistent application running environments are avoided, automatic operation and maintenance and rapid delivery of the running environments are realized through service arrangement, and the problems of complex running, long delivery cycle and the like of an application system in a traditional mode are avoided. The platform provides various automatic operation and maintenance tool management application cluster systems, for example, intelligent loads can observe changes of cluster nodes in real time and intelligently modify routing configuration, automatic expansion can achieve automatic adjustment of cluster scales under different service loads, and the like, automation of various management functions reduces manual operation and maintenance workload, and operation and maintenance cost is saved. The container of the platform resources is virtualized based on an operating system, decoupling is realized with laaS basic environment, most of the realization of the platform is a development framework and a standard API with wider application, the resource management level can be effectively improved, and the binding of manufacturers is effectively avoided; meanwhile, the effective deployment of the container density on a single operating system is reasonably adjusted, so that the resource utilization rate can be better improved, and the hardware purchasing cost is reduced. The standardization of the operating environment can really realize the fine control of the technical route, unify the technical research and development routes of different projects, effectively implement the effective landing of the CI/CD idea through the unification of the deployment tools, and effectively improve the quality control level in the software research and development process. Compared with the traditional mode that development, operation and maintenance respectively perform own functions, the method can effectively realize the landing implementation of DevOps thinking, promote enterprise management of enterprise IT flows and personnel frameworks, and better improve the overall technical level of each research and development team of an IT department, thereby better responding to business requirements. The construction thinking route of the information system is changed from taking the business process as the center to taking the user as the center by relying on the shared service capability provided by the platform. The participation of users is emphasized, the interaction is enhanced, the required service is customized for the specific user, and the continuous change of the user demand can be quickly responded, so that the supporting force of informatization for business is improved.
The edge processing layer is used for realizing data transmission between the service layer and the field device layer;
preferably, the edge processing layer comprises an intelligent controller, an edge gateway and an edge server, and the plant shop equipment of the field device layer is connected to the edge processing layer through an industrial protocol;
the intelligent controller is used for acquiring the production data of the factory workshop equipment acquired by the field equipment layer and controlling the production flow of the factory workshop equipment;
the edge gateway is used for collecting the production data of each factory workshop device, performing filtering statistics and desensitization treatment, and summarizing and transmitting the treated production data to the edge server;
and the edge server is used for integrating and centralizing the production data of the workshop equipment of the factory and transmitting the production data to the cloud database.
The edge access layer is a data plane for interaction between the edge terminal ecology and the platform, and can realize data transmission between the field device layer and the service layer. The edge access layer can be constructed based on a wired network, a wifi network or a 4G/5G network, so that a data link of the system can be ensured to be realized in a wired and wireless combined mode, high-bandwidth low-delay data transmission of mass traffic data is realized, and the edge access layer is the basis for realizing distributed deployment of all levels of the system.
The edge processing layer comprises an intelligent controller, an edge gateway and an edge server, and the devices of the field device layer are connected to the edge processing layer through industrial protocols such as USB interfaces, serial ports, Modbus, TCP/IP, OPC, CANopen, RS232, Profinet and the like. The intelligent controller controls the flow production process of the dyeing machine, the boarding machine and other equipment by acquiring data acquired by the equipment sensors (the equipment sensors are installed on each equipment on the field equipment layer), so that the equipment normally runs to complete the production task. The edge gateway collects data of each device for filtering statistics and desensitization processing, and collects valuable information and forwards the valuable information to an edge server for analysis. Meanwhile, the edge server is used as a data hub, massive data of all equipment in a factory are integrated and subjected to centralized preprocessing, the safety and the stability of data links of all the equipment are guaranteed through a secure API and a terminal cloud encryption technology called by RPC service, and the data links are transmitted to a cloud database.
And the field device layer is used for acquiring production data of various devices in a factory workshop.
The field equipment layer comprises various equipment facilities located in a factory workshop, including a color machine, a setting machine, a mercerizing machine, a washing machine, a cloth inspecting machine, a drying machine, a scouring and bleaching machine, a singeing machine, a scutching machine, a dehydrator, a logistics trolley and video monitoring equipment. The equipment is provided with a sensor and an audio and video signal acquisition device according to the working requirements, and the information acquired in the production process transmits data to the edge processing layer in a wired or wireless mode.
Besides being connected with field dyeing and finishing equipment, the system can also be connected with a third-party system (such as ERP, equipment central control, automatic weighing and feeding system and the like).
The technical principle of the present invention is described above in connection with specific embodiments. The description is made for the purpose of illustrating the principles of the invention and should not be construed in any way as limiting the scope of the invention. Based on the explanations herein, those skilled in the art will be able to conceive of other embodiments of the present invention without inventive effort, which would fall within the scope of the present invention.
Claims (10)
1. The utility model provides a weaving printing and dyeing's thing networking cloud platform system which characterized in that: the system comprises a field display layer, an access layer, a service layer, an edge processing layer and a field device layer which are sequentially in communication connection;
the field display layer is used for a client to negotiate communication with a server and visually display the cloud platform system on the client;
the access layer is used for identifying and verifying the caller identity of the client;
the service layer comprises a component service layer and a business service layer, wherein the component service layer is used for distributed storage and application of factory data, calculation and data processing, and provides interface resources and basic data services for the business service layer; the business service layer is used for providing a plurality of application subsystems, and performing real-time data analysis, visualization service and user-defined service on data of each application subsystem;
the edge processing layer is used for realizing data transmission between the service layer and the field device layer;
and the field device layer is used for acquiring production data of various devices in a factory workshop.
2. The internet of things cloud platform system for textile printing and dyeing according to claim 1, characterized in that:
the access layer is also used for exposing only the API gateway to the outside, and the API gateway has a black and white list and a current limiting function so as to identify the caller identity of the client, judge whether the caller has a calling authority and whether the calling frequency of the caller reaches the upper limit, and simultaneously judge whether the API reaches the called upper limit.
3. The internet of things cloud platform system for textile printing and dyeing according to claim 1, characterized in that:
the component service layer is also used for providing interface resources and basic data services for a plurality of application subsystems of the business service layer, and the interface resources and the basic data services comprise a rule engine, data authority, a data warehouse, scheduling management, log service, dictionary management, shift management, timing service, a process engine, form service, authentication service, interface management, workflow and tenant management.
4. The internet of things cloud platform system for textile printing and dyeing according to claim 2, characterized in that:
the business service layer comprises an MES manufacturing execution subsystem, an EMS energy management subsystem, an EAM equipment asset subsystem, a QMS quality management subsystem, an RMS process management subsystem, a WMS warehousing management subsystem, an HRMS personnel management subsystem and a DMS terminal operation and maintenance subsystem, and the application subsystem of the business service layer is visually displayed on the client through the field display layer.
5. The internet of things cloud platform system for textile printing and dyeing according to claim 4, characterized in that:
the application subsystems of the business service layer adopt a micro-service architecture, the micro-service modularization is carried out between the application subsystems, each micro-service is provided with an independent database, each micro-service is provided with an API module, and each micro-service calls an interface through the API module.
6. The internet of things cloud platform system for textile printing and dyeing according to claim 5, characterized in that:
the field display layer calls the API module of each micro service through the back end, and the method specifically comprises the following steps:
the field display layer directly penetrates and calls the API module of each micro service through a route penetration interface at the rear end and/or the field display layer creates a custom API module at the rear end and calls the API module of each micro service through the custom API module.
7. The internet of things cloud platform system for textile printing and dyeing according to claim 6, characterized in that:
the calling between the micro-service and the micro-service comprises the following steps:
when each micro service is started, the IP and the port of the micro service are stored in the registration center, each micro service can pull the IP and the port of all other micro services from the registration center, and the API module of the corresponding micro service is called through the pulled IP and port;
the current micro service can only call API modules of other micro services, and cannot directly access databases of other micro services.
8. The internet of things cloud platform system for textile printing and dyeing according to claim 7, characterized in that:
and when the API module of the micro service needs to be exposed to the network, the access layer authenticates through the API gateway and counts the request quantity of the system.
9. The internet of things cloud platform system for textile printing and dyeing according to claim 8, characterized in that:
the micro service is provided with a distributed transaction mechanism, and when delivering a non-transaction message, the micro service performs the following operations:
the microservice updates the database of the microservice, and if the updating fails, the delivery is terminated; if the delivery is successful, delivering the message to the message queue, and rolling back the database when the delivery is failed;
when the micro service delivers the transaction message, the following operations are executed:
delivering a Prepared message by the micro service, updating a database of the micro service, and rolling back the Prepared message if the updating of the database of the micro service fails; if the message is successful, the micro-service updates the state of the Prepared message to be the sent state;
if the state of the Prepared message fails to be updated, the message queue regularly confirms whether the database is successfully updated or not to the micro service, if the database is successfully updated, the state of the Prepared message is updated to be a sent state, and if the database is unsuccessfully updated, the Prepared message is rolled back.
10. The internet of things cloud platform system for textile printing and dyeing according to claim 1, characterized in that:
the edge processing layer comprises an intelligent controller, an edge gateway and an edge server, and factory workshop equipment of the field equipment layer is connected to the edge processing layer through an industrial protocol;
the intelligent controller is used for acquiring the production data of the factory workshop equipment acquired by the field equipment layer and controlling the production flow of the factory workshop equipment;
the edge gateway is used for collecting the production data of each factory workshop device, performing filtering statistics and desensitization treatment, and summarizing and transmitting the treated production data to the edge server;
and the edge server is used for integrating and centralizing the production data of the workshop equipment of the factory and transmitting the production data to the cloud database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110955780.5A CN113657774A (en) | 2021-08-19 | 2021-08-19 | Internet of things cloud platform system for textile printing and dyeing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110955780.5A CN113657774A (en) | 2021-08-19 | 2021-08-19 | Internet of things cloud platform system for textile printing and dyeing |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113657774A true CN113657774A (en) | 2021-11-16 |
Family
ID=78481372
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110955780.5A Pending CN113657774A (en) | 2021-08-19 | 2021-08-19 | Internet of things cloud platform system for textile printing and dyeing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113657774A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114328699A (en) * | 2022-03-15 | 2022-04-12 | 心鉴智控(深圳)科技有限公司 | Operation and maintenance control system for industrial production line |
| CN114828007A (en) * | 2022-04-30 | 2022-07-29 | 佛山技研智联科技有限公司 | Data processing method, device and system based on edge gateway and edge gateway |
| CN115203212A (en) * | 2022-09-07 | 2022-10-18 | 南通全织道家纺科技有限公司 | Home textile customer data collection system based on big data |
| CN116319090A (en) * | 2023-05-18 | 2023-06-23 | 中国电子信息产业集团有限公司第六研究所 | Power and environment monitoring system and method based on micro-service |
| CN117826694A (en) * | 2024-03-06 | 2024-04-05 | 北京和利时系统集成有限公司 | Intelligent electromechanical system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109709811A (en) * | 2018-12-20 | 2019-05-03 | 中国科学院沈阳自动化研究所 | A kind of edge calculations controller and its working method towards intelligence manufacture |
| CN110658794A (en) * | 2019-09-30 | 2020-01-07 | 歌尔股份有限公司 | Manufacturing execution system |
| CN112346347A (en) * | 2020-10-19 | 2021-02-09 | 天筑科技股份有限公司 | Intelligent building integrated management system and information processing method thereof |
| CN112765117A (en) * | 2021-01-26 | 2021-05-07 | 中国船级社 | Industrial internet identification analysis system based on micro-service architecture |
| WO2021103588A1 (en) * | 2019-11-28 | 2021-06-03 | 青岛海尔工业智能研究院有限公司 | Intelligent manufacturing system |
| CN113110326A (en) * | 2021-04-12 | 2021-07-13 | 清华大学 | Intelligent factory operating system based on industrial Internet architecture |
-
2021
- 2021-08-19 CN CN202110955780.5A patent/CN113657774A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109709811A (en) * | 2018-12-20 | 2019-05-03 | 中国科学院沈阳自动化研究所 | A kind of edge calculations controller and its working method towards intelligence manufacture |
| CN110658794A (en) * | 2019-09-30 | 2020-01-07 | 歌尔股份有限公司 | Manufacturing execution system |
| WO2021103588A1 (en) * | 2019-11-28 | 2021-06-03 | 青岛海尔工业智能研究院有限公司 | Intelligent manufacturing system |
| CN112346347A (en) * | 2020-10-19 | 2021-02-09 | 天筑科技股份有限公司 | Intelligent building integrated management system and information processing method thereof |
| CN112765117A (en) * | 2021-01-26 | 2021-05-07 | 中国船级社 | Industrial internet identification analysis system based on micro-service architecture |
| CN113110326A (en) * | 2021-04-12 | 2021-07-13 | 清华大学 | Intelligent factory operating system based on industrial Internet architecture |
Non-Patent Citations (3)
| Title |
|---|
| 史扬;: "边缘计算释放物理世界的潜能", 电气时代, no. 06, pages 47 - 49 * |
| 张洁: "大数据驱动的纺织智能制造平台架构", 《纺织学报》, no. 10, pages 159 - 165 * |
| 范钢: "《架构师书库 架构真意 企业级应用架构设计方法论与实践》", 30 June 2021, 机械工业出版社, pages: 204 - 210 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114328699A (en) * | 2022-03-15 | 2022-04-12 | 心鉴智控(深圳)科技有限公司 | Operation and maintenance control system for industrial production line |
| CN114828007A (en) * | 2022-04-30 | 2022-07-29 | 佛山技研智联科技有限公司 | Data processing method, device and system based on edge gateway and edge gateway |
| CN115203212A (en) * | 2022-09-07 | 2022-10-18 | 南通全织道家纺科技有限公司 | Home textile customer data collection system based on big data |
| CN116319090A (en) * | 2023-05-18 | 2023-06-23 | 中国电子信息产业集团有限公司第六研究所 | Power and environment monitoring system and method based on micro-service |
| CN116319090B (en) * | 2023-05-18 | 2023-08-11 | 中国电子信息产业集团有限公司第六研究所 | Power and environment monitoring system and method based on micro-service |
| CN117826694A (en) * | 2024-03-06 | 2024-04-05 | 北京和利时系统集成有限公司 | Intelligent electromechanical system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113657774A (en) | Internet of things cloud platform system for textile printing and dyeing | |
| CN111181727B (en) | Open API full life cycle management method based on micro service | |
| CN110995736B (en) | Universal industrial Internet of things equipment management system | |
| US9967168B2 (en) | Remote real-time monitoring system based on cloud computing | |
| CN105139139B (en) | Data processing method and device and system for O&M audit | |
| CN105119750A (en) | Distributed information security operation and maintenance management platform based on massive data | |
| CN107193669A (en) | The system and design method of maintenance interface based on mixed cloud or large-scale cluster | |
| JP2015062133A (en) | Web service based communication for use with process control system | |
| CN102739802A (en) | Service application-oriented IT contralized operation and maintenance analyzing system | |
| Ramesh et al. | The Smart Network Management Automation Algorithm for Administration of Reliable 5G Communication Networks | |
| CN106779485B (en) | SOA architecture-based comprehensive management system and data processing method | |
| CN104636678B (en) | The method and system of management and control is carried out under a kind of cloud computing environment to terminal device | |
| CN112926954A (en) | Cross-network government affair information exchange system and method based on artificial intelligent robot | |
| CN111130922A (en) | Airborne information safety automatic test method and test platform | |
| CN107193668A (en) | The call method and system at interface service end | |
| CN113642939B (en) | Power marketing system full-channel unified access platform and method | |
| US11531612B2 (en) | Methods for providing an enterprise synthetic monitoring framework | |
| CN113327060A (en) | Intelligent factory management system and method thereof | |
| US20050086285A1 (en) | System and method for dynamic distributed data processing utilizing hub and spoke architecture | |
| CN111464350B (en) | Method and system for managing heterogeneous brand network equipment | |
| CN106127573B (en) | A kind of lightness operation system and method | |
| CN112764944A (en) | MOM system automation equipment data interaction integration platform and method based on OPC UA protocol | |
| CN109886528A (en) | A method of management control is executed for manufacturing | |
| CN113204459A (en) | U shield testing method, device, equipment and medium | |
| CN113778709A (en) | Interface calling method, device, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |