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>

Zhuming Zhang Hechun Zhang

Use Case

Safety Of The Intended Functionality (SOTIF)  

SOTIF(ISO/PAS 21448) emphasizes to avoid unreasonable risks due to expected functional performance limitations.

The background of the birth of SOTIF is the development of intelligent driving

If classified according to the functional chain of intelligent driving: perception-decision-execution, the "functional performance limitation" is reflected in three aspects:

  • Sensor perception limitations lead to scene recognition errors (including missed recognition of driver misoperation)
  • Insufficient deep learning causes the decision algorithm to judge the scene incorrectly (including the wrong response to the driver's misoperation)
  • Actuator function limitations lead to deviation from the ideal target

  • For Area2 (known unsafe scenarios), the basic idea of SOTIF is to identify risk scenarios through safety analysis, and develop countermeasures against risk scenarios.
  • For Area3 (unknown unsafe scenarios), various scenarios that a car may encounter under various road conditions need to be identified (in theory) in the early stage of development

<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 API documentation

Hardware and Software Management

Licensing

  • GNU/common license

  • No labels