Changeset 11216 in ntrip for trunk/BNC/src/bnchelp.html


Ignore:
Timestamp:
Nov 20, 2026, 4:14:37 PM (less than one hour ago)
Author:
stuerze
Message:

Upload Ephemeris: majority vote approach improved

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/bnchelp.html

    r11215 r11216  
    1007010070  <p>
    1007110071    If the same data set (same TOC and IOD) is received from several streams, BNC votes on its content: the
    10072     first copy received is uploaded immediately; every further stream counts as a vote for the copy it delivers, and
    10073     a copy with different content replaces the uploaded one as soon as more streams deliver it than the current one,
    10074     i.e. with at least three streams. The content compared is the RTCM Version 3 message as uploaded, for GLONASS
     10072    first copy received is buffered; every further stream counts as a vote for the copy it delivers, and
     10073    a copy with different content replaces the buffered one as soon as more streams deliver it than the current one,
     10074    i.e. with at least three streams. A new data set is uploaded as soon as three streams deliver the same content as
     10075    the buffered copy, at the latest 40 seconds after its first copy; until then the previous data set of the
     10076    satellite stays in the upload; the hold is checked with each ephemeris received and every second. Data sets of satellites whose previous data set came from less than three streams
     10077    (and the first data set of a satellite) are uploaded immediately, as the vote cannot decide there. Receivers and
     10078    applications usually keep the first copy of a data set they received, also BNC itself, so a later replacement
     10079    with the same TOC and IOD would not reach them. The maximum of 40 seconds leaves time for the upload interval and
     10080    the latency before SSR providers may use the new IOD, 60 seconds after its broadcast; three streams agreed in the
     10081    median after 14 seconds and in 87 percent of the data sets within 40 seconds with 89 input streams
     10082    (18 Nov 2026). A replacement after the upload is still possible. The content compared is the RTCM Version 3 message as uploaded, for GLONASS
    1007510083    without the frame time tk and the system time offsets tau_c and tau_GPS, which differ legitimately between
    1007610084    receivers. This protects the uploaded stream against single receivers sending e.g. wrong health flags. Each
    … …  
    1008110089ephemeris vote R19 2026-11-18 17:45:18: copy of RIO200ARG0 replaced by that of BRAZ00BRA0 (2 of 3 streams;
    1008210090  - RIO200ARG0, + BRAZ00BRA0 RGDG00ARG0; differing: Cn A Bn P3 NA N4)
     10091</pre>
     10092  <p>
     10093    A data set uploaded after 40 seconds without three agreeing streams is logged as well, e.g.
     10094  </p>
     10095  <pre>
     10096ephemeris vote G14 2026-11-18 20:00:00: copy of OWMG00NZL0 uploaded after 40 s without 3 agreeing streams
     10097  (2 of 4 streams)
    1008310098</pre>
    1008410099  <p>
Note: See TracChangeset for help on using the changeset viewer.