...
Time slot 2) 07:30 - 08:00am PDT + BPs Title + PTL Name + the Link to the Rel "X" Documentation
Summary Table to Akraino TSC for BP (Integration Projects) Review status from August 2021
| Nr | Akraino BP Title | BP's PTL Name | Review Date | Release | Link to submitted BP's Documentation Templates | Documentation Sub-committee Recommendation to TSC (Approve/Not Approve) | Comments/Remarks |
|---|---|---|---|---|---|---|---|
| 1 | Public Cloud Edge Interface (PCEI) | Oleg Berzin | Aug. 8th, 2021 | Rel. 5 | https://wiki.akraino.org/display/AK/PCEI+Release+5+Documentation | Approve | Submitted Documents for Rel. 5 are well structured & written. |
| 2 | SmartNIC for IEC BP | Leo (acting as PTL due to the fact that the PTL Yihui stepped down) | Aug.13, 2021 | Rel. 5 | please see "Comments/Remarks" column | Approve | per mail notified that there is not any change in the documentation from Rel. 4 to Rel. 5. |
| 3 | 5G MEC/Slice System BP | Eagan Fu | Aug. 16, 2021 | Rel. 5 | please see "Comments/Remarks" column | Approve | per mail notified that there is not any change in the documentation from Rel. 4 to Rel. 5. Currently awaiting update/input on requirements from the Customer. |
| 4 | IEC Type 2 | Vinothini Raju | Aug. 17, 2021 | Rel. 5 | IEC Type 2 Release 5 Documentation | Approve | Submitted Documents for Rel. 5 are well structured & written. As both, the IEC Type 2 BP and PCEI BP, use Terraform, it might be worthwhile to explore the possibility for co-operation between the 2 BPs. |
| 5 | ICN (Integrated Cloud Native) | , | Aug. 20, 2021 | Rel. 5 | ICN Rel 5 Documentation | Approve | Submitted Documents for Rel. 5 are well structured & written. |
| 6 | ICN- MTSCN (Multi-Tenant Secure Cloud Native Platform) | Salvador Fuentes | Aug. 20, 2021 | Rel. 5 | ICN-MTSCN R5 Release Documentation | Approve | Submitted Documents for Rel. 5 are well structured & written. |
| 7 | EALTEdge (Enterprise Application on Lightweight 5G Telco Edge) BP | Khemendra Kumar | Aug. 27, 2021 | Rel. 5 | Enterprise Applications on Lightweight 5G Telco Edge Rel 5 Documentation | Approve | Submitted Documents for Rel. 5 are well structured & written. |
| 8 | Edge Lightweight and IoT Gateway (ELIOT GW) Blueprint | Khemendra Kumar | Aug., 27, 2021 | Rel. 5 | Approve | Submitted Documents for Rel. 5 are well structured & written. | |
1/8/2021 schedule
1/ 7:00 am – 7:30 am PDT Public Cloud Edge Interface (PCEI) Blueprint Family Oleg Berzin
...
All the EALTEdge Rel. 5 documents are well and thoroughly prepared. It is recommended to the TSC members to deem the EALTEdge Rel. 5 BP's Documentation for Rel. 5 as approved and accepted.
...
In addition to OPC UA Architecture specifications that that BP ELIOT GW & CPE follows, it was recommended to follow (get uppdated) on the 3GPP specified CIoT for 5G specifications due to major enhancements embedded in the 5GS Architecure for IoT related to RG with support for MA through 3IWG & N3IWG and ATSSS and several/many more (e.g UPF in chain/series connection and RRC Inactive with enhanced security and move of LMF to RAN. The OPC UA was initially released in 2006 - 2008 and has a very broad Market deployment footprint since then. OPC UA specificifies a Platform independent Service-oriented Architecture, that integrates all the functionality of the individual OPC Classic Specifications into one (1) extensible Framework. OPC UA specifications are stipulated in International Standard IEC 62541 62 541 (https://opcfoundation.org/news/opc-foundation-news/update-iec-62541-opc-ua-published/). The current version of the OPC UA specification is on 1.04 (22 November 2017). The new version of OPC UA now has added Publish/Subscribe in addition to the Client/Server communications infrastructure. The OPC UA Information Model is a so-called Full Mesh Network based on nodes. The OPC UA Architecure supports two (2) Protocols. This is visible to Application programmers only via changes to the URL. The binary protocol is opc.tcp://Server and http://Server is for Web Service. Otherwise OPC UA works completely transparent to the API. nodes. The OPC UA Architecure supports two (2) Protocols. This is visible to Application programmers only via changes to the URL. The binary protocol is opc.tcp://Server and http://Server is for Web Service. Otherwise OPC UA works completely transparent to the API.
For furthr information, please see attached below the OPC UA Open IEC 62 541 (current) Standard specification from Jan 2021.
View file name OPC UA IEC Open 62 541 Jan 2021.pdf height 250
All the ELIOT IoT GW BP Rel. 5 documents are well and thoroughly prepared. It is recommended to the TSC members to deem the ELIOT GW BP Rel. 5 BP's Documentation as approved and accepted.
10 Dec 2021 Federated ML Application at Edge Maturity Documentation Review/Meeting notes
Day/Month/Year Schedule Review
...