We are pleased to announce that in addition to Yota PCRF now we developed our own DRA! Moreover, we have already started using it in the production network.
Later on there will be Free DRA version available for download, but firstly we’d like to give you more insight into the product.
Why do you need DRA?
The number of signal interfaces and signaling traffic volume continues to grow at an unprecedented rate in the core of highly loaded LTE network. DRA is a key element that streamlines all the flow of Diameter signaling messages in the network. It provides load balancing, simplifies connectivity between the nodes and prevents network element overload.
Using DRA to centralize the signaling traffic
Yota DRA features and benefits:
Various vendor interoperability
Different interfaces support (Gx, Gy, Gz, Rf, Ro, Rx, S9, S13, Sy, S6a, etc.)
Multiple protocols support for routing, balancing and transformation: Diameter, HTTP, SOAP
Capacity of up to 100K messages/sec per server/blade
Linux based (Red Hat)
Centralized traffic management
Active/Hot standby High Availability
If you are interested in Free DRA version, please comment below or send us your feedback.
Leaders of our team Vladimir Romanov and Sergey Malygin will visit Berlin on 6th-9th April, presenting Yota PCRF product at the Policy Control & Data Pricing Conference 2014.
We will speak about Flexible Policy Engine and Yota PCRF success story.
So if you’re around, feel free to contact us and arrange meetings.
Looking forward to talking and sharing our knowledge with you!
Our team in Yota puts all the efforts to the PCRF product development. Policy and Charging Rules Function (PCRF) is an advanced policy management solution enabling the operator to dynamically control network elements and apply real-time policies based on service, subscriber and usage context. The performance of our application takes huge part of our energy and one of the key measurements that we definitely care is the CPU load. Below we would like to demonstrate the fantastic progress we’ve achieved from the version 3.5.2 to the version 3.6.1 in this field (there is a CPU load percent along the Y axis):
Most of the improvements touched the interaction between Data Base and PCRF logic. The smart statements usage, intelligent data r/w operations and cached information gave us such a great profit. To analyze and improve the DB statements usage our team developed a special utility called tt_perf_info. The idea of it is to measure the time that was spent in various parts of the statement execution. The fetch time, the execution time, the number of calls and the total percent from the whole time are collected with the help of this instrument. The measurements are based on the simple counters that are set inside the PCRF code for each statement and looks like:
Our team is developing PCRF (Policy and Charging Rules Function) product that is a significant component in operator network. We have a successful installation in Yota production network and so two important characteristics that we thoroughly care about from version to version are performance and stability under high load. To reach this goal we passed a long and interesting way from unit testing to functional regression testing and various performance testing in the end. And so here we would like to tell you some of our PCRF testing “secrets”. Below we will tell you about three main steps in PCRF testing (excluding unit testing that is zero and obvious one) that we follow during each version’s stabilisation.
1. Regression testing
We hold on to the Continuous Integration methodology and have Jenkins installed with all builds done there and unit tests and regressions tasks started from it after each build automatically. At present we have:
We are happy to share some great news with you! PCRF 3.6.0 release has started officially!
This version implements absolutely new strategy for SPR when DDF node becomes a permanent storage for subscribers profiles for all the systems interacting with the product. Of course you can use previous distributed SPR mode as well. Also a very useful real-time monitoring tool called “Dashboard” was presented where you can find main system parameters. And last but not least, new version includes extended diameter session start push-mode notifications to outer systems, new supportive test tools, extra config parameters for extra flexibility, monitoring instruments upgrades and performance optimizations.
This new 3.6.0 release has already been deployed to the production and now is working successfully in Russia central region and Sochi, the city of the 2014 Winter Olympic Games. You can also try it from the “Download” page here.
Our team in Yota is involved in development of PCRF, useful and important component of the operator network. Policy and Charging Rules Function (PCRF) is an advanced policy management solution enabling the operator to dynamically control network elements and apply real-time policies based on services, subscriber info and usage context. One of it’s key features we are really proud of is a flexible script-based policy decision maker. And here we would like to share our experience about this magical component.
Let’s take our thoughts away from PCRF, operators and clients for a while. Think about a high-performance and high-reliable system with some storage inside with a functionality like:
store & backup the information
reply HTTP requests as soon as possible
configure replies in a very flexible way so that it can be changed on fly