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 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:

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.

Sub-Committee Chair: Ike Alisson elected 17 Nov 2020 for one year.

Meeting Details:

Akraino Edge Stack 1 is inviting you to a scheduled Zoom meeting.

Topic: Documentation and Release Planning
Time: Sep 25, 2020 07:00 AM Pacific Time (US and Canada)
Every week on Fri, until Sep 3, 2021, 50 occurrence(s)

Please download and import the following iCalendar (.ics) files to your calendar system.
Weekly: https://zoom.us/meeting/u5Esc-uhqDwqDEmrwbuc-hTf4Jwhm-b0VQ/ics?icsToken=98tyKu-trz8oE9KSsFyCd7UqW5nlb9_2k1Vrp7FKngrmTihnZFfcIepPf7AvJumB

Join Zoom Meeting
https://zoom.us/j/651429670?pwd=QW16NGJXTmdUNHVVK3FXbkxKV3ZnUT09

Meeting ID: 651 429 670
Passcode: 883460
One tap mobile
+16699006833,,651429670# US (San Jose)
+12532158782,,651429670# US (Tacoma)

Dial by your location
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 646 558 8656 US (New York)
+1 301 715 8592 US (Germantown)
+1 312 626 6799 US (Chicago)
855 880 1246 US Toll-free
877 369 0926 US Toll-free
+1 587 328 1099 Canada
+1 647 374 4685 Canada
+1 647 558 0588 Canada
+1 778 907 2071 Canada
+1 204 272 7920 Canada
+1 438 809 7799 Canada
855 703 8985 Canada Toll-free
Meeting ID: 651 429 670
Find your local number: https://zoom.us/u/abS2XFh8ku

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.

Interested parties sign up:

Name	Affiliation	Email	LF ID	Self-Nominate for Chair (Y/N)
Tina Tsou	Arm	tina.tsou@arm.com	Tina Tsou (Deactivated)

James Williams	AT&T	jw4099@att.com	jw4099
sujata tibrewala	Intel	sujata.tibrewala@intel.com	Sujata Tibrewala
Samir Chatterjee	Rebaca	Samir@rebaca.com
Pradnesh Dange	Rebaca	pradnesh.dange@rebaca.com
Arif Khan	Parser Labs	arif@parserlabs.com
Ike Alisson	ALICON Sweden	ike@alicon.se	Ike Alisson	Y

Agenda

4. Release 4 Documentation Review Ike Alisson

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

4/ 7:45 am – 8:00 am

Meeting notes:

Prepared documentatio is very thorough with detailed information onArchitecture, APIs, Security, Testing (including) fall back.The Blueprint team, Hencun and Lya yu, were very well prepared.

During the review, there had been made minor remarks related to:

Use of outdated Akraino Logo in the documentation to be removed or updated with the latest one.
The Blueprint APIs are compliant with the OpenAPI Initiative Rel 3.0 and it was recommended to state it exlicitly in the documentation.
The presented UCs are commercial and it was recommended to explicitly state that in the Documentation.
The Blueprint Architecture follows the IEC standard specifications and it was recommended to provide reference to the respective IEC Specification.

The Blueprint AI Edge: School/Eductation Video Security Monitoring presented documentation fulfills the Akraino Documentation Sub-committee requirements. Therein, the Sub-committee recommends to the Akraino Process committee to accept the Blueprint submitted Documentation to the Akraino Sub-committee on Friday, November 20th, 2020.

12/04 schedule

Regular session:

1/ 7:00 am – 7:15 am PDT- The AI Edge: Federated ML application at edge rolandwu

2/7:15 am – 7:30 am - Radio Edge Cloud Documentation Paul Carver

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:

To review the Radio Edge Cloud Documentation and get back to Paul Carver via mail as a result to Paul Carver's input that there had been not changes/updates.
To get back to AI Edge with information about the possibility to re-schedule preferably for Monday, Nov., 7th, and get back in written either today Friday or on the weekend.
To go through the documentaiton on Predictive Maintenance and get back to Vladimir Suvorov via mail.
The following remarks had been provided during the Documentation review of the BP on 5G Telco Edge (EALTEdge):

- to update the Akraino logo with the latest one without the term "Edge Stack" to avoid infringement rights violation

- to refer explicitly to the BPs through which 5G connectivity is provided and the BP Enterprise Application works as currently there is an indication on the respective BP Family. It is also recommended to provide a reference to an internal Road Map development when it is tentativel plannes (in the Road Map, e.g. Q2 2021 or Q3, 2021) to deliver the intergation so that recipeients know that there is a preliminary plan for the BPs connectivity to 5G as indicated in the BP and threin E2E functionality compliance.

- to verify with the Akraino API subcommittee about the BPs reference to ETSI MEC MEP internal references to be denoted/treated as APIs

- the above remark on the APIs and possible mismatch between "ETSI MEC MEP internal inerfaces (3 groups on defined as Mx (external), Mp (internal) and Mm (on Management) is related to explicit indication on any APis that are used whether being compliant to Open API initiative 3.0 (on Open APis.org).

Since the respective documentation review of 1 (one) BP took a whole hour and it was inidcated that previously, there had been provided time slots only for 2 BPs Documentaiton Review during a Documentation Sub.committee review, the previous procedure to ´have 2 (two) BPs documentation review per TSC session is reinforced.

12/11 schedule

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.

It is recommended to the Akraino Process committee and Akraino TSC to further proceed with the respective two (2) BPs submitted documentation for Akraino Rel. 4.

12/18 schedule

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.

As the Zoom session could not be started on time and it took about 20 min to re-schedule the Zoom meeting, it was decided per mail to convey the remarks of Documentation review per mail. The following is recommended:

On the Architecture document:

Related to UPF shunting at the MNO (CSPs) to check the already implemented in 3GPP System Architecture related Local Traffic Routing and Service Steering the functionalities related to multiple N6 UDP sessions and selection and re-selection of UPFs by the AF.
If possible, to elaborate why it is selected to refer to UPF deployed in the DC and not the other 3 alternative UPF deployments
With regard to MNO/CSP's Network (5G NSA/LTE and/or 5G SBA Network Architecture Configuration) selected functions invoked in the MEC host through partial and/or full intergration of MNO/CSPs Network CCF with ETSI MEC Host Service Registry
On the management part, to elaborate on the MEC Host support for Virtualized Infrastructure (and defined on MEC Host support for 3rd Party to provide its own Application and enable its Mangement from its own Management environment without and integration with the MEC Orchestrator.
If the aim/purpose of PCEI is to provide an "Enabler Layer" to briefly elaborate on the MNOs provided Capabilities through SEES/FMSS (in SCEF/NEF) to 3rd party ICPs/ISPs.
In order to provide a better understanding to the reader on the maturity/evolvement level of the PCEI Solution, to elaborate whether PCEI current Availability Configuration and or the Rel 4 proposed implementation is a "Demo", "Concept", "Commercial" deployment version and/or there is/are references.
The above remarks are also made with regard to the Test Document part related to APIs (test) indicated as "work in progress".
Related to Latency in the defined 3GPP UCs ( as eMBB, URLLC, mIoT, V2X as with inidcated standard values for Slicing) is defined and published. It might be useful to add it to provide credibility that PCEI is aware of the required Latency requirements and therein able to contribute to be achieved. The IIoT (industry 4.0) within URLLC (for MCC/MCS - Mission Critical Communication/Mission Critical Services) in terms of Motion Control Discrete Automtion (for Robotics and Packaging) as well as Process Automation - Motion Control (for fluids, Gases, Electricity) is also defined/specified (even the manufacturing areas that shall be covered in terms of 30mx30mx10m and 100mx100mx30m. There is also support for 3GPP and non 3GPP access (3IWG and N3IWG) with ATSSS in order to comply with the QoS requirements for Service "Availability" and Service "Reliability" in MNOs Network.

2. On the attached Data sheet, to check on page 2, whether it should be "PCEI in Akraino Rel 4" (as the indicated term is probably a typing mistake, if not to elaborate what the indicated term means)?

3. In the Test Document, there is very limited information about performed tests (except for the Bluval) and even in the part on the tests related to APIs there is not provided any information except the inidication that this is a work in progress. It is recommended to provide a reference to either a Time Plan and/or Road Map indicating when the Testing is scheduled for (e.g. Q1 or Q2, 2021).

On your comment and inquiry on my remark about "Maturity of the Solution", I am sorry if I had been ambigous and/or misleading with my remark.

I meant about the status of Deployment Availability in terms of
1. "Concept" or
2. "Demo" or
3. "Commercial Deployment".

I suggest that with regard to the variety of preferences in terms of having a "Concept" that can be further built-upon (please read "Customized") or a "Demo", that provides a working SW/Functionality (that is "stable") or a Commercial Deployment that can be taken as it is (with integration to BSS/peripheral internal Platforms) to be deployed fast in order to be shown as a reference on the Market.

Such denomination (anyone of the listed 3 above) on the status of the "Solution Deployment Availability", depending on the party the Solution is discussed with, can provide opportunities.

Again, I would like to convey from my side that it is a remark-suggestion, rather than a requrement.

On the "Demo" elaboration, I suggest to people to elaborate about it in the "Architecture" documents as it is read by the Technical people, that provide recommendations to the Commercial people.

On the UPF deployment, please note that UPF might be deployed at the DC, Aggregation Point, BTS and/or 5G CN (Core Network) site.

There are certain conditions for that.

In your PCEI case, you chose DC. If you get some questions on that from people who are aware and work with that (that aso know the conditions, differences, requirements), depending on your answer, recipients of your answer, may measure your insights into various aspects that this issue concerns/relates to.

Just FYI.

The digram below may provide you with an insight about the use of the terms CSPs and Telco (difference) with regard to the presented by 3GPP High-level model of roles.

The below chart assigns a particular meaning in the Case of (5G NSA/SBA) Slicing (SST/SSI) deployment (NSaaS).

P.S. According to GSA, there are till now about 330 Applications to deploy 5G Private Network (and the allocated frequency is still witihn the Band 42). D.S.

1/15/2021 schedule

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

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

Meeting Notes: The scheduled for today two (2) BPs Documentation reviews, namely IEC Type 5 and IEC Type 3, had been re-scheduled to a further date as the respective PTLs had kindly inidcated per mail that they would like to have some additional time to resolve some issues. The PTLs had been notifed in the reply that they can take their time, but hopefully, perform the Documentation review before Feb. 10th, 2021.

1/22/2021 schedule

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

Meeting notes:

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

All set of Documents for Rel 4 were reviewed. During review, there were shown reference to acceptance/approval from other Sub-committees as Upstream, Security, Bluval and APIs. There were elaborations about how the BP supports/implements (through OpenNESS) the 3GPP 5G and ETSI MEC Architecture specifications. The convyed remarks related to some indications and elaborations as e.g. explicit reference to support & implementing Open API 3.0, ETSI MEC MP1 & MP2 defined specifications, and related to 3GPP 5G Slicing to show some future planing on Slicing and, if possible, to show reference to which of the 3GPP 5G (4 -four) SST standardized UC value(s), the BP intends to support/implement in the future.

It is recommended to Akraino TSC to deem the BPs 5G MEC/Slice System to support Cloud Gaming documentation for Akraino Rel 4 as approved.

The attached below paper is just for information in case that it may contribute to the BPs with some information for further enhancement.

1/29/2021 schedule

1/ 07:00 am - 07:30 am PDT IEC type 5 SmartNIC Yihui Wang

Meeting notes:

The documentation is well prepared and detailed. The Architecture and HW and SW is well specified. The installation and verification are also well specified. There is elaboration on the differences between Rel 3 and Rel 4. In the Installation documentation there is also provided verification instructions. The performed tests are made on load throughput. The latency is left outside as it is dependant on UC Latency requirements. On the Test document, there shall be made some minor refinements to avoid misunderstandings from the text as it is presented the "tested and deployed Architecture" rather than ( as indicated in the text) "The Test Architecture".

Akraino TSC is recommended to accept and thereby, approve the BPs presented set of Documentation for Akraino Rel 4.

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

2/05/2021 schedule

1/ 07:00 am - 07:30 am PDT IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family hanyu ding

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

2/24/2021 Presentations on Amazon AI ML Platform (SageMaker) Algorithms, Models

The following presentations are listed below:

1. Amazon Innovate Opening Key notes

2. From PoC to Strategies for achieving ML at Scale

3. How do you innovate to drive Business outcomes

4. Use of AI ML to enhance the Customer Experience

5. Closing Keynotes

2/25/2021 Review/Meeting notes

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.

It is recommended to Akraino TSC to accept the "AI Edge I-VICS" Blueprint documentation and deem them as "approved/eligible" for Akraino Rel. 4.

05 May 2021 Video Security Monitoring Rel. 4 Documentation Review/Meeting notes, PTL Liya Yu.

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)

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. Rel 3 Final Documentation and Milestone Review

19 May 2020 Documentation Report: All the BPs besides the ones listed below are good to go:

ACRN: is listed in Release 3 planning but no activity or response

The AI Edge: School/Education Video Security Monitoring: yet to present the Documents

Public Cloud Edge Interface (PCEI) Blueprint Family: yet to present the Documents

Connected Vehicle Blueprint: Not a first release and Bluval integration is missing

IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family: Not a first release and Bluval integration is missing

All PTLs please update Release 3 Planning table based on your schedule. We would like to have all PTLs make a 15 mins presentation starting 03 Apr 2020 Based on our meeting today, the schedule for the next meeting is below:

04/03 schedule

1/ 7:00 am – 7:15 am PDT-

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

3/ 7:30 am- 7:45 am-

4/ 7:45 am – 8:00 am -

04/9 schedule

Agenda:

Scope of work of the Document review: API, Architecture, Installation, Release, and Test
Plan the review activity
Open Discussion
Project presentation: As of now we have REC

1/ 8:00 am – 8:15 am PDT-

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

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

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

Meeting Notes:

REC Review: Paul made his presentation. There are no major changes to the BP, so he does not expect much change in any of the documents besides the Release notes and Test Document because of the mandatory Bluval validation that this BP has to meet. Release notes they would update towards the end of May when the BPs are due. 19 May 2020 Done

Paul Carver would discuss with Tapio and Deepak regarding the Bluval testing and get back with what and how they will update in the Test Document. The Bluval tests have been run. The security tests produce a large number of results that need to be individually evaluated one by one. On cursory examination, many of them are not relevant.

04/17 schedule

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 -

3/ 7:30 am- 7:45 am -

4/ 7:45 am – 8:00 am -

Meeting Notes:

5G MEC Review: Feng presented the document he had from his private space. It is not in the Documentation Template. He is going to rework his document and present it again on May 8th. In the meantime, we agreed that he will put up the draft version so that we can take a look at the material.

MEP Review: Was not present, need rescheduling.

04/24 schedule

1/ 7:00 am – 7:15 am PDT - SDN Enabled Broadband Access (SEBA) for Telco Appliance Blueprint Family Trevor Tao (Deactivated) cristinapauna Song Zhu (Arm Technology China)

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

3/ 7:30 am- 7:45 am- Provider Access Edge (PAE) Blueprint Yolanda Robla Mota

4/ 7:45 am – 8:00 am -

Meeting Notes:

SEBA for Telco Appliance: The PTL changed, hence no one was present, need rescheduling.

KNI PAE: The R3 release components need to be incorporated in the architecture doc. If they have active users, they need to add end-user story under TSC>Application User Story page. They are using Openshift hence their Bluval tests are failing. Will provide the alternate validation framework that they using in the Test Document

05/01 schedule

1/ 7:00 am – 7:15 am PDT-

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

3/ 7:30 am- 7:45 am-

4/ 7:45 am – 8:00 am -

05/08 schedule

Adhoc session:

1/6:00 am - 6:15 am PDT - µMEC, Tapio Tallgren Ferenc Székely

1/6:15 am - 6:30 am PDT -

1/6:30 am - 6:45 am PDT - ELIOT IoT Gateway Blueprint khemendra kumar Abhijit Dasgupta

1/6:45 am - 7:00 am PDT -ELIOT SD-WAN/WAN Edge/uCPE Blueprint khemendra kumar Abhijit Dasgupta

Meeting Notes:

uMEC: Presentation was made and the following items need to be incorporated in the document:

Architecture Doc: Integration of the uMEC platform with 3GPP architecture to highlight the user plane mapping is missing. This would help people understand how this interoperates with the Operators network. A Use Case description of this platform is also missing
Installation Doc: Build mechanism needs to be elaborated. The bootup method needs to be elaborated highlighting the value for the method used for embedded devices
API Doc: Enhancing the support of Sensors using OpenAPI needs to be elaborated. Incorporate the example use case for generating Client and Server code.
Test Doc: Identity the layers of testing to be executed by Bluval

Eliot IoT Gateway: Accepted no comments

Eliot SD-WAN/WAN Edge: Accepted no comments

Regular session:

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

Meeting Notes:

AI Edge: Requested to reschedule. Will try to do an adhoc session, no more slots available

AI/ML and AR/VR: Dropped out of R3

5G Telco Edge: Architecture Doc: Integration with the Telco network for and how to manage from an Orchestrator of an Operator should be added. User plane integration point needs to be identified.

05/15 schedule

Adhoc session:

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

PCEI: Requested for rescheduling

Network Cloud: Accepted no Comments

5G MEC Gaming: Accepted. Will check if API Doc is valid for this BP

Regular session:

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@zenlayer.com Mark Shan

4/ 7:45 am – 8:00 am - IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family hanyu ding wales wang

Meeting Notes:

IECC Type4 AR/VR: BluVal validation is missing. Need to execute the relevant layer validation and include in the Test Document.

ICN: No Comments

Connected Vehicle: BluVal validation is missing. Need to execute the relevant layer validation and include in the Test Document

IEC Type 3: No Comments

05/27 Meeting notes

PCEI: Oleg made a presentation of his first release. It was all in order and we have no comments from the Doc team

06/01 Meeting Notes:

AI Edge Video Security Monitoring: Presented by the team, the following are the comments

Table of Content is missing from some of the documents. This needs to be added
Architecture Document:
1. Component Description does not include a description of all the components.
2. There is no description of the Application that would have to be deployed on top of the OTE. There need to be some details on the application used to validate the functions of the OTE; along with criteria of other possible applications that can be used
Installation Docuement:
1. There is a DB that is used to configure OTE. The DB Schema Script to configure OTE is provided, but there needs to be some description of what is being configured and the different tables referred to in the Schema. Without it, users outside the BP team will not be able to use it.
2. The OTE Web portal is a critical piece of the BP. It is used to bring up the framework, configure things, deploy an application and monitor whether the BP is working. However, this portal is in Chinese. Hence, someone who does not understand Chinese will not be able to use this BP

19/02 2021

Persentation to API TSC - subcommittee

Release 2 Final Documentation and Milestone Review

11/01 -

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/18- IEC Type 1, Type 1, & Type 1 - Trevor Tao Cristina Pauna, xinhuili, Wen-Ping Ying Wenhui Zhang Tina Tsou,

SEBA Julie Lorentzen , ICN, Kuralamudhan Ramakrishnan (Deactivated),

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,

07/18 7:00 am PDT Rel 2 Milestones and Planning

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

05/10 7:00 am PDT – Kubernetes-Native Infrastructure for Edge (KNI-Edge) Family, Frank Zdarsky, Eliot- Abhijit

05/17 7:00 am PDT – Edge Video Processing- adnan.saleem@radisys.com, IEC Type 1 for Integrated Edge Cloud (IEC) Blueprint Family- trevor.tao@arm.com

05/24 6:00 am PDT –

IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family- lxinhui@vmware.com,

Edge Video Processing- adnan.saleem@radisys.com,

IEC Type 1 for Integrated Edge Cloud (IEC) Blueprint Family- trevor.tao@arm.com

Eliot IoT Gateway- khemendra.kumar@huawei.com

Radio Access Cloud pcarver@att.com

19 Apr 2019 7:00 am PDT

Review Architecture Document, Test Document, Release Notes, Installation Guide which are sub-linked to this page.
Review Akraino Project Reporting

Meeting Content (minutes / recording / slides / other):

May 10th, 2019, Recording
May 3rd, 2019, Recording, Minutes
April 25, 2019, Recording
April 19, 2019, Recording
April 12, 2019, Recording
March 29, 2019, Minutes/ Recording
March 22, 2019, Minutes/ Recording/Chat
March 15, 2019, Minutes/Recording
March 08, 2019, Minutes
March 01, 2019, Minutes
Feb 22nd 2019, Minutes
Jan 24th, 2019, Minutes / Recording
Jan 17th, 2019 Minutes / Recording
Jan 11th, 2019, Minutes
November 12, 2018 minutes / recording / slides

Browser not supported