Introduction to Octave Design Patterns

Through implementing Octave for different use cases, we've captured some recurring patterns for efficient designs, that you may wish to use in your Octave implementations. These Octave Design Patterns are detailed in the following use-case topics:

• Simple Telemetry, Edge Action and Command from the Cloud use case
• Report multiple Resources in a single Event and Stream
• Synchronize & schedule Resource reporting with Store and Forward
• Report multiple Resources in a single Event and Stream
• Return updated device Cloud properties as Commands

👍

Abbreviations used in these sections:

CA: Cloud Action
EA: Edge Action
CS: Cloud Stream
S&F: Store and Forward
ST: Storage
VR: Virtual Resource

Recommended steps in designing your Octave solution

We recommend you to follow three main steps:

Define how you will interface your Asset with the Octave Edge device:

• GPIOs,
• Modbus,
• Universal Serial Parser (USP),
• Octave Resource Protocol (ORP), ...

Define your Edge side architecture and configuration based on:

• Periodicity of measure acquisitions
• Edge side processing logic and Edge side required states (Virtual Resources)
• Periodicity of data reporting to the Cloud (Define Observations, Store and Forward, Edge Actions output)

Define Cloud side integrations:

• Edge to Cloud Stream structure
• Cloud Actions, Connectors, and Tasks
• Calls from your cloud to Octave API