1. High Level Component Definition and Architectural Relationships

2. Component API definitions

DCAE Component provides the following interfaces:

Interface Name	Interface Definition	Interface Capabilities	Protocol	Status	Consumed Models	API Spec (Swagger)
DCAE-EXT1	VES Collector	An interface to share FM/PM data for VNF FCAPS from the VNFs via the EMS Driver to VES Collector	REST	Available	VES	VES-Collector
DCAE-EXT2	HV-VES Collector	Interface to support GPB over TCP for highvolume VES Events	Proto/TCP	Available	VES	HV-VES (High Volume VES)
DCAE-EXT3	DataFileCollector	Supports bulk/batch datafile collection from xNF	http/sftp/ftpes	Available	3GPP	NA
DCAE-EXT4	SNMPTrap	Supports SNMP traps collection from SNMP agents deployed in the network	UDP	Available		NA
DCAE-EXT5	RESTConf	Subscribes to external controllers and retrieves data	restconf	Available		RESTConf
DCAE-EXT6	OnboardingAPI (MOD)	Used for onboarding MS component spec file and data-format into Design catalog	REST	Available (POC)		Onboarding HTTP API (MOD)
DCAE-EXT7	Deployment Handler	High-level API for deploying/undeploying composed DCAE services	REST	Available		Deployment-Handler
DCAE-EXT8	Inventory API	DCAE Inventory is a web service that provides the following: Real-time data on all DCAE services and their components Comprehensive details on available DCAE service types	REST	Available		Inventory API
DCAE-EXT9	Data Extraction Service (DES)	Provides basic computation and data retrieval/access from datastorage maintained by DL handlers (Feeder)	REST	Available (Guilin)		des-swagger.json
DCAE-EXT10	DCAE Openloop/CL Event	Open loop and Control Loop event trigger from DCAE analytics/correlation MS into DMAAP	REST	Available		CL Event Structure
DCAE-EXT11	PNF Registration Handler	PNF Registration event published through DMAAP	REST	Available	VES	PRH (PNF Registration Handler)
DCAE-EXT12	ConfigBindingService (CBS)	The CBS provides API for all DCAE deployment mS to retrieve configuration from Consul.	REST	Available		CBS API

DCAE Component consumes the following Interfaces:

Interface Name	Interface Definition	Interface Capabilities	Protocol	Status	Consumed Models	API Spec (Swagger)
POE-1	Policy update notification via DMAAP	Recieve updates to DCAE MS configuration policies via DMAAP (consumed by DCAE Policy Handler)	REST	Available	tosca.policies.root TOSCA
POE-5	PDP - Policy Handler	Fetched policies for DCAE MS from the Policy Framework via PDP query	REST	Available	Defined by policy	POE-5 (Policy Decision API)
AAIE-1	Topology Enrichment	Enrichment query by Correlation/analytics MS	REST	Available		AAI REST API Documentation on readthedocs.io
Acumos-E5 Subscription	Acumos - AA (MOD)	Acumos Adapter - Retrieves models from Acumos using E5 interface and onboard them into DCAE (MOD) using OnboardingAPI and make it available in Catalog	REST	Available (POC)
SDC-6	Artifact Distribution	DCAE Platform (SCH) uses notification to retrieve MS Blueprint DCAE-VESOpenAPI manager uses notification to retrieve VES schema uploaded and perform validation		Available		https://docs.onap.org/projects/onap-sdc/en/latest/offeredapis.html

3. Component Description:

DCAE R8 M2 Release Planning#Architecture

https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/architecture.html

4. Known system limitations

Architectural Technical Debt

Hardening MOD components (delivered as POC) into mainstream component with redesigned catalog and Helm charts contributions

Runtime: None

In Honolulu release, DCAE Platform (Cloudify and handlers) will be used primarily for dynamic Service Component orchestration. All static components deployment will be migrated to Helm. Depending on progress of REQ-439 platform function support via helm, dynamic deployment migration will be dealt in next release.