+- Unified REST API for managing A1 Policies in all near-RT-RICs.
+- Compliant with O-RAN R1 specification for A1-Policy Management (R1-AP v5.0, with additional features & fixes)
+- Synchronized view of A1 Policy instances for each rAPP
+- Synchronized view of A1 Policy instances in each near-RT-RIC
+- Synchronized view of A1 Policy types supported by each near-RT-RIC
+- Lookup service to find the near-RT-RIC to control resources in the RAN as defined in O1 (e.g. which near-RT-RIC should be accessed to control a certain CU or DU, which in turn controls a certain cell).
+- Monitors all near-RT-RICs and maintains data consistency, e.g. recovery from near-RT-RIC restarts
+- Support for different Southbound APIs to the near-RT-RICs (different versions of the A1-P and other similar APIs).
+- HTTPS can be configured to use a supplied certificate/private key and to validate peers towards a list of trusted CAs/certs.
+- HTTP proxy support for tunneling HTTP/HTTPS connections.
+- Fine-grained access-control - with new optional callouts to an external auth function
+- Fine-grained monitoring metrics, logging & call tracing can be configured
+
+## Configuration
+
+The A1 Policy Management Service uses default keystore and truststore files included in the container. The paths and passwords for these stores are specified in a YAML configuration file located at:
+
+
+
+### Default Truststore Certificates
+
+The default truststore includes the following trusted certificates:
+- **A1 Simulator Certificate**: [a1simulator cert](https://gerrit.o-ran-sc.org/r/gitweb?p=sim/a1-interface.git;a=tree;f=near-rt-ric-simulator/certificate)
+- **A1 Policy Management Service's Own Certificate**: Used for mocking and unit-testing purposes (ApplicationTest.java).
+
+### Overriding Default Configuration
+
+You can override the default keystore, truststore, and application.yaml files by mounting new files using the `volumes` field in Docker Compose or the `docker run` command.
+
+Assuming the new keystore, truststore, and application.yaml files are located in the same directory as your Docker Compose file, the `volumes` field should include these entries:
+
+```yaml