Learning Outcome 1 Layered Models

Section 1: Layered Models 

  • Learning Outcome 1 Layered Models

1 / 54
volgende
Slide 1: Slide
newEditor

In deze les zitten 54 slides, met tekstslides.

Dit is niet oké

Onderdelen in deze les

Section 1: Layered Models 

  • Learning Outcome 1 Layered Models

Outline the 7 Layers


Networking Models – Benefits

  • - Simplifies troubleshooting and development

  • - Encourages standardisation and modular design

  • - Supports interoperability between vendors

OSI Model – Overview

  • 1. Application

  • 2. Presentation

  • 3. Session

  • 4. Transport

  • 5. Network

  • 6. Data Link

  • 7. Physical

To see a detailed view of the OSI model click on this link

https://www.youtube.com/watch?v=vv4y_uOneC0

OSI Model – Layer Functions

  • - Application: User interface (HTTP, FTP)

  • - Presentation: Data formatting & encryption

  • - Session: Manages connections

  • - Transport: Ensures reliable delivery (TCP/UDP)

  • - Network: Routing (IP)

  • - Data Link: Error detection (Ethernet, MAC)

  • - Physical: Transmission media (cables, bits)

Data Encapsulation in OSI Model

  • - Application–Session layers: Encoded data

  • - Transport layer: Segments

  • - Network layer: Packets

  • - Data Link layer: Frames

  • - Physical layer: Bits

Protocols & Technologies

  • - Ethernet – Data Link Layer

  • - IP (Internet Protocol) – Network Layer

  • - TCP/UDP – Transport Layer

  • - HTTP, FTP, DNS – Application Layer

Networking Devices and OSI Layers

  • - Router – Network Layer

  • - Switch – Data Link Layer

  • - Hub – Physical Layer

  • - Firewall – Network/Transport Layer

  • - Modem – Physical/Data Link Layer




Introduce the concept of encapsulation and decapsulation as data transverses up and down the layers.


Wire shark

  • Open word docunmnet Introduction to Wire shark on moodle 

  • Copy over labs to virtual machine


The data encapsulation/decapsulation process

  • When a host transmits data across a network to another device, the data is wrapped – orencapsulated – in protocol and delivery information as it passes downward through each of the layers of the OSI model.

The data encapsulation process

  • At the receiving end, information that was added to the data is removed as it passes up the layers of the OSI stack. This process is called de-encapsulation.

The data encapsulation process

  • During the data encapsulation process, several steps occur at the transmitting device:

  • user information is converted to data The first step is to convert user input – or information at the Application layer – into a format that's suitable for transmission on a network. 
    Beside the Application layer of the OSI model, a data packet displays.

The data encapsulation process

  • data is converted to segments As the second step, the data stream is divided into smaller chunks, a Transport layer header is added, converting the data into segments, and a reliable connection is established between the transmitting
    and receiving hosts. 
    The Transport layer is highlighted, and
    the data becomes a segment at this
    layer.

The data encapsulation process

  • data segments are converted to packets or datagrams Once a connection between the transmitting and receiving hosts has been established, Network-layer protocols add a header to each data segment and then hand segments down to the Data Link layer.

    Each segment is converted into one or more data packets, each with logical header
    information so that the packets can be sent to and reassembled at the required destination. 
    The Network layer is highlighted, and the data is a packet at this layer.

The data encapsulation process

  • datagrams or data packets are converted to frames for transmission, After data has been converted into packets, the Data Link layer receives the packets and prepares them for transmission.

    Protocols on the Data Link layer add a frame and a MAC header to each data packet, to uniquely identify the host and hardware device
     to which the packet must be
    transmitted. The Data Link layer is
    highlighted, and the datais a frame
    at this layer.

The data encapsulation process

  • frames are converted to bits During the last step in the encapsulation process, frames are converted into bits at the Physical layer. Digital encoding, a clocking scheme, or a signaling method is used to convert the data frames into a format that network devices can read and interpret. 
    The Physical layer is highlighted and data takes the form of bits at this layer.


•Example Scenario:
You send an email from your laptop (Machine A) to a colleague’s laptop (Machine B) across the Internet



On the Sending Machine – OSI Layers Going Down:
1. Application: Email client formats message, uses SMTP.
2. Presentation: Converts format, applies encryption (TLS/SSL).
3. Session: Establishes and manages SMTP session.
4. Transport: Breaks into TCP segments, assigns ports.
5. Network: Encapsulates in IP packets, assigns IP addresses, routes.
6. Data Link: Encapsulates into frames with MAC addresses.
7. Physical: Converts frames into signals (copper, fibre, or wireless).


  • Across the Network:
    Message passes through multiple technologies (Ethernet, fibre, Wi-Fi, routers, switches). Layers 1 & 2 can change at each hop, Layers 3+ stay consistent.

    On the Receiving Machine – OSI Layers Going Up:
    1. Physical: Signals converted back to binary data.
    2. Data Link: Checks MAC, removes frame headers.
    3. Network: Checks IP, passes segment up.
    4. Transport: Reassembles segments, acknowledges.
    5. Session: Maintains session until complete.
    6. Presentation: Decrypts, decodes.
    7. Application: Displays email to the user.

Outline how the OSI model maps to the TCP/IP model and its variants.


TCP/IP Model Overview

  • 1. Application

  • 2. Transport

  • 3. Internet

  • 4. Network Access

For a detailed description of the TCP/IP Model

look at the following video

https://www.youtube.com/watch?v=2QGgEk20RXM

TCP/IP

  • The TCP/IP model is a reference model that describes the process of network communication based on the TCP/IP suite of network protocols.

    TCP/IP derives its name from Transmission Control Protocol – or TCP – and Internet Protocol – or IP. These are the two main protocols in the suite.

    Because it provides the basic framework for Internet communications, TCP/IP is sometimes also referred to as the Internet Protocol Suite.


TCP/IP

  • The TCP/IP model was developed by the United States Department of Defense and consists of four layers. These are the Application, Transport, Internet, and Network Interface layers.


Each layer in the TCP/IP model performs a specific function.

  • Application layer The Application layer provides definition of protocols for file, mail, and hypertext transfer. It also handles the encoding of data, controls the sessions, and defines socket services and other utilities over TCP/IP.

  • Transport layer The Transport layer provides connection establishment and communication services. It also defines protocols for end-to-end transfer of data, along with error and flow controls. In the TCP/IP model, there are two transport layer protocols: TCP and UDP. 

  • Internet layer The Internet layer provides addressing and routing services. It also controls congestion on the network. This layer involves transferring data from a source to a destination network when multiple networks are connected together. 

  • Network Interface layerThe Network Interface layer provides services to send and receive data packets on the network. It defines protocols for moving data frames between adjacent nodes, and for accessing the medium by the devices. It defines the protocols for encoding and transmitting.

TCP/IP

  • The TCP/IP model encapsulation process is the same as for the OSI model. The application interfaces with the Application layer, then the data is passed down to the Transport and Internet layers, and then forwarded to the Physical layer for transmission.

TCP/IP

  • When the destination device receives the data, the same process occurs across the destination device's TCP/IP layers – but in reverse.

Comparing the OSI and TCP/IP models

  • Like the TCP/IP model, the Open Systems Interconnection – or OSI – model describes how data from an application on one device moves through a network medium to an application on another device.

Comparing the OSI and TCP/IP models

  • By dividing network architecture into different functional layers using reference models like the TCP/IP and OSI models, administrators can implement protocols independently at each layer. This simplifies the design and development processes, as well as network troubleshooting




OSI model. This is how we describe how networks behave, but it's not really what happens. It is the best way to describe, and teach, and compartmentalize how protocols and technologies work. But when you get down to it, the TCP/TP stack is the specific thing that is being run in most cases

TCP/IP Protocols

Protocols in each layer

How data changes

Equipment at each layer

Comparing the OSI and TCP/IP models

  • Both the TCP/IP and OSI models provide similar representations of the data communication process. And like the layers of the TCP/IP model, each layer of the OSI model defines a set of functions and protocols designed to provide services to the layer above it.

Comparing the OSI and TCP/IP models

  • However, whereas the TCP/IP model divides network communications into four layers, the OSI model divides it into seven layers. Starting from the bottom layer, these are the Physical, Data Link, Network, Transport, Session, Presentation, and Application layers.


Each layer in the TCP/IP model corresponds to one or more equivalent layers in the OSI model.

  • Application layer The Application layer in the TCP/IP model maps to three different layers in the OSI model – the Application, Presentation, and Session
    layers. In the TCP/IP model, the Application layer deals with representation, encoding, and dialog control. Some of the protocols that are implemented at the Application layer of the TCP/IP model are Telnet, Post Office Protocol 3 – or POP3 – the File Transfer Protocol – or FTP– HTTP, the domain name system – or DNS –and Secure Shell or SSH. 

  • Transport layer The Transport layer in the TCP/IP model maps to the layer of the same name in the OSI model. 

  • Internet layer The Internet layer in the TCP/IP model maps to the Network layer in the OSI model. Some of the TCP/IP protocols that are implemented in this layer include IP, Internet Control Message Protocol – or ICMP – and the Address Resolution Protocol – or ARP. 

  • Network Interface layer The Network Interface layer of the TCP/IP model maps to two layers in the OSI model – the Data Link and Physical layers. The Network Interface layer defines methods for data transmission on the physical medium. Some of the TCP/IP Internet protocols that are implemented in the Network layer include Ethernet, the Point-to-Point Protocol – or PPP – and Asymmetric Digital Subscriber Line – or ADSL. 

Comparing the OSI and TCP/IP models

  • The TCP/IP and OSI models are broadly similar, except for some layers being joined together in the TCP/IP model. The two models are compatible and can be considered as different ways to view the same protocols.

Comparing the OSI and TCP/IP models

  • Basic units of information for transmission across a network are referred to as protocol data units - or PDUs. At the Application, Presentation, and Session layers of the OSI model, PDUs are simply referred to as data

Comparing the OSI and TCP/IP models

  • Based on how data is processed at each layer, it's converted into

  • segments at the Transport layer 

  • packets at the Network layer 

  • frames at the Data Link layer, and 

  • bits at the Physical layer 


Comparing the OSI and TCP/IP models

  • The most obvious difference between the OSI and TCP/IP models is the number and designation of the layers they include.





Explore what it means to be an “open” system.

  • Definition

  • An open system is a device or network that uses standard, publicly available protocols and interfaces so it can communicate with other systems—regardless of manufacturer or technology—without needing proprietary links or custom coding.


Indicate the importance of understanding the layered model as an abstraction/simplification of the real world which may not always find precise boundaries, while still having certain real-world benefits.


What We Mean by “Abstraction”


  • The OSI model is not a physical thing—it’s a conceptual framework for thinking about how network communication works.

  • It divides the complex process of sending/receiving data into seven layers, each with its own role.

  • In reality, technologies often combine or blur layers—for example, HTTP over TLS over TCP/IP is often implemented in one software stack.


Why the Boundaries Aren’t Always Precise


  • Some protocols span multiple layers (e.g., SSL/TLS affects both Presentation and Application layers).

  • Hardware can operate across layers (e.g., a router has Layer 3 and sometimes Layer 4 filtering capabilities).

  • Software stacks may optimise away strict separation for performance.

  • Vendor implementations might merge functions from different layers.



  • Even though it’s simplified, the OSI model has practical advantages


Why this is important for students


  • Prevents over-literal thinking – Students don’t expect all protocols to fit perfectly into one layer.

  • Prepares for exceptions – Helps identify and work with technologies that break strict OSI separation.

  • Improves troubleshooting – Knowing when to “bend the model” avoids wasted time chasing problems at the wrong layer.

  • Bridges theory and practice – Learners can move between textbook OSI theory and the messy real-world network environment.


Examples

  • When you send a secure web request:

  1. Application Layer: HTTP request.

  2. Presentation Layer: TLS encryption (often bundled in the same process as HTTP).

  3. Transport Layer: TCP segments.

  4. Network Layer: IP packets.

  5. Data Link Layer: Ethernet frames.

  6. Physical Layer: Electrical or optical signals.

  • ➡ In real devices, the HTTP+TLS stack might be one library, the OS may combine Layer 4–7 handling, and network cards may offload Layer 2–4 tasks. Still, thinking in OSI terms helps you see the data’s journey clearly.