Service Convergence: Multiple Services, One Interface

Think back just a couple of decades. Your telephone was plugged into a wall jack. Your television received its signal from an antenna or a separate cable. Your computer connected to the internet, often through that same phone line, but you could not make a call and surf the web at the same time. Each service-voice, video, and data-had its own separate, dedicated pipeline. Today, you probably watch high-definition movies on the same Wi-Fi network that carries your video calls, your online gaming, and your constant stream of emails. This massive shift is the magic of service convergence: the ability to deliver multiple, distinct services through a single, common interface and network.

The big dream: one pipe for everything 🔗

The core idea behind all this change is the move to a common infrastructure. In the old model, which engineers sometimes call a “vertical” structure, every service had its own network. The telephone company ran its voice network, the cable company ran its video network, and data networks were yet another separate world. This was incredibly inefficient. It meant laying different cables, maintaining different switches, and employing different teams of technicians for each service. For the customer, it meant multiple bills, multiple installation appointments, and a tangle of wires.

The goal of convergence was to change this from a vertical to a “horizontal” structure. The new dream was to build one single, powerful, high-capacity “pipe”-a common infrastructure-that could carry everything. Instead of treating voice, video, and data as fundamentally different things, the network would just see them all as digital information, or “packets.” This single-pipe approach, providers believed, would lead to massive cost savings, incredible efficiency, and a new world of simplified, bundled services for customers. This consolidation is the essence of a converged network, which merges data transmission, internet protocol (IP) communication, and traditional phone services onto one unified platform.

Service convergence in your daily life 🔗

This is not just a technical theory; you are living in the world that service convergence built. The lines between what a “phone company” or a “cable company” does have been almost completely erased. What was once a clear separation of services is now a blurry, bundled marketplace. These real-world examples show just how deeply this concept is integrated into our lives.

When your internet is your phone 🔗

The most classic example is Internet Telephony, also known as Voice over IP (VoIP). Services like Zoom, Skype, Google Meet, and even WhatsApp calls do not use the traditional, circuit-switched phone network. Instead, they convert your voice into digital data packets and send them over the public internet, just like any other piece of data. This is a prime case of a service (voice) that was once separate, now “converging” onto the data network. Similarly, the ability to get your corporate email on your mobile phone was a revolutionary step. It merged the data-centric world of the internet (email) with the voice-centric world of the cellular network.

When your TV is your computer 🔗

The convergence story is just as dramatic in our living rooms. Many people now get web access via their TV cables. Your cable provider, who once only delivered broadcast video, now offers high-speed internet and digital phone service through that very same coaxial cable. This “triple play” bundle (internet, TV, and phone) is a perfect, everyday example of service convergence. The cable network is no longer just a “video pipe”; it is a common infrastructure. The reverse is also true: we now see telephone services delivered via cable TV networks, and we use our data networks (Wi-Fi) to stream Netflix and YouTube to our smart TVs, effectively turning our data network into a video network.

A place for everything: how B-ISDN tried to sort the services 🔗

Long before our current internet could handle all this, engineers were trying to figure out how to build this “one pipe” future. The challenge was obvious: sending a simple text email is not the same as making a real-time phone call. A streaming movie has completely different needs than a still image. If all these services were to share the same pipe, the network needed a way to understand and prioritize them. This is where a framework called the Broadband Integrated Services Digital Network (B-ISDN) came in.

B-ISDN was an ambitious set of standards from the 1980s and 90s designed to be the high-speed, all-in-one digital network of the future. Its first job was to stop thinking about services in the old way (like “telephone service”) and start categorizing them by their technical characteristics. The idea was that if you could classify a service, you could tell the network how to treat it. B-ISDN generically categorized services into two main families, each with sub-categories:

1. Interactive services 🔗

These are services where there is a two-way flow of information. You are both sending and receiving, or you are actively requesting information.

• Conversational Services: This is real-time, two-way communication. Think of motion video (like a video conference) or audio (like a phone call). The data has to flow smoothly and quickly in both directions, because delays (latency) would make the conversation impossible.
• Messaging Services: This is a store-and-forward model. Think of email. You send a message (which could contain text or even still video/images), the network stores it, and then delivers it when the recipient is ready. It is not time-sensitive in the same way a call is.
• Retrieval Services: This is when you request information from a central source, like a server. You (the user) are pulling data. This could be browsing a database full of computer graphics, or an early concept of video-on-demand.

2. Distribution services 🔗

These services are primarily one-way, flowing from a provider to many users. Think of traditional broadcasting.

• Distribution without User Control: This is classic broadcast TV. The provider sends out the signal (like a motion video stream), and everyone receives the same thing at the same time. You can change the channel, but you cannot pause, rewind, or choose what to watch.
• Distribution with User Control: This was a more advanced idea. Here, the information is broadcast in a continuous cycle, and the user’s device could “grab” the parts it wanted. Imagine an electronic newspaper where you could select which articles to view as they cycled by.

By classifying all services this way, B-ISDN created a blueprint. It established that any future common infrastructure would have to manage services with vastly different digital capacity needs-from a tiny text file to a massive, high-definition video stream-all at the same time.

ATM: the “magic adapter” for all services 🔗

So B-ISDN gave engineers the *what*-a plan for classifying services. But they still needed the *how*. How do you physically build a network that can handle a time-sensitive voice call and a low-priority data file on the same wire? The answer was a groundbreaking technology called Asynchronous Transfer Mode (ATM).

ATM was the architecture chosen as the backbone for B-ISDN. Its core concept was brilliantly simple. Instead of dealing with data “packets” of all different sizes, like the internet does, ATM chops *everything* up into tiny, fixed-size “cells.” Each cell is 53 bytes long (a 5-byte header for addressing and a 48-byte payload for the actual data).

Think of it like a highway. Instead of letting giant 18-wheeler trucks (video files) and tiny motorcycles (text data) all try to merge at different speeds, ATM forces every vehicle to be a small, uniform-sized pod. These pods can be packed onto the highway incredibly efficiently, one after another, in a predictable stream. A voice call might get one pod every few milliseconds. A video stream might get hundreds of pods every millisecond. The network just sees a constant, “asynchronous” stream of cells, not a chaotic jumble of different services.

The all-important convergence sub-layer 🔗

But how does a video stream or a voice call *get* turned into those little 53-byte cells? This is where the real genius of the architecture lies, in a component called the ATM Adaptation Layer (AAL). The AAL’s job is to be the “adapter” between the different services and the uniform ATM network. The most critical part of this layer is the Convergence Sub-layer (CS).

As the name suggests, this is where the “convergence” truly happens. The Convergence Sub-layer takes the raw data from a specific service-like a stream of audio or a large data file-and “packages” it for transport. It prepares the data to be chopped up by the next layer (the Segmentation and Reassembly sub-layer) into those 48-byte payloads.

Crucially, there were different types of Convergence Sub-layers for different B-ISDN services. One type was designed for constant, real-time services like voice. Another was designed for variable, “bursty” services like data files. This sub-layer is what made it possible for the ATM network to multiplex, or combine, all these different services and carry them seamlessly over the underlying fiber optic network. It was the universal translator that allowed voice, video, and data to all speak the same basic language of “cells.”

While B-ISDN and ATM themselves were eventually overtaken by the sheer flexibility and low cost of the modern IP-based internet, their core principles are alive and well. The concepts they pioneered-classifying services, managing quality, and the need for a layer to “converge” different data types onto a single network-are the fundamental building blocks of the digital world you use every single day.

What do you think? As we move toward even faster 5G and fiber networks, what do you think the next great “converged” service will be? Do you see a future where the few remaining separate services (like car navigation and home internet) finally merge into one?

References

1. https://www.itu.int/en/wcit-12/documents/wcit-background-brief3.pdf
2. https://www.ruckusnetworks.com/insights/what-is-a-converged-network/
3. https://en.wikipedia.org/wiki/Network_convergence
4. https://www.tutorialspoint.com/what-is-bisdn-in-computer-network
5. https://www.egyankosh.ac.in/bitstream/123456789/12371/1/Unit-4.pdf