Network Protocol Gateway
The MATRIXX Network Protocol Gateway communicates with "northside" (mobile) network traffic protocols. You use Network Protocol Gateway as an entry point to communicate with network nodes, and you can rate and bill for services from those protocols. Currently, Network Protocol Gateway processes and bills for SMPP traffic by using the MATRIXX SMPP Adapter.
Figure 1 shows the MATRIXX components that work with Network Protocol Gateway. Network Protocol Gateway accepts mobile traffic from your network in its native format and uses Gateway Proxy to translate it into the MDC (MATRIXX data container) format that MATRIXX Digital Commerce components use. The MATRIXX Engine converts the message into an event that can be rated and, if necessary, charged for. If required, a return message can be sent back through the MATRIXX Digital Commerce environment to the appropriate network node.
SMPP Connection to Network Protocol Gateway
Network Protocol Gateway serves as the ESME for your SMSCs. When you start Network Protocol Gateway, it sends an SMPP BIND request to an SMSC to establish a link. It keeps the connection open by periodically sending ENQUIRE_LINK messages. If the link is lost, the application automatically attempts to reestablish it. Once the link is established, Network Protocol Gateway accepts SMPP+ AUTH_ACC requests to rate and bill for SMS messages and forwards the request to the SMPP Adapter. The SMPP Adapter converts the request to MDC format and forwards it to the MATRIXX Traffic Routing Agent (TRA). The TRA forwards the MDC to the active MATRIXX Engine for rating and billing.
Network Protocol Gateway loads custom MDCs from the MATRIXX Engine, and these MDCs can be highly customized at deployment. The expected structure of the SMPP+ messages is also configurable by using .yaml or .properties configuration files.