Image Added

The Documentation Sub-committee objective is to promote a consistent documentation structure and quality assurance across both the Akraino Project level and all individual Blueprint Families. It also serves the Akraino TSC requirements to follow the Akraino Procedures aiming Quanlity Quality assurance process and perform the required Documentation review.

About procedure to place a request for a Documentation review, please read/follow the instructions listed under Documentation Sub-committee Sub-catalogue titled "How to Request a Documentation review?

For further detailed information related to Documentation Sub-committee procedures and templates, you can look at the following sub-catalogues:

How to Request a Documentation Review?

Akraino Blueprint API Template

Akraino Blueprint Architecture Template

Akraino Blueprint Datasheet template

Akraino Blueprint Installation Guide Template

Akraino Blueprint Release Notes Template

Akraino Blueprint Test Template

Please join the Documentation Sub-Committee mail list by self-adding within the Akraino Mail List Sub-Groups page.

...

View file

name	Akraino_Doc_committe_june_2019.pptx
height	250
.pptx
height	250

Documentation sub-committee members(From Nov 2023~):

We have started the process to elect a new chair for the Documentation sub-committee. The process started on 23 Nov and will continue until Noon 15 Dec 2023 (Pacific)

The election process is two steps. The first is for people to self-nominate for the position. To do this, put a Y in the correct column if you wish to run for Chair. The second step is to have an election for the position. If there is only one person who has self nominated, then that person will be chair.

Note: Please ensure that both the name and email address for each member is listed on each sub-committee membership wiki page in order to properly set up CIVS voting when required.

Interested parties sign up:

Name	Affiliation	Email	LF ID	Self nominate as Chair (Y/N)	Self Nominate as Co-Chair (Y/N)

Documentation sub-committee members(From Nov 2020~Nov 2023):

Note: Election Nov 5 2020- Unfortunately Samir has notified the TSC that he will not be able to continue as Chair. Thus we are opening up the self-nomination process. Please put a Y in the Self-nomination column if you wish to be chair. If not, please put an N. This process will go until Noon on 12 Nov (Pacific time). If there is only one self nominee then that person will become chair. If there are two or more, we will have an election.

...

Friday 11/20/2020 Pacific

1/ 7:00 am – 7:15 am The AI Edge: School/Education Video Security Monitoring, Hechun Zhang

2/ 7:15 am – 7:30 am

...

3/ 7:30 am- 7:45 am- Predictive Maintenance (with a Thermal Imaging Camera, vibration sensors, etc.)

4/ 7:45 am – 8:00 am - Release 4 Documentation - Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)

Meeting Notes:

On Friday, 12/04, there had been a substantial failure in planing BPs review. There could be made review only of the BP on Lightweight 5G Telco Edge (EALTEdge). For ther other 3 (three) BPs, the following had been indicated briefly during the session:

...

1/ 7:00 am – 7:15 am PDT- Intergrated Cloud Native Kuralamudhan Ramakrishnan (Deactivated)

2/7:15 am – 7:30 am - Network Cloud with Tungsten Fabric Sukhdev Kapur

3/ 7:30 am- 7:45 am- IEC Type 4 AR/VR Bart Dong

4/ 7:45 am – 8:00 am - Connected Vehicle Blueprint(Aka CVB) Tao Wang

Meeting Notes:

There were conducted 2 reviews, namely BP IEC Type 4 AR/VR and BP Connected Vehicles (Aka CVB). Both BPs are in co-operation. CVB PTL, Tao Wang elaborated on the issue/status with the BPs APIs and that it had already been reviewed/discussed with the Akraino TSC API Sub-committee and agreed on it. No major issues in the documentation. There had been conveyed a remark on elaborating the status with the UC(s) so that the reader is aware where the BPs are used.

...

1/ 7:00 am – 7:30 am PDT

2/7:30 am – 8:00 am -

1/8/2021 schedule

1/ 7:00 am – 7:30 am PDT Public Cloud Edge Interface (PCEI) Blueprint Family Oleg Berzin

2/7:30am – 8:00 am -

Meeting notes:

The following remarks shall be treated as "recommendations" pursuing enhancements/improvements and in no way treated as "mandatory" to follow and/or implement.

...

1/ 07:00 am - 07:30 am PDT - 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint Zigeng Fu Feng Yang

2/ 07:30 am - 08:00 am PDT

...

Documentation review of Blueprint "The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System (I-VICS) is done over e-mail. Akraino Rel 4 Blueprint Documentation set at link: The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System(I-VICS).

All the required Blueprint's docs for Akraino Rel 4 are available and well prepared. There is provided reference to the utilized Blueprint's Open Source Platform SW (with link to the tool needed for Installation of SW as part of the Platform SW,namely, ROS2 - Robot Operating System 2) and support for 2 UCs namely, "Valet parking" and "SOTIF - Safety of the Intended Functionality". There is provided reference to HW list for a demo with Lexus RX 450h case. In the Installation Guide" document, the needed HW is specified. The Release document addresses mainly UC SOTIF. The Blueprint's APIs are based on FATE (Federated AI Technology Enabler), which is an Open-Source Project initiated by Webank’s AI Department to provide a Secure Computing Framework to support the Federated AI ecosystem.It seems that the current Blueprint HW and SW configueration is an outcome of Test/Trial/PoC (with Lexus RX 450h). The Blueprint had also added a document "Landing Applications", that provides a list of other Akraino Blueprints that can potentially run (as Application(s)) on the Blueprint (as a Platform). There is also a room for evolvement for the Blueprint to utilize the V2X UC specification(s) in ETSI MEC and 3GPP 5G for V2X SST.

...

Documentation review of Blueprint " Video Security Monitoring Release 4 Documentation" Rel. 4 is done over e-mail. All the required Blueprint's docs for Akraino Rel 4 are available and well prepared. The following remarks shall be considered as advisory and as a recommendation rather as mandaroty and subject to be used a ground for changein the BP's Documentation text:

In the API document. There is not an explicit reference to Open API Specification (OAS https://spec.openapis.org/oas/v3.1.0) and if the API structure follows it. In the Architecure Document, there is justa title "Open API. In case that BP follows OAS, it is recommended to explicitly state that in the BP's API Document. The API document is thorough. It is follows any Architecture Standard API structure, it is recommended to also explicitly refere to it.
In the Architecure Document, there is used the abbrerviation MEC. As "MEC" abbreviation is used by the ETSI MEC and respective Standard Solution Architecture, in case that the BluePrint follows the ETSI MEC Architecture Standard Specification, then it is recommended to use its complete denomination (ETSI MEC). If not, it is recommended not to use the abbreviation MEC, but its full name. The presented Architecture figures present the call flow based on Kubernetes (K3S Light and K8S). There is lack of indication of used interfaces and protocols. Therein, the respective presentation is just a "Diagram" rather than an "Architecure". It is recommended to indicate respective "Protocls" and "Interfaces" to indicate connections and/or dependencies. With regard to AI, there is harldy any information. It is recomended to add information about the utlized ML Algorithms, Type of Models and Models Training Approach, used Data Granularity and Charactristics for Training models, How the "test case data" is treated with regard to CNN RLU (to start with).
Installation Document is thorough and detailed. It is recommended to update with a Section related to ML (AI) Data handling/treatment and New Data gathering, Storage, Update and use for ML Model build-up and Algorithm(s) training.
Related to "Release" Document, it is recommended to provide the BP's Roadmap with respective Releases (Features, Functionalities, Dependancies, Security and Time Table) and with respect to that refer to what is new related to Akraino Rel. 4. It is impossible to understand how the Solution/Product/Platform is planned to be evolved.
On the Security Test Document, it is preferable for the Akraino TSC to receive the Akraino Security Sub-committee assessment analysis.

Attached below 5G General Performance Requirements for Video Production Applications & Airborne Base Stations for NPN (Non Public Network)

Image Added Image Added

Assessment summary and Recommendation to Akraino TSC: Overall assessment is that the BP's Documentation for Akraino Rel 4 is well prepared and thorough for each Part. There is a good overview on the overall Solution and related UCs. Therein, it is recommended to the Akraino TSC to deem the BP's Rel. 4 Documentation as accepted.

...

3/ 8:30 am- 8:45 am-

4/ 8:45 am – 9:00 am - Radio Edge Cloud (REC), Paul Carver

Meeting Notes:

...

1/ 7:00 am – 7:15 am PDT- 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint, Feng Yang

2/7:15 am – 7:30 am PDT -

...

1/ 7:00 am – 7:15 am PDT- The AI Edge: School/Education Video Security Monitoring, Hechun Zhang

2/7:15 am – 7:30 am -

3/ 7:30 am- 7:45 am- AI/ML and AR/VR applications at Edge Vikram Siwach

4/ 7:45 am – 8:00 am- Enterprise Applications on Lightweight 5G Telco Edge, khemendra kumar Abhijit Dasgupta

...

1/6:00 am - 6:15 am PDT - IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint Family, JiaXuan Tiejun Chen

1/6:15 am - 6:30 am PDT - Public Cloud Edge Interface (PCEI) Blueprint, cmti CA

1/6:30 am - 6:45 am PDT - Network Cloud and TF Integration Project, Sukhdev Kapur

1/6:45 am - 7:00 am PDT - 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint Feng Yang

Meeting Notes:

SmartNIC: Accepted no Comments

...

1/ 7:00 am – 7:15 am PDT- IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family thorking Mark Shan

2/7:15 am – 7:30 am - Intergrated Cloud Native Kuralamudhan Ramakrishnan (Deactivated)

3/ 7:30 am- 7:45 am- Connected Vehicle Blueprint(Aka CVB) thorking Jim Xu (Deactivated) Mark Shan

...

View file

name	Akraino TSC IkeA 5G System and SP New Services Data centric Approach 2021 02 19 Rev PA10_Akraino wiki.pdf
height	250

View file
name DMTF Redfish Specification Jan 2021.pdf
height 250

View file
name DMTF Redfish Scalable Platforms Management API Specification Aug 2018.pdf
height 250

Release 2 Final Documentation and Milestone Review

...

1/ 7:00 am – 7:15 am PDT- Micro-MEC, Tapio Tallgren, (absent, rescheduled to 11/22)

2/7:15 am – 7:30 am PDT - Connected Vehicle Blueprint, xin qiu (not complete, rescheduled to 11/08)

3/ 7:30 am- 7:45 am- Radio Edge Cloud (REC), Paul Carver (absent, rescheduled to 11/22)

4/ 7:45 am – 8:00 am - Network Cloud and TF Integration Project, @Sukhdev Kapur ( great start, some requirements are not met, follow up on 11/08)

...

New Final Review Schedule as on 11/01
11/08- IEC Type 1 - Trevor Tao Cristina Pauna, Type 2-Cristina Pauna, xinhuili, IEC Type 4, Wen-Ping Ying Wenhui Zhang Tina Tsou, ELIOT AIOT, jereliu@tencent.com, Network Cloud and TF Integration Project, Connected Vehicle Blueprint, xin qiu,

11/15- SEBA Aaron Byrd, ICN, Kuralamudhan Ramakrishnan,

11/20- Radio Edge Cloud (REC), Paul Carver

11/22- Network Cloud Rover - David Plunkett , Network Cloud Unicycle with SR-IOV- David Plunkett, Network Cloud Unicycle with OVS-DPDK, ELIOT IOT & SDWAN, khemendra kumar,

11/29- KNI provider Access Edge, Yolanda Robla Mota, , AI ML, AR/VR application at the edge, Vikram Siwach, Radio Edge Cloud (REC), Paul Carver, IEC Type 4, Wen-Ping Ying Wenhui Zhang Tina Tsou, ELIOT AIOT, jereliu@tencent.com,

10/04 - Radio Edge Cloud (REC), Paul Carver, ICN, Kuralamudhan Ramakrishnan (Deactivated), Network Cloud Unicycle with SR-IOVDavid Plunkett

Network Cloud and TF Integration Project, Sukhdev Kapur

10/11- Micro-MEC, Tapio Tallgren, SEBA Julie Lorentzen

...

10/25-AI/ML, AR/VR application at the edge, Vikram Siwach, ELIOT AIOT, IOT, SDWAN, Guoxu (Jeremy) Liu, khemendra kumar, Network Cloud and TF Integration Project, Sukhdev Kapur, KNI provider Access Edge, Yolanda Robla Mota, Connected Vehicle Blueprint, xin qiu , Network Cloud Rover, David Plunkett Starling X Bill Zvonar, IEC Type 2 Pauna, xinhuili,

...

Documentation Readiness Discussion for Rel 1

04/26 7:00 am PDT – Unicycle for NEC & Rover Blueprint Proposal for Addition to Network Cloud Blueprint Family -david.plunkett@att.com

05/03 7:00 am PDT- OVS-DPDK Unicycle Dell Blueprint Proposal- Rakesh Bohra <rakesh.bohra@ericsson.com>,

StarlingX Far Edge Distributed Cloud - Bill Zvonar,

Eliot- Abhijit