computer cables routing
Author Image

By: Aivis Olsteins

In News

2018-04-18

Least Cost Routing explained

Least Cost Routing or LCR is integral part of any Telecoms system, including VoIP and SMS. Here is how it works.

Longest Prefix Match

Typically call routing in Telecoms, including VoIP is done based on the longest prefix match basis. That means if there are several prefixes matching number, the longest one will be the right match. Let's take an example this routing table:

(table1)

Destination Code Name
1 US / Canada
1212 US – New York
44 UK
447 UK Mobile
447766 UK Mobile Vodafone

 

If the call is made to number 12127773456, it is designated to New York, because it matches both US/Canada code 1 and New York prefix 1212. However, the length of New York prefix 1212 is longer (4 digits) than US/Canada code 1 (1 digit), so New York takes precedence. If the call is made to number 13215551200, it is designated to general US/Canada breakout because the above table does not include specific breakout for Florida (which is 1321).

The call to 44712345678 will be similarly designaed to UK Mobile, whereas call to 44776612345 with be UK Mobile Vodafone because it matches prefix 447766.

Route Cost

Each destination has its cost. Lets add a cost column to the example table:

(table2)

Destination Code Name Cost (units)
1 US / Canada 5
1212 US – New York 6
44 UK 20
447 UK Mobile 35
447766 UK Mobile Vodafone 30

 

Therefore call to New York will cost 6 units, whereas to any other US/Canada destination starting with 1 it will be 5 units.

More than one choice

There can be more than one provider of any given destination, and the cost of these providers might vary. Lets add cost columns for more route providers:

(table3)

Destination Code Name Cost Provider 1 Cost Provider 2 Cost Provider 3
1 US / Canada 5 5 6
1212 US – New York 6 5 6
44 UK 20 25 N/A
447 UK Mobile 35 N/A 30
447766 UK Mobile Tele2 30 N/A 30

 

Above example shows 3 different priced routes to US and NY, and some routes to UK. Note, that not all providers can offer all routes. In the example above provider 2 does not offer UK Mobile at all (incl. Vodafone), and provider 3 does not provide UK routes except mobiles.

Least Cost Routing

Least Cost Routing (LCR) is method of finding the cheapest route for the given destination based on several available routes and the costs associated with these routes. The tables as above are used to determine the cheapest routes to the specific destination. Note, that there can be specific maximum prices. For example, user may be willing to pay maximum 5 units for calls to US/Canada. Therefore Provider 3 is out of routing because its cost is 6.

Since the real life code tables are far larger than example (can have 20-50k rows), the problem of finding cheapest route becomes more complex.

Code Range Normalization

Additionally, there is the problem of so called normalization. Not all providers have exactly same breakouts. Lets see 2 table below:

 

Provider 1

(table4)

Destination Code Name Cost Route 1
44 UK 20
447 UK Mobile 30
449 UK Premium 100

 

Provider 2

(table 5)

Destination Code Name Cost Route 1
44 UK 25
449 UK Mobile 35

 

As you see, Provider 1 will ask price of 100 units for all calls going to UK Premium service numbers starting with 449, whereas Provider 2 will obviously ask only 25 because it does not have specific prefix, and call fill fall into general 44 range.

 

In real life the differences are very frequent and must be addressed when building a LCR system.

To summarize, LCR system needs to be able to provide following functions:

  • To have up-to-date routing and cost information and be able to serve in real time;
  • Respect longest prefix match requirement;
  • Respect maximum allowed price requirement;
  • To be able to return least cost choices in the order of increasing costs, i.e. from cheapest to most expensive;
  • To take care of code range normalization, i.e. differences between code breakouts from various providers.

 

 

 

 

 

 

Leave a comment
About Author
Author Image

My name is Aivis Olsteins and I am owner of DataTechLabs. My experience in Telecoms started in early 1990's and I have worked in multiple technical positions in mobile, messaging and data networks. My expertise lies in telecom networks, database systems, distributed processing and large data analysis. These posts are my attempt to share my knowledge with everyone who might find it useful.

Get in Touch

If you have something to say, please use the contact form below to get in touch with us. We will get back to you as soon as possible.

Mail Us

DataTechLabs SIA, Muzikas str 12A
Jurmala, LV-2008, Latvia.

Call Us

+371 67 66 09 01
+ 1 202 499 1550

E-mail Us

info@datatechlabs.com
support@datatechlabs.com