Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

LS to ONAP on 3GPP MnS integration with VES (S5-197831)

3GPP Working Group SA5 (responsible for development of Telecom Management specifications) would like to inform ONAP of an ongoing work item aimed, in part, at developing solutions by which 3GPP management services may be consumed by ONAP components. In particular we would like to inform ONAP of a proposed methodology that allows a 3GPP management service producer to integrate with the ONAP VES collector in a way that preserves as much as possible the independence of 3GPP-specified management services and the ONAP-specified VES.

  1. Actions:

To ONAP DCAE Project

ACTION:

3GPP SA5 kindly requests ONAP DCAE Project to take the above information into account and provide feedback on the approach.

LS on 3GPP – ONAP Cooperation & WoW (S5-196792)

3GPP TSG SA WG5 (SA5) fully supports the Integration of ONAP and the 3GPP 5G management framework and strongly believes that it is necessary to align solutions between 3GPP and ONAP to avoid industry fragmentation.

SA5 highlights the need for establishing contacts between the ONAP community and 3GPP SA5, and for informing each other when a change is required to ONAP or 3GPP specifications. Until a formal procedure for exchanging Liaison statements (LS) between 3GPP and ONAP is established, we ask that Magnus Buhrgard, as ONAP coordinator, kindly act as the focal point for coordinating the receipt and disposition of requests and information exchange between 3GPP SA5 and ONAP.

ACTION:  

  1. SA5 kindly requests establishment of an individual to act as a liaison coordinator between 3GPP and ONAP
  2. SA5 kindly requests ONAP to inform SA5 when a version of VES API specification is available.
  3. SA5 kindly requests ONAP to consider establishing a permanent reference to the ONAP VES API specifications.



  • No labels