Linux and Open Source in Telecommunications
This article examines the impact that Linux and open-source software are having on the telecommunication industry, technology trends moving toward open and standards-based platforms and the .orgs that are active in promoting carrier grade base platforms. Furthermore, this article focuses on the Carrier Grade Linux initiative at OSDL and discusses its contributions to this growing ecosystem.
The telecommunication industry is facing several challenges:
Telecom service providers are looking to reduce their costs using commodity software and commercial off-the-shelf (COTS) hardware building blocks.
Telecom service providers require seamless integration of COTS carrier grade components; the integrated solution must be validated for carrier grade availability.
The growth of packet traffic is putting pressure on communication networks originally designed for “store and forward”; platforms in an all-IP environment that maintain carrier-class characteristics are delivering increasing levels of availability and dependability.
Operators want to decrease time to market and increase the capability for fast delivery of new services by shortening new service development time and unifying platforms.
Of course, operators want to roll out the above capabilities while still making money and increasing profits.
Linux and open-source software provide a compelling avenue to operator success. The open-source operating system has certain characteristics that confer upon it advantages over other operating systems; indeed, Linux has been a disruptive technology with clear impact in telecommunications. Today, not only do many of the server nodes with telecom networks run Linux, but Linux also powers mobile phones and many intermediate nodes “in the middle”.
So, what is a disruptive technology, and how does it impact an industry?
Disruptive technologies first appear saddled with significant deficiencies and are usually targeted at niche segments. Disruptive technologies, however, also provide significant cost benefits. For example, a truly disruptive technology may offer only half the performance of its legacy competitor but can be delivered at one-tenth the cost.
Disruptive technologies are most often taken up by early adopters and then experience a much slower adoption into the mainstream. The adoption of a disruptive technology always starts with non-mission-critical applications (such as utility computing) and moves to mission-critical application as it matures (such as business-critical and enterprise core applications). Linux adoption followed this pattern, starting out hosting Web servers, e-mail and FTP servers and moving now to mission-critical applications, such as telephony. With increasing adoption, a disruptive technology, such as Linux, provides an opportunity (or even forces) companies to re-evaluate and also re-invent their business models and identify real value-added products and services. Companies that do not provide clear value quickly find themselves out of the market.
Linux adoption in telecommunication has not only been increasing, but adoption is also accelerating. Reasons to adopt Linux vary but revolve around common key advantages, such as licensing terms, full access to source code, freedom to choose from multiple providers, lower costs versus legacy and proprietary operating systems, higher system performance, reliability, security, source code quality, innovation rate, peer review, testing resources and the availability of an established ecosystem.
The traditional telecommunication business model is one of high-margin and high-revenue business. In the past, telecom experienced better than 10% year-on-year growth, and almost any project could become successful because demand was so great. Telecommunication companies bought in and sold on proprietary solutions, taking a margin on top of the initial licensing costs. Standards were sufficient only to ensure basic connectivity; after that, essentially proprietary models were built up, with vendor lock-in as the norm.
Figure 1 illustrates the state of the telecom business beginning in the mid-1980s up to the present. In the 1980s, the carrier's business was monopoly-based with very few players in the field, which provided carriers the opportunity to make a lot of money, due to significant margins with voice telephony as a high-priced premium service. In the mid-1990s, new players (carriers/operators) entered the business, increasing the competition. However, voice telephony was still a premium service, and although prices were falling, operators still had significant margins. Today, the business looks very different. It is shrinking with many more players in the space, increased competition and much diminished profits. Voice telephony is a commodity. Furthermore, the industry faces additional threats, such as VoIP and broadband telephony. How can they beat free or close-to-free calling?
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- Designing Electronics with Linux
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- Using Salt Stack and Vagrant for Drupal Development
- Reply to comment | Linux Journal
2 hours 25 min ago - Dynamic DNS
2 hours 59 min ago - Reply to comment | Linux Journal
3 hours 58 min ago - Reply to comment | Linux Journal
4 hours 48 min ago - Not free anymore
8 hours 50 min ago - Great
12 hours 37 min ago - Reply to comment | Linux Journal
12 hours 45 min ago - Understanding the Linux Kernel
15 hours 18 sec ago - General
17 hours 30 min ago - Kernel Problem
1 day 3 hours ago





Comments
jackz
Barack Obama Biography