You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Note: This is a stretch goal for I-release.

High-level requirements

  1. ONAP NSMF shall support Option 1 and Option 2 in a model-driven manner.
  2. ONAP RAN NSSMF shall support Option 1 and Option 2 in a model-driven manner.
  3. In case of Option 2, NSMF shall communicate with TN NSSMF for FH and MH NSSI LCM calls. This shall be aligned with the calls done by RAN NSSMF to TN NSSMF for Option 1, to keep it uniform.
  4. For FH and MH, we take some assumptions for the short-term: for e.g., pre-provisioned endpoint info for RU, CU and DU. If feasible, endpoints should be a list, to enable multipoint to multipoint connectivity in future. Open point: how should we specify which RU(s) should be connected to which DU(s)?

Impacts

OOF


SO (NSMF)


SO (RAN NSSMF)


AAI

  • No labels