What is a Network Model ?

1. Introduction

To understand how networkings works, we need to make sure we understand how people communicate together. Let’s start with something simple: humans need a common language to communicate. For example, imagine someone who only speaks English trying to talk to someone who only speaks Chinese.

Illustration showing what is a network model using human language analogy between English and Chinese
Figure 1 – Communication Without a Shared Language

Without a shared language, they simply won’t understand each other. Networking devices work the same way! Without a common communication model, devices from different vendors can’t understand one another. That’s exactly the problem a network model solves.

So, what is a network model ?

A network model is a standardized structure that allows devices from any brand or vendor to communicate. It acts like a universal language that all devices can understand. Without this common language, each device would “speak” its own language, making communication between different brands impossible.

But this structure alone isn’t enough; it needs rules to function. That’s where protocols come in.

2. What Is a Protocol?

A protocol is a set of rules defining how data should be communicated between devices in a network. You can think of it as a language for computers. If two devices use different protocols, they won’t understand each other, just like two humans who don’t share a common language.

There are many types of protocols, each with its own role. For example:

  • Some handle IP addressing (like IP).
  • Others manage data delivery (like TCP).
  • Others handle file transfer (like FTP).

How do we make all these protocols work together? The network model provides a layered structure to organize protocols. Each layer is responsible for a specific part of the communication process, using specific protocols to get the job done.

In short:

  • Protocols do the work.
  • The model tells them where and how to work.

3. Early Networking Challenges

Imagine yourself in 1980, no Iphone created, no fiber optic, no instagram, nothing, the first laptop are just created!

At that time, the biggest companies in the technology sector were IBM and DEC,

In the early days of networking major computer manufacturers such as IBM and DEC and smaller manufacturers developed their own proprietary models.

Diagram showing vendor-specific systems in the 1980s before standardized models, explaining what is a network model
Figure 2 – Proprietary Communication in the 1980s

As you can see above, proprietary models are created for each manufacturer of network devices. These models are used to design their own communication languages.

The main problem with these proprietary model was that they allowed communication only between devices from the same vendor.

This means that devices from one vendor couldn’t communicate with those from another because each used a unique set of rules.

The problem in 1980s

Imagine buying networking equipment from IBM and later you decide to add a new device from another vendor like DEC. These devices just couldn’t talk to each other, just like someone who speaks only English trying to chat with someone who only speaks Chinese.

IBM and DEC devices in the 1980s failing to communicate, illustrating what is a network model through language barrier analogy
Figure 3 – Communication Breakdown Between Vendors in the 1980s

Without a common language, communication was impossible !

This proprietary model makes it hard for devices to communicate with each other.

This made communication very difficult in 1980…

Challenges of Proprietary Models

  1. Compatibility Problems
    Devices will only be able to communicate with the same manufacturer.
  2. Vendor Dependence
    Companies were forced to stick with one vendor’s equipment, making upgrades expensive and complicated.
  3. Added Complexity
    Special solutions were needed to connect devices from different vendors, which made networks harder to manage.
  4. Limited Growth
    Expanding networks was difficult and costly because they had to be redesigned for every change.

The Consequences

To solve these problems, the need for a vendor-neutral approach emerged. A standardized way of communication was required so devices regardless of who made them could communicate together.
This opened the door to a shared understanding of what is a network model across the entire industry.

4. Transition to Standardized Models

To overcome the limitations of proprietary systems, a universal model for communication was introduced.
This shift helped define what is a network model in practical terms, leading to the adoption of standards like OSI and TCP/IP.

The Rise of TCP/IP

The TCP/IP model was first developed in the 1970s as a set of protocols to standardize communication between devices. By the 1990s, it began to gain widespread adoption, replacing proprietary models that had dominated the early networking era.

In the 1990s, TCP/IP acted as a common protocol to allow DEC, IBM, and other vendors to communicate across networks
Figure 4 – The Rise of TCP/IP in the 1990s

Its open design allowed networks to grow and interconnect without being tied to specific vendors.

5. The Internet Era (2000s and Beyond)

By the 2000s, TCP/IP had become the dominant model for networking, connecting billions of devices worldwide.

Evolution from vendor-specific models to TCP/IP as the standard in networking, explaining what is a network model
Figure 5 – The Internet Era (2000s and Beyond)

Now that you understand how the Internet needed a standardized model to enable devices from different vendors to communicate.

Have you ever wondered how your laptop can access a website like pingmynetwork.com ?

How does this communication happen, step by step?

In the next course, we’ll explore the OSI Model which will give you a complete answer to the question: what is a network model and how does it work, layer by layer.

Follow me !