WO2021048818A1 - 工业物联网代理装置 - Google Patents
工业物联网代理装置 Download PDFInfo
- Publication number
- WO2021048818A1 WO2021048818A1 PCT/IB2020/058476 IB2020058476W WO2021048818A1 WO 2021048818 A1 WO2021048818 A1 WO 2021048818A1 IB 2020058476 W IB2020058476 W IB 2020058476W WO 2021048818 A1 WO2021048818 A1 WO 2021048818A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- iot
- data
- cloud platform
- module
- configuration
- Prior art date
Links
- 238000004519 manufacturing process Methods 0.000 claims abstract description 97
- 238000000034 method Methods 0.000 claims abstract description 38
- 230000008569 process Effects 0.000 claims abstract description 24
- 230000006399 behavior Effects 0.000 claims abstract description 19
- 238000004088 simulation Methods 0.000 claims description 44
- 238000004891 communication Methods 0.000 claims description 29
- 238000012545 processing Methods 0.000 claims description 21
- 238000012544 monitoring process Methods 0.000 claims description 19
- 230000005540 biological transmission Effects 0.000 claims description 16
- 238000013500 data storage Methods 0.000 claims description 14
- 238000013480 data collection Methods 0.000 claims description 13
- 230000008859 change Effects 0.000 claims description 10
- 230000007246 mechanism Effects 0.000 claims description 9
- 238000003860 storage Methods 0.000 claims description 8
- 238000004422 calculation algorithm Methods 0.000 claims description 7
- 238000010801 machine learning Methods 0.000 claims description 7
- 238000012986 modification Methods 0.000 claims description 6
- 230000004048 modification Effects 0.000 claims description 6
- 238000012546 transfer Methods 0.000 claims description 6
- 238000012360 testing method Methods 0.000 claims description 3
- 238000011161 development Methods 0.000 claims description 2
- 230000004044 response Effects 0.000 abstract description 6
- 238000009472 formulation Methods 0.000 abstract 1
- 239000000203 mixture Substances 0.000 abstract 1
- 230000008672 reprogramming Effects 0.000 abstract 1
- 239000003795 chemical substances by application Substances 0.000 description 122
- 230000006870 function Effects 0.000 description 14
- 238000013461 design Methods 0.000 description 10
- 238000013515 script Methods 0.000 description 9
- 210000004556 brain Anatomy 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 230000008901 benefit Effects 0.000 description 6
- 239000000047 product Substances 0.000 description 6
- 238000012800 visualization Methods 0.000 description 5
- 238000004138 cluster model Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 210000002569 neuron Anatomy 0.000 description 4
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 3
- 238000007405 data analysis Methods 0.000 description 3
- 238000013135 deep learning Methods 0.000 description 3
- 230000033001 locomotion Effects 0.000 description 3
- 230000011514 reflex Effects 0.000 description 3
- 238000012937 correction Methods 0.000 description 2
- 230000006378 damage Effects 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 210000005250 spinal neuron Anatomy 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 241000282412 Homo Species 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 244000309466 calf Species 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000002474 experimental method Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 210000003127 knee Anatomy 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 210000003205 muscle Anatomy 0.000 description 1
- 210000000653 nervous system Anatomy 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 210000004417 patella Anatomy 0.000 description 1
- 210000000426 patellar ligament Anatomy 0.000 description 1
- 230000026416 response to pain Effects 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 239000000344 soap Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
- G05B19/4188—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by CIM planning or realisation
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
- G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
- G05B19/41885—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by modeling, simulation of the manufacturing system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/23—Pc programming
- G05B2219/23005—Expert design system, uses modeling, simulation, to control design process
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/23—Pc programming
- G05B2219/23288—Adaptive states; learning transitions
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/25—Pc structure of the system
- G05B2219/25168—Domotique, access through internet protocols
-
- 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/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
-
- 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/80—Management or planning
Definitions
- the present disclosure generally relates to the Industrial Internet of Things. More specifically, the present disclosure relates to an industrial Internet of Things (I IoT) proxy module or device, which is preferably used as or used to replace a data acquisition and monitoring (SCADA) data node system and/or a traditional SCADA system to enable various Field devices and/or programmable logic controllers (PLCs) and their associated/controlled devices can be connected to the Industrial Internet of Things to perform required operations.
- I IoT industrial Internet of Things
- SCADA data acquisition and monitoring
- PLCs programmable logic controllers
- Fieldbus networks are still more reliable than Internet-connected networks and PLC control is still more reliable than cloud control.
- Industrial processes or manufacturing processes cannot tolerate any single signal loss or delay during operation, otherwise it may cause operation failure, Cause damage to equipment, cause loss of life, cause huge monetary loss, and/or cause safety issues. Therefore, there is a long-term need in the art for a system, device and/or method that can solve the above-mentioned problems, so that the existing SCADA system, PLC, and fieldbus network can be combined with I IoT, so as to perform required operations and achieve expectations. Production results and/or efficiency.
- the embodiments of the present disclosure preferably seek to alleviate, alleviate or eliminate one or more defects in the art, either individually or in any combination, by providing systems, devices and methods according to the appended claims. Or problems, such as those identified above.
- I IoT proxy module or device preferably used as or used to replace a data acquisition and monitoring (SCADA) data node, which is operatively connected to the I IoT cloud platform and To communicate in response to input from the I IoT cloud platform or automatically perform data collection and monitoring operations and exchange data and commands; it is characterized in that it can be dynamically changed according to the decisions/inputs/instructions of the I IoT cloud platform All production details/settings/parameters, including process logic, control methods, product recipes and data point settings, so that the I IoT cloud platform can control the working behavior or characteristics of I IoT modules or devices by sending reconfiguration/programming information
- the software part of the "reconfiguration/programming" is completely “reconfiguration/programming”; the "reconfiguration/programming” information is equivalent to the configuration of the I IoT module or device.
- the I IoT agent module or device is configured to be deactivated/idled or idle during initial startup or operation, until the I IoT cloud platform is initially configured or reconfigured/programmed; the I IoT agent The module or device is configured to control and monitor production after being configured or reconfigured/programmed by the I IoT cloud platform, and then transmit the corresponding predetermined or agreed data to the I IoT cloud platform; and the I IoT cloud platform can be based on the data To execute the machine learning algorithm, and can send reconfiguration/programming instructions to the I IoT agent module or device at any time, so as to realize a complete I IoT system control cycle.
- the I IoT agent module or device is configured as a "micro" environment for manufacturing In order to collect and visualize the daily operation data of the factory or process; and the I IoT cloud platform is configured into a “macro” environment focused on manufacturing, so that problems related to the desire to pursue optimal productivity can be solved.
- the I IoT proxy module or device is configured to provide security assurance to the I IoT cloud platform; wherein the I IoT proxy module or device is preferably configured to interact with field devices and/or programmable logic controllers (PLC ) Are directly connected to each other for data collection and monitoring during the process, and accurate data and results are transmitted to the I IoT cloud platform to ensure the accuracy and system security of the signal communication of the industrial Internet of Things control system.
- PLC programmable logic controller
- all data points can be set in the I IoT cloud platform, so that the type and number of data points to be transmitted can be designed according to the configuration details/detailed data in the I IoT cloud platform; and / Or, by changing the configuration details/detailed data in the I IoT cloud platform anytime and anywhere, more different types of data point transmission can be required to facilitate the interoperability of the system.
- adding new equipment to the system or changing the connection basic equipment can be carried out during the configuration process of the IoT cloud platform to contribute to the scalability of the system; and where the new configuration will be sent to the corresponding I IoT agent module or device, so that the new device can be monitored and controlled accordingly; preferably, any modification of the current configuration of the I IoT agent module or device can be completed on the remote I IoT cloud platform in a complete one-time, so that There is no need to repeatedly perform configuration updates through manual operations on both the I IoT agent module or device and the I IoT cloud platform; and the configuration consistency between the I IoT agent module or device and the I IoT cloud platform can be ensured, Because if the configuration between them is different due to errors, the data point transmission will not match, so that the system behavior will be different from what the I IoT cloud platform expects.
- the I IoT agent module or device is configured to actually perform supervisory control and data collection operations on behalf of the I IoT cloud platform, so as to facilitate centralized control of the system; and actual manufacturing behaviors therein And the results must obey the wishes of the I IoT cloud platform. Any wrong behavior of the I IoT agent module or device can be adjusted through remote configuration updates, so that the I IoT cloud platform can fully control the entire manufacturing process.
- the new I IoT agent module or device can be integrated into the I IoT cloud platform to perform manufacturing simulation based on reconfiguration/programming information or instructions, so that the newly configured I IoT agent module or device can be used.
- the IoT cloud platform is configured to include a real-time data storage area for storing/collecting real-time data during production, and preferably real-time data generated/collected during factory production, for storing/collecting simulations A simulation data storage area for data during production, and a configuration profile data storage area for storing/collecting configuration setting data of all I IoT agent modules or devices, which are set to be used for simulation processing, where the production results and/ Or the efficiency depends on the configuration setting data.
- the configuration setting data is preferably determined by at least one simulation production/testing.
- the simulation production is performed to pass the new configuration settings.
- the data is used to output simulated data, and the simulated data is compared with the real-time data input/collected in advance to determine whether the new configuration setting data reaches the expected production result and/or the target value of efficiency; and/or I IoT
- the cloud platform is configured to also include an AI processing module to facilitate the comparison between the simulated data generated by the new configuration setting data and the pre-input/collected real-time data to determine whether the new configuration setting data reaches the expected production
- the target value of the result and/or efficiency and when the target value of the expected production result and/or efficiency is not reached, new configuration setting data is generated, and the simulation production is performed again to output the new simulation data to be input/pre-input/
- the collected real-time data is compared until the expected production result and/or the target value of efficiency is reached; and/or the communication/information transfer processing module to facilitate the process between the I IoT cloud platform module and the I IoT agent module or device
- two or more I IoT agent modules or devices may form a group to provide an I IoT agent module or device cluster, so that in the event of a hardware failure, through remote configuration Mechanism, the problematic I IoT agent module or device is switched to a backup I IoT agent module or device to reduce downtime or downtime;
- the mode of the I IoT agent module or device cluster includes a repeated cluster mode, which uses dual I IoT agent modules or devices, one of the I IoT agent modules or devices in each pair is the running I IoT agent module or device, and the other is a spare I IoT agent module or device, each pair The I IoT agent modules or devices of, will switch between them; and the N+1 cluster mode, which uses N running I IoT agent modules or devices and the only backup I IoT agent module or device for switching.
- the IoT proxy module or device can not only solve the shortcomings of the existing data node SCADA solution, but also has more advantages.
- a very important concept or teaching of the present disclosure is that the integration of the I IoT agent module or device into the I IoT cloud platform can perform manufacturing simulation, so that the potential risks of the new configuration can be predicted/estimated before actual production, so as to better Solve various security issues of new technology/new I IoT.
- FIG. 1 shows the basis A schematic block diagram of an embodiment of an exemplary industrial Internet of Things agent device/system of the present disclosure
- Fig. 2 is a schematic block diagram of another embodiment of an exemplary industrial Internet of Things agent device/system according to the present disclosure
- Fig. 3 It is a schematic block diagram of another embodiment of an exemplary industrial Internet of Things agent device/system according to the present disclosure, in which I IoT agent modules or devices forming a cluster/group are used
- Figures 4a-4c show examples according to the present disclosure
- FIG. 5 is a schematic block diagram showing the data structure of an exemplary industrial Internet of Things proxy device and its specific application according to the present disclosure.
- I IoT is very important because a device that can express itself digitally becomes a device beyond itself.
- the device is no longer only used for one purpose, but can be connected to other connected devices and their data stored in the cloud. When many such devices work together, some form of environmental intelligence emerges.
- I IoT is not magical.
- the traditional automation system still exists. Newly built factories are still using proprietary SCADA, PLC and fieldbus networks. The reason for this disappointing situation is simple.
- the fieldbus network is still more reliable than the Internet connection, and PLC control is still more reliable than cloud control.
- Industrial processes cannot tolerate any single signal loss or delay during operation, because any signal loss in the industrial process may cause huge financial losses. Some things are damaged and safety issues. Therefore, according to the present disclosure, I IoT cannot completely replace the traditional SCADA system. Because the basic requirement of industrial automation is "safety", it is also the core principle of operational technology (0T, that is, dedicated hardware and software that detect or cause changes in physical processes by directly monitoring and/or controlling physical equipment (such as valves, pumps, etc.)) .
- I IoT will not deny the importance of safely opening and closing valves, starting or stopping motors, or resetting drives when receiving appropriate signals, it is still a long way for cloud-based I IoT solutions to prove their reliability.
- Security is also another important factor in the SCADA system, because it will be used for sensitive operations through dedicated protocols, proprietary interfaces, and closed networks.
- SCADA emphasizes safety control and monitoring, so standard SCADA has similar functions, for example, visual diagrams, alarms, data recording, real-time control and historical recording. Obviously, these functions are still not enough to achieve the industrial 4.0 goal, which is to provide consumers with faster, cheaper, more personalized and better quality products.
- I IoT extremely relies on the cloud platform to store daily mass production data and implement various deep learning and machine learning algorithms, it is necessary to transfer data from the automation system to the cloud platform.
- a common solution is to establish a connection between SCADA and the I IoT cloud platform.
- SCADA will be regarded as a data node for exchanging data with the I IoT cloud platform. This kind of SCADA can be called data node SCADA.
- Interoperability is the ability of I IoT to communicate between the entire system, where all system devices (regardless of their construction, version, model or manufacturer) can collect or exchange data with each other. Therefore, if a data node SCADA solution is used, the interoperability of I IoT will depend on how much data will be released to the cloud platform. The more data the data node SCADA can release, the higher the interoperability of I IoT. However, due to security reasons, the data in SCADA that can be published to the I IoT cloud platform is usually very limited. Scalability is the ability of I IoT to add devices or change the entire system infrastructure. Obviously, adding a physical device to an automation system first needs to define the device details in the data node SCADA.
- the data node SCADA should be downgraded to an I IoT agent module or device, which can be computer software or dedicated hardware/equipment, which represents the I IoT cloud platform or acts as its agent, and executes data just like a conventional SCADA. Acquisition and monitoring. It also establishes a communication channel with the I IoT cloud platform to exchange data and commands like a data node SCADA. The difference is that it can dynamically change all production details, such as process logic, control methods, product recipes, and data point settings, based on the decisions of the I IoT cloud platform.
- the I IoT cloud platform can completely “reconfigure/program” the working behavior of the I IoT agent module or device.
- This "reconfiguration/programming” information will be referred to as the configuration of the I IoT agent module or device.
- the I IoT proxy module or device starts to run, it only idles/freezes the software/device, and does nothing except wait for the I IoT cloud platform to be configured.
- I IoT agent modules or devices are just like ordinary SCADA — control and monitor production, and then transfer the agreed data to the I IoT cloud platform.
- the I IoT cloud platform can implement some machine learning algorithms, and when necessary, send reconfiguration commands to the I IoT proxy module or device at any time, thereby completing the I IoT system control cycle.
- the I IoT agent module or device which is preferably used or used to replace the data acquisition and monitoring (SCADA) data node, runs in the "microscopic" related to manufacturing, collecting and visualizing daily operating data in the factory or manufacturing process. "surroundings.
- SCADA data acquisition and monitoring
- the I IoT cloud platform can focus on the "macro" environment and more issues related to the desire to pursue the best productivity. As mentioned above, security is the core principle of OT, so it is necessary to ensure the accuracy of signal communication between the entire system.
- the I IoT cloud platform can ensure accurate communication by authorizing data collection and monitoring work to the local I IoT proxy module or device that has a direct connection between the field device and the PLC.
- the I IoT proxy module or device is a supplement to the security that the I IoT cloud platform lacks.
- the type and number of data points to be transmitted are designed by the configuration details in the I IoT cloud platform. Therefore, the number of data points in the I IoT cloud platform can be increased. Data points to increase interoperability. If necessary, the I IoT cloud platform can change the configuration details anytime and anywhere to accommodate more different types of data point transmission.
- the I IoT proxy module or device has the following two advantages. First, any modification to the current configuration in the I IoT agent module or device can be performed/completed only once on the remote I IoT cloud platform. Remote configuration updates can prevent software engineers from traveling too much, so that every time they make changes to the automation system, they do not need to perform the same update activity multiple times in different locations. Second, the configuration consistency between the I IoT agent module or device and the I IoT cloud platform can be ensured.
- I IoT agent module or device actually represents the I IoT cloud to perform supervisory control and data collection tasks. The actual behavior and results of production must obey the wishes of the I IoT cloud platform. Any erroneous behavior of the IoT agent module or device can be adjusted through configuration updates. Therefore, I IoT Cloud is the master of complete control of the entire manufacturing process.
- I IoT agent modules or devices can not only solve those imperfect data node SCADA solutions, but also gain more advantages.
- the I IoT agent module or device can be integrated on the I IoT cloud platform for manufacturing simulation. By predicting the potential risks of the new configuration before production, various security issues of the new technology I IoT can be further solved. This is a very important concept.
- FIG 2 there is a group of I IoT agent modules or devices that are remotely participating in the monitoring and data collection of the factory's automation system. Each agent has its own control area or specific purpose. These I IoT proxy modules or devices continuously send the content they capture from the manufacturing environment to the I IoT cloud platform.
- I IoT proxy modules or devices capture data
- three storage areas will be set up for simulation processing, including real-time data storage areas for storing/collecting real-time data during production and preferably real-time data generated/collected during factory production.
- a simulation data storage area for storing/collecting data during simulation production, and a configuration profile data storage area for storing/collecting configuration data/configuration setting data of all I IoT agent modules or devices.
- Other processing modules, such as AI communication modules may also exist.
- the same number of I IoT agent modules or devices are also running there for production simulation.
- the agents of the remote group include device drivers/programs for communication with external devices, but the agents of the cloud group are only equipped with analog drivers/programs for the internal communication of the I IoT cloud platform.
- the I IoT cloud platform receives data, it will immediately be stored in the real-time storage area. In the future, these data and message streams will become endless data sources for simulated agents in the cloud platform.
- the simulation agent processes the data stream, and then gives the resultant simulation data, which will be stored in the simulation data storage area. In theory, if the configuration files of two I IoT agent modules or device groups are the same, both groups will produce similar outputs.
- the output of the simulation will change according to the change.
- users can find out the relationships and characteristics between these parameters.
- This simulation process can be repeated until the user can find the best configuration solution for each I IoT agent module or device in terms of productivity, quality and safety. Then, these best configurations will be stored back into the configuration storage area. Users can transfer these configurations to the remote I IoT agent module or device and update them according to the planned maintenance schedule. After updating the I IoT agent module or device, change A new data set will be collected and sent to the I IoT cloud platform. The next simulation with a different goal starts again.
- This remote configuration mechanism allows I IoT users to adjust the manufacturing process more flexibly.
- the modification details must be carried out at a remote site, and it is difficult to verify/prove before implementation/action. As a result, it is difficult to achieve a utopia pursuing industrial 4.0.
- another advantage of using I IoT proxy modules or devices is that two or more I IoT proxy modules or devices can form a group to provide I IoT proxy modules or device clusters. Hardware failure is one of the common accidents that commonly occur. In traditional SCADA, it may not be possible to avoid downtime.
- the I IoT agent module or device can continue production by switching the problematic I IoT agent module or device to the backup I IoT agent module or device.
- the user must remotely set up more I IoT proxy modules or devices than originally needed.
- the remaining I IoT agent modules or devices will be set up with empty configuration and assigned to the standby mode, which is only used to wait for further instructions from the I IoT cloud platform.
- the second is the "N + 1" cluster model/cluster mode. That is, for any N running I IoT agent modules or devices, a backup agent will be provided for switching.
- Each model has its own advantages, and the choice can depend on the network design or project specifications.
- the implementation of various deep learning and machine learning algorithms enables the I IoT cloud platform to make decisions by identifying manufacturing patterns. Common applications such as automation and predictive maintenance are already using some of these features. Predictive maintenance completely eliminates the possibility of unexpected machine failures, thereby greatly reducing maintenance costs. This is also what Industry 4.0 promotes to manufacturers.
- its design may include the following items/features:
- SCADA functions such as real-time control, data recording, data exchange, data analysis, alarm processing and visualization.
- the modular design of the data register means that all functions/functions of the I IoT agent module or device are divided into various separate running programs. Each running program has its own unique functions. The collection of these programs is aimed at different industrial fields Solution package. By selecting different program combinations in the program group, different application requirements can be solved without touching any programming. Sometimes more specific modules are added for specific purposes. This separate program/module structure must be adopted in the design, because all the contents of the I IoT agent module or device can be configured by selecting several module programs to adapt to various application environments. As shown in Figure 4a, basically, there are three main categories of modules in the I IoT proxy module or device design.
- the Internet module is used to communicate with Internet devices, I IoT cloud and human machine interface (HMI) devices through various Internet protocols (such as Message Queuing Telemetry Transmission (MQTT), CoAP, Websockets, SOAP, AMQP, etc.).
- Industrial drives/programs or drive modules are used to communicate with fieldbuses through various industrial protocols, such as Modbus, Ethernet/IP, BACnet, and proprietary protocols of some brand PLCs, such as Mitsubishi, Siemens, Allen Bradley and Omron, etc.
- the equipment communicates with the PLC, equipment and automation system.
- the core module is used for data exchange, data processing and operation control. Industrial drive modules will participate in low-level data acquisition and control command transmission.
- the Internet module will participate in data exchange with the I IoT cloud.
- IPC inter-process communication
- the Internet Protocol module also has a similar design.
- the simulation/simulation module When using the I IoT proxy module or device for simulation/simulation in the I IoT cloud platform, the simulation/simulation module must be used to replace the drive module.
- This simulation/simulation module will be connected to the messaging system or database or any data stream processor. It reads the historical data collected by the previous I IoT agent module or device for analog output. Referring to Figure 4b, in the core module, a data register list will be constructed for storing data read from the device.
- Each node in the list has a device address to represent a data point of the device.
- the register list will automatically keep the data synchronized with the registers in various devices. The synchronization period can be set individually in each node of the register list.
- some registers are not linked to any device. These "internal" registers are usually used as temporary storage for calculations or data processing. Therefore, the register with the address link of the external device is used to read/write the register of the external device.
- the core module in addition to the data register list, the core module also maintains an event and alarm list. This list is used to track what happens in the equipment or factory. By comparing any two external or internal registers in the register list, the event point or alarm point flag will be triggered when the predefined condition/condition continues.
- the I IoT proxy module or device will represent the I IoT cloud to control various devices. Issuing control statements through the I IoT cloud platform is the best authorization method to achieve centralized control capabilities. The collection of these statements is a script that can be remotely transmitted to the I IoT agent module or device. I IoT agent module or device supports dynamic modification of scripts, It can be modified at any time, even when the device is running. According to the present disclosure, the IoT cloud platform is an Internet-based computing method/means.
- shared software and hardware resources and information can be provided to various terminals and other devices of the computer as required.
- it provides users with infrastructure hosting and developer products, used to build a series of programs from simple websites to complex applications, and provides a series of modular cloud-based services and a large number of development tools, hosting and computing, Cloud storage, data storage, translation API, forecasting.
- the cloud platform can be set up at any end of the network, for example, in a private cloud or intranet.
- the various parts of the programming environment run in sequence. First, there is a one-second idle loop (time interruption) before the main program starts. After completing the main program, the system will check the operating mode.
- the system will fully start in an idle loop. If it is in semi-automatic mode, the system continues the manual mode procedure. If it is in automatic mode, the system first continues with the automatic mode program. All parts/components (main mode, manual mode, service mode and automatic mode) can call subroutines. A subroutine can call other subroutines or call itself (recursive call). However, you should be careful when calling a subroutine so that it does not become an infinite loop. When the production line is running, all changes to the program can be made. Of course, if you make a wrong change, there may be some side effects.
- I IoT agent module or device The predecessor of I IoT agent module or device is SCADA, and its main purpose is to collect and monitor. All functions in SCADA, such as real-time control, data recording, data exchange, data analysis, alarm processing and visualization in SCADA, must be retained in the I IoT agent module or device.
- real-time system control must ensure that it responds within the specified time constraints/limits. Therefore, there must be a timer module to guarantee this specified time.
- the timer module sends a signal message to the core module at a specific time interval. When the core module receives this signal, it will complete all tasks that need to be completed, such as data refresh, script implementation, alarm processing and data logging.
- Web-based HMI can be the choice of I IoT agent module or device visualization module.
- the latest web-based technology is HTML5, and Websockets can enrich the dynamic graphics functions in the web browser.
- the client device does not need to install any software or plug-ins in the web browser. This means that any changes to the I IoT agent module or device do not require reinstallation of the software on the client side. This is why we choose Web-based HMI as the design direction of the visualization module.
- modules around the core module provide various plug-in functions or specific communication capabilities, and maintain data exchange with the core module through communication channels, such as message queues and shared memory.
- the external registers of the core module will be synchronized with the external device registers.
- the data generated by the processing engine or script calculations will be allocated to the internal registers. What's more, users can create more modules to meet their purpose. Therefore, all surrounding modules will create a data circulation flow with core modules, so the data can be switched to various devices or the IoT cloud platform.
- the IoT proxy module or device Internet protocol has set several communication channels for the above functions: Co-registered channel/topic telemetry channel/topic Heartbeat channel/theme service request channel/theme service response channel/theme registration
- Each IIoT proxy module or device must provide its identity to the IoT platform to gain access. Therefore, the IIoT proxy module or device must undergo a registration process.
- the IIoT proxy module or device will automatically generate a UUID, which is a unique identification ID used to distinguish other agents connected to the same IIoT cloud platform. Using the UUID, the IIoT proxy module or device can subscribe to the service request channel and place the registration request message in the public registration channel.
- the user must generate a serial number from the IIoT cloud platform and copy this serial number to the IIoT proxy module or device connection configuration file.
- This serial number is used in the IIoT cloud platform to distinguish IIoT proxy modules or devices.
- After restarting the IIoT proxy module or device it will send this number to the IIoT cloud platform along with registration information such as the device's host name, model, software version number, and protocol version number.
- the IIoT cloud platform will check whether this serial number accepts connections. Then, check whether the UUID number exists, and check whether the software version or protocol version supports the IIoT cloud platform. Finally, the IIoT cloud will reply whether the IIoT proxy module or device can accept the registration request.
- Heartbeat According to the present disclosure, at a specific time interval, such as every 5 seconds, the IIoT proxy module or device will send a heartbeat message to the IoT cloud platform through the heartbeat channel to inform the IIoT cloud platform of its existence. If the IIoT cloud platform cannot receive this heartbeat within a certain period of time (for example, 10 seconds), the IIoT proxy module or device can be regarded as dead.
- the heartbeat message contains some useful information, such as alarm status, mode status, communication status, and data usage status of the IIoT platform to understand the current operating status of the IIoT agent module or device.
- the IIoT proxy module or device will continuously send a data stream called telemetry to the I IoT cloud platform through the telemetry channel.
- the telemetry structure will depend on how the user designs the objects and data points, so it is dynamic and different from the project.
- the telemetry structure can also provide a time stamp based on the configured settings.
- Each object group has a unique key, namely prefix + object name + suffix, as described in the following section.
- the I IoT proxy module or device will provide various services to the I IoT cloud platform to control its behavior, such as restart, activation, deactivation and configuration.
- the IIoT proxy module or device will subscribe to the service request channel to listen for requests from the IIoT platform. When the request comes, if the request meets all the condition checks, the IIoT proxy module or device will analyze the required service type and execute the corresponding service. Not only can it control IIoT proxy modules or devices, the IIoT cloud can also directly control machinery and equipment by placing request messages on this service channel.
- the IIoT proxy module or device has three operating stages that can be connected to the IIoT cloud platform. These are the registration phase, the configuration phase and the operation phase.
- the gateway will have two operating modes available. These are active mode and standby mode.
- the I IoT agent module or device In the active mode, the I IoT agent module or device operates completely through telemetry and data polling. There is no telemetry transmission and data polling in the standby mode, so it is silent.
- Object-oriented modeling and address matching Object-oriented modeling is to construct an object by using an object collection containing the stored values of instance variables found in the object. It allows object recognition and communication, while supporting data abstraction, inheritance and encapsulation. This will be the best technology for users to create a data structure in the I IoT cloud and use the same data structure in the entire I IoT cloud and I IoT agent modules or devices.
- An object is a real-world entity with certain characteristics, which are identified as attribute values of the object. Each attribute is just a data point of the I IoT agent module or device. Objects are entities that encapsulate all data points as attributes. Therefore, when creating a project in the IoT cloud, these data points must be organized in an object-attribute structure.
- the I IoT system usually uses key-value storage as a NoSQL database because it is simple and has better durability and indexing. In addition, key-value stores can handle unstructured data in an excellent way. Therefore, the key value pair data transmission must be required in the I IoT agent module or device. There must be a translation method to make the data points of the object-attribute structure a key value pair (KVP) data structure. This is an example.
- KVP key value pair
- the device ST1021 can detect the humidity and temperature of the room.
- Object Object-ST1021 Attribute (ATTRIBUTES) Value (VALUE) Temperature (TEMPERATURE) 23.4 Humidity (HUMIDITY) 76.8
- Object OBJECT
- ATTRIBUTES Attribute
- TEMPERATURE Temperature
- Humidity Humidity
- ST1201 is a related object, which is just a device for detecting temperature and humidity.
- KVP Key/Data Points
- VALUE Key/Data Points
- each KEY represents a data point in the register list of the I IoT agent module or device.
- the data in these registers whether internal or external, will be encapsulated as KVP in the object package for transmission to the I IoT cloud.
- each data point is also linked to one or consecutive field device addresses. We usually call this field device address the tag address. The representation of these tag addresses varies from device to device. This is because various device tags have their own address format standards. for example,
- Each register file contains a list of data points with additional addresses. These addresses have some attributes, such as data type, register area, register address and operation size. These attributes must be abstracted into general processing details for operation.
- This Device-Tag data structure instead of simply using this Device-Tag data structure to encapsulate data points, we use an object-attribute data structure.
- the object-attribute structure is very similar to the device-tag structure, but they usually have different meanings. Which can encapsulate any register object on different devices. These objects with their own attributes are understandable to users.
- the device is just the hardware where the register list is located. These registers can be read through physical lines without any logical relationship or sequence. The device label structure may not be difficult to understand.
- DB1DW1006 R1_ST1021_2-HUMIDITY it generally provides an industrial Internet of Things (I IoT) proxy module or device, which is preferably used as or used to replace the data acquisition and monitoring (SCADA) data node system and/or
- the traditional SCADA system is operatively connected and communicated with the I IoT cloud platform to respond to input from the I IoT cloud platform or automatically perform data collection and monitoring operations and exchange data and commands; it is characterized in that it can be based on the I IoT cloud platform.
- the decision/input/instruction of the IoT cloud platform dynamically changes all its production details/settings/parameters, including process logic, control methods, product recipes and data point settings, so that the IoT cloud platform can be reconfigured by sending/
- the programming information completely "reconfigures/programs" the software part of the I IoT module or device that controls its working behavior or characteristics; the "reconfiguration/programming" information is equivalent to the configuration of the I IoT module or device.
- the I IoT agent module or device is configured to be deactivated/idled or idle during initial startup or operation, until the I IoT cloud platform is initially configured or reconfigured/programmed; the I IoT agent The module or device is configured to control and monitor production after being configured or reconfigured/programmed by the I IoT cloud platform, and then transmit the corresponding predetermined or agreed data to the I IoT cloud platform; and the I IoT cloud platform can be based on the data To execute the machine learning algorithm, and can send reconfiguration/programming instructions to the I IoT agent module or device at any time, so as to realize a complete I IoT system control cycle.
- the I IoT agent module or device is configured to be used in a "micro" manufacturing environment, so that daily operating data of the factory or process can be collected and visualized; and the I IoT cloud platform is configured to focus on The “macro” environment of manufacturing so that problems related to the desire to pursue optimal productivity can be solved.
- the I IoT proxy module or device is configured to provide security assurance to the I IoT cloud platform; wherein the I IoT proxy module or device is preferably configured to interact with field devices and/or programmable logic controllers (PLC ) Are directly connected to each other for data collection and monitoring during the process, and accurate data and results are transmitted to the I IoT cloud platform to ensure the accuracy and system security of the signal communication of the industrial Internet of Things control system.
- PLC programmable logic controller
- all data points can be set in the I IoT cloud platform, so that the type and number of data points to be transmitted can be designed according to the configuration details/detailed data in the I IoT cloud platform; and / Or, by changing the configuration details/detailed data in the I IoT cloud platform anytime and anywhere, more different types of data point transmission can be required to facilitate the interoperability of the system.
- adding new equipment to the system or changing the connection basic equipment can be carried out during the configuration process of the IoT cloud platform to contribute to the scalability of the system; and where the new configuration will be sent to the corresponding I IoT agent module or device, so that the new device can be monitored and controlled accordingly; preferably, any modification of the current configuration of the I IoT agent module or device can be completed on the remote I IoT cloud platform in a complete one-time, so that There is no need to repeatedly perform configuration updates through manual operations on both the I IoT agent module or device and the I IoT cloud platform; and the configuration consistency between the I IoT agent module or device and the I IoT cloud platform can be ensured, Because if they When the configuration is different due to errors, the data point transmission will not match, so that the system behavior will be different from the expected I IoT cloud platform.
- the I IoT agent module or device is configured to actually perform supervisory control and data collection operations on behalf of the I IoT cloud platform, so as to facilitate centralized control of the system; and the actual production behavior and The result must obey the wishes of the I IoT cloud platform. Any wrong behavior of the I IoT agent module or device can be adjusted through remote configuration updates, so that the I IoT cloud platform can fully control the entire manufacturing process.
- the new I IoT agent module or device can be integrated into the I IoT cloud platform to perform manufacturing simulation based on reconfiguration/programming information or instructions, so that the newly configured I IoT agent module or device can be used.
- the IoT cloud platform is configured to include a real-time data storage area for storing/collecting real-time data during production, and preferably real-time data generated/collected during factory production, for storing/collecting simulations A simulation data storage area for data during production, and a configuration profile data storage area for storing/collecting configuration setting data of all I IoT agent modules or devices, which are set to be used for simulation processing, where the production results and/ Or the efficiency depends on the configuration setting data.
- the configuration setting data is preferably determined by at least one simulation production/testing.
- the simulation production is performed to pass the new configuration settings.
- the data is used to output simulated data, and the simulated data is compared with the real-time data input/collected in advance to determine whether the new configuration setting data reaches the expected production result and/or the target value of efficiency; and/or I IoT
- the cloud platform is configured to also include an AI processing module to facilitate the comparison between the simulated data generated by the new configuration setting data and the pre-input/collected real-time data to determine whether the new configuration setting data reaches the expected production
- the target value of the result and/or efficiency and when the target value of the expected production result and/or efficiency is not reached, new configuration setting data is generated, and the simulation production is performed again to output the new simulation data to be input/pre-input/
- the collected real-time data is compared until the expected production result and/or the target value of efficiency is reached; and/or the communication/information transfer processing module to facilitate the process between the I IoT cloud platform module and the I IoT agent module or device
- two or more I IoT agent modules or devices may form a group to provide an I IoT agent module or device cluster, so that in the event of a hardware failure, through remote configuration Mechanism, the problematic I IoT agent module or device is switched to a backup I IoT agent module or device to reduce downtime or downtime;
- the mode of the I IoT agent module or device cluster includes a repeated cluster mode, which uses dual I IoT agent modules or devices, one of the I IoT agent modules or devices in each pair is the running I IoT agent module or device, and the other is a spare I IoT agent module or device, each pair The I IoT agent modules or devices of, will switch between them; and the N+1 cluster mode, which uses N running I IoT agent modules or devices and the only backup I IoT agent module or device for switching.
- the IoT agent module or device is configured to simulate or function as a neuron to form or implement a reflection function in response to system production tasks or operating states or events, thereby automatically performing required responses or processing.
- the experimenter Just as in the knee jump reflex experiment, in response to a knock under the kneecap or on the patellar tendon, the experimenter’s calf kicks unintentionally. Reflexes can be completed automatically and quickly without brain thinking, which is of great significance to the ability of humans to successfully deal with the environment.
- the information processing capacity of billions of neurons in the brain is very powerful, and independent neurons are especially needed to complete many tasks automatically. If there is no independent neuron to automatically complete the reaction and work automatically, the brain may be overloaded.
- the brain will constantly update/adjust the positions of various unstable body parts to keep the human body upright.
- the ability to carry out complex thoughts, such as learning, organizing work and memorizing things will be limited.
- the response to pain and other stimuli will be greatly slowed by the need for the brain to think.
- the reflex mechanism is very useful for correcting muscle movements, so that dangerous situations such as slips or trips can be quickly responded to, in which a very fast movement correction or correction is used to prevent human falls and injuries.
- the IoT cloud platform can be configured to simulate or play the role of the brain, and the IoT proxy module or device can be configured to simulate or play the role of spinal neuron.
- the sensor When the sensor sends signals to the I IoT agent module or device, it can immediately respond to these signals to perform corresponding appropriate operations, thereby simulating the reflection mechanism of the human body.
- the motion control and monitoring tasks are assigned to remote I IoT agent modules or devices (spinal neurons), so as to respond to the rapidly changing manufacturing and production environment as soon as possible and avoid the I IoT cloud platform (brain) Or the entire system is overloaded. It is obvious that the features and attributes of the specific embodiments disclosed above can be combined in different ways to form additional embodiments, and all these embodiments fall within the scope of the present disclosure.
- conditional language used here such as “can”, “may”, “may”, “may”, “for example”, etc., unless expressly stated otherwise, or can be understood in other ways in the context of use, otherwise It is generally meant to convey that certain embodiments include, while other embodiments do not include certain features, components, and/or states. Therefore, such conditional language is generally not intended to imply that one or more embodiments require the described features, components, and/or states in any case.
- the present disclosure has been described above with reference to specific embodiments. However, other embodiments than the above are equally possible within the scope of the present disclosure. Method steps different from those described above can be provided within the scope of the present disclosure. The different features and steps of the present disclosure can be combined into other combinations than those described. The scope of the present disclosure is only limited by the appended patent claims.
Landscapes
- Engineering & Computer Science (AREA)
- Manufacturing & Machinery (AREA)
- Automation & Control Theory (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Health & Medical Sciences (AREA)
- Programmable Controllers (AREA)
- Control By Computers (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB2112008.4A GB2599487B (en) | 2019-09-13 | 2020-09-11 | IIoT agent device |
CN202080016105.XA CN113841095A (zh) | 2019-09-13 | 2020-09-11 | 工业物联网代理装置 |
US17/432,588 US20220357724A1 (en) | 2019-09-13 | 2020-09-11 | IIoT Agent Device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
HK19129656.5 | 2019-09-13 | ||
HK19129656 | 2019-09-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021048818A1 true WO2021048818A1 (zh) | 2021-03-18 |
Family
ID=74865888
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2020/058476 WO2021048818A1 (zh) | 2019-09-13 | 2020-09-11 | 工业物联网代理装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20220357724A1 (zh) |
CN (1) | CN113841095A (zh) |
GB (1) | GB2599487B (zh) |
WO (1) | WO2021048818A1 (zh) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114721338A (zh) * | 2022-03-21 | 2022-07-08 | 西安拽亘弗莱工业自动化科技有限公司 | 一种基于嵌入式系统的物联网的数据采集设备 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104950836A (zh) * | 2014-03-26 | 2015-09-30 | 洛克威尔自动控制技术股份有限公司 | 使用工业云代理的预置型数据收集和摄取 |
US20170063566A1 (en) * | 2011-10-04 | 2017-03-02 | Electro Industries/Gauge Tech | Internet of things (iot) intelligent electronic devices, systems and methods |
CN107491044A (zh) * | 2016-06-09 | 2017-12-19 | 罗克韦尔自动化技术公司 | 用于自动控制系统的可扩展分析架构 |
CN109150703A (zh) * | 2018-08-23 | 2019-01-04 | 北方工业大学 | 一种工业物联网智能云网关及其通信方法 |
CN109729143A (zh) * | 2017-10-31 | 2019-05-07 | 慧与发展有限责任合伙企业 | 在终端设备上部署基于网络的云平台 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9467500B2 (en) * | 2012-08-09 | 2016-10-11 | Rockwell Automation Technologies, Inc. | Remote industrial monitoring using a cloud infrastructure |
US9703902B2 (en) * | 2013-05-09 | 2017-07-11 | Rockwell Automation Technologies, Inc. | Using cloud-based data for industrial simulation |
US9843617B2 (en) * | 2014-03-26 | 2017-12-12 | Rockwell Automation Technologies, Inc. | Cloud manifest configuration management system |
-
2020
- 2020-09-11 US US17/432,588 patent/US20220357724A1/en active Pending
- 2020-09-11 WO PCT/IB2020/058476 patent/WO2021048818A1/zh active Application Filing
- 2020-09-11 CN CN202080016105.XA patent/CN113841095A/zh active Pending
- 2020-09-11 GB GB2112008.4A patent/GB2599487B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170063566A1 (en) * | 2011-10-04 | 2017-03-02 | Electro Industries/Gauge Tech | Internet of things (iot) intelligent electronic devices, systems and methods |
CN104950836A (zh) * | 2014-03-26 | 2015-09-30 | 洛克威尔自动控制技术股份有限公司 | 使用工业云代理的预置型数据收集和摄取 |
CN107491044A (zh) * | 2016-06-09 | 2017-12-19 | 罗克韦尔自动化技术公司 | 用于自动控制系统的可扩展分析架构 |
CN109729143A (zh) * | 2017-10-31 | 2019-05-07 | 慧与发展有限责任合伙企业 | 在终端设备上部署基于网络的云平台 |
CN109150703A (zh) * | 2018-08-23 | 2019-01-04 | 北方工业大学 | 一种工业物联网智能云网关及其通信方法 |
Also Published As
Publication number | Publication date |
---|---|
GB2599487B (en) | 2024-04-10 |
CN113841095A (zh) | 2021-12-24 |
GB2599487A (en) | 2022-04-06 |
US20220357724A1 (en) | 2022-11-10 |
GB202112008D0 (en) | 2021-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Redelinghuys et al. | A six-layer digital twin architecture for a manufacturing cell | |
RU2674758C1 (ru) | Способ и система для управления процессом установки в сети "машина-машина" на основе opc-ua | |
US20230297408A1 (en) | Modular process control system | |
Lee et al. | Distributed measurement and control based on the IEEE 1451 smart transducer interface standards | |
Samad et al. | System architecture for process automation: Review and trends | |
Dai et al. | Toward self-manageable and adaptive industrial cyber-physical systems with knowledge-driven autonomic service management | |
Dai et al. | A cloud-based decision support system for self-healing in distributed automation systems using fault tree analysis | |
Koziolek et al. | Self-commissioning industrial IoT-systems in process automation: a reference architecture | |
Gonçalves et al. | A step forward on intelligent factories: A smart sensor-oriented approach | |
Bigheti et al. | Control as a service: a microservice approach to Industry 4.0 | |
Hästbacka et al. | Device status information service architecture for condition monitoring using OPC UA | |
Rosas et al. | Approach to Adapt a Legacy Manufacturing System Into the IoT Paradigm. | |
Bloch et al. | A microservice-based architecture approach for the automation of modular process plants | |
Strasser et al. | Autonomous application recovery in distributed intelligent automation and control systems | |
Lam et al. | Dynamical orchestration and configuration services in industrial iot systems: An autonomic approach | |
Elamanov et al. | Interworking between Modbus and internet of things platform for industrial services | |
Abdelsattar et al. | An OPC UA Client/Gateway-Based Digital Twin Architecture of a SCADA System with Embedded System Connections | |
WO2021048818A1 (zh) | 工业物联网代理装置 | |
Al Sunny et al. | Remote monitoring and online testing of machine tools for fault diagnosis and maintenance using MTComm in a cyber-physical manufacturing cloud | |
Tietz et al. | Development of an internet of things gateway applied to a multitask industrial plant | |
Vakili et al. | Open source fog architecture for industrial IoT automation based on industrial protocols | |
Redelinghuys | An architecture for the digital twin of a manufacturing cell | |
Barbosa et al. | Engineering an ADACOR based solution into a small-scale production system | |
Lyu et al. | Multi-agent based IEC 61499 function block modelling for distributed intelligent automation | |
Tan et al. | Development of an OPC client-server framework for monitoring and control systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20862570 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 202112008 Country of ref document: GB Kind code of ref document: A Free format text: PCT FILING DATE = 20200911 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20862570 Country of ref document: EP Kind code of ref document: A1 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20862570 Country of ref document: EP Kind code of ref document: A1 |