PDF of this tutorialAIN 0.1 is the first subset of AIN Release 1. There are two fundamental differences between AIN Release 0 and AIN 0.1 The first is a formal call model and the second is the messaging sets between the switching system and the SCP. The formal call model is separated into the originating call model (originating half call) and the terminating call model (terminating half call). The AIN Release 0 call model did not distinguish between originating and terminating. A standard or formal call model is necessary as we evolve to the Target AIN Release 1 capability, because the capabilities will have more PICs and TDPs. Also, there will be multiple switch types and network elements involved. Therefore, the service logic will need to interact with every element that will be required in the network.
AIN 0.1 includes several other major features. There are 254 announcements at the switching system, which provides more flexible messages available to customers. There are additional call-related and noncall-related functions as well as three additional triggers—the N11 trigger, the 3-6-10-digit trigger, and the termination attempt trigger. More triggers provide additional opportunities for SCP service logic to influence call processing. (Note: TCP was an AIN Release 0 term that changed to TDP in AIN 0.1).
There are several AIN 0.1 noncall-related capabilities. The SCP has the ability to activate and deactivate subscribed triggers. The AIN 0.1 SCP can also monitor resources. In addition to sending a call routing message to the switching system, the SCP may request that the switching system monitor the busy/idle status of a particular line and report changes. AIN 0.1 also supports standard ISDN capabilities.
As mentioned previously, there is a distinction between the originating side and the terminating side of a service switching point. This means that both originating and terminating triggers and service logic could influence a single call.
Figure 9 shows a portion of the AIN 0.1 originating call model. The AIN 0.1 originating call model includes four originating trigger detection points–origination attempt, information collected, information analyzed, and network busy.
Figure 9. AIN 0.1 Originating Call Model
The AIN 0.1 terminating call model includes one TDP—termination attempt, as depicted in the partial call model in Figure 10.
Figure 10. AIN 0.1 Terminating Call Model
AIN 0.1: SSP–SCP Interface
The AIN 0.1, as shown in Figure 11, is based on ANSI TCAP issue 2, which means that the message set is different than the message set in ANSI TCAP issue 1. For example, in AIN Release 0, there is only one message sent from the SSP to the SCP no matter what trigger is hit at any of the three TCPs. In AIN 0.1, separate messages are sent for the four originating and one terminating TDP.
Figure 11. AIN 0.1 SSP–SCP Interface
