13.07.2015 Views

CCSDS 734.2-R-1, CCSDS Bundle Protocol Specification (Red ...

CCSDS 734.2-R-1, CCSDS Bundle Protocol Specification (Red ...

CCSDS 734.2-R-1, CCSDS Bundle Protocol Specification (Red ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DRAFT <strong>CCSDS</strong> RECOMMENDED STANDARD FOR <strong>CCSDS</strong> BUNDLE PROTOCOL SPECIFICATION3 <strong>CCSDS</strong> PROFILE OF RFC 50503.1 GENERALThis document adopts the <strong>Bundle</strong> <strong>Protocol</strong> (BP) as specified in Internet RFC 5050(reference [1]), with the constraints and exceptions specified in section 3 of this document.3.2 COMPRESSED BUNDLE HEADER ENCODINGConformant implementations of the <strong>CCSDS</strong> <strong>Bundle</strong> <strong>Protocol</strong> shall implement the‘Compressed <strong>Bundle</strong> Header Encoding (CBHE)’ (reference [4]).NOTE – CBHE supports bit-efficient encoding of BP endpoint identifiers that use CBHEconformantschemes. Endpoints are identified by the combination of node numberand service number, both of which are Self-Delimiting Numeric Values (SDNVs).3.3 BUNDLE PROTOCOL EXTENDED CLASS OF SERVICEConformant implementations of the <strong>CCSDS</strong> <strong>Bundle</strong> <strong>Protocol</strong> shall implement the ‘ExtendedClass of Service (ECOS)’ block defined in annex B.NOTE – Spacecraft operations may require additional features beyond those identified inRFC 5050. One such feature is the expansion of the bundle process control flagsdesignated as ‘class-of-service’. ECOS provides the capability to prioritize orextend the service classes. Such uses include:– the creation of emergency or critical traffic;– expansion of traffic priorities reflective of a diverse user environment;– special handling of bundles.3.4 USE OF TIME IN SECTION 6.1 OF RFC 5050Where the spacecraft time system does not provide sufficient precision to support therequirements of RFC 5050 section 6.1, the precision of the onboard system shall be used.NOTE – Section 6.1 of RFC 5050 specifies that the time fields in administrative recordsuse seconds and nanoseconds since the start of year 2000. Spacecraft timesystems may not be able to provide meaningful values for the nanoseconds fieldsof these entries. In such a case the administrative time field shall support theprecision of the clock rate to the significant digits of the Command and DataHandling (C&DH) subsystem and will not drive requirements on the precision ofthe spacecraft clock.<strong>CCSDS</strong> <strong>734.2</strong>-R-1 Page 3-1 February 2012

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!