GLONASS

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
GLONASS
File:Glonass logo.jpg
GLONASS logo
Country of origin Russia
Operator(s) VKO
Type Military
Status Operational
Coverage Global
Precision 5–10 meters
Constellation size
Total satellites 24
Satellites in orbit 29
First launch October 1982
Last launch November 2014
Orbital characteristics
Regime(s) 3x MEO
Orbital height 19,130 km

Lua error in package.lua at line 80: module 'strict' not found.

A model of a GLONASS-K satellite displayed at CeBit 2011

GLONASS (Russian: ГЛОНАСС, IPA: [ɡlɐˈnas]; Глобальная навигационная спутниковая система; transliteration Globalnaya navigatsionnaya sputnikovaya sistema), or "GLObal NAvigation Satellite System", is a space-based satellite navigation system operating in the radionavigation-satellite service and used by the Russian Aerospace Defence Forces. It provides an alternative to GPS and is the second alternative navigational system in operation with global coverage and of comparable precision.

Manufacturers of GPS devices say that adding GLONASS made more satellites available to them, meaning positions can be fixed more quickly and accurately, especially in built-up areas where the view to some GPS satellites is obscured by buildings. Smartphones generally tend to use the same chipsets and since the versions used since 2015 receive GLONASS signals, smartphones using such chips receive GLONASS positioning information along with GPS.

Development of GLONASS began in the Soviet Union in 1976. Beginning on 12 October 1982, numerous rocket launches added satellites to the system until the constellation was completed in 1995. After a decline in capacity during the late 1990s, in 2001, under Vladimir Putin's presidency, the restoration of the system was made a top government priority and funding was substantially increased. GLONASS is the most expensive program of the Russian Federal Space Agency, consuming a third of its budget in 2010.

By 2010, GLONASS had achieved 100% coverage of Russia's territory and in October 2011, the full orbital constellation of 24 satellites was restored, enabling full global coverage. The GLONASS satellites' designs have undergone several upgrades, with the latest version being GLONASS-K.

History

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.

Inception and design

A GLONASS satellite

The first satellite-based radio navigation system developed in the Soviet Union was Tsiklon, which had the purpose of providing ballistic missile submarines a method for accurate positioning. 31 Tsiklon satellites were launched between 1967 and 1978. The main problem with the system was that, although highly accurate for stationary or slow-moving ships, it required several hours of observation by the receiving station to fix a position, making it unusable for many navigation purposes and for the guidance of the new generation of ballistic missiles.[1] In 1968–1969, a new navigation system, which would support not only the navy, but also the air, land and space forces, was conceived. Formal requirements were completed in 1970; in 1976, the government made a decision to launch development of the "Unified Space Navigation System GLONASS".[2]

The task of designing GLONASS was given to a group of young specialists at NPO PM in the city of Krasnoyarsk-26 (today called Zheleznogorsk). Under the leadership of Vladimir Cheremisin, they developed different proposals, from which the institute's director Grigory Chernyavsky selected the final one. The work was completed in the late 1970s; the system consists of 24 satellites operating at an altitude of 20,000 kilometres (12,000 mi) in medium circular orbit. It would be able to promptly fix the receiving station's position based on signals from four satellites, and also reveal the object's speed and direction. The satellites would be launched three at a time on the heavy-lift Proton rocket. Due to the large number of satellites needed for the program, NPO PM delegated the manufacturing of the satellites to PO Polyot in Omsk, which had better production capabilities.[3][4]

Originally, GLONASS was designed to have an accuracy of 65 metres (213 ft), but in reality it had an accuracy of 20 metres (66 ft) in the civilian signal and 10 metres (33 ft) in the military signal.[5] The first generation GLONASS satellites were 7.8 metres (26 ft) tall, had a width of 7.2 metres (24 ft), measured across their solar panels, and a mass of 1,260 kilograms (2,780 lb).[5]

Achieving full orbital constellation

In the early 1980s, NPO PM received the first prototype satellites from PO Polyot for ground tests. Many of the produced parts were of low quality and NPO PM engineers had to perform substantial redesigning, leading to a delay.[3] On 12 October 1982, three satellites, designated Kosmos-1413, Kosmos-1414, and Kosmos-1415 were launched aboard a Proton rocket. As only one GLONASS satellite was ready in time for the launch instead of the expected three, it was decided to launch it along with two mock-ups. The USA media reported the event as a launch of one satellite and "two secret objects." For a long time, the USA could not find out the nature of those "objects". The Telegraph Agency of the Soviet Union (TASS) covered the launch, describing GLONASS as a system "created to determine positioning of civil aviation aircraft, navy transport and fishing-boats of the Soviet Union".[3]

From 1982 to April 1991, the Soviet Union successfully launched a total of 43 GLONASS-related satellites plus five test satellites. When the Soviet Union disintegrated in 1991, twelve GLONASS satellites in two planes were operational; enough to allow limited use of the system (to cover the entire territory of the Union, 18 satellites would have been necessary.) The Russian Federation took over control of the constellation and continued its development.[4] In 1993, the system, now consisting of 12 satellites, was formally declared operational[6] and in December 1995 it was brought to a fully operational constellation of 24 satellites. This brought the precision of GLONASS on a par with the USA GPS system, which had achieved full operation а year earlier.[4]

Economic crisis

Since the first generation satellites operated for three years each, to keep the system at full capacity, two launches per year would have been necessary to maintain the full network of 24 satellites. However, in the financially difficult period of 1989–1999, the space program's funding was cut by 80% and Russia consequently found itself unable to afford this launch rate. After the full complement was achieved in December 1995, there were no further launches until December 1999. As a result, the constellation reached its lowest point of just six operational satellites in 2001. As a prelude to demilitarisation, responsibility of the program was transferred from the Ministry of Defence to Russia's civilian space agency Roscosmos.[5]

Renewed efforts and modernization

President Vladimir Putin with a GLONASS car navigation device. As President, Putin paid special attention to the development of GLONASS.

In the 2000s, under Vladimir Putin's presidency, the Russian economy recovered and state finances improved considerably. Putin himself took special interest in GLONASS[5] and the system's restoration was made one of the government's top priorities.[7] For this purpose, on August 2001, the Federal Targeted Program "Global Navigation System" 2002–2011 (Government Decision No. 587) was launched. The program was given a budget of $420 million[8] and aimed at restoring the full constellation by 2009.

On 10 December 2003, the second generation satellite design, GLONASS-M, was launched for the first time. It had a slightly larger mass than the baseline GLONASS, standing at 1,415 kilograms (3,120 lb), but it had seven years lifetime, four years longer than the lifetime of the original GLONASS satellite, decreasing the required replacement rate. The new satellite also had better accuracy and ability to broadcast two extra civilian signals.

In 2006, Defence Minister Sergey Ivanov ordered one of the signals (with an accuracy of 30 metres (98 ft)) to be made available to civilian users. Putin, however, was not satisfied with this, and demanded that the whole system should be made fully available to everyone. Consequently, on 18 May 2007, all restrictions were lifted.[6][9] The accurate, formerly military-only signal with a precision of 10 metres (33 ft), has since then been freely available to civilian users.

During the middle of the first decade of the 21st century, the Russian economy boomed, resulting in substantial increases in the country's space budget. In 2007, the financing of the GLONASS program was increased considerably; its budget was more than doubled. While in 2006 the GLONASS had received $181 million from the federal budget, in 2007 the amount was increased to $380 million.[6]

In the end, 140.1 billion rubles ($4.7 billion) were spent on the program 2001–2011, making it Roscosmos' largest project and consuming a third of its 2010 budget of 84.5 billion rubles.[10]

For the period of 2012 to 2020 320 billion rubles ($10 billion) were allocated to support the system.[11]

Restoring full capacity

In June 2008, the system consisted of 16 satellites, 12 of which were fully operational at the time. At this point, Roscosmos aimed at having a full constellation of 24 satellites in orbit by 2010, one year later than previously planned.[12]

In September 2008, Prime Minister Vladimir Putin signed a decree allocating additional 67 billion rubles ($2.6 billion) to GLONASS from the federal budget.[13]

Promoting commercial use

Although the GLONASS constellation has reached global coverage, its commercialisation, especially development of the user segment, has been lacking compared to the American GPS system. For example, the first commercial Russian-made GLONASS navigation device for cars, Glospace SGK-70, was introduced in 2007, but it was much bigger and costlier than similar GPS receivers.[7] In late 2010, there were only a handful of GLONASS receivers on the market, and few of them were meant for ordinary consumers. To improve the situation, the Russian government has been actively promoting GLONASS for civilian use.[14]

To improve development of the user segment, on 11 August 2010, Sergei Ivanov announced a plan to introduce a 25% import duty on all GPS-capable devices, including mobile phones, unless they are compatible with GLONASS. The government also planned to force all car manufacturers in Russia to support GLONASS starting from 2011. This would affect all car makers, including foreign brands like Ford and Toyota, which have car assembly facilities in Russia.[15]

GPS and phone baseband chips from major vendors Qualcomm, Exynos and Broadcom[16] all support GLONASS in combination with GPS.

In April 2011, Sweden's Swepos—a national network of satellite reference stations that provides real-time positioning data with meter accuracy—became the first known foreign company to use GLONASS.[17]

Smartphones and Tablets also saw implementation of GLONASS support in 2011 with devices released that year from Xiaomi Tech Company (Xiaomi Phone 2), Sony Ericsson, Samsung (Galaxy Note Galaxy Note II, Galaxy SII, the Google Nexus 10 in late 2012), Asus, Apple (iPhone 4S and iPad Mini in late 2012) and HTC adding support for the system allowing increased accuracy and lock on speed in difficult conditions.[18][19][20] For a more complete list of smartphones see List of smartphones using GLONASS Navigation and for a more complete list of tablets see the text GLONASS in the GPS column in the Comparison of tablet computers.

Finishing the constellation

Russia's aim of finishing the constellation in 2010 suffered a setback when a December 2010 launch of three GLONASS-M satellites failed. The Proton-M rocket itself performed flawlessly, but the upper stage Blok DM3 (a new version that was to make its maiden flight) was loaded with too much fuel due to a sensor failure. As a result, the upper stage and the three satellites crashed into the Pacific Ocean. Kommersant estimated that the launch failure cost up to $160 million.[21] Russian President Dmitry Medvedev ordered a full audit of the entire program and an investigation into the failure.[22]

Following the mishap, Roscosmos activated two reserve satellites and decided to make the first improved GLONASS-K satellite, to be launched in February 2011, part of the operational constellation instead of mainly for testing as was originally planned. This would bring the total number of satellites to 23, obtaining almost complete worldwide coverage.[23] The GLONASS-K2 was originally scheduled to be launched by 2013, however by 2012 was not expected to be launched until 2015.[24]

In 2010, President Dmitry Medvedev ordered the government to prepare a new federal targeted program for GLONASS, covering the years 2012–2020. The original 2001 program is scheduled to end in 2011.[21] On 22 June 2011, Roscosmos revealed that the agency was looking for a funding of 402 billion rubles ($14.35 billion) for the program. The funds would be spent on maintaining the satellite constellation, on developing and maintaining navigational maps as well as on sponsoring supplemental technologies to make GLONASS more attractive to users.[25]

On 2 October 2011 the 24th satellite of the system, a GLONASS-M, was successfully launched from Plesetsk Cosmodrome and is now in service.[26] This made the GLONASS constellation fully restored, for the first time since 1996.[27]

On 5 November 2011 the Proton-M booster successfully put three GLONASS-M units in final orbit.[28]

On Monday 28 November 2011, a Soyuz rocket, launched from the Plesetsk Cosmodrome Space Centre, placed a single GLONASS-M satellite into orbit into Plane 3.

On 26 April 2013 a single GLONASS-M satellite was delivered to the orbit by Soyuz rocket from Plesetsk Cosmodrome, restoring the constellation to 24 operational satellites, the minimum to provide global coverage.[29]

On 2 July 2013 a Proton-M rocket, carrying 3 GLONASS-M satellites, crashed during takeoff from Baikonur Cosmodrome. It veered off the course just after leaving the pad and plunged into the ground nose first. The rocket employed a DM-03 booster, for the first time since the December 2010 launch, when the vehicle had also failed, resulting in a loss of another 3 satellites.[30]

However, as of 2014, while the system was completed from technical point of view, the operational side was still not closed by the Ministry of Defense and its formal status was still "in development".[31]

System description

Comparison of geostationary, GPS, GLONASS, Galileo, Compass (MEO), International Space Station, Hubble Space Telescope and Iridium constellation orbits, with the Van Allen radiation belts and the Earth to scale.[lower-alpha 1] The Moon's orbit is around 9 times larger than geostationary orbit.[lower-alpha 2] (In the SVG file, hover over an orbit or its label to highlight it; click to load its article.)

GLONASS is a global satellite navigation system, providing real time position and velocity determination for military and civilian users. The satellites are located in middle circular orbit at 19,100 kilometres (11,900 mi) altitude with a 64.8 degree inclination and a period of 11 hours and 15 minutes.[32][33] GLONASS' orbit makes it especially suited for usage in high latitudes (north or south), where getting a GPS signal can be problematic.[5][7] The constellation operates in three orbital planes, with eight evenly spaced satellites on each.[33] A fully operational constellation with global coverage consists of 24 satellites, while 18 satellites are necessary for covering the territory of Russia. To get a position fix the receiver must be in the range of at least four satellites.[32]

Signal

FDMA

A Russian military rugged, combined GLONASS/GPS receiver

GLONASS satellites transmit two types of signal: open standard-precision signal L1OF/L2OF, and obfuscated high-precision signal L1SF/L2SF.

The signals use similar DSSS encoding and binary phase-shift keying (BPSK) modulation as in GPS signals. All GLONASS satellites transmit the same code as their standard-precision signal; however each transmits on a different frequency using a 15-channel frequency division multiple access (FDMA) technique spanning either side from 1602.0 MHz, known as the L1 band. The center frequency is 1602 MHz + n × 0.5625 MHz, where n is a satellite's frequency channel number (n=−7,−6,−5,...0,...,6, previously n=0,...,13). Signals are transmitted in a 38° cone, using right-hand circular polarization, at an EIRP between 25 to 27 dBW (316 to 500 watts). Note that the 24-satellite constellation is accommodated with only 15 channels by using identical frequency channels to support antipodal (opposite side of planet in orbit) satellite pairs, as these satellites are never both in view of an earth-based user at the same time.

The L2 band signals use the same FDMA as the L1 band signals, but transmit straddling 1246 MHz with the center frequency 1246 MHz + n×0.4375 MHz, where n spans the same range as for L1.[34] In the original GLONASS design, only obfuscated high-precision signal was broadcast in the L2 band, but starting with GLONASS-M, an additional civil reference signal L2OF is broadcast with an identical standard-precision code to the L1OF signal.

A combined GLONASS/GPS Personal Radio Beacon

The open standard-precision signal is generated with modulo-2 addition (XOR) of 511 kbit/s pseudo-random ranging code, 50 bit/s navigation message, and an auxiliary 100 Hz meander sequence (Manchester code), all generated using a single time/frequency oscillator. The pseudo-random code is generated with a 9-stage shift register operating with a period of 1 ms.

The navigational message is modulated at 50 bits per second. The superframe of the open signal is 7500 bits long and consists of 5 frames of 30 seconds, taking 150 seconds (2.5 minutes) to transmit the continuous message. Each frame is 1500 bits long and consists of 15 strings of 100 bits (2 seconds for each string), with 85 bits (1.7 seconds) for data and check-sum bits, and 15 bits (0.3 seconds) for time mark. Strings 1-4 provide immediate data for the transmitting satellite, and are repeated every frame; the data include ephemeris, clock and frequency offsets, and satellite status. Strings 5-15 provide non-immediate data (i.e. almanac) for each satellite in the constellation, with frames I-IV each describing five satellites, and frame V describing remaining four satellites.

The ephemerides are updated every 30 minutes using data from the Ground Control segment; they use Earth Centred Earth Fixed (ECEF) Cartesian coordinates in position and velocity, and include lunisolar acceleration parameters. The almanac uses modified Keplerian parameters and is updated daily.

The more accurate high-precision signal is available for authorized users, such as the Russian Military, yet unlike the US P(Y) code, which is modulated by an encrypting W code, the GLONASS restricted-use codes are broadcast in the clear using only security through obscurity. The details of the high-precision signal have not been disclosed. The modulation (and therefore the tracking strategy) of the data bits on the L2SF code has recently changed from unmodulated to 250 bit/s burst at random intervals. The L1SF code is modulated by the navigation data at 50 bit/s without a Manchester meander code.

The high-precision signal is broadcast in phase quadrature with the standard-precision signal, effectively sharing the same carrier wave, but with a ten-times-higher bandwidth than the open signal. The message format of the high-precision signal remains unpublished, although attempts at reverse-engineering indicate that the superframe is composed of 72 frames, each containing 5 strings of 100 bits and taking 10 seconds to transmit, with total length of 36 000 bits or 720 seconds (12 minutes) for the whole navigational message. The additional data are seemingly allocated to critical Luni-Solar acceleration parameters and clock correction terms.

Accuracy

At peak efficiency, the standard-precision signal offers horizontal positioning accuracy within 5–10 meters, vertical positioning within 15 metres (49 ft), a velocity vector measuring within 10 centimetres per second (3.9 in/s), and timing within 200 ns, all based on measurements from four first-generation satellites simultaneously;[35] newer satellites such as GLONASS-M improve on this.

GLONASS uses a coordinate datum named "PZ-90" (Earth Parameters 1990 – Parametry Zemli 1990), in which the precise location of the North Pole is given as an average of its position from 1990 to 1995. This is in contrast to the GPS's coordinate datum, WGS 84, which uses the location of the North Pole in 1984. As of 17 September 2007 the PZ-90 datum has been updated to version PZ-90.02 which differ from WGS 84 by less than 40 cm (16 in) in any given direction. Since 31 December 2013, version PZ-90.11 is being broadcast, which is aligned to the International Terrestrial Reference System at epoch 2011.0 at the centimeter level.[36][37]

CDMA

Since 2008, new CDMA signals are being researched for use with GLONASS.[38][39][40][41][42][43][44][45]

According to preliminary statements from GLONASS developers, there will be three open and two restricted CDMA signals. The open signal L3OC is centered at 1202.025 MHz and uses BPSK(10) modulation for both data and pilot channels; the ranging code transmits at 10.23 million chips per second, modulated onto the carrier frequency using QPSK with in-phase data and quadrature pilot. The data is error-coded with 5-bit Barker code and the pilot with 10-bit Neuman-Hoffman code.[46][47]

Open L1OC and restricted L1SC signals are centered at 1600.995 MHz, and open L2OC and restricted L2SC signals are centered at 1248.06 MHz, overlapping with GLONASS FDMA signals. Open signals L1OC and L2OC use time-division multiplexing to transmit pilot and data signals, with BPSK(1) modulation for data and BOC(1,1) modulation for pilot; wide-band restricted signals L1SC and L2SC use BOC (5, 2.5) modulation for both data and pilot, transmitted in quadrature phase to the open signals; this places peak signal strength away from the center frequency of narrow-band open signals.[44][48]

Binary phase-shift keying (BPSK) is used by standard GPS and GLONASS signals, however both BPSK and quadrature phase-shift keying (QPSK) can be considered as variations of quadrature amplitude modulation (QAM), specifically QAM-2 and QAM-4. Binary offset carrier (BOC) is the modulation used by Galileo, modernized GPS, and COMPASS.

The navigational message of the L3OC signal is transmitted at 100 bit/s. The navigational frame is 15 seconds (1500 bits) long and includes 5 strings of symbols each taking 3 seconds (300 bits); a frame contains ephemerides for the current satellite and part of the almanac for three satellites. The superframe consists of 8 navigational frames, so it takes 120 seconds (2 minutes) to transmit 12000 bits of almanac for all current 24 satellites. In the future, the superframe will be expanded to 10 frames or 15000 bits (150 seconds or 2.5 minutes) of data to cover full 30 satellites. The system time marker is transmitted with each string; UTC leap second correction is achieved by shortening or lengthening (zero-padding) the final string of the day by one second (100 bits), with shortened strings being discarded by the receiver.[49] The strings have a version tag to facilitate forward compatibility: future upgrades to the message format will not break older equipment, which will continue to work by ignoring new data (as long as the constellation still transmits old string types), but up-to-date equipment will be able to use additional information from newer satellites.[50]

Roadmap of GLONASS modernization
Satellite series Launch Current status Clock error FDMA signals CDMA signals Interoperability CDMA signals
1602 + n×0.5625 MHz 1246 + n×0.4375 MHz 1600.995 MHz 1248.06 MHz 1202.025 MHz 1575.42 MHz 1207.14 MHz 1176.45 MHz
GLONASS 1982–2005 Out of service 5×10−13 L1OF, L1SF L2SF
GLONASS-M 2003–2016 In service 1×10−13 L1OF, L1SF L2OF, L2SF L3OС
GLONASS-K1 2011, 2014 In service 5×10−14...1×1013 L1OF, L1SF L2OF, L2SF L3OС
GLONASS-K2 2018–2024 Design phase 5×10−14 L1OF, L1SF L2OF, L2SF L1OC, L1SC L2SC L3OC
GLONASS-KМ 2025– Research phase L1OF, L1SF L2OF, L2SF L1OC, L1SC L2OC, L2SC L3OC, L3SC L1OCM L3OCM L5OCM
"O": open signal (standard precision), "S": obfuscated signal (high precision); "F":FDMA, "С":CDMA; n=−7,−6,−5,...,6

Glonass-M series will include L3OC signal from 2014

Glonass-K1 test satellite launched in 2011 introduced L3OC signal. They will be used as fleet replacement from 2018 until the Glonass-K2 are validated.[51] The final Glonass-M satellites launched in 2014–2017 will also include L3OC signal.

Glonass-K2 satellites, to be launched in 2018, will feature a full suite of modernized CDMA signals in the existing L1 and L2 bands, which includes L1SC, L1OC, and L2SC, as well as the L3OC signal. Glonass-K2 should gradually replace existing satellites starting from 2017, when Glonass-M launches will cease.[51]

Glonass-KM satellites will be launched by 2025. Additional open signals are being studied for these satellites, based on the same frequencies and formats as GPS signals L5 and L1C and corresponding Galileo/COMPASS signals E1, E5a and E5b. These signals include:

  • The open signal L1OCM will use BOC(1,1) modulation centered at 1575.42 MHz, similar to modernized GPS signal L1C and Galileo/COMPASS signal E1;
  • The open signal L5OCM will use BPSK(10) modulation centered at 1176.45 MHz, similar to the GPS "Safety of Life" (L5) and Galileo/COMPASS signal E5a;[52]
  • The open signal L3OCM will use BPSK(10) modulation centered at 1207.14 MHz, similar to Galileo/COMPASS signal E5b.[40]

Such an arrangement will allow easier and cheaper implementation of multi-standard GNSS receivers.

With the introduction of CDMA signals, the constellation will be expanded to 30 active satellites by 2025; this may require eventual deprecation of FDMA signals.[53] The new satellites will be deployed into three additional planes, bringing the total to six planes from the current three—aided by System for Differential Correction and Monitoring (SDCM), which is a GNSS augmentation system based on a network of ground-based control stations and communication satellites Luch 5A and Luch 5B.[54][55] Additional satellites may use Molniya orbit, Tundra orbit, geosynchronous orbit, or inclined orbit to offer increased regional availability, similar to Japanese QZSS system.[40][49]

Satellites

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The main contractor of the GLONASS program is Joint Stock Company Reshetnev Information Satellite Systems (formerly called NPO-PM). The company, located in Zheleznogorsk, is the designer of all GLONASS satellites, in cooperation with the Institute for Space Device Engineering (ru:РНИИ КП) and the Russian Institute of Radio Navigation and Time. Serial production of the satellites is accomplished by the company PC Polyot in Omsk.

Over the three decades of development, the satellite designs have gone through numerous improvements, and can be divided into three generations: the original GLONASS (since 1982), GLONASS-M (since 2003) and GLONASS-K (since 2011). Each GLONASS satellite has a GRAU designation 11F654, and each of them also has the military "Cosmos-NNNN" designation.[56]

First generation

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The true first generation of GLONASS (also called Uragan) satellites were all three-axis stabilized vehicles, generally weighing 1,250 kilograms (2,760 lb) and were equipped with a modest propulsion system to permit relocation within the constellation. Over time they were upgraded to Block IIa, IIb, and IIv vehicles, with each block containing evolutionary improvements.

Six Block IIa satellites were launched in 1985–1986 with improved time and frequency standards over the prototypes, and increased frequency stability. These spacecraft also demonstrated a 16-month average operational lifetime. Block IIb spacecraft, with a two-year design lifetimes, appeared in 1987, of which a total of 12 were launched, but half were lost in launch vehicle accidents. The six spacecraft that made it to orbit worked well, operating for an average of nearly 22 months.

Block IIv was the most prolific of the first generation. Used exclusively from 1988 to 2000, and continued to be included in launches through 2005, a total of 25 satellites were launched. The design life was three years, however numerous spacecraft exceeded this, with one late model lasting 68 months.[57]

Block II satellites were typically launched three at a time from the Baikonur Cosmodrome using Proton-K Blok-DM-2 or Proton-K Briz-M boosters. The only exception was when, on two launches, an Etalon geodetic reflector satellite was substituted for a GLONASS satellite.

Second generation

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The second generation of satellites, known as Glonass-M, were developed beginning in 1990 and first launched in 2003. These satellites possess a substantially increased lifetime of seven years and weigh slightly more at 1,480 kilograms (3,260 lb). They are approximately 2.4 m (7 ft 10 in) in diameter and 3.7 m (12 ft) high, with a solar array span of 7.2 m (24 ft) for an electrical power generation capability of 1600 watts at launch. The aft payload structure houses 12 primary antennas for L-band transmissions. Laser corner-cube reflectors are also carried to aid in precise orbit determination and geodetic research. On-board cesium clocks provide the local clock source. Glonass-M consisting 31 satellites ranging from satellite index 21 - 92 and with 4 spare active satellites.

A total of 41 second generation satellites were launched through the end of 2013. As with the previous generation, the second generation spacecraft were launched in triplets using Proton-K Blok-DM-2 or Proton-K Briz-M boosters. Some where launched alone with Soyuz-2-1b/Fregat

On July 30, 2015, ISS Reshtev announced that it had completed the last GLONASS-M (N° 61) spacecraft and it was putting it in storage waiting for launch, along an additional eight already built satellites.[58][59]

Third generation

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

GLONASS-K is a substantial improvement of the previous generation: it is the first unpressurised GLONASS satellite with a much reduced mass (750 kilograms (1,650 lb) versus 1,450 kilograms (3,200 lb) of GLONASS-M). It has an operational lifetime of 10 years, compared to the 7-year lifetime of the second generation GLONASS-M. It will transmit more navigation signals to improve the system's accuracy—including new CDMA signals in the L3 and L5 bands, which will use modulation similar to modernized GPS, Galileo, and Compass. Glonass-K consist of 26 satellites having satellite index 65-98 and widely used in Russian Military space.[60][61][62] The new satellite's advanced equipment—made solely from Russian components—will allow the doubling of GLONASS' accuracy.[32] As with the previous satellites, these are 3-axis stabilized, nadir pointing with dual solar arrays.[citation needed] The first GLONASS-K satellite was successfully launched on 26 February 2011.[60][63]

Due to their weight reduction, GLONASS-K spacecraft can be launched in pairs from the Plesetsk Cosmodrome launch site using the substantially lower cost Soyuz-2.1b boosters or in six-at-once from the Baikonur Cosmodrome using Proton-K Briz-M launch vehicles.[32][33]

Ground control

The ground control segment of GLONASS is almost entirely located within former Soviet Union territory, except for a station in Brasilia, Brazil.[64] The Ground Control Center and Time Standards is located in Moscow and the telemetry and tracking stations are in Saint Petersburg, Ternopil, Eniseisk and Komsomolsk-na-Amure.[65]

Receivers

Septentrio, Topcon, C-Nav, JAVAD, Magellan Navigation, Novatel, Leica Geosystems, Hemisphere GNSS and Trimble Inc produce GNSS receivers making use of GLONASS. NPO Progress describes a receiver called GALS-A1, which combines GPS and GLONASS reception. SkyWave Mobile Communications manufactures an Inmarsat-based satellite communications terminal that uses both GLONASS and GPS.[66] As of 2011, some of the latest receivers in the Garmin eTrex line also support GLONASS (along with GPS).[67] Garmin also produce a standalone Bluetooth receiver, the GLOTM for Aviation, which combines GPS, WAAS and GLONASS.[68] Various smartphones from 2011 onwards have integrated GLONASS capability, including devices from Xiaomi Tech Company (Xiaomi Phone 2), Sony Ericsson,[69] ZTE, Huawei,[70] Samsung (Galaxy Note, Galaxy Note II, Galaxy S3, Galaxy S4),[71] Apple (iPhone 4S, iPhone 5, iPhone 5C, iPhone 5S, iPhone 6 and iPhone 6 Plus, iPhone 6s and iPhone 6s Plus),[72] iPad Mini (LTE models only), iPad Mini 2 (LTE models only), iPad Mini 3 (LTE models only), iPad Mini 4 (LTE models only)[73] iPad (3rd generation and 4th Generation, 4G and LTE models only [respectively]), iPad Air (LTE models only) and iPad Air 2 (LTE models only) and Apple's flagship iPad Pro,[74] HTC,[75] LG,[76] Motorola[77] and Nokia.[78]

Status

Availability

As of 19 June 2015, the GLONASS constellation status is:

28 SC
Operational 24 SC (Glonass-M)
In commissioning 0 SC
Flight testing 2 SC (Glonass-K)
In maintenance 0 SC (Glonass-M)
Spare 0 SC (Glonass-M)
In flight tests phase 2 SC (Glonass-M)

The system requires 18 satellites for continuous navigation services covering the entire territory of the Russian Federation, and 24 satellites to provide services worldwide.[79] The GLONASS system covers 100% of worldwide territory.

On 2 April 2014 the system experienced a technical failure that resulted in practical unavailability of the navigation signal for around 12 hours.[31]

On 14–15 April 2014 nine GLONASS satellites experienced another technical failure due to software problems.[80]

Accuracy

According to Russian System of Differentional Correction and Monitoring's data, as of 2010, precisions of GLONASS navigation definitions (for p=0.95) for latitude and longitude were 4.46–7.38 metres (14.6–24.2 ft) with mean number of navigation space vehicles (NSV) equals 7—8 (depending on station). In comparison, the same time precisions of GPS navigation definitions were 2.00–8.76 metres (6 ft 7 in – 28 ft 9 in) with mean number of NSV equals 6—11 (depending on station).[citation needed] Civilian GLONASS used alone is therefore very slightly less accurate than GPS. On high latitudes (north or south), GLONASS' accuracy is better than that of GPS due to the orbital position of the satellites.[81]

Some modern receivers are able to use both GLONASS and GPS satellites together, providing greatly improved coverage in urban canyons and giving a very fast time to fix due to over 50 satellites being available. In indoor, urban canyon or mountainous areas, accuracy can be greatly improved over using GPS alone. For using both navigation systems simultaneously, precisions of GLONASS/GPS navigation definitions were 2.37–4.65 metres (7 ft 9 in – 15 ft 3 in) with mean number of NSV equals 14—19 (depends on station).

In May 2009, Anatoly Perminov, then director of the Russian Federal Space Agency, stated that actions were undertaken to expand GLONASS's constellation and to improve the ground segment to increase the navigation definition of GLONASS to an accuracy of 2.8 metres (9 ft 2 in) by 2011.[82] In particular, the latest satellite design, GLONASS-K has the ability to double the system's accuracy once introduced. The system's ground segment is also to undergo improvements. As of early 2012, sixteen positioning ground stations are under construction in Russia and in the Antarctic at the Bellingshausen and Novolazarevskaya bases. New stations will be built around the southern hemisphere from Brazil to Indonesia. Together, these improvements are expected to bring GLONASS' accuracy to 0.6 m or better by 2020.[83]

See also

Notes

  1. Orbital periods and speeds are calculated using the relations 4π²R³ = T²GM and V²R = GM, where R = radius of orbit in metres, T = orbital period in seconds, V = orbital speed in m/s, G = gravitational constant ≈ 6.673×1011 Nm²/kg², M = mass of Earth ≈ 5.98×1024 kg.
  2. Approximately 8.6 times (in radius and length) when the moon is nearest (363 104 km ÷ 42 164 km) to 9.6 times when the moon is farthest (405 696 km ÷ 42 164 km).

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 5.4 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. Glonass still wants to be "the other guy in the sky. RT. 6 December 2010. Retrieved on 2011-10-06.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. GLONASS hits a snag. Russia Beyond The Headlines. 7 December 2010. Retrieved on 2011-10-06.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Broadcom Upgrades Its A-GPS Data Service and GPS LTO Product/Service with GLONASS Satellite Support. Broadcom.com (2011-02-09). Retrieved on 2011-10-06.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. GLONASS support in our latest Xperia™ phones – Developer World. Developer.sonyericsson.com. Retrieved on 2013-08-02.
  19. Samsung GALAXY Note - Samsung Mobile. Samsung.com. Retrieved on 2013-08-02.
  20. iPhone 5 - View all the technical specifications. Apple. Retrieved on 2013-08-02.
  21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. GLONASS finally becomes global NTV. 3 October 2011. (Russian)
  27. Russia restores its orbital GLONASS group – official. The Voice of Russia. 3 October 2011. (Russian)
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
  32. 32.0 32.1 32.2 32.3 Lua error in package.lua at line 80: module 'strict' not found.
  33. 33.0 33.1 33.2 Lua error in package.lua at line 80: module 'strict' not found.
  34. GLONASS transmitter specs
  35. "A Review of GLONASS" Miller, 2000
  36. National Reference Systems of the Russian Federation used in GLONASS. V. Vdovin and M. Vinogradova (TSNIImash), 8th ICG meeting, Dubai, November 2013
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. GLONASS Status and Progress, S.G.Revnivykh, 47th CGSIC Meeting, 2007. "L1CR and L5R CDMA interoperable with GPS and Galileo"
  40. 40.0 40.1 40.2 GLONASS Status and Development, G.Stupak, 5th ICG Meeting
  41. Russia’s First GLONASS-K In Orbit, CDMA Signals Coming. Inside GNSS (2011-02-26). Retrieved on 2011-10-06.
  42. GLONASS Status and Modernization. Ekaterina Oleynik, Sergey Revnivykh, 51st CGSIG Meeting, September 2011
  43. GLONASS Status and Modernization. Sergey Revnivykh. 6th ICG Meeting, September 2011
  44. 44.0 44.1 GLONASS Status and Modernization. Sergey Revnivykh. 7th ICG Meeting, November 2012
  45. GLONASS Government Policy, Status and Modernization Plans. Tatiana Mirgorodskaya. IGNSS-2013, 16 July 2013
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. http://www.insidegnss.com/auto/julyaug11-Dumas.pdf
  48. GLONASS Modernization Yuri Urlichich, Valery Subbotin, Grigory Stupak, Vyacheslav Dvorkin, Alexander Povalyaev, Sergey Karutin, and Rudolf Bakitko, Russian Space Systems. GPS World, November 2011
  49. 49.0 49.1 GLONASS: Developing Strategies for the Future. Yuri Urlichich, Valeriy Subbotin, Grigory Stupak, Vyacheslav Dvorkin, Alexander Povalyaev, and Sergey Karutin. GPS World, November 2011
  50. New Structure for GLONASS Nav Message Alexander Povalyaev. GPS World, 2 November 2013
  51. 51.0 51.1 Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. SDCM status and plans, Grigory Stupak, 7th ICG Meeting, November 2012
  56. Uragan, Russian Space Web
  57. GLONASS #787, 68.7 operational months; as reported by RSA "GLONASS constellation status" on 6 April 2007
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. 60.0 60.1 Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. GLONASS Summary, Space and Tech
  66. "GLONASS added to SkyWave terminals", Digital Ship, 4 December 2009. Thedigitalship.com
  67. [Garmin eTrex 20 https://buy.garmin.com/shop/shop.do?cID=145&pID=87771#overviewTab]
  68. GLO for Aviation | Garmin. Buy.garmin.com. Retrieved on 2013-08-02.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. iPad mini - Technical specifications. Apple. Retrieved on 2013-08-02.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Windows Phone 8X by HTC Overview - HTC Smartphones. Htc.com. Retrieved on 2013-08-02.
  76. Google Drive Viewer. Docs.google.com. Retrieved on 2013-08-02.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Russia to set world record with 39 space launches in 2009 RIA Novosti 2008-12-29
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

  • GLONASS Interface Control Document Edition 5.1, 2008 (backup)
  • GLONASS Interface Control Document Version 4.0, 1998
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links