Versions Compared

Key

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

Date:  

A short 30 minute meeting due to the conflict with DCAE impact review discussion.

Participants

Ahila P  (Wipro) 
Alessandro Alessandro Gerardo D'Alessandro 
Borislav Glozman 
Dong Wang  (China Telecom)
Fei Zhang 
Gautam Kumar 
Henry Yu 
Kevin Tang  (STL)
Maciej Lisowski Malewski (Samsung) 
Malarvizhi P Paramasivam  (Wipro)
rajiv.v@hcl.com Rajiv Vishwkarma (HCL)

Agenda

  1. J release updates
  2. ACTN Simulator Topology design support for front haul and mid haul 
  3. Bug Fix in ExtAPI project - CNFs instantiation issue in Core NSSMF
  4. Action items from previous meeting
  5. TBDMT Templates Preloading Demo (If time permits)
  6. ??

Notes and Actions

  1. J release updates (Ahila)
    • Architecture subcommittee and DCAE impact review scheduled for today.
    • Design for some requirements are completed and some are work in progress.
    • Implementation for some requirements and backlogged tests continues.
    • Discussion:
      1. (Henry/Ahila) Enhancement to the existing DCAE code would be a preferred option as opposed to adding new MS's. Code change can be added to the slice analysis MS to support IBN based slicing and close loop control. A new API can also be added to analyze data from TN slicing.
      2. (Henry/Ahila) Policy needs to have a code handler to process the notification from slice analysis MS. Conversation with policy team needed. There is a call from policy to SO and then goes to SDNR, conversation with SO and SDNR are also needed.
      3. (Rajiv/Ahila) HCL at India is working on external NSSMF (option 2), have done some functionalities in core NSSMF and have implemented ONAP defined APIs in the NSSMF adaptor. They are looking into the integration with ONAP. Ahila to share technical supporting documents offline and have offline discussion with Rajiv on SDNC impact on external NSSMF and how to make use of AI/ML functions in ONAP.
  2. ACTN Simulator Topology design support for front haul and mid haul (Henry)
    • One topology containing two domains to support FH, MH, BH slices, which has been tested by Deepika, does not reflect the real deployment. To support the disjoint TN, more testing and even more design are needed in TN slicing. SDNC testing or even code change may also be involved. Currently this work is in J release planning but only BH part is ongoing. Henry and team to do a feasibility study for J release in two weeks.
  3. Bug Fix in ExtAPI project - CNFs instantiation issue in Core NSSMF (Alessandro)
    • Alessandro to provide update in next weekly meeting.
  4. Action items from previous meeting
    1. Update on design details for External RAN NSSMF - activate and deactivate scenarios (Yogendra)
      • Yogendra to provide an update in next meeting
    2. TN changes based on latest IETF spec (Henry)
      • Code change likely to be minimal to support latest IETF spec with a couple of possible new parameters in SO code, no code change is likely on NSSMF side.

Recording

    1. RU yang model for RU applicability in slicing use case (Kevin)
      • No O-RU yang models has been specifically designed to support network slicing as of now in O-RAN. There seem to be no Work plan on this subject either. Current RU yang models, e.g., performance management yang models, are not specifically designed for network slicing.
      • Some relevant work in O-RAN includes WG5 work items on Slice SLA Assurance Use Case and Slice Subnet Management use case, which will cover CU and DU IM/DM aspects related to Slice Subnet Management such as NSSI provisioning and management, and Shared O-RU use case work item by both WG4 and WG5, which will cover additional O-DU operational and data model for O1/m-plane and O-DU. All above work items are targeted for completion by March 2022, we would have a clearer vision by then.
  1. TBDMT Templates Preloading Demo (If time permits) (Ahila)
    • Deferred to next meeting

Recording

We apologize for not being We are sorry that we were not able to record this meeting due to the zoom host code issue.