Domain: ccsds.org
Stories and comments across the archive that link to ccsds.org.
Comments · 15
-
What people need are specifications
Fortunately, I have them.
Space Communications Protocol Specifications
Consultative Committee for Space Data Systems
CCSDS Technical Specifications
Space Assigned Numbers Authority
Spacecraft ID list and manual
Disruption Tolerant Networking
Exploration and Space Communications at NASA
Free Space Optical Communication -
What people need are specifications
Fortunately, I have them.
Space Communications Protocol Specifications
Consultative Committee for Space Data Systems
CCSDS Technical Specifications
Space Assigned Numbers Authority
Spacecraft ID list and manual
Disruption Tolerant Networking
Exploration and Space Communications at NASA
Free Space Optical Communication -
What people need are specifications
Fortunately, I have them.
Space Communications Protocol Specifications
Consultative Committee for Space Data Systems
CCSDS Technical Specifications
Space Assigned Numbers Authority
Spacecraft ID list and manual
Disruption Tolerant Networking
Exploration and Space Communications at NASA
Free Space Optical Communication -
Re:Speed or power?
[INT. ENTERPRISE BRIDGE]
Picard: Mr. LaForge, we're having trouble receiving the signal from the Very Far Away Observatory. Can you boost the signal.
LaForge (v.o.): Sir, we're already using a holographic multi-modal optical receiver.We're operating near the theoretical limit.
Picard: Prehaps you could route secondary power through the replicators in the galley on deck 12.
LaForge (v.o.): Uhm ... yeah ... I'll get right on that. LaForge out.
Power v. Bandwidth is always one of the spacecraft design tradeoffs. For signals with really low power at the receiver, smaller bandwidth can be beneficial because you can use filters (physical and DSP) to improve your SNR and your chances of recovering your data. Generally, you can't evaluate each piece in the comm link individually. The trick is to find a solution that meets your power budget, link budget, bandwidth objective, mass budget, volume budget ... all simultaneously.
If you want some interesting docs on space communications, check out the pubs from the CDSDS. -
DTN
Delay / Disruption Tolerant Internet (DTN) is still at the Research Group stage. It's really more about replacing TCP than the Internet (UDP will work just fine in space), and has received some criticism (pdf download), ironically mostly centered around how it breaks the end-to-end principle.
While there is now an SIS-DTN green book (a necessary step for general deployment on space missions), and initial tests in space are positive, these things move so slowly that I think it's going to be a while before this is generally deployed in space.
-
DTN == Twitter in spaceVint Cerf on DTN:
streaming is a little nuts but file transfers will work - delays will be long however.
sensor nets are a natural. as is email
short messaging ditto
status reports from systems; some forms of control also ok.
image transfer, no problem.
vhttp://mailman.ccsds.org/pipermail/sis-dtn/2008-July/000038.html
-
Re:Open protocol
Actually, the majority (at least recently) use CCSDS
-
This is not new
The "Open" standards that are implied in this message are those developed by the CCSDS and OMG.
Go to the website http://www.ccsds.org/ ... there are some very interesting standards especially one called XTCE, which is the used for describing spacecraft data systems. -
Re:Vint
-
Re:Latency over lightyears...we'll have to use something different for IPN communications.
Look no further:
http://www.ccsds.org(Vint Cerf has a irons in this fire)
-
Interplanetary Internet
Routers in space will be the first steps towards an interplanetary internet. The folks at CCSDS (Consultive Committee for Space Data Systems) have been working on an interplanetary internet specification for a while now. Some additional technical details and other information is also available. Very interesting stuff.
-
Re:Interesting Rover data
MER is using Consultative Committee for Space Data Systems protocols (although I'm not sure which parts of the protocol suite they are actually using). As far as error correction schemes go, they were considering using a CCSDS standard Turbo code. I'm not sure if that actually went through - if not they are probably using a Reed-Solomon code.
-
Re:Engineering Issues with Space Design
NASA already uses multicast UDP for transferring telemetry and command data between ground stations and control centers/experimenters. Congestion control is handled by scheduling the bandwidth of the data lines. This is on a private NASA Internet that is not connected to the public Internet. The air/ground communications links use the CCSDS standards.
-
The Larger Mesh...IPNSIG (the InterPlanetary Internet Special Interest Group) submitted this document to the IETF. It's interesting to note that IPNSIG is looking at very long-term solutions, but (to me at least) it's equally fascinating to read about current space communications standards in development that already take into account many, indeed nearly all, of the "far reaching" recommendations made in the post.
Readers may be interested in the CCSDS (Consultative Committee for Space Data Systems) homepage which has many protocols, proposals, and drafts available for public review. Take for example their file transfer protocol (PDF - start reading on page 20) that already "bundles" data and looks to be somewhat comprehensively thought out.
Food for thought; these principles have not only been conceived before, but reduced to standards (and implementation).
-
The Larger Mesh...IPNSIG (the InterPlanetary Internet Special Interest Group) submitted this document to the IETF. It's interesting to note that IPNSIG is looking at very long-term solutions, but (to me at least) it's equally fascinating to read about current space communications standards in development that already take into account many, indeed nearly all, of the "far reaching" recommendations made in the post.
Readers may be interested in the CCSDS (Consultative Committee for Space Data Systems) homepage which has many protocols, proposals, and drafts available for public review. Take for example their file transfer protocol (PDF - start reading on page 20) that already "bundles" data and looks to be somewhat comprehensively thought out.
Food for thought; these principles have not only been conceived before, but reduced to standards (and implementation).