Internet providers and operators enthusiastically welcomed the arrival of Deep Packet Inspection (DPI) technology that classifies traffic by application and protocol and manages it by blocking, prioritizing, rerouting and assigning bandwidth. A further improvement in performance and revenue generation can be achieved by establishing user-specific traffic management policies, which in fact kills three birds with one stone.
First, such policies increase profit. Any operator wants a higher ARPU (Average Revenue Per User) and a better return on bandwidth and the amount of data delivered to the user. Some extra income from adjacent markets such as OTT (Over the Top) or Internet advertising also does not hurt.
Second, prioritizing or rerouting traffic brings down operation costs and reduces data loss in overloaded networks.
Third, user-specific traffic mana-gement enhances customer loyalty. Apart from high connection quality customers also appreciate a broader range of products available, access to personal selection and customzation of services, customer feedback opportunities and rapid response to market demand.
Policy Control and Charging (PCC) solutions deal with all these issues and personalize provider services by means of active traffic management.
PCC suites are based on the PCRF (Policy and Charging Rules Function) software module that connects the operator’s DPI platform with BSS (Business Support Systems) to trigger user-specific (or group-specific) scenarios, tariff plans and so on. JSM (Jet Subscriber Manager) is precisely one of those brain centers of a PCC suite. JSM collects information of user profiles (tariff plans, connected services etc.), network resources (channel load, applications priority), the user session status (particularly, traffic used). This information plus additional data (the time of day, info from external partners) is employed to formulate system-specific policies that are sent to the DPI platform for execution.
By interacting with the operator’s external systems, JSM processes events such as changes in the tariff plan, addition/cancellation of services or user status changes (e.g. disconnection). Several variables are included in user profiles stored in the JSM database along with instructions that are valid for the life of the contract (say, turn on the Turbo functionality from 7 to 12 p.m.).
As JSM interacts with the DPI platform, it monitors user authorization, the start/end of sessions and any changes in session parameters. A user session log contains a username, user terminal identification, IP-address and other parameters from the RADIUS/DIAMETER message. Also, JSM monitors user traffic and collects pertinent statistics. DPI can send data on all user traffic, p2p traffic, traffic to/from certain nodes and so on.
JSM’s component architecture can be easily scaled up and/or customized to fit the needs and systems of a particular operator (in terms of billing, personal profiles, authorization rules and so on).
More information: http://jet.msk.su/en/about/
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