CommLedgeNavigating IoT Architectures and Standards Days
The event has included keynotes, plenary and expert workshop sessions bringing answers to what has been achieved and what remains to be done by the IoT and DEI Large-Scale Pilots Programme funded under Horizon 2020.
The workshop has be an opportunity to discuss and challenge the guidelines and recommendations that STF 547 has developed in 7 Technical Reports (including Teaching Material on privacy and security).
On the first day (19 February ), the work has been centred around the outcome of ETSI’s STF 547: work done, lessons learned and key elements.
The successful development and deployment of IoT solutions relies on multi-dimensional IoT reference architectures that address the different functional layers, the cross-cutting functions and system properties. These include the requirements for data and device security, device discovery, provisioning and management, data normalization, analytics, and services.
The IoT reference architectures are key for standardization, as they define guidelines that can be used when planning the implementation of IoT systems in order to address the complexity of IoT solutions and ensure trustworthy, secure, scalable, interoperable IoT deployments.
· How can privacy regulation be supported by standards
· Is there anything specific to IoT regarding security?
· How to enable a wider adoption of semantic interoperability in various industry sectors?
· Are there available standardised platforms that can reduce the role of proprietary platforms in the development of new IoT systems?
On the second day (20 February), the work has been centred around the handover of common activities from the IoT LSP cluster (including CREATE-IoT) to the DEI LSP Cluster, enabling to capitalise on the experience built-up and ensure continuation of work on the gaps identified in the new projects cluster and the AIOTI working groups.
During the last day (21 February), the discussion has outlined how the development and the adoption of IoT standards is facing important issues related in particular to privacy, security, semantic interoperability or the availability of standardised platforms.
The workshop has be an opportunity to discuss and challenge the guidelines and recommendations that STF 547 has developed in 7 Technical Reports (including Teaching Material on privacy and security).
On the first day (19 February ), the work has been centred around the outcome of ETSI’s STF 547: work done, lessons learned and key elements.
The successful development and deployment of IoT solutions relies on multi-dimensional IoT reference architectures that address the different functional layers, the cross-cutting functions and system properties. These include the requirements for data and device security, device discovery, provisioning and management, data normalization, analytics, and services.
The IoT reference architectures are key for standardization, as they define guidelines that can be used when planning the implementation of IoT systems in order to address the complexity of IoT solutions and ensure trustworthy, secure, scalable, interoperable IoT deployments.
· How can privacy regulation be supported by standards
· Is there anything specific to IoT regarding security?
· How to enable a wider adoption of semantic interoperability in various industry sectors?
· Are there available standardised platforms that can reduce the role of proprietary platforms in the development of new IoT systems?
On the second day (20 February), the work has been centred around the handover of common activities from the IoT LSP cluster (including CREATE-IoT) to the DEI LSP Cluster, enabling to capitalise on the experience built-up and ensure continuation of work on the gaps identified in the new projects cluster and the AIOTI working groups.
During the last day (21 February), the discussion has outlined how the development and the adoption of IoT standards is facing important issues related in particular to privacy, security, semantic interoperability or the availability of standardised platforms.