aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/architecture/architecture.rst4
-rw-r--r--docs/consumedapis/consumedapis.rst22
-rw-r--r--docs/media/ONAP-A1ControllerArchitecture.pngbin0 -> 80069 bytes
-rw-r--r--docs/media/o-ran-onap-integration.pngbin218436 -> 0 bytes
-rw-r--r--docs/media/oran_architecture.pngbin23768 -> 0 bytes
-rw-r--r--docs/media/yaml_logo.pngbin3477 -> 0 bytes
-rw-r--r--docs/offeredapis/offeredapis.rst2
7 files changed, 23 insertions, 5 deletions
diff --git a/docs/architecture/architecture.rst b/docs/architecture/architecture.rst
index 3997950b..bfe827bd 100644
--- a/docs/architecture/architecture.rst
+++ b/docs/architecture/architecture.rst
@@ -21,8 +21,8 @@ Global NBI architecture for Frankfurt release
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
***************
diff --git a/docs/consumedapis/consumedapis.rst b/docs/consumedapis/consumedapis.rst
index bcf7267e..8357e43d 100644
--- a/docs/consumedapis/consumedapis.rst
+++ b/docs/consumedapis/consumedapis.rst
@@ -5,14 +5,32 @@ Consumed APIs
=============
-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.
diff --git a/docs/media/ONAP-A1ControllerArchitecture.png b/docs/media/ONAP-A1ControllerArchitecture.png
new file mode 100644
index 00000000..59516628
--- /dev/null
+++ b/docs/media/ONAP-A1ControllerArchitecture.png
Binary files differ
diff --git a/docs/media/o-ran-onap-integration.png b/docs/media/o-ran-onap-integration.png
deleted file mode 100644
index 5c66ae62..00000000
--- a/docs/media/o-ran-onap-integration.png
+++ /dev/null
Binary files differ
diff --git a/docs/media/oran_architecture.png b/docs/media/oran_architecture.png
deleted file mode 100644
index 3f99e090..00000000
--- a/docs/media/oran_architecture.png
+++ /dev/null
Binary files differ
diff --git a/docs/media/yaml_logo.png b/docs/media/yaml_logo.png
deleted file mode 100644
index 0492eb4b..00000000
--- a/docs/media/yaml_logo.png
+++ /dev/null
Binary files differ
diff --git a/docs/offeredapis/offeredapis.rst b/docs/offeredapis/offeredapis.rst
index 14fb881a..0efe5cea 100644
--- a/docs/offeredapis/offeredapis.rst
+++ b/docs/offeredapis/offeredapis.rst
@@ -21,7 +21,7 @@ Global ORAN architecture
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