2.1.1 TIF NP Message Flows

The following figure shows basic TIF NP CdPN Relay use cases.

Figure 2-1 ISUP Message Flows for TIF NP CdPN Relay

The following figure shows TIF NP Relay cases where NM bits are used in the ISUP IAM message. In the sequence diagrams, the NM bits are shown as binary values. Refer to Use of NM Bits for details on the use of NM bits.

Note:

Use of NM bits in the IAM message is an optional part of TIF NP.

Figure 2-2 ISUP Message Flows for TIF NP CdPN Relay, with Optional NM Bits

The following figure shows basic TIF NP CgPN portability use cases.

Figure 2-3 ISUP Message Flows for TIF NP CgPN Portability

A TIF NP CgPN use case is shown in te following figure for a TIFCGPN, TIFCGPN2, or TIFCGPN3 NPP service when NPRELAY (in TIF, TIF2, or TIF3) and CGPNNP (in TIFCGPN, TIFCGPN2, or TIFCGPN3) Service Actions are provisioned and Number Portability lookup is performed on both CdPN and CgPN. A TIFCGPN, TIFCGPN2, and TIFCGPN3 NPP service is invoked by the corresponding TIF, TIF2, or TIF3 NPP Service.

Figure 2-4 ISUP Message Flows for TIF NP CgPN with NPRELAY and CGPNNP

The following figure shows basic TIF NP Release use cases.

Figure 2-5 ISUP Message Flows for TIF NP Release

The following figure shows TIF NP Release use cases, with use of NM bits. See Use of NM Bits for details on the use of NM bits.

Figure 2-6 ISUP Message Flows for TIF NP Release, with Optional NM bits

The following figure shows Circular Route Prevention use cases. In these cases, subscriber X is ported from network A to network B. Network A’s NP database has the correct entry indicating that subscriber X is ported, but network B has incorrect routing information, indicating that subscriber B still belongs to network A. Subscriber Y belongs to network A. In the use case, subscriber Y calls subscriber X.

Figure 2-7 ISUP Message Flows for TIF CRP

A basic Service Portability use case is shown in the following figure. In this example, the Service Portability feature is turned on and the TIFOPTS SPORTRELAY option has been configured for Service Portability. If the subscriber is an own-network GSM or IS41 subscriber, then the Number Portability GRN is used for the RN.

Figure 2-8 ISUP Message Flows for Service Portability

A use case using both the NPRLS and NPRELAY Service Actions is shown in the following figure. In this example, only OLO subscribers are released; own-network subscribers are relayed. The Service Actions would be set to NPRLS and NPRELAY. The NPTYPERLS configuration option is set to RN and the NPTYPERLY configuration option is set to SP.

Figure 2-9 ISUP Message Flows for NPRLS + NPRELAY