The IT services offered by I-FLY are grouped based on the main technologies used in them and on the potential use case they address in terms of detection of incidents on Critical Infrastructures, and/or collection, administration and management of data.

The deployment of the necessary components is done through capsules. These are understood to be a docker container that will contain the specific Service Component to each case, plus a series of components and general communication and configuration services. In general, each use case will require the execution of one or several capsules depending on the case and the hardware support where they are deployed.

The basic components of a standard capsule and its functionalities are:

Capsule:

Docker container built using the versatility that docker provides since its version 17.05 of "Multi-Stage build". Separate images of each of its components will be generated and imported as dependencies at the time of the capsule image construction. This procedure allow us to provide more maintainability and uniqueness of components.

Configuration XML:

The XML hosts information about the container, configuration parameters of the components it contains, and information needed for its deployment and life cycle management.

Inputs:

  • Streaming:
    Symbolizes the video inputs, one or more, that feed the analysis components. This is also considered to be the audio channel input if required.
  • Metadata:
    Certain capsules will need information from the analysis performed by other capsules or other data sources such as UAV telemetry, this will be the transmission channel of this information, for example, GPS data for geolocation.

Service Component:

Component where the solution is implemented to address specific needs and use cases.

Event / Alarm Publisher:

Component in charge of interpreting the results of the video and audio analysis and merging them. It will generate a message containing the necessary metadata to identify the detected risk event as well as a video sequence evidencing such fact.

API:

Each capsule implements an application programming interface where all communication methods will be exposed:
  • Standard API for exchanging information with third parties, metadata and video.
  • Metadata needed when there are several capsules that work cooperatively.