AIN 0.2 builds on AIN 0.1 with additional capabilities to support two service driversphase 2 personal communication service (PCS) and voice-activated dialing (VAD). While AIN 0.2 is focused on capabilities to supports PCS and VAD, all requirements for these capabilities are defined in a service-independent manner. AIN 0.2 capabilities will include the following:
- ISDNbased SSPIP interface
- busy and no-answer triggers
- next event lists processing
- default routing
- additional functions in all operations areas (e.g., network testing)
The two primary AIN 0.2 capabilities are the ISDN interface between a switching system and an ISDNcapable device (such as an IP) and the addition of busy and no-answer triggers.
Next event lists processing is another important capability. In addition to TDPs, AIN 0.2 includes event detection points (EDPs). With EDPs, the SCP will have the ability to send a next-event list to the SSP. This next-event included is used by the SSP to notify the SCP of events included in the next-event list. These events may include busy, no answer, terminating resource available, etc.
AIN 0.2, also includes default routing capabilities. This means that when calls encounter error conditions, they can be sent to a directory number, an announcement, etc., as opposed to sending it to final treatment, as is the case in AIN 0.1.
AIN 0.2 SSPIP Interface
AIN Release 0 and AIN 0.1 assumed that the announcements were switch-based. With the introduction of 0.2, announcements can reside in an external database, such as an IP.
If the SCP sends a send-to-resource message to the switching system to have the IP play an announcement or collect digits, the switching system connects the customer to the IP via the SSPIP ISDN interface. The end user exchanges information with the IP. The IP collects the information and sends it to the switching system. The switching system forwards the information to the SCP. One of the fundamental switching system capabilities is the interworking of SS7 (SCP) messages with ISDN messages (SSPIP).
In addition the SSP may control IP resources without SCP involvement. VAD is an example. A VAD subscriber could be connected to the IP voice-recognition capabilities upon going off-hook. The VAD subscriber says "call mom," and the IP returns mom's telephone number to the switching system. The switching system recognizes mom's number as if the subscriber had actually dialed the number.


