EDRS (European Data Relay Satellite) Constellation
EDRS is an ESA project within the ARTES-7 (Advanced Research in Telecommunications Systems) program, a constellation of two geostationary data relay satellites, intended to provide links to satellites in LEO , and possibly other spacecraft, enabling real-time communications between these spacecraft and their respective Control Center.
ESA initiated already a precursor data-relay oriented program with the development and launch of Artemis in 2001. Artemis has demonstrated the many operational and performance benefits that the availability of a data-relay satellite offers. In the meantime, the demand for real-time high volume files is expected to increase dramatically with the beginning of operation of the Copernicus (formerly GMES) Sentinel system and future Earth observation and other missions. At the same time, the capacity of optical intersatellite links and their reduction in terms of mass and power requirements have jumped forward by at least one order of magnitude, as also radio systems have improved.
The EDRS program aims to create a new type of satellite services. It intends to bring the development and implementation of the system to a sufficiently mature stage, so that the resulting services can be provided by a satellite operator on a commercial basis. 1) 2)
Figure 1: Artist's rendition of the EDRS constellation architecture (image credit: ESA)
Legend to Figure 1: Various LEO spacecraft optically uplink their data to GEO stations which feed the data via conventional Ka-band links to the ground segment.
There are a number of key services that will benefit from this systems infrastructure right from the start:
• Earth Observation applications in support of a multitude of time-critical services, e.g. monitoring of land-surface motion risks, forest fires, floods and sea ice zones
• Government and security services that need images from key European space systems such as the Copernicus (formerly GMES) program
• Rescue teams that need Earth observation data in disaster areas
• Security forces that transmit data to Earth observation satellites, aircraft and unmanned aerial observation vehicles, to reconfigure such systems in real time
• Relief forces that operate among their units in the field and require telecommunication support in cut-off areas.
With the implementation of the joint European Commission/ESA Copernicus program, it is estimated that the European space telecommunications infrastructure will need to transmit a few TB (terabyte) of data every day from space to ground. The present telecommunications infrastructure is challenged to deliver such large data quantities quickly, and conventional means of communication may not be sufficient to satisfy the quality of service required by users of Earth observation data. 3)
To fulfil that demand, EDRS will become the first operational European data relay system (Figure 1) aiming at improving the quality of the data service and thereby enhancing the operational reliability and independence of European and Canadian space infrastructures such as the joint European Commission / ESA Copernicus initiative, and many national space assets. In particular, the objectives of ESA's EDRS program are:
• Provide ESA with the necessary data relay and related services via satellite. The Copernicus program will be the first customer of the EDRS service (Sentinel 1A/B and 2A/B LEO satellites). Hence, priority is currently given to the provision of services to the Copernicus/Sentinel users, given the fact that their needs are more mature and the associated timing is defined. However, the long-term objective for the EDRS program is to provide full and global data relay services to user communities related to ESA and partners of ESA.
• Foster the development of the satellite data relay services market through the exploitation of the infrastructure with commercial / institutional users beyond ESA.
• Support the standardization and adoption of optical and Ka-band data relay technology by means of the availability of technological solutions for the EDRS infrastructure as well as for the user community (Earth observation satellites, UAVs, etc.).
• Achieve a cost efficient program through a PPP (Public Private Partnership) scheme with satellite operators / service providers for the development of the infrastructure.
Unlike other ESA programs, the objective of EDRS is to develop a commercially sustainable data relay service, rather than developing only the necessary technical infrastructure (satellite and/or ground segment). Consequently, support to the adoption of EDRS by users beyond Copernicus is an important element of the program.
Events/milestones on the way toward EDRS realization:
• ESA approved the program in November 2008 following a strong push from Germany, which is the lead investor (50% share). After more than two years of negotiations, the governments of Europe have secured the full funding package for ESA to build a data-relay satellite system whose initial customer will be the European Commission's (EC's) Earth observation program.
• In October 2010, ESA selected Astrium GmbH (Business Unit Services) as the prime contractor and operator of the EDRS (European Data Relay System) consortium that will make these services available for the GMES (Global Monitoring for Environment and Security) program.
• In January 2011, final approval for the program was given by the Joint Communication Board, based on the mission technical baseline negotiated between ESA and Astrium, and on the funding from the Participating States. In the PPP concept, Astrium Services will operate the EDRS as a profit-making business, once the system is launched. The EC (European Commission) will be Astrium's anchor tenant, but the company will be free to seek other customers as well. 4) 5)
• In particular, ESA has selected Astrium Services to manage the development and operations of EDRS that would feature one dedicated satellite (EDRS-C) and one hosted payload (EDRS-A). Both of them will be positioned in the geostationary orbit with visibility over central Europe.
The EDRS system will be implemented in a so-called PPP (Public-Private Partnership) arrangement, an innovative structure in which ESA leads the creation of the initial system and infrastructure that is later taken over for full exploitation and further development by a commercial partner. EDRS will boost European-developed technology and make use of a cutting-edge intersatellite laser communication system as well as new data dissemination infrastructure on the ground. 6)
• On Oct. 3, 2011, ESA/TIA (Telecommunications & Integrated Applications) and Astrium Services signed a PPP contract in Paris for the development of the EDRS system. Under the terms of the agreement the partners will jointly finance the EDRS. With EDRS services starting in 2014, all suitably equipped future European Earth observation satellites will be able to perform quicker data transfers and transmit for longer periods. Astrium has the overall responsibility for designing and developing the complete space and ground infrastructure. Astrium will then acquire ownership of EDRS and is committed to its operation for the next 15 years. 7)
• On June 25, 2012, DLR, Astrium Satellites (prime contractor to ESA) and SES Astra TechCom S.A. (Luxemburg) signed contracts for large parts of the ground segment of the new EDRS. DLR has been appointed as a subcontractor by Astrium and is responsible for constructing large parts of the ground segment and for controlling the payloads on the first satellites, referred to as EDRS-A. DLR will also manage and control the EDRS-C relay satellites during routine flight operations that will last for at least 15 years. For this purpose, a dedicated EDRS control center will be developed within DLR's GSOC. The two geostationary relay satellites will transmit the data collected by the lower-orbiting Earth observation satellites to a total of four receiver antennas, which will be located on the sites of the existing ground stations at Weilheim (DLR) and Redu (Belgium), and at Harwell (United Kingdom). SES TechCom S.A. will supply the four antennas and will operate the antenna at Redu on behalf of DLR. 8) 9) 10) 11)
• The SRR (System Requirements Review) has been closed-out in July 2012. In parallel the EDRS-A PDR (Preliminary Design Review) has been successfully completed in April 2012.
• November 2012: The design of Europe's data relay satellite system – EDRS - has been completed and approved. This marks the moment when it moves ahead with a green light from its first customer, the GMES (Global Monitoring for Environment and Security) initiative from the European Union. A design review board of senior members from ESA, Astrium and the DLR German Aerospace Center approved the entire system design: from the satellites to the support that will be required from the ground. 12)
• May 2013: OHB System AG and Astrium GmbH signed the final contract for the delivery of a satellite for the upcoming EDRS (European Data Relay Satellite System). The EDRS-C satellite, which is now being developed and built by OHB System, thus forms part of a constellation of geostationary satellites which will be receiving data from LEO satellites and transmitting it to the Earth. EDRS-C is being assembled on the basis of the SmallGEO platform, currently under development at OHB System under ESA's ARTES 11 program. 13)
• Delivery of the EDRS-A / EDRS-C payloads to corresponding satellite integrators is scheduled for the end of 2013 and for mid-2014, with a satellite launch planned for the end of 2014 and early 2016, respectively.
• October 29, 2014: The first component of Europe's space data highway passed several critical tests this summer replicating the harsh launch and space conditions it will soon have to endure. EDRS-A, consists of three hosted packages on the Eutelsat-9B satellite for launch next year. 14)
- The first is a laser terminal capable of receiving 1.8 Gbit/s of user data from a satellite up to 45 000 km away.
- EDRS-A also carries a radio terminal that will handle up to 300 Mbit/s – a vast improvement over today's systems.
- The third package is an ‘opportunity payload' funded by Italy's ASI space agency operating independently of EDRS to provide broadcasting services over Italy.
The EDRS Space Data Highway is a commercially operated data relay system created as a PPP (Public–Private Partnership) between ESA and Airbus DS. As prime contractor, the company will build, operate and co-fund the infrastructure, as well as providing the data transmission services to ESA and customers worldwide. DLR (German Space Agency) also plays a key role in the funding of EDRS and in the development and the operation of the ground segment. 50 companies in 13 European countries are involved in the EDRS consortium, allowing European space industry to stay at cutting edge of technology.
• February 2015: Following the recent decision confirming the ESA/Airbus DS partnership on the EDRS, agreement has been reached with the European Commission (EC) for the provision of EDRS services to the European Union Copernicus program. 15)
- Subsequently, ESA and Airbus DS have signed a service level agreement on 20 February 2015 to provide high-speed communications to the Copernicus Sentinel-1 and -2 dedicated missions, starting in 2015 until 2021, with an option for extension until 2028.
At the same occasion, ESA and Airbus DS also signed a service contract providing data relay capacity to other ESA and ESA partner missions in the future. As a first additional user, ESA's Columbus module on the ISS (International Space Station) is planned to be provided with data relay services starting in 2018, which will support scientific experiments and enhance communication services to the astronauts on board the ISS.
• October 2015: EDRS-A Payload has been integrated with the spacecraft and passed successfully all tests on payload and satellite level. The satellite is now ready for launch (Ref. 31).
Figure 2: Photo of the EutelSat-9B/EDRS-A satellite in Toulouse prior to shippment (image credit: ESA, Airbus DS)
• December 9, 2015: After a year-long wait in storage for a Proton rocket to become available, the EDRS-A laser communications payload and its Eutelsat host satellite are finally at the Baikonur Cosmodrome and being prepared for launch in late January 2016. EDRS-A was packed into an Antonov plane by Airbus Toulouse, France and flown to Kazakhstan in November. 16)
- The Eutelsat-9B/EDRS-A satellite has undergone a plethora of tests to make sure it is space-ready after its launch and mission. EDRS-A's laser terminal is essentially an autonomous state-of-the-art telescope, with mirrors to help the laser lock on to its mark in lower orbits from its own position in geostationary orbit. The moving target can be up to 45 000 km away and requires an astonishing level of precision to hit. Extreme precision requires absolute cleanliness before EDRS-A reaches orbit – any grime or speck of dust can affect the terminal's mirrors and ability to pinpoint its target.
- Laser beams are capable of higher accuracy and capacity than radio – up to a record-breaking 1.8 Gbit/s of user data. The terminal is also fitted with a Ka-band radio transmitter to deliver the data to a ground station. The radio downlink is an important part of EDRS's services. Like the laser element, it is a two-way link that helps EDRS customers to send commands to their satellites.
Figure 3: Artist's view of the Eutelsat-9B / EDRS-A (image credit: Airbus DS)
Launch: The EDRS-A payload was launched on January 29, 2016 (22:20:08 UTC) as a hosted payload on the Eutelsat- 9B communication satellite (total launch mass of 5300 kg). The launch vehicle was the Proton-M/Briz-M of Khrunichev, ILS (International Launch Services) the launch provider, and the launch site was the Baikonur Cosmodrome, Kazakhstan. 17) 18) 19) 20)
Orbit: Geostationary orbit, altitude = 35,876 km, location = 9ºE.
Launch: A launch of the EDRS-C spacecraft, based on the SmallGEO platform of OHB Systems AG, is planned for Q1 2017. EDRS-C will also carry Avanti's HYLAS-3 telecommunications payload.
On March 19, 2015, Arianespace and Airbus Defence and Space reached an agreement for the launch of EDRS-C on Ariane-5 for Q1 2017 from Kourou. 21)
Orbit: Geostationary orbit, altitude = 35,876 km, location = 31ºE.
• November 23. 2016: EDRS (European Data Relay System) began servicing Europe's Earth observing Copernicus program yesterday, transferring observations in quasi-real time using cutting-edge laser technology. 22) 23)
- The EDRS–SpaceDataHighway will now begin providing a commercial service to the European Commission's Copernicus Sentinels – the first and only of its kind. EDRS is a public–private partnership between ESA and Airbus Defence and Space, with ESA supporting the initial technology development and the company providing the commercial service. The European Commission is EDRS's anchor customer through its Sentinel-1 and -2 missions.
- EDRS accelerates the transmission of data from low-orbiting satellites like the Sentinels to the end user on the ground. It does so by locking onto the satellites with a laser beam as they pass below, and immediately relaying the information to European ground stations via a high-speed radio beam.
- Low-orbiting satellites must usually wait until they travel within view of a ground station to downlink the data they have gathered, resulting in a delay of up to 90 minutes per 100-minute orbit. This is because most ground stations that serve low-orbiting satellites are located in the polar regions, although the Sentinels have additional stations in Italy and Spain.
- Nevertheless, Earth observation satellite data are increasingly being used for time-sensitive applications like disaster response, maritime surveillance and security, where speed is of the essence.
- EDRS will help to solve this problem. As the world's first optical satellite communication network in ‘geostationary' orbit – where satellites takes 24hr to circle Earth and thus appear to ‘hang' in the sky – it will relay unprecedented amounts of potentially life-saving data per day in near-real time.
- The EDRS-A first node will now start collecting data from Sentinel-1A. The two satellites will link via laser beam up to 15 times per day.
- The EDRS-C second node will be launched in 2017 to help transfer the massive amounts of data being sent back and forth over Europe.
- Unlike EDRS-A, which is hosted on a Eutelsat commercial satellite, EDRS-C is a dedicated satellite built specifically for the system.
- Both nodes carry a TESAT payload with a laser intersatellite terminal developed under funding by the DLR German Aerospace Center. EDRS-A also carries a high-speed Ka-band intersatellite payload to relay data to and from the International Space Station.
- The first two satellites are planned to be complemented by the EDRS-D third node over Asia in 2020. EDRS-D is part of a program called GlobeNet, which will extend the EDRS quasi-realtime data relay coverage from Europe to worldwide.
Figure 4: Illustration of the EDRS-A spacecraft in GEO transmitting high-rate data on laser beam technology between LEO spacecraft and Earth (image credit: ESA)
• June 1, 2016: ESA today unveiled the first Sentinel-1 satellite images sent via the European Data Relay System's world-leading laser technology in high orbit. The two images (Figures 5 and 6) were taken by the radar on the Copernicus Sentinel-1A over La Reunion Island (Indian Ocean) and its coastal area. The first was scanned in a high-resolution mode, the second in a wide-swath mode that provides broad coverage of surrounding waters, and used in particular for maritime surveillance. 24)
- Sentinel-1A in LEO (at 28,000 km/hr) transmitted the images to the EDRS-A node in geostationary orbit via a laser beam at 600 Mbit/s. The laser terminal is capable of working at 1.8 Gbit/s, allowing EDRS to relay up to 50 TB a day. EDRS immediately beamed the data down to Europe. The transfer between the two satellites was fully automated: EDRS connected to Sentinel from more than 35 000 km away, locking on to the laser terminal and holding that link until transmission was completed.
- DLR/GSOC (German Space Operations Center) in Oberpfaffenhofen, Germany, tasked by the MOC (Mission Operating Center) of Airbus Defence and Space in Ottobrunn, received the raw Sentinel-1A data at its station in Weilheim, Germany. They were then passed to the ESA-managed Sentinel-1 ground segment, where they were processed to generate the final products.
- Magali Vaissiere, ESA Director of Telecommunications and Integrated Applications, said at the Berlin Airshow today, "With today's first link, EDRS is close to becoming operational, providing services to the Copernicus Sentinel Satellites for the European Commission. EDRS is the world's first laser relay service and features technologies developed by European industry."
- For Sentinel-1, EDRS adds flexibility, increasing the availability of products to users. It will also allow fast downlink of data acquired outside of Europe, helping services requiring products in real time, as well as in emergency and crisis situations.
- The European Commission's Copernicus Sentinel satellites are the first users of the EDRS service. ESA is planning the GlobeNet program to extend EDRS by 2020, providing additional security services to satellites, aircraft and drones.
Figure 5: Sentinel-1A SAR image over La Reunion Island and its coastal area. This image was scanned in a high-resolution mode (image credit: ESA)
Figure 6: Sentinel-1A SAR image over La Reunion Island. This image was scanned in a wide-swath mode that provides broad coverage of surrounding waters, and is being used in particular for maritime surveillance (image credit: ESA)
• April 15, 2016: EDRS-A has been in orbit for a month and its testing is going well. The RSS (Redu Space Services) team in Belgium is now pushing it ever-closer to full service by laying the groundwork for it to be ready for its first laser links to the Copernicus Sentinels. Testing began two weeks after the Eutelsat satellite was launched and while it was still travelling towards its final position at 9°E, over Europe. 25)
- The tests are being performed by a pan-European web of ground and control centers managed by the various partners with Redu Space Services of Belgium playing a key role. The RSS team is carrying out most of the EDRS-A payload tests from ESA's Redu Center in Belgium in coordination with the DLR German Space Operations Center (GSOC) in Oberpfaffenhofen, Germany, and Eutelsat's Satellite Control Center in Rambouillet, France. Airbus Defence and Space hold the overall responsibility as the EDRS partnership prime.
• February 29, 2016: Demonstrating the capabilities of EDRS (European Data Relay System), dubbed "SpaceDataHighway", and Copernicus, ESA (European Space Agency) together with DLR (German Aerospace Center) and Tesat-Spacecom demonstrated the first quasi-real-time end-to-end delivery of a processed SAR (Synthetic Aperture Radar) image and ship detection information from an area farfrom any ground station within 18 minutes, using laser communication via a data relay. 26) 27)
- The Sentinel-1A SAR data collected over the South Atlantic (off Brazilian coast) have been received, after being relayed via optical intersatellite link to TDP1 (Technology Demonstration Payload No 1), at DLR facilities. By using the DLR ground segment in Oberpfaffenhofen and Neustrelitz, Germany, the raw data have been processed to a Level 1 image within 13 minutes after the data collect. The ship detection information was available after 18 minutes from the collect. This is well within the expectations for such information to be actionable for maritime surveillance.
- Maritime surveillance is benefitting to a major extent from satellites monitoring the Earth's surface with SAR, being capable of detecting ships and oil spills independent of weather and cloud covers. Within the Copernicus program the Sentinel-1 satellites carry a SAR, and thus is of major relevance for maritime surveillance in context of environmental protection, illegal migration, trafficking, piracy, and illegal fishing.
- Information like ship detection reports retrieved from SAR satellite imagery must be fresh to be actionable. This requires an immediate transfer of the imagery to ground, where it is processed, analyzed, and provided to the surveillance expert on duty. To still be considered actionable the information should be available in less than 30 minutes.
- Contributors to the information latency are the ground processing and analysis time, and the data transfer time from the satellite to the ground. The latter can be more than an hour if the satellite has to travel until reaching the next ground station following the image collection over the area of interest. To cut such delays down the use of an intersatellite data relay is an efficient solution.
- One of EDRS's services is to assist maritime surveillance with near- and quasi-realtime ship detection data. Eighteen minutes from collect to processing is well within the sector's needs to react to rapidly evolving situations like oil spills, illegal migration and piracy. Without EDRS, the time between the data being collected and the satellite passing over a ground station can be more than an hour.
Figure 7: Actionable maritime information from Europe's Copernicus System, through Data Relay also from Sea Areas outside of Europe (image credit: DLR, ESA, Tesat-Spacecom)
• January 30, 2016: EDRS-A has reached space aboard its host satellite and is now under way to its final operating position at 9º longitude over Europe, where it will be operated by Eutelsat. 28)
EDRS space segment:
The EDRS will be a constellation of GEO satellites intended to relay user data between LEO satellites, as well as UAVs (Unmanned Aerial Vehicles) in the future, and ground stations. EDRS will allow visibility between GEO and LEO satellites for the larger part of the orbits, offering significantly extended communication periods when otherwise LEO satellites only have a very reduced visibility from any ground station. EDRS is envisaged to significantly improve the stringent timeliness requirements of demanding Earth observation missions (i.e., time critical services).
The EDRS space segment is composed of two elements (Ref. 3):
1) The EDRS-A hosted payload, which contains a Laser Communications Terminal (LCT) and a Ka-band terminal for OISL (Optical Intersatellite Link) and Ka-band ISL, respectively. The EDRS-A payload will be placed as a piggyback payload on-board Eutelsat-9B commercial telecommunication GEO satellite manufactured by Airbus Defense and Space (formerly Astrium Satellites SAS,France). The Eutelsat- 9B satellite, which is based on Astrium's Eurostar E3000 bus heritage. 29)
Over its 15-year mission lifetime, Eutelsat-9B will operate up to 66 Ku-band transponders connected to a broad European widebeam and four regional beams over European countries. It will increase Eutelsat's capacity for video services in Europe, providing wide coverage for channels seeking maximum reach into satellite homes and terrestrial headends, as well as regional footprints addressing linguistic markets for digital TV in Italy, Germany, Greece and the Nordic/Baltic regions.
2) The EDRS-C platform (dedicated satellite manufactured by OHB of Bremen, Germany) carrying the EDRS-C payload (which includes an LCT for OISL). The EDRS-C satellite is based on the OHB developed SGEO (Small GEO) platform with an increased payload capability of about 360 kg and 3 kW and a lifetime of 15 years. This node will also host a 3rd party payload called HYLAS-3 built by MDA Corporation (Canada) for Avanti Communications (United Kingdom). The final orbital location is at 31ºE, taking into account the needs from other payloads on board.
Figure 8: EDRS infrastructure currently under development depicting the EDRS-A and EDRS-C nodes of the space segment (image credit: ESA)
The development and manufacturing of both the EDRS-A payload and the dedicated EDRS-C satellite (including the EDRS-C payload) are executed in parallel. EDRS-A and EDRS-C payloads (including the LCTs) are manufactured by Tesat Spacecom (Backnang, Germany; Tesat Spacecom is a subsidiary of Airbus Defence and Space).
The Eutelsat 9B satellite, in addition to Eutelsat's main payload and the EDRS-A payload, will also host the so-called "ASI Opportunity Payload," funded by ASI (Italian Space Agency. Furthermore, the EDRS-C Satellite will also embark the so-called HP (Hosted Payload), an opportunity offered by ESA to fill up the spare payload capacity on the EDRS-C platform. The Hylas-3 Ka-band payload has been selected by ESA for embarkation as a HP. The contract between ESA and the commercial satellite operator Avanti Communications (UK), the owner of the Hylas-3 payload, has been signed in July 2012. The Hylas-3 payload is procured by Avanti Communications, and the integration and test activities with the EDRS-C platform will be conducted jointly with OHB. 30)
Eutelsat 9B Layout: The LCT is accommodated on the hosting satellite Earth deck to allow pointing towards the Earth direction within the operational FOV, without any obstruction. The Eutelsat 9B satellite configuration is shown in Figure 9 with focus on the Earth deck where the LCT is accommodated (Ref. 29).
The LCT FUS (Frame Unit System) baseplate is tilted by 15º with respect to the Earth deck plane to ensure the CPA (Coarse Pointing Assembly) azimuth rotation axis is far enough (more than 3º) from the edge of the operational FOV. Figure 10 shows the tilted FUS baseplate and HTS (Heat Transport System) condenser plate interface to the satellite. The condenser plate is connected to dedicated radiators through heat pipe networks.
Figure 9: Eutelsat 9B satellite configuration (image credit: Airbus DS)
Figure 10: Embarkation of the EDRS-A LCT on Eutelsat 9B (image credit: Airbus DS)
The LCT accommodation guarantees its FOV is free of any obstruction (as shown in Figure 11). The "bean shape" of the actual FOV is due to the fact that the CPA aperture is offset with respect to the azimuth rotation axis and to the specific coupling between azimuth and elevation angles when pointing in a required direction.
Dedicated shielding screens and MLI blankets are implemented between the LCT FUS baseplate and the satellite top floor covering the HTS tubing and condenser plate to provide protection of the LCT against the space environment (radiation and micro-meteorites).
Figure 11: LCT beam pointing direction over operational FOV (image credit: Airbus DS)
EDRS-A payload: The part of the EDRS-A payload related to the OISL is sketched in Figure 8. The data received by the LCT are transferred to modulators through the DPU (Data Processing Unit). Modulators generate the corresponding RF (Radio Frequency) signal which is amplified and transferred to the ground via the dedicated antenna.
Figure 12: Communication scheme of the EDRS-A LCT payload (image credit: Airbus DS)
ESA will act as a major customer for Airbus DS (former Astrium) paying for relay services of data from the Sentinel satellites. However the system is designed such that more customers can be integrated.
Figure 13: The EDRS system architecture including the various elements of the space and ground segments (image credit: EDRS consortium)
Hybrid payload for EDRS: 31)
The motivation for EDRS was to overcome the drawbacks of classical LEO data transmission capabilities to ground, i.e. limited transferred data volume and data latency, by using high speed OISL (Optical Intersatellite Links) between LEO and GEO relay satellite and multi channel RF downlinks in Ka-band for the GEO to ground links. The motivation for to realize the payload system, is that Tesat Spacecom as one of the major satellite communication equipment and subsystem designer and manufacturer has all competence and heritage to realize such a system for commercial application.
Seen from a geostationary relay satellite, the visibility of a LEO satellite increases at least by a factor of 4 to approximately 45 minutes. The LCTs (Laser Communication Terminals) operating on both, LEO and GEO satellites exchange data with up to 1800 Mbit/s in Advanced Mode, hence an increase by an additional factor of 3.5 compared to conventional X-band data downlinks. This means an increase by a factor 14 of the data volume that can be dumped down to Earth per LEO orbit! - The first users of the EDRS GEO payloads are the Sentinel-1 and -2 satellites of ESA. Those carry LCTs and operate in a legacy Sentinel Mode, with data transmission at 600 Mbit/s.
Figure 14: Overview of the EDRS optical services (image credit: EDRS consortium)
A Ka-band ISL is present in addition to the OISL on EDRS-A only. This RF link follows the trajectory by means of a steerable reflector antenna. It constitutes mainly a transparent repeater with approximately 300 Mbit/s data rate.
The design of the EDRS payloads is driven by the overall EDRS system design, shown in Figure 16 in terms of the data flow from data source to data sink. The EDRS system includes the Sentinel-1 and Sentinel-2 LEO satellites, each of them equipped with a LCT. The interface from the LEO's mass memory, which stores the acquired sensor data of the LEO instruments, is connected to the LCT via LIAU (LCT Interface Adaption Unit (LIAU).
The main purpose of the LIAU is threefold, first it combines the two mass memory 8-bit wide input data streams containing CADU frames (each with approx. 280 Mbit/s) into one 16-bit bit wide output data stream. Second, it performs initial data framing (into so-called LIAU frames) and RS (255, 239) encoding. And third, it performs a data rate adaptation by stuffing idle data frames in order to achieve exactly 600 Mbit/s.
The repetition line encoding inside the LCT improves the optical channel performance further and adapts to the LCT net bit rate of 1800 Mbit/s. After reception by the GEO LCT, the received data is further channel-coded in the DPU.
A key contributor to errors introduced on the OISL data transmission is the respective satellites µ-vibration spectrum, originating from various sources like reaction wheels and solar array drive mechanisms. It has been found that the SNR (Signal-to-Noise Ratio) and the error statistics on the OISL are only slowly time-variant compared to the LIAU frame duration. Moreover, the SNR variations are rather small and limited to about 1 dB. Extensive simulations have been performed by Tesat to validate the efficiency of the employed channel codings. Those concluded, that the overall FER (Frame Error Rate) of 10-7 at the data sink on ground can be well achieved.
Figure 15: Overview of the EDRS Ka-band services (image credit: EDRS consortium)
Table 1: EDRS services
Figure 16: EDRS overall system data flow (image credit: Tesat Spacecom)
One of the main functions of the DPU are to split the 16-bit wide 1800 Mbit/s data stream from the LCT into two (Sentinel Mode) or four (Advanced Mode) data streams that will be picked up by the respective modulators later applied to the information rate of 300 Mbit/s. As for the Sentinel mode 2, active channels are used, these sum up to 600 Mbit/s useful data rate (Table 2).
Figure 17: Service to Copernicus Sentinel satellites (image credit: EDRS consortium)
Legend to Figure 18: The orbital position of the Alphasat satellite is also shown. The Antarctic coastline east and west of +20º longitude sees these GEO-satellites at more than 10º elevation.
LCT (Laser Communication Terminal):
Compared to typical RF communication systems laser communication terminals (LCT) offer the advantage of higher data rate and larger link distance at lower size, weight and power. The major factor is the four orders of magnitude shorter carrier wavelength translating into higher antenna gain. As additional benefits, laser communication links are free of interference problems, they provide secure transmission and the user is not limited by ITU regulations. Of the available optical technologies homodyne BPSK (Binary Phase Shift Keying) is superior due to the merits of: 33) 34) 35)
• Spatial filtering by the homodyne detection cone (the narrowest possible for a given aperture)
• Frequency filtering by phase locking loop (far more selective than available optical coatings)
• Leveraging the signal amplitude (superposition with orders of magnitude larger than the local oscillator amplitude).
The objective of the LCT is to operate a duplex communication link for binary digital data between two satellites or a ground station via a single optical carrier at 1.064 µm wavelength. The demonstration LCTs, accommodated on the TerraSAR-X (launch June 15, 2007) and NFIRE (Near Field Infrared Experiment) spacecraft of DoD (launch April 24, 2007), are considered to be verified on orbit throughout multi-year routine operations. More than 100 ISLs (Intersatellite Links) with bidirectional communication have been established so far. The first 2nd generation LCT , with the TDP1 (Technology Demonstration Package No 1), will be flown on Alphasat-1 / Inmarsat I-XL, a GEO spacecraft scheduled for launch in Q2 2013 (positioned at longitude 25º E).
The EDRS OISLs are based on 2nd generation LCTs (Laser Communication Terminals) which are developed and qualified by Tesat Spacecom (Germany) under DLR German national funding (Ref. 29) . These LCTs feature a significantly increased data transmission rate compared to SILEX technology, and at the same time reduced mass and size (Ref. 3). 36) 37) 38)
Table 3: Performance comparison between SILEX OISL technology and Tesat LCT technology (Ref. 3)
The EDRS LCTs will benefit from the space heritage attained in the following in-orbit demonstrations led by DLR (German Aerospace Center):
• The in-orbit verification of the 1st generation Tesat LCT as part of the LEO-LEO OISL between TerraSAR-X (German LEO satellite) and NFIRE (US LEO satellite), which took place in 2008, at a data rate of 5.6 Gbit/s over link distances of about 5000 km. It demonstrated the feasibility of beaconless spatial acquisition and the communications performance of the homodyne BPSK detection scheme (data stream of 5.625 Gbit/s with a BEP <10-9).
• The in-orbit validation, in cooperation with ESA and the Swiss Space Office, of the 2nd generation Tesat LCT as part of the LEO-GEO OISL between the GEO LCT embarked on ESA's Alphasat satellite, (Figure 19) and the LEO LCTs on board Sentinel-1A/-2A satellites. It will demonstrate a LEO-GEO bidirectional link. Furthermore, it will perform end-to-end preoperational experiments between Sentinels-1A/-2A satellites and Alphasat (i.e., EDRS precursor) at 600 Mbit/s of user data rate. The Alphasat spacecraft was launched on July 25, 2013, whereas the launch of Sentinel-1A and Sentinel-2A satellites is expected in 2014 and 2015, respectively.
Figure 19: Tesat 2nd generation LCT instrument showing the space side with hemispherical coarse pointing unit (image credit: Tesat Spacecom)
LCT instrument: The LCT itself consists of all subunits necessary to perform an optical data relay link, including data electronics for the transmit and receive paths, laser and fiber amplifiers and corresponding driver circuits as well as a computer that manages the operation, monitoring and control of the subunits. The LCT also contains a digital interface with the satellite main data bus, the mechanisms (coarse and fine pointer) and beam expander optics. The satellite bus voltage is converted into stabilized outputs for the internal electronics using a dedicated subunit.
All subunits are implemented on a single FUS (Frame Unit System) as shown in Figure 20. This unit also embeds part of the HTS (Heat Transport System) collecting power to be dissipated externally to the LCT through a dedicated condenser plate which is the main thermal interface of the LCT with the hosting satellite.
The CPA (Coarse Pointing Assembly) implements two articulations (called azimuth and elevation) to allow the optical beam to be pointed towards the target during a link: the azimuth rotation axis is perpendicular to the FUS baseplate and the elevation rotation axis is perpendicular to the azimuth rotation axis. The hemispherical CPA is locked in a park position for launch.
Figure 20: Annotated Tesat-Spacecom LCT, with CPA deployed and shown without full HTS (image credit: Tesat Spacecom)
The LCT block diagram is shown in Figure 21. Major changes are: For the 2nd generation LCT, an off-axis telescope is chosen, the optical power amplifier is changed to a 5 W device, the receiver is optimized for a user data rate of 1.8Gbit/s. For GEO applications, the electronics were redesigned to operate the adapted devices and to match with the GEO radiation environment for 15 years of continuous service. The thermal system is improved, the mechanics scaled for the bigger units.
LCT generic design/qualification approach: The LCTs are built such, that the LCTs for GEO and LEO application are same for its units design and their qualification. The GEO and LEO LCTs have identical optical space interfaces with same performance.
The optical data and laser paths are shown in Figure 21. The transmitted optical beam is generated by the coherent transmitter and correctly pointed towards the counter-part after deviation by point-ahead, fine pointing and CPA mirrors. The incoming beam is deviated by the CPA mirrors, then the fine pointing mirror before reaching the coherent receiver.
The HTS consists of two variable conductance loop heat pipes that enable a temperature control of the FUS under varying environmental and power conditions. The interface temperature of the HTS condenser plate (Figure 22) is maintained within the operational range (between -10ºC and +15ºC).
Figure 22: EDRS-A LCT FM (Flight Model) with LCT in delivery configuration and MLI installed (image credit: Tesat Spacecom)
The LCT one-unit design consists of a central rectangular base structure, a coarse pointer (gimbal) mounted on space side and the optics unit reaching through this structure on the S/C side. The frame unit structure houses the entire laser communication terminals electronics and active optics.
The optics unit comprises the receive/transmit optics, fine steering mechanisms and the receiver. A single telescope as optical antenna serves as common transmit and receive path. The coarse pointer is designed for hemispherical tracking of the counter terminal. In park position, the optics are protected during non-operational modes against contamination; a launch lock secures the coarse pointer during launch.
Together with Renishaw (UK), Tesat has successfully developed and tested a space qualified optical encoder. While it was tailored to the operation in a LCT under harsh environmental conditions outside the spacecraft in GEO, it can be used as well for many other applications in high precision, long life space instruments. 39)
Table 4: Performance parameters of the optical encoder
Figure 23: Photo of the EDRS-A LCT during acceptance tests in the TV chamber at Tesat Spacecom (image credit: Tesat Spacecom)
Main LCT Hosting Requirements:
Most of the LCT hosting requirements are similar to interface requirements of other equipment installed on the hosting platform (e.g. electrical interface, mechanical interface, data bus interface) and are handled following Eurostar E3000 standard processes. Special care was paid to a few requirements that are specific to the LCT. They are similar to requirements for hosting other optical instruments which require high pointing stability.
The LCT power dissipation depends on the mode in which it is running. Its maximum power dissipation is similar to TWT (Travelling Wave Tubes) used on telecommunications satellites. A specific feature of the LCT is that it requires an interface temperature at HTS condenser level lower than 15ºC.
Pointing towards a target and following its trajectory is performed by combining CPA rotations around azimuth and elevation axes. By design, this two-axes mechanism is such that for a given target speed, the closer the pointing direction is to the azimuth rotation axis, the faster the azimuth rotation speed will be. The azimuth rotation axis is tilted with respect to the nadir direction to be outside the operational FOV (Field of View), thereby limiting the maximum azimuth rotation speed. The trajectories of LEO satellites for altitudes up to 2000 km, seen from a geostationary position, are all within a cone of 11.5º half cone angle. The geometrical accommodation also needs to ensure a FOV free from obstructions when in operating conditions to allow performing a link with a target that can have an orbit altitude up to 2000 km, as shown in Figure 24.
Figure 24: LCT operational FOV (versus the hosting satellite nadir direction), image credit: Airbus DS
The link acquisition process is performed in open loop and requires both high pointing accuracy of the beam towards the counter-part as well as high pointing stability of the beam:
• In order to establish a link, both terminals have to be pointed accurately towards each other. The pointing direction of each terminal is computed taking into account the orbit position and velocity of the counter-part, the orbit position and velocity of the hosting satellite and the attitude of the hosting satellite. The maximum pointing error that remains during this open loop pointing phase defines the Uncertainty Cone (UC). This UC is larger than the beam divergence, but must be kept lower than the LCT acquisition sensor FOV (2500 µrad half cone angle). It is also important to note that the acquisition process is such that the smaller the UC is, the shorter the link acquisition duration will be. — The positions and velocities of the satellites hosting the two terminals during the link are predicted using orbit models computed by the operational ground segments. The relevant information is transferred to the corresponding LCTs in advance of the link by uploading a set of five telecommand blocks.
• One key step of the acquisition process is the scanning of the UC with the beam to ensure the counterpart will be illuminated at least once during one complete scanning. The detection of the incoming beam once per scanning allows the counterpart to reduce its own pointing error. Pointing stability of the hosting satellite is consequently a key asset during this phase to ensure a good coverage of the whole UC when scanning the narrow beam.
• Start of the acquisition process needs to be time-synchronized between the two terminals which will go through a scanning / repointing process until the beam of each terminal is repointed and tracked accurately on its TS (Tracking Sensor).
Regarding the hosting satellite, the LCT acquisition process therefore requires:
• Accurate absolute time reference: the start of the link acquisition process has to be synchronized with accuracy better than 0.5 seconds between the 2 LCT's engaged in the link.
• Accurate orbital position knowledge for the hosting satellite: conventional orbit determination methods using ground station ranging are sufficient for the hosting geostationary satellite. The orbital position of the target is propagated autonomously on-board the LCT itself using a dedicated model.
• Accurate pointing knowledge: the satellite pointing performance is one of the contributors to the UC. The standard pointing performance of a telecommunications satellite results from several errors (e.g. initial alignment and stability between attitude sensors and payload, attitude control performance, thermoelastic distortions). The maximum pointing error is in the range of 1200-1500 µrad, but the contribution to the LCT Line Of Sight (LOS) pointing error is usually not accurate enough with respect to the LCT requirements (an overall pointing error of 1500 µrad is targeted to ensure a short enough link acquisition duration). The contribution of the satellite can be improved by using the pointing knowledge using the AOCS (Attitude and Orbit Control System) sensors instead of relying on the pointing performance itself.
• Stable pointing: the required stability of the LCT LOS is far more demanding than the standard performance of a telecommunications satellite. The LCT requires stability in the order of magnitude of 1 µrad peak-to-peak for frequencies greater than 100 Hz, which is 10 to 100 times more stringent than what is achieved in the worst case on standard satellite platforms.
The LCT also needs to be protected against the space environment (radiation and micro-meteorites mainly).
EDRS ground segment:
In addition to the space segment, EDRS will develop the necessary ground segment infrastructure, consisting of (Ref. 3):
• EDRS SCC (Satellite Control Center) facilities: The dedicated EDRS SCC is linked to the EDRS-C spacecraft Operator (i.e., DLR in Oberpfaffenhofen), while for the EDRS-A payload this is a PCC (Payload Control Center) operated by DLR in conjunction with the Eutelsat operated SCC for the 9B satellite.
• EDRS MOC (Mission Operations Center) and the Back-up Mission Operations Center (B-MOC), which are the interface to the users for the planning of the EDRS services requests. The primary MOC will be in Ottobrunn (Germany), while the backup MOC will be installed at Redu Space Services (Belgium). The MOC function is provided by Astrium Services.
• EDRS DGS (Data Ground Stations), enabling reception of user data on ground. Two EDRS DGS shall be operational to provide service after completion of the EDRS-A LEOP (Launch Early Orbit Phase) operations and in-orbit commissioning.
• FLGS (Feeder Link Ground Station) and the B-FLGS (Backup -Feeder Link Ground Station), enabling user data reception as well as providing EDRS-C TM/TC capability. The FLGS and the B-FLGS shall be operational in line with the deployment of the EDRS-C satellite.
In June 2012, Astrium Services signed a contract with DLR (German Aerospace Center) to implement and operate major parts of the ground network. The agreement covers the design, implementation, delivery and operation of four ground stations: two DGS for the EDRS-A satellite in Weilheim (Germany) and in Harwell (United Kingdom), respectively, and the FLGS / B-FLGS for EDRS-C in Weilheim (Germany), and in Redu (Belgium). As part of the agreement, DLR will also implement and operate the DPCC (Devolved Payload Control Center) for EDRS-A and the SCC (Satellite Control Center) for EDRS-C in Oberpfaffenhofen (Germany). Major parts of the Ground Segment have been co-funded by DLR and the government of Bavaria. 40)
The space and ground segment for the EDRS user are intrinsically part of the end-to-end system, including space-to-space, space-to-ground as well as the ground-to-ground interfaces. A joint Copernicus/EDRS System team has been established in support to the definition and implementation of all aspects of the end-to-end link involving the Sentinels. This includes the definition of key performance indicators, applicable to a SLA (Service Level Agreement) between Copernicus and Astrium Services. Up to four Sentinels satellites are currently planned to be served simultaneously, with an average of 10 minutes of communication per orbit each. The current draft SLA expects a start of the service by 2015, extendable in phases until about 2030.
The EDRS concept of operation can be summarized as follows: Communication link sessions are planned and coordinated between the EDRS MOC and the user's MOC, making use of the visibility windows available between EDRS and the user satellites. The EDRS and the user's space infrastructure will be configured according to each link session parameters. User data will be transmitted from LEO user satellites to either of the EDRS payloads (i.e., EDRS-A, EDRS-C) and relayed to the DGS and/or FLGS/B-FLGS on the ground, from where it will be made available through terrestrial network to the users' sites (Figure 13). The users can also operate their own user ground stations to receive directly the user data.
Figure 25: Overview of the EDRS ground segment (image credit: DLR)
The central part of the EDRS ground segment, shown in Figure 25, is the MOC (Mission Operations Center) established by Airbus Defence and Space. It interfaces with all other components and coordinates the overall mission. On the one hand, it receives the link orders from the different users. It schedules the mission timeline for both EDRS satellites taken all known constraints into account and sends requests for the scheduled links to the DPCC (Devolved Payload Control Center), operating the EDRS-A payload, and the SCC (Spacecraft Control Center), operating the EDRS-C satellite. It also coordinates with four ground stations based at Harwell, Weilheim, and Redu which receive the user data from both EDRS satellites and deliver the data to the users. 41)
DPCC (Devolved Payload Control Center)
The DPCC is responsible for operating the EDRS-A hosted payload. A file-based interface with Eutelsat's SCC, which is operating the Eutelsat-9B satellite, is used for commanding. The telecommands (TC) of typically one flight operations procedure (FOP) are combined into one TC set file, transferred to the SCC in Paris, and released within Eutelsat's commanding system. For monitoring, two separated telemetry streams are received within the DPCC. One is forwarded by the Eutelsat SCC including all satellite telemetry, and one is received at an EDRS dedicated antenna containing only LCT related data.
The MOC is connected to the DPCC via a second file-based interface. The following request types are defined to be delivered by the MOC:
1) Payload link configuration request: The request type for each link execution either by the LCT or the Ka-band inter satellite antenna. It contains information of the link direction (EDRS to LEO, LEO to EDRS, or bidirectional), link speed, and LCT configuration parameters. It also contains coefficients of the LEO satellite's trajectory in the case of an LCT link, or vector data for the pointing direction of the Ka-band antenna.
2) Payload routine configuration request: A generic request type triggering the automatic execution of a flight operations procedure. The request contains the ID of the FOP, the necessary parameters for the FOP, and an execution time. Only a small number of FOP are possible to be requested for automated execution.
3) Payload basic configuration request: A generic request for the manual execution of a FOP. Similar to the routine request it contains the ID of the requested FOP, its parameters, and execution time. Contrary to a routine request this FOP is executed manually by the DPCC's flight operations team. Only a small quantity of requests of this type are expected and therefore no automatic mechanism is established.
4) Forward tasking data request: The LCT link service provides a mechanism to forward data from the EDRS GEO satellite to the target LEO satellite. These binary data are delivered to the DPCC via forward tasking data request and uploaded into the DPU (Data Processing Unit) on-board EDRS.
5) Payload configuration deletion request: All request types above can be deleted by this request type. In the case that the DPCC's internal processing is ongoing the process is stopped internally. Otherwise, if the request is already processed into TC sets forwarded to the Eutelsat SCC, a FOP to delete the commands from the on-board time-tag TC buffer is generated and executed.
The DPCC is located inside the multi-mission environment of DLR/GSOC (German Space Operation Center) in Oberpfaffenhofen. The very concept of multimission is based on the sharing of existing infrastructure (buildings, network, and software) with other missions. Within this environment a layered architecture of several components providing the EDRS service has been created. 42) A LMS (Link Management System) is processing the automatic requests received from the MOC. It interacts with a flight dynamics system and the Automator. The latter is the central component executing the automatized flight operations procedures. All components are reporting their current status to a common monitoring tool.
Due to the commercial nature of the program, highly ambitious performance requirements have been defined and need to be met by the DPCC: the service level agreement foresees continuous payload utilization, up to 200 links per day and communication channel, over the expected lifetime of 15 years, with a targeted service availability of at least 99.6% over 60 days and an order reaction time well below one hour; a task that can hardly be handled in a manual or semi-automated operations concept.
The EDRS payload is therefore controlled using a fully-automated operations engine which complements GSOC's core MCS (Monitoring and Control System), an enhanced derivative of ESA's SCOS-2000 v3.1 (Satellite Control and Operation System-2000, Version 3.1). The automation engine is designed to supervise the complete cycle of telecommand uplink and execution, as well as reaction monitoring of telemetry. Updates to the onboard mission timeline are scheduled and uplinked autonomously, triggered either by spacecraft events or high-level external link requests. Telemetry analysis and key performance indicators are provided in quasi real-time to the MOC (Mission Operations Center).
With EDRS-C being hosted on a very different platform than EDRS-A, the DPCC ground segment was designed to be independent of the particular spacecraft platform. This is realized via a layered system architecture centered around the core MCS, with layer 1 consisting of the commanding front-end and automation engine while layer 2 comprises the LMS (Link Management System) and interface to the MOC. This layered architecture allows for a seamless phase-in of EDRS-C, with no software changes required for layer 2 and only minor upgrades to components of layer 1. Differences in the platform will be masked through the versatility of the core MCS. 43)
The DPCC routine activities fall into two categories: nominal activities related to the provision of the link service, based on high-level requests from the Mission Operations Center. Secondly, the management of payload configuration and maintenance activities, which must be scheduled in coordination with any external requests. Both types of activities are executed in a fully autonomous way by the Link Management System and automation engine, designed and developed by DLR/GSOC for the EDRS mission.
In summary, the payload and satellite operations concept of the EDRS constellation poses both challenges and opportunities to the ground segment design. DLR/GSOC has leveraged the design and implementation of the DPCC ground segment and early operations of the EDRS-A payload. DLR is now in a position to reuse and extend the largest part of the system design for the EDRS-C ground segment implementation, which is currently ongoing. The mission integrates well with the GSOC multi-mission approach and a large part of operational concepts could be streamlined by the deployment of automation, resulting in a reduction of project costs and operational overhead.
Automator (Automatic command and control system):
For the DPCC, an automatic system, namely the Automator, was developed at DLR for commanding and monitoring the EDRS-A payload in its routine operations phase. The sheer number of up to 400 links per day are the main driver for such an approach. An additional driver is the required speed of processing, from receiving link requests from the MOC, until sending commands to the spacecraft. A late request is possible until 45 minutes (reception at DPCC) before its execution. With the involved complexity of each link, the processing is beyond the capability of manual commanding concepts (Ref. 41).
Link operations: The LMS (Link Management System) is responsible for the planning of all link requests transmitted from the MOC. Usually, these requests are available in the DPCC at eight hours prior to their planned execution time as shown by the autonomy displayed in Figure 26. In addition, late requests are possible until 45 minutes before execution. At each LMS planning cycle, it compares the list of pending (not yet uplinked) link requests with the table mirroring the current state of the on-board time-tagged telecommand (TTC) buffer. As a result of this comparison, the LMS selects which activity (LCT link, Ka-band link, routine) shall be uplinked next. The LMS will always take the next activity in the chain (chronologically sorted) and try to load it into the TTC buffer. In order to assess how many TTC slots are required for an activity, the LMS must know the number of TTC required by each FOP. The LMS scheduling process is triggered either after reception of a payload link configuration request or when the Automator delivers the current state of the TTC buffer to the LMS. This ensures low-latency LMS operation. In case not enough TTC slots are available for a pending complete activity, the LMS will postpone the uplink until the next planning cycle. Knowing the feedback from the Automator about the TTC buffer state, the LMS only uses the TTC buffer information that is verified by telemetry. Consequently it is ensured that enough space is really available in the TTC buffer before actually sending the commands. As such, the TTC buffer on-board will be constantly kept as full as possible. Through these successive planning cycles, the LMS tries to schedule any request in its request database.
Figure 26: Optical link sequence (image credit: DLR)
The link planning process of an optical inter satellite link only requires the execution of one FO; however, the process for a Ka-band link is difinitely more complex. While one flight procedure is executed to configure the RF components of the payload for the link, the steering of the inter-satellite antenna is a complex task. The antenna is commanded by entries of a time and a direction embedded into two tables with 1440 entries each. The on-board function interpolates between two entries of the active table while new entries can only be commanded into the inactive one. The processing is started at a commanded start entry of one table. Certainly this entry must have a feasible time in the future and an antenna direction that is reachable in time without exceeding speed limits. For link requests received at the DPCC eight hours before their execution the table entries are written into the inactive table and a table switch is planned at a time when all the entries for the upcoming eight hours are in the new active table (Figure 27a). For late requests or for the deletion of a link, the currently running table would have to be changed. Therefore, a new table for the next eight hours including the late request (link 8b in Figure 27c), or excluding the deleted link (link 6 in Figure 27b), is composed on ground and loaded to the inactive table on board. Afterwards the active table is switched to the new composed one.
Figure 27: Ka-band table management: for each operation, the currently active table (in blue) must be switched (image credit: DLR)
While the Ka-band link is always bidirectional, the LCT links are possible in return (from the target LEO satellite via EDRS to the ground), forward (to the LEO satellite), and bidirectional. The actual link commanding is similar in all three LCT link cases, but for forward and bidirectional links the binary data to be forwarded has to be uploaded to the DPU prior to link execution. This forward tasking data service is done via the normal commanding channel by telecommands containing 62 bytes of data. The filling of the DPU forward data buffer of five megabytes is planned by the LMS with a lower priority as the link commanding in order to not block the link execution.
Automated routine operations: In addition to the link operations a small number of routine operations are also performed automatically. These operations are also executed as time-tagged telecommands which are uploaded to the spacecraft eight hours in advance. Thereby the spacecraft autonomy of eight hours is ensured. Furthermore a synchronization between routine and link commands is needed.
The following routine operations are conducted by the DPCC autonomously from request provided by the MOC:
• LCT time synchronization
• On-orbit propagator
• LCT alignment matrix
• LCT park and unpark
• Ka-band antenna steering pause
All other tasks are performed in a more classical manual operations approach. This is the case for all contingency operations as well as nominal operational tasks that are only performed rarely. For that members of the flight operations team will execute the FOP, and decide the timing and execution state. The telemetry verification can be done by display pages. But as the Automator is still used for generating the TC sets delivered to the Eutelsat SCC, a semi-automatic FOP execution is possible.
SA (Situational Awareness):
Being aware of the situation of all parts of the system is of the outmost significance of any spacecraft mission. Already in the classical operations concept, the spacecraft controller (SPACON) is monitoring the spacecraft's status in telemetry as well as the state of the ground components. The added complexity is caused by the reduced knowledge of the ongoing activities triggered by the automatic system. The operator is not the actor anymore, but an observer. And with EDRS being included in the GSOC multimission environment, the SPACON cannot monitor only EDRS at all times.
This new role reduces the situational awareness significantly. Mica Endsley defined the situation awareness (SA) as "the perception of the elements in the environment within a volume of time and space, the comprehension of their meaning and the projection of their status in the near future". 44) Although the work of Mica Endsley is focused on aviation, the principles can be transferred to spacecraft operations. Three levels of SA have been defined in her work: Level 1 - Perception of the elements in the environment, Level 2 - Comprehension of the current situation, and Level 3 - Projection of the future status. Adapted to the operational scenario the three levels can be understood as: 45)
• Level 1: Perceive the presence of a not nominal situation
• Level 2: Comprehension of the system's situation and the processes going
• Level 3: Projection of the future status.
In summary, the EDRS system is setting new speed levels, not only for data transmission from space, but also in the operations for GEO satellites. The innovative automated operations at DPCC are now starting to be in use for the first time and handle this challenging mission after the manual in-orbit test campaign of EDRS-A is completed. After the DPCC systems will have shown its capability in automatic operations, the next improvements will be assessed for EDRS-C. Additional routine operations, such as station keeping maneuvers, might be able to be automatized with these cutting edge concepts (Ref. 41).
IOV (In-Orbit Verification) of LCT for EDRS (Ref. 3):
EDRS operations will take advantage of the LEO-GEO OISL experiments between the GEO Alphasat satellite and the LEO Sentinel-1A/-2A satellites planned after the launch of the first Sentinel. The payload data rate requirement for the Sentinel-1A/-2A satellites is 600 Mbit/s, which is well within the capabilities of 2nd generation Tesat LCT. The objectives of these experiments with Alphasat and Sentinel-1A/-2A satellites are:
• to optimize the technical performances of the LEO-GEO OISL (including GEO-ground tests)
• to perform an early validation of the end-to-end data relay system, which includes the LEO-GEO OISL, the RF feeder link between Alphasat and its ground segment, and the interfaces and operations with the Copernicus ground segment.
The experience gained from these experiments will be taken into account during the IOV activities of the LCTs on board the Eutelsat-9B and EDRS-C satellites and for the validation of the end-to-end EDRS performances.
The approach for the IOV of the LCTs is as follows:
- LCT self-test: this test is performed during commissioning to check out the LCT performances after launch. A functional end-to-end test of the entire data transmit and receive chain (including the telescope and the coarse pointer) can be performed while the LCT is in parking position thanks to a mirror mounted in the parking position unit.
- IOV with an OGS Optical Ground Station): these trials are required in order to calibrate the LCT setting parameters (e.g., acquisition scanning parameters, misalignment matrix between satellite coordinate reference system and LCT coordinate reference system, clock offset and other propagator parameters, etc.) and to verify the full PAT (Pointing Acquisition and Tracking) performances (e.g., uncertainty cone, link acquisition time, etc.). The baseline is to use the ESA's OGS on Tenerife Island (Spain) with some adaptations (Figure 9). As a mean of cross support, DLR's mobile OGS can, on request, be used as backup. The DLR mobile OGS is intended for experimental space-to-ground optical links with GEO satellites (e.g. Alphasat) or lower altitude vehicles (e.g. Sentinel-1A, Sentinel-2A).
- IOV with LEO user satellite: these tests are to further fine tune the LCT setting parameters, and to validate the LEO-GEO O-OISL acquisition, tracking and communications performances. The LCTs on board the LEO Sentinel-1A/-2A satellites will be used as counter terminals.
After successful completion of the remaining commissioning activities (e.g., EDRS space segment with EDRS ground segment commissioning, joint EDRS Copernicus service commissioning) to verify the full operational capability of the overall EDRS system with the user (i.e., Copernicus), the EDRS will enter into operational phase by mid of 2015.
Figure 28: The telescope of ESA's OGS on Tenerife used for the experiments is a Zeiss 1 m ∅ Ritchey-Chrétien/Coudé telescope supported by an English mount (image credit: ESA)
In addition to the downlink capabilities, the EDRS can also provide quasi real-time access from ground to the LEO user satellite during periods of direct line-of-sight, which can be used to reconfigure the EO (Earth observation) LEO payload / satellite, and hence, shortening the reaction time of EO LEO satellites in case of emergency events (i.e., request on-demand).
The EDRS provides different types of optical and Ka-band services, using the OISLs (Optical Intersatellite Links) and Ka-ISLs (Ka-band Intersatellite Links), respectively (Figures 14 and 15). Both ISLs between the LEO user and the GEO satellites are bi-directional, and are referred as the RTN (Return link), from LEO user to GEO) and the FWD (Forward link), from GEO to the LEO user. The EDRS-A and the EDRS-C payloads offer Optical services, whereas the Ka-band services are implemented on the EDRS-A payload only.
The Optical services are split into RTN and FWD services. The Optical RTN service is a high data rate channel transferring the user data from the LEO user satellite to ground via the GEO relay satellite. The user data rate for the Optical RTN service is 600 Mbit/s for the so-called Sentinel mode (e.g., for Sentinel-1A and Sentinel-2A) and 1.8 Gbit/s for the so-called "advanced mode" to cover future user needs. The EDRS RF feeder link is accordingly dimensioned to support these user data rate requirements. The Optical FWD service is a low data rate channel (limited by the uplink TM/TC channel) to transmit telecommands to the LEO user satellite in quasi-real time (e.g., for reconfiguration of the Earth observation LEO payload / satellite).
Alternatively to the Optical RTN service, the EDRS also offers the Ka-ISL RTN service, which relays the user data from the LEO user satellite to ground at a user data rate up to 300 Mbit/s.
Table 5: Maximum handling capacity of the EDRS system currently under development considering one or two GEO nodes and operating in Sentinel / Advanced mode
Figure 29: Evolution of Ground Ports and adding Relay Service (image credit: Astrium Services)
• 2013: 5 ground based Teleports
• 2015: 11 ground based Teleports
• 2018: full Service EDRS A/C
• 2020: full Service EDRS A/C/D/E.
1) "European Data Relay Satellite System (EDRS)," ESA, 2009, URL: http://multimeters/docs
2) "ESA issues open competition for EDRS phase B/C/D/ E1," Feb. 26, 2010, URL: http://telecommand/telecom/WWW
3) Michael Witting, Harald Household, Andrew Merell, Jean-Pascal Legality, Joseph Perigees, Jean Michel Later, Cedric Sal enc, Khalil Kabul, Helli Grues, Francois Ga rat, Hermann Ludwig Mueller, Silvia Mezzos, Rolf Meyer, Bjorn Gulch, Sabine Philippa-May, Ankle Pa gels-Keep, BSA Helen, Matthias Ligand, Marc Lead stone, Gerald Rickert, Georg Whetstone, Ludwig Lax, Lory Gerard, Dominique Ponced, Rolf Mag er, Klaus Schoenberg, Frank Heine, Stefan SEL, Konrad Panza, Her wig Zach, Hartman Campfire, Alexander Schneider, Ignacio Gutierrez Can as, Cristina Arias Perez, Herbert Sc huff, "Status of the European Data Relay Satellite System," Proceedings of the ICSOS (International Conference on Space Optical Systems and Application) 2012, Ajaccio, Corsica, France, October 9-12, 2012, URL: http://icsos2012.nict.go.
4) "European Data Relay Satellite," ESA Bulletin, No 146, May 2011, p. 93
6) "Announcement of Opportunity for Hosted Payload on board EDRS-C Satellite," ESA, Sept. 22, 2011, URL: http://telecom.esa.int/telecom/med
7) "EDRS: An independent data-relay system for Europe becoming reality," ESA, Oct. 4, 2011, URL: http://telecom.esa.int/telecom/ww
8) "Europe's 'data superhighway' in space sets sail," DLR, June 25, 2012, URL: http://www.dlr.de/dlr/en/desktopdefault.aspx
9) "Astrium contracts DLR for major parts of the EDRS ground network," Astrium, June 25, 2012, URL: http://www.astrium.eads.net/en/press_centre/astrium-c
10) "SES TechCom, Astrium and DLR achieve milestone for information highway in space," SES TechCom, June 27, 2012, URL: http://www.innovation.public.lu/en
11) Akos Hegyi, Martin Agnew, Judith Metschies, "SpaceDataHighway Will Redefine High-Speed Data Transfer," Earth Imaging Journal, July/August 2012, pp. 36-40, URL: http://www.edrs-spacedatahighway.com/tl_files/
12) "EDRS space network ready to go ahead," ESA, Nov. 23, 2012, URL: http://telecom.esa.int/telecom/www
13) "OHB System AG and Astrium GmbH sign contract for the delivery of an EDRS satellite," May 28, 2013, URL: http://www.edrs-spacedatahighway.com/news/items/ohb-system-ag-and-
14) "First EDRS node on track for launch," ESA, Oct. 29, 2014, URL: http://www.esa.int/Our_Activities
15) "European Data Relay System confirms services for Copernicus in cooperation with the European Commission," ESA, Feb. 25, 2015, URL: http://www.esa.int/Our_Activities/Observing_t
16) "EDRS-A and its laser are ready to fly," ESA, Dec. 9, 2015, URL: http://www.esa.int/Our_Activities/
17) "First SpaceDataHighway Laser Relay in Orbit," ESA, Jan. 30, 2016, URL: http://www.esa.int/Our_Activities/
19) Harald Hauschildt, Francois Garat, Heli Greus, Khalil Kably, Jean-Pascal Lejault, Hermann Ludwig Moeller, Andrew Murrell, Josep Perdigues, Michael Witting, Bas Theelen, Matthias Wiegand, Akos Hegyi, "European Data Relay System – one year to go," Proceedings of ICSOS 2014 (International Conference on Space Optical Systems and Applications), Kobe, Japan, May 7-9, 2014
20) "Successful launch of the first laser telecommunication satellite of the ‘SpaceDataHighway'," EDRS Space Data Highway, Feb. 1, 2016, URL: http://www.edrs-spacedatahighway.
21) "Arianespace selected by Airbus Defence and Space to launch EDRS-C satellite," Arianespace, March 19, 2015, URL: http://www.arianespace.com/news-press
22) "Start of service for Europe's SpaceDataHighway," ESA, Nov. 23, 2016, URL: http://m.esa.int/Our_Activ
23) "The SpaceDataHighway is Open for Traffic," Airbus DS, Nov. 23, 2016, URL: https://airbusdefenceandspace.com/newsroom/news-a
24) "Europe's SpaceDataHighway relays first Sentinel-1 images via laser," ESA, June 1, 2016, URL: http://m.esa.int/Our_Activities/Telecomm
25) "EDRS-A testing the waters," ESA, April 15, 2016, URL: http://www.esa.int/Our_Activities/Telecommunications_
26) "First Quasi-Real-Time Demonstration of an end-to-end delivery SAR image," EDRS Space Data Highway, Feb. 29, 2016, URL: http://www.edrs-spacedatahighway.com
27) "Brazil coast via laser beam," ESA, March 2, 2016, URL: http://www.esa.int/spaceinimages/Images
28) "First Space Data Highway laser relay in orbit," ESA, Jan. 30, 2016, URL: http://www.esa.int/Our_Activities/
29) D. Poncet, S. Glynn, F. Heine, "Hosting the first EDRS Payload," Proceedings of the ICSO (International Conference on Space Optics), Tenerife, Canary Islands, Spain, Oct. 7-10, 2014, URL: http://congrexprojects.com/Custom/IC
30) "EDRS makes room for Hylas-3," ESA, July 12, 2012, URL: http://www.esa.int/esaCP
31) Norbert Dörflinger, Matthias Motzigemba, Herwig Zech, Wolfram Lütke, "A new chapter begins for EO-Missions Hybrid Optical/RF Payloads for Data Relay Applications becomes operational," Proceedings of the 66th International Astronautical Congress (IAC 2015), Jerusalem, Israel, Oct.12-16, 2015, paper: IAC-15 B2.6.2
32) Dirk Giggenbach, Ricardo Barrios, Florian Moll, Ramon Mata Calvo,Sergei Bobrovskyi, Felix Huber, Nighat F. D. Johnson-Amin, Frank Heine, Mark Gregory, "EFAL: EDRS Feeder Link from Antarctic Latitudes - Preliminary Results of Site Investigations, Availability, and System Requirements," European Data Relay System – one year to go," Proceedings of ICSOS 2014 (International Conference on Space Optical Systems and Applications), Kobe, Japan, May 7-9, 2014, URL: http://elib.dlr.de/89312/1/__192.168.178.179
33) Stefan Seel, Hartmut Kämpfner, Frank Heine, Daniel Dallmann, Gerd Mühlnikel, Mark Gregory, Martin Reinhardt, Karen Saucke, Juri Muckherjee, Uwe Sterr, Bernhard Wandernoth, Rolf Meyer , Reinhard Czichy, "Space to Ground Bidirectional Optical Communication Link at 5.6 Gbit/s and EDRS Connectivity Outlook," 2011 IEEE Aerospace Conference, Big Sky, MT, USA, March 5-12, 2011
34) M. Gregory, F. Heine, H. Kämpfner , R. Meyer , R. Fields , C. Lunde, "Tesat laser communication terminal performance results on 5.6 Gbit coherent intersatellite and satellite to ground links," ICSO 2010 (International Conference on Space Optics), Rhodes, Greece, October 4-8, 2010, URL: http://congrex.nl/icso/Papers/Session%208a
36) Mark Gregory, Frank Heine, Hartmut Kämpfner, Robert Lange, Michael Lutzer, Rolf Meyer, "Commercial optical inter-satellite communication at high data rates," Optical Engineering, Vol. 51, No 3, March 13, 2012, pp: 031202-031202-7
37) Zoran Sodnik, Marc Sans, "Extending EDRS to Laser Communication from Space to Ground," Proceedings of the ICSOS (International Conference on Space Optical Systems and Application) 2012, Ajaccio, Corsica, France, October 9-12, 2012, URL: http://icsos2012.nict.go.jp/pdf/1569600353.pdf
38) Matthias Motzigemba, "Improvement of information latency in EO-Missions with the use of hybrid Laser/RF systems," Proceedings of the 64th International Astronautical Congress (IAC 2013), Beijing, China, Sept. 23-27, 2013, paper: IAC-13-B126.96.36.199
39) Martin Reinhardt, Konrad Panzlaff, Karl-Georg Friederich, Frank Heine, Roland Himmler, Klaus Maier, Eberhard Möss, Clive Parker, Simon McAdam, Jason Slack, Colin Howley, Rolf Meyer, "High Precision Encoders for GEO Space Applications," Proceedings of the ICSOS (International Conference on Space Optical Systems and Application) 2012, Ajaccio, Corsica, France, October 9-12, 2012, URL: http://icsos2012.nict.go.jp/pdf/1569587555.pdf
40) "DLR to Implement Major Parts of Ground Network," June 25, 2012, URL: http://www.edrs-spacedatahighway.com/news/
41) Jan-Christoph Scharringhausen, Andreas Kolbeck, Thorsten Beck, "A Robot on the Operator's Chair — The Fine Line Between Automated Routine Operations and Situational Awareness," Proceedings of the 14th International Conference on Space Operations (SpaceOps 2016), Daejeon, Korea, May 16-20, 2016, paper: AIAA 2016-2508, URL: http://arc.aiaa.org/doi
42) Thorsten Beck, Michael Schmidhuber, Jan-Christoph Scharringhausen, "Automation of Complex Operational Scenarios -Providing 24/7 Inter-Satellite Links with EDRS," Proceedings of the 14th International Conference on Space Operations (SpaceOps 2016), Daejeon, Korea, May 16-20, 2016, paper: AIAA 2016- 2417, URL: http://arc.aiaa.org/doi
43) Tobias Göttfert, Boris Grishechkin, Maria T. Wörle, Christoph Lenzen, "The Link Management System for the European Data Relay Satellite Program ," Proceedings of the 14th International Conference on Space Operations (SpaceOps 2016), Daejeon, Korea, May 16-20, 2016, paper: AIAA-2016-2645, URL: http://arc.aiaa.org/doi
44) Mica R. Endsley, "Design and Evaluation for Situation Awareness Enhancement," Proceeding of the Human Factors Society, 32nd Annual Meeting, Santa Monica, CA, USA, Human Factors and Ergonomics Society, Annual Meeting October1988, pp. 97-101
45) Mica R. Endsley, "Situation Awareness," The Oxford Handbook of Cognitive Engineering, Edited by John D. Lee and Alex Kirlik, Oxford Univ. Press, New York, May 2013, pp. 88-108.
The information compiled and edited in this article was provided by Herbert J. Kramer from his documentation of: "Observation of the Earth and Its Environment: Survey of Missions and Sensors" (Springer Verlag) as well as many other sources after the publication of the 4th edition in 2002. - Comments and corrections to this article are always welcome for further updates (firstname.lastname@example.org).