ONAP R7 Resource IM Call 2020-7-13

• Date and Time: 2020, July 13th, 9pm~10pm Beijing Time, 9am~10am US Eastern

• Meeting Room: https://zoom.us/j/97595070639

• Meeting Recording: zoom_0.mp4

• Meeting Chat Log: meeting_saved_chat.txt

Agenda:

• Agenda bashing - 5 minutes

• Model Proposals
  
  

  • allotted resource - 0 minutes

  • ETSI alignment - 10 minutes

  • 5G RAN service - 0 minutes

  • CNF - 0 minutes

  • Geolocation - 10 minutes

  • PNF instance model - 0 minutes

  • CPS model driven PoC - 0 minutes

• Modeling Documentation & Glossary - 5 minutes

• Modeling Process discussion - 0 minutes

• Model proposals:

  • Allotted Resource Revised

    • comments: Allotted Resource Model Review Comments

  • Support for CPS Model Driven PoC R8+

• Modeling process:

  • Proposed ONAP Release Process Updates for Information and Data Modeling

• Modeling requirements:

  • ONAP R7 Modeling High Level Requirements

• Related information:

  • Allotted Resource for Network Slicing

  • 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt

• Agenda bashing

  • vacation plan:

    • Jacqueline: July 6th~19th

• Model Proposals
  
  

  • ETSI alignment

    • analysis has been done to identify the specific changes need to do in R7 ONAP-ETSI-2.7.1-07-13-update.pptx

    • including VipCpd(new), SwImageDesc(changes), and additional minor changes

    • next step: making changes to UML diagrams, invite Offir to join the call and give suggestions to how to implement the data model changes

  • Geolocation

    • input from use case team: Generic Information Element Definition for Geolocation Model

    • will go back to the use case team with the updated information

  • 5G Service model

    • Ben will create a dedicate call for discussing this use case, invite modeling people to join

    • intent is to adopt 3GPP NRM

    • related to Network Slicing use case as well

    • the main difficulty is to identify the necessary information among tons of objects in the NRM

• Modeling Documentation
  
  

  • R6 readthedocs review

    • AP1: exchange Mult. - Type and Description - Stereotypes columns for the associations (Xu)

      • done, updated on ONAP Information Model - Gendoc Examples

    • AP2: simplify the sterotypes for the associations (Jacqueline and Xu)

  • add relationship documentation to the UML guideline: ONAPMODEL-28: Using the Documentation Property for RelationshipsOpen

    • UML principle wiki page:

      • under ONAP Modeling Design Principles and Guidelines

      • AP: Michela & Xu will check the current wiki pages whether they cover requirements for classes, relationships for Papyrus