Integration of Cloud Computing with Internet of Things. Группа авторов
Читать онлайн книгу.
to understand and reason on sensor-related human’s activities for effective dynamic environments. The use of SI remains vital for adequate representation and integration of huge amounts of data arrived from different IoT sources for their effective utilization. The information extracted semantically from high-level abstractions or data can provide a potential solution to reduce the heterogeneity in a shared or common IoT platform. The Semantic Interoperability (SI) assisted by the SW to facilitate consolidated technologies, standards, and languages by providing data as well as IoT platform interoperability. With an ever increasing demand in applications and their developments, the use of semantic interoperability in IOT domain remains significant and essential for its success. With many different smart technologies, the SI integration costs are likely to rise and the system becomes complex. Nevertheless, with thousands of potential data sources, application areas, industries, and customers, a smart city can be smarter with the combination, cross-compilation, and re-utilization of data generated by individual applications using SI. The intersection of different IoT visions is shown in Figure 1.10.
Figure 1.9 The steps of SIoT (SEG 3.0 methodology) [27].
A generalized SIoT architecture is shown in Figure 1.11.
It is not enough to gather data but requires an ability to convert or process the available data into fruitful decisions or information that can provide an edge in SI. For instance, if someone was to call an end-user on their phone and speak in London, most users would probably not be able to communicate or achieve a meaningful result. The same issue occurs in communication between things when they use implementation-specific data models.
Figure 1.10 Intersection of different IoT visions [2].
Figure 1.11 A generalized architecture of including semantics.
1.5.1 Standardization Using oneM2M
Many companies are still trying to gain a better understanding of how blending robotics, interconnected devices/systems, and convergent hybrid infrastructure, together with edge and cloud/data center compute, can improve productivity and reduce costs in the long run. Add different vendors’ technology to the mix and a very complicated picture is painted.
Working to reduce this complexity is oneM2M, a global standard that hides technology complexities for IoT application developers through an abstraction layer, and a wide area network perspective. Its areas of expertise extend to the industrial sector, with several completed Technical Reports (TRs) and work in progress dedicated to this area. TR-0018 Industrial Domain Enablement, for example, maps out several use cases relating to Industry 4.0 development and the potential requirements which need to be addressed to ensure M2M communications truly enhance operations. Based on industrial domain research carried out, the document highlights the need to develop an accepted strategy to implement Industry 4.0 as a means of accelerating the update of manufacturing systems that many global organizations have started to invest in. Other completed projects dedicated to tackling the challenges of Industry 4.0 include TR-0027 Data Distribution Services usage in oneM2M and TR-0043 Modbus Interworking. Meanwhile, work is continuing on TR-0049 Industrial Domain Information Mapping & Semantics Support around proximal– distal interworking. Further support for industrial IoT applications is also expected to come when oneM2M publishes Release 3 later this year. OneM2M also collaborates on a wider scale with other industry bodies on a wide range of projects. In its TR-0018 Industrial Domain Enablement report, oneM2M referenced several organizations and industry bodies with relevant activities in the area, including the Industrial Internet Consortium (IIC) and Platform Industrie 4.0 and their respective reference architectures including IIRS and RAMI 4.0. Cooperation with the IIC is already advancing through joint workshops and a oneM2M testbed. Cooperation with Platform Industrie 4.0, the central alliance for the coordination of the digital structural transition in Germany, which includes stakeholders from businesses, associations, trade unions, and academia, is another important alignment of technologies and concepts in the industrial domain, especially as the PI4.0 concept of an Asset Administration shell and the oneM2M CSE are so complementary. OneM2M has incorporated results from Plattform Industrie 4.0’s Reference Architecture Model, Industrie 4.0 (RAMI 4.0), into the TR-0018 Industrial Domain Enablement report. RAMI 4.0 provides a conceptual superstructure for organizational aspects of Industry 4.0, emphasizing collaboration infrastructures, and communication structures. It also introduces the concept of an asset administration shell that incorporates detailed questions on key topics such as semantic standards, technical integration, and security challenges. OneM2M’s joint work with key transformative actors develops and delivers workshops, testbeds, and reports, along with its unique asset. The concept of a service layer on top of a connectivity layer—contributes significantly to the overall Industry 4.0 framework and industrial internet as a whole, ushering in a new wave of digitalization which will mark the beginning of Industry 4.0.
SI has been introduced in the latest specification of oneM2M standard Release 2 [Swetina]. It allows the posting, distribution, and reuse of meta-tagged data through a gateway by providing timely notifications to interested clients or entities available in semantic discovery.
OneM2M acts as a software middle layer, by interconnecting devices with their respective application–infrastructure entities (cloud-based), independently from their underlying transport networks. In effect, it creates an abstraction layer that allows application developers to create value from their business and operational applications without having to deal with the technical protocols for connecting to and managing devices. The standard solves the problem of implementation variances for common service functions. Its technical specifications provide a global standard for the basic functions, such as device management, security, registration, and so forth. The use of oneM2M specifications in field-deployed devices ensures data and vendor interoperability. Furthermore, oneM2M provides global standardized APIs on the application-infrastructure side, where customers can interact with their device and/or even their platform. On the device side, oneM2M’s APIs help developers tailor applications for their specific purpose without the need to master technical details about the underlying connectivity networks. To enable end-to-end communication across different verticals, oneM2M provides the tools that enable various interworking possibilities. One approach is to map data models for shop-floor machines and sensors as oneM2M resource structures and vice versa. Since such inter-working definitions are available for other verticals, such as automotive and rail, different verticals can communicate with each other relatively easily. The primary aim of oneM2M is to standardize the common services necessary to deploy and operationally support IoT applications across multiple verticals. This implies a horizontal focus, aiming for a high degree of reuse and cross-silo interoperability. Vertical sector requirements are also important to oneM2M standardization participants. In the manufacturing and industrial sectors, oneM2M established a liaison with the Industrial Internet Consortium. OneM2M is also actively involved with the Open Connectivity Foundation, targeting interworking opportunities for consumer IoT applications. OneM2M’s standardization continues to address new frontiers for interoperability and interworking with the development of its latest specifications, Release 4. Release 4 will encompass industrial, vehicular, and fog/edge architectures. It also lays the groundwork for semantic interoperability and tools to help user adoption.
We all know that SIoT is taking place in modern applications for industries and is developing very fast making analytics crucial to ensure security. Since the SIoT analytics operates using the cloud and electronic instrumentation, it requires programmers to control and access IoT data. IT professionals approaching IoT analytics should capture data via packets in automated workloads, also known as flow. Flow is the sharing of packets with the for example, if you stream a video on the internet, packets are sent from the server to your