Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

-Add in a description of the family, what makes the species linked together

  • Needs to focus on the Industrial IoT use cases at the smart device edge (shop floor)Smart Device Edge (eg IoT edge compute deployed outside of the data center), not mobile devices/client
    • There can be other families that cover other smart device edge use cases- 
    • refer a lot to the white paper
    • 256 MB single node to a small server cluster 
    • gateway, router, hub, server
      • not just about gateways, 
  • This would be covered by the smart device edge under the User edge- Taxonomy Whitepaper page 3
  • is there a min hardware? maybe as small as a RPi, but really focused on true industrial machines
    • need some type compute functionality at the edge
  • agnostic to silicon (eg ARM and Intel chipx86 cpu, tpu, gpu, etc)
  • comprehend what are the unique needs of the Industrial smart device edge?IoT edge compute use cases
    • latency and safety critical applications 
    • priority for uptime and safety
    • prevention of sending control messages back to critical infrastructure from the cloud
    • comprehension of OT protocols 
    • a mix of on prem and cloud back end systems...
    • deployment of legacy VM and apps plus modern containers
  • add in a couple more UCs for this
  • add in alignment with Akraino blueprints
  • describe a baseline infrastructure
  • horizontal infrastructure- market-tecture need to scope this out; draw the picture
  • support to workload themes
    • computer vision, eg stream video
      • high bandwidth is needed
      • the killer app is to process this at the edge
    • machine intelligence, eg structured telemetry
      • many different protocols, 
      • varying amounts of data volume (eg vibration data vs temperature data)
  • enable workload consolidation


Need to update the text in the table to reflect the changes from the taxonomy

...