• Keine Ergebnisse gefunden

1. Communication Networks and Computer Networks:

N/A
N/A
Protected

Academic year: 2022

Aktie "1. Communication Networks and Computer Networks: "

Copied!
23
0
0

Wird geladen.... (Jetzt Volltext ansehen)

Volltext

(1)

www.kom.tu-darmstadt.de www.httc.de

Communication Networks II

Prof. Dr.-Ing. Ralf Steinmetz

TU Darmstadt - Technische Universität Darmstadt,

Dept. of Electrical Engineering and Information Technology, Dept. of Computer Science KOM - Multimedia Communications Lab

Merckstr. 25, D-64283 Darmstadt, Germany, Ralf.Steinmetz@KOM.tu-darmstadt.de Tel.+49 6151 166151, Fax. +49 6151 166152

httc - Hessian Telemedia Technology Competence-Center e.V Merckstr. 25, D-64283 Darmstadt, Ralf.Steinmetz@httc.de

Introduction and Overview

(2)

www.kom.tu-darmstadt.de www.httc.de

Scope

KN III (Mobile Networking), Distributed Multimedia Systems (MM I and MM II), Telecooperation II,III. ...; Embedded Systems

L5

Applications

Terminal access File access E-mail Web Peer-to- Peer Inst.-Msg.

IP-Tel.

Application Layer (Anwendung)

SIP &

H.323

L4 Transport Layer (Transport)

Internet:

UDP, TCP, SCTP

Netw. Transitions Security Addressing

Transport QoS - RTP

L3 Network Layer (Vermittlung)

Internet:

IP

Network QoS

L2 Data Link Layer (Sicherung)

LAN, MAN High-Speed LAN

L1 Physical Layer

(Bitübertragung) Queueing Theory & Network Calculus Introduction

Legend: KN I KN II

(3)

www.kom.tu-darmstadt.de www.httc.de

Overview

1. Communication Networks and Computer Networks: Objectives 2. ISO Reference Model for Open Systems

3. Layer Concepts

4. 5-Layer-Model Used Here

(4)

www.kom.tu-darmstadt.de www.httc.de

1. Communication Networks and Computer Networks:

Objectives

Shared usage of resources

(resource sharing: programs, data, devices)

share data

share load

share operation

High reliability

Cost reduction

e.g. shared usage of a data server (a.o. with X-terminal)

Extensibility

(5)

www.kom.tu-darmstadt.de www.httc.de

2. ISO Reference Model for Open Systems

Problem: engineering communication means

multitude of partially very complex tasks

interaction of differing systems and components Simplification:

to introduce abstraction levels of varying functionalities

general module, preferable: layer, level

Example (here using OSI-OSI reference model, later 5 layers

biologists with translator and FAX-office

Germany Argentina

peer to peer protocol

I love animals Ich liebe

Tiere

Fax no...

I love animals

I love animals

yo amo animales

Fax no...

I love animals

(6)

www.kom.tu-darmstadt.de www.httc.de

OSI (Open Systems Interconnection) Reference Model

model for layered communication systems

defines fundamental concepts and terminology

defines 7 layers and their functionalitites

7 Application Layer

6 Presentation Layer

5 Session Layer

4 Transport Layer

3 Network Layer

2 Data Link Layer

1 Physical Layer

(7)

www.kom.tu-darmstadt.de www.httc.de

OSI Architecture

Presentation

Transport Network Datalink Physical Session Application

End system

6

4 3 2 1 5 7

End system peer to peer protocol

Medium End system

6

4 3 2 1 5 7

End system

6

4 3 2 1 5 7

3 2 1

Intermediate system

(8)

www.kom.tu-darmstadt.de www.httc.de

OSI Layers: Functions

Layer Function

1 Physical

sending bit 1 is also received as bit 1 (and not as bit 0):

mechanics: connector type, cable/medium,..

electronics: voltage, bit length,..

procedural:

unidirectional or simultaneously bidirectional

initiating and terminating connections

2

Data Link

reliable data transfer between neighbouring stations with frames

introducing data frames and acknowledgement frames

error recognition and correction within the frame:

manipulation, loss, duplication

fast sender, slow receiver: flow control

distribution network requires access control:

Medium Access Control (MAC)

(9)

www.kom.tu-darmstadt.de www.httc.de

3 Network

connection endsystem with endsystem (subnets) with packets

routing, i.e. among others

fixed, defined during connect, dynamic

congestion control (too many packets on one path)

quality of service dependent

varying subnets, Internetworking, i.e. among others

addressing and packet size

comment distribution network: routing often simplified or non-existent, i.e. this layer often does not exist here

example: IP

4

Transport

connection end/source (application/process) to end/drain (application/process)

optimize required quality of service and costs

1 L4 connection corresponds to 1 L3 connection

increase througput: 1 L4 connection uses several L3 connections (splitting)

minimize costs: several L4 connections multiplexed onto 1 L3 connection

process addressing, connection management

fast sender, slow receiver: flow control

Layer Function

(10)

www.kom.tu-darmstadt.de www.httc.de

5 Session

support "session" over a longer period

synchronization

(during interrupted connection)

token management

(coordinate simultaneous processing of different applications)

6

Presenta- tion

data presentation independent from the end system

negotiating the data structure,

conversion into a global data structure

examples:

data types: date, integer, currency,

ASCII, unicode,..

7

Application

application related services

example:

electronic mail, directory service

file transfer, WWW, ..

Layer Function

(11)

www.kom.tu-darmstadt.de www.httc.de

3. Layer Concepts

N-Layer

abstraction layer with defined tasks N-Entity

active elements in a layer

process or intelligent I/O module

peer entities: corresponding entities on different systems N-Service Access Point, N-SAP

service identification N-Protocol:

amount of rules for transfering data between N-entities

(N+1)-entity (N+1)-entity

(N)-entity (N)-entity (N)-protocol

(N)-SAPS

(12)

www.kom.tu-darmstadt.de www.httc.de

Layer Concepts: Service and Protocol (2)

Service

amount of primitives/operations/functions which one layer offers to the next superior one

characterized by the "interface"

does not reveal anything about the implementation

analogy: programming, service corresponds to

abstract data type

object

Protocol

rules for the syntax (format) and the semantics (contents) of the data transfer (frames, packet, message) occuring between the peer entities

analogy: programming, protocol corresponds to

realizing the data type (procedures,etc.)

(13)

www.kom.tu-darmstadt.de www.httc.de

Layer Concepts: Service and Protocol (3)

Service Provider Service User

(N)-service user

(N)-service entity (N)-service

entity

(N)-service user (N)-service access point

(N)-service provider

(N-1)-service provider (N-1)-service access point

(N)-service protocol specification

(N)-service

(14)

www.kom.tu-darmstadt.de www.httc.de

3.1 Connection Oriented Service

Connection oriented:

3 phases:

1. connect

2. data transfer 3. disconnect

Analog: telephone service

(N)-connection

(N+1)-entity (N+1)-entity

(15)

www.kom.tu-darmstadt.de www.httc.de

3.2 Connectionless Service

Connectionless (Datagram Service)

transfer of isolated unit data Analog: letter delivery

applications (preferentially):

one-time data transfer

short duration

(16)

www.kom.tu-darmstadt.de www.httc.de

3.3 Communication between Layers

2

entitiesPeer Peer entities

N+1 Layer

N Layer

N-1 Layer Service

Service Service

primitives Service

primitives

= Logical Peer-Peer communication 1

2 2

2

1

(17)

www.kom.tu-darmstadt.de www.httc.de

Service Primitives

Service primitives

define a service in an abstract manner

are usually parametrized

Types:

service. REQUEST

service. INDICATION

service. RESPONSE

service. CONFIRMATION

Example:

Connect. REQUEST Connect. INDICATION Connect. RESPONSE

Connect. CONFIRMATION

(18)

www.kom.tu-darmstadt.de www.httc.de

3.4 Confirmed Service

accepting user

service.

CONFIRMATION time

requesting user

service.

RESPONSE service.

INDICATION

SAP SAP

Connect.

REQUEST

time

Connect.

INDICATION

SAP SAP

1: Maria dials Tom’s phone

number

2: Tom’s phone rings

Example:

service. REQUEST

.

(19)

www.kom.tu-darmstadt.de www.httc.de

3.5 Unconfirmed Service

accepting user

service. REQUEST time

requesting user

service.

INDICATION

SAP SAP

accepting user

Unitdata.

REQUEST time

requesting user

Unitdata.

INDICATION

SAP SAP

Example:

(20)

www.kom.tu-darmstadt.de www.httc.de

4. 5-Layer-Model Used Here

ISO-OSI

standardized too late

implementations usually worse than those of Internet protocols

in general, however, mainly good concepts TCP/IP (Internet)

TCP/IP already prevalent, SMTP also, now e.g. WWW

integrated into UNIX To be considered herein:

Layer Function

5 Application application related services incl. ISO-OSI L5 and L6 (as far as necessary)

4 Transport connection end/source (application/process) to end/drain (application/process)

3 Network connection end-system to end-system

(21)

www.kom.tu-darmstadt.de www.httc.de

5-Layer-Model: Some Details

KN III (Mobile Networking), Distributed Multimedia Systems (MM I and MM II), Telecooperation II,III. ...; Embedded Systems

L5

Applications

Terminal access File access E-mail Web Peer-to- Peer Inst.-Msg.

IP-Tel.

Application Layer (Anwendung)

SIP &

H.323

L4 Transport Layer (Transport)

Internet:

UDP, TCP, SCTP

Netw. Transitions Security Addressing

Transport QoS - RTP

L3 Network Layer (Vermittlung)

Internet:

IP

Network QoS

L2 Data Link Layer (Sicherung)

LAN, MAN High-Speed LAN

L1 Physical Layer

(Bitübertragung) Queueing Theory & Network Calculus Introduction

Legend: KN I KN II

(22)

www.kom.tu-darmstadt.de www.httc.de

5-Layer-Model: Some Details (2)

KN III (Mobile Networking), Distributed Multimedia Systems (MM I and MM II), Telecooperation II,III. ...; Embedded Systems

L5

Applications

Terminal access File access E-mail Web Peer-to- Peer Inst.-Msg.

IP-Tel.

Application Layer (Anwendung)

SIP &

H.323

L4 Transport Layer (Transport)

Internet:

UDP, TCP, SCTP

Netw. Transitions Security Addressing

Transport QoS - RTP

L3 Network Layer (Vermittlung)

Internet:

IP

Network QoS

L2 Data Link Layer (Sicherung)

LAN, MAN High-Speed LAN

L1 Physical Layer

(Bitübertragung) Queueing Theory & Network Calculus Introduction

(23)

www.kom.tu-darmstadt.de www.httc.de

Layers: Conception vs. Implementation

Concept

each layer has its own process or a multitude of processes (entities, because of multiplexing/splitting)

buffers between layers (incl. buffer management) Experiences with communication systems

changing the context of processes takes a lot of time

most of the processing time is used up for copying (despite e.g. DMA)

adapter -> main memory

within the main memory (layer to layer)

main memory -> adapter

difficult to review for correctness

parallelism, many potential states Implementation

pooling several layers to one process

using dedicated buffer management

copying is logical copying (pointer operations)

specification methods with conformance testing

Referenzen

ÄHNLICHE DOKUMENTE

– Impact of node failures on lookup failure rate. – lookup failure rate roughly equivalent to node failure

Jeder Knoten leitet ein Broadcast-Paket mit RangeHash X an alle ihm bekannten Knoten (mit aktualisiertem Range) zwischen seiner ID und X weiter.. Der Startknoten sendet

Basics of peer-to-peer systems: motivation, characteristics, and examples Distributed object location and routing in peer-to-peer systems3. Unstructured

Napster provided a service where they indexed and stored file information that users of Napster made available on their computers for others to download, and the files

ƒ Peer-to-Peer: Anwendungen, die Ressourcen am Rand des Internets ohne feste IP-Adressen ausnutzen Ressourcen: Speicherkapazität, CPU-Zeit, Inhalte, menschliche Präsenz.. Î

Eine Anfrage Q ergibt einen Treffer bei einem Dateinamen F, wenn die Wörter in Q eine Teilmenge von F sind.. Beispiel.: „Beatles Submarine“ ist ein Treffer „Beatles

 Suche von Daten = Routing zu verantwortlichem Knoten.  Verantwortlicher Knoten muss nicht vorab

To our best knowledge, there is no sport analysis system that uses a network of conventio- nal, low-cost machines for processing streaming sensor data and that shows the results on