Data overload – an OSS opportunity

“The Ericsson Mobility Report found that mobile data traffic is expected to grow by 12 times between 2012 and 2018.”

The quote is a sub-set of yesterday’s but I thought I’d drill down on one important prediction – that mobile data traffic will grow by twelve times in six years.

This indicates that as individuals, we are surrounded by so much information that our brains need ways to filter most of it out. But since we tend to have an increasing number of choices and not as much time to perform the analysis in , we need tools to help provide insightful filtering and/or connection of ideas.

And the exact same is true for organisations that rely on communications technologies – insightful filtering and valuable connections are required.

At both levels, OSS analytics tools have the potential to simplify and enlighten.

At the organisation level, OSS and related analytics have been providing this type of assistance for years and there is still plenty of room to evolve.

At the personal level, insightful filtering and the creation of valuable connections has been a niche where the OTT providers such as Google have led the way, albeit only application by application (eg Gmail, Google Analytics, etc). Meanwhile, CSPs tend to operate on a consumption-based model where they profit from increasing traffic, so there is no incentive to filter and connect.

However, if the barrage of information increases like Ericsson predicts, there will be a growing imperative to provide filtering and connections across all applications. The obvious place for this to occur is on the Operating System of the device you use but does it cover people who work across multiple different devices (eg phone, PC, tablet, etc)?

The less obvious place is within the analytics engines of a CSP‘s OSS. Personal concierge services delivered by a CSP to simplify and connect, predict and pre-empt, may not be completely far-fetched if the data overload problem continues apace. What opportunities may lie herein?

As an OSS implementer, it goes back to designing a product not just for your customer (the CSP), but for your customer’s customer (the end user of communications services).

Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.