Overview
This chapter defines the Database Interface (PDBI) request and response messages. The messages are
listed in alphabetical order.
Provisioning
Provisioning clients connect to the EAGLE Provisioning Application Processors (EPAPs) through the
PDBI. The PDBI consists of commands and their parameters, which allow you to define the messages
that provision the G-Flex, G-Port, INP, EIR, A-Port, and/or IS41 GSM Migration features and allow
the retrieval of feature data.
PDBI messages are sent across a TCP/IP socket. The client application (defined by the customer) is
responsible for connecting to the Provisioning Database Application (PDBA) well-known port and
being able to send and receive the defined messages.
Note:
The customer must write his own client application that uses the PDBI to communicate with the PDBA.
PDBI messages (requests and responses) are NULL-terminated strings, which allows sending and
receiving the messages from any language that has socket capability (for example, Perl or Java).
Message Definitions
Each message definition consists of one request and one or more responses. A request is a message
sent by the client to the client application to invoke a service. A response is a message returned to the
client by the client application to confirm that the a requested service has been invoked, the transaction
has been completed, or a connection has been established.
Request IDs
Each request has an integer identification (iid) as its first element. The client can use the iid to match
returned responses with the original requests The integer is expressed as a decimal number in ASCII
and has a range from 1 to 4294967295. The iid is optional. If an iid is not provided on a request, the
corresponding response also does not have one.
Optional Parameters
Optional parameters are surrounded by square brackets [ ] in the syntax examples. If you want to omit
an optional parameter from the request command, omit the entire field including the label, value, and
following comma. Do not leave a comma in as a place holder. The parameter labels in the fields that
are sent on the request provide enough information to determine which parameters were omitted.
However, the field labels must be present on all specified parameters.
48
910-6022-001 Revision A, March 2011
PDBI Request/Response MessagesProvisioning Database Interface Manual