At Traffix we come across many requests to connect Diameter to other legacy protocols.
We have the common familiar Gateway needs which usually involve two of the following:
LDAP, RADIUS, Diameter, Web Services, CAMEL.., but from time to time we got some other interesting requests, here are two that we recently had
Diameter GTP` connectivity
GTP` (GPRS Tunneling Protocol Prime) is used within GSM and GPRS networks, for transfer of charging data from GGSN’s to the charging function.
In MANY networks on the migration path to NGN, the GGSN’s are using GTP’ while the OCS (Online charging System) is already upgraded and using Diameter for charging connectivity, thus there is a need to convert GTP` messages into Diameter (Ro) and vice versa. We had an interesting case recently where we helped a service provider that had implemented a new charging system with all the goodies and with Diameter and needed to connect GTP` based charging interfaces from his GGSN’s to the new charging system.
Diameter CORBA connectivity
The Common Object Request Broker Architecture is a standard that enables software components written in multiple computer languages and running on multiple computers to work together, i.e. it supports multiple platforms. CORBA is widely used within NMS solutions, that are connected to different AAA Databases. With the migration to NGN, the AAA DB’s are migrating to Diameter, and a connectivity issue between existing CORBA interfaces and new Diameter interfaces arises. On a number of occasions recently we came across CORBA Diameter connectivity issues and with Traffix Diameter Gateway helped to bridge this gap.
Subscribe to:
Post Comments (Atom)
You are a very sharp guy. I think some of this stuff is going to go over the head of most people on blogger so my guess is that you are using it as a personal place to store your information or something. I understand your concepts and you are a visionary is my guess.
ReplyDeleteI am not sure how often you update.
Keep up the amazing posting.
Best regards
Regarding Diamteter-GRP connectivity, can this issue not be resolved by IMS charging co-relation, instead of converting GTP messages to DIAMETER Ro ?
ReplyDeleteThe access network charging information is passed from IP-CAN to P-CSCF via PCRF, over the Rx interface. This is for the signaling plane.
The Gx interface is shared between the GGSN (embedded PCEF) and the PCRF. This is for charging policies to be applied to the bearer.
Hence P-CSCF includes charging info in the P-Charging-Vector header based on the information received from the IP-CAN. This takes care of charging the signaling plane.
The PCEF already has interfaces towards the OCS and CDF for initiating online and offline charging. Charging is done based on the PCC rules that the PCEF pulls from the PCRF over the Gx interface. This takes care of charging the bearer plane.