About: Transactions on Petri nets and other models of concurrency III   Goto Sponge  NotDistinct  Permalink

An Entity of Type : rdac:C10001, within Data Space : data.idref.fr associated with source document(s)

AttributesValues
type
dc:subject
  • Programmation (informatique)
  • Computers
  • Software Engineering
  • Informatique
  • Actes de congrès
  • Logique mathématique
  • Computer science
  • Simulation par ordinateur
  • Génie logiciel
  • Mathematical Logic and Foundations
  • Mathematical logic
  • Computer Science
  • Theory of Computation
  • Software engineering
  • Computer programming
  • Programming Techniques
  • Mathematical Logic and Formal Languages
  • Information theory
  • Computer simulation
  • Simulation and Modeling
  • Petri nets
  • Petri, Réseaux de
  • Ordinateurs
  • Models and Principles
  • Parallélisme (informatique)
  • Computer multitasking
  • Parallel processing (Electronic computers)
  • Flux de travail
preferred label
  • Transactions on Petri nets and other models of concurrency III
Language
Subject
dc:title
  • Transactions on Petri nets and other models of concurrency III
Publishing director
note
  • AccordingtoHolzmann [14], protocol speci?cationscomprise ?veelements: the service the protocol provides toits users; the set of messages that are exchanged between protocol entities; the format of each message; the rules governingm- sage exchange (procedures); and the assumptionsabout the environment in which the protocol is intended tooperate. In protocol standards documents, information related to the operatingenvironment isusually writteninformally andmayoccur in several di?erentplaces [37]. This informal speci?cation style canlead to misunderstandings andpossibly incompatible implementations. In contrast,executableformalmodelsrequireprecisespeci?cations oftheoperating environment. Ofparticularsigni?canceisthecommunicationmediumorchannel over which the protocol operates. Channelscan havedi?erent characteristics depending on the physical media (e. g. optical ?bre, copper, cable orunguided media (radio)) they employ. The characteristics also depend on the levelof the protocol inacomputer protocol architecture. Forexample, the link-leveloperates over a singlemedium,whereas the network, transport andapplication levelsmayoperate over a network,or network of networks such as the Internet,which couldemploy several di?erent physical media. Channels (such as satellite links) can be noisy resulting in bit errors in packets. To correct biterrors in packets, many importantprotocols (such the Internet’s TransmissionControl Protocol [27]) use CyclicRedundancy Checks (CRCs)[28] to detect errors. On detectingan error,the receiver discards the packet andrelies on the sender to retransmit itforrecovery,known as Au- maticRepeatreQuest(ARQ)[28]. Thisisachievedbythereceiveracknowledging the receipt of good packets, andby the transmitter maintainingatimer. When the timer expires before an acknowledgementhasbeen received, the transmitter retransmits packets that havebeen sent but are as yet notacknowledged. It may also be possibleforpacketsto be lost due to routers in networks discarding packets when congested
dc:type
  • Text
http://iflastandar...bd/elements/P1001
rdaw:P10219
  • 2009
has content type
is primary topic of
is rdam:P30135 of
Faceted Search & Find service v1.13.91 as of Aug 16 2018


Alternative Linked Data Documents: ODE     Content Formats:       RDF       ODATA       Microdata      About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data]
OpenLink Virtuoso version 07.20.3229 as of May 14 2019, on Linux (x86_64-pc-linux-gnu), Single-Server Edition (70 GB total memory)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2025 OpenLink Software