Computer Network & Network Security System — Introduction to Computer Networks and Physical Layer, NEC licence examination syllabus (Nepal Engineering Council).
Here's the honest truth before we dive in: nobody actually builds networks exactly like this. So why do we still learn it?
The OSI (Open Systems Interconnection) model isn't a real implementation — it's a teaching and design framework. It breaks the impossibly complex job of "send data from one computer to another, anywhere on Earth" into 7 manageable layers, where each layer only has to worry about its own small job and trust the layer below it to handle the rest.
This is exactly how a company works. The CEO doesn't personally deliver packages — they trust the logistics department, who trusts the delivery driver, who trusts the vehicle. Each layer/person does ONE job and hands off to the next. If the delivery driver's job changes (say, from van to drone), nobody else in the company needs to change how they work — that's the entire point of "layering."Working bottom-up, here's what each layer's actual JOB is, in plain terms:
WhatPushes raw bits (0s and 1s) as electrical signals, light, or radio waves onto the actual wire/air.
WhereThe actual cable, connector pins, or radio antenna doing the sending.
WhyEverything above this layer is just numbers and logic — SOMETHING has to turn that into real electricity/light/waves, and this is it.
ProtocolsMostly hardware standards, not "protocols" in the usual sense — e.g. RS-232, USB, DSL, Bluetooth radio specs, Ethernet's physical-layer standards (10BASE-T etc).
CalledAt this layer, data is just a raw stream of bits — no structure, no address, nothing. It's the lowest possible level.
WhatGroups raw bits into frames, and manages communication between two directly-connected devices — including error detection and MAC addressing.
WhereYour network card / switch, checking "did this frame arrive correctly?"
WhyThe physical layer has no concept of "a message" — just a stream of bits. This layer is what turns that stream into meaningful, addressed chunks.
ProtocolsEthernet (IEEE 802.3), Wi-Fi (IEEE 802.11), PPP, HDLC, and ARP (often taught here even though it technically bridges L2/L3).
CalledA Frame. This is where a header carrying the source and destination MAC address gets wrapped around the data.
WhatFigures out the PATH data should take across multiple, different networks — this is where IP addressing and routing live.
WhereEvery router on the path between you and any website you visit.
WhyThe data link layer only knows about directly-connected devices — this layer is what lets data cross between totally separate networks (like your home network → your ISP → the website's server).
ProtocolsIP (IPv4/IPv6), ICMP (used by "ping"), IGMP, and routing protocols like RIP, OSPF, BGP.
CalledA Packet (sometimes called a "datagram" at this layer too, especially with IP). This is where the source and destination IP address headers get added.
WhatMakes sure data arrives completely and in order (or deliberately skips that check, for speed) — this is where TCP and UDP live.
WhereEvery time a webpage loads correctly even though the internet dropped a few packets along the way.
WhyThe network layer only promises "I'll try to get this there" — this layer is what actually guarantees (or chooses not to guarantee) real reliability.
ProtocolsTCP (reliable — web, email, file transfer) and UDP (fast, no guarantees — video calls, gaming, DNS lookups).
CalledA Segment if using TCP, or a Datagram if using UDP. Same layer, two different names depending on which protocol wrapped it — a favourite trick question.
WhatManages the "conversation" itself — starting, maintaining, and cleanly ending a session between two applications.
WhereA video call staying connected while you move between Wi-Fi and mobile data.
WhyWithout this, every tiny network hiccup would force you to restart your entire conversation from scratch.
ProtocolsNetBIOS, RPC (Remote Procedure Call), PPTP — this layer is thin in real TCP/IP networks, which is exactly why some of its job quietly gets absorbed into the application layer in practice.
CalledGenerically just Data at layers 5, 6, and 7 — these top three layers don't get their own special PDU name the way the lower four do.
WhatHandles translation, encryption, and compression, so data looks consistent regardless of which machine sent it.
WhereThe padlock icon in your browser (encryption) when you visit a secure website.
WhyDifferent systems represent data differently internally — this layer is the universal translator between them.
ProtocolsSSL/TLS (encryption), plus data-format standards like JPEG, MPEG, ASCII/Unicode encoding.
CalledStill just Data — same as session layer, no special name change here.
WhatThe layer closest to you — web browsers, email clients, anything you actually interact with directly.
WhereChrome, WhatsApp, your email app — right now, this note is technically an application-layer experience.
WhyEvery layer below exists purely to serve this one — none of it matters unless an actual application can use it to do something useful for a human.
ProtocolsHTTP/HTTPS (web), FTP (files), SMTP/POP3/IMAP (email), DNS (name lookup), Telnet, SNMP.
CalledJust Data (sometimes called a "Message" here) — this is where your actual content originates, before any layer below starts wrapping headers around it.
Here's the part that ties this whole topic together. As your data travels DOWN the layers to be sent, each layer wraps its own header around it — and gives the whole thing a new name. This process is called encapsulation. When it arrives at the other end, the layers unwrap it in reverse (de-encapsulation), each layer stripping off its own header before passing it up.
While OSI is the teaching model, TCP/IP is what real networks use — it's simpler, with only 4 layers, because it merges some OSI layers together.
Create a free account to tick topics off, take notes as you read, watch the video lessons and get a day-by-day study plan built around your exam date.
Loading…