Do you know your ENUM?

September 24, 2007

Isn’t it funny how a new concept is often universally derided as nonsensical? There are many examples of this but none more so than Voice over IP (VoIP) (I mean Internet Protocol not Intellectual Property).

But just look at how universal VoIP has become over the last fifteen years despite all the early knocking and mumblings that it would, could, not ever work. When I first started talking about VoIP in the mid 1990s, after a visit to Vocaltec in Israel, I was even banned from a particular country as my views were considered seditious. Looking at the markets of 2007, I guess they may have been right! However, trying to hold back the inevitable is never a good reaction to a possibly disruptive technology though this is still occurring on a wide scale in today’s telecommunications world. [Picture credit: Enum.at]

Earlier this year I wrote about the challenges of what I called islands of isolation in a posting entitled Islands of communication or isolation?. I consider this to be one of the main challenges any new communications technology or service needs to face up to if it is going to achieve world-wide penetration. Sometimes just an accepted standard can tip a new technology into global acclaim. A good example of this is Wi-Fi or ADSL. Because of the nature of these technologies, equipment based on these standards can be used even by a single individual so a market can be grown from even a small installed base when it is reinforced by a multiplicity of vendors jumping on the bandwagon when they think the market is big enough.

However, many communication technologies or services require something more before they can become truly ubiquitous and VoIP is just one of those services. Of course many of these additional needs can be successfully bypassed by ‘putting up the proverbial finger’ to the existing approach by developing completely stand-alone services based on proprietary technologies as so successfully demonstrated by Skype in the VoIP world. The reason Skype become so successful at such an early stage was that the service was run independently of the existing circuit-switched Public Switched Telephone Network (PSTN). This was quite a deliberate and wholly successful strategy. What was the issue that Skype was trying to circumvent (putting their views of their perceived monopolistic characteristics of the telco industry to one side)? Telephone numbers.

Numbering was the one important feature that made the traditional telephone industry so successful. Unfortunately, it is also the lack of this one feature that has held back the rollout of VoIP services more than any other. The issue is that every user of a traditional telephone had their own unique telephone number (backed up by agreed standards drafted by the ITU). As long as you knew an individual’s number you could call them where ever they were located. In the case of VoIP, you may not be able to find out their address if they use a different VoIP operator to yourself leading to multiple islands of VoIP users who are unable to directly communicate with each other.

If the user chooses to use a VoIP-based telephone service they still expect to be able talk to anyone no matter what service provider they have chosen to use, whether that be another user of the VoIP service or a colleague not using VoIP but an ordinary telephone.

One of the key issues cluttering the path to achieving this is that VoIP runs on an IP network that uses a completely different way of identifying users than traditional PSTN or mobile networks. IP networks use an IP addresses as dictated by the IPv4 standard ( IPv6 to the rescue – eh? ) while public telephone networks use the E.164 standard as maintained by the ITU in Geneva. So if a VoIP user wants to make a call to an individual’s desk or mobile phone or vice versa a cross-network directory look up is needed before a physical connection can be made.

This is where the concept of Telephone Number Mapping (ENUM) comes into its own as one of the key elements required to achieve the vision of converged VoIP and PSTN services. The key goal of ENUM is to enable calls to be made between the two worlds of VoIP and PSTN as easy as between PSTN users. This must be achieved if VoIP services are are to become truly ubiquitous.

In reality no individual really cares whether a call is being completed on a VoIP network or not as long as the quality is adequate. They certainly do care about cost of a call and this turned out to be one of the main drivers causing the rise of VoIP services as they are used to bypass the tradition financial settlement regimes that exist in the PSTN world (Revector, detecting the dark side of VoIP).

How does ENUM work?

There are three aspects that need to be considered:

  1. How is an individual is identified on the IP network or Internet (an IP network can be a closed IP network used by a carrier where a guaranteed quality of service is implemented unlike the Internet).
  2. How the individual is identified on the PSTN network segment from an addressing or telephone number basis.
  3. How these two segments inter-work.

The IP network segment: We are all familiar with the concept of a URL or Uniform Resource Locator that is used to identify a web site. For example, the URL of this blog is http://technologyinside.com . In fact a URL is a subset of a Uniform Resource Identifier (URI) along with a Uniform Resource Name (URN). A URL refers to the domain e.g. a company name, while the URI operates at a finer granularity and can identify an individual within that company such as with an email address. For VoIP calls, as an individual is the recipient of a call rather than the company, URIs are used as the address. The same concept is used with SIP services as explained in sip, Sip, SIP – Gulp! The IETF standard that talks about E.164 and DNS mapping is RFC 2916.

URIs can be used to specify the destination device of a real-time session e.g.

  1. IM: sip: xxx@yyy.com (Windows Messenger uses SIP)
  2. Phone: sip: 1234 1234 1234@yyy.com; user=phone
  3. FAX: sip: 1234 1234 1235@yyy.com; user=fax

On the PSTN segment: A user is identified by their E.164 telephone number used by both fixed and mobile / cell phones. I guess there is no need to explain the format of these as they are an example of an ITU standard that is truly global!

Mapping of the IP and PSTN worlds:

There are two types of VoIP call. Those that are carried end-to-end on an IP network or other calls that start on a VoIP network but end on a PSTN network or vice versa. For the second type, call. mapping is required.

Mapping between the two worlds is in essence managed by an on-line directory that can be accessed by either party – the VoIP operator wishing to complete a call on a traditional telephone or a PSTN operator wishing complete a call on a VoIP network. These directories are maintained ENUM registrars. Individual user records therefore contain both the E.164 number AND the VoIP identifier for an individual.

The Registrar’s function to manage both the database and the security issues surrounding the maintenance of a public database i.e. only the individual or company (in the case of private dial plans) that are concerned with the record are able to change its contents.

The translation procedure: When a call between a VoIP user and a PSTN user is initiated, four steps are involved. Of course, the user must be ENUM-enabled by having an ENUM record with an ENUM registrar.

  1. The VoIP user’s software, or their company’s PBX i.e. their User Agent translates the E.164 number into ENUM format as described in RFC 3761.To convert an E.164 number to an ENUM the follows steps are required:
    1. +44 1050 6416 (The E.164 telephone number)
    2. 44105056416 (Removal of all characters except numbers)
    3. 61465050144 (Reversal of the number order)
    4. 6.1.4.6.5.0.5.1.3.4 (Insertion of dots between the numbers)
    5. 6.1.4.6.5.0.5.1.3.4.e164.arpa (Adding the global ENUM domain)
  2. A request is sent to the Domain Number Service (DNS) to look up the ENUM domain requested.
  3. A query in a format specified by RFC 3403 is sent to the ENUM registrar’s domain which either returns the PSTN number or the URI number of the caller – whichever is requested.
  4. The call is now initiated and completed.

For this process to work universally then every user that uses both VoIP and PSTN services need to have an ENUM record. That is a problem today as it is just not the case.

ENUM Registrars

In a number of countries top-level public ENUM registrars have been set up driven by the ITU. For example this is the ENUM registrar in Austria – http://www.enum.at They then hold the DNS pointers to other ENUM registrars in Austria. Another example is Ireland’s ENUM registry.

However, in the USA, ENUM services are in the hands of private registrars.

If you sign up for a VoIP service that provides you with an E.164 telephone number, your VoIP provider will act as a registrar and hence your details will be automatically registered for look-up through a DNS call. If you do not use one of these services, it is possible to register yourself with an independent registrar.

Local Number Portability (LNP)

During the early days of VoIP services, many ENUM registrars were operated by 3rd party clearing houses acting on a federated basis who were quick to jump on an unaddressed need. Of course, these registrars charge for look-up services. Other third party companies offer provide “trusted and neutral” number database services such as Neustar, e164 and Nominum in the USA who not only offer ENUM services but also Local Number Portability services. To quote Neustar:

“LNP is the ability of a phone service customer in North America to retain their local phone number and access to advanced calling features when they switch their local phone service to another local service provider. LNP helps ensure successful local telephone competition, since without LNP, subscribers might be unwilling to switch service providers.”

However, as we start to see more and more VoIP service providers and more and more traditional voice carriers offering VoIP service to their customers we will see more carriers offering ENUM numbering capabilities. Moreover, They could also use ENUM technology to help reduce costs of the need to support Local Number Portability by managing translation / mapping databases themselves rather than paying a 3rd party for the capability. To quote an article in Telephony Online:

Not all service providers are rushing to do their own ENUM implementations, said Lynda Starr, a senior analyst with Frost & Sullivan who specializes in IP communications. “Some say it’s not worth doing yet because VoIP traffic is still small.” Eventually, however, Starr estimates that service providers could save about 20% of the cost of a call by implementing ENUM – even more if they exchange traffic with one another as peers.

An ITU committee is being planned by the ITU to look at service-provider hosted ENUM databases but the view is that it will be slow to be implemented as is usually the case with ITU standards.

Round up

If every PSTN network had an ENUM-compliant gateway and database, then truly converged voice services could be created and user’s preferences concerning on which device they would like to take calls could be accommodated. Today, as far as I am aware, even the neutral 3rd party ENUM registrars do not currently share their records with other parties, further exacerbating the numbering islands issue. This means you need to know which Registrar to go to before a call can be set up.

It is early days yet but we will undoubtedly start to see more and more carriers implementing ENUM capabilities rather than some of the proprietary number translation solutions that started with the concept of Intelligent Networks in the 1980s. In the mean time the industry will carry on in a sub-optimal way hoping beyond hope that something will happen to sort it all out soon. The real issue is that ENUM registries are the keystone capability needed to make VoIP services globally ubiquitous but they can hardly be considered a major opportunity to make money on a standalone basis. Rather they are an embedded capability in VoIP or PSTN service providers or neutral Internet exchanges so there is little incentive to pour vast amounts of money into the capability which will lead to continuing snail-like growth.

As is the case with standards, even though most would agree that using E.164 numbering is the way forward, there is another proposal called SRV or service record that proposes to use email addresses as the denomination rather than telephone numbers. The logic of this is that it would be driven by by IT directors riding on the back of disappearing PBXs and who are swapping over to Asterisk open-software systems. That is a story for another time however.

Addendum #1: sip, Sip, SIP – Gulp!


How to Be a Disruptor

September 11, 2007

An excellent article from Sandhill.com on running a software business along disruptive lines. Written by the CEO of MySQL, it looks like it needs a lot of traditional common sense!

These are the key issues  he talks about:

Follow No Model
Get Rich Slow
Make Adoption Easy
Run a Distributed Workforce
Foster a Culture of Experimentation
Develop Openly
Leverage the Ecosystem
Make Everyone Listen to Customers
Run Sales as a Science
Fraternize with the Enemy

Take a read: How to Be a Disruptor


WAP, GPRS, HSDPA on the move!

September 4, 2007

Over the last few months I have written many posts about Internet technologies but they have been pretty much focussed on terrestrial rather than wireless networks (other than dabbling in Wi-Fi with my overview of The Cloud. – The Cloud hotspotting the planet). This exercise was rather interesting as I needed to go back to the beginning and look at how the technologies evolved starting with The demise of ATM.

Back in 1994 a colleague of mine, Gavin Thomas, wrote about Mobile Data protocols and it’s interesting to glance back to see how ‘crude’ mobile data services were at the time. Of course, you would expect that to be the case as GSM Digital Cellular Radio was a pretty new concept at the time as well. In that 1993 post I ended with the statement that “GSM has a bright future”. Maybe it should have read ” the future is Orange”! No one foresaw in those days the up and coming explosive growth of GSM and mobile phone usage. Certainly n one predicted the surge in use of SMS.

Acronym hell has extended itself to mobile services over the last few years and the market has become littered with three, four and even five letter acronyms. In particular, wireless Internet started with a three letter acronym back in the late 1990s – WAP (Wireless Access Protocol), progressing through a four letter acronym, GPRS (General Packet Radio Service) and Enhanced Data GSM Environment (EDGE) and is now moving to a five letter broadband 3G acronym – HSDPA (High-Speed Downlink Packet Access). Phew!

The history of mobile data services has been littered with undelivered hype over the years that still lives on today. However, that hype led to the development of services that really do work unlike some of the early initiatives like WAP.

Ah, WAP, now that was interesting. I would probably put this at the top of my list of over-hyped protocols of all time. At least when ATM was hyped this only took place within the telecommunications community whereas WAP was hyped to the world’s consumers which created much more visibility of ‘egg on the face’ for mobile operators and manufacturers.

So what was WAP?

In the late 1990s the world was agog with the Internet which was accessed using personal computers via LANs or dial-up modems. There was clearly an opportunity (whether it was right or wrong) to bring the ‘Internet’ to the mobile or cell phone. I have put quotation marks around the Internet as the mobile industry has never seen the Internet in the same light as PC users – more on this later.

The WAP initiative was aimed at achieving this goal and at least it can be credited with a concept that lives on to this day - Mobile Internet. Data facilities on mobile phones were really quite crude at the time. Displays were monochrome with a very limited resolution. Moreover, the data rates that were achievable at the time over the air were really very low so this necessitated WAP content standards to take this into account.

There were several aspects that needed standardising under the WAP banner:

  • Transmission protocols. WAP defined how packets were handled on a 2G wireless network and consisted of wireless versions TCP and UDP as seen on the Internet and also used WTP (Wireless transaction protocol) to control communications between the mobile phone and the base station. WTP itself contained an error correction capability to better help cope with unreliable wire bearer.
  • Mobile HTML: It was immediately recognised that due to the limited screen size and the low data rates achievable on a mobile phone a very simplified version of HTML was required for use with mobile web sites. This led to the development of WML (Wireless Markup Language). This was a a VERY cut down version of HTML with very little capability and any graphic used being tiny as well. Towards the end of the 90s WAP 2.0 was defined which improved things somewhat and was based on a cut down of XHTML.

WAP clearly did not live up to its promise of a mobile version of the Internet with it’s crude and constrained user interface, high latency, the need to struggle with arcane menu structures (has anything changed here in ten years?) and to access services using exceedingly slow data rates experienced on the mobile networks of the day.

However, this did not stop mobile service operators from over hyping WAP services with endless hoarding and TV adverts extolling Internet access from mobiles. At one time it looked as if mobile operator advertising departments never talked to their engineering departments and were living in a world of their own that bore little relation to reality.

It all had to crash and it did along with the ‘Internet bubble’ in 2001. Many mobile operators sold their WAP service as an ‘open’ service similar to the Internet. In reality, they were closed garden services that forced users to visit their company portal as their first port of call making it well nigh impossible for small application developers to get their services in front of users. One could ask how much this has changed by 2007?

I should not forget to also mention that the cost of using WAP services was very high based as it was on bits transmitted. This led to shockingly high bills and low usage and provided one of the great motivators behind the ‘unforeseen’ growth of SMS services.

I believe that much of this still lives on in the conscious and unconscious memory of consumers and held back major usage of mobile data services for many years.

Along comes the ‘always-on’ GPRS service

After licking the WAP wounds for several years, it was clearly recognised that something better was required if data services were take off for mobile operators. One of the big issues for WAP were the poor data transmission speeds achieved so GPRS (General Packet Radio Service) was born.

GPRS is an IPv4-based packet switched based protocol where data users share the same data channel in a cell. Increased data rates in GPRS derives from the knitting together of multiple TDMA time slots where each individual GSM time slot can manage between 9.6 to 21.4 Kbps. Linking together slots can deliver greater than 40kbit/s ( up to 80kbit/s) depending on the configuration implemented.

GPRS users are connected all the time and have access to the maximum upstream bandwidth available if no other users in their cell are recieving data at the same time.

The improved data rate (that is in the range of an old dial-up modem) and improved reliability experienced when using GPRS has definitely led to a wider use of data services on the internet. Incidentally, a shared packet service should mean lowered cost but as users are still billed on a kilobits transmitted basis, GPRS bills are still shockingly high if the service is used a lot.

GPRS services are so reliable that there is wide spread availability of GPRS routers as shown in the picture above (Linksys) which are often used for LAN back up capabilities.

GPRS was definitely a step in the right direction.

Gaining an EDGE

EDGE (Enhanced Data rates for GSM Evolution) is an upgrade to GPRS that has gained some popularity in the USA and Europe and is known as a 2.5G service (although it is derives from 3G standards).

EDGE can be deployed by any carrier who offers GPRS services and represents an upgrade to GPRS by requiring a swap-out to an EDGE compatible transceiver and base station subsystem.

By using an 8PSK (8 phase shift keying) modulation scheme on each time slot it’s possible to increase data rates within a single time slot to 48kbit/s. Thus, in theory, it would be be possible, by combining all 8 times slots, to deliver an aggregate 384kbit/s data service. In practice this would not be possible as there would be no spare bandwidth available for voice services!

All in all EDGE achieves what it set out to achieve – higher data rates without an upgrade to full 3G capability and has been widely deployed.

The promise of the HSDA family

Following on from WAP, GPRS and EDGE have been the dominant protocols used for mobile data access for a number of years now. Achieved data rates are still slow by ADSL standards and this has put off many users after they have played with them for a bit.

With the tens of billions of $ spent on 3G licences at the end of the last century one would have imagined that we all would have access to megabit data rates on our mobile or cell phones by now, but that has just not been the case. 3G has been slow to be deployed and presented many operational issues that needed be resolved.

The Universal Mobile Telecommunications System (UMTS) known as 3GSM uses W-CDMA spread spectrum technology as its air interface and delivers its data services under the standards known as HSDPA (High-Speed Downlink Packet Access) and HSUPA (High-Speed Uplink Packet Access) known collectively as HSDA (High-Speed Data Access).

Unlike the TDMA technology used in GSM, W-CDMA is a spread spectrum technology where all users transmit ‘on the top’ of each other over a wide spectrum, in this case 5MHz radio channels. The equipment identifies individual users in the aggregate stream of data through the use of unique user codes] that can be detected. (I explained how spread spectrum radio works in 1992 in Spread Spectrum Radio). The use of this air interface adopted makes a 3G service incompatible with GSM.

In theory, W-CDMA is able to support data rates up to 14mbit/s but in reality offered rates are in the 384Kbit/s to 3.6Mbit/s and is delivered using a dedicated down link channel called the HS-DSCH, (High-Speed Downlink Shared Channel) which allows higher bit rate transmission than ordinary channels. Control functions are carried on sister channels. The HS-DSCH channel is shared between all users in a cell so in practice it would not be possible to deliver the ceiling data rate to any more than a single subscriber which makes me wonder how the industry is going to support lots of mobile TV users on a single cell? More on this issue in a future post.

Standardisation of HSDPA is carried out by the 3rd Generation Partnership Project (3GPP).

Inevitably, because of the ultra slow roll out of UMTS 3G networks, HSDPA will take a long time to get to your front door although this is happening is quite a few countries. Here in the UK, the 3 network is currently launching (August 2007) its HSDPA data service which will be followed by a HSUPA capability at a later date. Initially it will only offer HSDPA data cards for PCs.

Interestingly, The Register reports that 3 will offer 2.8Mbit/s and the the tariff will start at £10 Sterling a month for the Broadband Lite service providing 1Gbytes of data rising to £25 for 7Gbytes with the Broadband Max service.

You can pre-order a broadband modem now as shown on the right.

Incidentally, Vodafone’s UK HSDPA service can be found here and their 7.2Mbit/s service here.

The future is LTE

Another project within 3GPP is the Long Term Evolution (LTE) activity as a part of Release 8. The core focus of the LTE team is, as you would expect, on increasing available bandwidths but there are a number of other concerns they are working on.

  • Reduction of latency: Latency is not an issue for streamed services but is a prime concern for interactive services. There is no point post-WAP launching advanced interactive services if users have to wait around like in the early days of the Internet. Users have been there before.
  • Cost reduction: This is pretty self evident but the activity is focussed on reducing operator’s deployment costs not reducing consumer charge rates!
  • QoS capability: The ubiquitous need for policy and QoS capability and I’ve explored in depth on fixed networks.

The System Architecture Evolution (SAE) is another project that is running in parallel with but behind the LTE. It comes as little surprise that the SAE is looking at creating a flat all-IP network core which will (supposedly) be the key mechanism by which operators will reduce their operating costs. This still debatable to my mind.

Details of this new architecture can be found under the auspices of the Telecoms & Internet Services & Protocols for Advanced Neworks or TISPAN (a six letter acronym!) which is a joint activity between ETSI and 3GPP. To quote from the web site:

Building upon the work already done by 3GPP in creating the SIP-based IMS (IP Multimedia Subsystem), TISPAN and 3GPP are now working together to define a harmonized IMS-centric core for both wireless and wireline networks.

This harmonized ALL IP network has the potential to provide a completely new telecom business model for both fixed and mobile network operators. Access independent IMS will be a key enabler for fixed/mobile convergence, reducing network installation and maintenance costs, and allowing new services to be rapidly developed and deployed to satisfy new market demands.

Based as it is on IMS (which I wrote about in IP Multimedia Subsystem or bust!) this could turn out to be a project and a half. Saying that the “devil is in the detail” would seem to be a bit of an understatement when considering TISPAN.

A recent informative PowerPoint presentation about the benefits of NGN, convergence and TISPAN an be found here.

Roundup

We seem to have come a long way since the early days of WAP with HSDA now starting to deliver the speed of fixed line ADSL to the mobile world. Transfer rates are indeed important but high latency can be every bit as frustrating when using interactive services so it is important to focus on its reduction. The challenge with 3G is its limited coverage and this could cause slowness of uptake – as long as flat rate access charges are the norm and NOT per megabit charging as we have seen in the past. And boy, I bet the inter-operator roaming charges will be high!

However, bandwidth and service accessibility is not the only issue that needs addressing for the mobile Internet market to sky rocket. The platform itself is still a fundamental challenge, limited screen size and arcane menus to name but two. The challenge of writing of applications that are able to run on the majority of phones is definitely one the other major issues (I touched on this in Mobile apps: Java just doesn’t cut the mustard?).

I reviewed a book earlier this year entitled Mobile Web 2.0! that talks extensively about the walled-garden and protectionist attitudes still exhibited by many of the mobile operators. This has to change and there are definite signs that this is beginning to happen with fully open Internet access now being offered by the more enlightened operators.

Maybe, just maybe, if it all comes together over the next decade then the prediction in the above book “The mobile phone network is the computer. Of course, when we say ‘phone network’ we do not mean the ‘Mobile operator network. Rather we mean an open, Web driven application…” could just come about.


Follow

Get every new post delivered to your Inbox.