In-browser notification solutions – hardcore softies

21 December 2015 | Speaker: Sergey Khromov

In the previous post (“Subscriber engagement – when “agnostic” is the right word!”) the importance of being vendor agnostic was looked at, with the focus on the integration with 3rd party carrier grade systems, such as DPIs, PCRF and location-based servers. The spotlight of this post is on the importance for in-browser notification systems (IBNs) to be software-only solutions. And being agnostic here is just as critical, because IBNs must be able to function equally well on real and virtual servers.

Technologies today give operators more opportunities to reduce CAPEX, moving operations to virtual environments, and it is critical for carrier grade systems to support this. Experts of Jet Telco have identified several trends, driving operators to implement solutions that allow for quick and easy scalability, can be installed on real or virtual servers, ensure redundancy to guarantee high QoE, support different network environments and conditions. IBN needs to be a true carrier-grade solution to give operators the required flexibility and security – and the only way to achieve this is for IBN to be a software-only solution.

Consider a straightforward example – mobile operator installs IBN, covering only 3 of its 15 sites, with concurrent subscribers that can be targeted with this solution not exceeding 200K, but 3 months later operator wishes to extend the coverage to 9 more sites, increasing the number of concurrent subscribers to over a million, considering that it will require partially decentralized implementation, with additional integration with DPI and PCRF. That being said, operator wishes to have this as an on-premise solution (not cloud-based) but without significant additional CAPEX. And to make this more interesting, operator plans to add its public Wi-Fi network to this IBN coverage, to monetize on online ads, as well as advanced Wi-Fi tariff plans.

This example is based on a real life case, when the RFP requirements were such that budgetary constraints not only excluded the possibility of proportional HW expansion but also required advanced maintenance and support at costs that were too low for any HW vendor to possibly provide. The project was successfully completed because the IBN was a software-only solution, that could be installed and integrated remotely, with completely remote advanced 24/7 support, using real and virtual servers. The vendor only needed to upgrade the licenses and install software on several virtual machines that operator already had, significantly reducing the total project budget and completing the implementation within a very short time.

Oh, and to make this an even more attractive offer for the operator, the vendor provided the solution that supported injection through DPI that operator already had installed, thereby further reducing CAPEX by eliminating the need for additional servers. However, this part of the example will be looked at in more detail in the next post that will focus on the importance for IBNs to support different injection methods.





See examples of Jet Toolbar messages!

Find the icon in the bottom right-hand corner of this page.

Click on it and see some examples of messages that can be created with Jet Toolbar