{"id":23640,"date":"2022-04-01T11:15:34","date_gmt":"2022-04-01T10:15:34","guid":{"rendered":"https:\/\/reseau-orpheon.fr\/the-orpheon-network\/a-private-data-network\/"},"modified":"2024-05-14T15:35:30","modified_gmt":"2024-05-14T14:35:30","slug":"a-private-data-network","status":"publish","type":"page","link":"https:\/\/reseau-orpheon.fr\/en\/the-orpheon-network\/a-private-data-network\/","title":{"rendered":"A private data network"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Guarantee real-time availability<\/h3>\r\nTo be able to offer the best rate of data and service availability, we have optimized our infrastructures and implemented leading technical solutions with an MPLS (MultiProtocol Label Switching) infrastructure, which is an end-to-end private network, which does not does not travel over the Internet.\r\n\r\nAs corrections are disseminated in real time, it is essential to have better infrastructures to guarantee all data flows:\r\n
    \r\n \t
  • The streams from our stations to feed the servers<\/li>\r\n \t
  • The incoming and outgoing feeds of positions and corrections of each user<\/li>\r\n<\/ul>\r\nthe user’s mobile must receive at each measurement period (typically every second) the “corrections” corresponding to its work area, even when it is moving.\r\n\r\nThese corrections reach each user continuously by GPRS with an average delivery time of 750 ms, the standard deviation, i.e. the deviation from the mean for 68% of the corrections sent, also being of this magnitude.\r\n\r\nIn order to keep the system consistent, there is therefore less than 250ms left for:\r\n
      \r\n \t
    1. Receive observations from permanent stations on the computer center<\/li>\r\n \t
    2. Make them temporally consistent<\/li>\r\n \t
    3. Calculate “corrections”<\/li>\r\n \t
    4. Send “corrections” to user<\/li>\r\n<\/ol>\r\n\"null\"\r\n

      We have therefore chosen a very efficient infrastructure<\/h2>\r\n
      \r\n

      The implementation of this telecommunications network guarantees us the lowest possible latencies (data transmission time) between the permanent stations of the entire network and the computing center.<\/p>\r\n\r\n

      Goal: Have the lowest latencies<\/h3>\r\nThis uncompromising choice, in order to put the user’s mobile in the best possible situation by allowing it to receive as many corrections as possible in the most fluid and continuous way.\r\n\r\nThe load rates of a private network are guaranteed by the telecom operators offering this type of service. Such a network is also much more available than the Internet, the redundancy of the links being provided by the operators in charge of its operation.\r\n

      In the chain of transmission of corrections:<\/h3>\r\n

      The GPRS link between the GPS and our servers makes it possible to route 95% of the corrections with a latency of between 0 and 1.5 seconds, hence the capital importance of this proprietary network in terms of latency. A rover configured in interpolated mode (\u201caccuracy\u201d mode at Leica, \u201cforecast\u201d at Topcon and \u201cLow Latency\u201d at Trimble) can typically last 3 seconds without receiving corrections.<\/p>\r\n\r\n

      Why is an ordinary Internet connection not enough?<\/h3>\r\n

      The Internet is a network that pools resources for all users, on the principle of “best effort”, even if the performance deteriorates very sharply. The use of the Internet is therefore not relevant here, insofar as we wish to guarantee and control transmission times (latencies). The Orph\u00e9on network therefore does not undergo these “slowdowns” in order to be able to perform its correction calculations.<\/p>\r\n<\/blockquote>\r\n

      Full GNSS infrastructure<\/h2>\r\n
      With the idea of \u200b\u200breducing transmission times (latencies) as much as possible and increasing the availability of our services, powerful and reinforced machines used to calculate the NRTK correction, now Full GNSS, are hosted in a Datacenter located at the heart of the network of our telecommunications operator, that is to say as close as possible to its own machines.\r\n\r\nThe infrastructure and correction calculation software allow us to deliver “Full GNSS” corrections (GPS + GLONASS + Galileo + BeiDou)\r\n