Wed UTC: 12:00 / China 20:00  / Eastern: 07:00 (Happen every other week)

https://zoom.us/j/99340453185, passcode： 654833. Or click 

https://zoom.us/j/99340453185?pwd=UEhOcjVzT2tlMUNLSDFGd1NDRDEvQT09

Participants

Chuyi Guo Fernando Oliveira Andy Mayer Fernando Oliveira Byung-Woo Jun Fei Zhang Tony Finnerty

Agenda

  1. ETSI Network Service for 5G Network Slicing / ETSI Alignment
    ETSI Network Service for 5G Network Slicing   
  2. R8 E2E Network Slicing case modeling work 
    Modeling enhancements in Honolulu
    Modeling enhancements
  3. Other suggested topics
    1. Potential requirements toward I release, like, service/resource modeling and CPS model relationship regarding configuration part.... 

Minutes

  1. ETSI Network Service for 5G Network Slicing / ETSI Alignment
    1. H release‘s main work is data model definition for supporting CNF model, and progress goes well.
    2. Fred has a proposal of interaction between NSSMF and NFVO to support Network Slicing,  SO is working on the development of SOL 005,  there needs some analysis on SOL 005 to support Network Slicing and needs to discuss with E2E Network Slicing team.
    3. No agreement on separating CNFD from VNFD in ETSI now, ONAP I release will align with v 4.2.1 to do data model.
  2. R8 E2E Network Slicing case modeling work 
    1. ONAP NSST is for service level requirements/propertities, which includes network resource description(leveraging NSD to describe), and managed function description( can leverage VNFD, PNFD,etc. to describe). Fred will discuss with E2E Network Slicing team to see what has already been supported in Core Network Slicing, and seek the next step to combine NSD based model. 
  3. Potential requirements toward I release
    1. If you have any requirement, please go to  ONAP R9 Modeling High Level Requirements to propose, core NSST and NSD combination can be one of them.
    2. Service/Resource model and Topology model correlation->  ONAP can share the discovered topology, fisrt we need to have a good mechanism of topology forming and representation,  then explore how to associate with service layer or resource layer. Topology model now is looking at other SDOs' models as reference, what are the key conceptions to be presented, how to model endpoints, connectivity, how to map E2E connection down to components.
    3. Service/Resource model and CPS model correlation->  Can CPS handle the configuration files in onboarding CSARs? Currently not, CPS now is expected to be a data store and network data cache, and CPS supports YANG model. It can be model-driven in the future. 

Recordings

zoom_0.mp4

  • No labels