The Industry 4.0 platform and the Industrial Internet Alliance IIC jointly published the White Paper on Architecture Interconnection and Interoperability on December 5, 2017, which has aroused widespread interest in China. However, the IIC released the White Paper on the Connectivity Framework of the Industrial Internet of Things on February 28, 2017. It has been more than a year, but it has been a cold reception. Obviously, the importance of connecTIvity in Industry 4.0 and Industrial Internet has not been understood and fully understood in China.
This may be because there is no concept of connectivity in Industry Reference Architecture RAMI 4.0, but there is a level of communication (communicaTIon) in the dimension of the physical world mapped to the virtual world by its functional characteristics. The function of the communication layer in the white paper of RAMI4.0 is used to handle the transmission of communication protocols, data and files. It uses a uniform data format in the direction of the information layer to ensure communication standardization; and to provide control for the integration layer. This is simply to convert the various information generated during the manufacturing process into a unified data format, which has not been refined to which communication protocols are to be transmitted, and the task of "delivering the appropriate data to the right place at the right time" is completed. . This may also reflect Germany's unavoidable reality that lags far behind the United States in terms of digital communications and the Internet. Because German Industry 4.0 has had a profound impact on our country, we have turned a blind eye to some of its weaknesses. In fact, the German industrial and technological community has gradually understood and recognized this. Otherwise, it cannot explain the cooperation process between the Industry 4.0 platform and the Industrial Internet Alliance. Why did it start from 2015, but it encountered setbacks until 2017? Only then began to have a substantial push.
Another reason is that the connectivity technology belongs to the basic technology of communication. It is not the kind of technology with high so-called “display degreeâ€. The domestic has always adopted the attitude of passive follow-up, and most of them adopt “takenismâ€. Therefore, the articles on the Industrial Internet Platform are cumbersome, but few descriptions of connectivity are seen.
The leading alliance of Industrial Internet of Things IIoT is the US Industrial Internet Alliance IIC and the German Industrie 4.0 (I4.0) platform. Both have their own merits, IIC has established a technical framework across the industrial sector; while Industry 4.0 focuses on manufacturing, but beyond the technical architecture, involved in the supply chain and product life cycle. As these goals and architectures are complementary, the two organizations are working together to map out the future of development, establishing a blueprint for interoperability between Industry 4.0 and the Industrial Internet (see figure below).
Figure | Establishing Interoperability between Industry 4.0 and Industrial Internet
Ubiquitous connectivity is a basic technology for data sharing between various participating components in the Industrial Internet of Things IIoT system. Connectivity is the ability to connect between participants, providing functional domains, cross-functional domains within the system, and data exchange across systems. These data exchanges include sensor data refreshes, events, alarms, status changes, commands, and configuration refreshes. In short, connectivity is a horizontal interaction function across functional domains (defined by the Industrial Internet Reference Architecture) (see figure below).
Figure | Connectivity is a horizontal interaction
In the figure, the green arrow: data/information flow; gray-white arrow: decision flow; red arrow: command/request flow.
The functional domains are: control functional domain, information functional domain, application functional domain, operational operational functional domain and business functional domain.
The IIoT field is filled with a wide range of proprietary connectivity technologies, as well as some small-scale specific application cases and optimization standards in vertically integrated systems. These specific range of connection technologies are quite optimized within their respective applications, but they are an obstacle to data sharing, design, architecture, and communication in establishing new value streams and opening up the global IIoT market. The primary purpose of IIoT connectivity is to open the flow of these isolated, isolated systems, enabling data and interoperability between these closed components and subsystems to be used in a variety of industries and across industries. New and emerging ecological applications have been formed and developed.
We need to establish a wide range of IIoT connectivity. By defining a stacking model of IIoT connectivity and an open, connected reference architecture, the various stakeholders involved in IIoT, the applicability of the connectivity technologies being developed and applied by the opponent, are categorized, evaluated and validated.
Due to the limitations of historical development, the classic open system for interconnecTIon 7-layer model and the Internet 4-layer model cannot accurately describe the requirements of industrial Internet connectivity. As a key foundation of the Industrial Internet, IIoT requires a new connected functional layer model to focus on distributed sensors, controllers, gateways, devices and devices, and other application components of distributed systems.
Of course, this model is based on the OSI model and the Internet model. According to the new requirements, networking (physical layer, link layer, network layer), connectivity (transport layer, frame layer) and information are proposed. The layer communication model, also known as the IIoT joint stacking model, serves as the connectivity scope for the horizontal interaction function within the Industrial Internet Reference Architecture IIRA (see figure below).
Figure | 6-layer model of Industrial IoT IIoT communication
The interoperable layer of the IIoT system is in the shape of an hourglass. At the top is a broad data model pedigree and features for specific vertical industries; the neck is typically used across the Internet layer across vertical industries. Unicom provides a basic data sharing mechanism that supports advanced features such as distributed data interoperability and management as a horizontal interaction that enables grammar interoperability (note: not semantic interoperability).
Figure | IIoT Connectivity Stacking Model
The hourglass neck is the starting point for the "Internet" in IIoT. In view of the fact that the joint layer above the neck is not well understood and understood, in order to construct the IIoT system, it is necessary to focus on and study the connection function on the "Internet" networking layer.
Figure | Functionality of the joint stacking model of the IIoT system
The figure above shows the IIoT joint stacking model and the range of joint functionality as a horizontal interaction function in the Industrial Internet Reference Architecture IIRA. Unicom functionality provides a mechanism for data sharing between participants in the same functional domain and between participants across the functional domains in the IIoT system. As can be seen from the figure, the bottom layer is the physical layer, which uses physical media (wired, wireless) to connect all participants of the network, and carries out the transmission of physical signals (electric signals, optical signals or other) characterized by "bits". . It is a link layer for sharing physical links between adjacent participants and for exchanging "frames" by signal transmission protocols. Further above is the network layer, which performs exchanges characterized by a finite length of "packets", possibly with multi-link routing communication between non-adjacent (remote) participants. Further up is the transport layer, which communicates communication messages of different lengths between participants' applications. On top of this is the framework layer, which refers to the provision of configurable structured data (state, event, data flow) exchanges between participant applications with quality of service QoS. The above is beyond the scope of the connection, is the function of distributed data interoperability and management horizontal interaction, relying on the specific physical meaning of information sharing provided by the connection framework layer.
By the way, it is pointed out that the Internet Protocol (IP) is a connection standard popular in the network layer. It was born because of the Internet. Now it is also used in the Internet of Things, and it has independent enabling on the upper and lower layers of the network layer. Innovation. Although IP connectivity, non-IP connectivity, and considerable wireless access technologies continue to evolve and enter the market, the IIoT community has new options, but the following three layers are identical to the OSI model and are well known. The layers above the network layer have developed rapidly in the last decade, but have not been widely recognized and understood. Therefore, this document focuses on the layers above the network layer, namely the connection transport layer and the link frame layer.
Industrial Internet Reference Architecture IIRA Connectivity The task in the entire architecture is to support data exchange between endpoints in a participating interconnected system. For example, information includes sensor refresh, remote data, control commands, alarms, events, status changes or configuration updates, and time-recorded data. The basic task of linking is to provide interoperable communication between endpoints to ensure integration of various components. However, the goal of the connectivity feature is limited to providing syntax interoperability between the endpoints involved in the join.
Interoperability in communications can range from customer integration to abstraction of plug-and-play based on open standards. Interoperability is generally classified as follows:
☆ Technology interoperability refers to the ability to exchange information expressed in bits and bytes. This builds on the infrastructure of information exchange, and the networks and protocols under the infrastructure are clearly defined.
☆ Syntax interoperability refers to the ability to exchange information expressed in the usual data structure. This is based on a common protocol that already uses construction data, and the structure of the information exchange has been clearly defined. Syntax interoperability is premised on the fact that technology interoperability has been established.
☆ Semantic interoperability refers to the ability to exchange data meanings under the context of appropriate interpretation of information (ie, context). Semantic interoperability is premised on the fact that grammar interoperability has been established.
For the IIoT system, the connectivity functionality has two functional layers: the connection transport layer and the join frame layer. The former provides a method and means for transmitting data between endpoints; it implements technical interoperability between endpoints in data exchange. This function corresponds to the Layer 4 transport layer of the OSI7 layer model, or the transport layer corresponding to the Internet model. The join framework layer provides the endpoint with a structured structuring of the data and completes the parsed process; it provides a mechanism for grammatical interoperability between endpoints. In this join framework layer, "common data structure" refers to the structure or pattern of the data being exchanged. For example, the data structures and database schemas in the programming languages ​​we are familiar with. The function of the join framework corresponds to the 5th layer (conference layer) to the 7th layer (application layer) in the OSI7 layer model, or the application layer of the Internet model. The tasks and scope of the IIoT's connectivity functional layer can be found in the table below.
The data service framework in distributed data interoperability and management functions is based on the syntax interoperability provided by the link framework layer. The dynamic composition and coordination functions of the Industrial Internet Reference Architecture require semantic interoperability.
The join framework layer provides logical data exchange services for participating endpoints in the information exchange. At this level, data exchange can be observed and "understood", and relevant knowledge is used to optimize the transfer of data. It is a logical functional layer located above the connection transport layer, and it should not be necessary to know the techniques for implementing the connection transport layer. The join framework layer provides syntax interoperability between endpoints, and the data exchanged has a common and unambiguous data format that is independent of the implementation of the endpoint and decoupled from the hardware and programming platform. Related to the application logic behind the endpoint, one or more patterns of data exchange may be required, with two main modes of data exchange: publish-subscribe and request-response.
The key benefit of the connection framework layer is to abstract and hide the implementation of different functions, so that the application software used in the connection framework does not need to understand the specific method of implementation, but utilizes the capabilities of the Unicom framework layer. This reduces development costs and increases productivity and quality.
Table | Tasks and scope of the IIoT connectivity functional layer
The core functions of the connection framework layer include data resource model, publish-subscribe and request-response exchange mechanism, data quality of service, data security and programmable API. The following figure is summarized as follows.
Figure | The core functions of the link frame layer
The connection transport layer provides a logical transport network for endpoint connections. A join transfer is similar to an opaque pipe that performs data flow between endpoints. The key task of the Unicom transport layer is to provide technical interoperability between endpoints. The core functions of China Unicom's transmission include: endpoint addressing, communication mode, network topology, connectivity, priority management, timing and synchronization, and message security. The following figure outlines the core features of the connection transport layer.
Figure | The core functions of the connection transport layer
The IIoT joint frame layer standard gives the connection standards that were originally used for related vertical industries (eg oneM2M for the telecommunications industry, OPC-UA for manufacturing), which provides the technical characteristics of the enabling industries and can also Many other industries provide application services. Additional connectivity standards (such as DDS and Internet services) were originally used for general-purpose, non-specific industry applications, and can obviously be used for many different types of application services in many other industries. The transport layer is dedicated to the framework layer, and there is no other functional space between the framework layer and the transport layer.
Figure | IIoT System Connectivity Standard
The difference between the transport layer and the framework layer is important. The transport layer must be paired with a data type system. For example, the message queue telemetry transport protocol MQTT can be paired with a data type system technology such as protocol buffers developed by Google, and can be used to establish a dedicated user's connectivity framework. .
Obviously, none of the currently available connectivity standards can fully meet the requirements of the IIoT system, and can complete data from various types of industrial production systems and production management systems, such as high-speed robotic production lines, discrete manufacturing, and process control systems. Circulation and connectivity provide impeccable connectivity for ultra-large-scale systems that interconnect everything and connect people and things. To this end, it is necessary to select a number of standards to form a core standard, and constitute a complementary standard cluster of connectivity. However, this standard cluster cannot exceed 3 to 4 standards. Otherwise, the number of core gateways established between these standards is too large, and the timely flow and real-time flow of data becomes impractical and unrealizable.
The figure above outlines the core standards of the IIoT joint framework layer and transport layer. As can be seen from the figure, there are four core standards for the connection framework layer, one of which is derived from the general-purpose WEB service HTTP, and one is the data distribution service DDS which is rarely used by other countries except the United States; the other two It is derived from specific applications in certain vertical industries, but it can obviously be extended to many industries and even cross-industry applications, namely OPC UA popular in manufacturing and oneM2M developed by the telecommunications industry and currently mainly used for home automation. DDS and OPC UA define their own transport protocols, while Web services and oneM2M rely on a common transport protocol. For the complete expression, various protocols of the network IP layer and the lower link layer and physical layer are also shown. Web services that use HTTP are called a binding framework for applications, primarily for human user interaction interfaces.
The main basis for selecting core standards is 10, which are clearly outlined in the table below. The first five items are the key criteria that must be met, and they cannot be used as long as one item does not meet the requirements.
Table | Table of criteria for the core standard of the IIoT Connectivity Framework
The DDS goal is a joint framework standard for IIoT applications, typically used for control, industrial applications, information and operational operations. Its main purpose is to connect components (devices, gateways, or applications) to other components, making them systems in real-time systems and systems. Components interact in a shared data space and never interact directly with each other. It can also be called a data-centric middleware standard. It has been rooted in high-tech applications for defense, industry and embedded for many years.
DDS implements direct component-data-component communication through a relational data model. DDS is also known as the data bus because it simulates the moving data in the database, while the database only manages the data stored in it rather than flowing. Both the database and the data bus implement a data-centric abstraction; but their applications do not interact directly, but rather interact with the infrastructure. Unlike a database, a database stores the generated data for later searching with the relevant attributes of the stored data. The data bus filters incoming data through data attributes to manage future data. Data-centricity makes the database essentially a large-scale storage system. Data-centricity makes the data bus a basic technology for IIoT software integration and autonomous operation.
Similar to the method of access control for stored data, the data bus controls data access and refresh with many concurrent components. At its core, DDS builds a publish-subscribe data exchange mechanism around data. But the standard also defines a data exchange mechanism for request-response. The key abstraction is that each application interacts with the data bus itself, rather than having the application interact directly with other participating applications. DDS provides accurate data-centric quality of service QoS, including reliable multicast, configurable delivery, multiple levels of data duration, historical data, automatic discovery of component and transport redundancy, connection management, and no need to know Transfer details, data-centric transmission of information security. In addition, one-to-many, many-to-one communication is a prominent feature. DDS provides a powerful way to filter and precisely choose what data to send to, and this "where" target can be thousands of simultaneous components. To support small edge devices, there is a lightweight version of the DDS that runs in a limited embedded environment. The DDS data bus guarantees ultra-reliable operation and simplifies the coding for the program. It does not require service and is extremely easy to configure and operate, thus eliminating fault points and blocking points. A DDS-based system does not have application coding interactions between components. DDS automatically discovers and connects components that are being released and receiving, and new components (such as smart machines) are added to the system without having to make configuration changes. Components can be developed on their own or by an independent third party. DDS overcomes the problems of peer-to-peer systems, such as the lack of scalable performance, lack of interoperability, and the ability to evolve the architecture. It features plug-and-play simplicity, scalability, and exceptionally high real-time performance.
Due to its flexibility, reliability, and the ability to quickly build complex or real-time systems, DDS is often used for system integration and building autonomous systems. In summary, DDS is a proven, highly reliable, high-performance technology for building large-scale, cross-vertical IIoT software systems. Industrial IoT applications using DDS include farmland, hospital healthcare group, health insurance, autopilot and automotive, rail, asset tracking, automated testing, smart city, communications, data center switching, video sharing, consumer electronics, oil and gas exploration , radio and television, air traffic control, avionics, SCADA, robotics and defense.
Existing DDS gateways include many connection technologies such as DNP3, C37.118, Modbus, HLA, JMS and more. The DDS-Webv 1.0 specification defines a standard Web services gateway. The OMG organization is developing a gateway standard between DDS and OPC UA. The OPC Foundation is developing an OPC-UA-DDS release profile that targets DDS as an additional publish-subscribe communication option. oneM2M is studying the gateway that works together between oneM2M and DDS, the oneM2M protocol that binds DDS, and the direct exchange of data between oneM2M entities based on DDS.
Without a complete and efficient ubiquitous connectivity, the industrial Internet platform is a castle in the air, which is not used in the middle. Without the effective connection of a large number of on-site data sources (devices, sensors, various types of data acquisition devices and edge computing devices, etc.), there will be no real-time data flow, and no timely and timely data flow will be established. Industrial Internet There will be no new value streams and no new value chains.
The White Paper on the Connectivity Framework of Industrial IoT released by the American Industrial Internet Alliance IIC proposes the concept of the core standard of the connectivity framework layer, and selects four standards of DDS, OPC UA, HTTP and oneM2M from among many standards. The core standards cover almost all the requirements of ubiquitous connectivity in various industries.
At present, China has set off a boom in the development of the industrial Internet, but it has not paid enough attention to the connectivity of the Industrial Internet of Things IIoT, which is the main component of the industrial Internet. The current industry urgently needs to supplement this short board, otherwise it will be endless.
LED flag screen totem on light poles or Outdoor led screen kiosk, can save installation cost and time by pulling down and updating the printing advertising for light box. you can also unified management of intelligent management system. advertising can be really controlled,The Outdoor flat screen Is expected to become a large-scale media after as new carrier of advertising.
Small body, big world, It is not only small pixel pitch for led display, but a small era of led screen!
The flag LED display kiosk on each road poles, not only can realize the comprehensive utilization of road poles, making the road no longer monotonous, but also can play content according to different festivals and beauty the city. At the same time, it will also provide the public with weather changes, environmental pollution and road access. bring more convenience to the public.
Priva provides professional intelligent Led light pole screen solutions and professional commercial LED display technology With a wealth of LED project engineering experience, Priva Led will meet customer`s varity needs.
Integrated design, easy to use
Operate controller inside, Optional of installation on back column and side of pole, Easy to transport & install.
Intelligent management and Large scale cluster control and management. easy and convenient
Managing multiple displays via cable, 3G, 4G, WAN and LAN; Could manage by mobile phone with APP. 1-1 and 1-N management One click to release, timing, updating AD.
Outdoor Led Flag Screen Totem,Outdoor Led Flag Screen,Outdoor Flag Screen,Slim Outdoor Led Poster
Shenzhen Priva Tech Co., Ltd. , https://www.privaled.com