I hope that the U/V digital service is 8-bit transparent so that it can be used efficiently for non-text communication, like APRS and collecting weather data with the fewest number of bits. It's also not a store-and-forward system so it really isn't messaging - although that could be added if message size was restricted. The number of data rates implemented in the ACP or SDX could be increased, so attaching names to each data rate may be a problem. How about calling class 1 advanced low-speed satellite communication (ALSC) and class 2 and 3 advanced high-speed satellite communication (AHSC)? There could then be a suffix for each data rate, such as AHSC-4800 and AHSC-256K.
73,
John KD6OZH
----- Original Message ----- From: "Dick Jansson-rr" rjansson@cfl.rr.com To: "'Matt Ettus'" matt@ettus.com; "'AMSAT Eagle'" Eagle@amsat.org Sent: Monday, October 09, 2006 21:35 UTC Subject: [eagle] Re: Service class names
I think that Matt has hit the nail on the head. This a simple extension of an existing nomenclature system. We worked hard to establish this system for AO-40. It isn't broken, don't fix it - use it!
Dick Jansson
rjansson@cfl.rr.com
-----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Matt Ettus Sent: Monday, 09 October, 2006 1851 To: 'AMSAT Eagle' Subject: [eagle] Re: Service class names
The more I think about it, the more I think we don't need to name anything. We just say the satellite has these users:
U/V Linear L/S Linear Text messaging Low Rate ACP High Rate ACP
By not having an ordering, nobody gets slighted, and there is less confusion.
Matt _______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle