SOIS architecture to handle RIUs

Slides:



Advertisements
Similar presentations
OSI Model OSI MODEL.
Advertisements

Protocols and the TCP/IP Suite
® The Bluetooth Architecture APIs, L2CAP, Link Management, Baseband, and the Radio.
The OSI Model and the TCP/IP Protocol Suite
Exemplar CFS Architecture
ESA UNCLASSIFIED – For Official Use EDS Schema F. Torelli & P. Skrzypek CCSDS Spring Meeting /04/2013.
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
Spacecraft Onboard Interface Services Application Support Services Working Group (SOIS-APP WG) CCSDS Spring 2013 Meeting.
SOIS P&P Concepts & Mapping of the Device Discovery service onto the MIL-STD-1553 Massimiliano Ciccone ESA/ESTEC 02-Oct-2007 (CCSDS-Darmstadt)
Building a Simple Serial Network © 2004 Cisco Systems, Inc. All rights reserved. Understanding the OSI Model INTRO v2.0—1-1.
ESA UNCLASSIFIED – For Official Use Example of EDS usage in SOIS [recap from SAFI meeting 23/6/2012] F. Torelli CCSDS SOIS WG, Darmstadt 17/04/2012.
12006 MAPLD International ConferenceSpaceWire 101 Seminar CCSDS Standard On-Board InterfaceS (SOIS) Rick Schnurr NASA – Goddard Space Flight Center CCSDS.
Layer Architecture Layer architecture simplifies the network design. It is easy to debug network applications in a layered architecture network. The network.
Spacecraft Onboard Interface Services Application Support Services Working Group (SOIS-APP WG) Use Cases Identified in ESA TRP Project CCSDS Spring 2013.
ESA UNCLASSIFIED – For Official Use SOIS architecture to handle RIUs F. Torelli (ESA) & G. Rakow (NASA) 15/04/2013.
A Study of Wireless Virtual Network Computing Kiran Erra.
ESA UNCLASSIFIED – For Official Use SOIS Evaluation by the Primes F. Torelli (ESA) Software Reference Architecture - Focus on the Execution Platform ADCSS.
ESA UNCLASSIFIED – For Official Use Metadata in SOIS Service Primitives F. Torelli & P. Skrzypek CCSDS Spring Meeting /4/2013.
1 SOIS Plenary Washington March 2008 Chris Taylor.
ESA UNCLASSIFIED – For Official Use Recap of SOIS Evaluation by the Primes F. Torelli (ESA) CCSDS Spring Meeting, 23/03/2015.
ESA UNCLASSIFIED – For Official Use SOIS EDS & Toolchain ESA YGT Study F. Torelli & P. Skrzypek CCSDS Fall Meeting /10/2013.
An Introduction to Networking
ESA UNCLASSIFIED – For Official Use Inputs to SOIS EDS Schema F. Torelli CCSDS SOIS WG, Darmstadt 17/04/2012.
RIU as related to SOIS EDS Glenn Rakow CCSDS SOIS Spring Meeting 2013.
1 CCSDS 2007 Fall Meeting SOIS Plenary Chris Taylor Estec (27/09/2007.
SOIS EDS and Onboard Architectures. ESA ‘de-facto’ Architecture PUS Services Mission Applications Data Handling PUS TM/TC Internal Datapool API System.
CCSDS SOIS Working Group Meeting – Berlin, Germany 14th of October 2008 Prototyping of CCSDS SOIS services on 1553 Bus Sev Gunes-Lasnet, Olivier Notebaert.
ESA UNCLASSIFIED – For Official Use NPAL Datasheet F. Torelli & P. Skrzypek CCSDS Spring Meeting /04/2013.
Spacecraft Onboard Interface Services Application Support Services Working Group (SOIS-APP WG) CCSDS Spring 2013 Meeting.
Computer Engineering and Networks, College of Engineering, Majmaah University Protocols OSI reference MODEL TCp /ip model Mohammed Saleem Bhat
Chapter 4 : Network models. Lecture 8. Layered Tasks - We use the concept of layers in our daily life. As an example, let us consider 2 friends who communicate.
Written by : Oren Frenkel Intel Confidential ® C CD SDS.
SOIS Services. Layered View This is the traditional diagram that summarizes SOIS services in layers of a protocol stack.
ESA UNCLASSIFIED – For Official Use Migration of information along the Onion diagram F. Torelli CCSDS Fall Meeting /10/2013.
OSI Model OSI MODEL. Communication Architecture Strategy for connecting host computers and other communicating equipment. Defines necessary elements for.
OSI Model OSI MODEL.
Protocols and the TCP/IP Suite
SOIS APP Working Group Overview
Subnet plus Composable Applications
Prototyping of CCSDS SOIS services on 1553 Bus
I/O SYSTEMS MANAGEMENT Krishna Kumar Ahirwar ( )
SOIS Application Support Services WG – Fall 2009 Meeting
Exemplar CFS Architecture
Version 4, 2016 March 1 Teleconference
HTTP Server Protocol Module :
Network Architecture Layered system with alternative abstractions available at a given layer.
Version 3, with post 19 Jan 2016 Telecon mods
A Study of Wireless Virtual Network Computing
Recap of SOIS Evaluation by the Primes
Polled Device Data Aquisitions
Lecturer, Department of Computer Application
CHAPTER 4 TOP LEVEL VIEW OF COMPUTER FUNCTION AND INTERCONNECTION
1 Input-Output Organization Computer Organization Computer Architectures Lab Peripheral Devices Input-Output Interface Asynchronous Data Transfer Modes.
TECH SESSION #1 ELECTRONIC DATA SHEETS
& Mapping of the Device Discovery service onto the MIL-STD-1553
DEPARTMENT OF COMPUTER SCIENCE
CS4470 Computer Networking Protocols
SPACECRAFT ONBOARD INTERFACES SERVICES
SOIS EDS Interoperability
SPACECRAFT ONBOARD INTERFACES SERVICES
Inputs to SOIS EDS Schema
See embedded notes post 21 Sept telecon
Integrating CCSDS Electronic Data Sheets into Flight Software
Direct Attached Storage and Introduction to SCSI
Protocols and the TCP/IP Suite
Introduction to networking
OSI Model OSI MODEL.
ARCHITECTURE OVERVIEW
Protocols and the TCP/IP Suite
Chapter 4: outline 4.1 Overview of Network layer data plane
Presentation transcript:

SOIS architecture to handle RIUs F. Torelli (ESA) & G. Rakow (NASA) 15/04/2013

Outline Remote Interface Unit (RIU) definition Tunnelling RIU and SOIS Smart RIU and SOIS RIUs and SOIS EDS Summary The presentation summarises the tech note “Aggregated devices in SOIS and SOIS EDS” distributed to the SOIS WG mailing list on 28/11/2012

Remote Interface Unit (RIU) definition

Remote Interface Unit 1/2 Also known as Remote Terminal Unit Connects devices to the Processor Module (PM) where flight SW (FSW) runs Data concentrator Physical aggregation Interfaces to very simple sensors/actuators Interfaces to smart devices Handles point-to-point links Handles sensor buses Sensor bus DEVA Point-to-point link DEV1 DEVB DEV2 DEVC Processor Module FSW RIU I/F Logic System bus/subnetwork

Remote Interface Unit 2/2 Tunnelling RIU: PM manages each device separately PM is aware of the access protocol and data formats of each device RIU is just a multiplexer/demultiplexer Smart RIU: RIU autonomously access the devices RIU is aware of access protocol and data formats of each device PM is only aware of the access protocol and data formats of the RIU DEVA DEVA DEV1 DEVB DEV1 DEVB DEV2 DEVC DEV2 DEVC RIU complexity RIU Cmd & Acq Logic RIU Mux/Demux

Tunnelling RIU and SOIS

Tunnelling RIU in SOIS 1/2 Device access protocol is managed at DAS level in the PM The “simple” RIU Mux/Demux protocol is managed at DAS level in the PM System bus communication between PM and RIU is managed at subnetwork level

Tunnelling RIU in SOIS 2/2 Possible mux/demux mechanisms: Commands/data encapsulation via Packet Service Time separated commands via Packet or Memory Access Service Packet exchanged at the subnetwork service interface Cmd/Data consumed/produced by Dev X RIU Channel X Selector Dev X Header Dev X Command/Data Packet exchanged betwen RIU and Dev X RIU Channel X Selection Dev X Command/Data RIU Channel Y Selection Dev Y Command/Data Command to RIU Cmd/Data to/from Dev X Command to RIU Cmd/Data to/from Dev Y

Smart RIU and SOIS

Smart RIU in SOIS 1/2 Device access protocol is managed at RIU level Device data are accessed via RIU DAS using specific Value Ids RIU access protocol is managed at DAS level in the PM System bus communication between PM and RIU is managed at subnetwork level

Smart RIU in SOIS 2/2 Possible RIU/device access mechanisms: Devices Cmd/Data mixed inside RIU Cmd/Data (Packet Service) Devices Cmd/Data allocated in RIU memory space (Memory Access Service) Packet passed to the subnetwork service RIU Header Dev X Cmd/Data 1 Dev Y Cmd/Data 1 Dev X Cmd/Data 2 Dev X Cmd/Data for Value Id X1 Dev Y Cmd/Data for Value Id Y1 Dev X Cmd/Data for Value Id X2 Dev X Cmd/Data 1 at 0x10 Value Id X1  MAS rd/wr.req to RIU at addr 0x10 Dev X Cmd/Data 2 at 0x20 Value Id X2  MAS rd/wr.req to RIU at addr 0x20 Dev Y Cmd/Data 1 at 0x28 Value Id Y1  MAS rd/wr.req to RIU at addr 0x28 Dev X Cmd/Data 3 at 0x30 Value Id X3  MAS rd/wr.req to RIU at addr 0x30 Dev Z Cmd/Data 1 at 0x34 Value Id Z1  MAS rd/wr.req to RIU at addr 0x34 Dev Z Cmd/Data 2 at 0x3C Value Id Z2  MAS read.req to RIU at addr 0x3C

RIUs and SOIS EDS

Tunnelling RIU and SOIS EDS RIU + Devices can be described by separate EDS The DAS of each Device is built from RIU and device specific EDS Adding a new device to the RIU implies introducing the new Device EDS and a new DAS instance and updating the Device Layout in the RIU EDS Dev1 EDS Service I/F Dev1 Access Prot. Dev2 EDS Service I/F Dev2 Access Prot. RIU EDS Service I/F Mux/Demux Prot. Devices Layout

Smart RIU and SOIS EDS One EDS describes RIU + Devices as a single equipment The DAS of the RIU is built from RIU EDS only Adding a new device to the RIU implies updating the RIU EDS and regenerating the MIB of the RIU DAS to access the new valid Value Ids RIU EDS Service I/F RIU Access Prot. Devices Layout RIU EDS is built using devices EDS as input (for data formats) Credit for the onion diagram: S. Fowell

Summary

Summary Tunnelling RIU Smart RIU 1 DAS for every device Each Access Protocol composed by device + RIU access protocol 1 EDS for each device 1 EDS for the RIU RIU as equipment is described by the collection of the device and RIU EDS Smart RIU 1 DAS for the RIU as equipment RIU Access Protocol in charge to extract the device specific data from the RIU data 1 EDS for the RIU as equipment EDS is built with inputs from device EDS