The customer wants Telephony service ONAP Telephonymodel1 techno voip vnfvendor vendorA Telephonymodel2 techno voip vnfvendor vendorB Telephonymodel3 ID: 1042680
Download Presentation The PPT/PDF document "BSS to ONAP Resolver René ROBERT" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. BSS to ONAP Resolver René ROBERT
2. The customer wants Telephony serviceONAPTelephony_model_1: {techno : voipvnf_vendor : vendorA}Telephony_model_2 : {techno: voipvnf_vendor: vendorB}Telephony_model_3: {techno: pstn}ONAP can instantiate telephony service based on several possible modelsBSS« Telephony »: {QualityLevel : HighLocation : Britany}No automatic choice?it is not possible to plug a BSS to order a service with optionsIf quality = High select Telephony_model_2If Location = Bearn select Telephony_model_3The need (1/2)
3. ONAPvFirewall_model_1: {techno : VNF X vnf_vendor : vendorA}vFirewall_model_2 : {techno: VNF Yvnf_vendor: vendorB}vFirewall_model_3 : {techno: VNF X + VNF LoadBalancing Xvnf_vendor: vendorA + Vendor C}?The service instantiation requires a human decisionMultiple services models in ONAP for the same service typeNo automatic choiceI want to instantiate the simplest vFirewall but I am not sure which model to use ?I have onboarded multiple vFirewall service modelsIf simple then select vFirewall model 2The need (2/2)
4. There is a difference between the service perceived as a ‘know-how’ from the BSS and the service as a technical solution to be delivered to fulfil the customer request. This service distinction is already existing in standard :TMF/SID extract : “A CustomerFacingService defines the properties of a particular (…) know-how that represents a realization of a Product within an organization's infrastructure; This is in direct contrast to ResourceFacingServices, which support the network/infrastructure (…)technical solution. “ Our observation about NBI & SO : NBI manage RFS ordering and not able to identify from a generic CFS which RFS fulfil. SO manage RFS level service deliver orchestration
5. Our assumption is to work with ExtAPI project but have a distinct component from NBIThis component must be optional This component must leverage NBI (nothing prevent BSS to trigger serviceOrder directly to nbi as long as they described ONAP service-level action) and not competing with NBI or any other ONAP components. This new component features:Management of rules to define RFS to be fulfilled for a given CFS ordered (design time defined rule – catalog type data). All actions (add, change, delete) must be managed.Capability to receive serviceOrder (assumption at cfs level) and calculate RFS-level operation to be performedTrigger to NBI RFS-level service order – leveraging NBI capability to handle multi-item service order & order item relationshipProvide service order follow-up (for serviceOrder managed)Provide inventory information (for CFS type service but also to have the link with RFS-used) . This new component will be master of data for CFS inventory & and will use AAI for RFS inventory. These inventory information is not existing currently and could be leverage to introduce other feature in future (as east-west service level modification).Proposal : Introduce a new ExtAPI component to manage this CFS-RFS distinction.
6. BSS_CFS_resolver : component view
7. BSS_CFS_resolver : How to Design a CFS specification1 – define and onboard service models ( = rfs spec level) in ONAP SDC2 – identify all potentials rfs spec that can be part of the cfs spec you want to expose to BSS3 – for each rfs spec that can be part of the cfs spec model, identify the instantiationDecision rules4 – write the CFS specification in a JSON file5 – onboard the CFS Specification in BSS_CFS_resolver Apps using cfs_spec API (json file content = POST payload
8. BSS_CFS_resolver : instantiationDecisionRulesInstantiation decision based on a cfs characteristicInstantiation decision based on existing rfs instance in a set Instantiation decision based on service capacity of existing rfs instanceRules can be chainedOnly 3 rules identified todayA « set » can be : customer, all, slice, admin domain…
9. Based on ONAP vCPE use-case described here : https://wiki.onap.org/pages/viewpage.action?pageId=33068582BSS_CFS_resolver : DEMO« infra » services are instantiated when they do not exists yet« infra » services instances are shared between cfs instances
10. BSS_CFS_resolver : Model DistributioncfsOrderorderItemcfsSpecificationrfsSpecificationrfscfsis composed ofwill contain aIs based onIs based onis composed ofis composed ofrfsOrderorderItemwill contain ais composed ofServiceSpec (NBI)ONAPserviceOrder (NBI)BSS-CFS-ResolverInstantiationRulesIs a copyService(NBI)A generic model for all kind of services
11. BSS_CFS_Resolver : High level ServiceOrder sequence