900026 SENSORS: Ocean Observing System Instrument Network Infrastructure : Behaviors_Services
This page last changed on Mar 14, 2007 by kgomes.
  • How do instruments appear as a resources on the network?
    • SIAM: Has to take initiative because of safety concerns.
      • instrument plugged in, then scanport (plug and work).
  • Classes of instruments
    • Dumb instrument all the way to plugging in a computer
  • Five services:
    • Streaming Interface (generate and listen)
      • Data and Metadata Acquisition
        • Instrument Identification is metadata (1451 idea of metadata)
        • Automatic sequencing of data
      • Event
    • Management Interface
      • State of Health
      • Reset Cycle (Power reset, logical reset, safe mode)
        • Generic commands "shutdown", instrument would then do what it needed to and reply "OK".
      • Statement of/Request for Capability
        • Power should have information model to capture peak, etc.
      • Statement of Capacity/Request for Allocation (power/bandwidth/storage)
      • Some form of time service (get time- both ways)
    • Control Interface (these have to come with identity of actor that sent it)
      • Is this identity allowed to do the request? (Needs a handle to a decision maker upon creation). Call identity provider for authentication. Policy decision service can be called also.
      • Perform/Execute
        • get/setChannel (Property, parameter, etc.)
        • updateChannel
      • Pub/sub
        • Channel subscribe
      • Perform Action (this is more than get/set, you can send whole XML) - asynch (get back key to monitor progress)
    • Life-cycle Services (logical device management)
    • Plug and Work Services (physical device management)
  • AMQP
    • Apache QID
  • JMS with broker
Document generated by Confluence on Feb 03, 2026 13:35