The blacklist data is used by the EAGLE 5 ISS to support IDP queries. If the calling party is associated
with a blacklisted flag and a GRN has been provisioned against the associated DN or DN Block, then
a connect message is sent back to the switch along with the GRN number. The GRN is then used to
re-route the call to a predetermined destination. Pre-existing DN and DN Block records have blacklisting
disabled by default.
EPAP-related features share the same Real Time Database (RTDB) database when operated together
on a single node. EIR and INP/AINPQ are mutually exclusive on a node.
Introduction to the Data Model on the Platform
The PDBA uses an object-oriented approach for data organization. The data is organized into three
independent “objects” that correspond to MSISDNs, IMSIs and SPs/RNs. These “objects” are a subset
of the database. Associations are established between an IMSI and MSISDN, IMSI and SP/RN, MSISDN
and SP/RN or IMSI, MSISDN and SP/RN through the use of pointers between the objects.
The database is created as follows:
• When an IMSI, MSISDN or NE (that is, an SP identifier) is created, this data is added to the
corresponding object, which is a subset of the database.
• When an IMSI, MSISDN or NE is deleted, the related data is removed from the corresponding
object.
• When an association is established between an IMSI, MSISDN and SP/RN, pointers are set up
between the appropriate objects.
• When an association is removed, the pointers between the objects are removed.
For example, assume that the database already contains several IMSIs, MSISDNs and SP addresses,
but that no associations have been established. The IMSIs exist in the ‘IMSI object,’ that is, the IMSI
portion of the database. Likewise, the MSISDNs exist in the ‘MSISDN object’ and the SP addresses
exist in the ‘SP object.’ When the ent_sub or upd_sub commands are used to establish an association
between an IMSI and an MSISDN, a pointer is created that points to the correct location in the ‘MSISDN
object,’ that is, the correct portion of the database where the MSISDNs reside. The same process occurs
when other associations are established, such as IMSI pointing to SP, MSISDN pointing to SP, or IMSI
pointing to MSISDN pointing to SP.
The EIR feature introduces the IMEI to the database. The IMEI for EIR may be associated with up to
8 IMSIs, but it is important to note that this IMSI has no relationship to the existing IMSI used by the
G-Port/G-Flex feature (ent_sub, upd_sub,dlt_sub, rtrv_sub) commands. In other words, IMSIs
provisioned for EIR are strictly added to the EIR database only. An IMSI may appear in both the
G-Port/G-Flex database and the EIR database, but must be provisioned by both sets of commands
(ent-eir and ent-sub).
Data Organization
MSISDN data is provisioned into two tables: a single instance table (Single DNs) and a block instance
table (DN Blocks). The database considers both Single DNs and DN Blocks as entities in their own
right. Therefore, a distinction must be made between the terms ‘DN range’ and ‘DN Block’ as they
are used in this document. A DN Block is considered to be an autonomous entity, just as a Single DN
is. A DN range is just a range of numbers. Within a specified DN range, several Single DNs and also
several DN Blocks may exist. For instance, consider the following example:
Assume the following single DNs are provisioned:
10050
20
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual
To Next Page
Loading...
