<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The exploitation of the COSMO-SkyMed Interoperability, Expandability, Multimission-Multisensor capabilities for the SIASGE System of Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Luca Fasano</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italian Space Agency Rome</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy luca.fasano@asi.it</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Giuseppe Francesco De Luca</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Italian Space Agency Rome</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2016</year>
      </pub-date>
      <abstract>
        <p>- COSMO-SkyMed is an Italian Earth Observation system born to cope with Dual-Use (i.e. military and civilian) and Multimission (MM)/Multisensor (MS) (SAR, Optical, …) requirements. Within this perspective, it is a highly innovative system capable to be expanded to other systems and sensors.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>SIASGE is a Space Earth Observation System set-up by an
international cooperation between Italy and Argentina for
complementary utilisation of COSMO-SkyMed and the
SAOCOM CONAE (Comisión Nacional de Actividades
Espaciales) Mission.</p>
      <p>This work describes how a system already in operation
(COSMO-SkyMed) can be used, thanks to its IEM
(Interoperability, Expandability, Multimission/Multisensor)
native capabilities, to form, jointly with a new-developed system
(SAOCOM), the complex SIASGE “System of Systems”.</p>
      <p>Keywords— SIASGE; COSMO-SkyMed; IEM; SAOCOM;
satellite; SAR</p>
      <p>I.</p>
      <p>INTRODUCTION</p>
      <p>Historically, Earth Observation (EO) missions have largely
been technology-driven. A promising idea for an instrument
design has often been the starting point for a satellite mission
specifically conceived to satisfy certain scientific requirements.
This situation has led to a high number of scattered facilities
each providing different specific, regional, thematic functions
such as near real time data production and distribution, off-line
archive and distribution, and added-value services with
complex data and information flows.</p>
      <p>This has created a high level of complexity for the users to
find and access the EO (Earth Observation) data, and an
infrastructural overcapacity in the basic data services with
operational and cost inefficiencies over such different EO
systems.</p>
      <p>SIASGE is a Space Earth Observation System set-up by an
international cooperation between Italy and Argentina for
complementary utilisation of the Italian Mission
COSMOSkyMed and the Argentinian Mission SAOCOM. It has the
main purpose of generating information on Risk Management
with synergetic observations with synthetic aperture radar
(SAR) operating in L- (SAOCOM) and X- (COSMO-SkyMed)
band.</p>
      <p>It’s the first time ever that an already in operation SAR dual
EO system, COSMO-SkyMed, is joint to a new other EO
system, SAOCOM, in an International “System of System”,
able to satisfy the two partners’ needs both with the two
mission single products and with joint products. This
collaborative system must continue to satisfy all the single
systems’ security requirements (also the Defense ones for
COSMO-SkyMed). It must not influence on the singles
systems’ performance, but has to take advantage of the analysis
and upgrades of the years of COSMO-SkyMed operative
phase, also in the Integrated Logistic and Operations fields.
Some other “System of Systems” initiatives have already been
implemented for Earth Observation missions, such as
Copernicus [1] and others will be implemented in the future,
such as EUMETSAT-NOAA Joint Polar System (JPS) [2].
They all aim to find a viable way to exploit both the systems’
capabilities and to provide cost-effective solutions, but they do
not deal with the Civilian part of a native dual and
multimission system or with a system already in operational
phase, so they not have to preserve some characteristics (es.
Security, previous performances, etc.). In this sense, SIASGE
is considered an innovative system.</p>
      <p>The main challenge of this work is to analyze all the
possible capabilities required by SIASGE system that can be
realized applying the COSMO-SkyMed IEM capabilities,
including some of “COSMO-SkyMed di Seconda
Generazione” (CSG) ones (external to the Memorandum of
Understanding, but however to keep into consideration).</p>
      <p>II.</p>
      <p>THE INVOLVED SYSTEMS
A.</p>
    </sec>
    <sec id="sec-2">
      <title>COSMO-SkyMed</title>
    </sec>
    <sec id="sec-3">
      <title>1) The Mission</title>
    </sec>
    <sec id="sec-4">
      <title>COSMO-SkyMed (COnstellation of small Satellites for</title>
    </sec>
    <sec id="sec-5">
      <title>Mediterranean basin Observation, CSK) [3] [4] is the largest</title>
      <p>Italian investment in Space Systems for Earth Observation,
commissioned and funded by Italian Space Agency (ASI) and
Ministry of Defence (MoD), and it is “natively” conceived as
a Dual-Use (Civilian and Defence). It is composed of a Space
•
•
•
•
•
•
•
•
Segment, a Ground Segment and an Integrated Logistics and
Operations Segment (ILS&amp;OPS).</p>
      <p>The system consists of a constellation of four Low Earth
Orbit mid-sized satellites, each equipped with a multi-mode
high-resolution Synthetic Aperture Radar (SAR) operating at
X-band and fitted with particularly flexible and innovative
data acquisition and transmission equipment. PFM (Prototype
Flight Model) was launched in 2007, FM4 (Flight Model n. 4)
in 2010 and today all satellites are in orbit and still in good
health [5].</p>
      <p>The set of requirements imposed at highest level has
brought to strict performances, in terms of:
daily acquired images,
Satellites worldwide accessibility,
All weather and Day/Night acquisition capabilities,
Image quality
Capability to be a cooperating, interoperable,
expandable to other EO missions</p>
      <p>Due to the need of many combinations between image size
and spatial resolution the SAR was chosen as a multimode
sensor operating in:</p>
      <p>A Spotlight mode, for metric resolutions over small
images
Two Stripmap modes, for metric resolutions over
tenth of km images; one mode is polarimetric with
images acquired in two polarizations
Two ScanSAR for medium to coarse (100 m)
resolution over large swath</p>
    </sec>
    <sec id="sec-6">
      <title>2) IEM key principles</title>
      <p>The “native” high versatility characteristics of
COSMOSkyMed led ASI and It-MoD to further promote these
characteristics, looking forward an actual multi-mission
architectural framework. This challenge envisages the
COSMO-SkyMed system capable to be integrated and
cooperating with heterogeneous Partner’s EO systems, in order
to plan multi-mission requests, and to exploit mission data
from heterogeneous EO sensors, thus also saving not only
operational costs, but development and integration as well.</p>
      <p>The IEM [6] [7] (Interoperability, Expandability,
MultiMission/Sensor) concept objective is hence to support
cooperation scenarios between COSMO-SkyMed System and
other EO systems.</p>
      <p>In general terms, “Interoperability” is the ability of two or
more elements to mutually exchange data, information, and
access to their provided services through specific "exported"
interfaces. COSMO-SkyMed provides a full set of capabilities
to interoperate with foreign systems, through a variety of
implementation solutions, ranging from “simple” exchange of
products (by means of ad hoc protocols), to plugging of
partner’s architectural elements into the COSMO-SkyMed
architecture to give local, autonomous, capabilities (ingestion,
production, etc).</p>
      <p>The “Expandability” is instead the ability of an architecture
to embody mission-specific components “imported” from
Partner’s EO System, thus designated as PFI (i.e. Partner’s
Furnished Items). The COSMO-SkyMed architecture is
designed to manage several PFI’s from different Partner’s
Systems, such as: Acquisition Chain, Processing Chain, and
Programming Chain, in order to locally achieve multi-mission
and multi-sensor capabilities. Reciprocally, COSMO
missionspecific components can be configured as PFI to be exported
towards Partner’s EO Systems. A clear specification of PFI’s
scope and interfaces constitute key issues for COSMO
architecture expandability feature.</p>
      <p>“Multisensoriality” is the generic ability to manage several
sensors, in terms of submission of related requests,
programming, and products delivery. Multisensoriality is
obtained by the concurrence of Management (the ability to
coordinate the monosensor capabilities) and Interoperability
(the ability of the monosensor capabilities to interact among
them). Multisensoriality can be reached through a procedural
approach or through an architectural approach.
COSMOSkyMed implements it through an architectural approach, i.e.
providing an environment (supported by H/W and S/W)
capable to provide multisensor services, with the objective to
increase Standardization, Effectiveness, Response Time,
Reproducibility, Reliability.</p>
    </sec>
    <sec id="sec-7">
      <title>3) Ground Segment</title>
      <p>The CSK Ground Segment is responsible for the
operations and control of the entire system including the
generation and dissemination of the final products. It is
composed of:
•
•
•
•
•
•
•
the Core Ground Segment, including Satellite control
facility, TT&amp;C, Internal Communication Network,
Flight Dynamics System
Mission Planning and Control Centre, including
Mission planning facility (CPCM)
Receiving, processing and archiving centres,
including Processing and archiving facility, Satellite
data receiving stations, Data exploitation, Calibration
&amp; validation, Data distribution
Communication infrastructure including Terrestrial
links
Remote Ground Stations, including External TT&amp;C
Network, Satellite data receiving stations
Mobile Acquisition and Processing Stations
Fiducial Network, which provides GPS ephemeris
and correction data necessary to improve precision in
Precise Orbit Determination (POD)</p>
      <p>An Integrated Logistics and Operations Segment
(ILS&amp;OPS) includes all necessary operations &amp; logistic
resources and services required for operating the Space
Segment throughout the whole system lifetime</p>
    </sec>
    <sec id="sec-8">
      <title>SAOCOM</title>
      <p>The SAOCOM [8] [9] CONAE Mission consists of two
satellites, flying in constellation, provided with a Polarimetric
Synthetic Aperture Radar in L Band (Polarimetric L Band
SAR). Its objectives are:
• provide all weather, day/night polarimetric L
band SAR information in real time/store mode,
the Ground Acquisition Stations: one located in
Cordoba and one provided by ASI in Italy
the Mission Operations Center (MOC) for Mission
Planning, Command encoding and routing, Telemetry
decoding and monitoring, Orbit determination and
maintenance
the Users’ Segment Services (CUSE), a portable User
Terminal
the Orbit Dynamics Service (CODS) for orbit
dynamic information useful for all other components
of the CONAE GS
III.</p>
      <p>RESULTS: THE EXPLOITATION OF COSMO-SKYMED</p>
      <p>IEM TO FORM SIASGE</p>
      <p>As above described, SIASGE is a system of systems aimed
to exploit the capabilities of the Italian COSMO-SkyMed and
Argentinian SAOCOM missions. It is composed by:
1) A percentage exploitation of the capabilities/services
belonging to COSMO-SkyMed and SAOCOM Systems in
agreement of predefined resource sharing policies;
2) A Common Ground Infrastructure deployed in
Argentina and in Italy, with the aim of:
interfacing SIASGE Users with capabilities outside
the already available ones
interfacing COSMO-SkyMed and SAOCOM, for
standard product requests and reception with
capabilities outside the already available ones;
generating, exploiting and distributing Joint Value
Added Products.</p>
      <p>In the following, a methodology to exploit the
COSMOSkyMed IEM in order to fulfil SIASGE requirements will be
described. Such a methodology can be summarized in two
main steps:</p>
      <p>Analyze the SIASGE mission requirements as for
Memorandum of Understanding between ASI and
CONAE
•
•
with high spatial resolution (10 –100 meters), and
with different incidence angles.
obtain specific L band SAR derived products,
obtain L band interferometric SAR derived
products, in particular DEM’s, terrain
displacement maps and forest features, which
represent a great help for the major applications
mentioned.</p>
      <p>The two satellites are planned to be launched starting from
2018 and they will be directly injected in a Sun Synchronous
(SSO) nearly-circular frozen orbit and will be able to acquire in
2 modalities: Stripmap and TOPS modes. The nominal orbital
position will be decided in order to form the more efficient
constellation taking into consideration also the four CSK
satellite.</p>
    </sec>
    <sec id="sec-9">
      <title>1) Ground Segment</title>
      <p>The Ground Segment for the SAOCOM Mission includes
the following multiple facilities:
2. Identify how to apply the IEM COSMO-SkyMed
capabilities (“IEM Portfolio”) to SIASGE</p>
      <p>These two steps will be separately detailed for Mission
(5.1) and Ground Segment (5.2) designs. For what concern the
algorithm generating Joint Value Added (X+L) Products, it
shall consist in a data fusion between CSK X-Band and
SAOCOM L-Band Products. The generation of CSK and
SAOCOM products involve the COSMO IEM Capabilities
and PFIs, as described below. The X+L Products generation
requires instead an ad-hoc developed algorithm, because it
takes as input the outputs of the two systems and no fusion
between different data is foreseen in CSK and SAOCOM
systems. Figure 1 shows the flow chart of the full analysis:
•
•
•
•
•
•
•</p>
      <p>Fig. 1: The research flow-chart</p>
    </sec>
    <sec id="sec-10">
      <title>A. The analysis on SIASGE Mission</title>
      <p>In this section the result of the mission analysis on SIASGE
are presented. Considering that the CSK satellites are already
in orbit (but some manoeuvres, if needed, would be possible),
the main impacts will be on the SAOCOM (and CSG) satellites</p>
    </sec>
    <sec id="sec-11">
      <title>1) The SIASGE Mission Requirements</title>
      <p>The SIASGE orbital requirements are, briefly:
1. A SAOCOM (or CSK) satellite shall pass after a
CSK (or SAOCOM) satellite after few minutes in
order to be able to identify fast changes on the
same zone with the same acquisition geometry
2. The manoeuvres on the CSK satellites (if needed)
shall take into account the residual propellant
3. The orbital configuration shall minimize the
collision risks among the satellites
4. The orbital configuration shall take into account
the SAOCOM launcher accuracies
5. The orbital configuration shall take into account</p>
      <p>CSG future launches</p>
    </sec>
    <sec id="sec-12">
      <title>2) The SIASGE Mission Design</title>
    </sec>
    <sec id="sec-13">
      <title>a) Inclination</title>
      <p>
        Both CSK and SAOCOM orbits are SSO [
        <xref ref-type="bibr" rid="ref3">10</xref>
        ]. Their
inclination can be subject, as other orbital parameters, to
natural changes caused by the oblateness of the Earth,
gravitational attraction from the Sun and Moon, solar radiation
pressure, and air drag (they are called "perturbing forces"). So
some compensation manoeuvres are necessary to maintain the
satellite in the same orbit; they are not needed if all the orbital
parameters are fixed in such a way to compensate the natural
perturbations.
      </p>
      <p>The CSK orbital parameters are already established and
applied in that way. Also the SAOCOM orbital Inclination
should be defined in order to minimize these manoeuvres (it is
a “gold value” very near to 98 degrees).</p>
    </sec>
    <sec id="sec-14">
      <title>b) True anomaly</title>
      <p>The SAOCOM True Anomaly would be defined in order to
avoid collision risks with CSK satellites and to satisfy the
needed SIASGE revisit time requirements, i.e. acquiring in the
same zone with the same acquisition geometry with the lowest
possible time gap. The better true anomaly at the time being is
shown in the next figure:</p>
      <p>It is worth to underline that CSK and SAOCOM satellites
are not on the same orbital plane.</p>
    </sec>
    <sec id="sec-15">
      <title>c) Right Ascension of the Ascending Node (RAAN)</title>
      <p>If we have a X+L images couple with a few minutes’ gap,
we can monitor every fast event (for example flooding) in a
more efficient way. So, a SAOCOM satellite will be able to
pass after a CSK satellites after few minutes on the same area
(or vice versa). The orbital parameter to be controlled is the
RAAN.</p>
      <p>A SAOCOM orbit RAAN very near to CSK one, doesn’t
increase collision risks, but requires a way to handle two
subsequent satellite passes on the common Ground Stations
(Matera and Cordoba). In fact, SAOCOM and CSK satellites
will share the same antennas in Matera and Cordoba. To handle
two subsequent passes, this Ground Stations can:
•
•
•</p>
      <p>Handle all the passages with a single antenna:
this antenna would be able to be
autoreconfigured in the time gap between the two
passages. It is requested to have few minutes
between two subsequent passages, so a
reconfiguration time too low and impossible to
realize would be necessary.</p>
      <p>Handle every mission with a dedicated
antenna: in this way we should have a
CSKdedicated and a SAOCOM-dedicated antennas.</p>
      <p>This solution is the easiest one and allow
(because there are several available compatible
antennas in Matera and Cordoba) to handle all
the passages also with a small gap.</p>
      <p>Have two (or more) antennas with an
automatic switching between the two
missions. In this way every single antenna would
be automatically reconfigured to handle a CSK
or SAOCOM pass. In addition to the previous
solution, in this way we can easily manage an
antenna failure.</p>
      <p>The last solution is obviously the best one, but the most
complex. So, it won’t be probably possible to implement it
before the SAOCOM first satellite’s launch. The proposed
solution is to adopt the second solution in the meanwhile, and,
when the implementation of the last possibility will be ready,
switch to it.</p>
      <p>Taking into account these considerations and adopting the
proposed solution, the SAOCOM RAAN could be defined in
order to have the desired gap with CSK one (this last one could
be different from the value at the launch because of
manoeuvres and a natural long term sinusoidal oscillation)</p>
      <p>The launcher accuracy: the mission analysis must
always consider the launcher accuracy to grant the
satellites safety;
2. SIASGE Mission requirements concern only CSK
and SAOCOM satellites (because it started several
years ago), not CSG ones (they will be launched in
2018 and 2019). The optimal “CSG only”
configuration (from time performance and
interferometric points of view) is being refined.</p>
      <p>The optimal CSK+CSG configuration will be
studied trading off the “CSG only” performance
and the overall constellation performances. The
possibility to simultaneously have in orbit CSK,
CSG and SAOCOM satellites is very realistic at
this point, so the CSK+CSG+SAOCOM
configuration must be studied. If the SAOCOM
satellites will be located in the position depicted in
Figure 2 and the “CSG only” configuration will
require 180° of delta True Anomaly, a possible
configuration could be the one in the next figure:</p>
    </sec>
    <sec id="sec-16">
      <title>B. The analysis on SIASGE Ground Segment</title>
    </sec>
    <sec id="sec-17">
      <title>1) The SIASGE GS Requirements</title>
      <p>
        In the planned solution, the following main functionalities
can be identified:
1. A User Care Layer in charge to “interpret” the
user requests, to submit to the Multisensor Layer
the related Programming Requests, to receive the
standard products, and to produce/deliver the joint
products (X+L) [
        <xref ref-type="bibr" rid="ref4">11</xref>
        ].
2. A Multisensor Layer in charge to take the
programming requests coming from the User Care
Layer for any sensor, and to dispatch the related
standard products to it. It also includes the
harmonization process.
3. “X+L” Product Layer, devoted to Multisensor
      </p>
      <p>Products generation
4. The Monosensors: it represents the capability at
monosensor level of programming, acquiring,
processing, dispatching the monosensor products.
It is mission specific and does not need any
modification
5. The Planning: because it is mission-specific, no
modifications are necessary
SIASGE
Common</p>
      <p>Ground
Infrastructure</p>
      <p>Not impacting
on this analysis
SIASGE Jointly
Developed Ground
Infrastructures
Constellation
control
Planning
Multisensor
management,
acquisition and
monosensor
products delivery
SIASGE SPECIFIC
PRODUCTS AND
CAPABILITIES</p>
      <p>USER CARE
Satellites
Constellation
control
Planning
USER</p>
      <p>S</p>
      <p>Multisensor management,
interoperability acquipsirtoiodnucatnsddmeliovneorsyensor
(reuse of COSMO if needed)</p>
      <p>SIASGE Reused</p>
      <p>Ground
Infrastructure
a) “COSMO-SkyMed di Seconda Generazione” IEM
improvements useful for SIASGE.</p>
      <p>
        “COSMO-SkyMed di Seconda Generazione” (CSG) [
        <xref ref-type="bibr" rid="ref5">12</xref>
        ]
[
        <xref ref-type="bibr" rid="ref6">13</xref>
        ] [
        <xref ref-type="bibr" rid="ref7">14</xref>
        ] [
        <xref ref-type="bibr" rid="ref8">15</xref>
        ] has been conceived at the twofold need of
ensuring operational continuity to the currently operating “first
generation” constellation, while achieving a generational step
ahead in terms of functionality and performances. CSG User
Ground Segment, in continuity with CSK architectural key
principles, is based on an interoperable and multi-mission
design.
      </p>
      <p>A subset of functionalities of the CSG User Ground
Segment is implemented in the MSI-UGS (Multi-Sensor
Interfacing User Ground Segment), representing the unique
front end of the final user and composed of the following CSG
Ground Segment subsystems and tools:
•
•
•
•
•</p>
      <p>Interface Management S/S (S-IM)
Production Management S/S (S-PM)
Remote Programming Functions S/S (S-RPF)
Network LAN, WAN and Network Services
(SNET)</p>
      <p>Logistic Tools</p>
      <p>The MSI-UGS is being integrated into First Generation
system in these months, several months before the launch of
the first CSG satellite, adding some new functionalities,
especially in the User Interface and in the IEM capabilities.</p>
      <p>IV. CSG S-IM</p>
      <p>The CSG Interface Manager (S-IM) subsystem shall
interface the CSK and CSG catalogues and potential catalogues
of further Mission GS supporting the same protocols and also
different ones (for example SAOCOM).</p>
      <p>For this reason, the catalogue plug-ins interface contains
the definition of a set of methods (Common Catalogue Service
Methods) needed to allow the overlapping of the functionalities
foreseen by the CSK and CSG Interoperability protocols and,
additionally, by the most common and standard Catalogue
Protocols (e.g.: OGC). In this way it is possible the integration
of a plug-in developed to interface catalogues supporting
services that this new plug-in manages as its own specialized
implementation of the Common Catalogue Service Methods.
The plug-in approach is used also to provide the access to
ordering services supporting different protocols. It is used to
interface the feasibility tools foreseen by CSG, CSK,
CSK+CSG and it is easily expandable to SAOCOM. The CSG
S-IM subsystem will interface the CSK and CSG feasibility
and check conflict functions and potentially feasibility and
check conflicts functions of foreign Mission GS supporting the
same protocols and also different ones. It’s important to state
that it could also be used to for SAOCOM feasibility with a
minor configuration. The same approach is used also for
harmonization management. The S-IM internal server shall be
able to manage the CSK and the CSG harmonization and
potentially harmonization of request for a foreign Mission GS.
Also for the expandability of the production and delivery
functionalities it is foreseen a common interface defining the
signatures and relevant parameters for the production and
delivery methods to be implemented by specialized plug-ins
according to the server to be interfaced. For all these reason,
the S-IM allows an important improvement of the
COSMOSkyMed IEM capabilities showing all the characteristics
needed by the SIASGE Multisensor Layer.</p>
    </sec>
    <sec id="sec-18">
      <title>b) User Care and Multisensor Layers</title>
      <p>The User Care is the layer needed to support users, with the
following functionalities:
technical information about the offered services
e.g. geographical coverage of zones in which is
allowed to order products and/or services,
technical characteristics and features of the
product generated by the system, type of data
needed to realize a Value Added product and so on
Commercial Information about the offered
services
Service Order information like status of orders,
percentage of completion and so on</p>
      <p>The Multisensor includes common functions to be used by
both components (Argentina+Italy) in order to guarantee the
interoperability between COSMO-SkyMed and SAOCOM.
The current baseline of the identified solution is to fully use the
multisensor capabilities of COSMO. Thanks to its native
characteristics, the COSMO-SkyMed MSI-UGS subsystem can
be used, with minor updates, to satisfy all the SIASGE
Multisensor needs, taking the programming requests coming
from the User Care Layer for any sensor, and dispatching the
related standard products to it.</p>
      <p>In fact, Multisensor Services in the current
COSMOSkyMed baseline encompass:
•
•
•
•
multi and monosensor Imagery Customer
Requests (ICR), programming request and Product
Delivery Request and mono-sensor product
elaboration request. The foreseen levels of
multisensors requests are:
o
coupled acquisition: the area has to be
imaged by both L-Band and X-band,
with respect of a maximum delay
condition between two radar
acquisitions,
o mixed acquisition: it is accepted that the
area is covered partly by L-Band and
partly by X-band, as long as the whole
area is covered.
visualization services designed as multi-sensor
services at multi sensor level, or mono sensor
level
deposit tools at multi sensor and at mono sensor
level. Whenever possible, the mono sensor level
information will be automatically proposed to the
deposit operator, according to the multi sensor
level information he has defined.
progress reports capable to manage multi-sensor
request status and provide feed-back to the
deposit operators.
raw data catalogue access through a multi-sensor
imagery request function. This means that a
single catalogue request, shall allow to browse
COSMO-SkyMed catalogue and SAOCOM
catalogue.</p>
      <p>Capability to issue product generation request
from either the multi-sensor level or from a
mono-sensor level.</p>
      <p>Access to catalogue of products through a
multisensor imagery request function.</p>
      <p>It’s also clear that the S-IM component can be configured
in order to constitute the SIASGE User Care Layer,
interpreting the User requests and sending the products to the
Users.</p>
    </sec>
    <sec id="sec-19">
      <title>c) The Monosensors</title>
      <p>The Monosensor represents the same capability at
monosensor level, i.e., it takes care to program, acquire,
process, dispatch the X and L products.</p>
      <p>CSK has followed an architectural interoperability
approach. It implements interoperability for specific UGS
functions (e.g. Programming Requests elaboration, science data
acquisition, processing) using architectural components of the
Partner UGS. As such, a SIASGE UGS encompasses "Partner
Furnished Items" (PFI) as monosensor components through
which it can perform the relevant functions of the Partner UGS
and can interact with it in given modalities.</p>
      <p>In details, COSMO-SkyMed IEM capabilities, several
CUTs (Commercial User Terminals - portable Ground
Segments with some functionalities simplified) have been
realized and nowadays are in different countries. A CUT can
be realized and moved in Cordoba, in order to allow the
CONAE system to directly request COSMO-SkyMed products
and receive them using the CUT antenna. In the same way a
SAOCOM CUSE can be moved in the Matera Space Centre to
allow COSMO-SkyMed system to download the SAOCOM
data using CUSE antenna in Matera. In this way both in
COSMO-SkyMed and SAOCOM User Ground Segments will
be possible to download the data of both the missions.</p>
    </sec>
    <sec id="sec-20">
      <title>d) Harmonization</title>
      <p>This COSMO-SkyMed harmonization capability can be
used to harmonize Italian and Argentinian requests at the
monosensor level, both in Matera (the harmonization
capability is already present in First Generation system and is
improved with Second Generation S-IM, so no modifications
are required) and in Cordoba (automatically starting from the
SIASGE Phase 2 (see 5.2.2.5)).</p>
    </sec>
    <sec id="sec-21">
      <title>e) A possible SIASGE architecture implementation</title>
      <p>For what concern the possible SIASGE architecture
implementation, only the User Ground Segments, the most
interested Centers, is detailed; the other Centers, for example
the CSK and SAOCOM External Stations (useful to maximize
the possible acquisitions per orbit and to reduce the System
Response Time) don’t show very interesting updates and are
not detailed in this work.</p>
      <p>Considering the time needed for the design,
implementation, test and validation of the
automaticallyswitching antennas, an ad-hoc scheduling is necessary (see
5.1.2.3). This scheduling allows to exchange the SAOCOM
and CSK data in very few time, and improving the SIASGE
User Services, also adding new ones, progressively.</p>
      <p>The scheduling can be divided into 3 phases:
a. the Interface between S-IM and the CSK
subsystems (CUT and I-CUGS) is automatic
by design
b. the interfaces between S-IM and the</p>
      <p>SAOCOM subsystems (CDAE+CUSE and
GS) is easy to be set, thanks to its CSK IEM
capabilities (the SAOCOM subsystems are
seen as PFI).</p>
      <p>This work describes how the SIASGE User Requirements
can be satisfied using COSMO-SkyMed native IEM
capabilities jointly with SAOCOM system. The analysis has
taken into account the fact that COSMO-SkyMed is an already
in operation dual EO system with performances and security
constraints to be continuously granted. In this work almost all
the SIASGE functionalities are described; some other required
capabilities, for example the X+L joint products, are not
detailed because they requires an ad-hoc algorithmic analysis
not involving the CSK IEM capabilities and they won’t use any
COSMO-SkyMed PFI (main topic of this work). This residual
functionalities can be object of future works.
F. Caltagirone, A. Capuzi, A. Coletta, G. F. De Luca, The
COSMOSkyMed Dual Use Earth Observation Program: Development,
Qualification, and Results of the Commissioning of the Overall
Constellation, IEEE Journal of Selected Topics in Applied Earth
Observations and Remote Sensing ( Volume: 7, Issue: 7, July 2014 )
L. Fasano, M. Cardone, R. Loizzo, M. L. Battagliere, G. F. De Luca,
“MCO strategies and actions to successfully increase the life of both
Ground Segment and Space Segment”, IGARSS 2016, Pechino
SAOCOM,
http://www.conae.gov.ar/index.php/english/satellitemissions/saocom/technical-characteristics</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <given-names>P.P.</given-names>
            <surname>Mathieu</surname>
          </string-name>
          et al.,
          <source>The ESA's Earth Observation Open Science Program (Space Agencies)</source>
          ,
          <source>IEEE Geoscience and Remote Sensing Magazine (Volume: 5</source>
          , Issue: 2,
          <year>June 2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>G. F. De Luca</surname>
          </string-name>
          , G. Rum,
          <string-name>
            <surname>P. M. De Carlo</surname>
            , G. Marano, G. Angino,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Piemontese</surname>
          </string-name>
          ,
          <string-name>
            <surname>COSMO-SkyMed</surname>
            <given-names>Interoperability</given-names>
          </string-name>
          ,
          <article-title>Expandability and Multi-Sensor capabilities: the keys for full multi-mission spectrum operations</article-title>
          , SCI-150
          <string-name>
            <surname>Symposium</surname>
          </string-name>
          , Colorado,
          <fpage>10</fpage>
          -
          <lpage>12</lpage>
          October 2005
          <string-name>
            <given-names>D.</given-names>
            <surname>Giudici</surname>
          </string-name>
          et al.,
          <article-title>Roll-steering for improving SAOCOM-SAR performances</article-title>
          , Radar Conference,
          <year>2010</year>
          IEEE
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>A.</given-names>
            <surname>Ciccolella</surname>
          </string-name>
          ,
          <article-title>Mission Analysis aspects for Earth Observations missions</article-title>
          , Summer School of Alpbach
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [11]
          <string-name>
            <surname>John</surname>
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Curlander</surname>
          </string-name>
          ,
          <source>Synthetic Aperture Radar: Systems and Signal Processing</source>
          , Wiley-Interscience
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [12]
          <string-name>
            <surname>COSMO-SkyMed di Seconda Generazione</surname>
          </string-name>
          , https://directory.eoportal.org/web/eoportal/satellite-missions/cmissions/cosmo-skymed-second-generation
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [13]
          <string-name>
            <surname>G. F. De Luca</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <string-name>
            <surname>Valentini</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Fasano</surname>
            ,
            <given-names>C. A. M.</given-names>
          </string-name>
          <string-name>
            <surname>Fiorentino</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Porfilio</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Scopa</surname>
          </string-name>
          , S. Serva, “
          <article-title>The Capability of COSMO-SkyMed di Seconda Generazione to Support Cooperation Scenarios with Other Earth Observation Systems”</article-title>
          , 14th International Conference on Space Operations, Daejeon, Korea,
          <fpage>16</fpage>
          -
          <lpage>20</lpage>
          May 2016
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>G.</given-names>
            <surname>Casonato</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Caltagirone</surname>
          </string-name>
          ,
          <string-name>
            <surname>G. F. De Luca</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Covello</surname>
            ,
            <given-names>C. A. M.</given-names>
          </string-name>
          <string-name>
            <surname>Fiorentino</surname>
          </string-name>
          , et al.,
          <article-title>“COSMO-SkyMed di Seconda Generazione” development status and prospects relevant to Interoperability, Expandability and Multi Mission/Multi Sensor Capabilities”</article-title>
          ,
          <source>IAC 2012</source>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>G.</given-names>
            <surname>Valentini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Scopa</surname>
          </string-name>
          ,
          <string-name>
            <surname>G. F. De Luca</surname>
          </string-name>
          ,
          <article-title>COSMO-Skymed di Seconda generazione system access portfolio</article-title>
          ,
          <source>Geoscience and Remote Sensing Symposium (IGARSS)</source>
          ,
          <year>2016</year>
          IEEE International.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>