TOFFEEプロジェクト
ホームドキュメンテーション更新ビデオ研究ダウンロードスポンサー接触


RESEARCH 》 A study on Deep Space Networks (DSN)

When you are dealing Deep Space Networks (DSN) one among the most challenging parts is the Interplanetary distances and communicating data across such vast distances. This is where we are not dealing with common Internet type traffic such as HTTP/FTP/VoIP/etc but it is completely different when it comes to DSN so far. So optimizing data in DSN becomes mandatory. For example if you think one of the Mars Rovers, they have used LZO lossless compression. Although they do to an extent lossy compression on images shot by these space-probes at times they we may also need high-resolution detailed high-quality images. And sometimes it is not just photos sent back to the earth, at times the space probes may also report their health status, keep alive messages as well transmit the scientific research data such as data recorded in various sensors situated on-board.

Although we got space probes across the space and ISS (International Space Station) orbiting over Earth, we do not have a scenario yet something like human colonies/bases on Moon or Mars and other planets. Eventually when such things happen in around 2020-2030 or so as the way NASA and scientists predict, DSN is going to be a case where more private companies may offer their solutions. But before that we need to still solve some of the fundamental data communication challenges involved in DSN. This is on of the fields which I am actively involved since a decade.

Unlike here on Earth upgrading a piece of hardware or communication technology is just impossible to do on a space probe which may exist millions of miles away from Earth. This also makes this technology evolve quite slowly unlike Earth bound communication technologies such as Mobile communications, Satellite networks and so on. For further complete coverage of this topic kindly refer my below detailed video titled Deep Space Communication - Episode1.

Understanding Communication Speeds: Most DSN networks are radio-wave signal based and not light (photonic) based communication. Radio waves do not travel at the speed of light. It is also one of the reason for the slow-down of the DSN unlike ground or earth bound fibre optic links since in this case data travels almost (since the medium is not vacuum and speed of light depends on the medium) at the speed of light. Before we imagine network speeds in DSN, let us understand an ideal situation of speed of light between two points in space:

Distance Speed of Light
Earth <> Moon1.5 seconds
Earth <> Mars4 minutes (240 seconds)
Earth <> Sun8 minutes (480 seconds)
Earth <> Jupiter30 minutes (1800 seconds)
Earth <> Saturn1 hour (3600 seconds)
Earth <> Neptune4 hours (14400 seconds)
Earth <> Pluto4.6 hours (16560 seconds)

NOTE: Since we compute network speeds often in bits/sec (and latency in nano-seconds and milli-seconds), in the above chart I am converting everything in seconds to understand the scale.

So based on the above chart now we can understand the scale of complexity in DSN. This underscores a fundamental limitation of physics !

Communication Protocols for DSN: For DSN a complete new set of protocols are defined which is SCP (stands for Space Communications Protocol). There are various RFCs which are defined which is called as SCPS (where S stands for Specifications). There are various variants under SCPS are defined such as SCPS-FP, SCPS-TP, SCPS-SP and SCPS-NP. The biggest difference you may find in DSN is that the delay involved due to inter-planetary distances. So based on the distance you may experience communication delays, loss of packets, etc. Say for example if you think a successful connection is established (for example a TCP session/connection), you may have to-and-fro keep alive acknowledgement packets exchanged every few milliseconds. But whereas in a case of DSN you may experience this happening every few minutes or every few hours. So that is how bizarre it is. Although there is no packet exchanges happening in few minutes or hours you should understand this is due to vast distances involved.

These SCPS specifications are defined by a committee called as CCSDS (stands for Consultative Committee for Space Data Systems). This is a body which is formed as per collaborative effort of various space agencies across the world. An Internet spanning across multiple planets is termed as IPN (stands for Interplanetary Network or in short InterPlanet). For further complete coverage of this topic kindly refer my below detailed video titled Deep Space Communication - Episode2.

Lossless Compression Algorithms for DSN: A specific set of tailor made algorithms are required for space communications unlike the ones which are used in communications here on Earth. They have to be light-weight and at the same time super-efficient and should have least processing latencies. The communication data could be just anything such as scientific research data collected via space probe sensors or it could be hi-resolution photos sent back to earth or it could be commands sent to these probes via ground control crew. I have done extensive research on this for almost more than a decade on various lossless compression algorithms. This is a case where we are dealing optimizing real-time data. This is not a passive file compression something like creating a tar-ball or some zipfile. This is a case you are sending and receiving packets continuously and you are processing them in real-time.

NASA have their own lossless compression variants and often they are customized. One of the well known algorithms which NASA uses is the LOCO-I (stands for Low Complexity Lossless Compression) which is mainly meant for compressing images. LOCO-I is a kind of lossless compression variant of JPEG. Which is why it is also can be sometimes called as JPEG-LS (stands for JPEG-Lossless). Based on LOCO-I NASA did hardware based solution which is FPGA-LOCO. Since it is hardware based, it is good in performance, reliability and extremely energy efficient.

Apart from this CCSDS have their own variant of RICE lossless compression algorithm. For further complete coverage of this topic kindly refer my below detailed video titled Space Lossless Compression.

References:

NASA:

Wikipedia:

Other:



Suggested Topics:


WAN Optimization and Network Optimization

💎 TOFFEE-MOCHA new bootable ISO: Download
💎 TOFFEE Data-Center Big picture and Overview: Download PDF


おすすめトピック:

TOFFEE-Mocha WAN Emulation software development - Update: 1-July-2016 ↗
Saturday' 13-Mar-2021
Today I got a feature request from Jonathan Withers. Jonathan is from a company called MultiWave Australia. He said he is able to get the TOFFEE-Mocha Raspberry Pi setup up and with that he is able to emulate geostationary satellite link. But he requested me is there a way to extend the constant packet delay from 40mS to 500mS. So as a part of his request I supported the same in the current ongoing development version of TOFFEE-Mocha.

INDEX :: Content Delivery Networks or Content Distribution Networks (CDN) ↗
Saturday' 13-Mar-2021

TOFFEE-Mocha WAN Emulation software development - Update: 15-July-2016 ↗
Saturday' 13-Mar-2021
Today I completed doing all the changes which are meant for the new upcoming TOFFEE-Mocha release. I have increased the resolution and the range of all factor variables. Instead 1 to 10 range now they have a range of 1 to 30. Unlike before the value 1 means it is lot more intense (or in some cases less intense) and the uppermost value 30 means lot less intense (or in some cases lot intense).

TOFFEE-Mocha WAN Emulation software development - Update: 19-July-2016 ↗
Saturday' 13-Mar-2021
Today I refined the first page consolidated report graphs. TOFFEE-Mocha (unlike TOFFEE) is a WAN Emulator, so the graphs are supposed to highlight this purpose and should display the overall network activity. Unlike TOFFEE, the TOFFEE-Mocha report should contain in general what is received versus what is sent across the wire. In case if the packet drop feature is enabled, you should see few missing bytes and packets. Similarly in future I may support packet duplication feature, in that case you may see more packets/bytes sent versus the packets/bytes actually received.

The TOFFEE Project :: TOFFEE-Butterscotch :: Save and Optimize your Internet/WAN bandwidth ↗
Saturday' 13-Mar-2021
TOFFEE-Butterscotch is an open-source software which can be used to save and optimize your Internet/WAN bandwidth. Unlike TOFFEE (and TOFFEE-DataCenter) TOFFEE-Butterscotch is a non peer-to-peer (and asymmetric) network optimization solution. This makes TOFFEE-Butterscotch an ideal tool for all Home and SOHO users.

CDN Content Delivery Networks - Types ↗
Saturday' 13-Mar-2021



CDN Introduction - Content Delivery Networks or Content Distribution Networks ↗
Saturday' 13-Mar-2021

Network Latency in WAN Networks and performance optimization ↗
Saturday' 13-Mar-2021
Here is my video article on Network Latency in WAN Networks (such as long distance Satellite links, etc) and how you can optimize the same to achieve better network performance.

Riverbed and Silver Peak WAN Optimization vs TOFFEE-DataCenter (TOFFEE and or TrafficSqueezer) - FAQ ↗
Saturday' 13-Mar-2021

Building my own CDN - Finally Completed - Update: 17-Dec-2017 ↗
Saturday' 13-Mar-2021
Today I finally completed building my own private CDN. As I discussed so far in my earlier topics (Building my own CDN), I want to custom build the same step-by-step from scratch. And I don't want to for now use/buy third-party CDN subscriptions from Akamai, CloudFlare, Limelight, etc as I discussed earlier.



Featured Educational Video:
Youtubeで見る - [17445//1] 294 - VRF - Virtual Routing and Forwarding - Introduction ↗

Detect and Monitor Failing Harddrive in Linux - My Seagate 500GB HDD Died ↗
Saturday' 13-Mar-2021
My 500GB Seagate Barracuda 7200RPM hard-drive suddenly started making mild clicking noise. I found this happening since morning. I was suspicious that something wrong in this drive and when I opened the Linux Disks app, I can find the cause of this issue. The disk is increasingly getting read errors. Besides I can see various other parameters such as Power-On Hours, Temperature, Head flying hours, etc.

TOFFEE-DataCenter - First Live Demo and software development - Update: 26-Aug-2016 ↗
Saturday' 13-Mar-2021
Today I have done a test setup so that I can able to connect my Android Samsung Tab via TOFFEE DataCenter. Below is my complete test topology of my setup. For demo (and research/development) context I configured TOFFEE DataCenter in engineering debug mode. So I do not need two devices for this purpose.

CDN Hosting ↗
Saturday' 13-Mar-2021
It is quite interesting that there are few web hosting firms are offering direct CDN based hosting services. Since it is a direct CDN based hosting, it is cheap, extremely easy or transparent CDN service. It is transparent, since each time you publish your content in the hosting web-server (origin server), it is immediately is in sync automatically in the user-serving CDN caching machines. Since the hosting vendor and the CDN vendor are all the same, it is also easy to use their services. There is no incompatibility issues, interoperability issues, and better integrated analytics, are all the benefits of CDN Hosting services.

TrueBench - Linux CPU Benchmarking system ↗
Saturday' 13-Mar-2021
TrueBench is an unique open-source benchmarking system in which the core system performance and efficiency parameters are measured at extreme high resolution in the order of several million/billion µ-seconds for a given specific task. TrueBench is a part of The TOFFEE Project research.




Streaming CDN Types ↗
Saturday' 13-Mar-2021



Research :: Optimization of network data (WAN Optimization) at various levels:
Network File level network data WAN Optimization


Learn Linux Systems Software and Kernel Programming:
Linux, Kernel, Networking and Systems-Software online classes


Hardware Compression and Decompression Accelerator Cards:
TOFFEE Architecture with Compression and Decompression Accelerator Card


TOFFEE-DataCenter on a Dell Server - Intel Xeon E5645 CPU:
TOFFEE-DataCenter screenshots on a Dual CPU - Intel(R) Xeon(R) CPU E5645 @ 2.40GHz - Dell Server