Name of Use Case:
BBS (Broadband Service)
Use Case Authors:
Swisscom, Huawei, Nokia
more participants are welcome
Presentation Materials:
Description:
The use case proposes using ONAP for the design, provisioning, lifecycle management and assurance of broadband services. It covers new scenarios, such as nomadic ONT (Optical Network Terminal) and subscription plan changes. It leverages on BBF (Broadband Forum) specifications.
Users and Benefits:
To be added
Use Case Flows:
User Story
The Service Provider provisions Broadband Internet Access Service for end customers through ONAP. One day, a customer moves the ONT to a new location without notifying the service provider and thus needs to re-register ONT (PNF) in a new location and have all his services been re-provisioned/reconfigured. After moving to the new location, the customer needs higher bandwidth Broadband Internet Access Service and thus makes such order to his service provider. To this effect, the service provider needs to provision/upgrade the already existing broadband service.
Short description
This use case shows the extensibility of the ONAP platform in supporting the orchestration of Services in many different technology Domains. We believe that this use case will cover several different ONAP components and may also introduce some new platform capabilities:
Nomadic ONT devices
- PNF (Re-)Registration
- Service reconfiguration / service continuity
Subscription plan change
- Change Management
- External API
Data Collection, Analytics and Close-Loop
- Including custom Data collectors and Analytics Microservices
Business Service Flow
Service Provisioning(Include PnP)
- Service Provider sell a broadband service and post ONT to customer
Nomadic ONT Service:
1.ONAP provisions Broadband Internet Access Service
2.Customer moves to a new location without notifying the service provider
3.ONAP re-registers ONT (PNF) in a new location and re-provisions/reconfigures customer service
ONAP Components Cooperation in detail sub-usecase
Topology Discovery in ONAP
- User registers SDN M&C to ESR via ESR Portal
- ESR triggers third party controller registration event to SDN-C via DMaaP
- SDN-C syncs PNF topology via access/edge SDN M&C.
- SDN-C decomposes topo into corresponding A&AI node
- SDN-C saves topo into A&AI
Plug and Play in ONAP
Assumption: OLT/ONT/BNG related resource already modeled in SDC and distributed
1.OSS sends the create_service request to ONAP External API with Customer ID, OTO, PON Port, SN, service Package(string).
2.External API transfers the request to SO.
3.SO inserts the information(Customer ID, OTO, PON Port, SN, service Package(string)) to A&AI and sets the service status to inactive.
4.SO translates the CustomerId to Controller readable ID and sends the request to SDN-C?
5.SDNC calls SDN M&C /DHCP/ACS with specific DGs.
6.Customer receives the ONT and triggers the event to DCAE.
7.DCAE and Policy trigger SO(or directly) to update the service status into Active in A&AI.
8.SoO updates Service status in A&AI (To Be decided, SDN-C also could update A&AI directly?)
Nomadic ONT Service in ONAP:
1.Access SDN M&C reports the roaming event to DCAE.
2.DCAE and Policy notifies SO with an event.
3.SO queries the Service in A&AI with SN or Customer ID.
4.SO sends the delete old ONT service instances request to SDNC.
5.SDNC deletes the business on Access SDN M&C and Edge SDN M&C.
6.After successfully deletes the business, SO sends the service creation request to SDNC.
7.SDNC creates the business on Edge/Access SDN M&C,DHCP,ACS with specific DGs.
8.After successful creation, SO updates service instance inside A&AI.