Proposed-BuildingBlocks

Landing page for all proposed building blocks; use the README to navigate through all the Building Blocks.

Implementation of new BBs

• New BB should be implemented using the BB_Template.
• If you create a folder without content, put a .gitkeep into the folder.
• Whitespaces in Folders: "-" (Dash)
• Whitespaces in Files: "_" (Underscore)

Abbreviations have to be added to the abbreviation list.

Folder Structure

When implementing a new BB one has to comply to the following folder structure:

└── 📁BB-SC  # primary tag
        └── readme.md  
        └── 📁AppLayer  # layer (AppLayer, MWLayer, OSLayer, HWLayer)
            └── readme.md  
            └── 📁Communication  # functional cluster name
                └── BB_AOSP_Push_Notification_Service.md  # BB - if it is in >1 FC or tag, put symlink there
                └── 📁BB_OTA_Manager  # folder if more than a .md file exists for BB
                    └── BB_AOSP_Push_Notification_Service.md # BB if it is in >1 FC or tag, put symlink there
                    └── BB_AOSP_Push_Notification_Service.xml 

BB Tags

First tag of BB defines its location in git repo

Tag	Description
BB-SC	Building Block Stack Component (In-Vehicle / On-Board)
BB-CSC	Building Block Cloud Stack Component (Cloud / Off-Board)
BB-MU	Building Block Mockup Unit (In-Vehicle / On-Board Component)
BB-CMU	Block Cloud Mockup Unit (Cloud / Off-Board Component)
BB-EST	Building Block Engineering & Support Tools (for In-Vehicle / On-Board Components)
BB-CEST	Building Block Cloud Engineering & Support Tools (for Cloud / Off-Board Components)
S-BB	Supporting Building Blocks (Standards, API & Interface Definitions, standardized Data Model)
FC	Functional Cluster – Logical group of technically similar BBs
BB-SC-TC	Building Block Stack Component ToolChain (contains compatible set of Engineering & Support Tools and Mockup Units for In-Vehicle dev)
BB-CSC-TC	Building Block Cloud Stack Component ToolChain ToolChain (contains compatible set of Engineering & Support Tools and Mockup Units for Cloud dev)
BB-WE	Whatever Tag / Whitecard

Navigation

Cloud

• BB-CSC

• BB-CEST

• Cross-Layer

  • _Not_Clustered
    • Car Simulator

• BB-CSC-TC

• BB-CMU

---

In-Vehicle

• BB-SC

• AppLayer

  • Communication
    • AOSP Push Notification Server

• MWLayer

  • Communication
    • Communication Service S2S
    • Constraint DDS embeddedRTPS
    • Gateway Mirroring
    • Network Management
    • SecOS
    • Smart Charging Communication
    • Standard Android VHAL
  • Configuration
    • Local Update Manager
    • OTA Master
  • Diagnostics
    • Policy Manager
  • Platform Health Management
    • Distributed Health Management
    • Watchdog
  • Power Management
    • Power Management Coordination
  • Runtime
    • State Management
    • Diagnostic Services Applications
  • Security
    • Crypto Service Manager
    • Internet Protocol Security
    • Intrusion Detection
    • Secure Onboard Communication
    • Security Event Manager
    • Security Transport Layer
  • Storage
    • Vehicle Data Collector
    • Vehicle Data Persistency
    • Vehicle Logging and Recording
  • Time
    • Time Service
  • Tools and Methods
    • Key Management System

• OSLayer

  • Time
    • Automotive Edge Runtime

• HWLayer

• BB-EST

  • Build and Implementation
  • Deployment
  • Design
  • Implementation
  • Lifecycle Management
  • Monitoring and Diagnostics
  • Requirements
    • DocAsCode
  • Testing

• BB-SC-TC

  • Testing
    • Shadowing
  • Virtualization
    • Digital Twin

• BB-MU

---

Other

• S-BB

• AppLayer

  • Standardization of Vehicle API
  • Standardized Architectural Patterns for Cross Platform Data Service Infrastructure
  • Standardized Description of Data from Related Domains
  • Standardized Procedure and Tooling for Combining Data from Different Domains
  • Standardized Procedure and Tooling for Modelling Data from Different Domains

• MWLayer

  • SOA

  • sSOA

  • Standardized Data Conversion Tools for Info-Knowledge Layers

  • Standardized Data Description for Vehicle Sensors, Attributes, and Actuators

  • Standardized way for Reasoning on Data Streams

• OSLayer

---

Use Cases and Scenarios

While building blocks are useful as a starting point for specific software component design and implementation considerations, it is always desireable to be able to put building blocks into a larger context, asking the question: what actual use cases and scenarios should a system be able to cover? Such use case scenarios are collected and maintained in a dedicated structure.