When it was first approved by the CCITT in the 1980 Yellow Book, Signaling System No. 7 was described as "an internationally standardized general purpose Common Channel Signalling (CCS) system: <tex xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">\bullet</tex> optimized for operation in digital telecommunications networks in conjunction with stored program controlled exchanges; <tex xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">\bullet</tex> that can meet present and future requirements of information transfer (circuit and non-circuit related) for inter-processor transactions within telecommunications networks for call control, remote control, network data base access, and management and maintenance signalling; <tex xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">\bullet</tex> that provides a reliable means of information transfer in correct sequence, without loss or duplication." It then consisted of a three-level message transfer part (MTP-for connectionless message transfer), a telephone user part (for analog call setup and control), a data user part (for analog circuit switched data), and a four-level architectural model with a "fuzzy" relation to the OSI seven-layer model. By 1984, in the Red Book, the MTP had matured considerably (especially in the area of congestion control), a new level had been added to provide additional transport functionality (the signaling connection control part or SCCP), an ISDN user part provided call control for digital facilities, and the architectural model had been "adjusted." Future efforts are focusing on cod-to-end ISDN signaling compatibility (harmonization of SS7 and <tex xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">D</tex> -channel procedures), non-circuit-related transaction capabilities (e.g., for network database interactions), a complete operations and maintenance application part (OMAP), and a more formal architectural relationship with the OSI model.
Read full abstract