Layered Communications Systems & Protocol Engineering · Layered Communications and Protocol...

Layered Communications and Protocol Engineering

Prof. Dr. Jürgen Jasperneite / Prof. Dr. Stefan Witte 1

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

1

Chapter 2.1

Layered Communications Systems & Protocol Engineering

Prof. Dr. Jürgen Jasperneite / Prof. Dr.-Ing. Stefan WitteinIT - Institut Industrial IT Ostwestfalen-Lippe University of Applied Sciences

Course Web Site:http://www.hs-owl.de/fb5/cds/

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

2

Content

• Basic Concepts and Terminology – Services– Protocols

• Layered Architectures– OSI– TCP/IP

• Protocol Engineering



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

3

Services

• Computer networks provides services, which realizes the access to the network by a user.

• Def.: Service– Capability of a computer network to support the

communication and the cooperation between Users

• Example:

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

4

Services

• Computer networks provides services, which realizes the access to the network by a user.

• Def.: Service– Capability of a computer network to support the

communication and the cooperation between Users• Example:

– eMail– WWW



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

5

Type of Services

Source: [Kö2008]

Request

Response

Asymmetrical Service

Symmetrical Service

Communicationrelationship

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

6

Type of Services

• Asymmetrical Services– Services, which are performed by a service provider

(Server) and requested by the service user (Client)– Example: Remote Procedure Call

• Symmetrical Services– provides the service at two or more access points

simultaneously– Example: Communication Services

• Hereafter symmetrical services are the main focus!



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

7

Service Model of a Communication Service

• Two Service Users are mandatory, while the service provider is presented as a single unit.

• Example: Telephone Service: Two Service User and one Service Provider (Network)

Service Provider

Service User Service User

Service Interface

Service Access Point (SAP)

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

8

Service Model of a Communication Service

• Two Service Users are mandatory, while the service provider is presented as a single unit.

• Example: Telephone Service: Two Service User and one Service Provider (Network)



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

9

Service Access Points (SAP)

• Services are offered to the Service User at well-defined Service Access Points (SAP) only.– Analogy:

Telephone Service SAP PhoneMail delivery SAP Postbox

• Every SAP must have its unique address– Analogy: Phone number, zipcode

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

10

Service Access Points (SAP)

• Services are offered to the Service User at well-defined Service Access Points (SAP) only.– Analogy:

Telephone Service SAP

– Mail delivery SAP • Every SAP must have its unique address

– Analogy:



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

11

Service Primitives (SP)

• A Service is realized by service primitives (SP)• Abstract Representation of the interaction between

Service User and Service Provider• SPs doesnt say anything about the implementation of

the service.• The order of SPs at a SAP is not random.• The Syntax of SPs is well defined.

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

12

Service Primitives (SP)

• A Service is realized by • Abstract Representation of the interaction between

Service User and Service Provider• SPs do not say anything about the implementation of

the service.• The order of SPs at a SAP is not random.• The Syntax of SPs is well defined.



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

13

Example: Telephone Service

(Phone Network)

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

14

Example: Telephone Service

Service User

Service Provider (Phone Network)

Service User

SAP

Service Primitive

Service Primitive



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

15

SPs and Sequence Diagram

SAPInstance A Service

SAPInstance B

CONNECT.req()CONNECT.ind()

unconfirmed Servicetime

SAPInstance A Service

SAPInstance B

PDUxx.req() xx.ind()

Confirmed Service

xx.resp(+/-)xx.conf(+/-)time

PDU

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

16

SPs and Sequence Diagram



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

17

Entity (Instance)

Service Provider


Service InterfaceService Access Poin

Entity Entity

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

18

Entity (Instance)

Service Provider




CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

19

Entity (Instance)

• A service of the service provider is performed by Entities (instances)

• Entity:– Active Object of the service provider, which

exchanges messages with its environment.– Entities are related to specific SAPs.

• Analogy: telephone exchange center, Mail center

Entity

SAP

valid invalid

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

20

Entity (Instance)

• A service of the service provider is performed by Entities (instances)

• Entity:– Active Object of the service provider, which

exchanges messages with its environment.– Entities are related to specific SAPs.

• Analogy: telephone exchange center, Mail center



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

21

Service and Protocol

Service Provider



Entity Entity

Protocol

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

22

Service and Protocol

Service Provider



Entity Entity



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

23

Peer-Entity

• A entity interacts with another entity, which is assigned to the SAP of the communication partner– Peer Entity

• The interaction between the entities is based on Messages.

• The procedure of the message exchange is based on rules.– defined by a Communication Protocol– This messages are called Protocol Data Units

(PDU)

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

24

What is a Protocol?

• Term Protocol in our daily life:– Meeting Minutes / Dialog– Convention/Ritual

• Diplomatic Protocol• A Communication Protocol matches the 2nd meaning

– Convention of the behavior– Defined Procedure between two entities, which

repeats forever• No dialog

– Dialog is not predictable not repeatable



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

25

Communication Protocol

• A Communication Protocol is a convention on behavior, which defines the temporal sequence of the interactions between the corresponding entities and the format (Syntax and Semantic) of the exchanged messages.

• „ .. A protocol is a set of conventions and rules governing their use that regulates the communication of an entity under observation with its environment.“[Pop2006]

• Consists of two parts:

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

26

• WEEK 2



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

27

Communication Protocol

• A Communication Protocol is a convention on behavior, which defines the temporal sequence of the interactions between the corresponding entities and the format (Syntax and Semantic) of the exchanged messages.

• „ .. A protocol is a set of conventions and rules governing their use that regulates the communication of an entity under observation with its environment.“[Pop2006]

• Consists of two parts:– Specification of the Sequences– Specification of the PDUs

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

28

Protocol Flow in a Sequence Diagram

(N-1)-SAP(N)-Entity A

(N-1)-SAP(N)-Entity B

(N-1)-CONNECT.req()(N-1)-CONNECT.ind()

time

CR

CC (N-1)-CONNECT.res()

(N-1)-CONNECT.conf()

CR: Connect Request PDUCC: Connect Confirm PDU

Succesful Connection Setup



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

29

Types of Protocols

• Symmetrical Protocols– Same behavior/functionality of both entities– E.g. Protocols with duplex Data Exchange– Most Protocols are symmetrical

• Asymmetric Protocols– Entities with different behavior– E.g. Protocols with unicast Data Exchange

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

30

Principle of Transparency

• The principle of Transparency states, that the content of a PDU is not accessible by the service provider. The Data Unit must be delivered unmodified at the SAP.

• Analogy: privacy of letters• Realization of Transparency

– The delivered Data Unit (SDU: Service Data Unit) will be extended by control informations (PCI: Protocol Control Informations), which are put in front and/or back to the SDU.

– (N)-PDU = (N)-PCI + (N)-SDU

• Most Protocols are using only a prefixed PCI (Header).– In the lower Layer (DL) sometimes also a Suffix

(Trailer)



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

31


• The principle of Transparency states, that the content of a PDU is not accessible by the service provider. The Data Unit must be delivered unmodified at the SAP.

• Analogy: privacy of letters• Realization of Transparency

– The delivered Data Unit (SDU: Service Data Unit) will be extended by control informations (PCI: Protocol Control Informations), which are put in front and/or back to the SDU.

• Most Protocols are using only a prefixed PCI (Header).– In the lower Layer (DL) sometimes also a Suffix

(Trailer)

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

32


UserData

UserData

SDU SDU

Service User

Service ProviderPCI

H

PDU

T H

PDU

T

PCI: Protocol Control InformationSDU: Service Data UnitPDU: Protocol Data Unit



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

33


PCI: Protocol Control InformationSDU: Service Data UnitPDU: Protocol Data Unit

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

34

Layered Communication



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

35

Why Layered Communication?

• Q:How can we tackle complexity?• A: Divide the total problem into

smaller pieces

• Layering (Modularization) as a technique for structuring– similar to structured programming techniques

• Only the functions performed by a module (and not its internal functioning) are known by its users.

• The basic idea:– each layer adds a value to services provided by the set

of lower layers– the highest layer offers the set of services needed to

run distributed applications.

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

36

A daily life example: Taking an airplane trip

Ticket (purchase)

Baggage (check)

Gates (load)

Runway takeoff

Airplane routing

Runway landing

Gates (unload)

Baggage (claim)

Ticket (complain)

Someone ask you to describe a airline system

Source: [Ku2008]

Airplane routing

Airplane routing



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

37


CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

38


Ticket (purchase)

Baggage (check)

Gates (load)

Runway takeoff

Airplane Routing Airplane Routing Airplane Routing Airplane Routing

Ticket (complain)

Baggage (claim)

Gates (unload)

Runway landing

Source: [Ku2008]

Departure Airport Arrival AirportIntermediate Air-trafficControl center



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

39

Hierarchical Service Structure in aLayered Architecture

Service Provider (N-2)

User (N-2) User (N-2)

Service Provider (N-1)

User (N-1) User (N-1)

Service Provider (N)

User ofService (N)

User ofService (N)

System A System B

[Source: Wikipedia]

Matryoshka:A russian nested doll

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

40

Generation of PDUs within a Layered Architecture

N+1

N

N-1

N+1

N

N-1

(N+1) PDU(N)PCI

(N) PDU

(N-1) PDU

(N-1)PCI



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

41

Generation of PDUs within a Layered Architecture

N+1

N

N-1

N+1

N

N-1

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

42

Mapping to (N-1) Layer

• The virtual communication (peer-to-peer) must be mapped to the services of the (N-1) Layer.– Mapping of the (N)-PDUs to (N-1) Service Primitives– Assignment of the (N)-Entity to (N-1)-SAPs

(N)-Entity

(N-1)-SAPvalid invalid



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

43

Mapping to (N-1) Layer

• The virtual communication (peer-to-peer) must be mapped to the services of the (N-1) Layer.– Mapping of the (N)-PDUs to (N-1) Service Primitives– Assignment of the (N)-Entity to (N-1)-SAPs

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

44

Protocol Flow in a Sequence Diagram(Again)

(N-1)-SAP(N)-Entity A

(N-1)-SAP(N)-Entity B

(N-1)-CONNECT.req()(N-1)-CONNECT.ind()

time

CR

CC (N-1)-CONNECT.res()

(N-1)-CONNECT.conf()

CR: Connect Request PDUCC: Connect Confirm PDU

Succesful Connection Setup



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

45

Structure of a (N)-Layer

(N)-COM

(N)-CODEX

(N)-Config

(N-1)-SAP

(N)-SAP

[(N)-SPs]

(N)-PDU

[(N-1) SPs]

(N)-

C-S

AP

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

46

Structure of a (N)-Layer



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

47

OSI-Reference Model

• The early development of LANs, MANs, WANs was not well structured and coordinated.– Result: Proprietary Systems

• 1977 OSI recognized the special and urgent need for standards for heterogeneous networks and create a new subcommittee (SC16) for “Open Systems Interconnection.”– ISO investigated DECnet, SNA, und TCP/IP to find uniform

protocol rules.– Result: Architecture (1984) for the development of compatible

devices– Reference model for Communication Networks

• Describes Layers and Principles of Interaction

ISO-7498, 1984

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

48

Principles

• ISO determined a number of principles to be considered for defining the specific set of layers in the OSI architecture [Zim1980]

1. Not so much layer

2. Boundaries with small interactions

3. Seperate layers for different functions

4. Similiar functions into the same layer

5. Redesign a layer without changing the interfaces



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

49

Principles

• ISO determined a number of principles to be considered for defining the specific set of layers in the OSI architecture [Zim1980]

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

50

Principles

• ISO determined a number of principles to be considered for defining the specific set of layers in the OSI architecture [Zim1980]– Do not create so many layers as to make difficult the system

engineering task describing and integrating these layers– Create a boundary at a point where the services description

can be small and the number of interactions across the boundary is minimized.

– Create separate layers to handle functions which are manifestly different in the process performed or the technology involved.

– Collect similar functions into the same layer.– Create a layer of easily localized functions so that the layer

could be totaly redesigned in a major way to take advantages of new advances in technology without changing the services and interfaces with the adjacent layers.



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

51

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

Network

End-to-End

The ResultC

DS

2.1

Laye

red

Com

mun

icat

ion

JJ

52

• Physical Medium

• Line Coding

• Synchronization

• voltage level

• Baud Rate

• Connectors (Pin Assignments)

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

53

• Physical Addressing

• Medium Access Control

• Error Protection

• Framing

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

54

• Logical Addressing between Hosts

• Routing

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

55

• Segmentation

• Reliable Data Transport Service

• Connect, Disconnect and Maintainingof Connections

• Flow Control

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

56

• Session Management

• Negotiation of Data Transfer (Duplex, Half-Duplex)

• Introduction of Synchronization and Recovery Flags for long sessions.

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

57

• Agreement of the used character set(e.g. ASCII for Text)

• Encryption

1 2 3

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

58

• Source and Destination of Application Data

• Offering Services, e.g. File transfer, Web, for the End user

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

59

DataTXProcess

RXProcess

Application Protocol

Peer-to-Peer Communication

Transport Protocol

Network Protocol

Data Link Protocol

Physical Layer Protocol

Session Protocol

Presentation-Protocol

1 2 3 Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7 Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

ProtocolsC

DS

2.1

Laye

red

Com

mun

icat

ion

JJ

60

DataTXProcess

RXProcess

Application Protocol

Transport Protocol

Network Protocol

Data Link Protocol

Physical Layer Protocol

Session Protocol

Presentation-Protocol

1 2 3 Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7 Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

Protocols



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

61

DataPH

DataTXprocess

RXprocess

Vertical communication using encapsulation

DataAH

DataTH

DataNH

DataDH DT

Bits

DataSH

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7Services

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

ServicesC

DS

2.1

Laye

red

Com

mun

icat

ion

JJ

62

DataPH

DataTXprocess

RXprocess

Vertical communication using encapsulation

DataAH

DataTH

DataNH

DataDH DT

Bits

DataSH

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7Services

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

Services



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

63

1

2

3

4

5

6

7

1

2

3

4

5

6

7

1 1

Repeater

Host A Host BIntermediate System

Extended OSI Model

Network1 Network 2

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

64

1

2

3

4

5

6

7

1

2

3

4

5

6

7

1 1

Bridge

Host A Host B

2 2

Intermediate System

Network1 Network 2



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

65

1

2

3

4

5

6

7

1

2

3

4

5

6

7

1 1

Router

Host A Host B

2 2

3 3

Intermediate System

Network1 Network 2

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

66

1

2

3

4

5

6

7

1

2

3

4

5

6

7

1 1

Gateway

Network1 Network 2

Host A Host B

2 2

3 3

4

5

6

7

4

5

6

7

Intermediate System



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

67

TCP/IP Model

OSI

Network Access

Internet

Transport

Application

TCP/IP

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer1

2

3

4

5

6

7

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

68

Network Access

• All Definitions to transport IP Datagrams via physical channels (Framing)

• Physical Addressing• Error Detection• phy. Connection to the Network

Network Access

Internet

Transport

Application



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

69

Internet Protocol (IP)

Internetschicht

Transportschicht• unreliable Datagramm Service (packets)

• Fragmentation of Packets• Logical Addressing• Routing

Anwendungsschicht

Network Access

Internet

Transport

Application

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

70

Transport Layer

• Reliable Transport of Byte streams• Segmentation• Flow Control • Multiplexing of simultaneous Connections

using PortsInternetschicht

Transportschicht

Anwendungsschicht

Network Access

Internet

Transport

Application



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

71

Application Layer- Properties -

• Connection with the Network• Provides frequently used Services• Covering OSI -Layer 5 and 6

Internetschicht

Transportschicht

Anwendungsschicht

Network Access

Internet

Transport

Application

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

72

Communication Protocol Engineering



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

73

Protocol Engineering

• Protocol Engineering deals with all issues about the Design, Implementation and Testing of Communication protocols.

• Developing Communication Protocols with „engineer-like“ Thinking and Computer Science Methods– Combines Aspects of Computer Networks, Operating

Systems, Software Development and Computer Science

– Becomes more and more a independent field of interest.

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

74

Communication Systems

• Service Specification (What?)– How can the Service User (Client) use the Service

offered by the Service Provider at a SAP?– Describes the dynamic behavior at the SAPs– Service Specification is used by the Client

• Protocol Specification (How?)– How is the specified service made available by the

service provider? – How is the procedure between the service-providing

entities and how is the format of the exchanged PDUs?



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

75

Subjects of Protocol Engineering

RequirementAnalysis

Service- andProtocol Design

PerformanceEvaluation

ProtocolVerification

Implementation

Test

Installation/Integration

RequirementSpecification

Service- andProtocol Specification

OptimizedDesign

verifiedSpecification

Code

Tested Communication Software

Source: [Kö2008]

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

76

Informal Description (todays practise)

• Elements of informal descriptions are:– Textual Description– Descriptions of – Sequence Diagrams– State machines– Tables

• Problem: Only representation of singular aspects• For a complete Protocol a lot of pieces of a puzzle are

needed! • Not suitable for large complex protocols.• Often leads unclear and ambiguous specifications.• The complexity of protocols make them very hard to

analyze in an informal way.



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

77

Formal Methods

• Fundament of modern Protocol Engineering is the usage of Formal Description Techniques (FDT) for Protocol Specification

• Properties of FDTs– formal defined Syntax and Semantic– unambiguous interpretation

• Examples: Petri Nets, SDL, UML2.0

• UML2.0 will be introduced in the lab

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

78

Our Flow for Protocol Engineering in this Course

1.Requirements

2. Service andProtocol Design

4.Test &Validation

Use Case DiagramsSequence Diagrams

Class DiagramsState ChartsComposite Structure

Simulation usingSequence Diagrams

Implementation Code generationPerformanceEvaluation

DES



CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

79

Our Flow for Protocol Engineering in this Course

1.Requirements

2. Service andProtocol Design

4.Test &Validation

Use Case DiagramsSequence Diagrams

Class DiagramsState ChartsComposite Structure

Simulation usingSequence Diagrams

Implementation Code generation

CD

S2.

1 La

yere

dC

omm

unic

atio

nJJ

80

References

• [Pop2006] : M. Popovic, Communication Protocol Engineering, CRC Press, 2006

• [Zim1980]: H. Zimmermann, OSI Reference Model- The ISO Model of Architecture for Open Systems, Interconnection, IEEE Transactions on Commications, Vol. Com-28, No. 4,1980

• [Ku2008]: J.F. Kurose, K.W. Ross, Computer Networking, Pearson International, 2008

• [Kö2008]: H. König, Lecture Computer Networks and Communication Systems I (german), BTU Cottbus, 2008

Layered Communications Systems & Protocol Engineering · Layered Communications and Protocol...

Documents

Transcript of Layered Communications Systems & Protocol Engineering · Layered Communications and Protocol...