source: ntrip/trunk/BNS/bnshelp.html@ 1091

<h3>BKG Ntrip State Space Server (BNS) Version 1.0</h3>

<p>
The BKG Ntrip State Space Server (BNS) is a program for transforming GNSS satellite clocks and orbits into corrections to Broadcast Ephemeris. These corrections are then encode in RTCM Version 3.x format and uploaded to NTRIP broadcasters like <u>http://www.euref-ip.net/home</u> or <u>http://www.igs-ip.net/home.</u> BNS is created as a tool for service providers with real-time access to a network of continentally or globally distributed GNSS reference stations.
</p>

<p>
BNS has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of EUREF's Real-time GNSS Project (EUREF-IP, IP for Internet Protocol) and the Real-Time IGS Pilot Project (RTIGS PP).
</p>

<p>
BNS is released under the GNU General Public License (GPL). Binaries for BNS are available for Windows, 32-bit and 64-bit Linux (compiled under -m32 32-bit compatibility mode), Solaris, and Mac OS X systems. The MinGW compiler (Version 5.3.1) is used to produce the Windows binary. It is likely that BNS can be compiled on other systems where a GNU compiler and Qt Version 4.3.2 are available.
</p>

<p>
Before running, please ensure that you have installed the latest version available. The latest version of BNS can be obtained from <u>http://igs.bkg.bund.de/index_ntrip_down.htm</u>. We are continuously working on the program and would appreciate any comments, suggestions, or bug reports. They can be emailed to [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de].
</p>

<h3>Contents</h3>
<p>
<h4>
<a href=#purpose>1. Purpose</a><br>
<a href=#function>2. Functioning</a><br>
<a href=#resources>3. Resources</a><br>
<a href=#options>4. Options</a><br>
<a href=#limits>5. Limitations</a><br>
<a href=#authors>6. Authors</a><br>
<a href=#annex>7. Annex</a><br>
</h4>
</p>

<p><a name="purpose"><h3>1. Purpose</h3></p>
<p>
Differential GNSS and RTK operation using RTCM is currently based on corrections and/or raw measurements from single or multiple reference stations. This approach to differential positioning is using 'observation space' information. The representation with the RTCM standard can be called 'Observation Space Representation' (OSR). 
</p>
<p>
An alternative to the observation space approach is the so called 'sate space' approach. The principle here is to provide information on individual error sources and can be called 'State Space Representation' (SSR). For a rover position, state space information concerning precise satellite clocks, orbits, ionosphere, troposphere et cetera can be converted into observation space and used to correct the rover observables for more accurate positioning. Alternatively the state information can directly be used in the rover's processing or adjustment model.
</p>

<p>In order to support applications following the state space approach, the purpose of BNS is to

<ul>
<li>read GNSS clocks and orbits in plain ASCII format from an IP port. They can be produced by a real-time GNSS engine such as RTNet and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system.</li> 
<li>read GNSS Broadcast Ephemeris in RINEX Navigation file format from an IP port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program.</li>
<li>convert the IGS Earth-Centered-Earth-Fixed clocks and and orbits into corrections to Broadcast Ephemeris with radial, along-track and cross-track components.</li>
<li>upload the clock and orbit corrections as a stream to an NTRIP Broadcaster.</li>
<li>log the Broadcast Ephemeris clock corrections as files in Clock RINEX files.</li>
<li>log the Broadcast Ephemeris orbit corrections as files in SP3 files.</li>
</ul>
</p>
<p>
Note that BNS currently only generates the tentative RTCM Version 3.x message types 4056 for Combined GPS and GLONASS orbit corrections and 4057 for Combined GPS and GLONASS clock corrections to Broadcast Ephemeris.
</p>

<p><a name="function"><h3>2. Functioning</h3></p>
<p>
The procedures taken by BNS to generate clock and orbit corrections to Broadcast Ephemeris in radial, along-track and cross-track components are as follow:
</p>
<p>
<ul> 
<li>Continuously receive up-to-date Broadcast Ephemeris carrying approximate orbits and clocks for all satellites. Receive them in RINEX Version 3 Navigation file format. Read new Broadcast Ephemeris immediately whenever they become available. Tools like the 'BKG Ntrip Client' (BNC) provide this information.</li>
</ul> 
</p>
<p>
Then, epoch by epoch:
<ul> 
<li>Continuously receive the best available clock and orbit estimates for all satellites in X,Y,Z Earth-Centered-Earth-Fixed IGS05 reference system. Receive them every epoch in a plain ASCII format as provided by a real-time GNSS engine such as RTNet.</li>
<li>Calculate X,Y,Z coordinates from Broadcast Ephemeris orbits.</li>
<li>Calculate differences dX,dY,dZ between Broadcast Ephemeris orbits and IGS05 orbits.</li>
<li>Model orbit differences through low degree polynomial.</li>
<li>Derive model-based estimation of corrections to Broadcast Ephemeris orbits.
<li>Tranform model-based orbit corrections into radial, along-track and cross-track components.</li>
<li>Calculate differences dC between clocks from Broadcast Ephemeris and IGS05 clocks.</li>
<li>Model clock differences through low degree polynomial.</li>
<li>Derive model-based estimation of corrections to Broadcast Ephemeris clocks.</li>
<li>Encode Broadcast Ephemeris clock and orbit corrections in RTCM Version 3.x format.</li>
<li>Upload corrections in RTCM Verion 3 format to NTRIP Broadcaster.</li>
</ul>
</p>
<p>
Although it is not compulsory, because BNS puts a significant load on the communication link, it is recommended that BNS, the Broadcast Ephemeris server (i.e. BNC), and the server providing orbits and clocks (i.e. RTNet) are run on the same host.
</p>

<p><a name="resources"><h3>3. Resources</h3></p>
<p>
The size of the real-time stream produced by BNS is in the order 2 to 3 kbits/sec depending on the number of visible satellites. When uploading the stream to an NTRIP Broadcaster, user needs to ensure that the connection used can sustain the required bandwidth.
</p>
<p>
Running BNS requires the clock of the host computer to be properly synchronized.
</p>

<p><a name="options"><h3>4. Options</h3></p>
<p>
4.1. <a href=#file>File</a><br>
4.2. <a href=#help>Help</a><br>
4.3. <a href=#proxy>Proxy</a><br>
4.4. <a href=#general>General</a><br>
&nbsp; &nbsp; &nbsp; 4.4.1. <a href=#logfile>Logfile</a><br>
&nbsp; &nbsp; &nbsp; 4.4.2. <a href=#appfile>Append Files</a><br>
4.5. <a href=#eph>RINEX Ephemeris</a><br>
&nbsp; &nbsp; &nbsp; 4.5.1. <a href=#ephserver>Host & Port</a><br>
&nbsp; &nbsp; &nbsp; 4.5.2. <a href=#ephsave>Save</a><br>
4.6. <a href=#co>Clocks & Orbits</a><br>
&nbsp; &nbsp; &nbsp; 4.6.1. <a href=#coport>Listening Port</a><br>
&nbsp; &nbsp; &nbsp; 4.6.2. <a href=#cosave>Save</a><br>
4.7. <a href=#ephc>Ephemeris Corrections</a><br>
&nbsp; &nbsp; &nbsp; 4.7.1. <a href=#ephcserver>Host & Port, Password</a><br>
&nbsp; &nbsp; &nbsp; 4.7.2. <a href=#ephcmount>Mountpoint</a><br>
&nbsp; &nbsp; &nbsp; 4.7.3. <a href=#ephcsys>System</a><br>
&nbsp; &nbsp; &nbsp; 4.7.4. <a href=#ephcsave>Save</a><br>
4.8. <a href=#clkrnx>RINEX Clocks</a><br>
&nbsp; &nbsp; &nbsp; 4.8.1. <a href=#clkdir>Directory</a><br>
&nbsp; &nbsp; &nbsp; 4.8.2. <a href=#clkint>Interval & Sampling</a><br>
4.9. <a href=#orb>SP3 Orbits</a><br>
&nbsp; &nbsp; &nbsp; 4.9.1. <a href=#orbdir>Directory</a><br>
&nbsp; &nbsp; &nbsp; 4.9.2. <a href=#orbint>Interval & Sampling</a><br>
4.10. <a href=#start>Start</a><br>
4.11. <a href=#stop>Stop</a><br>
4.12. <a href=#nw>No Window</a>
</p>

<p><a name="file"><h4>4.1. File</h4></p>

<p>
The 'File' button lets you
<ul>
<li>
select an appropriate font.<br>
Use smaller font size if the BNS main window extends beyond the size of your screen.
</li> 
<li> save selected options.<br>
Note that on Windows systems options are saved in register BKG_NTRIP_Server. On Unix/Linux systems options are saved in file ${HOME}/.config/BKG/BKG_NTRIP_Server.conf.
</li>
<li>
quit the BNS program.
</li> 
</ul>
</p>

<p><a name="help"><h4>4.2. Help</h4></p>

<p>
The 'Help' button provides access to
<ul>
<li>
help contents.<br>
You may keep the 'Help Contents' window open while configuring BNS.
</li> 
<li>
a 'Flow Chart' showing BNS linked to tools like BNC and a real-time GNSS engine such as RTNet.
</li> 
<li>
general information about BNS.<br>
Close the 'About BNS' window to continue working with BNS.
</li> 
</ul>
</p>
<p>
BNS comes with a help system providing online information about its functionality and usage. Short descriptions are available for any widget. Focus to the relevant widget and press Shift+F1 to request help information. A help text will appear immediately; it disappears as soon as the focus is shifted to something else. The dialogs on some operating systems may provide a "?" button that users can click; they then click the relevant widget to pop up the help text.
</p>

<p><a name="proxy"><h4>4.3. Proxy - for usage in a protected LAN</h4></p>

<p>
If you are running BNS within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you don't know the address and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.
</p>
<p>
Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification of the local security policy or for the installation of a TCP relay to the NTRIP Casters. If these are not possible, you might need to run BNS outside your LAN on a host that has unobstructed connection to the Internet.
</p>
<p><a name="general"><h4>4.4. General Options</h4></p>

<p><a name="logfile"><h4>4.4.1 Logfile - optional</h4></p>
<p>
Records of BNC's activities are shown in the Log section on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Log (full path)' field. The message log covers the communication status between BNC and the NTRIP broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Log (full path)' is an empty option field, meaning that BNC logs will not saved into a file.
</p>

<p><a name="appfile"><h4>4.4.2 Append Files</h4></p>
<p>
When BNS is started, new files are created by default and any existing files with the same name will be overwritten. However, users might want to append existing files following a restart of BNS, a system crash or when BNS had crashed. Tick 'Append files' to continue with existing files and keep what has been recorded so far. Note that option 'Append files' affects all types of files created by BNS.
</p> 

<p><a name="eph"><h4>4.5. RINEX Ephemeris</h4></p>
<p>
BNS requires GNSS Broadcast Ephemeris in RINEX Version 3 Navigation file format from an IP address and port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program. Note that whenever a new set of Broadcast Ephemeris becomes available, BNS needs it immediately.
</p>

<p><a name="ephserver"><h4>4.5.1 Host & Port - mandatory</h4></p>
<p>
Enter the IP address and port number of a Broadcast Ephemeris server like BNC to establish a persistent socket connection, see section 'Flow Chart' under 'Help' for socket communication details. If BNS runs on the same host as BNC, 127.0.0.1 should be used as the server's IP address. Make sure that this server is up and running before you start BNS.
</p>

<p><a name="ephsave"><h4>4.5.2 Save - optional</h4></p>
</p>
Specify the full path to a file where received Broadcast Ephemeris will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
</p>
<p>
The following is an example log of Broadcast Ephemeris records in RINEX Version 3 Navigation file format for satellite GPS PRN32 and GLONASS PRN04:
</p>

<p>
<pre>
G32 2008 07 22 12 00 00  3.08818183839e-04  2.72848410532e-12  0.00000000000e+00
     1.10000000000e+01 -4.00312500000e+01  4.63269297026e-09  9.74027926504e-01
    -2.19419598579e-06  1.39143558918e-02  8.25151801109e-06  5.15381674576e+03
     2.16000000000e+05 -8.56816768646e-08 -3.26801342873e-02 -2.94297933578e-07
     9.68688494953e-01  2.30468750000e+02 -1.30607654294e+00 -8.26105839196e-09
    -3.62872257943e-10  1.00000000000e+00  1.48900000000e+03  0.00000000000e+00
     2.00000000000e+00  0.00000000000e+00 -2.79396772385e-09  1.10000000000e+01
     0.00000000000e+00  0.00000000000e+00
R04 2008 07 22 08 15 14  4.76110726595e-05  0.00000000000e+00  2.88600000000e+04
    -1.76267827148e+04 -4.64202880859e-01  1.86264514923e-09  0.00000000000e+00
    -1.79631489258e+04 -3.41343879700e-01 -2.79396772385e-09  6.00000000000e+00
    -4.20270556641e+03  3.50097942352e+00  0.00000000000e+00  0.00000000000e+00
</pre>
</p>

<p><a name="co"><h4>4.6. Clocks & Orbits</h4></p>
<p>
BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. They can be provided by a real-time GNSS engine such as RTNet and are expected to refer to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. 
</p>

<p><a name="coport"><h4>4.6.1 Listening Port - mandatory</h4></p>
<p>
BNS is listening at an IP port for incoming GNSS clocks and orbits in a plain ASCII format. Enter the respective IP port number to setup a server socket for incoming data, see section 'Flow Chart' under 'Help' for socket communication details. Make sure that the software providing clocks and orbits is up and running before you start BNS.
</p>

<p><a name="cosave"><h4>4.6.2 Save - optional</h4></p>
<p>
Specify the full path to a file where received clocks and orbits from a real-time engine will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
</p>

<p>
Below you find an example of precise clocks and orbits coming in plain ASCII format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by GPS Week, Second in GPS Week and Number of satellites. Subsequent records provide the following set of parameters for each satellite:
</p>

<p>
<ul>
<li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
<li>X,Y,Z coordinates in Earth-Centered-Earth-Fixed system [m]</li>
<li>Satellite clock error [ns]</li>
<li>Standard deviation of satellite clock error [ns]</li>
</ul>
</p>

</p>
<p>
<pre>
*  1489  218527.000000 13
G08    -76413.307  24866966.637   8527190.979     -162.790607     0.375
G09  13547198.314 -14993483.355  16521052.798        6.462891    -0.335
G12  23546505.279 -11419650.825  -4126405.941     -356.488306    -0.103
G15  20671877.676   1926153.017  16592944.847     -147.015776    -0.216
G17  14584397.556  20610108.909   8557082.997       38.709284    -0.081
G18   8169428.184 -16862693.369  18872507.835     -153.553965    -0.149
G22  -6624646.069 -14262545.420  21565075.194      211.479778    -0.089
G26  21424721.760   7905958.802  13511083.183      296.893434     0.413
G28   5220247.539  14404808.121  22087340.167      -21.263655     0.184
R04  14087836.321 -12766880.844  16904727.671       47.601404    -0.302
R13   9968458.843   4774687.770  22964489.920     -205.604626     0.526
R14  11765674.558 -13533158.122  18154217.335     -142.409508     0.093
R23  15142315.506  19152857.044   7329580.240     -111.465205    -0.316
*  1489  218528.000000 13
G08    -76893.521  24867989.053   8524186.937     -162.790606     0.376
G09  13547066.674 -14991254.946  16523118.186        6.462896    -0.334
G12  23547101.712 -11419571.961  -4123272.866     -356.488305    -0.102
G15  20673380.091   1927636.846  16590899.052     -147.015776    -0.215
G17  14583421.795  20609591.381   8559990.870       38.709276    -0.083
G18   8171742.449 -16863250.285  18870956.178     -153.553959    -0.148
G22  -6622069.142 -14263374.211  21565314.170      211.479771    -0.091
G26  21425938.906   7907253.545  13508540.885      296.893448     0.415
G28   5217668.842  14405642.686  22087373.519      -21.263659     0.183
R04  14090047.809 -12767642.452  16902327.088       47.601401    -0.303
R13   9967725.004   4777752.821  22964170.268     -205.604617     0.529
R14  11764988.257 -13530761.727  18156438.374     -142.409512     0.091
R23  15141704.650  19152042.802   7332976.247     -111.465201    -0.316
</pre>
</p>

<p><a name="ephc"><h4>4.7. Ephemeris Corrections</h4></p>
<p>
BNS can upload the resulting stream(s) of clock and orbit corrections to Broadcast Ephemeris to an Ntrip Broadcaster. Both EUREF and IGS operate an NTRIP broadcaster at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u> which can be used for stream upload. The stream's format is RTCM Version 3.x. Note that it only carries the thentative message Types 4056 and 4057 for combined GPS and GLONASS clock and orbit corrections.
</p>

<p><a name="ephcserver"><h4>4.7.1 Host & Port, Password - optional</h4></p>
<p>
Enter the NTRIP Caster's 'Host' IP name or number for stream upload.
</p>
<p>
Enter the NTRIP Caster's IP 'Port' number for stream upload. Note that NTRIP Casters are often configured to provide access on more than one port, usually port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).
</p>
</p>
In NTRIP Version 1.0 stream upload may be protected through an upload 'Password'. Enter the password you received from the Caster operator along with the mountpoint(s).
</p>

<p><a name="ephcmount"><h4>4.7.2 Mountpoint - mandatory if 'Host' is set</h4></p>
<p>
Each stream on an NTRIP Caster is defined using a unique source ID called mountpoint. An NTRIP Server like BNS upload a stream to the Caster by referring to a dedicated mountpoint that has been set by the Caster operator. Specify here the mountpoint based on the detail you received from the operator for your stream. It is often a four character ID (capital letters) plus an integer number.
<p>

<p><a name="ephcsys"><h4>4.7.3 Reference System - mandatory if 'Host' is set</h4></p>
<p>
BNS refers its final clock and orbit corrections to a specific reference system. Available options are
<p>
<ul>
<li>IGS05 which stands for the GNSS-based IGS realization of the International Terrestrial Reference Frame (ITRF2005), and</li>
<li>ETRS89 which stands for the European Terrestrial Reference System 1989 adopted by EUREF.</li>
</ul>
</p>

<p>
<u>IGS05:</u>
As the clocks and orbits coming from real-time GNSS engine are expected to be in the IGS05 system, no transformation is carried out if this option is selected.
</p>
<p>
<u>ETRS89:</u>
From the complete transformation chain 'IGS05->ITRF2005->ITRF2000->ETRS89' only the transformation 'ITRF2000->ETRS89' has been implemented. The formulas for that are taken from 'Boucher and Altamimi 2007: Specifications for reference frame fixing in the analysis of EUREF GPS campaign', see <u>http://etrs89.ensg.ign.fr/memo2007.pdf</u>. The following 6 Helmert transformation parameters were introduced:
</p>
<p>
<pre>
Translation in X:  0.054 m
Translation in Y:  0.051 m
Translation in Z: -0.048 m
Rotation in X:  0.081 mas/y
Rotation in Y:  0.490 mas/y
Rotation in Z: -0.792 mas/y
</pre>
</p>
<p>
Note that the neglect of transformations 'IGS05->ITRF2005->ITRF2000' in BNS may cause discrepancies up to a maximum of 2 centimenters.
<p>


<p><a name="ephcsave"><h4>4.7.4 Save - optional</h4></p>
<p>
The clock and orbit corrections streamed by BNS to the NTRIP Caster can be logged locally. Specify a full 'Save stream' path here to save this information to a local file. Default value for 'Save stream' is an empty option field, meaning that logging is disabled.
</p>
<p>
The file is in plain ASCII format comprising records containing the following set of parameters:
</p>

<p>
<ul>
<li>GPS Week</li>
<li>Second in GPS Week</li>
<li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
<li>IOD referring to Broadcast Ephemeris set</li>
<li>Clock Correction to Broadcast Ephemeris [m]</li>
<li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li>
<li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li>
<li>Cross-track Component of Orbit Correction to Broadcast Ephemeris [m]</li>
</ul>
</p>
<p>
The following is an example file contents based on combined GPS and GLONASS clock and orbit corrections carried in RTCM Version 3.x message Type 4056 and 4057:
</p>
<p>
<pre>
1489 325606.0 G31    18     -1.021      0.110   -1.308   -0.120
1489 412006.0 R10    18      7.342      1.393    4.858   -2.634
1489 412006.0 R19    18      4.696      2.358    1.707   -2.907
...
1489 325607.0 G30    80      6.022      0.591   -0.318    0.022
1489 325607.0 G31    18     -1.022      0.110   -1.308   -0.120
1489 412007.0 R10    18      7.341      1.390    4.860   -2.636
1489 412007.0 R19    18      4.698      2.356    1.706   -2.906
...
</pre>
</p>

<p><a name="clkrnx"><h4>4.8. RINEX Clocks</h4></p>
<p>
The clock corrections generated by BNS can be logged separately in Clock RINEX format. The file naming follows the RINEX convention.
</p>

<p><a name="clkdir"><h4>4.8.1 Directory - optional</h4></p>
<p>
Here you can specify the path to where the Clock RINEX files will be stored. If the specified directory does not exist, BNS will not create Clock RINEX files. Default value for 'Directory' is an empty option field, meaning that logging of Clock RINEX files is disabled.
</p>

<p><a name="clkint"><h4>4.8.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p>
<p>
Select the length of the Clock RINEX file generated. The default value is 1 day.
</p>

<p>
Select the Clock RINEX sampling interval in seconds. A value of zero '0' tells BNS to store all received epochs into Clock RINEX. This is the default value.
</p>

<p><a name="orb"><h4>4.9. SP3 Orbits</h4></p>
<p>
The orbit corrections generated by BNS can be logged separately in SP3 Orbit files. The file naming follows the IGS convention.
</p>

<p><a name="orbdir"><h4>4.9.1 Directory - optional</h4></p>
<p>
Here you can specify the path to where the SP3 Orbit files will be stored. If the specified directory does not exist, BNS will not create SP3 Orbit files. Default value for 'Directory' is an empty option field, meaning that logging of SP3 Orbit files is disabled.
</p>

<p><a name="orbint"><h4>4.9.2 Interval & Sampling - mandatory if 'Directory' is set</h4></p>
<p>
Select the length of the SP3 Orbit file generated. The default value is 1 day.
</p>
<p>
Select the SP3 Orbit file sampling interval in seconds. A value of zero '0' tells BNS to store all received epochs into SP3 Orbit files. This is the default value.
</p>

<p><a name="start"><h4>4.10. Start</h4></p>
<p>
Hit 'Start' to start receiving IGS orbits and clocks and convert them into corrections to Broadcast Ephemeris. Note that when started BNS by default will begin with new files which might overwrite existing files when necessary unless the option 'Append files' is ticked.
</p> 

<p><a name="stop"><h4>4.11. Stop</h4></p>
<p>
Hit the 'Stop' button in order to stop BNS. 
</p> 

<p><a name="nw"><h4>4.12. No Window - optional</h4></p>
<p>
On all systems BNS can be started in batch mode with the command line option '-nw'. BNS will then run in 'no window' mode, using options from the configuration file ${HOME}/.config/BKG/BNC_NTRIP_Server.conf (Unix/Linux, see Config File example in the Annex) or from the register BKG_NTRIP_Server (Windows).
</p> 
<p> 
The self-explanatory contents of the configuration file or the Windows registry can easily be edited. Before editing, terminate BNS first using Windows Task Manager when running it in 'no window' mode on Windows systems.
</p> 
<p><a name="limits"><h3>5. Limitations</h3></p>
<ul>
<li>
In Qt-based desktop environments (such as KDE) on Unix/Linux platforms users may experience a crash at startup even when BNS is run in the background using the '-nw' option. This is a known bug most likely resulting from an incompatibility of Qt libraries in the environment and in BNS. Entering the command 'unset SESSION_MANAGER' before running BNS may help as a work-around.
</li>
<li>
Currently BNS can only generate the tentative RTCM Version 3.x message Type 4056 and 4057 for combined GPS and GLONASS orbit and clock corrections.
</li>
<li>
We experienced some limitation with the Standard Version of Microsoft Windows related to socket communication where sockets are not always handled properly. Since BNS makes intensive use of communication through sockets, we recommend to use the Server Version of Microsoft Windows when running BNS continuously for extended period on a Windows platform.
</li>
<li>
Once BNS has been started, its configuration can not be changed unless without a restart. An on-the-fly reconfiguration is not implemented.
</li>
<br>
</ul>
<p><a name="authors"><h3>6. Authors</h3></p>
<p>
The BKG Ntrip State Space Server (BNS) Qt Graphic User Interface (GUI) has been developed for the Federal Agency for Cartography and Geodesy (BKG) by Leos Mervart, Czech Technical University Prague, Department of Geodesy. BNS includes a GNU GPL open source RTCM 3.x encoder, written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld.
</p>
<p>
Georg Weber<br>
Federal Agency for Cartography and Geodesy (BKG)<br>
Frankfurt, Germany<br>
[euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]
</p>

<p><a name="annex"><h3>7. Annex</h3></p>
<p>
7.1. <a href=#history>History</a><br>
7.2. <a href=#rtcm>RTCM</a><br>
&nbsp; &nbsp; &nbsp; 7.2.1 RTCM <a href=#ntrip>NTRIP</a><br>
&nbsp; &nbsp; &nbsp; 7.2.2 RTCM <a href=#rtcm3>Version 3.x</a><br>
7.3. <a href=#config>Config File</a><br>
7.4. <a href=#links>Links</a><br>
</p>

<p><a name=history><h4>7.1 History</h4></p>
</p>
<table>
<tr></tr>
<tr><td>August 2008 &nbsp;</td><td>Version 1.0 &nbsp;</td><td>[Add] Beta Binaries published.</td></tr>
</table>
</p>

<p><a name="rtcm"><h4>7.2. RTCM</h4></p>

<p>
The Radio Technical Commission for Maritime Services (RTCM) is an international non-profit scientific, professional and educational organization. Special Committees provide a forum in which governmental and non-governmental members work together to develop technical standards and consensus recommendations in regard to issues of particular concern. RTCM is engaged in the development of international standards for maritime radionavigation and radiocommunication systems. The output documents and reports prepared by RTCM Committees are published as RTCM Recommended Standards. Topics concerning Differential Global Navigation Satellite Systems (DGNSS) are handled by the Special Committee SC 104.
</p>
<p>
Personal copies of RTCM Recommended Standards can be ordered through <u>http://www.rtcm.org/orderinfo.php</u>.
</p>

<p><a name="ntrip"><h4>7.2.1 NTRIP</h4></p>

<p>
'Networked Transport of RTCM via Internet Protocol' Version 1.0 (NTRIP) stands for an application-level protocol streaming Global Navigation Satellite System (GNSS) data over the Internet. NTRIP is a generic, stateless protocol based on the Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams.
</p>

<p>
NTRIP Version 1.0 is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, Laptop, PDA, or receiver connections to a broadcasting host. NTRIP supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.
</p>

<p>
NTRIP is implemented in three system software components: NTRIP clients, NTRIP servers and NTRIP broadcasters. The NTRIP broadcaster is the actual HTTP server program whereas NTRIP client and NTRIP server are acting as HTTP clients. The NTRIP broadcaster maintains a source-table containing information on available NTRIP streams, networks of NTRIP streams and NTRIP broadcasters. The source-table is sent to an NTRIP client on request.
</p>

<p>
NTRIP is an open none-proprietary protocol. Major characteristics of NTRIP's dissemination technique are:
<ul>
<li>Based on the popular HTTP streaming standard; comparatively easy to implement when having limited client and server platform resources available.</li>
<li>Application not limited to one particular plain or coded stream content; ability to distribute any kind of GNSS data.</li>
<li>Potential to support mass usage; disseminating hundreds of streams simultaneously for thousands of users possible when applying modified Internet Radio broadcasting software.</li>
<li>Considering security needs; stream providers and users don't necessarily get into contact, streams often not blocked by firewalls or proxy servers protecting Local Area Networks.</li>
<li>Enables streaming over mobile IP networks because of using TCP/IP.</li>
</ul>
</p>

<p><a name="rtcm3"><h4>7.2.2 RTCM Version 3.x</h4></p>
<p>
RTCM Version 3.x has been developed as a better alternative to RTCM Version 2.x. Service providers and vendors have asked for a standard that would be efficient, easy to use, and easily adaptable to new situations.
</p>
RTCM is in the process of developing new Version 3 message types to carry satellite clock and orbit corrections in real-time. Based on the latest available proposal, the following tentative messages currently under discussion of relevance to BNS are listed here:
<p>
<ul>
<li>Message type 4050: GPS orbit corrections to Broadcast Ephemeris</li>
<li>Message type 4051: GPS clock corrections to Broadcast Ephemeris</li>
<li>Message type 4052: GPS code biases</li>
<li>Message type 4053: GLONASS orbit corrections to Broadcast Ephemeris</li>
<li>Message type 4054: GLONASS clock corrections to Broadcast Ephemeris</li>
<li>Message type 4055: GLONASS code biases</li>
<li>Message type 4056: Combined GPS and GLONASS orbit corrections to Broadcast Ephemeris</li>
<li>Message type 4057: Combined GPS and GLONASS clock corrections to Broadcast Ephemeris</li>
</ul>
</p>
<p>
RTCM Version 3.x streams carrying these messages may be used for example to support real-time Precise Point Positioning (PPP) applications using the 'state space' approach.
</p>

<p><a name="config"><h4>7.3. Config File</h4></p>
<p>
The following is an example of the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Server.conf. It enables the upload of streams CLCK1 and CLCK2 to www.igs-ip.net. Clock RINEX files and SP3 Orbit files are saved to a directory /home/weber/rinex :
</p>
<p>
<pre>
[General]
clkPort=7000
ephEcho=/home/weber/rinex/eph.rnx
ephHost=clock-ip.bkg.bund.de
ephPort=6000
fileAppend=0
font="Helvetica [Adobe],8,-1,5,75,0,0,0,0,0"
inpEcho=/home/weber/rinex/ClocksOrbits.dat
logFile=/home/weber/rinex/bns.log
mountpoint_1=CLCK1
mountpoint_2=CLCK2
outFile_1=/home/weber/rinex/CLCK1
outFile_2=/home/weber/rinex/CLCK2
outHost=www.igs-ip.net
outPort=2101
password=serverPass
proxyHost=
proxyPort=
refSys_1=IGS05
refSys_2=ETRS89
rnxIntr=1 day
rnxPath=/home/weber/rinex
rnxSampl=30
sp3Intr=1 day
sp3Path=/home/weber/rinex
sp3Sampl=300
</pre>
</p>

<p><a name="links"><h4>7.4 Links</h4></p>
<table>
<tr></tr>
<tr><td>NTRIP &nbsp;</td><td><u>http://igs.bkg.bund.de/index_ntrip.htm</u></td></tr>
<tr><td>EUREF-IP NTRIP broadcaster &nbsp;</td><td><u>http://www.euref-ip.net/home</u></td></tr>
<tr><td>IGS-IP NTRIP broadcaster &nbsp;</td><td><u>http://www.igs-ip.net/home</u></td></tr>
<tr><td>NTRIP broadcaster overview &nbsp;</td><td><u>http://www.rtcm-ntrip.org/home</u></td></tr>
<tr><td>EUREF-IP Project &nbsp;</td><td><u>http://www.epncb.oma.be/euref_IP</u></td></tr>
<tr><td>Real-time IGS Pilot Project &nbsp;</td><td><u>http://www.rtigs.net/pilot</u></td></tr>
<tr><td>Radio Technical Commission<br>for Maritime Services &nbsp;</td><td><u>http://www.rtcm.org</u>
</table>