Blueprint Overview/Introduction
<introduce what the blue print is about, industry, business use case, applications and where it sits on the edge infrastructure>
Use Cases
Below are some sample use cases which could benefit from the approaches implemented in this blueprint.
Interactive Live Sports/Music
In a live event featuring audiences in multiple remote spaces, data can be combined by sharing between groups of edge nodes and sensors in each physical space. The combined data, such as video and audio feeds, can be integrated to provide a shared experience in a 3D virtual space to all audiences while reducing overall network bandwidth usage.
Agriculture/Infrastructure Monitoring
Widely separated sensor nodes can benefit from low-power radio connectivity to edge nodes, and edge nodes can react in real time to events in neighboring areas. The illustration below shows a storm drain monitoring application where, for example, sudden changes in water level can be used to trigger increased sampling rate in nearby sensors.
Where on the Edge
The blueprint is mainly focused on interactions between groups of smart edge nodes or gateways and sensors which can be grouped, either by physical location or by some other shared characteristics. The blueprint applies to situations where a large amount of data is generated from large numbers of sensor nodes, and which can benefit from localized integration and analysis of this data. Some such situations are described in the use cases above.
Business Drivers
Cyber-physical systems (CPS), which combine sensor networks with computing to monitor and control the physical environment are becoming more popular each day. The bandwidth of the sensor network depends on use cases. Large amounts of data from large numbers of sensor nodes will put pressure on the available network bandwidth between the edge and the cloud. Therefore, we need to have a means to optimize bandwidth utilization according to use cases. This blueprint propose a solution for network bandwidth optimization through data sharing at the edge, also enabling a more responsive and smarter total system.
Overall Architecture
<This could inform the non-technical audience, but now is more geared towards a more engaged, technical audience>
< Blue print's relation to Akraino generic architecture, how it relates to it >
< This section will use the Akraino architecture document as reference>
Platform Architecture
<Hardware components should be specified with model numbers, part numbers etc>
Software Platform Architecture
<Software components with version/release numbers >
<EDGE Interface>
<ETSI MEC Interaction>
APIs
APIs with reference to Architecture and Modules
High Level definition of APIs are stated here, assuming Full definition APIs are in the API documentation
Hardware and Software Management
Licensing
GNU/common license