Light Reading Mobile – Telecom News, Analysis, Events, and Research

8:00 AM -- How will communications service providers (CSPs) manage their revenue collection processes in the future? Are we on the cusp of a major shift away from post-paid billing to pure real-time charging?

That's a critical debate for the CSPs, their Service Provider Information Technology (SPIT) systems suppliers, outsourcing partners and, of course, customers.

Currently, it seems, there is no consensus on how this will play out, but the debate is as interesting as it is critical.

It's not a new topic of discussion but one that was given a new shot in the arm recently following the publication of this incendiary article, "The Death of Billing – and the Rise of Real Time" by Alex Leslie at Billing Views, which reported on a presentation given by an operator about the impending arrival of the "Post Billing Era".

That article -- give it a read, it only takes a few minutes -- sparked a response from Dominic Smith, marketing director at Cerillion Technologies Ltd., a supplier of billing, CRM and other telecom back-office software capabilities with more than 40 customers globally.

Smith's blog, "Billing: reports of my death are greatly exaggerated", is also well worth reading, as it provides seven reasons why the billing process isn't likely to disappear any time soon.

Now, you might say that any billing vendor is going to say "Of course billing isn't dead!" and that's true enough -- Smith isn't going to write a blog agreeing that a major part of his business is about to disappear. But his response is compelling and it's hard to argue against his vision of a world where online real-time charging sits alongside traditional billing mechanisms as part of the CSP revenue assurance strategy.

This is a debate that has an impact on many other parts of the CSPs' businesses, from application development to marketing, to mobile packet core capability selection. Check out both sides of the debate, no matter what part of the comms ecosystem you're in.

— Ray Le Maistre, International Managing Editor, Light Reading

8:00 AM Does post-paid billing have a future? The debate is intensifying…
November 22, 2012 | Ray Le Maistre |


Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Going Soft at MWC

SPONSORED BY
Related Videos
White Papers SPONSORED CONTENT
Featured
Interlaken
A chip-to-chip interface useful in 100G