1. Orange Contribution to ONAP project Northbound API October update
Ludovic Robert / Hervé Poupon
Orange
October 16th, 1017

2. Orange contribution to ONAP Project
Objectives of the work:
Through a first API (or small set of APIs ) and simple use case implementation quickly learn lessons about the functional and technical gaps to integrate ONAP to a BSS for fulfilment with minimal customization on BSS
Get a first assessment of ONAP/MSO API native capabilities vs TMF API
Assumptions:
TMF Open APIs will be leveraging to articulate the interface between BSS and ONAP (Legato LSO)
The initial software architecture will not be optimized and will consist of “façades” on top of existing ONAP APIs, but the implementation will also bring lessons to help refine the best target software architecture
Benefit from support of other teams to perform configurations of ONAP modules which are pre-requisites to Service Orchestrator requests (ie design-time catalogue configuration in SDC)
Target date:
End of this year

3. Orange contribution to ONAP Project – Drop 1 Northbound TMF API
When ? before end of ‘17 PO
Product order mngt component
API scope:
BSS triggers a POST serviceOrder to an API Layer on top of ONAP.
This layer stores serviceOrder and triggers MSO workflow request to MSO API Request Handler
API Layer is responsible for serviceOrder status update (retrieving information from ONAP)
ONAP AdaptationLayer use PATCH operation to update serviceOrder with delivery milestone
Provide FIND/GET ServiceOrder to BSS
Optional features (not in first drop)
ServiceOrder delivery notification (triggered from API Layer)
Contribution
Scope
Request
POST serviceOrder
Response POST serviceOrder
(id)
Response GET serviceOrder
(order detail)
Request
GET serviceOrder/id
Service order mngt component SO
Request
PATCH serviceOrder
Request
deliveryRequest (using serviceOrder format)
Tech.
acknowledge
ONAP
Adaptation Layer

4. Orange contribution to ONAP Project – after drop 1 Northbound TMF API
When ? TBD PO
Expand ONAP footprint:
Assess serviceOrder component integration within ONAP – which means:
Service order are stored in ONAP component
Relationship between service order management component and MSO are ‘ONAP-Internal ‘ (what about adaptation layer role ? Could be merged with MSO ?)
Product order mngt component
ONAP extension ?
Response GET serviceOrder
(order detail)
Request
POST serviceOrder
Response POST serviceOrder
(id)
Request
GET serviceOrder/id
Service order mngt component SO
ONAP
Adaptation Layer ?

5. Orange contribution to ONAP Project – after drop 1 Northbound TMF API
When ? TBD
Expand API footprint:
Assess capabilities to expose service catalog API from SDC and alignment with TMF API
Leverage service catalog API to improve service Order API  dynamic service order build based on catalog information
Master catalog provides ProductSpec  ServiceSPec
SDC catalog API provide serviceSpec information to build accordingly serviceOrder/item/relationship
Assess capabilities to expose service inventoryAPI from AAI and alignment with TMF API
Leverage service inventory API to tackle service management UC (modification of existing service)
ONAP
Service order API SO
Service Catalog API
Service inventory
API
Service catalog
Service inventory