Environment Archives - Page 14 of 14 - Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design

Environment

January 1, 2006

GLONASS: The Once and Future GNSS

Once widely written off as another victim of the economic and political disarray following the collapse of the USSR, Russia’s GLObal NAvigation Satellite System (GLONASS) has arguably demonstrated the most stability of the world’s three GNSS programs in recent years.

Once widely written off as another victim of the economic and political disarray following the collapse of the USSR, Russia’s GLObal NAvigation Satellite System (GLONASS) has arguably demonstrated the most stability of the world’s three GNSS programs in recent years.

GLONASS followed the Global Positioning System into space with its first satellite launch on October 12, 1982, 4½ years behind the first GPS satellite went up. After reaching a high point in 1996 with more than two dozen operating satellites in orbit, GLONASS dwindled over the next five years to a nadir of seven operational satellites.

Strapped for cash and expecting a greater role in Europe’s Galileo project, Russia allowed paying commercial payloads from foreign customers to get in line ahead of GLONASS at its launch facilities. A dispute with newly independent Kazakhstan over maintenance, operation, and funding of the Baikonur launch facility further complicated the picture. Meanwhile, the relatively short design life of the spacecraft (three years compared to 7½ years for GPS) contributed to a rapid decline in operational satellites.

In 2001, a new Russian government under President Vladimir Putin reassessed its commitment to space-based positioning, navigation, and timing (PNT), and refashioned its development timeline to more sustainable dimensions. An August 21, 2001, decision committed the government to a 2002-2011 program to rebuild and modernize GLONASS.

A schedule of annual launches since then has doubled the constellation to 13 operational satellites. As a result, since 2001 the gap in worldwide navigation with GLONASS declined from 14 to 2 hours as of November with coverage 98 percent of the time over Russia, according to Sergey Revnivykh, an official with Roscosmos’ Satellite Navigation Department at the Mission Control Center of the Central Research Institute of Machine Building.

Picking Up the Pace

On December 25, Russia placed three more spacecraft into orbit and brought the system within striking distance of an 18-satellite constellation, which should be in place late next year with all satellites in service by early 2008. Under the current plan, the frequency of launches would increase over the next two years to provide a 24-satellite constellation by 2010–11.

The day after the December 25 launch, however, Putin expressed support for accelerating the GLONASS effort. According to the Russian Information Agency Novosti, Putin told government members, “The GLONASS system should be created before 2008, as it was originally planned. We have the possibility. Let us see what can be done in 2006-2007.”

RIA Novosti subsequently quoted Anatoly Perminov, head the Russian Federal Space Agency, as saying a proposal for earlier completion of the system would go to Putin before January 15, 2006.

Modernized GLONASS spacecraft (GLONASS-M) with a 7-year design life have flown on the launches since 2003. Two more went up with the most recent launch. Not well known is the fact that these include a second open civil signal at L2.

The availability of a second full open signal provides little practical benefit, however, because of the lack of user equipment outside the GLONASS control segment that can process the GLONASS L2 civil signal. New 72-channel chips recently announced by Javad Navigation Systems (the GeNiuSS) and Topcon Positioning Systems (Paradigm – G3) employ a common technical design that can process the GLONASS L2 signals, both C/A-code and P-code, as well as the new Galileo signals. Topcon has launched a new line of surveying equipment based on the technology, with the first product to be released as the NET-G3 receiver for reference station installations.

Technology, Policy, and Budgets

Unlike the Global Positioning System and Galileo, in which each satellite broadcasts a distinct code on the same frequency, GLONASS broadcasts the same code on different frequencies. At the L1 frequency, for example, the GLONASS open signal is spread between 1598.0625 MHz to 1607.0625, in sub-bands with signal peaks separated by 0.5625 MHz. This RF strategy requires broader swaths of increasingly rare radio spectrum and, at one point, brought the Russian system under pressure from radioastronomers and satellite communication systems that wanted to operate at the upper end of its RF allocation.

An agreement in the late 1990s committed Russia to an “antipodal” signal strategy that halved the number of bands on which satellites transmit their signals by assigning the same frequency to spacecraft orbiting on opposite sides of the Earth. This ensured that GLONASS receivers would not see conflicting signals on the same frequency, while allowing the bandwidth that it required to be compressed toward the lower portion of its allocation.

A 1999 presidential decree formally established GLONASS as a dual-use (civil and military) system, as is GPS. An Interagency Coordination Board comprised of civil and military agencies provides inputs from user communities, similar to the U.S. Interagency GPS Executive Board and its successor, the Space-Based PNT Executive Committee. The Russian Ministry of Defense (MoD) maintains and controls the system’s ground and space assets, although Roscosmos – the Russian Space Agency – acts as the program coordinator.

GLONASS receives funding directly from the Russian federal budget through line items in the MoD and Roscosmos agency allocations. Until recently, however, getting the funds through the civil agency remained problematical, according to Russian sources. The run-up in oil prices over the past couple of years has benefited Russia substantially. The nation produces and sells on the world market large quantities from its central Asian petroleum fields. President Putin has primarily used the funds to pay down indebtedness to the International Monetary Fund. Military programs, however, have received higher levels of support, which has translated into more stable funding for GLONASS, too.

Closing the Performance Gap

Shorter satellite survival on orbit has exacerbated the difficulty of sustaining the GLONASS constellation. All of the current operational spacecraft have been launched since 2000, and the mean mission duration (actual operational lifespan) is 4.5 years – about half that of GPS satellites.

Moreover, GLONASS performance has lagged behind GPS. A March 2005 study by the Swiss Institute of Science Research and Engineering, cited in a Tokyo symposium in November, reported that the accuracy of GPS ephemerides (the orbital locations of satellites broadcast as part of the navigation message) averaged about one meter compared to postprocessed tracking data from monitoring stations. In contrast, GLONASS ephemerides averaged about seven to eight meters.

In part, that reflects the more difficult challenge of tuning multiple signal/frequency combinations and accounting for the different propagation effects of carrier waves with slightly varying lengths. But the quality of on-board atomic clocks and system timekeeping, as well as weaknesses in the satellite navigation payload software and ground monitoring network, also contributed to the problem.

Now Russia is implementing an accuracy improvement program with modernization of satellites and ground infrastructure. Beginning with the GLONASS-M, manufactured by Reshetnev Applied Mechanics Research and Production Association (NPO-PM) in Krasnoyarsk, on-board clock stability over 24 hours has improved from 5×10-13 to 1×10-13. An improved dynamic model in the satellite navigation software will produce a lower level of unpredicted accelerations.

GLONASS-M spacecraft use previously reserved bytes in the navigation message to provide additional information, including the divergence of GPS and GLONASS time scales, navigation frame authenticity (validity) flags, and age of data information. Moreover, improved filters have been installed to reduce out-of-band emissions.

On the ground, GLONASS will also gain 3 stations from military tracking facilities and 9 to 12 from the Roscosmos network, much as the United States has done by incorporating National Geospatial-Intelligence Agency monitoring sites into the GPS tracking network. Both the United States and Russia are evaluating the utility and security of adding facilities from the International GNSS Service, an extensive network coordinated by NASA’s Jet Propulsion Laboratory in California.

New system clocks with high stability and improved systemwide synchronization will further improve GLONASS timing. Definition of the GLONASS coordinate system will tie it to the International Terrestrial Reference System, an international standard. As a result of these modernization efforts, Russian officials predict that GLONASS performance will equal that of GPS by 2008.

A new generation of satellites — GLONASS-K — is planned for launch beginning in 2008. These satellites will have a 10-year design life and carry a third civil signal at L3 frequency band, with a couple of frequency schemes under consideration in the 1198 to 1208 MHz band. Current plans for GLONASS-K include providing GNSS integrity information in the third civil signal and global differential ephemeris and time corrections to enable sub-meter real-time accuracy for mobile users.

Renewed Initiative

The recent progress in rebuilding and modernizing GLONASS appears to have bolstered the confidence of Russian officials in promoting the system internally and internationally. Russian state policy enacted last June mandates that, beginning in 2006, federal GNSS users employ only GLONASS or combined GLONASS/GPS receivers on Russian territory for aerospace and transport vehicles as well as for geodesy and cadastral surveying. And even before Putin’s recent remarks, Russia had re-engaged in several initiatives

The most recent round of talks with the United States led to a joint statement in December 2004 confirming that direct user fees would be imposed on civil GLONASS or GPS services and committed the two nations to ensuring the compatibility and interoperability of the two systems, implementing search and rescue functions using GNSS positioning, and cooperating on GNSS issues at international organizations.

On December 6, Russia and India signed an intergovernmental pact on the protection of classified military technologies during long-term cooperation under an agreement reached a year earlier for the joint development and peaceful use of GLONASS. This includes cooperation in GNSS ground infrastructure development and launch of GLONASS-M satellites on India’s Geosynchronous Satellite Launch Vehicle (GSLV). The GSLV design incorporates Russian rocket engine technology.

Finally, consultations with the European Union continue on a prospective Galileo/GLONASS agreement, with a technical working group scheduled to submit a proposal in April on signal compatibility and interoperability at the GLONASS L3 and Galileo E5b bands. Russian rockets will help launch Galileo satellites, including a Soyuz-Fregat used in the successful first launch of GIOVE-A on December 28 (See article on page 16.), and laser retro-reflectors produced by NIIPP, the Russian Scientific-Research Institute of Precision Instrument-Making, will measure the altitude of both GIOVE spacecraft to within centimeters.

By

The Perils (and Pearls) of Galileo

Successful launch of the first Galileo satellite on December 28 marks the culmination of a process that began almost exactly 13 years earlier.

Successful launch of the first Galileo satellite on December 28 marks the culmination of a process that began almost exactly 13 years earlier.

On January 19 the European Space Agency and Galileo Industries GmbH, the European company steering a consortium of more than 100 subcontractors, signed a €950 million (US$1.15 billion) contract that will pave the way for the operational deployment of Galileo. The contract calls for a mini-constellation of four satellites backed by an extensive network of tracking and control stations that will validate the design of the Galileo space and ground infrastructure. Four satellites are the minimum required to generate three-dimensional positioning and precise timing over the selected showcase sites.

In December 1992, however, Galileo was just a glimmer in a few visionaries’ eyes. That was the month that two European Commission (EC) directorates-general — those for transport and science, research, and development – decided to fund a modest study of satellite navigation options for Europe. The intervening years produced a kind of programmatic version of “The Perils of Pauline,” the cliffhanger serial movie in which each installment ends with the title character – a perpetual damsel in distress – placed in a situation that threatens her imminent demise, only to be rescued at the beginning of the next episode.

Galileo’s most recent “peril” revolved around a dispute between Germany and other members of the European Union (EU) over the allocation of contracts and responsibilities that they would have during the deployment phase of the system. A December 5 agreement on sharing Galileo operational and control centers among five nations rescued Galileo from the months-long impasse.

The next (but probably not final) act of the “Perils of Galileo” remains to be played out: the signing of an agreement with a consortium of companies that will complete the development of the space and ground segments and operate the system for the next 20 years. Current estimates place that milestone in the latter half of 2006, reflecting delays that have dogged the program since its inception and finally pushed its timeline for completion to 2010 – two years beyond the date long proposed by the EC and its Galileo partner, the European Space Agency (ESA).

Nonetheless, the launch of GIOVE-A, the experimental Galileo spacecraft built by Surrey Satellite Technology Ltd., marks a major—and probably irrevocable—step forward for the European GNSS. The start of transmissions from GIOVE-A and a second testbed satellite, GIOVE-B, manufactured by Galileo Industries, will allow the system to lay claim to use of the radio frequencies allocated at World Radio Conferences in 2000 and reaffirmed in 2003.

They will also allow ESA to evaluate on-orbit performance of several new satellite components and technologies and, significantly, also enable GNSS receiver developers to work with real signals in space. For example, GIOVE-B will be launched in the first half of 2006 and will have a passive hydrogen-maser clock as an additional payload, the first such clock ever flown into space. Current spaceborne clocks are cesium and rubidium frequency standards. Galileo satellites will also have rubidium clocks on board.

Political Merry-Go-Round

Several aspects of the €3.8 billion (US$4.6 billion) Galileo program distinguish it from its U.S. and Russian counterparts, GPS and GLONASS: full civilian control, a so-called public-private partnership (PPP) in its deployment and operation, international participation, and a multitude of services, including some that will be fee-based with guaranteed delivery of service. Indeed, the political challenges have long eclipsed the technical ones.

Fusing the interests of 15 (later 25) EU member-states, three additional non-EU ESA participants, and their leading industrial factors into a single enterprise has required a sustained exercise in what’s sometimes called “concertation.” Galileo represents the first Europe-wide infrastructure project and, consequently, challenged the EU and ESA to achieve a new level of political capability — within themselves and between one another. After the original 1992 satnav study, it took nearly seven years before Galileo even got its name in a February 1999 EC document, “Involving Europe in a New Generation of Satellite Navigation Services.”

Until then the program had been known rather generically as GNSS 2, distinguishing it from GNSS 1, the European Geostationary Navigation Overlay Service (EGNOS), a satellite-based augmentation of GPS and GLONASS. In May 1999 the ESA Ministerial Council approved the GalileoSat program; in June 1999 the EU Transport Council endorsed a first resolution on Galileo.

A November 22, 2000, EC communication to the European Parliament and European Council laid out the financing, organization, R&D, and implementation plan. In November 2001 the ESA Ministerial Council approved the development of Galileo (Phase-C/D, with a budget of €550 million). In May 2002 the Council authorized a joint undertaking, an institutional entity envisioned under Article 171 of the European Community Treaty but only implemented once previously, which allows the EU to collaborate in a single enterprise with non-EU bodies.

ESA and the EC (on behalf of the EU) comprised the initial membership of the Galileo Joint Undertaking (GJU), which has as its primary task the completion of a concession contract. Subsequently, non-EU governmental organizations representing China and Israel signed on with the GJU. Other nations, including Ukraine and India, are expected to join soon. The concessionaire will complete deployment of the Galileo satellites and ground infrastructure and operate the system over the next 20 years, monitored by a Galileo Supervisory Authority.

Final action to deploy the system only came with European Council action on December 10, 2004. Along the way, however, the growing EU-ESA cooperation on Galileo led to a broader initiative on a common European space policy. Late in 2003 the two institutions issued a White Paper on Space and signed a “framework agreement” for cooperation in space activities. Under the agreement, “the EC and ESA will launch and fund joint projects, participate in each other’s schemes, create common management agencies, carry out studies and jointly organize conferences and training of scientists, exchange and share experts, equipment and materials, and access to facilities.”

The overall cost of the Galileo system was first estimated at €3.4 billion, with a public investment for the development and validation phase of €1.1 billion divided between the EC and ESA. This phase was re-evaluated in 2005 at €1.5 billion.

The Art of the Deal

Currently, a “grand coalition” of leading European aerospace, telecommunications, and banking interests is negotiating with the GJU in a formerly competitive process that saw the merger of the two leading consortia in March 2005. Last month’s agreement on Galileo’s operational and administrative direction saw Eurely — a grouping led by Alcatel, Finmeccanica, and Vinci Networks — and the iNavSat consortium headed by the European Aeronautic Defense and Space Company (EADS), Thales, and Inmarsat, joined by a new consortium of Munich, Germany–based companies. The latter group, TeleOp, includes the commercial arm of the German Space Agency (DLR), the LfA Förderbank Bayern, and subsidiaries of EADS and T-Systems.

But the agreement didn’t come easily. Multi-sided talks by representatives of eight companies and five governments (France, Germany, United Kingdom, Italy, and Spain) would reach tentative accords at one level or with one group of negotiators but then fall apart when brought to another forum. Coloring the dialog were national ambitions to be seen as leading the Galileo program and the sensitivity to geographic return — the practice of spreading contracts and revenues among program participants in a proportion close to the contributions made by the various nations.

“Finally, we realized we can’t keep on fighting over these assets without getting an agreement,” Martin Ripple, director of Galileo Program for EADS Space Services, told Inside GNSS. “So, EADS said let’s put the all industrial players in one room and get the five governmental players into the same room. And lock them in until they come out with something.”

What they came out of the room with was a plan that reallocated key components of Galileo operations among the five leading space nations in Europe. The headquarters of the Galileo concessionaire will be located in Toulouse, France, with administrative and market development responsibilities. Inmarsat will have overall management leadership of the operations company based in the United Kingdom and responsible for global network operations, including performance monitoring and operations security. The two control centers (for constellation and mission) will be located in Germany (near Munich in Bavaria) and Italy (Fucino space center in Abruzzo region) along with two performance evaluation centers supporting the concessionaire headquarters. Spain will host backup control centers as well as facilities related to Galileo safety-critical applications.

“It’s a major step toward a concession contract,” says Ripple.

The Same, Only Different

On the technical side of the program, Galileo has entered the in-orbit validation (IOV) and development phase using the two GIOVE experimental satellites to test out ESA’s spacecraft design and ground control. The IOV phase will conclude with the deployment of four operational satellites in 2008. According to the current schedule, an additional 26 satellites will then be launched over the following two years with full operational capability (FOC) declared in 2010.

Galileo operational satellites will transmit signals in a variety of bands clustered around the 1176-1207 MHz spectrum near the GPS L2 frequency, 1775.42 MHz centered at the GPS L1 frequency, and 1278.75 MHz. The latter band lies at some distance from the GPS L2 signals at 1227.6 MHz, but would fall within one of the bands that Russia is considering for the third civil GLONASS signal that will begin broadcasting with launch of its new satellites in 2008.

Galileo signal structures include a combination of biphase shift keying (BPSK) and binary offset carrier (BOC) designs. (Current GPS signals are BPSK variations, but future signals will also be BOC-based.) Recently, the Galileo Signal Task Force has proposed the addition of a composite binary coded symbols (CBCS) design that superposes BOC and a binary coded symbol waveform with the same chipping rate.

Galileo will offer five services: a free open service; a fee-based, encrypted commercial service offering higher accuracy and service guarantees; a safety of life service the includes signal authentication and integrity alerts (targeting, for example, commercial aviation); a search and rescue service operating in near-real time with a return communications link possible; and an encrypted governmental service known as the “public regulated service” or PRS, which will be used by public safety agencies and, conceivably, military forces. Certification for safety of life services is scheduled to occur within a year after FOC.

This final point and the liability issues that it raises probably is the largest complication for the final negotiations in the concession contract. Sizing and sharing the risk associated with service guarantees introduces a problematical element to the Galileo project not faced by its GPS and GLONASS counterparts. As one participant in the deliberations has posed the dilemma: What do you do if a hiker in the Rocky Mountains gets lost and sues Galileo in front of a U.S. judge? Once signed, the concession agreement will lead to the phasing out of the GJU and the advent of the Galileo Supervisory Authority’s role. The concession contract also represents the turning point of the public-private partnership that marks Galileo as a different kind of beast from publicly funded GPS and GLONASS. The framework for negotiating the concession contract assumes a two-thirds contribution from the private sector for the €2.2 billion deployment phase and all of the €220 million annual expense of operating and maintaining Galileo.

Given the past history of the European GNSS initiative persevering and escaping perils — including self-created ones, the Galileo project will probably manage to solve the PPP riddle and get on with the (comparatively) simple task of building and operating a system.

By
1 12 13 14
IGM_e-news_subscribe