If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor

DGNSS Standards: Difference between revisions

From Navipedia
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
(24 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Article Infobox2
{{Article Infobox2
|Category=Fundamentals
|Category=Fundamentals
|Title={{PAGENAME}}
|Editors=GMV
|Authors=GMV
|Level=Intermediate
|Level=Medium
|YearOfPublication=2011
|YearOfPublication=2011
|Logo=GMV
|Logo=GMV
|Title={{PAGENAME}}
}}
}}
The classical DGNSS technique technique is an enhancement to a primary GNSS system, that consists of the determination of the GNSS position for an accurately-surveyed position known as reference station.


The classical DGNSS technique technique is an enhancement to a primary GNSS system, that consists of the determination of the GNSS position for an accurately-surveyed position known as reference station.
==Introduction==
 
Unlike other [[GNSS Augmentation]] systems as SBAS or GBAS, DGNSS is not used for civil aviation, but for urban transportation and in offshore areas. Therefore, the standards applying to DGNSS systems are the ones of data transmission standards defined by the Special Committee 104 on DGNSS of the [http://www.rtcm.org/about.html Radio Technical Commission for Maritime Services] (RTCM). Except for RTCM, there exist other proprietary DGPS standards, such as [http://www.trimble.com Trimble] [http://trl.trimble.com/docushare/dsweb/Get/Document-469944/WhitePaper_HeavyHighway_CMRxrev1.pdf Compact Measurement Record] (CMR).
 
==RTCM Standards==
 
The internationally accepted data transmission standards for DGNSS are defined by RTCM, particularly by its Special Committee SC-104. RTCM SC-104 is a standard that defines the data structure for differential correction information for a variety of differential correction applications. It was developed by the [http://www.rtcm.org/about.html Radio Technical Commission for Maritime Services] (RTCM) and has become an industry standard for communication of correction information. Note that RTCM is a binary data protocol.
 
The applicable documents to DGNSS systems are listed in the following table and constitute the current version of the core set of documents to be used for the development of a new DGNSS system.
 
 
{| class="wikitable"
!Document Item
!Reference
!Issue
!Comments
|-
|Recommended Standards for Differential GNSS (Global Navigation Satellite Systems) Service
|align="center"|RTCM 10402.3
|align="center"|2.3
|This standard is used around the world for differential satellite navigation systems, both maritime and terrestrial.
|-
|Differential GNSS (Global Navigation Satellite Systems) Services
|align="center"|RTCM 10403.1
|align="center"|3.1
| A more efficient alternative to RTCM 10402.3
|-
|Standard for Networked Transport of RTCM via Internet Protocol (Ntrip)
|align="center"|RTCM 10410.0
|align="center"|1
| An application-level protocol that supports streaming Global Navigation Satellite System (GNSS) data over the Internet
|-
|Standard for Differential Navstar GPS Reference Stations and Integrity Monitors (RSIM)
|align="center"|RTCM 10401.2
|align="center"|2
|  A companion to RTCM 10402.3, this standard addresses the performance requirements for the equipment which broadcasts DGNSS corrections
|}
 
The RTCM 10402.3 standards defined the messages for differential correction information. There are 64 types of messages. The message format is a sequence of 30 bits. The messages 1 to 17 are available in older RTCM versions, while messages 18-21 have been added in version 2.3 to made the standard applicable to [[Real Time Kinematics|RTK]] corrections.
 
The RTCM 10402.3 DGNSS message types are summarized in the following table:
 
{| class="wikitable" align="center"
!Message type identifier
!Message Name
|-align="center"
|-align="center"
| 1
| Differential GPS Corrections
|-align="center"
| 2
| Delta Differential GPS Corrections
|-align="center"
| 3
| Reference Station Parameters 
|-align="center"
| 4
| Surveying
|-align="center"
| 5
| Constellation Health
|-align="center"
| 6
| Null Frame
|-align="center"
| 7
| Beacon Almanacs
|-align="center"
| 8
| Pseudolite Almanacs
|-align="center"
| 9
| Partial Satellite Set Differential Corrections
|-align="center"
| 10
| P-Code Differential Corrections (all)
|-align="center"
| 11
| C/A-Code L1, L2 Delta Corrections
|-align="center"
| 12
| Pseudolite Station Parameters
|-align="center"
| 13
| Ground Transmitter Parameters
|-align="center"
| 14
| Surveying Auxiliary Message
|-align="center"
| 15
| Ionosphere (Troposphere) Message
|-align="center"
| 16
| Special Message
|-align="center"
| 17
| Ephemeris Almanac
|-align="center"
| 18
| Uncorrected Carrier Phase Measurements
|-align="center"
|19
| Uncorrected Pseudorange Measurements
|-align="center"
| 20
| RTK Carrier Phase Corrections
|-align="center"
| 21
| RTK Pseudorange Corrections
|-align="center"
|22-58
| Undefined 
|-align="center"
| 59
| Proprietary Message
|-align="center"
|60-63
|geMultipurpose Usa
|}


Standards:
The release of RTCM version 3.0 is developed to be more efficient in terms of broadcast bandwidth and also provides higher integrity <ref> Lin Minmin (2006). ''RTCM 3.0 Implementation in Network RTK and Performance Analysis.'' Msc Thesis, University of Calgary, Dept of Geomatic Engineering.</ref>. Note that Version 3 messages are not compatible with Version 2.x. The new release, Version 3.1, now designated as RTCM Standard 10403.1, incorporates GPS Network Corrections, which enable a mobile receiver to obtain accurate RTK information valid over a large area. In addition, new GPS and GLONASS messages provide orbital parameters to assist in rapid acquisition. A Unicode text message is also provided for the transmission of textual data. Finally, a set of messages are reserved for vendors who want to encapsulate proprietary data in their broadcasts. Unlike Version 2.x, this standard does not include tentative messages. The messages in Version 3 have undergone testing for validity and interoperability, and are considered to be permanent. Since many receivers have been designed and programmed for use with Version 2.x messages, RTCM is maintaining both standards 10402.3 and 10403.1 as "current" standards.
Differing from SBAS and GBAS augmentation systems, DGNSS is not used for civil aviation. Therefore, there are no standards coming from IACO. The internationally accepted data transmission standards for DGPS are defined by RTCM (Radio Technical Commission for Maritime Services), particularly by its Special Committee SC-104. Currently version 2.3 of the DGPS standard is widely used. At the time of this writing (May 2005), the new version of the standard, 3.0, has recently been released. The version of RTCM3.0 for Galileo is now in the making. Except for RTCM, there exist other proprietary DGPS standards, such as Trimble’s CMR. (taken from septentrio webpage)


RTCM SC-104 is a standard that defines the data structure for differential correction information for a variety of differential correction applications. It was developed by the Radio Technical Commission for Maritime services (RTCM) and has become an industry standard for communication of correction information. RTCM is a binary data protocol.
==Other Standards==
--------


La transmisión de correcciones diferenciales entre el receptor de referencia (BASE) y los receptores remotos está estandarizada según propuesta de la Radio Technical Commission for Maritime Services, Special Committee 104, RTCM-SC104. La versión 2.0 incluye mensajes para hacer posible la corrección a las pseudodistancias y variación con el tiempo a la corrección de éstas. La versión 2.1 contiene además tipos para las correcciones a las medidas de fase.
The Compact Measurement Record (CMR) was developed by and initially used by [http://www.trimble.com Trimble] in 1992. The format was developed as a method of transmitting code and carrier phase correction data in a compact format from GPS base stations to GPS rovers for [[Real Time Kinematics|RTK]] GPS surveying. Dr. Nicholas Talbot of Trimble publicly introduced the CMR format at the 1996 [http://www.ion.org/ Institute of Navigation] (ION) Conference.


Hay 64 tipos de mensajes disponibles. El formato de los mensajes consiste en secuencias de palabras de 30 bits. Los últimos 6 bits en cada palabra son los bits de paridad. Cada mensaje comienza con dos palabras cabecera. La primera palabra es fija y contiene lo que se denomina preámbulo (preamble), el tipo de mensaje, y el identificador de la estación de referencia. La segunda palabra contiene la marca de tiempo en forma de cuenta Z, el número de secuencia, la longitud de mensaje y la salud de la estación de referencia.
==Notes==
<references group="footnotes"/>


Los mensajes 1-17 están disponibles en ambas versiones de RTCM, mientras que los mensajes 18-21 contienen cabeceras de 3 palabras y tienen como propósito el posicionamiento RTK (Real Time Kinematic) de aplicación en receptores que admitan esta técnica. La "estación base" debe de estar a una distancia de unas pocas decenas de kilómetros (20-30 Km) para que la correción sea efectiva. Esta técnica permite alcanzar precisiones centimétricas en tiempo real.
==References==
<references/>


Número de mensaje Estado actual Título
[[Category:Fundamentals]]
1 Fixed Differential GPS Corrections
2 Fixed Delta Differential GPS Corrections 
3 Fixed Reference Station Parameters 
4 Retired Surveying
5 Fixed Constellation Health
6 Fixed Null Frame
7 Fixed Beacon Almanacs
8 Tentative Pseudolite Almanacs
9 Fixed Partial Satellite Set Differencial Corrections 
10 Reserved P-Code Differential Corrections (all)
11 Reserved C/A-Code L1, L2 Delta Corrections 
12 Reserved Pseudolite Station Parameters
13 Tentative Ground Transmitter Parameters
14 Reserved Surveying Auxiliary Message
15 Reserved Ionosphere (Troposphere) Message
16 Fixed Special Message
17 Tentative Ephemeris Almanac
18 Tentative Uncorrected Carrier Phase Measurements
19 Tentative Uncorrected Pseudorange Measurements
20 Tentative RTK Carrier Phase Corrections
21 Tentative RTK Pseudorange Corrections
22-58 Undefined 
59 Tentative Proprietary Message
60-63 Reserved geMultipurpose Usa

Latest revision as of 15:02, 23 July 2018


FundamentalsFundamentals
Title DGNSS Standards
Edited by GMV
Level Intermediate
Year of Publication 2011
Logo GMV.png

The classical DGNSS technique technique is an enhancement to a primary GNSS system, that consists of the determination of the GNSS position for an accurately-surveyed position known as reference station.

Introduction

Unlike other GNSS Augmentation systems as SBAS or GBAS, DGNSS is not used for civil aviation, but for urban transportation and in offshore areas. Therefore, the standards applying to DGNSS systems are the ones of data transmission standards defined by the Special Committee 104 on DGNSS of the Radio Technical Commission for Maritime Services (RTCM). Except for RTCM, there exist other proprietary DGPS standards, such as Trimble Compact Measurement Record (CMR).

RTCM Standards

The internationally accepted data transmission standards for DGNSS are defined by RTCM, particularly by its Special Committee SC-104. RTCM SC-104 is a standard that defines the data structure for differential correction information for a variety of differential correction applications. It was developed by the Radio Technical Commission for Maritime Services (RTCM) and has become an industry standard for communication of correction information. Note that RTCM is a binary data protocol.

The applicable documents to DGNSS systems are listed in the following table and constitute the current version of the core set of documents to be used for the development of a new DGNSS system.


Document Item Reference Issue Comments
Recommended Standards for Differential GNSS (Global Navigation Satellite Systems) Service RTCM 10402.3 2.3 This standard is used around the world for differential satellite navigation systems, both maritime and terrestrial.
Differential GNSS (Global Navigation Satellite Systems) Services RTCM 10403.1 3.1 A more efficient alternative to RTCM 10402.3
Standard for Networked Transport of RTCM via Internet Protocol (Ntrip) RTCM 10410.0 1 An application-level protocol that supports streaming Global Navigation Satellite System (GNSS) data over the Internet
Standard for Differential Navstar GPS Reference Stations and Integrity Monitors (RSIM) RTCM 10401.2 2 A companion to RTCM 10402.3, this standard addresses the performance requirements for the equipment which broadcasts DGNSS corrections

The RTCM 10402.3 standards defined the messages for differential correction information. There are 64 types of messages. The message format is a sequence of 30 bits. The messages 1 to 17 are available in older RTCM versions, while messages 18-21 have been added in version 2.3 to made the standard applicable to RTK corrections.

The RTCM 10402.3 DGNSS message types are summarized in the following table:

Message type identifier Message Name
1 Differential GPS Corrections
2 Delta Differential GPS Corrections
3 Reference Station Parameters
4 Surveying
5 Constellation Health
6 Null Frame
7 Beacon Almanacs
8 Pseudolite Almanacs
9 Partial Satellite Set Differential Corrections
10 P-Code Differential Corrections (all)
11 C/A-Code L1, L2 Delta Corrections
12 Pseudolite Station Parameters
13 Ground Transmitter Parameters
14 Surveying Auxiliary Message
15 Ionosphere (Troposphere) Message
16 Special Message
17 Ephemeris Almanac
18 Uncorrected Carrier Phase Measurements
19 Uncorrected Pseudorange Measurements
20 RTK Carrier Phase Corrections
21 RTK Pseudorange Corrections
22-58 Undefined
59 Proprietary Message
60-63 geMultipurpose Usa

The release of RTCM version 3.0 is developed to be more efficient in terms of broadcast bandwidth and also provides higher integrity [1]. Note that Version 3 messages are not compatible with Version 2.x. The new release, Version 3.1, now designated as RTCM Standard 10403.1, incorporates GPS Network Corrections, which enable a mobile receiver to obtain accurate RTK information valid over a large area. In addition, new GPS and GLONASS messages provide orbital parameters to assist in rapid acquisition. A Unicode text message is also provided for the transmission of textual data. Finally, a set of messages are reserved for vendors who want to encapsulate proprietary data in their broadcasts. Unlike Version 2.x, this standard does not include tentative messages. The messages in Version 3 have undergone testing for validity and interoperability, and are considered to be permanent. Since many receivers have been designed and programmed for use with Version 2.x messages, RTCM is maintaining both standards 10402.3 and 10403.1 as "current" standards.

Other Standards

The Compact Measurement Record (CMR) was developed by and initially used by Trimble in 1992. The format was developed as a method of transmitting code and carrier phase correction data in a compact format from GPS base stations to GPS rovers for RTK GPS surveying. Dr. Nicholas Talbot of Trimble publicly introduced the CMR format at the 1996 Institute of Navigation (ION) Conference.

Notes


References

  1. ^ Lin Minmin (2006). RTCM 3.0 Implementation in Network RTK and Performance Analysis. Msc Thesis, University of Calgary, Dept of Geomatic Engineering.