Professional Documents
Culture Documents
IntroductiontoBasicsof CommunicationProtocol
ProfPallapa.Venkataram
PhysicalCommunicationModel
Source
Transmitter
Transmission System
Receiver
Destination
Communication
Itisanytransmission,emission,orreceptionofsigns,signals, writings,imagesandsoundsorintelligenceofanynatureby wire,radio,opticalorotherelectromagneticsystem
Communicationmodel
ElectronicsCommunicationModel
Workstation Modem
Server
Network Model
SwitchingNode
DestinationSystem
Receiver
Destination
LocalAreaNetwork
CommunicationSoftware
Itisasetofcomputerprogramswhichareusedforgeneration, transmissionandreceptionofinformationbetween/amongthe setofcomputersconnectedbywiredorwirelessmedia. DifferentKindsofProgramsforCommunicationare: Dialing:Dialingsoftwaretellsthecomputer,howtoplacea callonthephonelineconnectedtoit. FileTransfer:Transferoffiles,fromonetotheother (Downloading/Uploadingoffiles) TerminalEmulation:Programsrunningonanetworkthat connectstoacomputerbulletinboardsystem DataEncryption:Programtoencodedata
CommunicationSubsystems
Thedesignandimplementationoflargescalecommunication systemsrequirestheinterconnectionandintegrationof diversesubsystems. Themainpurposeofthecommunicationenvironmentisto keepallthesubsystemsinformedofanychangesinthe designparameters. 1.Changereportedfromoneofthesubsystems. 2.Requestfordatafromonesubsystemtoanother
Communicationbetweentwosystem
UserA
Hi,Iwanttochatwithyou Ok.Iamready DialoguebetweenA&B Hi,Letusfinishchatting Ok.Letusdisconnect
UserB
Protocol
Itisasetofrulesgoverningtheformatandmeaningof frames,packets,ormessagesthatareexchangedbypeer entitieswithinalayer. Protocolareusedforcommunicationsbetweenentitiesina systems. Entitiesuseprotocolsinordertoimplementtheirservice definitions. Thekeyelementsofaprotocolare: Syntax:IncludeTimedataformatsandsignallevels Semantics:Includescontrolinformationanderrorhandling.
Simplemessageexchangeprotocolflowchart
SENDER:A
RECEIVER:B
no Isdataready yes getdata TellhostB(receiver) Requestto Send(RTS) requestto sendreceived yes getreadytoreceive tellsender no isreceiverready yes senddata datasent no dataconsumed yes ACK tellsender Readyto Receive(RTR) Data datareceived yes dataconsumed no no
RepresentationofProtocol
Theprocessofaprotocollike,senderandreceiverprotocolcan beformallyspecifiedusing 2. FiniteStateMachine(FSM/PETRINETS) 3. Statetransitiontable FiniteStateMachine(FSM) A:FinitestatemachineMisaquintuple,M=(I;O;S;N;A) I:Finiteandnonemptysetsofinputsymbols O:Finiteandnonemptysetsofoutputsymbols S:Finiteandnonemptysetsofstates FiguregivesFSMofsimplemessageexchangeprotocol
FSMofsimplemessageexchangeProtocol
Sender Receiver Data_ready(i.e.1) RTS RTS
Idle
Idle
ACK sent
get_ready(i.e.3) RTR
Ready_Send
RTR
Data_sent(i.e.2)
ACK Received
Send_Data
ACK
Wait_Ack
ACK
FSMstateandtransitionscanberepresentedintheformof tablecalledasstatetransitiontables.
Input
(data_ready)
StateTransitionTable
i.e.1
RTR
S1/ S3/ S3/ S4/
State
(data_ready)
i.e.2
ACK
S1/ S2/ S3/ S1/
S1 S2 S3 S4
Communicationprotocoldevelopmentmethods
Therearetwowaysofdesignanddevelopmentof Communicationprotocols 1.Informal 2.FormalMethods
Informalmethods
Informalwayofspecificationoftheprotocolsinclude textualdescription. Notsuitableforlargecomplexprotocols. Oftenleadsunclearandambiguousspecifications. Thecomplexityofprotocolsmakethemveryhardto analyzeinaninformalway.
InformalSpecifications
Informal Specification ofneeds Concept
Implementation
Formalmethods
Useofformalspecificationlanguages. Theseprotocolsmustbeofhighqualitywithhigher performancewithlowcost. Informal
Specification ofneeds Formal Specification Simulation Validation Compilation Programmer
FormalSpecifications
Implementation
Petrinetmodel
Apetrinetisafourtuple(P;T;IN;OUT;M0)where, P=fp;p;:::::::;pgisasetofplaces. 1 2 n T=ft;t;:::::::;pgisasetoftransition. 1 2 n M0=Initialmarking(tokenataplace). IN:(PT)!Nisaninputfunctionthatdefinesdirectedarcs fromplacestotransition OUT:(PT)!Nisanoutputfunctionthatdefinesdirectedarcs Fromtransitiontoplaces.
APetrinetmodelofasimpleprotocolwithatimeoutmechanism
i2 P2
i1
P5
i6 i3 P1 i7 i8 P7 i5 P4 i4 P6
P3
ProtocolEngineeringProcess
Needforprotocolengineering
Manyprotocolsifnotproperlydesignedandimplemented aspertherequirements,leadstoimproperbehaviorof networkandsystemmayjamthenetworks. Henceitisrequiredto,engineertheprotocolsfortheir correctnessreliability,optimizedperformance,reusability, andcodeoptimization Dealswithapplicationofformaltechniquesandsoftware engineeringmethodologiestoprotocoldesignand implementation
PhasesofProtocolEngineering
Service Specification Synthesis Protocol Specification Monitoring Diagnosis Protocol Implementation Performance Analysis Verification/ Validation
Conformance Testing
Functions:
Servicespecification:Theservicerequiredforperformingcertaintasksin anygivenenvironment. Synthesis:Itisanautomatedtooltogeneratetheformalspecificationofa protocol. Protocolspecification:Itlooksintosyntaxandsemanticsoftheprotocols specifications. Protocolverification/validation:Usermakesaboutthestructureof possibledialogsbetweenprocessesofprotocol. Performanceanalysis:Itanalysestheprotocolperformanceintermsof messagecomplexity,timecomplexity,spacecomplexity,scalability. Conferencetesting:ittestswhethertheprotocolconformstothe specificationslaiddowninprotocolspecificationphasebygenerating exhaustivesetoftestsequences. Protocolimplementation:Itdealswiththerealcodingoftheprotocol usingsoftwareengineeringaspects. Monitoring/diagnosis:Itmonitorstheworkingofimplementedprotocol andchecksfortheerrors.