ICSA 411: Week 4 Protocol Architectures

1
ICSA 411 Week 4Protocol Architectures

• Elizabeth Lane Lawley, Instructor

2
Data Compression

• Works on the principle of eliminating redundancy
• Codes are substituted for compressed portions of
  data
• Lossless reconstituted data is identical to
  original (ZIP, GIF)
• Lossy reconsituted data is only perceptually
  equivalent (JPEG, MPEG)

3
Run Length Encoding

• Replace string of anything with flag, character,
  and count
• Used in GIF to compress long stretches of
  unchanged color, in fax transmissions to transmit
  blocks of white space

4
Huffman Encoding

• Length of each character code based on
  statistical frequency in text
• Tree-based dictionary of characters
• Encoding is the string of symbols on each branch
  followed. String Encoding TEA 10 00 010
  SEA 011 00 010 TEN 10 00 110

5
Lempel-Ziv Encoding

• Used in V.42 bis, ZIP
• buffer strings at transmitter and receiver
• replace strings with pointer to location of
  previous occurrence
• algorithm creates a tree-based dictionary of
  character strings

6
Compression Formats

• Software/Data Files (all lossless)
• PKZip (.zip)
• Stuffit (.sit)
• UNIX Compress (.c)
• Graphics/Video
• GIF (lossless)
• JPEG/MPEG (lossy)

7
Related Formats

• Binary to text conversion formats
• Binhex (.hqx)
• Uuencoding
• UNIX archive (.tar)

8
Simple Protocol Architecture

• Not an actual architecture, but a model for how
  they work
• Similar to pseudocode, used for teaching
  programming
• Once we understand the building blocks, we can
  look at specific examples
• Open Systems Interconnection (OSI) 7-Layer Model
• TCP/IP
• Systems Network Architecture (SNA)

9
Why Use Protocol Architecture?

• Data communications requires complex procedures
• Sender identifies data path/receiver
• Systems negotiate preparedness
• Applications negotiate preparedness
• Translation of file formats
• For all tasks to occur, high level of cooperation
  is required

10
Modular Approach

• Breaks complex tasks into subtasks
• Each module handles specific subset of tasks
• Communication occurs
• between different modules on the same system
• between similar modules on different systems

11
Simple Modular Example

• File transfer facility
• Three modules
• File transfer module could handle translation and
  inter-application communication
• Communication service module could handle
  negotiation of preparedness, data flow
• Network access module could handle data path

12
Advantages of Modularity

• Easier application development
• Network can change without all programs being
  modified

13
Three-Layer Model

• Distributed data communications involves three
  primary components
• Networks
• Computers
• Applications
• Three corresponding layers
• Network access layer
• Transport layer
• Application layer

14
Network Access Layer

• Concerned with exchange of data between computer
  and network
• Includes addressing, routing, prioritizing, etc
• Different networks require different software at
  this layer
• Example X.25 standard for network access
  procedures on packet-switching networks

15
Transport Layer

• Concerned with reliable transfer of information
  between applications
• Independent of the nature of the application
• Includes aspects like flow control and error
  checking

16
Application Layer

• Logic needed to support various applications
• Each type of application (file transfer, remote
  access) requires different software on this layer

17
Addressing

• Each computer on a network requires a unique
  address on that network
• Each application on the computer must have a
  unique address within the computer to allow the
  transport layer to support multiple applications
• Data units must include network and application
  addresses

18
Standardized Protocol Architectures

• Vendors like standards because they make their
  products more marketable
• Customers like standards because they enable
  products from different vendors to interoperate
• Two protocol standards are well-known
• TCP/IP widely implemented
• OSI well-known, less used, still useful for
  modeling/conceptualizing

19
OSI

• Application
• Presentation
• Session
• Transport
• Network
• Data Link
• Physical

• Open Systems Interconnection
• Developed by ISO
• Contains seven layers(see page 358)

20
OSI Lower Layers

• Physical
• Data Link
• Network

21
OSI Physical Layer

• Responsible for transmission of bits
• Always implemented through hardware
• Encompasses mechanical, electrical, and
  functional interfaces
• e.g. RS-232

22
OSI Data Link Layer

• Responsible for error-free, reliable transmission
  of data
• Flow control, error correction
• e.g. HDLC

23
OSI Network Layer

• Responsible for routing of messages through
  network
• Concerned with type of switching used (circuit v.
  packet)
• Handles routing between networks, as well as
  through packet-switching networks

24
OSI Upper Layers

• Transport
• Session
• Presentation
• Application

25
OSI Transport Layer

• Isolates messages from lower and upper layers
• Breaks down message size
• Monitors quality of communications channel
• Selects most efficient communication service
  necessary for a given transmission

26
OSI Session Layer

• Establishes logical connections between systems
• Manages log-ons, password exchange, log-offs
• Terminates connection at end of session

27
OSI Presentation Layer

• Provides format and code conversion services
• Examples
• File conversion from ASCII to EBDIC
• Invoking character sequences to generate bold,
  italics, etc on a printer

28
OSI Application Layer

• Provides access to network for end-user
• Users capabilities are determined by what items
  are available on this layer

29
OSI in Action Outgoing File Transfer

• Program issues command to Application Layer
• Application passes it to Presentation, which may
  reformat, passes to Session
• Session requests a connection, passes to
  Transport
• Transport breaks file into chunks, passes to
  Network

• Network selects the datas route, passes to Data
  Link
• Data Link adds error-checking info, passes to
  Physical
• Physical transmits data, which includes
  information added by each layer

30
OSI in Action Incoming File Transfer

• Physical receives bits, passes to Data Link
• Data Link checks for errors, passes to Network
• Network verifies routing, passes to Transport
• Transport reassembles data, passes to Session
• Session determines if transfer is complete, may
  end session, passes to Presentation

• Presentation may reformat, perform conversions,
  pass to Application layer
• Application presents results to user (e.g.
  updates FTP program display)

31
TCP/IP v. OSI

• See diagram page 359 for relationships
• Most production software uses TCP/IP rather
  than OSI
• Why has OSI lost the war? Two primary reasons
• Not as mature as TCP/IP
• Unnecessarily complex (seven layers rather than
  five)

32
Why Study OSI?

• Still the best model for conceptualizing and
  understanding protocol architectures
• Later ICSA networking classes expect you to know
  and understand this model
• Key points
• Modular
• Hierarchical
• Boundaries between layersinterfaces

33
TCP/IP

• Transmission Control Protocol/Internet Protocol
• Developed by DARPA
• No official protocol standard
• Can identify five layers

• Application
• Host-to-Host (transport)
• Internet
• Network Access
• Physical

34
TCP/IP Physical Layer

• Physical interface between a DTE (e.g. computer
  or terminal) and a transmission medium
• Specifies
• Characteristics of medium
• Nature of signals
• Data rate
• Similar to mechanical aspects of RS-232

35
TCP/IP Network Access

• Exchange of data between end system and network
• Address of host and destination
• Prioritization of transmission
• Software at this layer depends on network (e.g.
  X.25 vs. Ethernet)
• Segregation means that no other software needs to
  be concerned about net specifics

36
TCP/IP Internet Layer

• An Internet is an interconnection of two or more
  networks
• Internet layer handles tasks similar to network
  access layer, but between networks rather than
  between nodes on a network
• Uses IP for addressing
• Implemented in workstations and routers

37
TCP/IP Transport Layer

• Also called host-to-host layer
• Reliable exchange of data between applications
• Uses TCP protocols for transmission

38
TCP/IP Application Layer

• Logic needed to support variety of applications
• Separate module supports each type of application
  (e.g. file transfer)

39
Test 1 Reminders

• You may bring one sheet of notes, handwritten,
  one side of the page only, which must be turned
  in with the test
• Three parts matching/acronym fill-in, multiple
  choice, short answer
• Follow the instructions carefully!