Architecture
The Provisioning Gateway architecture is shown below:

Figure 1-1 Architecture Diagram

The installation of Provisioning Gateway as an interface between MTAS
and UDR provides the following solution:
- It automatically identifies and establishes the connection to each of the primary UDRs and starts provisioning. It uses SOAP interface for provisioning to SDS and UDRs.
- It has multiple instances of Provisioning Gateway but MTAS (Provisioning System) sends provisioning requests to only one instance at any point of time. This architecture does not provide high availability and is stateless. It means both the instances of provisioning gateway do not communicate with each other.
- It converts MTAS (Provisioning Client) requests to UDR SOAP request format and provisions the same to UDRs. It also transmits the original request to SDS.
- It provides FABR Segmentation feature along with multiple segments of UDR. UDR uses SLF data (Comcol based DB for FABR) and proprietary ComAgent for lookups from DA-MPs (Diameter Agent Message Processors). Each UDR pair is deployed in an active, standby configuration and each segment can have any number of such pairs.
- Each segment of UDR has multiple active-standby pairs and each pair has one VIP. In a segment, there is only one active VIP, which is a primary UDR.
- Each UDR instance in a segment has a complete SLF DB, which is replicated by comcol within the segment.