rokoi

download rokoi

of 74

Transcript of rokoi

  • 8/3/2019 rokoi

    1/74

    Introduction

    Chapter 1

  • 8/3/2019 rokoi

    2/74

    Computer network

    computer network, often simply referred to as a

    network, is a collection of hardware components

    and computers interconnected by

    communication channels that allow sharing of

    resources and information.Where at least one

    process in one device is able to send/receive

    data to/from at least one process residing in aremote device.

  • 8/3/2019 rokoi

    3/74

    Uses of Computer Networks

    Business Applications

    Home Applications

    Mobile Users Social Issues

  • 8/3/2019 rokoi

    4/74

    Business Applications of Networks

    A network with two clients and one server.

  • 8/3/2019 rokoi

    5/74

    Business Applications of Networks (2)

    The client-server model involves requests and replies.

  • 8/3/2019 rokoi

    6/74

    Home Network Applications

    Access to remote information

    Person-to-person communication

    Interactive entertainment Electronic commerce

  • 8/3/2019 rokoi

    7/74

    Home Network Applications (2)

    In peer-to-peer system there are no fixed clients and servers.

  • 8/3/2019 rokoi

    8/74

    Home Network Applications (3)

    Some forms of e-commerce.

  • 8/3/2019 rokoi

    9/74

    Mobile Network Users

    Combinations of wireless networks and mobile computing.

  • 8/3/2019 rokoi

    10/74

    Network Hardware

    Local Area Networks

    Metropolitan Area Networks

    Wide Area Networks Wireless Networks

    Home Networks

    Internetworks

  • 8/3/2019 rokoi

    11/74

    Broadcast Networks

    Types of transmission technology

    Broadcast links Point-to-point links

  • 8/3/2019 rokoi

    12/74

    Broadcast Networks (2)

    Classification of interconnected processors by scale.

    V i l i ibl f

  • 8/3/2019 rokoi

    13/74

    Various topologies are possible for

    broadcast LANs.

    Bus

    Ring

    Star

    Mesh

    Tree Hybrid

  • 8/3/2019 rokoi

    14/74

    Bus Topology

  • 8/3/2019 rokoi

    15/74

    Ring Topology

  • 8/3/2019 rokoi

    16/74

    Star Topology

  • 8/3/2019 rokoi

    17/74

    Tree topology

  • 8/3/2019 rokoi

    18/74

    Mesh Topology

  • 8/3/2019 rokoi

    19/74

    Hybrid Topology

  • 8/3/2019 rokoi

    20/74

    Metropolitan Area Networks

    A metropolitan area network based on cable TV.

  • 8/3/2019 rokoi

    21/74

    Wide Area Networks

    Relation between hosts on LANs and the subnet.

  • 8/3/2019 rokoi

    22/74

    Wide Area Networks (2)

    A stream of packets from sender to receiver.

  • 8/3/2019 rokoi

    23/74

    Wireless Networks

    Categories of wireless networks:

    System interconnection

    Wireless LANs

    Wireless WANs

  • 8/3/2019 rokoi

    24/74

    Wireless Networks (2)

    (a) Bluetooth configuration

    (b) Wireless LAN

  • 8/3/2019 rokoi

    25/74

    Wireless Networks (3)

    (a) Individual mobile computers

    (b) A flying LAN

  • 8/3/2019 rokoi

    26/74

    Home Network Categories

    Computers (desktop PC, PDA, shared peripherals

    Entertainment (TV, DVD, VCR, camera, stereo, MP3)

    Telecomm (telephone, cell phone, intercom, fax)

    Appliances (microwave, fridge, clock, furnace, airco) Telemetry (utility meter, burglar alarm, babycam).

  • 8/3/2019 rokoi

    27/74

    Internetworks

    A collection of interconnected networksis called an internetwork and internet.

  • 8/3/2019 rokoi

    28/74

    Network Software

    Protocol Hierarchies

    Design Issues for the Layers

    Connection-Oriented and Connectionless Services

    Service Primitives The Relationship of Services to Protocols

  • 8/3/2019 rokoi

    29/74

    Protocol Hierarchies

    Most networks are designed as a stack of layers

    to reduce the design complexity.

    The purpose of each layer is to offer certain

    services to the higher layers, shielding those

    layers from the details of how the offeredservices are actually implemented.

    The fundamental idea is that a particular piece of

    software provides a service to its users but keepsthe details of its internal state and algorithms

    hidden.

  • 8/3/2019 rokoi

    30/74

    Layer n on one machine carries on a

    conversation with layer n on another machine.

    The rules and conventions used in thisconversation are collectively known as the layer

    n protocol.

    Basically a protocol is an agreement betweenthe communicating parties on how

    communications is to proceed.

    N t k S ft

  • 8/3/2019 rokoi

    31/74

    Network SoftwareProtocol Hierarchies

    Layers, protocols, and interfaces.

  • 8/3/2019 rokoi

    32/74

    In reality, no data is directly transferred from layer n on

    one machine to layer n on another machine.

    Instead each layer passes data and control informationto the layer immediately below it, until the lowest layer

    is reached.

    Below layer 1 is the physical medium through which

    actual transmission occurs.

    The Interfaces defines which primitive operations and

    services the lower layer makes available to the upper

    one.

    Each layer must perform a specific collection of well-

    understood functions.

  • 8/3/2019 rokoi

    33/74

    Defining a clear cut interface makes it easy to

    replace an old implementation by a new one

    provided that it gives the same services as theolder one.

    A set of layers and protocols is called a network

    architecture. Niether the details of the implementation nor the

    specification of the interfaces is a part of the

    architecture because they are kept hidden. A protocol stack is a list of protocols used my a

    system.

  • 8/3/2019 rokoi

    34/74

  • 8/3/2019 rokoi

    35/74

    Example information flow supporting virtual communication in layer 5.

  • 8/3/2019 rokoi

    36/74

    Design Issues for the Layers

    Addressing: A means is required for a process on onemachine to specify with whom it wants to talk because

    of multiple destinations.

    Data Transfer: It needs to be specified that how many

    logical connections can a system provide. For. Eg:some systems provide 2 logical connections: one for

    normal data and one for urgent data.

    Error Control: Errors are bound to occur because the

    physical communication circuits are not perfect. Both

    the communicating parties need to decide on which

    error control technique needs to be used.

  • 8/3/2019 rokoi

    37/74

    Flow Control: When the speed differs on the senders

    side and the receivers side, a mechanism is needed to

    assure the sending party that all the packets are being

    received. This can involve some kind of feedback from

    the receiver. Or they can decide the transmission speed

    before hand.

    Message size: If the process insists on breaking anarbitrarily long message into very small packets which

    will be very inefficient to send individually, then a

    number of small packets that belong to different

    messages can be assembled that are going in the samedirection/ destination, and furthur can be diassembled

    at the destination.

  • 8/3/2019 rokoi

    38/74

    Multiplexing: When it is very expensive to set

    up a separate connection for different or

    unrelated conversations, then the sameconnection can be used

    Routing: Choosing the best path when a number

    of paths are available.

  • 8/3/2019 rokoi

    39/74

    Connection-oriented services It is like a telephone system where to talk to someone,

    you have to pick up a phone, dial the number, talk andthen hang up.

    Similarly a user who wishes to communicate has to first

    set up a connection, use it and then terminate it.

    Acts like a tube where the data is inserted at one end by

    the sender and extracted at the other end by the

    receiver.

    In some cases after the connection is setup, both theparties can decide on the parameters like message size,

    quality of srevice etc.

  • 8/3/2019 rokoi

    40/74

    Connectionless service

    It is like a postal system where a post card

    contains the address of the receiver and is sent.

    Each message is sent through the system

    independent of all the others.

  • 8/3/2019 rokoi

    41/74

    Each service is characterized by quality of service

    Could be reliable/Non reliable.

    For a reliable service, acknowledgements can beused which introduces overhead and delays which

    are often worth it but sometimes undesirable,

    A reliable connection-oriented service isappropriate in a file transfer situation.

    Reliable connection oriented service has two

    variations- Message sequences and byte streams.

  • 8/3/2019 rokoi

    42/74

    Where as the delays introduced by

    acknowledgements are not acceptable is case of

    digitized voice traffic. Not all applications require setting up

    connections. For. Eg: e-mail.

    Various other services are:

    Datagram service: e.g. telegram service

    Acknowledged datagram service.: sending aregistered letter

    Request-reply.: query to the local library

    C i O i d d C i l

  • 8/3/2019 rokoi

    43/74

    Connection-Oriented and Connectionless

    Services

    Six different types of service.

  • 8/3/2019 rokoi

    44/74

    Service Primitives

    Five service primitives for implementing a simple connection-

    oriented service.

  • 8/3/2019 rokoi

    45/74

    Service Primitives (2)

    Packets sent in a simple client-server interaction on a

    connection-oriented network.

  • 8/3/2019 rokoi

    46/74

    Services to Protocols Relationship

    The relationship between a service and a protocol.

  • 8/3/2019 rokoi

    47/74

    Reference Models

    The OSI Reference Model

    The TCP/IP Reference Model

    A Comparison of OSI and TCP/IP A Critique of the OSI Model and Protocols

    A Critique of the TCP/IP Reference Model

    f d l

  • 8/3/2019 rokoi

    48/74

    Reference Models

    The OSI

    referencemodel.

    f d l (2)

  • 8/3/2019 rokoi

    49/74

    Reference Models (2)

    The TCP/IP reference model.

    R f M d l (3)

  • 8/3/2019 rokoi

    50/74

    Reference Models (3)

    Protocols and networks in the TCP/IP model initially.

    C i OSI d TCP/IP M d l

  • 8/3/2019 rokoi

    51/74

    Comparing OSI and TCP/IP Models

    Concepts central to the OSI model

    Services

    Interfaces

    Protocols

    A C i i f h OSI M d l d P l

  • 8/3/2019 rokoi

    52/74

    A Critique of the OSI Model and Protocols

    Why OSI did not take over the world

    Bad timing

    Bad technology Bad implementations

    Bad politics

    B d Ti i

  • 8/3/2019 rokoi

    53/74

    Bad Timing

    The apocalypse of the two elephants.

    A C i i f h TCP/IP R f M d l

  • 8/3/2019 rokoi

    54/74

    A Critique of the TCP/IP Reference Model

    Problems: Service, interface, and protocol not distinguished

    Not a general model

    Host-to-network layer not really a layer No mention of physical and data link layers

    Minor protocols deeply entrenched, hard to replace

    H b id M d l

  • 8/3/2019 rokoi

    55/74

    Hybrid Model

    The hybrid reference model to be used in this book.

    E l N t k

  • 8/3/2019 rokoi

    56/74

    Example Networks

    The Internet

    Connection-Oriented Networks:

    X.25, Frame Relay, and ATM

    Ethernet

    Wireless LANs: 802:11

    Th ARPANET

  • 8/3/2019 rokoi

    57/74

    The ARPANET

    (a) Structure of the telephone system.

    (b)Barans proposed distributed switching system.

    Th ARPANET (2)

  • 8/3/2019 rokoi

    58/74

    The ARPANET (2)

    The original ARPANET design.

    Th ARPANET (3)

  • 8/3/2019 rokoi

    59/74

    The ARPANET (3)

    Growth of the ARPANET (a) December 1969. (b) July 1970.

    (c) March 1971. (d) April 1972. (e) September 1972.

    NSFNET

  • 8/3/2019 rokoi

    60/74

    NSFNET

    The NSFNET backbone in 1988.

    I t t U

  • 8/3/2019 rokoi

    61/74

    Internet Usage

    Traditional applications (19701990)

    E-mail

    News Remote login

    File transfer

    A hit t f th I t t

  • 8/3/2019 rokoi

    62/74

    Architecture of the Internet

    Overview of the Internet.

    ATM Virt al Circ its

  • 8/3/2019 rokoi

    63/74

    ATM Virtual Circuits

    A virtual circuit.

    ATM Virtual Circuits (2)

  • 8/3/2019 rokoi

    64/74

    ATM Virtual Circuits (2)

    An ATM cell.

    The ATM Reference Model

  • 8/3/2019 rokoi

    65/74

    The ATM Reference Model

    The ATM reference model.

    The ATM Reference Model (2)

  • 8/3/2019 rokoi

    66/74

    The ATM Reference Model (2)

    The ATM layers and sublayers and their functions.

    Ethernet

  • 8/3/2019 rokoi

    67/74

    Ethernet

    Architecture of the original Ethernet.

    Wireless LANs

  • 8/3/2019 rokoi

    68/74

    Wireless LANs

    (a) Wireless networking with a base station.

    (b) Ad hoc networking.

    Wireless LANs (2)

  • 8/3/2019 rokoi

    69/74

    Wireless LANs (2)

    The range of a single radio may not cover the entire system.

    Wireless LANs (3)

  • 8/3/2019 rokoi

    70/74

    Wireless LANs (3)

    A multicell 802.11 network.

    Network Standardization

  • 8/3/2019 rokoi

    71/74

    Network Standardization

    Whos Who in the Telecommunications World

    Whos Who in the International Standards World

    Whos Who in the Internet Standards World

    ITU

  • 8/3/2019 rokoi

    72/74

    ITU

    Main sectors Radiocommunications

    Telecommunications Standardization

    Development

    Classes of Members

    National governments

    Sector members

    Associate members

    Regulatory agencies

    IEEE 802 Standards

  • 8/3/2019 rokoi

    73/74

    The 802 working groups. The important ones are

    marked with *. The ones marked with are

    hibernating. The one marked with gave up.

    Metric Units

  • 8/3/2019 rokoi

    74/74

    Metric Units

    The principal metric prefixes.