Page History

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

• Needs to focus on Industrial IoT use cases at the 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 x86 cpu, tpu, gpu, etc)
• comprehend the unique needs of the Industrial 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

...

Type of Devices-

            Devices that live at the Smart Device Edge are characterized by having a small footprint yet being powerful enough to being able to many compute tasks at the edge.  They tend to have a minimum of 256 MB for a single node and can grow to the size of a small cluster.  These resources could be a router, hub, server, or gateway that are accessible.  This is as opposed to On-Prem Data Center Edge, the Service Provider Edge or Central Data Centers, which are much more powerful and have some type of physical security around them (a locked door to the server room).  The family is agnostic to the type of silicon that runs these devices, since the devices come from a wide variety of manufacturers and do a wide array of different things (ARM and x86 CPUs, TPU, GPU, etc.)  

Comprehension of the Uniqueness of the IIoT-

            There are many unique concepts that make the IIoT world.  But these devices very widely in their age, OS, compute abilities, with an assortment of legacy VMs and apps which need to run alongside modern containers and apps.   Thus this family is very varied in the devices it covers.  The devices are created to prioritize for uptime and the safety of the equipment and people who run them, thus the compute resources were designed to lessen latency and prioritize safety critical applications.  They handle a wide range of OT protocols and have a mix of On-Prem and Cloud back end systems that they can send messages to.  Yet, the control messages back to the devices themselves, need to be handled on the compute resource itself. 

Use Case Details:

<add in the taxonomy image from the white paper>

...

Contributors: 

Tina Tsou