1 / 83

Net-Centric Computing Division Department of Computer Science Bogor Agricultural University

Net-Centric Computing Division Department of Computer Science Bogor Agricultural University. KOM 312 Komunikasi Data dan Jaringan Komputer. Packet Switching Network. Sri Wahjuni my_juni04(at)ipb.ac.id. agenda. Network-layer Functions Packet Network Topology Network Service Model

fauve
Download Presentation

Net-Centric Computing Division Department of Computer Science Bogor Agricultural University

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Net-Centric Computing Division Department of Computer Science Bogor Agricultural University KOM 312 Komunikasi Data danJaringanKomputer Packet Switching Network Sri Wahjuni my_juni04(at)ipb.ac.id

  2. agenda • Network-layer Functions • Packet Network Topology • Network Service Model • Routing Principles • Shortest Path Routing • QoS in Network Layer swj/11

  3. review • OSI Reference Model • TCP/IP Architecture swj/11

  4. Two views of networks • External view: what services provided to transport layer by a network (i.e. network layer) • Need connection setup or not • What QoSs are provided • Services should be independent from underlying networks so that transport layer can run over any networks as long as the networks provide the services • Internal view: • physical topology, • datagram message transfer or virtual circuit information transfer, • addressing and routing, congestion control. swj/11

  5. Comparisons of two views by examples • Broadcast networks and packet-switched networks • From external view, both networks provides transfer of information between users, not too much different • But from internal view, very different: • A broadcast network (such as LANs) is small, addressing is simple, frame transferred in one hop so no routing is needed • In a packet-switching network, addressing must accommodate large-scale networks and routing is necessary. swj/11

  6. Packet switching • Transfer of information as payload in data packets • Packets undergo random delays & possible loss • Different applications impose differing requirements on the transfer of information swj/11

  7. Network service • Network layer can offer a variety of services to transport layer • Connection-oriented service or connectionless service • Best-effort or delay/loss guarantees swj/11

  8. Network-layer Functions Essential • Routing: mechanisms for determining the set of best paths for routing packets requires the collaboration of network elements • Forwarding: transfer of packets from NE inputs to outputs • Priority & Scheduling: determining order of packet transmission in each NE Optional: congestion control, segmentation & reassembly, security swj/11

  9. agenda • Network-layer Functions • Packet Network Topology • Network Service Model • Routing Principles • Shortest Path Routing • QoS in Network Layer swj/11

  10. Access multiplexer swj/11

  11. Local Area Network LAN 1 Bridge swj/11 LAN 2

  12. Intradomain and interdomain swj/11

  13. Key Role of Routing How to get packet from here to there? • Decentralized nature of Internet makes routing a major challenge • Interior gateway protocols (IGPs) are used to determine routes within a domain • Exterior gateway protocols (EGPs) are used to determine routes across domains • Routes must be consistent & produce stable flows • Scalability required to accommodate growth • Hierarchical structure of IP addresses essential to keeping size of routing tables manageable swj/11

  14. agenda • Network-layer Functions • Packet Network Topology • Network Service Model • Routing Principles • Shortest Path Routing • QoS in Network Layer swj/11

  15. Message switching swj/11

  16. Message switching delay Source T t Switch 1 t  Switch 2 t swj/11 t Destination Delay Minimum Delay = 3 + 3T, : propagation delay (umumnya panjang hop/kecepatan cahaya) T: message transmission time

  17. Datagram packet switching • Messages broken into smaller units (packets) • Source & destination addresses in packet header • Connectionless, packets routed independently • Packet may arrive out of order • Pipelining of packets across network can reduce delay, increase throughput • Lower delay that message switching, suitable for interactive traffic swj/11

  18. Datagram Packet Switching Delay Assume three packets corresponding to one message traverse same path τ • Minimum Delay = 3τ + 5(T/3) (single path assumed) • Additional queuing delays possible at each link • Packet pipelining enables message to arrive sooner T swj/11

  19. Delay for k-Packet Message over L Hops Source t 1 3 2 t 3 1 2 t 1 2 3 t swj/11 L hops 3 hops 3 + 2(T/3) first bit received L + (L-1)P first bit received 3 + 3(T/3) first bit released L + LP first bit released 3 + 5 (T/3) last bit released L + LP + (k-1)P last bit released where T = k P ; P disebut delay transmisi

  20. datagram vs message switching • Delay in message switching : L + L(kP) • Delay in packet switching (k packets): L + LP + (k-1)P • Additional delay in message switching : P(k-1)(L-1) swj/11

  21. Routing Tables in connectionless packet switching • Route determined by table lookup • Routing decision involves finding next hop in route to given destination • Routing table has an entry for each destination • specifying output port that leads to next hop • Size of table becomes impractical for very large number of destinations swj/11

  22. Example: Internet Routing • Internet protocol uses datagram packet switching across networks • Networks are treated as data links • Hosts have two-part IP address: • Network address + Host address • Routers do table lookup on network address • This reduces size of routing table swj/11

  23. Virtual-Circuit Packet switching • Network-layer connection-oriented service • Call set-up phase sets ups pointers in fixed path along network • All packets for a connection follow the same path • Abbreviated header identifies connection on each link • Packets queue for transmission • Variable bit rates possible, negotiated during call set-up • Delays variable, cannot be less than circuit switching swj/11

  24. Connection Setup • Signaling messages propagate as route is selected • Signaling messages identify connection and setup tables in switches • Typically a connection is identified by a local tag, Virtual Circuit Identifier (VCI) • Each switch only needs to know how to relate an incoming tag in one input to an outgoing tag in the corresponding output • Once tables are setup, packets can flow along path swj/11

  25. Connection Setup Delay • Connection setup delay is incurred before any packet can be transferred • Delay is acceptable for sustained transfer of large number of packets • This delay may be unacceptably high if only a few packets are being transferred swj/11

  26. VC implementation A VC consists of: • Path from source to destination • VC numbers, one number for each link along path • Entries in forwarding tables in routers along path • Packet belonging to VC carries a VC number. • VC number must be changed on each link. • New VC number comes from forwarding table swj/11

  27. VC Forwarding table 􀁺 Each input port of packet switch has a forwarding table 􀁺 Lookup entry for VCI of incoming packet 􀁺 Determine output port (next hop) and insert VCI for next link 􀁺 Very high speeds are possible 􀁺 Table can also include priority or other information about how packet should be treated swj/11

  28. agenda • Network-layer Functions • Packet Network Topology • Network Service Model • Routing Principles • Routing algorithm • Routing tables • Hierarchical routing • Flooding and Deflection Routing • Shortest Path Routing • QoS in Network Layer swj/11

  29. Routing Algorithm Requirements • Responsiveness to changes • Topology or bandwidth changes, congestion • Rapid convergence of routers to consistent set of routes • Freedom from persistent loops • Optimality • Resource utilization, path length • Robustness • Continues working under high load, congestion, faults, equipment failures, incorrect implementations • Simplicity • Efficient software implementation, reasonable processing load swj/11

  30. Routing algorithm classification Centralized vs Distributed Routing • Centralized Routing • All routes determined by a central node • All state information sent to central node • Problems adapting to frequent topology changes • Does not scale • Distributed Routing • Routes determined by routers using distributed algorithm • State information exchanged by routers • Adapts to topology and other changes • Better scalability swj/11

  31. Routing algorithm classification -2 Static vs Dynamic Routing • Static Routing • Set up manually, do not change; requires administration • Works when traffic predictable & network is simple • Used to override some routes set by dynamic algorithm • Used to provide default router • Dynamic Routing • Adapt to changes in network conditions • Automated • Calculates routes based on received updated network state information swj/11

  32. Routing Tables in Datagram swj/11

  33. Routing table in Virtual-Circuit swj/11 • Route determined during connection setup • Tables in switches implement forwarding that realizes selected route

  34. Routing Tables in VC - cont swj/11

  35. Non-Hierarchical Addresses andRouting • No relationship between addresses & routing proximity • Routing tables require 16 entries each swj/11

  36. Hierarchical Addresses andRouting • Prefix indicates network where host is attached • Routing tables require 4 entries each swj/11

  37. flooding • Send a packet to all nodes in a network • No routing tables available • Need to broadcast packet to all nodes (e.g. to propagate link state information) • Approach • Send packet on all ports except one where it arrived • Exponential growth in packet transmissions swj/11

  38. swj/11 Flooding is initiated from Node 1: Hop 1 transmissions

  39. swj/11 Flooding is initiated from Node 1: Hop 2 transmissions

  40. Flooding is initiated from Node 1: Hop 3 transmissions swj/11

  41. Limited Flooding • Time-to-Live field in each packet limits number of hops to certain diameter • Each switch adds its ID before flooding; discards repeats • Source puts sequence number in each packet; switches records source address and sequence number and discards repeats swj/11

  42. Deflection Routing • Network nodes forward packets to preferred port • If preferred port busy, deflect packet to another port • Works well with regular topologies • Manhattan street network • Rectangular array of nodes • Nodes designated (i,j) • Rows alternate as one-way streets • Columns alternate as one-way avenues • Bufferless operation is possible • Proposed for optical packet networks • All-optical buffering currently not viable swj/11

  43. Example: Node (0,2)→(1,0) Tunnel from last column to first column or vice versa swj/11

  44. Example: busy node swj/11

  45. agenda • Network-layer Functions • Packet Network Topology • Network Service Model • Routing Principles • Shortest Path Routing • QoS in Network Layer swj/11

  46. Shortest Paths & Routing • Many possible paths connect any given source and to any given destination • Routing involves the selection of the path to be used to accomplish a given transfer • Typically it is possible to attach a cost or distance to a link connecting two nodes • Routing can then be posed as a shortest path problem swj/11

  47. Routing Metrics Means for measuring desirability of a path • Path Length = sum of costs or distances • Possible metrics • Hop count: rough measure of resources used • Delay: sum of delays along path; complex & dynamic • Bandwidth: “available capacity” in a path • Load: Link & router utilization along path (congestion) • Cost: $$$ swj/11

  48. Shortest Path Approaches Distance Vector Protocols • Neighbors exchange list of distances to destinations • Best next-hop determined for each destination • Ford-Fulkerson (distributed) shortest path algorithm Link State Protocols • Link state information flooded to all routers • Routers have complete topology information • Shortest path (& hence next hop) calculated • Dijkstra (centralized) shortest path algorithm swj/11

  49. Iterative, asynchronous: each local iteration caused by: local link cost change DV update message from neighbor Distributed: each node notifies neighbors only when its DV changes neighbors then notify their neighbors if necessary wait for (change in local link cost of msg from neighbor) recompute estimates if DV to any dest has changed, notify neighbors Distance Vector Algorithm Each node: swj/11

  50. Bellman-Ford Algorithm • Now consider parallel computations for all destinations d • Initialization • Each node has 1 row for each destination d • Distance of node d to itself is zero: Dd(d)=0 • Distance of other node j to d is infinite: Dj(d)= ∝ , for j ≠ d • Next node nj = -1 since not yet defined • Send Step • Send new distance vector to immediate neighbors across local link • Receive Step • For each destination d, find the next hop that gives the minimum distance to d, • Minj { Cij+ Dj(d) } • Replace old (nj, Di(d)) by new (nj*, Dj*(d)) if new next node or distance found • Go to send step swj/11

More Related