tag:blogger.com,1999:blog-19181559239826228212024-03-13T23:53:38.127-07:00Diameter BlogEverything about the Diameter protocolDiameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.comBlogger27125tag:blogger.com,1999:blog-1918155923982622821.post-348038203638577212012-03-10T01:54:00.002-08:002012-03-10T01:54:27.923-08:00In case you haven't heard<div dir="ltr" style="text-align: left;" trbidi="on">
<br />
<div class="MsoNormal">
The media had it in the spotlight for a while and you can
still catch a piece here or there. But just in case you haven’t heard the good
news, Traffix was acquired by F5 Networks (NASDAQ: FFIV), the leader in
Application Delivery Controllers. In
this post, I’d like to delve slightly deeper to explain why this is a good
thing for Traffix customers, all service providers, and ultimately, for the end
user. <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
F5 is a company of over a billion dollars in annual sales
and a market value of over 10 billion dollars, clearly deserving of the
reputation as the experts in IP solutions. Furthermore, the F5 organization is
unsurpassed in its investment in R&D, responsive support and timely
delivery. And their results speak for themselves. <o:p></o:p></div>
<div class="MsoNormal">
Now that Traffix is an integral and important part of F5,
the experts of the applications and data planes (the edge of a telephony
network) are joined by the experts of Diameter and the control plane (the core
of a network).</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
And most importantly, service providers have already begun to
experience the added value of our products’ synergies. Our solutions work
together to form the most comprehensive IP solution for telcos, ensuring
optimal performance of the edge and core networks. This end-to-end approach
enables service providers to seamlessly transform their networks to IP based
technology. And IP-based technology, or otherwise known as 4G, gives the
consumer the best experience in using a mobile device for data, meaning viewing
videos, playing games, checking Facebook, sending photos or many others. <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
There are multiple positive energies of the F5-Traffix
combination. Not only do service providers receive 100% reliable signaling
management, but they benefit from fortified R&D, delivery and support teams.
And there is renewed confidence that we are there for the long haul. <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
I’m confident that the market, both service providers and
their customers will be pleased with the merging of the two worlds because if
not immediately, sometime soon, your phone system will move to 4G, an IP-based data
and control. So what could be better than having the IP experts of all parts of
the telephone network put their resources, knowledge and expertise together to
ensure the highest quality of service, wherever you are, and however you need
it to work.<o:p></o:p></div>
<div class="MsoNormal">
Stay in touch, it'll be exciting.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Ben Volkow</div>
<div class="MsoNormal">
CEO Traffix </div>
</div>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com2tag:blogger.com,1999:blog-1918155923982622821.post-47716593278090156542011-11-15T06:19:00.001-08:002011-11-15T06:27:56.406-08:00What are the ingredients for a market leading Diameter router?<div dir="ltr" style="text-align: left;" trbidi="on">
<br />
<div class="MsoNormal" style="text-align: center;">
</div>
<div class="MsoNormal" style="text-align: left;">
<span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span class="Apple-style-span" style="line-height: 36px;">We've often asked what makes the Traffix Signaling Delivery Controller the market leading Diameter solution. We put our heads together and here's why we can proudly say that the </span><span style="line-height: 150%; text-indent: -24px;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"> </span></span><span dir="LTR" style="line-height: 24px; text-indent: -24px;"></span><span style="line-height: 150%; text-indent: -24px;">Traffix Signaling Delivery Controller (SDC) is the market’s first and most mature Diameter routing solution, available since early 2009.</span></span></div>
<div class="MsoListParagraphCxSpMiddle" style="text-indent: -0.25in;">
</div>
<ul>
<li style="line-height: 150%; text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="line-height: 150%;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"> </span></span><span dir="LTR"></span><span style="line-height: 150%;">Traffix SDC is the market’s most deployed Diameter routing solution with over a dozen live deployments in Tier 1 carriers.</span></span></li>
<li style="line-height: 150%; text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"> Traffix SDC is the market’s only full Diameter routing solution combining DRA, DEA and IWF that goes far beyond the industry standards’ requirements.</span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC offers far more Interworking functions between Diameter to Diameter, and between Diameter to legacy protocols than other vendors.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC is the only solution that can run on multiple IBM, HP and Sun hardware flavors with unparalleled performance in each.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC is the only dedicated Diameter routing platform (not HSS or PCRF….) in the market.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC has unbeaten performance and value/cost ratio – 4 times more than the closest competitor.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC supports over 50 Diameter interfaces – it’s the only solution that fits all Tier 1 Diameter needs.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC is the only market solution supporting Active/Active configuration.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC includes WideLens™, a network analysis, statistics and management solution.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC includes a full Diameter test suite.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix SDC is the solution of choice for vendors such as Ericsson, ATOS, NSN, Alcatel-Lucent, Amdocs, Bridgewater and others.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span style="line-height: 150%;">Traffix has the largest work force dedicated to Diameter in the industry.</span></span></li>
<li style="text-align: left;"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";"><span class="Apple-style-span" style="font-size: x-small;"><span class="Apple-style-span" style="line-height: 24px;"> </span></span><span class="Apple-style-span" style="line-height: 150%;"> </span></span><span dir="LTR" style="line-height: 150%;"></span><span style="line-height: 150%;">Traffix has demonstrated unbeaten commitment to our customers for the best support, flexibility and satisfaction.</span></span></li>
</ul>
<br />
</div>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-58908686376496323702011-11-06T04:49:00.000-08:002011-11-06T05:18:02.898-08:00The Brain Surgeons of DiameterI’ve been hearing something from the field that doesn’t quite sit right. I’ve been hearing that developers of 3G voice protocol SS7 can easily segue into developing good solutions using 4G Diameter protocol such as real-time intelligent routers and reliable load balancing solutions. <br /><br />Diameter was selected by the industry standards bodies such as 3GPP to be the one protocol that replaces all legacy protocols (MAP, LDAP, Radius, and others) because of its extreme flexibility to support data, services, and applications. <br />On the flip side, that side flexibility does cause management difficulties. Software engineers who work with Diameter find that after years of intense programming, they can succeed in creating cutting-edge solutions. They understand why Diameter is the chosen protocol to support all the data dominated services and applications of 4G. They know how to configure the code to ensure a 4G network’s reliability to send the right message to the right location 100% of the time. They can design intelligent routing and load balancing solutions to give the network unlimited scalability and 100% reliability.<br /> <br />However, this expertise took some years to perfect and a dedicated team focusing solely on the Diameter protocol and here’s the secret. It took the experience of deploying the Diameter protocol stack in operators around the world to learn the deep secrets and tricks of the trade of working with Diameter. And that is why today, Traffix is the only company that can call themselves true experts in the field of Diameter. That is why there is still is no other vendor offering a full Diameter solution of routing, load balancing and gateway solutions with the added value that Traffix Service Delivery Controller (SDC) offers. <br /><br />I would say that for others to claim, “we know signaling” based on past experience with SS7 or other legacy protocol is equivalent to a heart surgeon leading a team to operate on a brain without the back up of a brain surgeon. <br /><br />My son wants to have laser eye surgery to correct his myopia. Am I going to look for a doctor who recently went to a short course to perform the operation, or am going to ask everyone I know for their references, and then select the surgeon who has been doing this operation for years with the highest rate of success? I think the answer is obvious. <br />Susan Becker <br /> <br />Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-14834673501129364122011-09-11T05:27:00.000-07:002011-09-11T05:45:34.557-07:00Town Planning/Network Planning<a href="http://traffixsystems.blogspot.com/"></a>Imagine, if a small town consisting of one main road, a few arterial roads, with the traditional system of traffic lights, one day woke up to a new reality. Overnight its town residents were shocked to see thousands of new business moving in, bringing with them many more residents, constant commercial activity and of course, higher volume of traffic.<br />Well, if you think that the first tactic the town should take is to add more houses and streets, think again. Just adding these elements without the necessary infrastructure would just burden the congestion and confusion, and slow down the efficiency of the town.<br />It’s the same in a network. Just adding bandwidth or spectrum can’t solve today’s sudden surge of more activity of thousands or hundreds of thousands of smartphone subscribers using their mobile data for most of their awake hours.<br />The town needs to revamp its traffic light system just as the network – now filled with new elements and fragmented from the data strain and new services, needs to upgrade its signaling – and in 4G this means its Diameter signaling.<br />And what does upgrade mean? Well let’s go back to our town. If once upon a time, the town’s planners would have simply added more streets and traffic lights, today, they would consider a wireless traffic management system that operates according to the traffic flow for maximum optimization. So too, network architects must include Diameter solutions such as DRAs for intelligent, dynamic routing, load balancers for unlimited scalability and network control, and Diameter gateways for instant connectivity with legacy elements. <br />You wouldn’t want to live in a town whose infrastructure hasn’t kept up with its growth would you? Well, why would you subscribe to a carrier whose network hasn’t kept up with your needs for reliable and fast service?Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-88996037075728664982011-06-07T23:20:00.000-07:002011-06-07T23:21:06.626-07:00Diameter for the Technically Challenged"Diameter for the Technically Challenged" or what should you know about Diameter signaling protocol even if you are not a telecom engineer<br /><br />During your average day how many times do you speak and text on your smartphone, browse on your tablet, or work on your laptop? In the evenings you may read ebooks, message from your mobile, or check your Facebook. You go on vacation and watch videos while waiting for the plane, take pictures with your phone and send them to friends back home. You leave your Skype or instant messenger open on your tablet so you can always see who among your contacts are available for a quick chat. In short, you are always connected to the network, meaning that the mobile operator's processing behind the scenes to support all your data communications is always on, and has now become a critical factor in the performance of the mobile network. And the trend to use the mobile network for data is growing in leaps and bounds. <br /><br />Your Mobile Network is Moving to IP<br />To support your constant use of the Internet through your cellular network, many mobile operators are beginning to empower networks with Internet Protocol (IP) using technologies generally referred to as 4G such as IMS, LTE and others. These technologies require systems to communicate with each other using what is known as a signaling protocol that can support millions of subscribers accessing the Internet all the time. The particular signaling protocol selected by the telecommunication industry is known as Diameter. <br /><br />Diameter: The Chosen Standard<br />The organizations who set international standards in the telecommunications industry (such as 3GPP and ETSI) have selected Diameter as the signaling protocol to enable operators to support 4G services. Why is that? Because Diameter is the only signaling protocol that is capable of managing the constant flow of core network signaling in an environment that has become far more complex with many more network elements needed to fulfill the promises of 4G. <br /><br />Fulfilling the Promises of LTE Mobile Technology <br />Today's mobile network operator growth is fueled by data traffic; voice has become secondary. On paper, LTE and other IP-based technologies have made amazing promises to provide you with high quality mobile broadband, sophisticated services, tiered charging plans, better roaming schemes, and much more. However, the implementation of all these promised services takes place in the core network and requires signaling that will tackle the challenges for cost-effective connectivity, scalability and control in the section of the network known as the control plane. <br /><br />Data Brings Complexity <br />In fact, your mobile operator's focus on data will only increase in time as the initiatives of voice over LTE (VoLTE) take hold, introducing a network where everything is data. Access to data, meaning the web, video, SMS, MMS, presence, and VoIP, requires constant Diameter signaling with a spaghetti of network nodes and interfaces. Network operators need a configuration of Diameter solutions such as gateways to connect the new elements to the old ones, load balancers for scalability meaning to grow the network easily, and routers that ensure the messages from each subscriber go to the right places – in short, to support communications that are becoming increasingly complicated. <br /><br />Using Diameter to Control the Complexity<br />Once upon a time, network signaling was activated when a phone call began and ended when the speakers hung up. Now this scenario is no longer relevant, and your mobile operator has far greater challenges to solve. The only way for your mobile operator to successfully manage its network is to focus on its control plane with the right signaling products that provide cost effective, robust and intelligent solutions. <br /><br />You may not be a telecom engineer, but you want to know that your network will respond rapidly to your request the next time you pick up your tablet or mobile device. Whether you want to send a message home, check your train's timetable or download an app, you want fast communications. In summary, it doesn’t take a telecom engineer to understand that almost everything you do with your mobile device depends on data communications, and that the right Diameter solution is the key ingredient for high performance, excellent quality of service, and advanced service enablement. <br /><br /><br /><br />** The above was written by Susan Becker Traffix Marketing manager, I thought it’s a very good “Diameter for dummies” articaleDiameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com1tag:blogger.com,1999:blog-1918155923982622821.post-73402917646156291772010-08-04T08:51:00.000-07:002010-08-04T08:52:27.555-07:00Diameter over SCTPI want to discuss today one of the issues we had elaborated on in the Diameter technical group (http://www.linkedin.com/groups?mostPopular=&gid=1787697 )<br /><br />This is the trend towards Diameter SCTP<br />We see more and more Diameter running over SCTP in some major operators, really everywhere – APAC, EU and US.<br />This is still a very small percentage of Diameter (which in itself is still in early adoption days) but this is certainly a trend.<br />This creates some new issues:<br />- Vendors support for SCTP is limited – so connectivity problem is an issues<br />- Connectivity between Diameter SCTP/Diameter TCP requires mediation (Diameter SCTP to Diameter TCP gateways)<br />- Testing is problematic – many in between entites (routers/switches/load balancer…) have problems with SCTP and it takes time to understand this is not a problem related directly to your product, so you only test your product you test all the transport layer in between (something that works with no problem with TCP)<br />- Need for through testing – the product beaves completely different with none TCP layer 3 stack<br /><br />I really don’t know what the future hold, will Diameter over SCTP trend increase and it will become the common path ?<br />I personally don’t think so, there were many initiative to improve TCP over the years (e.g WTCP) and although they had great advantages over TCP they never won, so I’m afraid SCTP will follow the same route. But still there is Diameter over SCTP trend on the rise. Well we’ll need to wait and see.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com1tag:blogger.com,1999:blog-1918155923982622821.post-46746332654077403312010-06-18T21:23:00.000-07:002010-06-18T21:26:20.354-07:00Improving Diameter protocolThis time I want to discuss one of the problems we see with Diameter and introduce a work being done to overcome this problem.<br />Capabilities exchange is one of the fundamental and most important mechanisms in Diameter, it is taking place in the beginning of each session, and allows peers to define the basic parameters/capabilities for the session (version number, supported Diameter apps, security mechanisms, etc…)<br />But what if the capabilities on one of the sides change during the session ? what if the sessions are being kept open for long time<br />and in this time an upgrade or configuration change in one of the clients/servers involved takes place ? <br /><br />The way Capabilities exchange is defined in RFC 3588 is that it can take place only in the inception of a session, so if there is a change<br />during the session it means we need to tear down all the existing sessions involved and restarted in order for the updated capabilities to be taken into account – not very efficient you’ll agree.<br /><br />But worry no more, the cure is on the way, a new IETF Diameter draft is here to help - The Diameter Capabilities Update Application.<br />A work led by Glen Zorn, whom is one of the driving forces behind Diameter since his Cisco days.<br /><br />This work defines a new Diameter application intended to allow the dynamic update of a subset of Diameter peer capabilities over an<br />existing connection.<br />Because the new proposed Capabilities Update application operates over an existing transport connection, modifications of certain capabilities is prohibited.<br />There are a lot of heated discussions going on in the Diameter swamp around this new work – some security issues have being raised, but I think those will be handled also.<br />This is a blessed and important work (I can see all of you with Gx interface related work scars nodding your heads) and let’s hope we will have this draft approved soon.<br /><br />I personally believe with service providers complaining on the amount of signaling in Diameter and the delays involved in some of sessions set up times – this new work is very important and sheds bright healthy light into one of the dark corners of the Diameter 3588 RFC.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-72042326510743472472010-05-20T17:42:00.000-07:002010-05-20T17:43:52.114-07:00RFC 3588 vs 3588bis, what will the market adoptRFC 3588, the Diameter base protocol RFC was officially introduced in 2003 by the IETF.<br />Over the last couple of years there was a lot of work done to introduce a new Diameter base, this was led by people like Glen Zorn and Victor Fajardo, was named RFC 3588bis.<br /><br />RFC 3588bis is set to replace the original RFC 3588 with fixes to some of the Diameter base issues, mainly in the areas of session, security (TLS) and some improvements and clean up (IPSec..) <br /><br />I have a few concerns how It will affect the adoption of Diameter, which is today mainly in the telecom field (and not the Internet)<br /><br />There are a few questions that come to mind (and my own personal bet)<br />- Will the market move to RFC 3588 bis? (yes, the big question is in what rate)<br />- Will it create interoperability issues ? (yes of course)<br />- Will it create confusion ? (you bet)<br />- Will it help to establish Diameter position as the AAA/Control protocol of the next decade ? (maybe)<br />- Is it needed ? (I prefer not to answer this one )<br /><br />One thing for sure it’s going to be interesting in the Diameter scene, with continuing adoption, growing amount of Diameter signaling, Diameter spreading out of the mobile core to the wireline, booming amount of Diameter interfaces, LTE (which should be renamed to Diameter TE due to the amount of Diameter signaling there) and of course new Diameter base.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-85581655289685694472010-04-06T07:32:00.000-07:002010-04-06T07:33:48.886-07:00Diameter Routing Agent – some open questionsI want to share with you, some thoughts from discussion I recently had about DRA.<br />Diameter Routing Agent (DRA) was defined in 3GPP Release 8 and onwards to manage PCRF interaction in LTE networks.<br />PCRF’s are becoming more advanced, with more and more Diameter interfaces, more and more traffic – and pretty soon you need someone to manage this Diameter signaling Spaghetti – this is where DRA comes into the picture – putting some order and management.<br />We come across some first implementations of DRA’s (and yes we in Traffix have one also, and it’s fully 3GPP Kosher) in the market this days.<br />Some questions that come to mind from some first glimpse in DRA implementations: <br /><br />DRA – Standalone / or part of the PCRF<br />We see both scenarios in the market, some of the DRA’s out there are part of the PCRF, maybe it’s because they were rolled out by the PCRF vendors, I personally believe there is a huge advantage for a standalone installation, separate from the PCRF.<br /><br />DRA – Diameter Proxy agent / Redirect agent<br />DRA was defined to act as both Proxy or Redirect agent, there was a big argument if both functionalities are needed, and eventually it was decided not to decide.<br />I personally think giving the DRA the flexibility to act as both Proxy or Redirect is great, and makes sure that networks could be tuned and set with much less limitations.<br /><br />DRA - Interconnectivity<br />Policy in 3GPP is all about freedom – either in roaming scenarios or in interconnectivity between different technologies.<br />However with DRA being supported only by 3GPP for mobile networks, how will it integrate to the RACS in the TISPAN wireline networks for example ? will it affect fixed mobile convergence scenarios ?<br /><br />Diameter Routing Agent is still new functionality, both in the specifications and much more in the market, with first glimpses mainly in LTE labs and with half backed products that only resemble DRA from a far.<br />I personally believe DRA will become a central component in LTE and future telecom networks, getting more and more responsibility and functionality, but this days are still far and many standardization open issues need to be closed before that.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-71421553552690123612010-02-25T08:33:00.000-08:002010-02-25T08:35:01.809-08:00Telecom Analytics - the advantages of DiameterService Providers today are looking for new ways to increase revenues. One of the main paths towards achieving this goal is the use of analytics for targeted customer approach and for personalized, tuned, advanced and combined service offering. The above require real-time analysis of subscriber behavior and other information known to the service provider. This information should be analyzed per subscriber or a group of subscribers and used in order to tune customer service offering and user experience.<br />This information is available and encapsulated inside Diameter, some of the advantage of using Diameter compared to traditional Data path methods are:<br /><br /><strong>Granularity of information</strong> – the information that flows in the control plane contains the most valuable and strategic information in the network – the location of the subscribers, their buddies (IM friends) list, their phone number, the kind of technology they use to connect to the network, their charging scheme, their IP Address, services they are using, etc.<br />Most of this information is not available in the in the service and the data domain.<br /><br /><strong>Smaller amount of traffic</strong> – extracting information from the signaling flows can be done efficiently with software based solutions using off the shelf servers and is much more cost effective – the amount of traffic is typically 1/1,000 of the data path traffic.<br /><br /><strong>Synchronization and correlation</strong> – the signaling flows in the control plane enable synchronization between different transactions and extraction of information according to pre-configured definitions. For example: extraction of all information related to a specific subscriber, a specific services, a group of users or even a specific location.<br /><br /><strong>Pre-defined routes</strong> - extracting information from the data domain is not simple.<br />For example: messages might go through one route, and come back via another, this is the nature of IP environments, and thus a large scale implementation covering all possible routes is required. Furthermore, the amount of data that should be processed for the large amount of available applications and proprietary protocols is enormous. In the signaling domain on the other hand, traffic is controlled, interactions and routing is fixed, the implementation effort is therefore several scales smaller and the correlation of information is easier.<br /><br /><br />Information that can be extracted from Diameter:<br /><br />• Accounting-Record-Type<br />• WLAN-Information // used in WLAN access//<br />• Unit-Cost<br />• Traffic-Data-Volumes<br />• Time-Usage<br />• Tariff-Information<br />• Supplementary-Service // info on additional supported services //<br />• Charging-Rule-Base-Name<br />• QoS-Information<br />• Rating-Group<br />• Time-First-Usage<br />• Time-Last-Usage<br />• Time-Usage<br />• 3GPP-User-Location-Info<br />• SDP-Media-Name //file name //<br />• SDP-Media-Description // type, size,format …////<br />• Authorized-QoS<br />• SDP-Type<br />• 3GPP-Charging-Id<br />• 3GPP-PDP-Type<br />• PDP-Address<br />• QoS-Information<br />• GGSN-Address<br />• 3GPP-IMSI-MCC-MNC // Mobile Network Identifer //<br />• 3GPP-Charging-Characteristics<br />• Traffic-Data-Volumes<br />• User-Equipment-Info // terminal related information – vendor, model….//<br />• Terminal-Information<br />• Number-Of-Participants //for multi participent services //<br />• Participants-Involved //for multi participent services //<br />• Participant-Group //for multi participent services //<br />• LCS-Client-ID //Location info//<br />• Location-Type<br />• Location-Estimate<br />• Positioning-Data<br />• Calling-Party-Address //the call participents info//<br />• Called-Party-Address //the call participents info//<br />• Low-Balance-Indication<br />• Remaining-Balance<br />• MSISDN<br />• Service-Indication<br />• Service-area-ID<br />• Global-Cell-ID<br />• Location-area-ID<br />• Bearer-Identifier<br />• Guaranteed-Bitrate-DL //QoS//<br />• Guaranteed-Bitrate-UL //QoS//<br />• QoS-Information<br />• RAT-Type AVP // Radio Access WLAN (0) UTRAN (1000) /GERAN (1001)/GAN (1002)/ HSPA(1003) ..//<br />• Termination-Cause<br />• User-Name<br /><br />Summary<br />The signaling transactions through the control plane in telecom networks are the perfect enabler for network intelligence, analysis and user behavior monitoring. In Internet based networks over the top services model is the only model, the signaling is minimal and differentiation hardly exists. The common (and maybe best) way to extract user-related information is extracting it from the data path using DPI like products. The telecom market, however, offers a much richer and granular source of information which is encapsulated in the signaling path.<br /><br />Using the signaling as the main source for network intelligence offers several advantages:<br />o Signaling is easier to collect - smaller in size, routes are predictable<br />o Signaling is much richer in information compared to the data path<br />o Signaling could be correlated easily<br />o In converged networks and roaming scenarios signaling is the only source of intelligence<br />o Cost efficient – no need for large scale deployment of expensive super processors, signaling domain – 1/1,000 of the usual amount of traffic, in predictable routes.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-74298750031931130622010-01-22T07:39:00.000-08:002010-01-22T07:42:02.786-08:00Diameter on going work<span style="font-family:verdana;">Diameter is rapidly gaining momentum, breaking the mobile network implementations boundaries.<br />But still Diameter is young and misses some important capabilities and applications needed in order to “fulfill its destiny” and become the signaling protocol for telecommunications – taking full responsibility over control, policy, QoS and AAA and replacing over a dozen legacy protocols that are used today in both wireless and wireline networks and of course the Internet (don’t forget the IETF is the main sponsor of Diameter)<br /><br />I wanted to share with you some of the important work that is being done by the good people at IETF DIME to add those missing capabilities.<br />Here are some examples of work that is being standardized:<br /><br />draft-ietf-dime-diameter-base-protocol-mib<br />Defines the Management Information Base (MIB) module needed to manage an implementation of the Diameter protocol.<br /><br /><strong>draft-ietf-dime-local-keytran</strong><br />Some AAA applications require the transport of cryptographic keying material; this work specifies a set of AVP’s providing native Diameter support of cryptographic key delivery.<br /><br /><strong>draft-ietf-dime-nat-control<br /></strong>The Diameter NAT Control Application allows external devices to configure and manage a Large Scale NAT (LSN) device - expanding the existing Diameter-based AAA and policy control capabilities with a NAT control component<br /><br /><strong>draft-ietf-dime-capablities-update</strong><br />The Capabilities Update application is intended to allow the dynamic update of Diameter peer capabilities while the peer-to-peer connection is in the open state.<br /><br /><strong>draft-ietf-dime-ikev2-psk-diameter<br /></strong>Specifies the interaction between the Access Gateway and Diameter server for the IKEv2 based on pre-shared secrets.<br /><br /><strong>draft-ietf-dime-extended-naptr</strong><br />Describes an extended format for the NAPTR service fields used in dynamic Diameter agent discovery.<br /><br /><strong>draft-ietf-dime-realm-based-redirect<br /></strong>RFC 3588 allows a Diameter redirect agent to specify one or more individual hosts to which a Diameter message may be redirected. However, in some circumstances an operator may wish to redirect messages to an alternate domain without specifying individual hosts. This work defines an application by which this can be achieved.<br /><br /><strong>draft-wu-dime-pmip6-lr</strong><br />Support for Proxy Mobile IPv6 Mobile Access Gateway (MAG) and Local Mobility Anchor (LMA) routing.<br /><br /><strong>draft-ietf-dime-qos-attributes</strong><br />Defines a number of Diameter AVP’s for traffic classification with actions for filtering and Quality of Service (QoS) treatment.<br /><br /><strong>draft-ietf-dime-diameter-cc-appl-mib<br /></strong>Defines the Management Information Base (MIB) module needed to manage an implementation of the Diameter Credit Control application. </span>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-85180210383316002482009-12-10T14:02:00.000-08:002009-12-10T14:03:55.867-08:00The need for Native Diameter Load BalancingLoad balancing has been almost a mandatory component to successfully provide high availability and nearly transparent scalability to web-based applications in the last 20 years.<br /><br />Unlike HTTP and other web application protocols (SMTP, FTP, etc.), which are synchronous and stateless, the Diameter protocol is not only asynchronous but also do not abide by to a single request/reply communication sequence like web based communication protocols. This makes it more difficult to distribute Diameter because traditional web based load balancers are designed to operate best in a synchronous messaging environment in which a single request is made and responded to before another is processed.<br /><br />In traditional load balancing, the load balancing is achieved in layer 4 (TCP/UDP), unlike this in Diameter the load balancing need to be message based, which means it has to be done in the Diameter level, above the TCP (and SCTP in Diameter case) level, since sessions are long lived and can outlive the relating layer 4 signaling.<br /><br />More than this Diameter, due to its dynamic nature and the ability to add almost infinite amount of standard and vendor specific AVP’s and Grouped AVP’s in almost any combination, is a challenge to traditional web based load balancers, which cannot support the complex structure of Diameter and cannot fully use the Diameter AVP’s dictionary in order to perform dynamic load balancing of Diameter messages (for example try to configure iRules for Diameter, not a pleasant experience, I can assure you, make sure you got a few weeks of spare time)<br />To meet Diameter load balancing demands the Diameter load balancer needs to be a real native Diameter entity, this means it has to be a Diameter proxy in order to successfully use the entire set of AVP’s for load balancing decisions.<br />Being a native Diameter entity also enables the Load Balancer to offer many other benefits which are crucial for service providers, such as stateful configuration, Diameter masquerading, the ability to work dynamically with SCTP and TCP per the same session and to engage in Diameter over TLS in different scenarios.<br /><br />To act in a stateful mode, is important requirement for Diameter load balancers due to the nature of the information inside the Diameter messages and service provider’s assurance needs.<br /><br />Another related issue affecting service providers launch of new services is the complexity, cost and time associated with new network functionalities introduction. With the wide adoption of Diameter by service providers, every new network component is either a Diameter server or client, and needs to communicate with the other Diameter servers and clients around, this result in vast configuration and management burden and slow introduction of new services.<br />Having a Diameter native load balancer masquerades the need for this slow configuration, and services can be integrated and launched smoothly and faster, all the Diameter introduction/routing handling can be done in the native Diameter load balancer.<br /><br />The ability to load balance Diameter requires a unique understanding of the way<br />in which the applications that use Diameter behave. Protocols such as Diameter that are<br />asynchronous and communicate bi-directionally are challenging to scale, hence rise the need for a native Diameter load balancer that has the ability to be stateful, extract and route requests at the Diameter message level and can load balance based on connections.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-36083746117052972872009-11-07T10:13:00.000-08:002009-11-07T10:14:24.688-08:00Some interesting Diameter Legacy connectivity issuesAt Traffix we come across many requests to connect Diameter to other legacy protocols.<br />We have the common familiar Gateway needs which usually involve two of the following:<br /> LDAP, RADIUS, Diameter, Web Services, CAMEL.., but from time to time we got some other interesting requests, here are two that we recently had<br /><br /><span style="color:#000099;">Diameter GTP` connectivity</span><br />GTP` (GPRS Tunneling Protocol Prime) is used within GSM and GPRS networks, for transfer of charging data from GGSN’s to the charging function.<br />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.<br /><br /><span style="color:#000099;">Diameter CORBA connectivity</span><br />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.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com2tag:blogger.com,1999:blog-1918155923982622821.post-5687980092152727692009-10-06T08:43:00.000-07:002009-10-06T08:50:14.307-07:00Next Generation Networks Control Plane Challenges<div dir="ltr"><strong>The Challenge</strong><br />The introduction of NGN elements into the telecom network present opportunities to utilize technological advancements to reliably and cost effectively provide a broad array of all IP based services (mobile data, streaming video, advertisements, stock-market quotes,…) to an ever-expanding customer-base, in real time. Yes, we all know NGN is not happening overnight, nor is it happening all over the network at one time. But it is clear to the telecom observer that certain NGN elements are making their appearance in the telecom network, at times as a new Diameter-based OCS node and at other times as a newly introduced NGN element such as a PCRF. <br /><br />But to make this efficient, manageable and cost effective, the telco must adopt an overall NGN strategy. This NGN strategy needs to take into account both the opportunities that NGN presents to them as well as deal with the challenges presented by the new architecture. An NGN strategic view is especially important because an NGN network doesn't happen overnight. The last thing a telecom operator would like is to have an evolving NGN introduction without a real vision of the final goal. Were NGN an easy short term effort, the coherent implementation would be a simple part of the NGN project implementation; but NGN introduction is slow, at times very local to a specific area within the network (such as the interface between the GGSN and the OCS). Especially under these conditions the challenge of having an overall NGN strategy is crucial to the telecom operator.<br /><br />Of the many opportunities and challenges that NGN strategy presents to the telco, I would like to focus on those related to the NGN Control Plane. Unlike legacy networks, in which the control plane was primarily the proprietary domain of the Network Equipment Provider, the new NGN control plane is more open and standard. It benefits from well defined interfaces and functionalities and a new broad and flexible enhanced AAA signaling protocol –Diameter - which replaces the existing variety of legacy signaling protocols.<br /><br />Information that in the past was very difficult to retrieve from the network is now easily obtained. Interfaces requiring long and cumbersome integration are now replaced by standardized connectivity. NGN signaling enables new, fast, easy and cost effective service launches, translating into more services to the customer.<br /><br />However, this new NGN architecture faces some critical challenges (especially since more and more services will be, over time, launched based on this architecture):<br />· How to roll out and activate new real time services.<br />· How to handle the rapidly increasing signaling volume from the new services (which are typically more signaling-intensive than common in the past. Most legacy protocols that are UDP based, Diameter is TCP-based, with an ACK for each transaction – this alone doubles the amount of signaling),<br />· How to deal with the unavoidably greater fragmentation and amount of network components needed for real time and new multimedia services introduced by NGN.<br />Thus, load balancing (LB) becomes a key issue, - specifically the control plane load balancing. <br /><br />This is the challenge of the Control Plane – ensuring that the network is able to optimize the signaling load according to individual telco-defined network, subscriber needs and business operations parameters.<br /><br /> </div>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-48856004761551744752009-08-27T01:13:00.000-07:002009-08-29T21:36:04.743-07:00RADIUS Diameter GatewayWe come across many issues involving RADIUS to Diameter connectivity with requests to assist with our Diameter-RADIUS Gateway.<br />It’s really became a very common scenario, the System Integrator is deploying NGN infrastructure that comes equipped with Diameter connectivity and in is network he has legacy equipment that is sitting there for many years (and will stay for many years more) and supports only legacy connectivity (i.e. RADIUS) and now the System Integrator needs to connect the two protocols.<br />And of course Diameter and RADIUS are different protocols and cannot be bridged.<br /><br />I stumbled across an initial work by the IETF Dime group- <em>draft-zorn-dime-radia-gate-00.txt</em>, really in early stages, not even a draft yet, driven by Lionel Morend and Glen Zorn. <br />Glen is really one of the major forces behind Diameter for many years (I still don’t understand why the blessed CMS related work driven by him wasn’t standardized)<br /><br />It’s an interesting case where the standard bodies (the technical guys, flying in the air with no commercial weights to reality ) are behind the network adoption and the market need. Usually it’s the other way, for example LTE was standardized and until we will see real deployments it will be a few more years. <br />But in this case the standard bodies are behind, maybe because we live in a non standard world and the migration to NGN is evolution and not revolution, and RADIUS and Diameter need to co-exist for many years. Anyway this is blessed and very important work, and is based on real market need.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-29211186093461391402009-07-14T08:19:00.000-07:002009-08-29T21:36:04.753-07:00Diameter Routing AgentI want to discuss today a new network function introduced by 3GPP in its Release 8 standards.<br />The Diameter Routing Agent (DRA), the DRA is a functional element that ensures that all Diameter sessions established over the Gx, S9, Gxx and Rx reference points for a certain IP-CAN session reach the same PCRF when multiple and separately addressable PCRFs have been deployed in a Diameter realm.<br />What this means in plain English, is that the DRA helps to sort out the Diameter spaghetti in the network.<br />Routing of Diameter messages from a network element towards the right Diameter realm in a PLMN is based on standard Diameter realm-based routing, as specified in IETF RFC 3588.<br />The DRA keeps status of the assigned PCRF for a certain UE and IP-CAN session across all reference points (e.g. Gx, Gxx, S9 and Rx interfaces)<br />The DRA supports the functionality of a proxy agent and a redirect agent as defined in RFC 3588 . The mode in which it operates (i.e. proxy or redirect) shall be based on the operator’s requirements.<br />Diameter clients of the DRA (i.e. AF, PCEF, BBERF and PCRF) in roaming scenarios shall support all procedures required to properly interoperate with the DRA in both the proxy and redirect modes.<br /><br />After all this technical flood, I think that the main importance of DRA from Diameter perspective is that it’s the first time that the 3GPP standard body is supporting and backing an “in between” Diameter component.<br />Those components known as agents are part of Diameter in its IETF base, but were never used and adopted by the telecom standard bodies that adopted Diameter and headed by 3GPP, it was always a client server game. A DRA is really a Diameter Redirect Agent or a Diameter Proxy Agent as defined by the IETF.<br /><br />In my opinion the adoption and backing of the DRA, is the final stamp of approval to the IETF Diameter work and to the embracement of Diameter as the main signaling protocol for telecommunication networks. I suspect we will see more and more Diameter agents either packaged as DRA or in other names in the coming years with the continuing migration to NGN and the growing amount of signaling.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-27392053085320802162009-06-12T12:09:00.000-07:002009-08-29T21:36:04.774-07:00The forces behind increasing Diameter signalingI want to discuss some of the issues pushing the amount of signaling and Diameter.<br />We see growing amount of Diameter traffic in the networks, presenting Service providers with new challenges of managing Diameter traffic, scalability and confronting bottlenecks in their networks.<br /><br />Here are some of the reasons for the growing amount of Diameter signaling<br />- Subscriber growth and subscribers migration to Next Gen. Networks<br />- Flat rate plans for data services<br />- Growing amount of Converged networks<br />- Diameter maturity with growing amount of interfaces and connectivity<br />- Continuing network migration to NGN<br />- Growing number of enforcement (DPI/PCEF) and policy (PDF/PCRF) functions, which are major source of Diameter signaling<br />- Increase in new services<br />- Continuing migration from 2G/2.5G to 3G, NGN and beyond (e.g. LTE)<br />- New interface speeds<br /><br />Another important affect to take into consideration is that with the increase in network and signaling complexity and traffic of Diameter signaling in NGN, the network management becomes a growing concern, with new issues (surprisingly familiar from the days of SS7 based networks) related to identifying, analyzing and solving network related issues.<br />All those signaling and Diameter related issues can result in growing maintenance and management costs, increasing downtime, QoS issues, customer satisfaction and of course Service providers revenues.<br /><br />To confront those issues, Services providers need to add and scale NGN infrastructure capacity, and to take into account Diameter and network design, scalability, signaling balancing and routing when charting new NGN related RFP’s. <br />Here at Traffix we offer them a set of products to confront those issues, from Diameter Gateways to confront vendor and standard interoperability issues, through Diameter load balancers and up to advanced contextual signaling and Diameter management solutions.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com1tag:blogger.com,1999:blog-1918155923982622821.post-64350435479992629992009-05-18T11:33:00.000-07:002009-08-29T21:36:04.785-07:00Hi,<br /><br />I want to share with you a question asked by our VP Marketing Lior in the Diameter group<br /><br />What is the most interesting (for you) Diameter based service?... and why?<br /><br />I think it's a great question, and represents the real reason to move to NGN/IMS/LTE and as a result Diameter.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-46943484205934189092009-05-02T23:16:00.000-07:002009-08-29T21:36:04.794-07:00Diameter implementations – not for the faint of heartI want to share with you a few horror stories about some of the Diameter implementations we see out there.<br />We recently came across an implementation by one of the main network vendors where Diameter server is sending Diameter client messages – of course that the clients in the other end could not respond and some of them where getting quite mixed up with the unexpected message.<br />This is really the tip of the iceberg, Diameter is very flexible and in NGN the applications are still very young – a destructive combination it seems, so the way the standards are translated and implemented varies across different vendors.<br />It’s not only the network equipment providers, some of the operators have also joined the party, with in-house Diameter standards and requirements that have already gained quite a “notorious reputation” in where they taken the standards and their non conformance, I don’t want to name and shame anyone, but I’m sure some of you are nodding their heads with called sweat.<br /><br />Is it becoming better ? well not really, LTE/SAE is being developed today, new cable standards, new ETSI TISPAN equipment, and there things aren’t better, development is starting before the interfaces are finalized, so sorry no good end to this post, I believe the interoperability issues will keep accompany us in the recent future and will affect the dream of open plug & play no silo networks.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-36145816838859573412009-04-20T08:34:00.000-07:002009-08-29T21:36:04.803-07:00Some thoughts about DiameterIs there a need in Diameter cards ? I looked at some SS7 and Sigtran projections a few days ago, there is a market for SS7 and Sigtran cards, this is a market along the stack market and actually even bigger.<br />I’m personally not sure there is a need for Diameter cards, I think IP based protocols market behave differently, but time will tell.Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-9944337463214927602009-04-04T10:33:00.000-07:002009-08-29T21:36:04.810-07:00The amount of Diameter signaling<div dir="ltr" align="justify">I come across more and issues regarding the amount of Diameter signaling and how it affects service providers networks.<br />Diameter is coming out of the labs, and when it’s moving to working environment the real network issues are starting to emerge.<br />So why Diameter is creating so much signaling, I believe the main issues are:<br />- Diameter is TCP/SCTP based compared to legacy signaling protocols like RADIUS that where mostly UDP based.</div><div dir="ltr" align="justify"><br />- Network fragmentation - in NGN like architectures, the number of network components is increasing, and many components were divided (for example the softswitch was divided to three different CSCF functionalities) </div><div dir="ltr" align="justify"><br />- Nature of new services – many of the services and applications (AS) are heavy signaling generators – like Presence and Location servers that create heavy signaling load or Policy servers (PDF/PCRF/RACS) that are creating heavy policy and enforcement Diameter traffic.</div><div dir="ltr" align="justify"><br />- Direct connectivity – in NGN connectivity between the components was defined directly, point to point - from functionality to functionality, at the time the standard bodies didn’t believe “in-between” components are needed, well I guess they skipped the history lessons especially the chapters about routers, STP’s and SBC’s – this is also contributing to the heavy load, complexity and lack of ability to balance and manage the Diameter signaling.</div><div dir="ltr" align="justify"><br />- New charging models and closer integration of BSS and network, which create heavier network load, in both the network side (Diameter signaling) and the BSS (CDR’s).<br /><br />I believe this is only the tip of the iceberg, Diameter today is really still mainly in testing and within the labs, I think the amount of signaling issues will only increase in the coming years directly with Diameter adoption. It’s defiantly going to be interesting.<br /><br /><br /> </div>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-85520754400894468922009-03-20T00:53:00.000-07:002009-08-29T21:36:04.874-07:00Diameter adoption and network geography<div dir="ltr" align="justify"><br />Diameter is used everywhere in the NGN core network – it is in the mobile, wireline, WiMax, Cable, from the ASN’s, GGSN’s and BRAS up to Application Servers. There isn’t a network core entity without at least Diameter interfaces, and some of them network functionalities have up to 4 different Diameter interfaces.<br />There are dozens of Diameter interfaces defined, over 110 interfaces are actually defined for Mobile, Wireline, Cable and WiMax and it seems also that the number is growing rapidly, new interfaces are introduced all the time, either for LTE (dozen of new interfaces), Lawful interception, interoperability, Roaming, IPTV, advanced policy and other needs.<br /><br />But in reality most of those interfaces are still on the drawing boards or in the R&D labs, and not deployed and used yet in operators networks.<br />So what we see in the market, what places have the highest Diameter maturity, here is my view, top to bottom<br />I believe that the highest maturity is around the Charging and Billing systems ( what is called Rf, Ro, Gy, Gz, CCA interfaces)<br />It could be the connection from the Application to the Charging system, or from the GGSN to the Billing, or other network functionality, but it seems always to involve some charging component.<br />2nd place is given to the AAA servers and subscribers databases area, either HSS, NASS or other AAA Server, (interfaces like Sh, Dh, Cx, Dx), it could be CSCF connectivity to HSS, HSS to Application Server or one of many other scenarios of connecting to a AAA and subscriber databases using Diameter.<br />The 3rd place closely behind is taken by the policy and enforcement area. Policy is a spaghetti of Diameter with more than 9 Diameter interfaces (Gx, Rx, Gq, Gq’, Tx,Ty…) and we see almost any combination you can imagine of those policy related Diameter interfaces nd sometimes requests for all of them.<br /><br />The rest of the network Diameter interfaces are defiantly behind, we see growing number of requests for almost all the 100+ defined interfaces, but they are still tailoring behind and you can find them today mainly in the vendors and operators labs and not in deployed operational networks.<br />Actually one of the emerging areas is the LTE related Diameter interfaces, although not finalized yet, and bearing a temporary name those Diameter interfaces are in high demand with strong interest by vendors starting to developing and testing LTE related equipment.<br /> </div>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-44626510267683002492009-03-03T12:04:00.000-08:002009-08-29T21:36:04.883-07:00LTE and Diameter<div dir="ltr" align="justify"> It seems LTE is moving to the manufacturing halls.<br />The industry has aligned behind it (leaving far behind some potential alternatives such as Mobile WiMax), and in recent weeks we saw some new announcements on first deployments in Tier-1’s in 2010.<br />What place does Diameter take in LTE architecture ? well it seems much bigger than in the past, even compared to IMS.<br /><br />There are about 15 new Diameter interfaces (on top of the existing 30 inherited from previous 3GPP versions and that are also used in LTE), and Diameter is getting out of the network core, closer to the edge and to the interconnectivity and roaming connections between operators.<br />However there are some warning signs – LTE standards are still work in progress, and the same for the LTE Diameter interfaces – so the potential for interoperability, connectivity and vendor lock-in issues is stronger than ever before.<br />Here in Traffix we supplied a number of network equipment vendors with LTE Diameter interfaces – and surprisingly each one wanted a different version of the still forming LTE (3GPP Rel. 8) specifications.<br />In some places where the standards and the Diameter interfaces are still too young to do the job, the equipment vendors are using earlier Diameter interfaces – again this wont contribute to connectivity.<br />So what’s the conclusion – well that the interoperability issues that operators are facing today won’t disappear with LTE, actually I believe they will be even bigger than in the past, especially in the first 2-3 years of LTE deployments.<br />I believe this might also slow LTE adoption – operators will understand the immaturity and that the “dream” is far from reality, and the related costs and will prefer to wait a bit until LTE will be more mature.<br />Actually it sounds a bit like IMS all over again (just replace LTE with IMS in the lines above :-) )</div><div dir="ltr" align="justify"> </div><div dir="ltr" align="justify">Ben<br /> </div>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-68063308354468166262009-02-21T11:05:00.000-08:002009-08-29T21:36:04.892-07:00Barcelona – thoughts in Layer 5<div dir="ltr" align="left"><br />This week I been in the Mobile World Congress in Barcelona.<br />A lot of words were written about the show, by people with much more knowledge and better writing skills.<br /></div><div dir="ltr" align="left">I will try to give another view of the show – not from the shiny handsets point of view, but from the Diameter view of things.<br /></div><div dir="ltr" align="left">I think that from the network side there are three main trends/activities that are happening and have close symbiotic relationship with Diameter<br /></div><div dir="ltr" align="left">The first one is Convergence, I know it’s been around since the millennium, but it’s really happening, maybe not because of the service transparency and new services, as much as the fact that it can save OPEX and CAPEX and create new revenues by opening new markets. Convergence requires a lot of Diameter, but also presents a huge challenge in the Diameter level – how to connect wireline and mobile infrastructure that use different Diameter standards, or how to connect mobile Diameter based equipment to ISP equipment that is still using RADIUS.<br /><br />The second trend is LTE, it’s enough to see some of the press releases from Verizon, Ericsson and Alcatel-Lucent to understand that the industry is aligning behind the technology, and in 2010 we are expected to see the first roll outs.<br />LTE represent a all new set of Diameter interfaces, with brand new networks that are using (by the standard) more than 45 Diameter interfaces, Diameter is everywhere and actually not limited to the core anymore, it is moving out to the edges, up to the last mile – those Diameter interfaces are not out there yet – so what will NEP’s do – I guess as always – build their own semi standard interfaces – and will continue to sweat on interoperability and lock the operators<br /><br />The last trend is the Cloud – some heavyweights such as IBM, are pushing it, and they see it taking over the telecom world.<br />Financially it makes sense, mainly with MVNO’s and small operators but also with the Tier-1’s that don’t want to spend billions on OPEX and CAPEX.<br />I think one of the main issues that I can see from that level is that there are going to be huge interoperability issues, and the datacenters will need to have Diameter Gateways in the entrance to the cloud to make sure the information can be spread inside the cloud with no vendor and standard lock-in.<br /><br />There are a few more things that changed this year, such as UMA – one of the big trends of the last few years almost disappeared, and it seems that Mobile WiMax might be going in the same route, unless something drastic will change, most of the people I met weren’t’ optimistic on its future.<br /><br />That it, next time I will try to dig in Diameter and LTE, what is new, and some of the challenges.</div>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0tag:blogger.com,1999:blog-1918155923982622821.post-49427204656105036362009-02-10T10:52:00.000-08:002009-08-29T21:36:04.902-07:00Diameter and the Internet<p dir="ltr" align="justify">Diameter and the Internet<br /><br />Diameter as the primary control and AAA protocol in the telecom arena, is something most of you will shift a bit in your chair but will agree is around the corner.<br />What about Diameter as the primary AAA protocol in the Internet ? well this is something that might require a bit more imagination (and wider chair).<br />(OK now take a deep breath) I personally believe there is no other alternative and this is not so far away.<br /><br />The Internet and the telecom environment are moving closer – FMC, Convergence, unified subscriber databases, mobile operators becoming ISP’s, death of the telecom walled garden and NGN are some of the reasons. Convergence and FMC don’t end up in the flyers and marketing brochures, it goes down beneath the hood, to the wires – to the signaling – to Diameter.<br /><br />New services – The Internet is shifting, new services are being introduced by ISP’s – few examples are gambling, multimedia, VoIP, QoS, Ads – those require a bit more than the current RADIUS AAA signaling of user name and password used today. ISP’s want it all, they want advanced pre/post billing, insured QoS for SIP and VoIP services, content based billing and so on.<br /><br />Standard bodies – last but not least, did you know that Diameter was initially defined for the Internet by IEEE ? so this is a good start – Diameter is not seen by the IEEE Internet gurus as another “strange telco feature” that the strange guys in 3GPP and TISPAN want them to adopt . Also there is a lot of ongoing work in IEEE and other standard bodies in this direction(such as the Diameter SIP Application)<br /><br />Those are some of the reasons why I believe Diameter is on a solid path to become the leading AAA and Control protocol in the Internet arena.<br />Now if I managed to convince you, the next question is When ? </p><div dir="ltr" align="justify"></div>Diameter Signaling Expertshttp://www.blogger.com/profile/08192378690267787229noreply@blogger.com0