PDF of this tutorialThe demand for AIN services far exceeded the availability of network functionality. Service providers could not wait for all the features and functionality as described in AIN Release 1. AIN Release 1 defined all types of requirements, which made the capability sets too large to be adapted by the industry.
In North America, the industry agreed to develop subsets of AIN Release 1 that provided for a phased evolution to AIN Release 1. AIN 0.1 was the first subset targeted for use in the industry.
Telcordia Technologies developed functionality to address the FTS 2000 requirements set forth by the U.S. government. The RBOCs in turn adapted these requirements to meet their customers' immediate needs. This effort resulted in AIN Release 0, which had a time frame before the availability of AIN 0.1.
Meanwhile, the international standards body, the International Telecommunications Union (ITU), embraced the concepts put forth in the AIN Release 1 requirements. The ITU developed an international IN standard called Capability Set 1, or CS–1. As with AIN Release 1 in North America, CS–1 was all encompassing. To meet the market demand, the ITU formed a subgroup called ETSI to focus on the immediate needs. This subgroup developed the Core INAP capabilities. Many PTTs and their switch vendors have adopted the ETSI Core INAP as the standard and are providing Core INAP capabilities.
The following modules discuss the functionality of various AIN releases, as well as the international standards.
