Uploaded image for project: 'ONAP Architecture Committee'
  1. ONAP Architecture Committee
  2. ONAPARC-582

Guilin-R7 Architecture Review - REQ-327 - AR-0009-R7-052020--R7 HARMONIZATION: ONAP/3GPP & O-RAN ALIGNMENT–STANDARDS DEFINED NOTIFICATIONS OVER VES

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Highest Highest
    • None
    • None

      Synopsis:

       

      Sponsors: Marge Hillis, Vimal Begwani, Oskar Malm, Damian Nowak**
       
       

      Description and/or Referenced Materials:

      • This proposal is part of the Harmonization Use Case to provide harmonization between 3GPP, ONAP and O-RAN. 3GPP sent liaison statement (S5-197831) to ONAP/DCAE proposing a solution for the delivery of 3GPP defined events to a VES collector :
        • 3GPP native notification format/schema remains as defined in 3GPP.
        • ONAP/VES Header added to the notification as defined by ONAP.
        • Goal to decouple the 3GPP payload from the overall event format defined by ONAP/VES and allow more independent evolution in 3GPP and ONAP.
      • This proposed resolution is agreed to by members of 3GPP, O-RAN and ONAP discussing the liaison proposal:
        • two modifications to the VES Common Header (new domain field enumeration value for standards defined notifications and new field that supports the routing of these notifications to the appropriate DMaaP topic).
        • 3GPP will define and publish the valid contents for the new routing-related field
      • 3GPP published an informative Annex B in 28.532 version 16.3. http://www.3gpp.org/ftp//Specs/archive/28_series/28.532/28532-g30.zip documenting this approach and defining the valid contents for the new field.
        • Next Steps:  ONAP publishes update to VES Event Listener document as described.
        • CR opened in 3GPP to propose making the changes in 28.532 Annex B Normative.

       

      • Proposed solution is generic: readily extensible to other standards bodies. The same approach can be followed, with no further VES Event Listener modifications, when integrating their events with the ONAP/DCAE platform.

      ArchCom Decision and Comments

      Uploaded file for Architecture presentation made on May 19 --Marge Hillis

      Conditional approval on 19-May-2020 for all 4 reviews pending discussion/agreement  on impact with DCAE PTL

      01-July-2020 update: Changed Status to Approve base on the supporting documents below:
      From: Nowak, Damian (Nokia - PL/Wroclaw) <damian.nowak@nokia.com>
      Sent: Wednesday, July 01, 2020 12:12 PM
      To: Chaker Al-Hakim <chaker.al.hakim@futurewei.com>
      Cc: VENKATESH KUMAR, VIJAY <vv770d@att.com>; Hillis, Marge (Nokia - US) <marge.hillis@nokia.com>; Horn, Linda (Nokia - US/Murray Hill) <linda.horn@nokia.com>
      Subject: REQ-327 / ORAN-ONAP-3GPP Harminization - agreement reached with PTL

      Hello Chaker,

      I am writing to You regarding the REQ-327: https://jira.onap.org/browse/REQ-327 ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES

      So the status up until today on this was “Approved conditionally – requires PTL approval”.
      I just wanted to let You know, that we discussed with Vijay today in DCAE weekly call, the final shape of that feature within DCAE – and I think, this agreement was reached.
      Vijay confirmed as well, that he`s good to proceed in the scope discussed.

      So this is just a notification, that we can move the status for this requirement to “Approved”, as we have resolved the condition stated.
      -------------------------------------------------
      Damian Nowak
      System Architect
      Phone: +48 727 500 167
      http://nok.it/onap

       

            ca2853 ca2853
            ca2853 ca2853
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: