Skip to end of metadata
Go to start of metadata


As of R6, in order to build a stable release, Upstream will need each BP/Feature to specify upstream repositories completely and with corresponding version/branch information.


R6 Requirement:

  • If a BP has no code changes to upstream repositories, then it would just need to specify fully its upstream release versions in its release document, matching with its bluval testing versions.
  • If a BP has code changes to upstream repositories, then it would need to either merge the code into the upstream before the R6 release time frame and updates its release versions. If the code cant be merged the code into upstream timely, then the BP will not fit into the R6.
  • Or an upstream fork is acceptable by BP, then the BP should lock the fork before R6 release and the code should be merged back to upstream eventually.

Steps to update Upstream information by BP:

  • Add an entry in the following table
  • Fill in the Upstream document field, typically the release note
  • Add detail upstream information into release notes, including the name of the upstream/releases. For example, Ubuntu/20.04. Please list all major upstreams the BP used.


R6 Release Review Status (In Progress, all BPs please follow the schedule)



Project/BP NameUpstream Document links (Mostly in release note; Provided by BP)Review DateReview Status (Edited by Upstream Subcommittee only)Comments (any members)
Connected Vehicle Blueprint(Aka CVB)



IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family



Integrated Cloud Native NFV/App stack family (Short term: ICN)ICN R6 Release Notes and https://github.com/akraino-edge-stack/icn/blob/master/doc/software-bom.mdhttps://github.com/akraino-edge-stack/icn/blob/master/doc/software-bom.md5/10/2022Approved
Multi-Tenant Secure Cloud Native Platform 



ELIOT IoT Gateway BlueprintELIOT R6 - IoT Gateway Release Notes5/10/2022Approved
ELIOT SD-WAN/WAN Edge/uCPE Blueprint



Network Cloud and TF Integration Project



Provider Access Edge (PAE) Blueprint



Industrial Edge (IE) Blueprint



Micro-MEC



The AI Edge: School/Education Video Security Monitoring



The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System(I-VICS)



5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint



IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family

Release 6 Release Notes of IEC Type 3: Android cloud native applications on Arm servers in edge

5/10/2022Approved 5/12/2022
IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint Family



Enterprise Applications on Lightweight 5G Telco EdgeR6 - Release Notes of Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)5/16/2022Approved
Public Cloud Edge Interface (PCEI) Blueprint Family

https://wiki.akraino.org/x/Ui0wAw

4/21/22Approved
The AI Edge: Federated ML application at edge



KubeEdge Edge Service Blueprint



Private LTE/5G ICN Blueprint



Rural Edge blueprint for Tami COVID-19 Blueprint Family



Smart CitiesSmart Cities R6 Upstream4/27/2022Approved
MEC-based Stable Topology Prediction for Vehicular Networks



IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family



IIoT at the Smart Device Edge (family)



Federated Multi-Access Edge Cloud Platform



Smart Data Transaction for CPS

Smart Data Transaction for CPS Release Notes

(See Release Contents section)

4/22/22Approved
Robot basic architecture based on SSESRobot basic architecture based on SSES Release Notes - Akraino - Akraino Confluence4/21/22Approved















  • No labels