"use strict"; const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0]; const {useMDXComponents: _provideComponents} = arguments[0]; function _createMdxContent(props) { const _components = { code: "code", em: "em", h3: "h3", li: "li", ol: "ol", p: "p", pre: "pre", strong: "strong", ul: "ul", ..._provideComponents(), ...props.components }, {Analogy, Answer, Assessment, BlockDiagram, ContentAttribution, DefinitionEntry, DefinitionGroup, English, Explanation, Hinglish, ImportantQA, KeyPoints, MCQ, Practical, Prompt, QAQuestion, Remember, SubTopicHeader, Theory, TopicOverview, TypesOf} = _components; if (!Analogy) _missingMdxReference("Analogy", true); if (!Answer) _missingMdxReference("Answer", true); if (!Assessment) _missingMdxReference("Assessment", true); if (!BlockDiagram) _missingMdxReference("BlockDiagram", true); if (!ContentAttribution) _missingMdxReference("ContentAttribution", true); if (!DefinitionEntry) _missingMdxReference("DefinitionEntry", true); if (!DefinitionGroup) _missingMdxReference("DefinitionGroup", true); if (!English) _missingMdxReference("English", true); if (!Explanation) _missingMdxReference("Explanation", true); if (!Hinglish) _missingMdxReference("Hinglish", true); if (!ImportantQA) _missingMdxReference("ImportantQA", true); if (!KeyPoints) _missingMdxReference("KeyPoints", true); if (!MCQ) _missingMdxReference("MCQ", true); if (!Practical) _missingMdxReference("Practical", true); if (!Prompt) _missingMdxReference("Prompt", true); if (!QAQuestion) _missingMdxReference("QAQuestion", true); if (!Remember) _missingMdxReference("Remember", true); if (!SubTopicHeader) _missingMdxReference("SubTopicHeader", true); if (!Theory) _missingMdxReference("Theory", true); if (!TopicOverview) _missingMdxReference("TopicOverview", true); if (!TypesOf) _missingMdxReference("TypesOf", true); return _jsxs(_Fragment, { children: [_jsxs(Theory, { children: [_jsx(SubTopicHeader, { id: "4.1", title: "The OSI Model: Layered Architecture, Encapsulation" }), _jsx(English, { children: _jsx(TopicOverview, { title: "The OSI Model: Layered Architecture, Encapsulation", topicId: "4.1", readingTime: "11 min read", difficulty: "Medium", children: _jsx(_components.p, { children: "Computer networks connect millions of different devices made by different vendors. For all of them to communicate correctly, we need a common set of rules. The OSI (Open Systems Interconnection) model is a 7-layer conceptual framework that explains how data travels from one device to another. This subtopic covers why we use layering, the 7 layers of the OSI model, the principles of layering, and the process of encapsulation and de-encapsulation where each layer adds its own header as data moves down the stack." }) }) }), _jsx(Hinglish, { children: _jsx(TopicOverview, { title: "OSI Model: Layered Architecture, Encapsulation", topicId: "4.1", readingTime: "11 min read", difficulty: "Medium", children: _jsx(_components.p, { children: "Computer networks mein lakhoh alag alag devices hote hain jo alag alag vendors ke banaye hote hain. In sabhi ko sahi tarike se communicate karne ke liye humein common set of rules chahiye. OSI (Open Systems Interconnection) model ek 7-layer conceptual framework hai jo batata hai ki data ek device se doosre device tak kaise travel karta hai. Yeh subtopic cover karta hai ki hum layering kyun use karte hain, OSI model ki 7 layers, layering ke principles, aur encapsulation-de-encapsulation process jahan har layer apna header add karti hai jab data stack ke neeche jata hai." }) }) }), _jsxs(DefinitionGroup, { children: [_jsx(DefinitionEntry, { term: "OSI Model", children: _jsx(_components.p, { children: "The OSI model is a 7-layer reference model developed by ISO that standardizes how communication systems exchange information, from the physical cable up to the application software. Think of it as a rulebook that lets a Windows laptop talk to a Linux server. Hinglish: OSI model ek 7-layer reference model hai jo ISO ne banaya tha, jo standardize karta hai ki communication systems information kaise exchange karte hain — physical cable se lekar application software tak. Ise ek rulebook samjhiye jo ek Windows laptop ko Linux server se baat karne deta hai. Example: Jab aap Google par search karte hain, data OSI ke saare 7 layers se ho kar guzarta hai." }) }), _jsx(DefinitionEntry, { term: "Layer", children: _jsx(_components.p, { children: "A layer is a self-contained group of functions in the OSI model that performs a specific job (like error detection or routing) and communicates only with the layer directly above and below it. Hinglish: Layer OSI model ka ek self-contained group of functions hai jo ek specific kaam karta hai (jaise error detection ya routing) aur sirf apne upar wale aur neeche wale layer se communicate karta hai. Example: Data Link layer ka kaam hai frames bhejna aur errors check karna, bina Network layer ke routing detail jaane ke." }) }), _jsx(DefinitionEntry, { term: "Encapsulation", children: _jsx(_components.p, { children: "Encapsulation is the process where each OSI layer wraps the data received from the upper layer inside its own header (and sometimes trailer), adding control information as the data moves down toward the physical medium. Hinglish: Encapsulation wo process hai jahan har OSI layer upar wale layer se aaya data apne header (aur kabhi trailer) mein wrap karta hai, control information add karte hue jab data physical medium ki taraf neeche jata hai. Example: Application data ko Transport layer segment banata hai, Network layer packet, Data Link layer frame." }) }), _jsx(DefinitionEntry, { term: "De-encapsulation", children: _jsx(_components.p, { children: "De-encapsulation is the reverse process at the receiving end, where each layer removes its own header and passes the remaining data upward until the original message reaches the application. Hinglish: De-encapsulation receiving end par reverse process hai, jahan har layer apna header remove karti hai aur bacha hua data upar ki taraf pass karti hai jab tak original message application tak na pahunch jaaye. Example: Receiver par frame → packet → segment → original data, har hop par ek header hatta." }) }), _jsx(DefinitionEntry, { term: "Protocol", children: _jsx(_components.p, { children: "A protocol is a set of agreed rules that two peer layers on different devices use to communicate (e.g., how to format, send, and acknowledge data). Hinglish: Protocol ek agreed set of rules hai jo alag alag devices par do peer layers use karte hain communicate karne ke liye (e.g., data ko format, send, aur acknowledge kaise karna hai). Example: HTTP (Application layer), TCP (Transport layer), IP (Network layer) sab protocols hain." }) }), _jsx(DefinitionEntry, { term: "Service & Interface", children: _jsx(_components.p, { children: "Each layer provides a service to the layer above it through a well-defined interface, while hiding its internal implementation. The upper layer does not need to know how the lower layer works. Hinglish: Har layer apne upar wale layer ko ek service deti hai ek well-defined interface ke through, apna internal implementation chhupa kar. Upar wale layer ko nahi pata hota ki neeche wali layer kaam kaise karti hai. Example: Application layer sirf data deta hai Transport layer ko bhejne ke liye, bina yeh jaane ki packets kaise route honge." }) })] }), _jsxs(Explanation, { children: [_jsxs(English, { children: [_jsx("h3", { children: "🎯 Why Do We Use Layering?" }), _jsx("p", { children: "Building a network as one giant block of code would be a nightmare to design, debug, and upgrade. Layering breaks the problem into smaller, manageable pieces. The main reasons are:" }), _jsxs("p", { children: [_jsx("strong", { children: "1. Modularity:" }), " Each layer has a clear, separate responsibility. If the Wi-Fi technology changes, only the Physical/Data Link layers are affected — the Application layer keeps working."] }), _jsxs("p", { children: [_jsx("strong", { children: "2. Interoperability:" }), " Because every vendor follows the same OSI rules, a Cisco router can talk to an HP laptop. Standardization is the reason the Internet works across the world."] }), _jsxs("p", { children: [_jsx("strong", { children: "3. Easy maintenance & upgrades:" }), " A layer can be replaced or improved without rewriting the whole system, as long as its interface stays the same."] }), _jsxs("p", { children: [_jsx("strong", { children: "4. Independent development:" }), " Different companies can build different layers (hardware, drivers, apps) in parallel."] })] }), _jsxs(Hinglish, { children: [_jsx("h3", { children: "🎯 Hum Layering Kyun Use Karte Hain?" }), _jsx("p", { children: "Agar network ko ek bade block of code ki tarah banayein toh design, debug, aur upgrade karna bahut mushkil ho jaayega. Layering problem ko chote, manageable pieces mein todta hai. Main reasons yeh hain:" }), _jsxs("p", { children: [_jsx("strong", { children: "1. Modularity:" }), " Har layer ki clear, alag responsibility hoti hai. Agar Wi-Fi technology change ho, sirf Physical/Data Link layers affect hote hain — Application layer waise hi kaam karta hai."] }), _jsxs("p", { children: [_jsx("strong", { children: "2. Interoperability:" }), " Kyunki har vendor same OSI rules follow karta hai, ek Cisco router ek HP laptop se baat kar sakta hai. Standardization hi wajah hai ki Internet poori duniya mein kaam karta hai."] }), _jsxs("p", { children: [_jsx("strong", { children: "3. Easy maintenance & upgrades:" }), " Ek layer ko bina poora system rewrite kiye replace ya improve kiya ja sakta hai, bas uski interface same rahe."] }), _jsxs("p", { children: [_jsx("strong", { children: "4. Independent development:" }), " Alag alag companies alag alag layers (hardware, drivers, apps) parallel bana sakti hain."] })] }), _jsxs(English, { children: [_jsx("h3", { children: "🗂️ The 7 Layers of the OSI Model" }), _jsxs("p", { children: ["The OSI model has seven layers. A common memory trick is ", _jsx("strong", { children: "\"All People Seem To Need Data Processing\"" }), " (Layer 7 down to Layer 1). Below is a quick diagram from top (Application) to bottom (Physical)."] })] }), _jsxs(Hinglish, { children: [_jsx("h3", { children: "🗂️ OSI Model Ki 7 Layers" }), _jsxs("p", { children: ["OSI model mein saat layers hote hain. Ek famous memory trick hai ", _jsx("strong", { children: "\"All People Seem To Need Data Processing\"" }), " (Layer 7 se Layer 1 tak). Niche ek quick diagram hai top (Application) se bottom (Physical) tak."] })] }), _jsx(BlockDiagram, { title: "OSI Model — 7 Layers (Top to Bottom)", children: _jsx(_components.p, { children: "Layer 7 Application ← User apps, HTTP, FTP, SMTP\nLayer 6 Presentation ← Encryption, compression, translation\nLayer 5 Session ← Start, manage, end sessions\nLayer 4 Transport ← Reliable delivery, TCP / UDP\nLayer 3 Network ← Logical addressing, routing, IP\nLayer 2 Data Link ← Frames, MAC address, error detection\nLayer 1 Physical ← Bits, cables, signals, voltages" }) }), _jsx(TypesOf, { title: "OSI Layers — Brief Role of Each", children: _jsxs(_components.ul, { children: ["\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Layer 7 — Application" }), ": Closest to the user. Provides network services directly to apps like browsers and email. Protocols: HTTP, HTTPS, FTP, SMTP, DNS."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Layer 6 — Presentation" }), ": Translates, encrypts, and compresses data so that the receiving application can understand it. Handles formats like JPEG, ASCII, and TLS encryption."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Layer 5 — Session" }), ": Manages and controls the dialog (session) between two devices — establishing, maintaining, and terminating connections."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Layer 4 — Transport" }), ": Splits data into segments, provides reliable or fast delivery, and controls flow/error recovery. Protocols: TCP (reliable), UDP (fast)."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Layer 3 — Network" }), ": Adds logical addressing (IP) and finds the best path (routing) to send packets across networks."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Layer 2 — Data Link" }), ": Packages bits into frames, uses MAC addresses, and detects/corrects errors on the local link (switches work here)."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Layer 1 — Physical" }), ": Converts frames into raw electrical/optical/radio signals (bits) and transmits them over the cable or air."] }), "\n"] }) }), _jsxs(English, { children: [_jsx("h3", { children: "📏 Principles of Layering" }), _jsx("p", { children: "The OSI model follows a few simple design rules that keep the layers clean and independent:" }), _jsxs("p", { children: [_jsx("strong", { children: "1. Service to upper layer:" }), " A layer offers a well-defined service to the layer just above it."] }), _jsxs("p", { children: [_jsx("strong", { children: "2. Use of lower layer:" }), " A layer gets its work done by using the services of the layer just below it — it never skips layers."] }), _jsxs("p", { children: [_jsx("strong", { children: "3. Peer communication:" }), " Logically, layer N on one machine talks to layer N on another machine using a protocol. Physically, data only moves vertically (down then up)."] }), _jsxs("p", { children: [_jsx("strong", { children: "4. Hidden implementation:" }), " Changes inside a layer do not affect other layers, as long as the interface stays the same."] })] }), _jsxs(Hinglish, { children: [_jsx("h3", { children: "📏 Layering Ke Principles" }), _jsx("p", { children: "OSI model kuch simple design rules follow karta hai jo layers ko clean aur independent rakhte hain:" }), _jsxs("p", { children: [_jsx("strong", { children: "1. Service to upper layer:" }), " Ek layer apne bilkul upar wale layer ko ek well-defined service deti hai."] }), _jsxs("p", { children: [_jsx("strong", { children: "2. Use of lower layer:" }), " Ek layer apna kaam neeche wale layer ki service use karke karti hai — kabhi layers skip nahi karti."] }), _jsxs("p", { children: [_jsx("strong", { children: "3. Peer communication:" }), " Logically, ek machine par layer N doosri machine par layer N se protocol use karke baat karta hai. Physically, data sirf vertically move karta hai (neeche phir upar)."] }), _jsxs("p", { children: [_jsx("strong", { children: "4. Hidden implementation:" }), " Layer ke andar change karne se doosri layers affect nahi hoti, bas interface same rahe."] })] }), _jsxs(English, { children: [_jsx("h3", { children: "📦 Encapsulation & De-encapsulation" }), _jsxs("p", { children: ["When the sender transmits data, it starts at the Application layer and moves down. At each step a header is added (and the Data Link layer also adds a trailer). This wrapping is called ", _jsx("strong", { children: "encapsulation" }), ". The data changes name at each layer:"] }), _jsx("p", { children: _jsx("strong", { children: "Data → Segment (Transport) → Packet (Network) → Frame (Data Link) → Bits (Physical)" }) }), _jsxs("p", { children: ["At the receiver, the reverse happens — each layer strips off its header. This is ", _jsx("strong", { children: "de-encapsulation" }), ", finally delivering the original data to the application."] })] }), _jsxs(Hinglish, { children: [_jsx("h3", { children: "📦 Encapsulation & De-encapsulation" }), _jsxs("p", { children: ["Jab sender data transmit karta hai, toh wo Application layer se start hota hai aur neeche jata hai. Har step par ek header add hota hai (aur Data Link layer ek trailer bhi add karti hai). Is wrapping ko ", _jsx("strong", { children: "encapsulation" }), " kehte hain. Data ka naam har layer par badalta hai:"] }), _jsx("p", { children: _jsx("strong", { children: "Data → Segment (Transport) → Packet (Network) → Frame (Data Link) → Bits (Physical)" }) }), _jsxs("p", { children: ["Receiver par reverse hota hai — har layer apna header hata deti hai. Ise ", _jsx("strong", { children: "de-encapsulation" }), " kehte hain, aur end mein original data application tak pahunchta hai."] })] }), _jsxs(English, { children: [_jsx("h3", { children: "🔁 Encapsulation Flow (Sender Side)" }), _jsx("p", { children: "The diagram below shows how the original message gets wrapped with a header at every layer as it travels down the OSI stack before becoming bits on the wire." })] }), _jsxs(Hinglish, { children: [_jsx("h3", { children: "🔁 Encapsulation Flow (Sender Side)" }), _jsx("p", { children: "Niche diagram dikhata hai ki original message har layer par apne header ke saath kaise wrap hota hai jab wo OSI stack ke neeche jata hai aur wire par bits banata hai." })] }), _jsx(_components.pre, { children: _jsx(_components.code, { className: "language-mermaid", children: "flowchart TD\n A[\"Application Data
(L7)\"] --> B[\"+ Presentation Header
(L6)\"]\n B --> C[\"+ Session Header
(L5)\"]\n C --> D[\"+ Transport Header = SEGMENT
(L4)\"]\n D --> E[\"+ Network Header = PACKET
(L3)\"]\n E --> F[\"+ Data Link Hdr/Tlr = FRAME
(L2)\"]\n F --> G[\"Convert to BITS & send
(L1 Physical)\"]\n" }) }), _jsxs(English, { children: [_jsx("h3", { children: "🔄 De-encapsulation Flow (Receiver Side)" }), _jsx("p", { children: "At the receiver, bits arrive at the Physical layer and move upward. Each layer reads and removes only its own header, passing the rest up until the Application layer gets the clean original message." })] }), _jsxs(Hinglish, { children: [_jsx("h3", { children: "🔄 De-encapsulation Flow (Receiver Side)" }), _jsx("p", { children: "Receiver par bits Physical layer par aate hain aur upar ki taraf jate hain. Har layer sirf apna header padhta aur hata deta hai, baaki ko upar pass karta hai jab tak Application layer ko clean original message na mil jaaye." })] }), _jsx(_components.pre, { children: _jsx(_components.code, { className: "language-mermaid", children: "flowchart TD\n G[\"Receive BITS
(L1 Physical)\"] --> F[\"Strip Data Link Hdr/Tlr = FRAME
(L2)\"]\n F --> E[\"Strip Network Header = PACKET
(L3)\"]\n E --> D[\"Strip Transport Header = SEGMENT
(L4)\"]\n D --> C[\"Strip Session Header
(L5)\"]\n C --> B[\"Strip Presentation Header
(L6)\"]\n B --> A[\"Deliver clean Application Data
(L7)\"]\n" }) }), _jsx(KeyPoints, { children: _jsxs(_components.ul, { children: ["\n", _jsx(_components.li, { children: "Layering gives modularity, interoperability, and easy upgrades — vendors follow one standard so devices can talk." }), "\n", _jsx(_components.li, { children: "OSI has 7 layers: Application, Presentation, Session, Transport, Network, Data Link, Physical (top to bottom)." }), "\n", _jsx(_components.li, { children: "Each layer serves the layer above and uses the layer below; peers talk via protocols." }), "\n", _jsx(_components.li, { children: "Encapsulation adds a header at every layer going down: Data → Segment → Packet → Frame → Bits." }), "\n", _jsx(_components.li, { children: "De-encapsulation removes headers going up, recovering the original message at the Application layer." }), "\n", _jsx(_components.li, { children: "Memory aid: \"All People Seem To Need Data Processing\" (L7 → L1)." }), "\n"] }) }), _jsx(Remember, { children: _jsxs(_components.ul, { children: ["\n", _jsx(_components.li, { children: "Exam tip: Encapsulation naming is frequently asked — Segment (L4), Packet (L3), Frame (L2), Bits (L1)." }), "\n", _jsxs(_components.li, { children: ["OSI is a ", _jsx(_components.em, { children: "reference/conceptual" }), " model; the real Internet uses the TCP/IP model, but OSI is still taught for clear concepts."] }), "\n", _jsx(_components.li, { children: "Layers never skip — data always moves vertically, even though logically peer layers communicate." }), "\n", _jsx(_components.li, { children: "The Data Link layer is the only one that adds both a header AND a trailer." }), "\n"] }) }), _jsx(Analogy, { children: _jsxs(_components.p, { children: [_jsx("b", { children: "Analogy: Encapsulation = Sending a Gift by Post" }), _jsx("br", {}), "\nImagine you write a letter (Application data). You put it in an envelope with the receiver's name (Transport/Network header). The post office adds a routing barcode (Data Link header/trailer) and the truck carries the physical box (Physical bits). At the other end, each wrapper is removed in reverse order until your friend reads the original letter. That is encapsulation and de-encapsulation in real life."] }) })] }), _jsxs(_components.p, { children: ["=", _jsx("mark", { children: "SUMMARY_SEPARATOR" }), "="] }), _jsx(_components.p, { children: "The OSI model is a 7-layer reference framework (Application, Presentation, Session, Transport, Network, Data Link, Physical) created by ISO to standardize how devices communicate. We use layering for modularity, interoperability, and easy maintenance, with each layer offering a service to the layer above while using the layer below, and peer layers talking through protocols. As data travels down the sender's stack, each layer wraps it with its own header — a process called encapsulation — turning data into segments, packets, frames, and finally bits on the wire. At the receiver, de-encapsulation reverses this, stripping headers layer by layer to deliver the original message to the application. Understanding these layered principles and the encapsulation flow is essential before studying the TCP/IP model and real-world networking protocols." })] }), "\n", _jsx(Practical, { children: _jsxs(ImportantQA, { children: [_jsxs(QAQuestion, { marks: 2, children: [_jsx(Prompt, { children: "List the seven layers of the OSI model in correct order from top to bottom." }), _jsxs(Answer, { children: [_jsxs(_components.p, { children: ["The OSI (Open Systems Interconnection) model has ", _jsx(_components.strong, { children: "7 layers" }), " arranged from top (application side) to bottom (physical media side):"] }), _jsxs(_components.ul, { children: ["\n", _jsx(_components.li, { children: _jsx(_components.strong, { children: "Layer 7 — Application" }) }), "\n", _jsx(_components.li, { children: _jsx(_components.strong, { children: "Layer 6 — Presentation" }) }), "\n", _jsx(_components.li, { children: _jsx(_components.strong, { children: "Layer 5 — Session" }) }), "\n", _jsx(_components.li, { children: _jsx(_components.strong, { children: "Layer 4 — Transport" }) }), "\n", _jsx(_components.li, { children: _jsx(_components.strong, { children: "Layer 3 — Network" }) }), "\n", _jsx(_components.li, { children: _jsx(_components.strong, { children: "Layer 2 — Data Link" }) }), "\n", _jsx(_components.li, { children: _jsx(_components.strong, { children: "Layer 1 — Physical" }) }), "\n"] }), _jsxs(_components.p, { children: ["Mnemonic: ", _jsx(_components.strong, { children: "A" }), "ll ", _jsx(_components.strong, { children: "P" }), "eople ", _jsx(_components.strong, { children: "S" }), "eem ", _jsx(_components.strong, { children: "T" }), "o ", _jsx(_components.strong, { children: "N" }), "eed ", _jsx(_components.strong, { children: "D" }), "ata ", _jsx(_components.strong, { children: "P" }), "rocessing (top to bottom)."] }), _jsx(Remember, { children: _jsx(_components.p, { children: "Top layer (7) is closest to the user application, bottom layer (1) is closest to the physical cable/wireless signal." }) })] })] }), _jsxs(QAQuestion, { marks: 4, children: [_jsx(Prompt, { children: "Explain the need for layering in computer networks with its main advantages." }), _jsxs(Answer, { children: [_jsx(_components.h3, { children: "📝 Why We Need Layering" }), _jsx(_components.p, { children: "A network is complex, so dividing it into layers makes design, implementation, and troubleshooting manageable." }), _jsx(_components.h3, { children: "🎯 Main Advantages" }), _jsxs(_components.ul, { children: ["\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Modular design:" }), " Each layer has a specific job, so changes in one layer do not affect others."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Easy troubleshooting:" }), " Problems can be isolated to a specific layer."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Interoperability:" }), " Different vendors can build products for the same layer (e.g. any NIC works with any OS at the Data Link layer)."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Reuse & abstraction:" }), " Upper layers use lower layers as black boxes without knowing internal details."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Standardization:" }), " Open standards let devices from different manufacturers communicate."] }), "\n"] }), _jsx(_components.h3, { children: "🔧 How Layers Cooperate" }), _jsxs(_components.p, { children: ["Each layer provides a ", _jsx(_components.strong, { children: "service" }), " to the layer above it and uses the service of the layer below it through well-defined interfaces."] }), _jsx(Remember, { children: _jsx(_components.p, { children: "Layering follows the principle of 'divide and conquer' — break a big problem into smaller independent pieces." }) })] })] }), _jsxs(QAQuestion, { marks: 6, children: [_jsx(Prompt, { children: "Describe the process of encapsulation and de-encapsulation in the OSI model with a sender and receiver example." }), _jsxs(Answer, { children: [_jsx(_components.h3, { children: "📝 Definition" }), _jsxs(_components.p, { children: [_jsx(_components.strong, { children: "Encapsulation" }), " is the process where each OSI layer at the sender adds its own ", _jsx(_components.strong, { children: "header (and sometimes trailer)" }), " to the data received from the upper layer. The data grows as it moves down. ", _jsx(_components.strong, { children: "De-encapsulation" }), " is the reverse process at the receiver, where each layer removes its header and passes the remaining data upward."] }), _jsx(_components.h3, { children: "🔄 Encapsulation at Sender (Top to Bottom)" }), _jsxs(_components.ol, { children: ["\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Application/Presentation/Session" }), " create the actual message data."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Transport" }), " adds a header (containing port numbers) → unit is called a ", _jsx(_components.strong, { children: "Segment" }), " (TCP) or ", _jsx(_components.strong, { children: "Datagram" }), " (UDP)."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Network" }), " adds an IP header (containing source and destination IP) → unit is called a ", _jsx(_components.strong, { children: "Packet" }), "."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Data Link" }), " adds header and trailer (containing MAC addresses) → unit is called a ", _jsx(_components.strong, { children: "Frame" }), "."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Physical" }), " converts the frame into ", _jsx(_components.strong, { children: "bits (0s and 1s)" }), " and transmits over the medium."] }), "\n"] }), _jsx(_components.h3, { children: "🔓 De-encapsulation at Receiver (Bottom to Top)" }), _jsxs(_components.ol, { children: ["\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Physical" }), " receives bits and rebuilds the frame."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Data Link" }), " checks MAC address and removes its header/trailer → gives Packet."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Network" }), " checks IP address and removes its header → gives Segment."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Transport" }), " removes its header and reassembles data → gives original message."] }), "\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "Session/Presentation/Application" }), " deliver the final data to the user application."] }), "\n"] }), _jsx(_components.h3, { children: "🖼️ Flow Diagram" }), _jsx(_components.pre, { children: _jsx(_components.code, { className: "language-mermaid", children: "flowchart LR\n A[Application Data] --> B[+ Transport Header: Segment]\n B --> C[+ Network Header: Packet]\n C --> D[+ Data Link Header/Trailer: Frame]\n D --> E[Bits on Medium]\n E --> F[Receiver removes headers upward]\n F --> G[Original Data Delivered]\n" }) }), _jsx(_components.h3, { children: "📌 Key Terms" }), _jsxs(_components.ul, { children: ["\n", _jsxs(_components.li, { children: [_jsx(_components.strong, { children: "PDU (Protocol Data Unit):" }), " Name of data at each layer — Segment, Packet, Frame, Bits."] }), "\n", _jsxs(_components.li, { children: ["The added headers are read only by the ", _jsx(_components.strong, { children: "peer layer" }), " on the other side."] }), "\n"] }), _jsx(Remember, { children: _jsx(_components.p, { children: "Encapsulation wraps data on the way DOWN; de-encapsulation unwraps it on the way UP. Headers are added/removed in strict layer order." }) })] })] })] }) }), "\n", _jsxs(Assessment, { topicId: "4.1", children: [_jsx(MCQ, { questions: [{ "id": "78544b94-3edb-4342-813a-b9811e5b4a4e", "q": "Which layer of the OSI model is closest to the end user and provides network services to applications?", "options": ["Application layer", "Physical layer", "Network layer", "Data Link layer"], "answer": 0, "hint": "Application layer is the topmost layer closest to the user.", "explanation": "The Application layer (Layer 7) is the topmost layer that provides network services directly to the user applications." }, { "id": "368e416a-f3a0-499f-8838-66d276ee7d4f", "q": "Which is the lowest layer in the seven-layer OSI model?", "options": ["Session layer", "Transport layer", "Presentation layer", "Physical layer"], "answer": 3, "hint": "Remember the bottom layer deals with raw bits over the medium.", "explanation": "The Physical layer (Layer 1) is the lowest layer and is responsible for transmitting raw bits over the physical medium." }, { "id": "d12ebf59-f3e1-4f7b-8637-6ddd882c83b8", "q": "What is the correct order of the OSI layers from layer 7 down to layer 1?", "options": ["Physical, Data Link, Network, Transport, Session, Presentation, Application", "Application, Presentation, Session, Transport, Network, Data Link, Physical", "Application, Session, Presentation, Transport, Network, Data Link, Physical", "Physical, Network, Data Link, Transport, Session, Presentation, Application"], "answer": 1, "hint": "Use the mnemonic Please Do Not Throw Sausage Pizza Away.", "explanation": "The correct top-to-bottom order is Application, Presentation, Session, Transport, Network, Data Link, Physical." }, { "id": "181cdcaa-283e-4e32-b0bc-983855d17a84", "q": "What is the main purpose of dividing network functions into layers?", "options": ["To increase the physical cable length", "To reduce the number of network devices", "To manage complexity and hide implementation details from other layers", "To eliminate the need for protocols"], "answer": 2, "hint": "Layering hides lower details from upper layers.", "explanation": "Layering breaks complex networking into manageable parts, hides implementation details, and lets each layer change independently." }, { "id": "1e4f63cf-739c-4ec4-8f53-c77d88e535dd", "q": "What is the term for adding layer-specific headers to data as it moves down the OSI stack?", "options": ["Encapsulation", "Decapsulation", "Multiplexing", "Modulation"], "answer": 0, "hint": "Each layer adds its own header as data moves down.", "explanation": "Encapsulation is the process where each layer adds its own header (and sometimes trailer) to the data from the layer above as it passes down." }, { "id": "483fc454-3c7a-492a-8252-d6bc0da3b8a3", "q": "On the sending side, which layer directly passes data to the Transport layer?", "options": ["Network layer", "Data Link layer", "Physical layer", "Session layer"], "answer": 3, "hint": "The Transport layer receives data from the Session layer above it.", "explanation": "When data moves down, the Transport layer receives data from the Session layer (layer 5) and passes segments to the Network layer (layer 3)." }, { "id": "13719a02-6f1f-4314-9984-2d25dc251734", "q": "What data unit does the Transport layer pass down to the Network layer?", "options": ["Frame", "Segment", "Bit", "Message"], "answer": 1, "hint": "The unit passed from Transport to Network is called a segment.", "explanation": "The Transport layer sends a segment to the Network layer, which then adds its own header and creates a packet." }, { "id": "d8be14be-2c43-4c1b-9a17-3a34fd84ca99", "q": "At the receiving end, what is the process of removing headers added by peer layers called?", "options": ["Encapsulation", "Compression", "Decapsulation", "Fragmentation"], "answer": 2, "hint": "Decapsulation strips headers as data moves up.", "explanation": "At the receiver, each layer removes (strips) the header added by its peer layer; this reverse process is called decapsulation." }, { "id": "23d952bb-9bf7-4626-9cae-25a8d88e307c", "q": "Which OSI layer is responsible for logical addressing and routing of packets?", "options": ["Network layer", "Transport layer", "Data Link layer", "Physical layer"], "answer": 0, "hint": "Layer 3 is the Network layer handling routing.", "explanation": "The Network layer (Layer 3) is responsible for logical addressing and routing packets across networks." }, { "id": "9f805933-ec08-41e0-99c5-603dc2455457", "q": "How do two peer layers (for example layer 4 on sender and receiver) appear to communicate?", "options": ["They share the same physical wire directly", "They never exchange any information", "They communicate through the Physical layer only", "They communicate logically using the same layer protocol"], "answer": 3, "hint": "Peer layers communicate logically using their protocols.", "explanation": "Peer layers on different systems appear to communicate directly using the same protocol; the actual data moves vertically through the stack via encapsulation and decapsulation." }], topicId: "4.1" }), _jsx(ContentAttribution, { sourceTitle: "Curriculum Reference", sourceUrl: "https://learningway.in", professor: "Faculty Review Team", model: "Curriculum AI", seoTitle: "The OSI Model", seoDesc: "Master The OSI Model with comprehensive notes, real-world examples, and practice quiz on LearningWay.", seoKeywords: "the osi model, the osi model notes, the osi model examples, diploma engineering notes, practice quiz, learningway" })] })] }); } function MDXContent(props = {}) { const {wrapper: MDXLayout} = { ..._provideComponents(), ...props.components }; return MDXLayout ? _jsx(MDXLayout, { ...props, children: _jsx(_createMdxContent, { ...props }) }) : _createMdxContent(props); } return { default: MDXContent }; function _missingMdxReference(id, component) { throw new Error("Expected " + (component ? "component" : "object") + " `" + id + "` to be defined: you likely forgot to import, pass, or provide it."); }