...
The PTL, Kural P. presented all the documents. There was indicated in the Documentation that it was an add on related to Local Broker that is the new BP part in the Rel. 5. It was recommended to add the ONAP EMCO API in YAML format to provide an opportunity for Automation and Intent-based Management. It was also recommended to provide reference to the input that the Community members had tried out the BP. There was made a remark to contemplate on the benefit from the the use of the term "edge" as it was explicitly indicated that the the BP objective is to be in close proximity to the source of Data through the deployment of Loal Broker and interact for defined set of Data to be sent to the Global Broker.
All the documents are well and thoroughly prepared. It is recommended to the TSC members to deem the ICN BP's Documentation for Rel. 5 as approved and accepted.
08/20/2021 7:30 - 8:00 BP ICN- Multi-Tenant Secure Cloud Native Platform, PTL Salvador Fuentes (Deactivated) Rel 5. Documentation Review. The link to ICN Rel. 5 Documentation is: ICN-MTSCN R5 Release
The PTL, Salvador F. presented all the documents. There was recommended, as in the case of ICN Rel. 5, to benefit from API's in YAML format. There is an explicit comparison and presentation on the benefits with the Kata Containers, that the PTL presented, that provides a good overview on the BP's focus and provided advantages at its essence.
All the ICN MTSCN Rel. 5 documents are well and thoroughly prepared. It is recommended to the TSC members to deem the ICN MTSCN BP's Documentation for Rel. 5 as approved and accepted.
08/27/29212021 07:00 - 07:30am PDT, EALTEdge BP Rel 5 Documentation review, PTL Khemendra Kumar, the link to BP's Rel 5 Documentation is: Release 5 Documentation - Enterprise Applications on Lightweight 5G Telco Edge
08/27/2021 07:30 - 08:00am PDT, ELIOT IOT Gateway BP Rel 5 Documentation review, PTL Khemendra Kumar, the link to ELIOT BP Rel 5 documentation is: ELIOT R5 IoT Gateway Blueprint Documentation
The PTL Khemendra K. presented all the documents. There were suggested to refine the Data sheet summary with the parts remaning from the template as well as related to formating text, that is not readable (& in case that it doesn not work to follow the PCEI BP solution by downloading as *.pdf doc. Related to the BP's use of Edge Gallery as a way to connect to the CN, there was provided information per mail to the PTL about the way ETSI MEC/MEP is intergated with 5G through 3GPP 5G defined CCF (CAPIF Core Function) in the MEP Service Registry.
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.
08/27/2021 07:30 - 08:00am PDT, ELIOT IOT Gateway BP Rel 5 Documentation review, PTL Khemendra Kumar, the link to ELIOT BP Rel 5 documentation is: ELIOT R5 IoT Gateway Blueprint Documentation
The PTL Khemendra K. presented all the documents. As in the case of EALTEdge Rel. 5 Data sheet summary document, there were suggested to refine the Data sheet summary with the parts remaning from the template as well as related to formating text, that is not readable (& in case that it doesn not work to follow the PCEI BP solution by downloading as *.pdf doc.
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 2008 and has a very broad Market deployment footprint. 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 (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.
Day/Month/Year Schedule Review
...