Recommended Posts

NASA and the European Space Agency have tested out a prototype system that may one day help enable Internet-like communications between Earth and robots on another planet.

Astronaut Sunita Williams, commander of the International Space Station's current Expedition 33 mission, used NASA's experimental Disruption Tolerant Networking (DTN) protocol to drive a small LEGO robot at the European Space Operations Center in Germany late last month.

The European-led experiment simulated a scenario in which an astronaut orbiting another world controls a robotic rover on the planet's surface, NASA officials said.

"The demonstration showed the feasibility of using a new communications infrastructure to send commands to a surface robot from an orbiting spacecraft and receive images and data back from the robot," Badri Younes, deputy associate administrator for space communications and navigation at NASA Headquarters in Washington, said in a statement.

"The experimental DTN we've tested from the space station may one day be used by humans on a spacecraft in orbit around Mars to operate robots on the surface, or from Earth using orbiting satellites as relay stations," Younes added.

NASA's DTN architecture is a new technology designed to enable standardized communications over long distances and through time delays, agency officials said. At its core is something called the Bundle Protocol (BP), which is similar to the Internet Protocol, or IP, that serves as the heart of the Internet here on Earth.

The big difference between the two is that IP assumes a seamless end-to-end data path, while BP is built to account for errors and disconnections ? glitches that commonly plague deep-space communications.

Data move through the BP network in a series of short hops, waiting at one node until the next link becomes available, NASA officials said.

source

NASA DTN Protocol: Interplanetary Internet, How It Works, What LEGOS Have to To With It

NASA is calling it the interplanetary Internet, and announcements have been hitting in recent weeks regarding the sending of the first emails, voicemails and, of late, news of an experiment that involved remote controlling of a LEGO space robot with it. But what?s truly cool is the technology enabling it ? it?s a protocol called Delay-Tolerant Networking, better known as DTN.

At its heart is Vint Cerf?s Bundle Protocol (BP), a version of the IP protocol he helped develop to pioneer the Internet decades ago.

In testing for several years, DTN got a major boost recently, says Badri Younes, a NASA administrator in Washington. Astronaut Sunita Williams ? she commanded the International Space Station?s current Expedition 33 mission ? used NASA?s experimental Disruption Tolerant Networking (DTN) protocol to drive a small LEGO robot at the European Space Operations Center in Germany late last month.

That was big news for the DTN and BP protocols, developed jointly by Internet pioneer +Vint Cerf and NASA?s Jet Propulsion Laboratory.

In a nutshell ? we?ll get down and dirty with the tech lower in the piece ? DTN allows a standard method of communication over long distances and through time delays, agency officials said. Its centering tech is similar to the IP protocol (that is the TCP/IP protocol) that is the building block of the Internet we use on Earth. That?s called the Bundle Protocol (BP).

The big difference between BP and IP is that, while IP assumes a more or less smooth pathway for packets going from start to end point, BP allows for disconnections, glitches and other problems you see commonly in deep space, Younes said. Basically, a BP network ? the one that will the Interplanetary Internet possible ? moves data packets in bursts from node to node, so that it can check when the next node is available or up.

?The demonstration (of the DTN controlled robot) showed the feasibility of using a new communications infrastructure to send commands to a surface robot from an orbiting spacecraft and receive images and data back from the robot,? Younes said. ?The experimental DTN we?ve tested from the space station may one day be used by humans on a spacecraft in orbit around Mars to operate robots on the surface, or from Earth using orbiting satellites as relay stations,? Younes added.

DTN-lego-NASA-ESA-robot-pic1-580x348.png

The first thing to understand is that the DTN testbed with BP driving it is in active testing now, NASA says.

Its first successful test was in 2008, when NASA announced that early DTN software for the first time enabled the transmission of more than a dozen of space images to and from a NASA science spacecraft located about 20 million miles (32M KM) from Earth. In a statement then, NASA?s Jet Propulsion Laboratory and Google?s +Vint Cerf said it kicked off the Interplanetary Internet. But what is DTN?

?The experimental DTN we?ve tested from the space station may one day be used by humans on a spacecraft in orbit around Mars to operate robots on the surface, or from Earth using orbiting satellites as relay stations,? Younes added.

In a nutshell, says NASA, ?The Disruption Tolerant Networking (DTN) program establishes a long-term, readily accessible communications test-bed onboard the International Space Station (ISS). Two Commercial Generic Bioprocessing Apparatus (CGBA), CGBA-5 and CGBA-4, will serve as communications test computers that transmit messages between ISS and ground Mission Control Centers. All data will be monitored and controlled at the BioServe remote Payload Operations Control Center (POCC) located on the Engineering Center premises at the University of Colorado ? Boulder,? reps said today.

interplanetary-internet-shot-nasa.gov_1-580x346.png

According to NASA?s Delay-Tolerant Networking Research Group (DTNRG), ?the DTN protocol is under active development.?

An experiment using DTN to control the LEGO robot is in the news today, but NASA says there are real world, military and consumer applications that affect Internet users worldwide.

?In addition to network security, research goals for the DTN activity will focus on testing and evolving important network services including naming and addressing, time synchronization, routing, network management and class of service,? NASA reps add, saying that ?the DTN experiments on the International Space Station (ISS) consist of software which is to be placed on both Commercial Generic Bioprocessing Apparatus (CGBA), CGBA-4 and CGBA-5, and then tested from a ground operations center.

What?s going on? Researchers explain ?the DTN activity will focus on testing and evolving important network services including naming and addressing, time synchronization, routing, network management and class of service. The DTN experiments on ISS consist of software (that) is to be placed on both Commercial Generic Bioprocessing Apparatus, CGBA-4 and CGBA-5, and then tested from a ground operations center. This software is not in any critical path of the CGBA operations and may be turned off at anytime. This software does not preclude the use of the CGBA units for other purposes or research support.

DTN, say NASA reps, is ?a networked architecture required to successfully complete these missions. The experiments that will be performed are designed to test the DTN protocol suite in an actual space environment, and to determine how well the protocols perform and what improvements may need to be made. The impact of the results of the research will help to advance the technical maturity of the DTN communications technology so that it is available for NASA use in both human and robotic Exploration missions.

"The Delay-Tolerant Networking Research Group (DTNRG) is a research group chartered as part of the Internet Research Task Force (IRTF). Members of DTNRG are concerned with how to address the architectural and protocol design principles arising from the need to provide interoperable communications with and among extreme and performance-challenged environments where continuous end-to-end connectivity cannot be assumed. Said another way, we are concerned with interconnecting highly heterogeneous networks together even if end-to-end connectivity may never be available. Examples of such environments include spacecraft, military/tactical, some forms of disaster response, underwater, and some forms of ad-hoc sensor/actuator networks. It may also include Internet connectivity in places where performance may suffer such as developing parts of the world.

"DTNRG members research aspects of delay-tolerant networking in a number of ways including academic publications, technical specifications, several active mailing lists, and code (reference implementation) development. DTNRG holds semi-regular teleconferences for software developers and occasional face-to-face public meetings. The public meetings usually occur in conjunction with an IETF meeting. The current co-chairs for DTNRG are Kevin Fall (Qualcomm), Stephen Farrell (Trinity College, Dublin) and J?rg Ott (Aalto University, Helsinki). Back in 2006 Stephen wrote a book on DTN. Several of the members of DTNRG participated in the (highly-related) DARPA Disruption Tolerant Networking program."

DTN research is necessary in space especially, NASA says, for the maturation of protocols to enable Internet-like communications with space vehicles, remote planetary habitats, rover vehicles and support infrastructure on a planetary surface. ?It is being tested for the first time on ISS Onboard (local) ISS , ISS-to-ground, and NASA ground communications networks will become DTN-enabled,? NASA says. ?That is the key stepping stone to enabling the Interplanetary Internet.

http://anewdomain.ne...-to-to-with-it/

Every article I've read on this has been kinda light on details, there's obviously a reason why DTN/BP is better than IP/UDP/TCP, but they don't say why specifically (The reasons given, things like latency or packet drop are an issue on IP networks to, part of it's design is to handle them)

From reading Wikipedia I get the idea that BP is message based, rather than packet based, but that's about it.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      +Edouard
      228
    3. 3
      PsYcHoKiLLa
      163
    4. 4
      Steven P.
      76
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!