...

1. Both options for RAN and Transport Slicing interaction shall be supported in Guilin release. RAN NSSMF within ONAP shall support Option 1, while external RAN NSSMF shall support Option 2. NSMF within ONAP shall support both options.
2. In a single ONAP deployment, only one of the 2 options shall be supported, and shall be known apriori. As a consequence, the NSTs also shall reflect only the option that is supported in the deployment. For example, if Option 1 is supported, NST shall comprise of RAN, Core and TN (BH) NSSTs, while when Option 2 is supported, NST shall comprise of RAN, Core, TN (FH), TN (MH) and TN (BH) NSSTs.
3. SO (NSMF) shall know which Option is supported by examining the NST (Option 1 => NST contains 3 NSSTs, Option 2 => NST contains 5 NSSTs). OOF shall operate based on the NST contents in a model-driven way.

7. KPI Monitoring

1. No trigger for KPI monitoring shall be sent from SO or other micro-services in DCAE. The KPIs to be computed by PM Handler MS shall be configured via Policy, and the NSI/NSSI for which the KPIs shall be computed shall be determined by accessing AAI before the computation.
2. It is assumed that the NFs already "know" which PM data should be reported to ONAP.

...