Versions Compared

Old Version 2

changes.mady.by.user Ike Alisson

Saved on

compared with

New Version 3

changes.mady.by.user Ike Alisson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

4. Release 4 Documentation Review Ike Alisson

Friday 11/20/2020 Pacific

...

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:

...

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.

3. Rel 3 Final Documentation and Milestone Review


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

  1. Scope of work of the Document review: API, Architecture, Installation, Release, and Test
  2. Plan the review activity
  3. Open  Discussion
  4. 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.  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:

  1. 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
  2. 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
  3. API Doc: Enhancing the support of Sensors using OpenAPI needs to be elaborated. Incorporate the example use case for generating Client and Server code.
  4. 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 (Deactivated) 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

  1. Table of Content is missing from some of the documents. This needs to be added
  2. 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
  3. 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