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

Compare with Current View Page History

« Previous Version 5 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 preception or nevigation workload. 

<use case 2>

<use case 3>

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>

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