Lorenzo Maria Gagliardini

English

PORTO@iris (Publications Open Repository TOrino - Politecnico di Torino)

29 November 2022POLITECNICO DI TORINORepository ISTITUZIONALEPacket Utilisation Standard and Mission Operations: a Service Frameworks Comparison / Gagliardini, LORENZOMARIA. - (2021). ((Intervento presentato al convegno Aerospace PhD Days.OriginalPacket Utilisation Standard and Mission Operations: a Service Frameworks ComparisonPublisher:PublishedDOI:Terms of use:openAccessPublisher copyright(Article begins on next page)This article is made available under terms and conditions as specified in the  corresponding bibliographic description inthe repositoryAvailability:This version is available at: 11583/2971676 since: 2022-09-23T12:49:07ZMUL2Lorenzo GagliardiniPolitecnico di Torino, ITALYPacket Utilisation Standard and MissionOperations: a Service FrameworksComparisonResearch areas:• Aerospace mission and system design• Space system Assembly integration• Functional verification• Technology developmentMain facilities:• CubeSat Concurrent Design Facility• Clean room ISO 7• Laminar Flow Bench ISO 5• Ground Control Station for CubeSatMain Topic: CubeSatSTAR Team: Undergraduate and PhD students led byProf. Sabrina Corpino Politecnico di Torino- STAR TeamService Oriented Architectures (SOA)TBD 3• Application Level• Service Level• Communication LevelApplication Level❑ Each Application Process constitutes a separate entity❑ The applications/components rely on the service level to exchange data❑ No common standard for conceiving the On-board elementsTBD 4Service LevelBoth ECSS Packet Utilisation Standard and CCSDS Mission Operations define the features of this layer, in terms of:TBD 5❑ The communication behaviours with other application processes❑ The type of information❑ The intrinsic semantic of the informationCommunication LevelService specific information (e.g. Parameter Setting)TBD 6Protocol consistent structureThe Communication level allows the translation:SPP → TCP/IPTranslationECSS Packet Utilisation Standard (PUS)TBD 7ECSS-E-ST-70-41AECSS-E-ST-70-41BECSS-E-ST-70-41CECSS Packet Utilisation Standard (PUS)❑ The service message structure reflects the semantic of the service-specific informationTBD 8Set Parameter Value Service:• How many parameters?• Which parameters?• To which value?PUS Data Types:• Boolean• Enumerated• Unsigned Integer• Signed Integer• Real• Bit-string• Octet-string• Character-string• Absolute Time• Relative Time• Deduced• PacketECSS Packet Utilisation Standard (PUS)TBD 9Marked distinction between:❑ On-board processes❑ Ground-based processesTelemetryTelecommandTelecommandTelemetryECSS Packet Utilisation Standard (PUS)This Standard promotes using space packets compliant to the CCSDS space packet protocol to transport the PUS messages. It does not prescribe the protocol used to transport requests initiated on-board and reports destined for on-board.❑ A "telecommand packet" is the data unit that is used to carry a service request from an application process on the ground to an application process on-board ❑ A "telemetry packet" is the data unit that is used to carry a service report from an application process on board to an application process on the ground.TBD 10CCSDS Mission Operations (MO)TBD 11❑ Reduced heritage if compared with PUS❑Marked subdivision within the service layerCCSDS Mission Operations (MO)The Message Abstraction Layer (MAL) is responsible for the definition of:TBD 12❑Data types as basis for data structures❑Abstract definition of the message header❑Interaction patternsCCSDS Mission Operations (MO)TBD 13The Common Object Model (COM) defines:❑ How object refer to each other❑ The rules for managing service objectsCCSDS Mission Operations (MO)TBD 14❑ No distinction between on-board and ground-based processesData❑ Interaction patterns composed by message sequencesCCSDS Mission Operations (MO)TBD 15❑The data structure rely on the MAL data types❑Each service specification defines its data structuresCCSDS Mission Operations (MO)TBD 16Space Packet ProtocolTCP/IPHTTP..Service messagestructureConclusionsECSS PUS:❑ High heritage❑ Limited standardisation span❑ Too prescriptive in single parts❑ Heavy documentationWhich leads to:❑ Difficulties in adaptation❑ Need for very high expertiseTBD 17CCSDS MO:❑ Limited presence in the marketIndependency from:❑ Transport protocol❑ Implementation languageWhich allows:❑ Migration of platform❑ Software reuse❑ Separation of concernsNext StepsTBD 18• Application Level• Service Level: Standard service interface• Communication Level:SPP, HTTP, TCP/IPService-Protocol MappingImplementation into a specific programming languageThank YouTBD 19

Packet Utilisation Standard and Mission Operations: a Service Frameworks Comparison

https://iris.polito.it/bitstream/11583/2971676/1/AerospacePhDDays2021.pdf

Packet Utilisation Standard and Mission Operations: a Service Frameworks Comparison

Abstract

Similar works

Full text

Available Versions

PORTO@iris (Publications Open Repository TOrino - Politecnico di Torino)