Quality of Experience: well for a user, a must for a provider
Popular and actually not so funny joke: wanna know the darker side of a certain person? Like, how rich is the obscene vocabulary of this individual? How this person behaves while intensively stressed, etc.? It’s easy. Put this unfortunate human in front of a computer and provide slow Internet connection. Results might be stunning.
Worship thy customers – by knowing them
There is the peculiar transfer of meaning in the very name of Quality of Experience (QoE). If we are thinking “quality experience”, then it has to be an end-user thing. Something similar to User Experience: very trendy lately. And let’s be honest, User Experience is the purely marketing (social-marketing, to be precise) concept. Well-known UX – the one the shopper gets in stores, no matter online or offline for our case, and which can be extracted from that individual by questionnaires, feedbacks and other very subjective, human-factor-involved ways.
As such, that “end-user side” Quality of Experience is widely perceived as a brand/customer interaction, as loyalty in progress, so to speak. A complicated kind of communication with a good chunk of psychology – to where exact measurement application is, again, quite complicated. Even at the very end of definitions and functionalities it is hardly seen as a tool. Neither an ingenious technical solution that produces tangible, manageable and conclusive data.
Our contemporary digital world shifts everything related to QoE to the “provider side”. It is not a user anymore who monitors available Internet services and either enjoys technicalities or complains to the provider. (We mean, customers can still watch their connection and give feedback – but their words cease to be important). It is already a provider who attempts to see its connection end to end: being confident “Thy Customers” always receive an agreed level of service, monitoring service quality in real time and taking steps to prevent possible deterioration.
So it is both: Quality of Experience technical stuff is on a provider; and the meaning, the burden, the obligation to have an experience is taken from a customer too. And it’s more than just a peculiar game of senses. With QoE enabled provider gets a powerful tool to examine its entire network, to pinpoint the weakest links and in some cases to forecast the upcoming issues. All to furnish clients the best possible services – as well as to care for provider’s own ability to compete on a market.
Note: in this review we refer to as “services” various telecommunication offers exclusively, as the entire QoE topic is within the telecom framework.
Coming close. On tiptoes
It is usually extremely hard to elaborate a working definition of anything that involves – in our cases rather “embraces” – the human factor. Network capacities, bandwidth use, computing powers submit their data almost willingly. But what about an end user who rarely notices anything more than possible downtime or jittery sound or video? No complaints – then considered satisfied. Complaints present – dissatisfied, and it is very much like pure 0 or 100, either black or white, no grey zones or satisfaction expressed in percents.
We came with the following working definition for Quality of Experience. On a technical side it is a set of sensors gathering data as close to an end user as possible. On a social side it is the tool of interaction between a user and a provider.
On a social side also comes the most amusing part. Ideal QoE should act like a government of a Western democratic country – being as unobtrusive as possible, working almost stealthy. Emerging issues have to be addressed in no time, with proper Support Desk interventions, etc. But non-mandatory information should reach customers only when relevant, and in small portions. An example: a customer will be pleased if informed beforehand that some services will be down due to maintenance and will resume operation at indicated time. While some notifications on better tariffs will only get an individual annoyed, since the existing offer fits this person flawlessly.
So, there’s another game of meanings. An end user gets the best Quality of Experience when it comes unnoticed. “The less we mark our presence, the better we look in the customer’s eyes”; the same delicate matter when the act of observation itself changes particles’ behavior.
Side effects. Benign ones
Properly set QoE module helps you, a provider: a) to save money, b) to earn money.
Since Quality of Experience is able to scrutinize the network, you will have handy the complete map of your possible issue triggers. With this map the need for total overhaul of your wiring is over – unless, of course, you were planning such overhaul for long time. So, patching only the most vulnerable spots will lower you CapEx: average indicator is 15-20%, while the absolute numbers are stunning – a wireless operator with about 30.000 cells may annually save USD 20M to 30M (!) just on cells upgrade.
Then, with your network optimized, come OpEx savings. And, if things done right, customers are about to start bringing you more revenue. The logic is simple: if the network proves to be fault-proof, then a customer can intensify the use, consuming more content and services – and getting very own positive Quality of Experience.
One more important matter: QoE monitoring close to an end user is legal, since the observing party watches not the client’s exact traffic, with site names, etc., but the NetFlow statistics – provider’s billing sees the same thing.
Experience the best
Stingray Service Gateway primary design is Deep Packet Inspection. Yet, with its multifaceted solutions, this software is capable to control traffic and analyze system components in wide variety of telecom services.
Stingray’s QoE module collects data and compares them to the preset metrics. Based on this evaluation the module can initiate improvements in quality of service. Here is to name only several capabilities of Stingray’s QoE module:
- Traffic prioritization with customizable triggers and filters; black list filtering installed.
- Integration with BRAS and various billing systems; possibility to use integration API.
- Automated tickets in Support.
Stingray’s QoE module is called to carry out the selection of tasks, from detailed network monitoring to various Marketing & Sales activities, all the way up to customer profiling and advertising insertions.