Wholesale Operators | Traffic Control
Traffic Control for Wholesale functions as a messaging hub, allowing SMS and MMS messages
to be exchanged between client networks. Traffic Control manages various message flows
involving SMPP, CMPP, UCP, MAP, MM4 and MM3 protocols, that allow operators to overcome
technical and contractual constraints on messaging interconnects. The system also provides
a full record on all processed messages, to allow billing and settlement between the hub
operator and various client networks.
Click for larger image
Features:
Routing of messages between carriers using combinations of any of the following protocols on input and output legs:
HLR, MSC and SMSC Proxy Support
The system has the ability to act as a proxy for HLR, MSC and SMSC network elements, thereby enabling SS7 connectivity through the
hub between client and destination operators.
TCAP Negotiation
In order to maintain the security of the international SS7 network Traffic Control includes support for TCAP Negotiation. This feature
ensures that all originating TCAP dialogues are authenticated to counter spoofing, faking or other fraudulent behaviour.
Mobile Number Portability
Traffic Control implements an intelligent subscriber resolution function in order to identify the true home network of any mobile
subscriber. Look-ups to determine the home network can be performed via INAP, LDAP, ENUM, static configuration, IR21-compatible line
ranges or as an SRI_SM. Additional look-up techniques can be implemented as needed.
Address Transparency
One of the main goals of the Open Connectivity project is to guarantee that the true identity of the originating network is available to the
destination network. Traffic Control ensures that this information is maintained for messages routed through the system via SMPP or MAP protocols.
Black Listing
Traffic Control allows black listing based on rules combining the originating operator, address details taken from the message, and destination operator.
These rules can be configured by the Hub Network administrators to block known threats to their domain. Blacklisting support at MSISDN level is provided.
Fraud Prevention
Traffic Control implements full compliance to IR.70 fraud prevention rules. Address information contained in SMS handled by the platform is inspected to prevent
against spoofing, faking, spamming or other fraud threats.
Reporting
Traffic Control maintains detailed statistics on all messages routed through the system. These statistics can be viewed as graphical reports via the web GUI or exported
as CSV for onward processing. The statistical information on the platform can also be queried via the onboard SNMP agent (get, getnext operation support).
Billing
Traffic Control facilitates inter-operator settlement based on AA.19 and AA.71 recommendations. Details of all message flows and events are maintained for all client networks
and so that billing for SMS Interworking can be affected correctly.
Automatic Handling of MM4 Variants
As differences exist in how the MM4 standard used to pass messages between MMSCs has been implemented by different vendors, Traffic Control supports automatic adjustments to
protocol messages to ensure successful Interworking between MMSCs.
MMS Acknowledge Request
The Operator can globally force the setting of the X-Mms-Ack-Request header to "Yes" of an MM4_forward.REQ. The resulting MM4_forward.RES is not relayed back to the sender if
it was not originally requested but is used by the platform to confirm successful delivery.
Partner Unable to Generate MM4_forward.RES Acknowledgements
The Operator can flag a destination endpoint as unable to generate MM4_forward.RES acknowledgements. For traffic to those endpoints where an MM4_forward.RES is required the
X-Mms-Ack-Request header is unset and the system manufactures the MM4_forward.RES that would have been expected.
Validation Checks on Incoming Messages
The Operator can enable per originating endpoint whether to perform a verification of the headers for an incoming MM4_forward.REQ. If enabled the checking that is performed
includes that all mandatory headers are present and well-formed. Non-compliant messages are rejected either in the MM4_forward.RES with the error "Error-message-format-corrupt"
or otherwise as an SMTP rejection.
Ericsson Multi-Tenant MMSC
Some Ericsson MMSC sites use a "multi-tenant" configuration of several nodes. Special handling is required to ensure that responses are routed back correctly to the originating
node in the cluster.
The Operator can provision an endpoint as a non-standard Ericsson "multi-tenant" MMSC. This requires that the X-Mms-Message-Id header is modified on all MM4 PDUs appending the
destination domain to the Id. The original Id needs to be remembered and reinstated for responses coming back.
Maximum Message Size per Endpoint
The Operator can provision a maximum size value (in Kbytes) for a destination endpoint which if exceeded in an MM4_forward.REQ causes that message to be rejected (either with an error in the MM4_forward.RES or with an SMTP error as appropriate). The message size is calculated after all adaptation has been performed.
Multiple IP addresses for an Endpoint
Traffic Control allows the operator to configure multiple IP addresses for a single Endpoint.
AA.70 Statistics
Traffic Control IX maintains statistics which support the reporting requirements of Annex 14 of the GSM Association AA.70 standards. Reports are monthly and per-Operator with values reported hourly and daily.
Substitution of Original Sender Domain
The Operator can provision per destination endpoint the substitution of the original domain in the "Sender" SMTP header of the MM4_forward.REQ.
Maintain Visibility of Originating Domain
The Operator can provide visibility of originating domain by provisioning one of two alternative adaptations of the MM4_forward.REQ per destination endpoint:
- The "Mail From" header has the local domain substituted. The X-Mms-Originating-System header has the local domain appended to a list which retains the previous domain.
- The X-Mms-Originating-System header has either the original or local domain appended to a list which retains the previous domain.
Substitution of Original "Mail From" Domain
The Operator can provision per source endpoint the substitution of a presentation originating domain in the "Mail From" SMTP command for all MM4 PDUs from the endpoint.
Prepaid Interfaces Supported
- DIAMETER
- Siemens IN (CORBA)
- PSA
Benefits
-
Full Interoperability with all Partners and Clients
Using Traffic Control our clients have a guarantee that they can interwork with all their partners and clients using the industry standard protocols used to transport SMS
traffic. The platform is fully extensible and additional interworking protocols can be added as needed.
This capability maximizes the possible SMS traffic the Interconnect Carrier is able to support, and ensures that they can rapidly launch new services for new clients.
-
High Performance and Reliability
With the fully distributed and scalable Message-OS architecture, our customers are secure in the knowledge that their systems will operate 24x7 and that their client’s traffic will be routed successfully to its destination.
-
Revenue Assurance
Traffic Control manages complex routing scenarios for Tier 1 levels of messaging to and from client networks, destination operators and other hub providers. In order to prevent revenue leakage, and to maximize potential revenues,
the system maintains full billing and accounting information for every transaction handled.
The sophisticated retry and buffering capabilities supported by the system also ensure that the greatest possible number of messages routed to the system will be delivered by the system thereby ensuring that no revenue generating opportunity is lost.