System Architecture and Requirements PCC(3.2)

This chapter contains a brief overview of the PCC architecture. For further information about the architecture and system requirements, see PCC Installation Instructions(3.2).

The Policy Charging and Control (PCC) solution consists of the following components:

• Usage Engine - Containing the Access, Control and Execution Zones for execution of workflows.

• Real-time Data Repository - For storage of runtime information. This is called Data Repository throughout this document.

The Policy Charging and Control solution is designed for high availability, with high throughput and low latency.

There are four options for the Data Repository:

• Using In-Memory Storage as PCC Data Repository (3.2) (that is set as default in the backend yaml but not intended for use in Production)
• Using Couchbase as PCC Data Repository (3.2)
• Using Redis as PCC Data Repository (3.2)
• Using MySQL as PCC Data Repository (3.2)