You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Blueprint overview/Introduction

<Purpose- it should introduce what the blue print is about, industry, business use case, applications and where it sits on the edge infrastructure>

<It should be readable by a semi technical audience , e.g. product marketing, business account executives etc>


Use Case

User case 1: Smart road and autonomous driving scenario: KubeEdge facilitates smart road, deploy MEC sites along highway system. The smart road system is designed for the emerging autonomous driving industry. Those self-diving cars can leverage the smart road facility to process perception or navigation workload. 

Use case 2: KubeEdge can be helpful in logistics, especially useful in tracking product and equipment conditions in cold chain logistics. To maintain low temperature as well as control other conditions, cold chain cargo need to process inputs from sensors in it, and take actions in the real-time. KubeEdge enables cargo fleets on-board system to control and communicate the situation of cold-chain conditions.  

Use case 3: Smart building scenario, KubeEdge can be perfectly used in helping the smart building local data processing. Lately, IoT sensors have been used in commercial buildings, however due to the data security requirement, most of IoT data need to be processed on-perm. Handerds of data processing systems support different commercial tenants.  

Where on the Edge

Business Drivers


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>

Software Framework Architecture

APIs

APIs with reference to Architecture and Modules

High Level definition of APIs are stated here, assuming Full definition APIs are in the KubeEdge BP API Documents

Hardware and Software Management

Licensing

  • GNU/common license

  • No labels