...
- User resgister SDN M&C to ESR via ESR Portal
- ESR trigger third party controller registration event to SDN-C via DMaaP
- SDN-C sync pnf topology via access/edge SDN M&C.
- SDN-C decompose topo into corresponding A&AI node
- SDN-C save topo into A&AI
Plug And Play
Assumption: OLT/ONT/BNG related resource already modeled in SDC and distributed
1.OSS send the create service request to ONAP External API with Customer ID, OTO, PON Port, SN, service Package(string).
2.External API transfer the request to SO.
3.SO insert the information(Customer ID, OTO, PON Port, SN, service Package(string).) to A&AI and service status with inactive.
4.SO translate the CustomerId to Controller readable ID and send the request to SDN-C?
5.SDNC call SDN M&C /DHCP/ACS with specific DGs.
6.Customer receive the ONT and trigger the event to DCAE.
7.DCAE and Policy trigger SO(or directly) to update the service status into Active in A&AI.
8.So update Service status in A&AI.(To Be decide, SDN-C also could update A&AI directly?)
Nomadic ONT Service:
Nomadic ONT Service in ONAP:
1.Access SDN M&C report the roaming event to DCAE.
2.DCAE and Policy notify SO the event.
3.SO query the Service in A&AI with SN or Customer ID.
4.So send the delete old ONT service instances request to SDNC.
5.SDNC delete the business on Access SDN M&C and Edge SDN M&C.
6.After successfully delete the business, So send the service creation request to SDNC.
7.SDNC create the business on Edge/Access SDN M&C,DHCP,ACS with specific DGs.
8.After successfully creation, so update service instance inside A&AI.