Satellite-based Messaging Uplink for In-Situ Sensors Specification (D4.1)

By Pau Costa Foundation on

This deliverable presents the specification for the satellite based uplink for in-situ sensor data. The main task contributing to this deliverable is Task 4.1 (Satellite-based uplink for in- situ sensor data) which started in month 7 and is planned to finish in month 24. The main motivation behind introducing a satellite link to interface sensor networks to the service platform is to be found in the additional resilience that such a link would provide, and the strategic relevance that this represents in a context such as PHAROS.

The objectives of task 4.1 are drawn as follows:

  • Review the F-SIM standard, in particular the parts that deal with the random access return link, according to the requirement of the PHAROS applications.
  • Realise and evaluate a data interface between the terrestrial FireWatch system and the prototype satellite terminal. To do this, a deep understanding of the FireWatch as selected in-situ sensor network to be used during the PHAROS short term approach has been necessary.
  • Implement the required adaptations at the satellite prototype terminal as well as at the hub.
  • Identify CAPEX and OPEX.

The work performed to specify the PHAROS overall system architecture, described in D2.9 [1], the set of requirements and the system engineering process documented in D2.5 [2] have been used as a basis for the present deliverable. Moreover, the outcome of the Advisory Board (AB) and end user workshop held in Barcelona, in October 2014, has highlighted two important things that have taken into account for preparing the document: (i) the importance of providing a system able to integrate different available sensor networks, (the importance of meteorological data was highlighted) which has led to broaden the discussion within the task and extend it to analyse the scenario from a higher level perspective which included different sensor networks and (ii) the possibility of using communication systems alternative to the satellite one on which the task is focused that may be possibly considered for the long term approach.

Additionally, during the first discussions which took place at the beginning of the task, it was decided by the involved partners (in Task 4.1 as well as in Task 2.2 – Service sustainability and business plan) not to document the identified CAPEX and OPEX in the current deliverable, but to include them in D2.2 [3] (draft) and D2.3 [4] (final version). The rationale behind this decision is the fact that the overall analysis of the CAPEX and OPEX for the whole system and for each of its modules is planned to be carried out within the context of Task 2.2 and must be documented in the Task 2.2-related documents. Therefore, to avoid duplication of this information, it seems to be reasonable to perform the complete analysis in a unique document where all related information can be found, rather than providing an independent section within this document. This decision does not have any impact in the  time and working plan, since both activities run in parallel and the submission of the deliverables related to each of them is planned for the same point in time.

Login or register to download this file