General Description
The Provisioning Database Interface (PDBI) provides commands that communicate provisioning
information from the customer database to the provisioning database (PDB) in the Active PDBA in
an EAGLE 5 ISS. The customer executes provisioning commands using a provisioning application.
This application uses the PDBI request/response messages to communicate with the EPAP Provisioning
Database Application (PDBA) over the customer network.
EPAP (EAGLE Provisioning Application Processor)
As shown in Figure 1: Example EPAP/PDBA Network, the provisioning system contains two mated
EPAPs. Of the two mated EPAPs, only one is the Active PDBA, while the other acts as a Standby
PDBA.
Each EPAP maintains two copies of the RTDB in the B-Tree format. When a Service Module card needs
a copy of the RTDB, the Active RTDB downloads the B-Tree file to the Service Module card. Each
Service Module card uses the B-Tree file to create its own copy of the RTDB database. The primary
purpose of an EPAP is to download the RTDB to the Service Module cards.
The Active PDBA interfaces with the customer database through the PDBI, which provides PDB
updates. When the customer submits provisioning requests, the Active PDBA updates its PDB. After
the updates are applied to the PDB of the Active PDBA, the updates are sent to the Standby PDBA.
Service Module Card
As Figure 1: Example EPAP/PDBA Network shows, the provisioning system uses up to 25 Service Module
cards . Multiple Service Module cards are used to provide a means of load balancing in high-traffic
situations. The database is in a B-Tree format to facilitate rapid lookups.
16
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual