BB24.C Application Layer Protocols and Cloud Architectures

From its-wiki.no

Revision as of 17:41, 13 July 2017 by Josef.Noll (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Title Application Layer Protocols and Cloud Architectures
Page Title BB24.C Application Layer Protocols and Cloud Architectures
Technology Line Distributed Cloud Integration
Lead partner INTEGRA
Leader Pedro Ruiz
Contributors Telenor, PRE, RTE, VTT, VEMCO
Related to Use Cases SCOTT:WP8, SCOTT:WP9, SCOTT:WP11, SCOTT:WP15, SCOTT:WP17, SCOTT:WP10
Description Application layer protocols (e.g. SOAP, REST, CoAP, MQTT, etc.) and versatile cloud architectures. Versatile cloud architectures provide a dynamic service based architecture servicing networked control systems (NCS). An infrastructure adaptable to various application areas (such as industrial automation), providing support for fault tolerant, safe, secure and dynamic resource systems. The architecture must provide centralized but also local information processing. Potentially concurrent local sub-structures should be able to operate and be maintained independently.
Main output Guideline on suitable application layer protocols in SCOTT for cloud communication. Readers of this guideline should be able to select the appropriate protocol according to their needs (e.g. resource-constraint nodes, access to specific cloud interfaces, etc.). The main focus is to re- use existing and standardized protocols as much as possible and to develop extensions where needed for the specific SCOTT domains.
BB category Interface, Means for establishing cross-domain interoperability
Baseline Baseline of this building block are standardized application layer protocols from IETF, OMG, OASIS, etc. as well as utilized protocols in the DEWI project (DEWI bubble level 1 and 2 interconnectivity)
Current TRL 3-4 (although established protocols may be used as a basis, the specific application for SCOTT domains is still unproven)
Target TRL 6 (verification of suitable/extended protocols in several SCOTT use cases)