The JAS specific services will be based on the PUS service concept. Most PUS services were created for communication between onboard applications and ground systems. JAS adds additional services to support more onboard payload functions.
[Placeholder: Additional development is needed to define the JAS specific services to support onboard payload functions. Future releases of this specification will have more concrete specifications.
Contact SNL if immediate support is needed with this topic. Content will be developed for JT 2.0.]
The PUS standard uses APID exclusively to identify any entity in the system that is the source or destination of command and telemetry data. JAS introduced additional identifiers to help further categorize elements within the payload. These identifiers are used within the data fields of messages. Examples are device, file or memory buffer identifiers. These identifiers allow applications to access physical elements within the payload using abstract references. It is assumed that configuration tables will be provided mapping from the abstract identifiers to their physical references. The configuration tables are typically stored separately from the applications in non-volatile memory, allowing them to be changed independently. All of this is in an effort to make applications more portable and reusable.
"Internal Standards developed by Sandia National Laboratories". Experience Base, Sandia National Laboratories, Albuquerque, NM, 0000.