Summary

New SS7 implementations must be tested for both validation and compatibility. Validation is performed before the implementation is connected to a live network and is used to check that the implementation functions correctly; that is, it conforms to the appropriate protocol standards. Compatibility testing is executed after the implementation has passed the validation phase of testing. Compatibility seeks to check interoperability and requires the implementation to be connected to the live network. The ITU-T has specified test documents, which cover both validation and compatibility testing for the core SS7 protocols. These documents should be tailored to suit the implementation under test—specifically, the implemented protocol variants and the nature of the solution itself. This is achieved by aligning the ITU-T test specifications to the national (or regional) variant specifications and the nature of the implementation itself. For example, particular country (or regional) variants might not use particular messages so that any tests relating to these messages can be removed; in addition, where a variant adds messages or parameters, tests should be added to check these areas. Where a particular solution under test does not have an area of functionality (for example, it can only terminate calls), tests surrounding the areas of functionality that do not require implementation can be removed (for example, the ability to originate calls). Each of the core SS7 protocols (MTP 2, MTP 3, ISUP, ISUP supplementary services, SCCP, and TCAP) has a corresponding ITU-T test specification. These specifications aim to broadly test the main functional areas of each protocol. The IETF is currently working on similar test specifications, which are to be used for the SigTran protocol suite.