Mobile Originated Based GSM SMS Number Portability

The Mobile Originated Based GSM SMS Number Portability (MO-Based GSM SMS NP) feature provides network information to the Short Message Service Center (SMSC) for subscribers in the GSM network. This ported information allows the SMSC to distribute the messages to the correct operating network for the Called Party Number.

The SMSC uses the DN porting information to determine whether to forward the message to other operators or to process the message for an in-network subscriber.

The MO-Based GSM SMS NP feature applies to GSM MAP ForwardSM MSUs for either ITU or ANSI MTP messages.

Mobile Originated Based IS41 SMS Number Portability

The Home SMSC uses the DN porting information to determine whether to forward the message to other operators or to process the message for an in-network subscriber.

The MO-Based IS-41 SMS NP feature applies to ANSI IS41 SMDPP MSUs for either ITU or ANSI MTP messages.

MO SMS IS41-to-GSM Migration

The MO SMS IS41-to-GSM Migration feature allows IS41 to GSM migration. This feature migrates subscribers based on Called Party Number from IS41 networks to GSM networks, and also allows the IS412GSM Migration Prefix to be used instead of the Routing Number (RN) obtained from the Real-time Database (RTDB). The MO SMS IS41-to-GSM Migration feature:

The MO SMS IS41-to-GSM Migration feature applies to ANSI TCAP/MAP and ANSI or ITU transport (MTP and SCCP).

Portability Check for Mobile Originated SMS

When the Portability Check for Mobile Originated SMS (MNP SMS) feature is enabled and turned on, the EAGLE 5 ISS filters incoming messages based on the MAP Operation Code. If the message is an MO Forward Short Message (MO FSM), the MSISDN number of the originating subscriber is used to search the G-Port Mobile Number Portability database. If a match is found indicating the subscriber has been ported-out, the EAGLE 5 ISS uses the destination SMSC address obtained from the SCCP CdPA to search a list of home network SMSC addresses. If a match is found, indicating the ported-out subscriber is fraudulently attempting to send SMS using the SMSC of the old network, the message is discarded and an error message is generated and returned to the originating MSC.

Prepaid Short Message Service Intercept

The Prepaid Short Message Service Intercept (PPSMS) feature applies to only mobile originated SMS, which are messages sent from a mobile handset through an Mobile Switching Center (MSC) to the Short Message Service Center (SMSC). PPSMS screens incoming messages from the MSC based on the MAP operation code. Message Discrimination determines whether the MSISDN of the sender is retrieved and a database lookup performed. Database lookup determines if the MSISDN belongs to a contract subscriber or a prepaid subscriber. If the MSISDN belongs to a contract subscriber, the message is routed to the SMSC. If the MSISDN belongs to a prepaid subscriber, the message is diverted to a Prepaid SMS Server for a credit check before allowing the message to be delivered to the SMSC.

MO SMS Additional Subscriber Data

The MO SMS Additional Subscriber Data (MO SMS ASD) feature allows for the insertion of Additional Subscriber Data (ASD) values into the outgoing message. The MO SMS ASD feature supports the ASDLKUP or CGPNASDRQD NPP Service Actions for GSM or IS41 MO SMS NPP Services. The ASDLKUP and CGPNASDRQD NPP Service Actions are mutually exclusive within the same NPP Rule.

The ASDLKUP Service Action populates the ASD digits retrieved from an RTDB lookup of the individual or range DN table. The ASD digits are used with the Formatting Action. ASDLKUP supports both Calling Party and Called Party NPP Services for GSM and IS41: MOSMSGCDPN, MOSMSGCGPN, MOSMSICDPN, MOSMSICGPN. However, ASD digits retrieved by Calling Party or Called Party NPP Services are not used for modifying CgPN. ASD digits retrieved by Calling Party NPP Service are used with the Formatting Action for the Called Party Number if CGPNASDRQD Service Action is executed from Called Party NPP Service. If no ASD digits are found, no action is taken.

The CGPNASDRQD Service Action retrieves the ASD digits from the RTDB lookup of the Calling Party Number. The ASD digits are used with the Formatting Action for the Called Party Number. CGPNASDRQD supports Called Party NPP Services for GSM or IS41: MOSMSGCDPN, MOSMSICDPN.

MO SMS Generic Routing Number

The MO SMS Generic Routing Number (MO SMS GRN) feature allows for the insertion of a Generic Routing Number (GRN) digit string into the outgoing message. The MO SMS GRN feature supports the GRNLKUP or CGPNGRNRQD NPP Service Actions in GSM or IS41 MO SMS NPP Services. The GRNLKUP and CGPNGRNRQD NPP Service Actions are mutually exclusive within the same NPP Rule.

The GRNLKUP Service Action populates the GRN digits retrieved from an RTDB lookup of the individual or range DN table. The GRN digits are used with the Formatting Action. GRNLKUP supports both Calling Party and Called Party NPP Services for GSM and IS41: MOSMSGCDPN, MOSMSGCGPN, MOSMSICDPN, MOSMSICGPN. However GRN digits retrieved by Calling Party or Called Party NPP Services are not used for modifying CgPN. GRN digits retrieved by Calling Party NPP Service are used with the Formatting Action for the Called Party Number if CGPNGRNRQD Service Action is executed from Called Party NPP Service. If no GRN digits are found, no action is taken.

The CGPNGRNRQD Service Action retrieves the GRN digits from the RTDB lookup of the Calling Party Number. The GRN digits are used with the Formatting Action for the Called Party Number. CGPNGRNRQD supports Called Party NPP Services for GSM or IS41: MOSMSGCDPN, MOSMSICDPN.

Service Portability

Service Portability (S-Port) extends the scope of the MO SMS Number Portability solutions beyond traditional number portability processing. Service Portability allows a subscriber to retain the same subscriber number when moving from one network type or service technology to another within the network of a single operator. Unlike traditional number portability, the subscriber does not move from one network operator or service provider to another. Service Portability provides different routing number digits for formats that require routing numbers. Service Portability does not affect message flows.

MTP Routed SCCP Traffic

When the MTP Msgs for SCCP Apps feature is turned on, all MTP routed UDT/non-segmented XUDT SCCP messages are routed to Service Module cards. When the MTP Routed GWS Stop Action feature is turned on, messages are filtered based on the provisioned Gateway Screening rules on a per linkset basis. This feature forwards only UDT, UDTS, XUDT and XUDTS SCCP messages to the Service Module cards for processing. The Service Module cards then perform SCCP decode and verification on the MTP routed messages.

TCAP Segmented SMS Support Phase 1

The TCAP Segmented SMS Support Phase 1 enhancement allows the Portability Check for Mobile Originated SMS and Mobile-Originated Based GSM SMS NP features to correctly process TCAP Segmented SMS messages. If a segmented message is subjected to the service associated with either of these features, then the EAGLE 5 ISS routes the initial TC_Begin message using standard GTT processing. The subsequent TC_Continue message is subjected to the specified service. The GTT feature and either the Portability Check for Mobile Originated SMS or the Mobile-Originated Based GSM SMS NP feature must be turned on before the TCAP Segmented SMS Support Phase 1 enhancement can be provisioned. The MOSMSTCAPSEG parameter of the chg-gsmsmsopts command is used to provision TCAP Segmented SMS Support Phase 1.

HomeSMSC Match with Digits

The HomeSMSC Match with Digits option enhances the ability of the EAGLE 5 ISS to compare the Home Short Message Service Center (HomeSMSC) digits in the SCCP CdPA, if present, of incoming Mobile Originated Forward Short Messages (MO_FSM) or the SMDPP message to HomeSMSCs that are stored in the database. If the beginning digits of the incoming HomeSMSC matches a stored HomeSMSC, then the HomeSMSCs are considered a match, even if additional digits are attached to the end of the incoming HomeSMSC. If a match is found, then the message is processed further.

This option can be used with these features:

• MO-Based GSM SMS NP
• MO-Based IS41 SMS NP
• MO SMS IS41-to-GSM Migration
• Portability Check for Mobile Originated SMS
• Service Portability (S-Port)

The HomeSMSC Match with Digits option is provisioned with the MOSMSDIGMAT parameter of commands chg-is41smsopts and chg-gsmsmsopts. The possible values of the parameter are:

• GSMSMSOPTS:MOSMSDIGMAT= exact, bestfit
• IS41SMSOPTS:MOSMSDIGMAT= exact, bestfit, bypass

If a message is subjected to multiple SMS-related features that require matching with the provisioned HomeSMSCs, a single HomeSMSC address lookup in the HomeSMSC table is performed; the result is used for subsequent processing by all features which need the HomeSMSC address result.

Because the CdPA GTA digits are not available for GTI=0 MTP routed messages, the message is checked to determine whether the MTP DPC is a HomeSMSC in the Destination table. If the MTP DPC is a HomeSMSC in the Destination table, the HomeSMSC match is considered successful.

HomeSMSC Check Bypass

The HomeSMSC Check Bypass option allows the HomeSMSC address check to not be performed. In some IS41 networks, the SCCP CdPA digits do not contain the SMSC address used by the HomeSMSC check. This bypass option applies to only the MO-Based IS41 SMS NP and MO SMS IS41-to-GSM Migration features; the bypass option is not needed in GSM networks.

The system level options stored in the GSMSMSOPTS table are used to perform number conditioning, response generation, and other feature-specific options. Table 2-1 shows the MO SMS options in the GSMSMSOPTS table, possible values, and the actions taken for each value.

The MO-Based GMS SMS NP, MO SMS ASD, MO SMS GRN, Portability Check for MO SMS, or Prepaid SMS Intercept feature must be enabled before these options can be specified in the GSMSMSOPTS table. Refer to chg-gsm41smsopts in EAGLE GSM SMS Options Commands and in Commands User's Guide for associations and limitations.

The system level options stored in the IS41SMSOPTS table are used to perform number conditioning, response generation, and other feature-specific options. Table 2-2 shows the MO SMS options in the IS41SMSOPTS table, possible values, and the actions taken for each value.

The MO-Based IS41 SMS NP, MO SMS IS41-to-GSM Migration, MO SMS ASD, or MO SMS GRN feature must be enabled before these options can be specified in the IS41SMSOPTS table. Refer to chg-is41smsopts in EAGLE IS41 SMS Options Commands and in Commands User's Guide for associations and limitations.

1. GTT must be turned on before enabling the MO-Based GSM SMS NP, MO-Based IS41 SMS NP, and MO SMS IS41-to-GSM Migration features.

2. The MO-Based GSM SMS NP and MO-Based IS41 SMS NP features can be turned on, but not turned off.

3. The MO SMS IS41-to-GSM Migration feature can be turned on or off; however, after the feature is enabled, it cannot be disabled.

4. No Temporary Feature Access Key is provided for the MO SMS features with the exception of the MNP SMS feature.

5. The enabling or turning on of the MO SMS features is not dependent upon the A-Port or G-Port feature being enabled or turned on.

6. All MO SMS features can co-exist with other EPAP-related EAGLE features, including G-Port, A-Port, INP, G-Flex, and EIR.

7. All MO SMS features are mutually exclusive with all features that require ELAP, such as LNP and TLNP, unless the Dual ExAP Configuration feature is enabled.

8. The MO SMS features require Service Module cards running the VSCCP application.
9. The MO SMS features require that the Service Module cards have a minimum of 4 GB of memory. If the MO SMS features are enabled and a Service Module card with less than 4 GB of memory is inserted, the Service Module card will be auto-inhibited. If a Service Module card with less than 4 GB of memory is provisioned and installed, then the MO SMS features will not be allowed to be enabled.

Portability Check for Mobile Originated SMS Call Flow

The MAP_FORWARD_SHORT_MESSAGE (FSM), in the following Call Flow example is used to carry a text message (short message) being transmitted from the mobile handset of one subscriber to the mobile handset of another subscriber. In practice, the short message is delivered first to the Short Message Service Center (SMSC) of the sending subscriber, and then the SMSC is responsible for sending the short message to the intended recipient.

Refer to the following steps in the flow for this call.

The EAGLE 5 ISS will perform the following with respect to MNP SMS Feature functionality.

1. The EAGLE 5 ISS receives an UDT message.

2. EAGLE 5 ISS checks whether the service selector value is smsmr. If the service selector matches smsmr, continue to the next step. If the service selector is not smsmr, the message falls through to GTT (#12).

3. The MAP OpCode is examined. If the OpCode is MO_FSM, PPSMS processing continues with the next step. If the OpCode is not MO_FSM, the message falls through to GTT (#12).

4. If the PPSMS feature is on, the message falls through to PPSMS processing (#8). If the PPSMS feature is not on, processing continues with the next step.

5. If the MNP SMS feature is on, the Mobile Subscriber Integrated Services Digital Network (MSISDN) number is used to search the G-Port Mobile Number Portability subscriber database. If the MNP SMS feature is not on, the message falls through to GTT (#12).

6. If the MSISDN Number is found in the PDB/DN table, then the portability type of the subscriber is checked for Not Known to be Ported (0) / Ported-out (1) / FNPTFN (2) /Not identified to be ported (36) and processing continues. If the MSISDN Number is not found in the PDB/DN table, the message falls through to GTT (#12). If the portability type is in the range of Prepaid1 (3) to Prepaid32 (35), the message falls through to GTT (#12).

7. The SCCP CdPA Address is used to search the list of home network SMSC addresses. If a match is found, the ported-out subscriber is fraudulently attempting to send SMS using the SMSC of the old network. The message is discarded; UIM #1129 is issued; an error message is generated and returned to the originating MSC, and the message falls through to #15. If the message is not on the list, the message falls through to GTT (#12).

8. If the message is from one of the IN Platforms (PPSMS Servers), The message exits from MNP SMS feature functionality and falls through to PPSMS processing (#14). If the message is not from one of the PPSMS Servers, processing continues to the next step.

9. The MSISDN number (phone number) of the originating subscriber is used to search the G-Port Mobile Number Portability subscriber database. If the MSISDN Number is found in the PDB/DN table, then continue to the next step. Otherwise, exit from MNP SMS feature functionality and continue with Normal GTT processing (#12).

10. Check the portability type of the subscriber. If the portability type matches the range of Prepaid1 (3) to Prepaid32 (35), go to #14; otherwise, continue with the next step.

11. If the subscriber portability type is Not Known to be Ported (0) /Ported-out (1) / FNPTFN (2) /Not identified to be ported (36) and MNP SMS feature is also ON, then go to #7. Otherwise, exit from MNP SMS feature functionality and continue with Normal GTT processing.

12. Exit from MNP SMS feature functionality and continue with existing processing for other services or GTT.

13. Exit from MNP SMS feature functionality and continue with existing processing for G-Port.

14. Exit from MNP SMS feature functionality and continue with existing processing for PPSMS.

15. Exit from MNP SMS feature functionality.

Message Discrimination

PPSMS uses the G-Port message selection methods to determine whether the message should receive PPSMS/G-Port service versus GTT.

If the incoming selectors match a SRVSEL entry and the entry has SERV=SMSMR, PPSMS is performed. If no match is found in SRVSEL table then GTT is performed. If the SSN is for HLR, G-Port is performed. If the SSN is for MSC, PPSMS is performed, and if the SSN is for neither, GTT is performed. Next, the MAP Operation Code received in the message is examined. Only Mobile originated forward short message calls receive PPSMS service. Other messages fall through to GTT. After MAP operation code discrimination, PPSMS provides discrimination based on SCCP CgPA GTA digits. This allows the operator to decide whether messages from certain CgPAs will receive PPSMS service or fall through to GTT, even if the messages meet all of the previous service selection criteria.

Number Conditioning

The RTDB stores international MSISDNs only. The received MSISDN number or SCCP CdPA digits may need to be converted to an international number to do a database lookup.

When PPSMS is required to be performed on a message and the number is not international (that is, the NAI of MSISDN number is “National (Significant) Number” or “Subscriber Number)”, the National/Local to International number conditioning is triggered.

For a National (Significant) Number, the received MSISDN digits are prepended with the default country code and for a Subscriber number, the MSISDN digits are prepended with the default country code and the default network code. If the NAI is neither International or Subscriber, the message is treated as National.

Prepaid Screening

Once the number is conditioned, the PPSMS feature performs a database search to determine if the MSISDN belongs to a prepaid subscriber. This is determined by the portability type field associated with the database entry for the MSISDN. PPSMS performs the database lookup using the international MSISDN. The individual number database is searched first, and if the number is not found, then the number range database is searched. If a match is not found in individual nor range-based database, then GTT is performed on the message. In case of MSISDN numbers in the PPSMS database being odd and the last digit of the decoded MSISDN from the FSM being 'zero', PPSMS first performs a database lookup once using the even number. If no match is found, then PPSMS performs the database lookup again, now using the odd number (without last digit).

Message Relay to IN Platform

If the database search determines that the subscriber is prepaid, the message is redirected to one of the two IN platforms using the translation data in the PPSOPTS table. If the routing indicator in the IN platform translation data is route-on-SSN, the mated application table is accessed to determine the point code/subsystem status for the IN platform, and if it has a mate. The SCCP CdPA GTA should not be changed as a result of this operation. If the RI in the translation data indicates route-on-GT, and if the Intermediate GTTLoad Sharing feature is turned on, the Mated Relay Node (MRN) table is accessed to determine the point code status and if the IN platform has a mate. Subsystem status is not maintained in the mated relay node.

Prepaid Short Message Service Intercept Message Handling

Prepaid Short Message Service Intercept (PPSMS) performs message handling in the following steps.

1. The message arrives at the EAGLE route-on-gt. The EAGLE decodes the SCCP portion and uses the data to perform the G-Port selection based on the CdPA NP, NAI, TT, SSN, and GTI. The result of the selection provides a service indicator. The service indicator is SMSMR if PPSMS is required. If a SMSMR selector does not match the incoming GT fields, the message is passed on for GTT selection.
2. If #1 indicates PPSMS is required, and the message is not a UDTS generated by EAGLE, the EAGLE performs PPSMS service.
3. If the message is a UDTS generated by the EAGLE, then regular GTT is performed on the message.
4. If the EAGLE receives a UDTS message from another node, it is treated in the same manner as any other message. If GTT is indicated, then the UDTS translation is based on the CdPAGTA, and the message is routed to the translated address. If GTT is not indicated, the UDTS is through switched via MTP routing. The one exception is that if translation fails on the UDTS, the EAGLE will not generate another UDTS to send to the originator of the UDTS that failed.
5. The TCAP/MAP portion of the message is decoded by PPSMS. If the message is not a TC_BEGIN, the message falls through to GTT.
6. If the message is a TC_BEGIN, PPSMS decodes the Operation Code of the MAP message to distinguish MO_FSMs from the rest. If the OpCode is not FSM (MAP version 1 or 2) or MO_FSM (MAP version 3), the message falls through to GTT.
7. If the OpCode is FSM (MAP version 1 or 2) or MO_FSM (MAP version 3), the MAP portion of the message is decoded and searched for a MSISDN tag. If a MSISDN tag is not found, the message falls through to GTT. For version 3 MO_FSMs, the SMRPOA parameter would contain the MSISDN tag. For version 1 or 2 FSMs, a MSISDN tag is found if the message is mobile originated. If it is mobile terminated, a MSISDN tag is not found and the message falls through to GTT.
8. If the MSISDN is found in #7, the SCCP CgPA GTA is compared to the IN platform GTAs provisioned in the PPSOPTS table. If the decoded GTA matches one of the IN platform Gas, the message falls through to GTT.
9. If the SCCP CgPA GTA in #8 does not match any of the IN platform GTAs, the MSISDN from the MAP portion is decoded and conditioned to an international number before performing the lookup. The number conditioning is based on NAI of MSISDN parameter. The number is converted to an international number, if necessary.
10. The database lookup is performed in two parts:
    • The exception or individual number database is searched for a match. If the match is found, the data associated with this entry is considered.
    • If the conditioned number is absent in the exception database, the number range database is searched. If the match is found, the data associated with this range entry is considered. If the search is unsuccessful, the result is no match.

    In case of MSISDN numbers in the PPSMS database being odd and the last digit of the decoded MSISDN from the FSM being 'zero', PPSMS first performs database lookup once using the even number. If no match is found then PPSMS performs the database lookup again, using the odd number (without last digit).

11. If a number match is found as a result of the search, the portability type field associated with the entry is examined.
    • If the portability type is in the range of Prepaid1 to Prepaid32, the IN platform translation information (PC and RI) associated with that type is retrieved from the GSM options. If the RI is SSN, the information is used to access the mated application (MAP) table for point code status and to see if the selected IN platform is in a load sharing relationship with another. If the RI is GT, and if the IGTTLoad Sharing feature is on, the mated relay node table is used for this purpose. If the point code is available, the message is routed the IN platform. If the point code is in a load sharing relationship with other point codes, messages are equally divided between them.
    • If the portability type is not in the range of Prepaid1 to Prepaid32, the message falls through to GTT.
12. If a number match is not found as a result of the search in #10, the message falls through to GTT.

MO SMS NPP Message Processing

After decoding the MTP and SCCP portion of the MSU, the system verifies whether the SCCP parameters of the message match any of the provisioned Service Selectors. If the Service Selector = smsmr, MO SMS processing begins. The TCAP portion of the message is decoded.

NPP-related functions are performed next. The incoming Called Party Number or Calling Party Number is conditioned to international format using Conditioning Actions. All Service Actions provisioned for the NPP Services are performed after verifying whether the feature is enabled and turned on.

After the NPP service functions are completed, the message is directed to post-NPP processing. The message is encoded and dispatched. If the message is redirected to Global Title Translation (GTT), translation can be performed based on the SCCP Called Party Address digits or the TCAP Called Party Number.

NPP Processing

NPP processing supports both GSM Forward Short Message Mobile Originated (MO) messages and IS41 SMDPP messages. GSM protocol supports MO-Based GSM SMS NP, Portability Check for MO SMS, and Prepaid SMS Intercept. IS41 protocol supports MO-Based IS41 SMS NP and MO SMS IS41-to-GSM Migration features.

NPP processing for GSM

NPP processing performed for GSM protocol and possible Service Actions that can be provisioned are shown in Figure 2-9. GSM protocol supports two NPP Services: MOSMSGCDPN for processing Called Party Numbers and MOSMSGCGPN for processing Calling Party Numbers. The Calling Party Number is processed first. The Calling Party Number is the MSISDN digits of the SM-RP-OA parameter of the Forward Short Message. The Called Party Number is processed second. The Called Party Number is the TP-DA digits of the SM-RP-UI parameter of the message being processed.

NPP processing for IS41

NPP processing performed for IS41 protocol and possible Service Actions that can be provisioned are shown in Figure 2-10. IS41 protocol supports two NPP Services: MOSMSICDPN for processing Called Party Numbers and MOSMSICGPN for processing Calling Party Numbers. The Calling Party Number is processed first. The Calling Party Number is the Original Originating Address (OOA) digits of the message. The Called Party Number is processed second. The Called Party Number can be either the Destination Address (DA) or Original Destination Address (ODA) parameter of the message being processed.

Post-NPP Processing

After conditioning the number, performing Service Actions, and formatting the number passed to NPP, the decoded message is encoded and sent to the correct module or destination for further processing. For IS41 protocol, only two features are supported and the message falls through to GTT. For GSM protocol, several dispositions are possible:

• The message can be sent to a Prepaid Server after PPRELAY Service Action processing.
• The message can be NACK if the FRAUDCHK Service Action determines that the message is fraudulent.
• The message can fall through to GTT after CDPNNP Service Action processing.

RTDB Lookup for NPP Services

An entry for a conditioned number can be found in either an Individual DN RTDB Table or a range DN RTDB Table. If an entry is found in the Individual DN RTDB Table, the range DN table is not searched. An Individual DN Table entry has precedence over a range DN Table entry. Most NPP Service Actions require an RTDB Lookup result. For a given NPP Service, RTDB Lookup is performed only once. This RTDB Lookup is performed by the first Service Action that needs an RTDB Lookup result.

S-Port Subscriber Differentiation

S-Port Subscriber Differentiation is used to allow use of provisioned ASD digits in place of GRN digits as an alternative Routing Number for own-network subscribers. For example, the ASD digits are used as the subscriber’s private routing number for message relay features and the GRN digits are used as the subscriber’s public routing number for query/response features.

S-Port Subscriber Differentiation processing occurs if the S-Port Subscriber Differentiation feature is enabled and turned on using Part Number 893-0379-01 and a Feature Access Key. The SUBDFRN option value must also be on to allow S-Port Subscriber Differentiation processing. The SUBDFRN option cannot be specified by the chg-sccpopts command unless the S-Port Subscriber Differentiation feature is enabled and turned on.

Provisioned ASD digits are used in place of GRN digits when these conditions are met:

• The Service Portability feature is enabled and turned on.

• The GSMSMSOPTS:SPORTTYPE or IS41SMSOPTS:SPORTTYPE option is provisioned. Refer to Table 2-8.

• The S-Port Subscriber Differentiation feature is enabled and turned on.

• The SUBDFRN option value is on.

• Service Portability is applicable.

Subscribers without provisioned ASD digits follow standard Service Portability processing and always use GRN digits.

The MTP Msgs for SCCP Apps and MTP Routed GWS Stop Action features forward MTP routed SCCP messages to the Service Module cards. The SCCP messages forwarded by either feature are processed in the same way on the Service Module cards. The difference between the two features is that the MTP Routed GWS Stop Action feature filters messages based on provisioned Gateway Screening rules on a per linkset basis and forwards only UDT, UDTS, XUDT and XUDTS SCCP messages to Service Module cards, while the MTP Msgs for SCCP Apps feature forwards all MTP routed SCCP messages to the Service Module card without filtering. Because the MTP Routed GWS Stop Action feature selectively forwards the messages to the Service Module card, the feature has less impact on SCCP performance than the MTP Msgs for SCCP Apps feature. The features can coexist, which means that both features can be turned on in the same system.

MTP Msgs for SCCP Apps

MTP routed SCCP messages are supported with the MTP Msgs for SCCP Apps feature. LOCREQ and SMSREQ messages are supported. A Feature Access Key (FAK) for part number 893-0174-01 is required to enable the MTP Msgs for SCCP Apps feature. ThisThe MTP Msgs for SCCP Apps feature (part number 893-0174-01) can be turned on and off, but cannot be enabled with a temporary FAK. GTT must be on to enable the MTP Msgs for SCCP Apps feature.

After the MTP Msgs for SCCP Apps feature is turned on, all SCCP messages are routed to Service Module cards. The Service Module card then performs SCCP decode/verification. Use of the MTP Msgs for SCCP Apps feature adversely affects the SCCP capacity because all of these messages are counted under SCCP capacity.

If the MTP routed messages have CdPA RI=GT or SSN and GTI ≠ 0 (GTI = 2 or 4), then a service selection (SRVSEL) lookup is performed using the SCCP CdPA information. If the result of the lookup is MNP service, then the message is sent to MNP handling. If a service selector does not match or the service is OFFLINE, then MTP routing is performed on the messages. MNP SCCP Service re-route is not performed on MTP routed messages.

If the MTP routed messages have CdPA GTI=0, the TCAP portion of ANSI TCAP messages is decoded. SMSMR service is invoked for SMDPP messages; IAR Base feature is invoked for Analyzed messages. For all other messages, MNP service is invoked.

The SMSMR service and IAR Base feature require the global title address to determine whether the destination of the message is Home SMSC or Home SCP. Because GTI=0 messages do not have a global title address, two additional parameters, homesmsc and homescp, for the chg-dstn and ent-dstn commands are provided for each provisioned point code to indicate whether the DPC is a Home SMSC (SMSMR service) or a Home SCP (IAR Base feature).

MNP handling checks whether the TCAP portion of the message is ITU or ANSI.

If the message has ANSI TCAP, then:

• General TCAP/MAP verification for A-Port is performed if the A-Port or IGM feature is turned on. Only LOCREQ and SMSREQ messages are handled by A-Port or IGM for MTP routed messages.

• When GTI ≠ 0, message relay is performed on non-LOCREQ and non-SMSREQ ANSI TCAP messages based on the SCCP CdPA portion of the message.

• When GTI = 0, MTP routing is performed on non-LOCREQ ANSI TCAP messages.

If the message has ITU TCAP, the IGM feature is on, and GTI ≠ 0, then:

• The message is considered for relaying based on the RTDB lookup results. General TCAP/MAP verification is not performed on the message.

• Message relay is performed based on the SCCP CdPA portion of the message with GTI = 2 or 4.

If the message has ITU TCAP, the IGM feature is on, and GTI = 0, then MTP routing of the message is performed.

ITUN-ANSI SMS Conversion is not affected by the MTP Msgs for SCCP Apps feature; ITUN-ANSI SMS Conversion handles only Registration Notification and SMS Notification messages.

MTP Routed GWS Stop Action

The MTP Routed GWS Stop Action feature (part number 893-0356-01) provides a Gateway Screening (GWS) stop action: sccp. This stop action allows IS41-based features to process MTP routed traffic. GWS rules are used to filter MTP routed SCCP messages (UDT, UDTS, XUDT, and XUDTS) on a per linkset basis. The messages are then forwarded to Service Module cards for processing by features that support MTP routed messages based on Service Selection criteria. A Feature Access Key (FAK) for part number 893-0356-01 is required to enable the MTP Routed GWS Stop Action feature. This feature can be turned on and off, but cannot be enabled with a temporary FAK. GTT must be on to enable the MTP Routed GWS Stop Action feature. The MTP Routed GWS Stop Action feature must be enabled before the sccp stop action can be provisioned, and before message processing can occur. The sccp stop action must be the last stop action in the GWS action set.

If the MTP Msgs for SCCP Apps feature is turned on, all SCCP messages are forwarded to Service Module cards without the sccp GWS stop action being executed, regardless of whether the MTP Routed GWS Stop Action feature is turned on.

After provisioning, the sccp stop action can be used by these features:

• A-Port

• G-Flex

• Info Analyzed Relay ASD

• Info Analyzed Relay Base

• Info Analyzed Relay GRN

• Info Analyzed Relay NP

• IS41 GSM Migration (IGM)

• ITUN-ANSI SMS Conversion

• MNP Circular Route Prevention

• MO-Based IS41SMS NP

• MO SMS ASD

• MO SMS B-Party Routing

• MO SMS GRN

• MO SMS IS41 to GSM Migration

• MTP MAP Screening

• MT-Based IS41 SMS NP

Refer to Database Administration – GWS User's Guide for additional information and provisioning procedures for the MTP Routed GWS Stop Action feature.

SMSREQ Handling for Migrated or Ported Subscribers

The SMSREQ Handling for Migrated or Ported Subscribers enhancement allows MTP routed SMSREQ messages to be supported by A-Port, IGM, MNPCRP, and MT-Based IS41 SMS NP features. Service selection criteria for MTP routed SMSREQ messages is the same for MTP routed LOCREQ messages. The MNP service processing for MTP routed SMSREQ messages is the same for Global Title (GT) routed SMSREQ messages. However, MTP routing is performed on MTP routed messages when these messages fall through from the MNP service. Feature precedence is applied for SMSREQ messages as shown:

1. MNPCRP - If a circular route condition is detected, a UIM is generated and MTP routing is performed on the message.

2. IGM - If the DN is own-network GSM subscriber (Portability Type = 5) and SMSREQBYPASS = No, then send an SMSREQ Error Response (Return Result message) to the originator with SMS Access Denied Reason = 5.

3. MT-Based IS41 SMS NP - If the DN matches the MT-Based IS41 SMS NP feature criteria (IS41SMSOPTS:MTSMSTYPE), the SMSREQ response is generated.

4. A-Port - A-Port relays the message based on the RTDB lookup result. If relay information is not present in the RTDB data associated with the DN, then the message is MTP routed.

5. If A-Port is not turned on, then IGM relays the SMSREQ message for only own-network subscribers if the SMSREQ response is not previously sent for subscribers not handled by IGM. If relay information is not present in the Network Entity Type (RN/SP) associated with the DN or if Network Entity Type indicates an Other Licensed Operator (OLO) subscriber, then the message is MTP routed.

6. If none of the feature processing in the previous items is performed, then the message is MTP routed.

If a feature in the precedence list is off, processing by that feature is not performed.

EPAP-related features that perform an RTDB lookup require Service Module cards (E5-SM4G, E5-SM8G-B, or SLIC cards) running the SCCPHC application. The EAGLE can be equipped with up to 32 (31+1) Service Module cards.

Features that do not perform an RTDB lookup require Service Module cards only for GTT processing that might be performed for the feature. These features can coexist in systems with EPAP, but do not require an EPAP connection.