ub3ratl4sf00 at gmail.com
Wed Jun 26 00:50:40 UTC 2013
Our SATCOM system utilizes basically two satellite channels to achieve ISDN
capability (two 64 kb pipes) so that imagery data can be fed back to
whoever wants it. This was our old system, via INMARSAT of Britian.
We have a new SATCOM system, and I don't even have a clue of its throughput
yet, but its going to be better.
On Tue, Jun 25, 2013 at 8:46 PM, Mike Harrison <cluon at geeklabs.com> wrote:
> Slightly off topic, but the SATCOM stuff the Air Force has is amazing.
> Steven, What can you link to or share without fear of giving away national
> secrets, impuning the NSA.. etc..
> I'm interested in many ways... for example, I know we have a utility in W.
> Africa using Sat coms to use Juice and are impressed with how it works in a
> high latency environment. I know they are on 64k links with 150ms to 300ms
> round trips.
> From memory: 64k might be expressed as one half an ISDN connection,
> ISDN is 2 B's (64k each) and a D or lower rate data/signalling channel.
> Multiple B's (64k) can be bonded together for aggregate bandwidth
> with that D (data) channel providing sync and bonding info.
> I can see where that same structure could be used for any communications
> medium, just kind of suprised that it is. I'd like to know what the useful
> typical limits are in the military variations.
> Chugalug mailing list
> Chugalug at chugalug.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Chugalug