Specification and Description Language

Description

Specification and Description Language (SDL) is a formal, object-oriented, graphical modeling language standardized by the International Telecommunication Union (ITU-T) in the Z.100 series. Within the 3GPP standardization context, SDL is employed to provide rigorous, unambiguous specifications for communication protocols, system procedures, and state machine behaviors. Its primary role is to define the dynamic behavior of systems, focusing on the sequence of events, message exchanges, and state transitions that occur in response to stimuli. This formal approach eliminates the ambiguities inherent in natural language text, thereby reducing the risk of misinterpretation and implementation errors across different equipment vendors and network operators.

SDL models a system as a set of concurrent processes that communicate asynchronously via signals. The language uses a hierarchical structure, starting with a system block diagram that defines the overall system and its communication channels. This system is decomposed into blocks, which are further refined into processes. Each process is defined using Extended Finite State Machines (EFSMs), represented by SDL process diagrams. These diagrams consist of states, inputs (triggering signals), outputs (sent signals), tasks (internal actions), decisions, and procedures. The language supports data typing, variables, timers, and the creation of new signal instances, enabling the specification of complex, real-time interactions found in telecommunications protocols.

In 3GPP technical specifications (TS), SDL diagrams are often provided as normative annexes to complement the prose descriptions of protocols. For instance, SDL is extensively used in the specification of layer 3 signaling protocols in both the Core Network and the Radio Access Network, such as Non-Access Stratum (NAS) and Radio Resource Control (RRC) procedures. The language's ability to precisely define timers, message formats, and conditional behavior is crucial for interoperability testing and conformance certification. By providing a visual and formal model, SDL serves as a critical tool for protocol engineers, test developers, and system architects to understand, implement, and verify the correct operation of 3GPP systems.

Purpose & Motivation

The primary purpose of SDL within 3GPP is to achieve unambiguous and precise specification of complex, reactive systems. Telecommunications protocols involve intricate sequences of messages, timers, and state-dependent behaviors. Describing these solely in natural language can lead to multiple interpretations, causing interoperability failures between equipment from different manufacturers. SDL addresses this by providing a formal, graphical notation that defines behavior with mathematical rigor, ensuring all implementers derive the same logical model from the specification.

Historically, as mobile systems evolved from 2G to 3G (UMTS) and beyond, the complexity of protocols increased dramatically. The introduction of packet-switched domains, sophisticated mobility management, and quality of service mechanisms required a more robust specification methodology. SDL, being an ITU-T standard already used in other telecom domains, was adopted to bring this rigor to 3GPP. It solves the problem of specification ambiguity, which is a major source of bugs and delays in multi-vendor network deployments.

Furthermore, SDL models are not just documentation; they can be used for simulation, validation, and even as a basis for automated test generation. This allows standards bodies and equipment vendors to verify the logical consistency of a protocol specification before it is finalized and to develop comprehensive test suites. Thus, SDL's purpose extends beyond static specification to actively improving the quality, reliability, and time-to-market of 3GPP-compliant products.

Key Features

• Formal graphical notation based on Extended Finite State Machines (EFSMs)
• Support for concurrent processes communicating via asynchronous signals
• Hierarchical system decomposition (System, Block, Process)
• Integrated data modeling with abstract data types and variables
• Explicit modeling of timers, timeouts, and real-time constraints
• Ability to generate executable code or simulation models from specifications

Evolution Across Releases

Defining Specifications