Network Organization Concepts Seventh Edition Chapter 9 Network

  • Slides: 71
Download presentation
Network Organization Concepts Seventh Edition Chapter 9 Network Organization Concepts

Network Organization Concepts Seventh Edition Chapter 9 Network Organization Concepts

Learning Objectives After completing this chapter, you should be able to describe: • Several

Learning Objectives After completing this chapter, you should be able to describe: • Several different network topologies—including the star, ring, bus, tree, and hybrid—and how they connect numerous hosts to the network • Several types of networks: LAN, MAN, WAN, and wireless LAN • The difference between circuit switching and packet switching, and examples of everyday use that favor each Understanding Operating Systems, 7 e 2

Learning Objectives (cont'd. ) • Conflict resolution procedures that allow a network to share

Learning Objectives (cont'd. ) • Conflict resolution procedures that allow a network to share common transmission hardware and software effectively • The two transport protocol models (OSI and TCP/IP) and how the layers of each one compare Understanding Operating Systems, 7 e 3

Basic Terminology • Network – Collection of loosely coupled processors – Interconnected by communication

Basic Terminology • Network – Collection of loosely coupled processors – Interconnected by communication links • Using cables, wireless technology, both – Common goal • Provide convenient resource sharing • Control access – General network configurations • Network operating system (NOS) • Distributed operating system Understanding Operating Systems, 7 e 4

Basic Terminology (cont'd. ) • Network operating system (NOS) – Networking capability • Added

Basic Terminology (cont'd. ) • Network operating system (NOS) – Networking capability • Added to single-user operating system – Users aware of specific computers and resources in network – Access resources • Log on to remote host • Data transfer from remote host Understanding Operating Systems, 7 e 5

Basic Terminology (cont'd. ) • Distributed operating system – Users not aware of specific

Basic Terminology (cont'd. ) • Distributed operating system – Users not aware of specific computers and resources in network • Access remote resources as if local – Good control: distributed computing systems • Allows unified resource access – Total view across multiple computer systems • No local dependencies for controlling and managing resources – Cooperative management Understanding Operating Systems, 7 e 6

Basic Terminology (cont'd. ) • Distributed operating system (cont'd. ) – Comprised of four

Basic Terminology (cont'd. ) • Distributed operating system (cont'd. ) – Comprised of four managers with a wider scope (figure 9. 1) This five-sided pyramid graphically illustrates how the five managers in a networked system work together and support the user interface. © Cengage Learning 2014 Understanding Operating Systems, 7 e 7

Basic Terminology (cont'd. ) • Distributed operating system (cont'd. ) – Advantages over traditional

Basic Terminology (cont'd. ) • Distributed operating system (cont'd. ) – Advantages over traditional systems • • • Easy and reliable resource sharing Faster computation Adequate load balancing Good reliability Dependable communications among network users Understanding Operating Systems, 7 e 8

Basic Terminology (cont'd. ) • Remote – Other processors and resources • Local –

Basic Terminology (cont'd. ) • Remote – Other processors and resources • Local – Processor’s own resources • Site – Specific location in network • One or more computers • Host – Specific computer system at site • Services and resources used from remote locations Understanding Operating Systems, 7 e 9

Basic Terminology (cont'd. ) • Node – Name assigned to computer system • Provides

Basic Terminology (cont'd. ) • Node – Name assigned to computer system • Provides identification (figure 9. 2) Clients request data or services from the host server and wait for the response. If the client host has resources needed by the server host, the roles can be reversed. © Cengage Learning 2014 Understanding Operating Systems, 7 e 10

Network Topologies • Physically or logically connected sites • Most common geometric arrangements: star,

Network Topologies • Physically or logically connected sites • Most common geometric arrangements: star, ring, bus, tree, hybrid • Topology trade-offs – – Need for fast communication among all sites Tolerance of failure at a site or communication link Cost of long communication lines Difficulty connecting one site to large number of other sites Understanding Operating Systems, 7 e 11

Network Topologies (cont'd. ) • Four basic criteria in design consideration – Basic cost

Network Topologies (cont'd. ) • Four basic criteria in design consideration – Basic cost • Expense required to link various sites in system – Communications cost • Time required to send message from one site to another – Reliability • Assurance of site communication if link or site fails – User environment • Critical parameters for successful business investment Understanding Operating Systems, 7 e 12

Star • Transmitted data from sender to receiver – Passes through central controller •

Star • Transmitted data from sender to receiver – Passes through central controller • Hub or centralized topology • Advantages – Permits easy routing – Easy access control to network • Disadvantages – Requires extremely reliable central site – Requires ability to handle all network traffic • No matter how heavy Understanding Operating Systems, 7 e 13

(figure 9. 3) Star topology. Hosts are connected to each other through a central

(figure 9. 3) Star topology. Hosts are connected to each other through a central controller, which assumes all responsibility for routing messages to the appropriate host. Data flow between the hosts and the central controller is represented by dotted lines. Direct host-to-host communication isn’t permitted. © Cengage Learning 2014 Understanding Operating Systems, 7 e 14

Ring • Sites connected in closed loop • May connect to other networks –

Ring • Sites connected in closed loop • May connect to other networks – Using bridge: same protocols – Using gateway: different protocols • Data transmitted in packets – Source and destination address fields • Packet passed from node to node – One direction only • Every node must be functional – Bypass failed node needed for properation Understanding Operating Systems, 7 e 15

(figure 9. 4) Double loop computer Ring topology. Hosts are connected to each other

(figure 9. 4) Double loop computer Ring topology. Hosts are connected to each other in a circular fashion with data flowing in one direction only, shown here as dotted lines. The network can be connected to other networks via a bridge or gateway. © Cengage Learning 2014 Understanding Operating Systems, 7 e 16

(figure 9. 5) Double loop computer network using a ring topology. Packets of data

(figure 9. 5) Double loop computer network using a ring topology. Packets of data flow in both directions. © Cengage Learning 2014 Understanding Operating Systems, 7 e 17

(figure 9. 6) Multiple rings bridged together. Three rings connected to each other by

(figure 9. 6) Multiple rings bridged together. Three rings connected to each other by two bridges. This variation of ring topology allows several networks with the same protocol to be linked together. © Cengage Learning 2014 Understanding Operating Systems, 7 e 18

Bus • • Sites connect to single communication line Messages circulate in both directions

Bus • • Sites connect to single communication line Messages circulate in both directions One site sends messages at a time successfully Need control mechanism – Prevent collisions • Data passes directly from one device to another – Data may be routed to end point controller at end of the line Understanding Operating Systems, 7 e 19

(figure 9. 7) Bus topology. Hosts are connected to one another in a linear

(figure 9. 7) Bus topology. Hosts are connected to one another in a linear fashion. Data flows in both directions from host to host and is turned around when it reaches an end point controller. © Cengage Learning 2014 Understanding Operating Systems, 7 e 20

Tree • Collection of buses connected by branching cable – No closed loops •

Tree • Collection of buses connected by branching cable – No closed loops • Designers create networks using bridges • Message from any site – Received by all other sites until reaching end point • Message reaching end point controller without acceptance – End point controller absorbs message • Advantage – Message traffic still flows even if single node fails Understanding Operating Systems, 7 e 21

(figure 9. 8) Tree topology. Data flows up and down the branches of the

(figure 9. 8) Tree topology. Data flows up and down the branches of the trees and is absorbed by controllers at the end points. Gateways help minimize differences between the protocol used on one part of the network and the different protocol used on the branch with host 7. © Cengage Learning 2014 Understanding Operating Systems, 7 e 22

Hybrid • Strong points of each topology in combination – Effectively meet system communications

Hybrid • Strong points of each topology in combination – Effectively meet system communications requirements (figure 9. 9) Hybrid topology, version 1. This network combines a star and a ring, connected by a bridge. Hosts 5, 6, 7, and 8 are located on the ring. © Cengage Learning 2014 Understanding Operating Systems, 7 e 23

(figure 9. 10) Hybrid topology, version 2. This network combines star and bus topologies.

(figure 9. 10) Hybrid topology, version 2. This network combines star and bus topologies. Hosts 5, 6, 7, and 8 are located on the bus. © Cengage Learning 2014 Understanding Operating Systems, 7 e 24

Network Types • Grouping – According to physical distances covered • Characteristics are blurring

Network Types • Grouping – According to physical distances covered • Characteristics are blurring • Network types – Local area networks (LAN) – Metropolitan area networks (MAN) – Wide area networks (WAN) Understanding Operating Systems, 7 e 25

Personal Area Network (PAN) • Information technology – Operating within 10 m radius –

Personal Area Network (PAN) • Information technology – Operating within 10 m radius – Centered around one person: body area network (BAN) • Wearable technology – Gloves, caps, monitors, etc. • May be connected to LAN Understanding Operating Systems, 7 e 26

Local Area Network • Single office building, campus, similarly enclosed environment – Single organization

Local Area Network • Single office building, campus, similarly enclosed environment – Single organization owns/operates • Communicate through common communication line • Communications not limited to local area only – Component of larger communication network – Easy access to outside • Through bridge or gateway Understanding Operating Systems, 7 e 27

Local Area Network (cont'd. ) • Bridge – Connects two or more geographically distant

Local Area Network (cont'd. ) • Bridge – Connects two or more geographically distant LANs – Same protocols • Example: connection of two LANs using Ethernet • Gateway – Connects two or more LANs or systems – Different protocols • Translates one network protocol into another • Resolves hardware and software incompatibilities • Systems network architecture (SNA) gateway connecting microcomputer network to mainframe host Understanding Operating Systems, 7 e 28

Local Area Network (cont'd. ) • Data rates: 100 Mbps to more than 40

Local Area Network (cont'd. ) • Data rates: 100 Mbps to more than 40 Gbps • Close physical proximity – Very high-speed transmission • Star, ring, bus, tree, and hybrid – Normally used • Transmission medium: varies • Factors determining transmission medium – Cost, data rate, reliability, number of devices supported, and distance between units Understanding Operating Systems, 7 e 29

Metropolitan Area Network • Configuration spanning area larger than LAN – Several blocks of

Metropolitan Area Network • Configuration spanning area larger than LAN – Several blocks of buildings to entire city • Not exceeding 100 km circumference • May be owned and operated as public utilities – Means for internetworking several LANs • High-speed network often configured as a logical ring Understanding Operating Systems, 7 e 30

Wide Area Network • Interconnects communication facilities: different parts of a country or world

Wide Area Network • Interconnects communication facilities: different parts of a country or world – Operated as part of public utility • Uses common carriers’ communications lines – Telephone companies • Uses broad range of communication media – Satellite, microwaves • WANs generally slower than LANs – Examples: ARPANET (first WAN), Internet (most widely recognized WAN) Understanding Operating Systems, 7 e 31

Wireless Local Area Network • LAN using wireless technology to connect computers or workstations

Wireless Local Area Network • LAN using wireless technology to connect computers or workstations – Located within range of network • Security vulnerabilities – Open architecture; difficulty keeping intruders out Understanding Operating Systems, 7 e 32

(table 9. 1) Comparison of IEEE standards for wireless networks. © Cengage Learning 2014

(table 9. 1) Comparison of IEEE standards for wireless networks. © Cengage Learning 2014 Understanding Operating Systems, 7 e 33

Wireless Local Area Network (cont'd. ) • Wi. MAX standard 802. 16 – High

Wireless Local Area Network (cont'd. ) • Wi. MAX standard 802. 16 – High bandwidth, long distances (figure 9. 11) In a WLAN, wireless enabled nodes connect to the cabled LAN via access points (APs) if they are located within the range of the device sending the signal. © Cengage Learning 2014 Understanding Operating Systems, 7 e 34

Software Design Issues • • How do sites use addresses to locate other sites?

Software Design Issues • • How do sites use addresses to locate other sites? How are messages routed and how are they sent? How do processes communicate with each other? How are conflicting demands for resources resolved? Understanding Operating Systems, 7 e 35

Addressing Conventions • Addressing protocols – Fulfill need to uniquely identify users – Closely

Addressing Conventions • Addressing protocols – Fulfill need to uniquely identify users – Closely related to site network topology and geographic location • Distinction between local and global name – Local name within its own system – Global name outside its own system • Must follow standard name conventions (length, formats) Understanding Operating Systems, 7 e 36

Addressing Conventions (cont'd. ) • Example: Internet address – someone@icarus. lis. pitt. edu –

Addressing Conventions (cont'd. ) • Example: Internet address – someone@icarus. lis. pitt. edu – Periods and @ sign: separate components – Domain Name Service (DNS) protocol • General-purpose data query service • Hierarchical • Domain names read left to right – – Logical user to host machine Host machine to net machine Net machine to cluster Cluster to network Understanding Operating Systems, 7 e 37

Routing Strategies • Router – Internetworking device (primarily software-driven) – Directs traffic • Between

Routing Strategies • Router – Internetworking device (primarily software-driven) – Directs traffic • Between two different types of LANs • Between two network segments (different protocol addresses) – Network layer operation – Role changes (network designs changes) • Connects sites – To other sites and Internet Understanding Operating Systems, 7 e 38

Routing Strategies (cont'd. ) • Router functions – Securing information • Generated in predefined

Routing Strategies (cont'd. ) • Router functions – Securing information • Generated in predefined areas – Choosing fastest route • From one point to another – Providing redundant network connections • Routing protocol considerations – Addressing, address resolution, message format, error reporting • Address resolution – Maps hardware address Understanding Operating Systems, 7 e 39

Routing Strategies (cont'd. ) • Message formats – Allow performance of protocol functions •

Routing Strategies (cont'd. ) • Message formats – Allow performance of protocol functions • • • Finding new network nodes Determine whether they work (testing) Reporting error conditions Exchanging routing information Establishing connections (transmit data) • Most widely used Internet routing protocols – Routing information protocol (RIP) – Open shortest path first (OSPF) Understanding Operating Systems, 7 e 40

Routing Strategies (cont'd. ) • Routing information protocol (RIP) – Path selection based on

Routing Strategies (cont'd. ) • Routing information protocol (RIP) – Path selection based on node and hop number • Between source and destination – Path with smallest number of hops: always chosen – Advantage • Easy to implement – Disadvantages • No consideration: bandwidth, data priority, network type • Update and reissue routing table: changes or not • Tables propagate: router to router Understanding Operating Systems, 7 e 41

Routing Strategies (cont'd. ) • Open shortest path first (OSPF) – Network state determined

Routing Strategies (cont'd. ) • Open shortest path first (OSPF) – Network state determined first – Transmission path selected – Update messages sent when changes in routing environment occur • Reduces number of messages in internetwork • Reduces message size: not sending entire table – Disadvantages • Increased memory usage • Bandwidth savings offset by higher CPU usage • Shortest path calculation Understanding Operating Systems, 7 e 42

Connection Models • Communication network concerns – Moving data from one point to another

Connection Models • Communication network concerns – Moving data from one point to another – Minimizing transmission costs – Providing full connectivity • Circuit switching – Dedicated communication path • Established between two hosts before transmission begins – Example: telephone system – Disadvantage • Delay before signal transfer begins Understanding Operating Systems, 7 e 43

Connection Models (cont'd. ) • Packet switching • Store-and-forward technique – Before sending message

Connection Models (cont'd. ) • Packet switching • Store-and-forward technique – Before sending message • Divide into multiple equal-sized units (packets) – At destination • Packets reassembled into original long format • Header contains pertinent packet information • Advantages – Greater line efficiency – Users allocate message priority – More flexible and reliable Understanding Operating Systems, 7 e 44

(figure 9. 12) A packet switching network does not require a dedicated connection. It

(figure 9. 12) A packet switching network does not require a dedicated connection. It sends packets using a three-step procedure: (a) divide the data into addressed packets; (b) send each packet toward its destination; (c) and, at the destination, confirm receipt of all packets, place them in order, reassemble the data, and deliver it to the recipient. © Cengage Learning 2014 Understanding Operating Systems, 7 e 45

(table 9. 2) Comparison of circuit and packet switching. © Cengage Learning 2014 Understanding

(table 9. 2) Comparison of circuit and packet switching. © Cengage Learning 2014 Understanding Operating Systems, 7 e 46

Connection Models (cont'd. ) • Path selection methods: datagrams and virtual circuits • Datagrams

Connection Models (cont'd. ) • Path selection methods: datagrams and virtual circuits • Datagrams – Packet destination and sequence number added to information • Uniquely identifying message to owning packet – Each packet handled independently – Route selected as each packet accepted – At destination • All packets of same message reassembled Understanding Operating Systems, 7 e 47

Connection Models (cont'd. ) • Datagrams (cont'd. ) – Diminishes congestion and provides reliability

Connection Models (cont'd. ) • Datagrams (cont'd. ) – Diminishes congestion and provides reliability – Accounts for all packets before delivering message – Receiving node requests retransmission • Lost or damaged packets – Advantages • • Diminishes congestion Sends incoming packets through less heavily used paths More reliability Alternate paths set up upon node failure Understanding Operating Systems, 7 e 48

Connection Models (cont'd. ) • Virtual circuit – Complete path sender to receiver •

Connection Models (cont'd. ) • Virtual circuit – Complete path sender to receiver • Established before transmission starts – All message packets use same route – Several virtual circuits to any other node – Advantages • Routing decision made once: speeds up transmission – Disadvantages • All virtual circuits fail upon one failure • Difficult to resolve congestion: heavy traffic Understanding Operating Systems, 7 e 49

Conflict Resolution • Device sharing requires access control methods – Facilitates equal and fair

Conflict Resolution • Device sharing requires access control methods – Facilitates equal and fair network access • Access control techniques – Round robin – Reservation – Contention • Medium access control protocols – Carrier sense multiple access (CSMA) – Token passing – Distributed-queue; dual bus Understanding Operating Systems, 7 e 50

Conflict Resolution (cont'd. ) • Round robin – Node given certain time to complete

Conflict Resolution (cont'd. ) • Round robin – Node given certain time to complete transmission – Efficient • If many nodes, transmit over long time periods – Substantial overhead • If few nodes, transmit over long time periods • Reservation – Good if lengthy and continuous traffic – Access time on medium divided into slots – Node reserves future time slots Understanding Operating Systems, 7 e 51

Conflict Resolution (cont'd. ) • Reservation (cont'd. ) – Good configuration • Several terminals

Conflict Resolution (cont'd. ) • Reservation (cont'd. ) – Good configuration • Several terminals connected to host through single I/O port • Contention – Better for short and intermittent traffic • No attempt to determine transmission turn; nodes compete for medium access – Works well under light to moderate traffic • Performance breaks down under heavy loads – Advantage: easy implementation Understanding Operating Systems, 7 e 52

Conflict Resolution (cont'd. ) • Carrier sense multiple access (CSMA) – Contention-based protocol –

Conflict Resolution (cont'd. ) • Carrier sense multiple access (CSMA) – Contention-based protocol – Easy implementation – Carrier sense • Node listens to/tests communication medium before transmitting messages • Prevents collision with node currently transmitting – Multiple access • Several nodes connected to same communication line as peers • Same level and equal privileges Understanding Operating Systems, 7 e 53

Conflict Resolution (cont'd. ) • CSMA disadvantages – Collision • Two or more nodes

Conflict Resolution (cont'd. ) • CSMA disadvantages – Collision • Two or more nodes transmit at same instant – Probability of collision increases • As nodes get further apart – Large or complex networks • Less appealing access protocol Understanding Operating Systems, 7 e 54

Conflict Resolution (cont'd. ) • CSMA/CD – Modification of CSMA: includes collision detection –

Conflict Resolution (cont'd. ) • CSMA/CD – Modification of CSMA: includes collision detection – Reduces wasted transmission capacity – Prevents multiple nodes from colliding • Collisions reduced: not completely eliminated – Implemented in Apple’s cabling system: Local. Talk • Collision occurrence involves small packet: not actual data • No guarantee data will reach destination • Any data delivered: ensured to be error-free Understanding Operating Systems, 7 e 55

Conflict Resolution (cont'd. ) • Token passing – Special electronic message (token) • Generated

Conflict Resolution (cont'd. ) • Token passing – Special electronic message (token) • Generated and passed node to node – Only node with token allowed to transmit • Then passes token – Fast access – Collisions nonexistent – Typical topologies • Bus • Ring Understanding Operating Systems, 7 e 56

Conflict Resolution (cont'd. ) • Token bus – Token passed to each node in

Conflict Resolution (cont'd. ) • Token bus – Token passed to each node in turn • Data attached; sent to destination – Receiving node • Copies data; adds acknowledgment; returns packet to sending node – Sending node passes token to next node in sequence – Initial node order determination • Cooperative decentralized algorithm • Then determined by priority based on node activity Understanding Operating Systems, 7 e 57

Conflict Resolution (cont'd. ) • Token bus (cont'd. ) – Higher overhead at each

Conflict Resolution (cont'd. ) • Token bus (cont'd. ) – Higher overhead at each node (than CSMA/CD) – Nodes may have long waits before receiving token • Token ring – Token moves between nodes in turn • One direction only – To send message • Node must wait for free token – Receiving node copies packet message • Sets copied bit indicating successful receipt Understanding Operating Systems, 7 e 58

Conflict Resolution (cont'd. ) • Distributed-queue, dual bus (DQDB) • Dual-bus configuration – Each

Conflict Resolution (cont'd. ) • Distributed-queue, dual bus (DQDB) • Dual-bus configuration – Each bus transports data one direction only – Steady stream of fixed-size slots • Slots generated at end of each bus – Marked as free and sent downstream • Marked busy and written to • Written by nodes ready to transmit – Nodes read and copy data from slots – Continue travel toward end of bus: dissipate Understanding Operating Systems, 7 e 59

(figure 9. 13) Distributed-queue, dual bus protocol. Free slots are generated at one end

(figure 9. 13) Distributed-queue, dual bus protocol. Free slots are generated at one end of each bus and flow in only one direction. Using DQDB, if node C wants to send data to node D, it must wait for a free slot on Bus 1 because the slots are flowing toward node D on that bus. © Cengage Learning 2014 Understanding Operating Systems, 7 e 60

Conflict Resolution (cont'd. ) • DQDB advantages – – Negligible delays under light loads

Conflict Resolution (cont'd. ) • DQDB advantages – – Negligible delays under light loads Predictable queuing under heavy loads Suitable for MANs managing large file transfers Satisfy interactive users’ needs Understanding Operating Systems, 7 e 61

Transport Protocol Standards • Network usage grew quickly (1980 s) • Need to integrate

Transport Protocol Standards • Network usage grew quickly (1980 s) • Need to integrate dissimilar network devices – Different vendors • Creation of single universally adopted network architecture – Two models: OSI reference model and TCP/IP Understanding Operating Systems, 7 e 62

OSI Reference Model • ISO universal network architecture creation • Basis for connecting open

OSI Reference Model • ISO universal network architecture creation • Basis for connecting open systems – Distributed applications processing • “Open” – Connect any two systems conforming to reference model and related standards • Vendor independent • Similar functions collected together – Seven logical clusters (layers) Understanding Operating Systems, 7 e 63

OSI Reference Model (cont'd. ) • Layer 1: physical layer – Describes mechanical, electrical,

OSI Reference Model (cont'd. ) • Layer 1: physical layer – Describes mechanical, electrical, and functional specifications – Transmits bits over communication line • Examples: 100 Base-T, RS 449, CCITT V. 35 • Layer 2: data link layer – Establishes and controls physical communications path before data sent – Transmission error checking – Problem resolution (on other side) • Examples: HDLC and SDLC Understanding Operating Systems, 7 e 64

OSI Reference Model (cont'd. ) • Layer 3: network layer – Addressing and routing

OSI Reference Model (cont'd. ) • Layer 3: network layer – Addressing and routing services moving data through network to destination • Layer 4: transport layer – Maintains reliable data transmission between end users • Example: Transmission Control Protocol (TCP) • Layer 5: session layer – Provides user-oriented connection service – Transfers data over communication lines • Example: TCP/IP Understanding Operating Systems, 7 e 65

OSI Reference Model (cont'd. ) • Layer 6: presentation layer – Data manipulation functions

OSI Reference Model (cont'd. ) • Layer 6: presentation layer – Data manipulation functions common to many applications • Formatting, compression, and encryption • Layer 7: application layer – Application programs, terminals, and computers • Access network – Provides user interface – Formats user data before passing to lower layers Understanding Operating Systems, 7 e 66

TCP/IP Model • Transmission Control Protocol/Internet Protocol (TCP/IP) – – Oldest transport protocol standard

TCP/IP Model • Transmission Control Protocol/Internet Protocol (TCP/IP) – – Oldest transport protocol standard Internet communications basis File-transfer protocol: send large files error-free TCP/IP • Emphasizes internetworking • Provides connectionless services – Organizes communication system: three components • Processes, hosts, and networks – Four layers Understanding Operating Systems, 7 e 67

(figure 9. 15) Comparison of OSI and TCP/ IP models and their corresponding functional

(figure 9. 15) Comparison of OSI and TCP/ IP models and their corresponding functional layers node D on that bus. © Cengage Learning 2014 Understanding Operating Systems, 7 e 68

TCP/IP Model (cont'd. ) • Network access layer (data link layer) – Protocols provide

TCP/IP Model (cont'd. ) • Network access layer (data link layer) – Protocols provide access to communication network – Flow control, error control between hosts, security, and priority implementation performed • Internet layer – Equivalent to OSI model network layer performing routing functions – Implemented within gateways and hosts – Example: Internet Protocol (IP) Understanding Operating Systems, 7 e 69

TCP/IP Model (cont'd. ) • Host-host layer (transport layer) – Transfer data between two

TCP/IP Model (cont'd. ) • Host-host layer (transport layer) – Transfer data between two processes • Different host computers – Error checking, flow control, and manipulate connection control signals – Example: Transmission Control Protocol (TCP) • Process/application layer – Protocols for computer-to-computer resource sharing Understanding Operating Systems, 7 e 70

Conclusion • Network operating systems: coordinate functions – Memory Manager, Processor Manager, Device Manager,

Conclusion • Network operating systems: coordinate functions – Memory Manager, Processor Manager, Device Manager, File Manager – Must meet owners’ reliability requirements • Detect node failures; change routing instructions to bypass; retransmit lost messages successfully • Basic network organization concepts – – Terminology Network topologies and types Software design issues Transport protocol standards Understanding Operating Systems, 7 e 71