Participants

@guochuyi @Xu Yang @Kevin Scaggs @Fei Zhang (Ericsson) @Andy Mayer @Joanne Liu Rudel @Zhulia Ayani

Agenda

Diagram of "How the model works":
1. Current diagram is not clear enough, need to change to two separated diagrams, one is original 3GPP conception, one is the mapping to ONAP components
2. Q: Is NSMF and NSSMF internally ONAP scope or not?
  Chuyi: If ONAP supports NSMF and NSSMF, and the 3rd party slice service subscribers use this ability, then it is ONAP scope, may leverage SO, SDNC or VFC to implement the function; if using vendor's NSMF and NSSMF, then out of ONAP scope.
Attribute SNSSAIId in Service Descriptor
1. This attribute is to attach the KPIs to the slice communication service that has the KPI monitoring requirement, each slice communication service has 1 unique SNSSAI and the KPIs will be measured and monitored for this service.
2. Add this attibute to SD may be inappropriate, where it should be depends on the answer of: is this a real Id, where does it come from, should this be given in run time? Take this as a homework to find out.
Q: In the E2E service, how can the KPI be decomposed and mapped to the Network Functions?
Chuyi: Not really need to map, NSMF will find all the NFs related to this slice service and measured the corresponding metrics.