Changeset 4065 in ntrip


Ignore:
Timestamp:
Apr 27, 2012, 11:08:24 AM (13 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r4064 r4065  
    17111711<p>The stream upload may be protected through an upload 'Password'. Enter the password you received from the Caster operator along with the mountpoint(s).</p>
    17121712<p>
    1713 If 'Host', 'Port', 'Mountpoint' and 'Password' are set, the stream will be encoded in RTCM's 'State Space Representation' (SSR) messages and uploaded to the specified broadcaster following the NTRIP Version 1.0 transport protocol.
     1713If 'Host', 'Port', 'Mountpoint' and 'Password' are set, the stream will be encoded in RTCM's 'State Space Representation' (SSR) messages and uploaded to the specified broadcaster following the NTRIP Version 1 transport protocol.
    17141714</p>
    17151715
     
    20752075<p><a name="ntripv"><h4>3.18.1.5 NTRIP Version - mandatory</h4></p>
    20762076<p>
    2077 Some limitations and deficiencies of the NTRIP version 1 stream transport protocol are solved in NTRIP version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are:
    2078 </p>
    2079 <p>
    2080 &nbsp; 1:&nbsp; NTRIP version 1, TCP/IP.<br>
    2081 &nbsp; 2:&nbsp; NTRIP version 2 in TCP/IP mode.<br>
    2082 &nbsp; 2s:&nbsp; NTRIP version 2 in TCP/IP mode via SSL.<br>
    2083 &nbsp; R:&nbsp; NTRIP version 2 in RTSP/RTP mode.<br>
    2084 &nbsp; U:&nbsp; NTRIP version 2 in UDP mode.
    2085 </p>
    2086 <p>
    2087 If NTRIP version 2 is supported by the broadcaster:
     2077Some limitations and deficiencies of the NTRIP Version 1 stream transport protocol are solved in NTRIP Version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are:
     2078</p>
     2079<p>
     2080&nbsp; 1:&nbsp; NTRIP Version 1, TCP/IP.<br>
     2081&nbsp; 2:&nbsp; NTRIP Version 2 in TCP/IP mode.<br>
     2082&nbsp; 2s:&nbsp; NTRIP Version 2 in TCP/IP mode via SSL.<br>
     2083&nbsp; R:&nbsp; NTRIP Version 2 in RTSP/RTP mode.<br>
     2084&nbsp; U:&nbsp; NTRIP Version 2 in UDP mode.
     2085</p>
     2086<p>
     2087If NTRIP Version 2 is supported by the broadcaster:
    20882088</p>
    20892089<ul>
     
    20922092</ul>
    20932093<p>
    2094 Select option '1' if you are not sure whether the broadcaster supports NTRIP version 2.</li>
     2094Select option '1' if you are not sure whether the broadcaster supports NTRIP Version 2.</li>
    20952095</p>
    20962096
     
    24022402<tr>
    24032403<td>Apr 2011 &nbsp;</td><td>Version 2.6 &nbsp;</td>
    2404 <td>[Add] Complete integration of BNS in BNC<br> [Add] SP3 and Clock RINEX output<br> [Add] PPP in Post Processing Mode<br> [Add] Some RINEX editing & QC functionality<br> [Add] Threshold for orbit outliers in combination solution<br> [Add] Real-time engine becomes orbit/clock server instead of client<br> [Mod] 'EOE' added to orbit/clock stream from engine<br> [Add] Correction for antenna eccentricities<br> [Add] Quick start mode for PPP<br> [Mod] Design of format for feeding engine changed to follow RINEX v3<br> [Mod] Implementation of SSR message encoding modified according to standard<br> [Add] SSL/TLS Support of Ntrip Version 2<br> [Mod] Switch to Qt version 4.7.3<br> [Add] RINEX editing, concatenation and quality check<br> [Mod] RTCMv3 Galileo Broadcast Ephemeris message 1045</td>
     2404<td>[Add] Complete integration of BNS in BNC<br> [Add] SP3 and Clock RINEX output<br> [Add] PPP in Post Processing Mode<br> [Add] Some RINEX editing & QC functionality<br> [Add] Threshold for orbit outliers in combination solution<br> [Add] Real-time engine becomes orbit/clock server instead of client<br> [Mod] 'EOE' added to orbit/clock stream from engine<br> [Add] Correction for antenna eccentricities<br> [Add] Quick start mode for PPP<br> [Mod] Design of format for feeding engine changed to follow RINEX v3<br> [Mod] Implementation of SSR message encoding modified according to standard<br> [Add] SSL/TLS Support of NTRIP Version 2<br> [Mod] Switch to Qt version 4.7.3<br> [Add] RINEX editing, concatenation and quality check<br> [Mod] RTCMv3 Galileo Broadcast Ephemeris message 1045</td>
    24052405</tr>
    24062406
     
    24282428
    24292429<p>
    2430 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.
     2430NTRIP Version 1 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.
    24312431</p>
    24322432
     
    24632463
    24642464<p>
    2465 The major changes of NTRIP version 2.0 compared to version 1.0 are:
     2465The major changes of NTRIP Version 2 compared to Version 1.0 are:
    24662466</p>
    24672467
     
    24752475</ul>
    24762476
    2477 <p>NTRIP version 2 allows to either communicate in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas version 1 is limited to TCP/IP only. It furthermore allows using the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure NTRIP communication over the Internet.
     2477<p>NTRIP Version 2 allows to either communicate in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas Version 1 is limited to TCP/IP only. It furthermore allows using the Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL) cryptographic protocols for secure NTRIP communication over the Internet.
    24782478</p>
    24792479
Note: See TracChangeset for help on using the changeset viewer.