Message Sequence Chart

Message Sequence Chart
Name	Message Sequence Chart
Caption	Example of a Message Sequence Chart
Type	Interaction diagram
Introduced	1980s
Standard	ITU-T Z.120

Message Sequence Chart Message Sequence Chart is a graphical formalism for describing interactions between entities in distributed systems, telecommunications, and protocols. It was developed to model communication traces among processes, actors, and components, enabling analysis of protocols, verification of interoperability, and documentation of requirements for systems such as SS7, SIP, GSM, TCP/IP, and HTTP. The notation influenced and interoperates with standards and tools from organizations such as ITU-T, ISO, IEEE, IETF, and ETSI.

Introduction

Message Sequence Chart provides a visual representation of events exchanged by named instances (lifelines) over time, showing message arrows, synchronous and asynchronous communication, and timing constraints. The chart is used by practitioners affiliated with Bell Labs, Ericsson, Nokia, Siemens, and Alcatel-Lucent to specify protocol behaviors in projects like SS7 and GSM. In standardization work within ITU-T and ISO/IEC, the notation complements formal methods developed at institutions such as the University of Cambridge, MIT, and ETH Zurich.

History and Standardization

Origins trace to research in the 1980s on protocol engineering at laboratories such as Bell Labs and academic groups including University of California, Berkeley and University of Manchester. The formalization effort culminated in an international standard produced by ITU-T as Recommendation Z.120, with parallel attention from ISO/IEC working groups and influence on OMG specifications. Development intersected with projects led by companies like Siemens during the evolution of SS7 and further harmonized in forums with contributors from IETF and ETSI task forces. Subsequent revisions addressed use in software engineering communities that included members from Microsoft Research, IBM Research, and Siemens AG.

Notation and Components

A Message Sequence Chart uses vertical lifelines labeled with entity names drawn from companies or institutions such as Cisco Systems, Huawei Technologies, Intel Corporation, ARM Holdings, and Google product teams. Messages are depicted as directed arrows annotated with operation names, IDs, or protocol primitives, referencing technologies like SIP, RTP, TLS, IPsec, and BGP. Interaction fragments such as alternatives, loops, and parallels echo constructs found in standards from OMG and ISO/IEC JTC 1, and may reference timing constraints aligned with specifications from IEEE 802.11, 3GPP, or ITU-T. Notational elements also support process creation and termination as seen in protocol specifications by IETF working groups and industrial consortia like GSMA.

Semantics and Execution Models

Semantics for Message Sequence Charts can be interpreted via trace semantics, partial orders, or automata-theoretic models employing languages and tools from research groups at ETH Zurich, INRIA, University of Oxford, and SRI International. Execution models map charts to state machines, labeled transition systems, or Petri nets studied by scholars associated with Princeton University, Stanford University, and University of Edinburgh. This allows formal verification with model checkers and theorem provers such as SPIN, UPPAAL, NuSMV, and integration with proof assistants like Coq and Isabelle/HOL used by teams at Microsoft Research and INRIA.

Comparison with Sequence Diagrams and UML

Message Sequence Charts are often compared to UML Sequence Diagrams standardized by OMG and used by vendors like IBM Rational and Sparx Systems. While both convey interaction traces, Message Sequence Charts as standardized by ITU-T emphasize formal semantics and protocol-oriented constructs familiar to ETSI and IETF engineers, whereas UML Sequence Diagrams integrate with model-driven engineering frameworks promoted by OMG and adopted by SAP and Siemens PLM Software. Research collaborations between groups at University of York, KTH Royal Institute of Technology, and Technical University of Munich explored mappings and interoperability between the two notations for toolchains used by Siemens, Bosch, and Thales.

Applications and Use Cases

Message Sequence Charts are applied in telecom protocol design for GSM, UMTS, LTE, and 5G NR specifications driven by 3GPP and ETSI; in internet protocol development for IETF documents such as RFC 3261 (SIP); and in aerospace and defense projects involving contractors like Lockheed Martin, BAE Systems, and Northrop Grumman. They are used in interoperability testing labs run by ETSI and GSMA, in safety-critical system design in companies like Airbus and Rolls-Royce, and in academic case studies at Carnegie Mellon University and University of California, Santa Barbara.

Tools and Examples

Tool support for Message Sequence Charts includes commercial and open-source offerings from vendors and projects associated with IBM, Microsoft, Eclipse Foundation, Modelio, Sparx Systems, and academic tools developed at TU Wien and University of Twente. Formal verification and synthesis tools integrate MSCs with model checkers such as SPIN and UPPAAL, and with code generation frameworks in environments provided by GitHub repositories maintained by research groups at KTH Royal Institute of Technology and INRIA. Example MSCs appear in standards documents from ITU-T, interoperability test suites from ETSI, and protocol appendices in IETF RFCs.

Category:Diagrams