Updated architecture picture.
Remove unused pictures.
Update consumed APIs.
Change-Id: Icede1f1326dde1287014207842eb6bc06cd6858a
Issue-ID: CCSDK-2966
Signed-off-by: elinuxhenrik <henrik.b.andersson@est.tech>
Following illustration provides a global view about Non-Real-Time-RIC architecture,
integration with other ONAP components and API resource/operation provided.
-.. image:: ../media/o-ran-onap-integration.png
- :width: 800pt
+.. image:: ../media/ONAP-A1ControllerArchitecture.png
+ :width: 500pt
***************
=============
-Policy Management Service application is interacting with one ONAP API.
+Policy Management Service application is interacting with two ONAP APIs and the A1-P API.
*******
CBS API
*******
-This API is used to get the dynamic configuration of the service, such as available Near-RT RICs.
+The CBS API is used to get the dynamic configuration of the service, such as available Near-RT RICs.
::
CBS_GET_ALL
+
+*********
+DMAAP API
+*********
+
+The DMaaP API is used to provide the possibility to interact with the Policy Management Service through DMaaP Message
+Router.
+
+::
+
+ DMAAP_GET_EVENTS
+
+********
+A1-P API
+********
+
+The A1-P API is used to communicate with the Near-RT RICs (north bound). All endpoints of the OSC A1 REST API and the
+standard A1 REST API version 1.1 are used.
Following illustration provides a global view about **ORAN** architecture,
integration with other ONAP components and API resource/operation provided.
-.. image:: ../media/oran_architecture.png
+.. image:: ../media/ONAP-A1ControllerArchitecture.png
:width: 500pt