...
- Show how it works for a particular use cases. the vCPE use cases is a good approach.
- Cover the following:
- Model representation (Cover E2E service, NS, xNF):
- Onboard and defined model
- Dynamic model in AAI
- Onboarding
- Distribution from SDC to the rest
- Service instantiation
- Model representation (Cover E2E service, NS, xNF):
2 Option A:
...
Implicit NSD representation
2.1 Assumptions:
- Management of the application-specific functionality of a VNF is envisioned as being outside of the scope of ETSI NFVO and VNFM functionality. ETSI NFV is currently silent about how such application level management is to be performed for a given VNF, but the assumption seems to be that it will be performed by OSS/BSS (e.g., SM/NM) or EM. This can be seen by the lack of specification of the EM to VNF interactions in Fig 5-1 below, as well as in the delegation of application configuration to the EM in the highlighted portions of the figure labeled B.3.2.2 below. (Figures taken from ETSI GS NFV-MAN 001 V1.1.1, 2014-12).
- Alternative Text: ETSI NFV is currently silent about how application level data is managed for a given VNF, but provides elements in the VNF descriptor which are intended to hold this application level data. The ETSI SOL003 Or-Vnfm interface between the NFVO and the VNFM provides mechanisms to pass this data to the VNF but alternative mechanisms such as direct communication from the OSS/BSS (e.g., SM/NM) or EM. The common alternative of using the vendor's EM is highlighted in the the figure labeled B.3.2.2 below. (Figures taken from ETSI GS NFV-MAN 001 V1.1.1, 2014-12).
...
(Should this be removed??)
3 Option B:
...
Explict NSD representation
3.1 Assumptions
Can refer to above is necessary
...