sensor, interface and data interoperability esonet wp2 a) status eric delory dbscale env. tech.,...
TRANSCRIPT
Sensor, interface and data interoperability
ESONET WP2 a) statusEric Delory
dBscale Env. Tech., ICCM, ICEOAntoni Manuel, Joaquín del Rio
SARTI, UPC-CSICChristoph Waldmann, KDM
Outline
• Interoperability initiatives• ESONET statement and WP2 a) work items• Where we are: inventory of standards and
interoperability initiatives• sketch of the application of standards to a
generic sensor system• Where we are going: existing systems, to map
necessities and drawing recommendations
ESONET statement
<<The ESONET federation will oversee standards, data management and co-ordinate observatory deployment. Data will be interfaced to national and international data centres.>>
WP2 Standardization and interoperability a) work items
• Inventory of existing interoperability concepts as possible candidates for future observatory systems
• Inventory of existing sensors and interfaces• Recommendations and roadmap for possible
realisation schemes
Inventory of standards and interoperability initiatives
• Identification and mapping of existing standards– Sensing systems– Communication– Data management
• Identification of relevant interoperability initiatives (INSPIRE, GMES, IOOS, GEOSS)
Interoperability initiatives
• INSPIRE: Infrastructure for Spatial Information in Europe
• GMES: Global monitoring for Environment and Security
• EuroGOOS, IOOS Data Management and Communications
• IEEE Committee on Earth Observations• GEOSS Global Earth Observation System of
Systems
GEOSS SBAs and Systems
Component and services Registration Process
ESONET or Component Register Component
Reference registered standard
Work with SIF
Register ServiceComponent has interface?
Uses registered standard?
SIF recommends solution
Enter solution in registry
N
Y
Y
Y
N
NDone
Solution Accepted?
Interoperability of ESONET at largefrom sensor interfaces to data
Interoperability & Standards
What should be standardised ?
Interoperability
What can be standardised ?
“What few things must be the same so that everything else can be different” Eliot Christian, lead of GEO task AR 06-03
Inventory of standards• Sensing systems functional groups
– Networks topologies– Power– Data Storage/Memory– Clock– Interface– System Engineering– Languages– Cables– Connectors– Signal Modulation– Other features
Inventory of standardsData Storage/Memory Standards defining hardware, form
factors, memory access protocols and buses of interest applicable underwater sensor systems.
Bus/protocol: I2C, SPI, DMAProprietary EEPROM: SD, CompactFlash, USBDrives: SCSI, IDE, ATA, Fibre Channel
Clock Standards defining technical specifications and protocols to provide clock information and synchronise underwater sensors and sensor packages
LXI, IEEE 1588-2002, Network Time Protocol
Interface Standards defining hardware interfaces, of interest to underwater sensor and sensor packages, and general Science Instrument Interface Modules (SIIM)
IEEE 1451, IEEE 488, NMEA 0183, LXI TransducerML, USB, Firewire, Ethernet
System Engineering Standards defining complex systems engineering processes, architectures, other system engineering concepts and modeling
UML, SysML, ISO 10303-AP233, ANSI/GEIA EIA-632, EIA/IS 731.1, ECSS-E-10 (part 1B, 6A, 7A), ISO/IEC 15288: 2002, ISO/IEC 19760:2003, ISO/IEC 15504: 2004, ANSI/AIAA G-043-1992, IEEE 1471, 2000, Capability Maturity Model Integration (CMMI), UML Profile for DoDAF/MODAFSee: www.incose.org
Inventory of standardsLanguages Standards defining languages
specific to sensor modeling, access and communication, applicable to underwater sensing systems
TransducerML, SensorML
Cables The two most basic cable categories are flat and round.CABLE CONSTRUCTION. Copper conductors come in standard sizes according to the American Wire Gauge (AWG) system.SHIELDSOne problem that arises with long distances is a transmission line’s susceptibility to interfering signals.Electro-magnetic interference (EMI) is unavoidableand a long transmission line is very susceptible. Long wiresmake good antennasAmerican Wire Gauge (AWG)
Multiconductor or twisted pair configurations andeach with or without shieldingMulticonductor cables are available for basic single-ended, i.e., unbalanced applications. Twisted pair cables are available for differential, i.e., balanced applicationsImpedance, Velocity of Propagation, Attenuation, Rise Time DegradationCost/km, weight/km.
Inventory of standardsLanguages Standards defining languages
specific to sensor modeling, access and communication, applicable to underwater sensing systems
TransducerML, SensorML
Cables The two most basic cable categories are flat and round.CABLE CONSTRUCTION. Copper conductors come in standard sizes according to the American Wire Gauge (AWG) system.SHIELDSOne problem that arises with long distances is a transmission line’s susceptibility to interfering signals.Electro-magnetic interference (EMI) is unavoidableand a long transmission line is very susceptible. Long wiresmake good antennasAmerican Wire Gauge (AWG)
Multiconductor or twisted pair configurations andeach with or without shieldingMulticonductor cables are available for basic single-ended, i.e., unbalanced applications. Twisted pair cables are available for differential, i.e., balanced applicationsImpedance, Velocity of Propagation, Attenuation, Rise Time DegradationCost/km, weight/km.
Inventory of standards
• CommunicationWithin the same system: Communications between electronic circuits.
•Parallel Bus communications : Backplane•Serial Bus communications (same board)
Communication between different systems•Parallel Communication•Serial Communication
•Serial Multimedia Communications •Home Automation communications•Telephone Communications •Wireless Communications•Radio Frequency Communications. Free Band •Light Communications. IRDA•Acoustic communications•Optical fiber Communications
Inventory of standards1 Parallel Communication between
electronic circuits BackplaneLocal bus using backplane (printed circuit bus lines). Rack size 3U, each U: , 160 x (Eurocard). Connectors DIN 41612.
Microprocessors local busEurocard. VME (Versa Module Eurocard). IEEE 1014. Future Bus IEEE 896. PC104 Bus. VME Bus extensions for instrumentation (VXI). (PCI Extensions for Instrumentation)PXIISA Bus (Industry Standard Architecture). PCI Bus (Peripheral Component Interconnect). RapidIO Bus.AGP Bus (Accelerated )IDE (Integrated Drive Electronics). ATA Bus (Advanced Technology Attachment). ATAPI Bus (Advanced Technology Attachment Packet Interface)PPI Bus(Parallel Peripheral Interface)
2 Communications between electronic circuits. Serial Bus between electronic circuits
Communication between microprocessor peripheral using the minimum number of lines.
MicrowireSPI™ (Serial Peripheral Interface), QSPII2C™ (Inter Integrated Circuit Bus)SMBus (System Management Bus) and ACCESS.busSCI (Serial Communication Interface) UART (Universal Asynchronous Receiver Transmitter)
3 Communication between different systems: Parallel
IEEE1284 Centronics, Parallel Bus SPP ( ), EPP (Enhanced ), ECP (Extended ). SCSI Bus (Small Computer System Interface)LVDS (Low Voltage Differential Signalling) EIA/TIA 644
4 Communication between different systems: Serial
Class A and B LXI instruments use IEEE 1588 precision time protocol for accurate synchronization and timing.
TIA/EIA RS-232 Recommended Standard TIA/EIA RS-422BEIA RS-485. INTERBUS. MODBus 4-20 mA loop. HART Protocol (Highway Addressable Remote Transducer)PROFIBUSIEEE 1451.XV/F – F/VCAN (Controller Area Network). CANOpen (Controller Area Network Open). LIN (Local Interconnect Network)IEEE 488.2. Standard and the Standard Commands for Programmable Instruments(SCPI). LXI (LAN eXtensions for Instruments). IEEE 1588 standard forLAN-based precision timing.Power Line Modem (PLM) o Power Line Communication (PLC)
5 Serial Multimedia Communications
USB (Universal Serial Bus)Ethernet, Fast Ethernet, Token RingIEEE1394 Firewire
6 Optical fiber Communications FDDI (Fiber Distributed Data Interface)
Inventory of standards
Parallel Bus Physical Hierarchy
Inventory of standards
Serial Bus Communication between different systems: Wired
Inventory of standards
IEEE inside!
Inventory of standards
• Data management towards interoperability– Metadata (content)– Data Format– Catalog/Registry Service– Data Access– Streaming Protocols– Semantics– Portrayal and Display Service– Data Transformation Services– Quality/Assurance, Quality Control– Schema– Modeling, Simulation, or Analytic Processing Service – Archival – Communications and Telecommunications– Data Acquisition– Engineering Process– Development Environments and Software Languages– Technical Documentation
Inventory of standards
1 Metadata (content)
These standards describe the description of data. In data processing, metadata is definitional data that provides information about, or documentation of, other data managed within an application or environment. For example, metadata would document data about data elements or attributes, (name, size, data type, etc) and data about records or data structures (length, fields, columns, etc) and data about data (where it is located, how it is associated, ownership, etc.). Metadata may include descriptive information about the context, quality and condition, or characteristics of the data.
ISO 19115, FGDC , Dublin Core, IEEE 1451, TransducerML, SensorML*, ASTM D5714-95(2002)
• Data management towards interoperability
Inventory of standards
2 Data Format These standards describe the structure of distinct pieces of information, which are usually formatted in a special way. Data standards are organized to distinguish between binary machine-readable information as opposed to textual human-readable information. For example, some standards make distinction between data files (files that contain binary data) and text files (files that contain ASCII data). Graphics formats are used to store the appearance of an image or graphic. In contrast, scientific data formats are used to store numbers.
NetCDF, HDF, OGC Geography Markup Language, GeoTIFF, FITS, ASCII, HDF, CDF, GIF, JPEG, Bitmap, PostScript. Non-disk formats include TCP/IP, SEG-A, SEG-B, etc. They may also be in acoustic based files in formats such as WAV and MIDI. Others might be of gridded data (GDB, GRIB, ETOPO2, etc.). Hydrographic data might be in International Hydrographic Standards (IHO) S-44, IHO S-57, FACC, REEGIS, DIGEST, or TSSDS format. Some data might be compressed, such as RLE, Huffman, LZW, JPEG, ANSI N42.42, TransducerML , SensorML*, etc.
• Data management towards interoperability
Inventory of standards
• Data management towards interoperability
4 Data Access These standards describe the software and activities related to storing, retrieving, or acting on data housed in a database or other repository. Historically, different methods and languages were required for every repository, including each different database, file system, etc., and many of these repositories stored their content in different and incompatible formats. Recently, standardized languages, methods, and formats, have been created to serve as interfaces between the often proprietary, and always idiosyncratic, specific languages and methods. Some of these standards enable translation of data from unstructured (such as HTML or free-text files) to structured (such as XML or SQL).
OpenDAP , THREDDS, OGC WFS, OGC WCS, CORBA, SQL, ODBC, JDBC, ADO.NET, XML, XQuery, XPath, and Web Services.
Inventory of standards
• Data management towards interoperability5 Streaming
ProtocolsThese standards describe multimedia, and associated protocols, that are continuously received by, and normally displayed to, the end-user while it is being delivered by the provider. These standards describe the delivery method of the medium rather than to the medium itself. The distinction is usually applied to media that are distributed over telecommunications networks, as most other delivery systems are either inherently streaming (e.g. radio, television) or inherently non-streaming (e.g. books, video cassettes, audio CDs). Streaming video content over the Internet includes: NSV format, Windows Media, QuickTime video, RealAudio and RealVideo streams.
RSS, SWE, APP, IEEE 1451, TransducerML , SensorML*
Inventory of standards
• Data management towards interoperability
9 Quality/Assurance, Quality Control
These standards describe the quality evaluation, assurance, and control aspects in development and maintenance of critical software programs, software products, and calibration processes and products. These standards also describe the uniform, minimum acceptable requirements for preparation and content of Software Quality Assurance Plans (SQAPs). For noncritical software, or for software already developed, subsets of these requirements of these standards may be applied.
ISO 19113, 19114:2003, ISO 9000 series
Practical example
• Many standards were formulated by the industry to define some or all of the following sensor attributes:
- Metadata - Calibration methods - Definition - Identification - Means of interaction
Sensor System Example
Sensor 1Hydrophone
UW Scientific Package
Sensor 2Accelerometers
Sensor 3Compass
Sound Pressure
Particle Velocity
Magnetic field
Digital Numbers
3D Wave Bearing
3-axis System tilt information
Sensor System Example
Sensor 1Hydrophone
UW Scientific Package
Subsystem 2 Accelerometers
Sensor 3Compass
Sound pressure
Particle Velocity
Magnetic field
Acoustic pressure
Bearing 3D
3-axis System tilt information
Detector Boolean/Digital Numbers
Calibration Inversion
Processing
Sensors and ArraysCalibration CurveGives the mapping of input to output values for a steady state regime. Two curves are used to describe a Hysteretic behavior.
Random Error CurveGives the relative measurement error versus the input value itself or any other environmental quantity such as temperature.
Spectral Response CurveSpecifies dynamic characteristics of the detector in the frequency domain. It gives the sensitivity of the detector versus the frequency or wavelength of the input signal.
Impulse Response CurveSpecifies dynamic characteristics of the detector in the time domain. It represents the normalized output of the detector for an impulse (D function) input.
Spatial Response Curve(s)Gives the sensitivity of the detector relative to spatial coordinates (location of the source, or orientation of the incoming signal, e.g., point spread function, polarization)
Temporal Response CurveGives the sensitivity of the detector relative to a temporal coordinate frame (e.g., sampling time). This is a more descriptive form of the integration time.
© Alexandre Robin
Calibration
in
out
Random Error
%
q
Spectral Response
dB
Impulse Response
t
dB
Spatial Response
Temporal Response
t
dB
Integrationtime
Web enablement for this sensor
• SensorML, TransducerML (OGC web enablement, SOS, SPS, SAS)
• IEEE 1451 (TEDS + STIM + NCAP, smart sensors)
drawing recommendations
• Surveying ESONET data management systems• Surveying ESONET physical interfaces• Match needs and existing standards in a
pragmatic fashion and recommend
Relevant Portals
• ISWG Survey for GEO: www.dbscale.com/ISWGSurvey
• IEEE EO Standards Registry (seabass.ieee.org)• GEO Components and services registry portal
http://uddi.csiss.gmu.edu/geosspub/login.jsp• www.geoportal.org (ESA)• www.earthobservations.org (geo)
References of interest• [1] L. Bermudez, P. Bogden, E. Bridger, G. Creager, D. Forrest, and J. Graybeal, "Toward an Ocean Observing System of
Systems," in OCEANS 2006, 2006, pp. 1-4.• [2] A. D. Chave, B. St Arnaud, M. Abbott, J. R. Delaney, R. Johnson, E. Lazowska, A. R. Maffei, J. A. Orcutt, and L. Smarr, "A
management concept for ocean observatories based on Web services," in OCEANS '04. MTS/IEEE TECHNO-OCEAN '04, 2004, pp. 2187-2193 Vol.4.
• [3] D. Chayes, A. Maffei, and G. Myers, "SeaNet Lite: on demand Internet connectivity at sea," in OCEANS '97. MTS/IEEE Conference Proceedings, 1997, pp. 45-50 vol.1.
• [4] P. Cornillon, J. Caron, T. Burk, and D. Holloway, "Data access interoperability within IOOS," in OCEANS, 2005. Proceedings of MTS/IEEE, 2005, pp. 1790-1792 Vol. 2.
• [5] R. E. Duane, D. Daniel, and C. O. R. Thomas, "Ocean Observing System Instrument Network Infrastructure," in OCEANS 2006, 2006, pp. 1-4.
• [6] J. Graybeal, K. Gomes, M. McCann, B. Schlining, R. Schramm, and D. Wilkin, "MBARI's SSDS: operational, extensible data management for ocean observatories," in Scientific Use of Submarine Cables and Related Technologies, 2003. The 3rd International Workshop on, 2003, pp. 288-292.
• [7] J. B. Graybeal and K. J. Gomes, "Technical advances in comprehensive oceanographic data management," in Oceans 2005 - Europe, 2005, pp. 1357-1361 Vol. 2.
• [8] D. H. Rodgers, A. Maffei, P. M. Beauchamp, G. Massion, A. D. Chave, T. M. McGinnis, S. Gaudet, W. S. D. Wilcock, and H. Kirkham, "NEPTUNE regional observatory system design," in OCEANS, 2001. MTS/IEEE Conference and Exhibition, 2001, pp. 1356-1365 vol.3.
• [9] S. M. Smith, S. McPhail, A. Healey, and R. Russell, "LONTalk as a standard protocol for underwater sensor platforms," in OCEANS '97. MTS/IEEE Conference Proceedings, 1997, p. 267 vol.1.
• [10] F. Sonnichsen, A. Maffei, K. Asakawa, and X. Garcia, "Basic requirements and options for communication systems in scientific underwater cable networks," in OCEANS '04. MTS/IEEE TECHNO-OCEAN '04, 2004, pp. 2211-2218 Vol.4.
• [11] G. Waterworth, "Industrial solutions for regional cabled ocean observatories," in Oceans 2005 - Europe, 2005, pp. 1033-1037 Vol. 2.
Thank you!