1/8/2021 schedule
1/ 7:00 am – 7:30 am PDT Public Cloud Edge Interface (PCEI) Blueprint Family Oleg Berzin
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:
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:
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 Maturity Documentation Review/Meeting notes, PTL Liya Yu.
Maturity Documentation review of Blueprint " Video Security Monitoring" 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:
Attached below 5G General Performance Requirements for Video Production Applications & Airborne Base Stations for NPN (Non Public Network)
Attack types related to Securing AI and related to it Mitigation Strategies are classified into two (2) main Categories, i.e. Training Attacks which occur during Development Stage and Inference Attacks which occur during Deployment Stage. Training Attacks include Poisoning Attacks and Backdoor Attacks while Inference Attacks include Evasion Attacks and Reverse Engineering Attacks. Model Stealing Attacks and Data Extraction Attacks are two (2) subtypes of Reverse Engineering Attacks. Some State-of-the-Art Adversarial ML papers & reports provide more details of existing attacks against Deep Learning (DL) Systems.
Assessment summary and Recommendation to Akraino TSC: Overall assessment is that the BP's Documentation for Akraino Maturity Review 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 Maturity Review Documentation as accepted.
Day/Month/Year Schedule Review
Time slot 1) 07:00 - 07:30am PDT + BPs Title + PTL Name
Time slot 2) 07:30 - 08:00am PDT + BPs Title + PTL Name