1. ONAP Service Capability Management
(SCM) Proposal
November 15, 2017

2. Catalogue Project Introduction Project Name Project Description Scope
2. Architecture Alignment
High level architecture diagram
Inner structure/inner modules of SCM
High Level Sequence Diagram of SCM
Service Unit Identification & Functionalities
3. Resources
4. Other Information
5. Key Project Facts

3. Project Description Project Name:
Proposed name for the project: Service Capability Management (SCM)
Proposed name for the repository: scm
Project Description:
The Service Capability Management provides highly Identifiable, loose coupling and ready to be exposed service capability for ONAP SDC/SO with user-friendly, operator level Design time and Running time environment functions. The SCM also coming with a Graphical User Interface (GUI) to present logical correspond service capability list for the operators and end-users.
SCM provides capability encapsulation based on the micro-services registered on MSB. SCM functions also includes design, administration, classification, cataloging, publishing, version management, access control , presenting for the above encapsulated service capabilities.
SCM is facing service and end-user level, while micro service is facing system level.

4. Project Description Scope: Target:
Available service capability registration into SC catalogues through corresponded API
Registered SC is managed / exposed to users with different levels.
Function Management: Service Functionality Description and Management
Version Management
External Service
Retrieve service
Routing service

5. High level architecture diagram
SCM

6. High level architecture diagram
Scalability:
Service Capability Management (SCM) provides service capability management for the operators and end-users, and have enough scalability so as to adapt various operators and end-users.
Security:
Service Capability Management (SCM) adopts comprehensive and exclusive safety control system. The outside system needs to carry assigned token when they call service instance catalogues and the catalogues tree allows traverse from outside requests after result filter.
Stability:
Service Capability Management (SCM) provides efficient and stable 24*7 service to all users and adopts specific rules when establish the catalogues tree to ensure stability.

7. Inner structure/inner modules of SCM
Service Capability Management (SCM) uses a three-layer architecture to manage the service instance information.
Coding rule:
SCM assigns unique identification code for each directory item with the name of their textual name.
System codes are assigned when the directory items are first built, and directory items name are provided by registration administrator. Then system codes of directory items are unique for the entire directory lifecycle.
.（root）
| -- First-level subdirectory
|---- Second-level subdirectory
| Service Capability item
Service Capability directory and register items both adopt ‘(system coding, directory)’ to identify uniquely.
The directory items are defined untidily by the directory Administrator. And the SC items can implement new, open, and undo through API after audit.

8. Level Sequence Diagram of SCM
Service Capability Management
Operators and end-users
Root
GUI
Items
First level subdirectory
Second level subdirectory
SCM SO
SDNC
Registration Proxy
Service Gateway
A&AI
NFV
Service Discovery
MSB

9. Inner structure/inner modules of SCM
SDC
Service
API SO
Design Time UI
Running Time UI
Name
Path
Admin
SC1
URL1
Ver/…
SC2
URL2
SC3
URL3 …
Service Finder
A&AI
Fault
Tolerance
Data Manager
MSB
Micro Service 1
Micro Service 1
Micro Service 1

10. aai-cloudInfrastructure
SCM Example for E-vCPE
Workflow Queue
Core
Scheduler
Task
Queue
SCM
Executor
Executor
service capability
Resource
Check
L3VPN Service
Cloud Service
Auto Test
Auto Test ……
vnfmgr
Micro
Service
SDNC
aai-cloudInfrastructure
aai-search
vnfres

11. Key Project Facts Project Name:
JIRA project name: Service Capability Management (SCM)
JIRA project prefix: scm
Repo name: scm
Lifecycle State: incubation
Primary Contact:
Project Lead: TBD
Mailling list tag:
Committers:
Please refer to the table above.
*Link to TSC approval:  Link to approval of additional submitters: 

12. Thanks
November 15, 2017