Specifications (issue 2)


This deliverable comprises the technical specifications of the CAMELOT systemin regards to the User Interface (UI), middleware, data model, and external interfaces that will allow the implementation of the consortium’s vision for the CAMELOT system. Firstly, the document starts by presenting the CAMELOT architecture and its baseline architecture, the STANAG 4817, to provide clarity to the reader on the generic framework adopted, which impacts directly the technical specifications presented in the following chapters. Following the description on the architectures, this deliverable presents the technical specifications of CAMELOT in descending order of the OSI layers, i.e.  starting from the UI and finishing in the lowest layer, the physical layer. Therefore, the first section, the CAMELOT UI, depicts a series of figures that illustrate the interface that enables the end-user to access information coming from the CAMELOT system and control the unmanned assets available at any given moment. Afterwards, the work performed by the consortium in the definition of an appropriate middleware solution is reported. Given the diverse background of the partners, several middleware solutions were proposed by each beneficiary and no consent was reached during the first discussions. In this sense, a middleware benchmark as performed, being the solutions under analysis DDS, ECOA, JAUS, Kafka, RabbitMQ with JSON, and ZeroMQ with Protocol Buffers. The CAMELOT data model structure is then presented. This data model departs from both the SAE UCS 3.4 and the EUCISE 2020 data model. The data structures of the CAMELOT data model are presented in Annex I.  External interfaces with the local Ground Control Stations (GCSs) and legacy systems (e.g. GNR’s SIVICC) are presented.  Concerning the legacy systems, the interface is done through an Application Programming Interface (API) Representational State Transfer (REST), by which the legacy system can receive and produce information, and consume CAMELOT services.