1. EAGLE ATINP User's Guide
  2. Feature Description

2 Feature Description

This chapter describes the functions provided by the ATINP feature, including MSU protocol handling, ATI message decoding, and response message formatting.

The chapter includes an overview of the Oracle Communications EAGLE Application Processor (EPAP). EPAP provides the Realtime Database (RTDB) that is used in the database lookup functions.

ATINP Feature Overview

ATINP Functions

The ATINP feature provides number portability functions and Service Portability functions for decoding the incoming ATI message, conditioning the MSISDN to International format if needed, performing the RTDB lookup, and determining the result of the lookup.

ATINP configuration options affect the following functions and values:
  • Number conditioning of the incoming MSISDN digits before RTDB lookup is performed
  • Determination of a successful RTDB lookup
  • Controlling whether the IMSI, MSISDN, Routing Number, and Location parameters will be included or not included in the ATI ACK response message
  • Controlling the length of formatted digits for Location Information queries
  • Formatting of the IMSI, MSISDN, Routing Number, and Location parameters in the ATI ACK response message, and the maximum number of digits to be used from the SRFISMSI or entity ID in the encoding format
  • Default routing number and outbound message digits delimiter to be used in outbound message formats
  • Use of GRN digits as Routing Number digits in the ATI ACK response message for own-network subscribers (example: using GRN digits for ROP information)

Response message handling functions determine whether a success or failure response is needed (or no response), format the information in the response message, send the response, and issue any required UIMs and network management messages.

ATINP Considerations

The GTT feature must be on before the ATINP feature can be enabled.

The ATINP feature must be enabled before configuration options can be provisioned in the ATINPQOPTS table for ATINP. The Service Portability feature must be also enabled before the ATINPQOPTS SPORTTYPE configuration option can be provisioned to use Service Portability with ATINP.

The ATINP feature and the Service Portability feature must be turned on before Service Portability processing will occur for ATI Query messages.

Note:

The Service Portability feature, the IDP A-party Blocklist feature, support for ROP data, and ATINP support for Location Information use GRN data for different purposes. The IDP A-party Blocklist feature is mutually exclusive with the Service Portability feature, and this restriction is enforced in feature provisioning. Feature provisioning does not enforce the restriction that the Service Portability feature is mutually exclusive with ROP data support and ATINP support for Location Information.

The ATINPQ Local Subsystem

Local subsystems in the EAGLE are maintainable entities for query and response that are used when the STP acts as an SCP. Specific point codes can be defined for routing to local subsystems independently of the STP in the network. A local subsystem can be taken online and offline as needed in the system.

The ATINPQ local subsystem in the EAGLE processes ITU-TCAP ATI messages with the requested information parameter MNP Requested Info or Location Information. The EAGLE responds with an ATI ACK message that contains number portability and routing information or location information, or responds with an ATI NACK message if the requested information cannot be provided. The original ATI query is discarded.

If RequestedInfo contains MNP Requested Info and Location Information or other requests (for example: subscriberState), then RequestedInfo is considered to contain only MNP Requested Info. The other requests will be ignored. Refer to Table 2-1 for handling of multiple requests in RequestedInfo. A Location Information query is processed only if ATINP is enabled and turned on and the ATISUPPLOCINFO option is set to ON.

Table 2-1 Handling of Multiple Requests in RequestedInfo

MNP Requested Info Location Information any other request Request handled by ATINPQ Subsystem

No

No

Yes

UIM 1402: ATINPQ: Invalid Requested Info will be generated and an error response will be sent

Yes

No

No

MNP Requested Info

Yes

Yes

No

MNP Requested Info

Yes

Yes

Yes

MNP Requested Info

No

Yes

No

Location Information

No

Yes

Yes

Location Information

ATINP supports ANSI MTP/SCCP and ITU-TCAP ATI query or ITU MTP/SCCP and ITU-TCAP ATI query.

For ATINP, EAGLE supports ANSI, ITU-I, ITU-N, ITU-I Spare, and ITU-N Spare capability point code types. ITU-N24 point codes are not supported. Capability point codes for the ATINPQ local subsystem can be configured only after the ATINP feature is enabled.

The ATINPQ local subsystem can have a mate subsystem and a concerned point code group assigned to it. The ATINPQ local subsystem cannot be set to Load Shared mode (as end nodes do not perform load sharing), but can be set only to Dominant or Solitary mode. The ATINPQ local subsystem can be entered in MAP table if the ATINP feature is enabled.

The ATINPQ local subsystem can be taken online and offline using the procedures in Changing the State of a Subsystem Application.

Messages for the ATINPQ Local Subsystem

Messages for the ATINPQ local subsystem can arrive Rt-on-SSN or Rt-on-GT. All MSUs must contain either the EAGLE true or secondary point code (TSPC), or the ATINPQ capability point code (CPC) in the DPC field of the message. Traditionally, messages for local subsystems were allowed to have the DPC as the EAGLE STP CPC. However, it is strongly recommended to use the ATINPQ CPC for ATI queries, and not the CPC of the STP for network management issues that can arise.

Rt-on-SSN Handling

If the message arrives Rt-on-SSN, it must contain the EAGLE ATINPQ subsystem number in the Called Party Subsystem field of the message.

If the ATINPQ local subsystem is online, the DPC field can contain either the EAGLE true or secondary point code or the ATINPQ capability point code. Any response message will use the true or secondary point code assigned to the EAGLE as the OPC. Because the EAGLE cannot generate an SSP when a message arrives Rt-on-SSN for the EAGLE CPC, nodes sending Rt-on-SSN traffic should use the true or secondary point code.

If the ATINPQ local subsystem is offline and the mated subsystem is available, the EAGLE will generate a network management message to force the network to transition traffic to the mate.

Rt-on-GT Handling

Rt-on-GT MSUs can arrive either with SCCP CdPA information that matches an EAGLE service selector, or with a GTA address that has been provisioned to translate to the ATINPQ local subsystem.

If the ATINPQ subsystem is online, the DPC field can contain either the EAGLE true or secondary point code or the ATINPQ capability point code. The query is directed to the local subsystem and processed. Any response message will use the true or secondary point code assigned to the EAGLE as the OPC.

If the ATINPQ local subsystem is offline and the mated subsystem is available, the EAGLE will act as both STP and SCP, and reroute the message to the mated subsystem. If a Rt-on-GT message arrives for the EAGLE true or secondary point code, the EAGLE cannot generate a TFP. The EAGLE handles and reroutes these messages, instead of forcing the adjacent node to route to the mate. Therefore, nodes that send Rt-on-GT traffic to an EAGLE should use anf ATINPQ CPC, not the EAGLE TSPC.

Network Management Responses

The EAGLE must reply to network management queries about the current state of the local subsystem. When the local subsystem changes state, network management messages are sent to the CSPC group.

Multiple Local Subsystems

The EAGLE supports provisioning Capability Point Codes for two or more local subsystems, allowing local subsystems for two or more EPAP-based features to operate at the same time in the system. For example, local subsystems for the ATINP feature and the EIR feature can coexist in the system.

Though queries meant for any local system will still be processed if they are sent with DPC = STP CPC, it is strongly recommended not to use the STP CPC for such queries. Instead, the CPC for the appropriate subsystem should be used as the DPC of the message. For instance, for LNP queries use the LNP CPC, not the STP CPC. For ATI queries, use the ATINPQ CPC, and so on.

ATINP Configuration Options

The ATINP configuration options described in Table 2-2 are used for the following functions:

  • Specify the format of the IMSI, MSISDN, Routing Number, or Location parameters in the ATI ACK response message, and the maximum number of digits to be used from the SRFIMSI or Entity ID in the encoding format.
  • Determine whether the IMSI, MSISDN, Routing Number, or Location parameter is included or not included in the ATI ACK response message.
  • Specify the default routing number and outbound message digits delimiter to be used in outbound message formats.
  • Specify the number conditioning to be performed on the MSISDN digits in the incoming ATI query message before RTDB lookup is performed, and indicate the determination of a successful RTDB lookup.
  • Specify Service Portability processing that can be performed for ATI messages.

Table 2-2 ATINP Options

Option Value Action in the STP
ATIACKIMSI - used for IMSI parameter encoding in the ATI ACK message NONE

This is the default value.

The IMSI parameter is not included in the ATI ACK response message.
SRFIMSI If an Entity was found during lookup and
  • If SRFIMSI is provisioned in the Entity, then encode the outgoing IMSI digits as the SRFIMSI.
  • If SRFIMSI is not provisioned in the Entity, then do not include the IMSI parameter in the ATI ACK response.
ASD

The IMSI digits in the ATI ACK response are encoded as the ASD (Additional Subscriber Data) if ASD is found during RTDB lookup and ASD was provisioned in the EPAP.

If ASD is not available, the IMSI parameter is not included in the response message.

GRN The IMSI digits in the ATI ACK response are encoded as the GRN if GRN is supported and found during RTDB lookup and GRN was provisioned in the EPAP.

If GRN is not supported or not provisioned, the IMSI parameter is not included in the response message.

ATIACKMSISDN - specifies the inclusion and formatting of the MSISDN in the ATI ACK response NONE

MSISDN parameter is not included in the ATI ACK response.

MSISDN

This is the default value.

MSISDN digits in the ATI ACK response are encoded as the MSISDN from the incoming ATI query.

If the RTDB lookup matched on odd number of digits, then the MSISDN is encoded with the match in the RTDB without the trailing 0.
ASD The MSISDN in the ATI ACK response is encoded as the ASD (Additional Subscriber Data) if the MSISDN was found during RTDB lookup and ASD was provisioned in EPAP.

If ASD is not available, the MSISDN parameter is not included in the ATI ACK response.

ASDDLMMSISDN The MSISDN digits in the ATI ACK response message are encoded as ASD (if available) + ATIDLM (if not NONE) + MSISDN from the incoming message.

If the RTDB lookup matched on odd number of digits, then the MSISDN is encoded with the match in the RTDB without the trailing 0.
GRN The MSISDN digits in the ATI ACK response message are encoded as GRN if supported and found during RTDB lookup, and provisioned in the EPAP.

If GRN is not supported or not provisioned, the MSISDN parameter is not encoded in the ATI ACK response.
GRNDLMMSISDN The MSISDN digits in the ATI ACK response are encoded as GRN (if supported and available) + ATIDLM (if not NONE) + MSISDN from the incoming message.

When GRN field is supported, it is returned in the entity lookup data if GRN entity was found. If GRN field is not supported or not available by EPAP, it is not included in any formats specifying GRN.

If the RTDB lookup matched on odd number of digits, then the MSISDN is encoded with the match in the RTDB without the trailing 0.
ATIACKRN - specifies the formatting of the Routing Number digits in the ATI ACK response NONE The Routing Number parameter is not included in the response.
RN

This option value is expected to be used when Service Portability is used with ATINP.

If Entity type RN was found in RTDB lookup, the subscriber is generally considered to be a foreign subscriber.

The exception is the case when Entity data is RN with PT=0, and either the IGM feature is on or the Service Portability feature is enabled; the subscriber is considered to be an own-network IS41 subscriber in this case. The Entity type is considered to be SP.

Foreign Subscribers

Encode Routing Number digits as the found Entity ID. (Not affected by Service Portability processing.)

Own Subscriber

If the Service Portability feature is ON, the Entity type is SP (GSM subscriber), the SPORTTYPE option value is GSM or ALL, and GRN is available, encode the Routing Number as GRN. If GRN is not available, a UIM is generated and the Routing Number is not included in the response.

If the Service Portability feature is ON, the Entity type is SP (GSM subscriber), the SPORTTYPE option value is IS41 or NONE, the behavior is the same as when the Service Portability feature is OFF.

If the Service Portability feature is ON, the Entity type is RN and PT = 0 (IS41 subscriber), the SPORTTYPE option value is IS41 or ALL, and GRN is available, encode the Routing Number as GRN. If GRN is not available, a UIM is generated and the Routing Number is not included in the response.

If the Service Portability feature is ON, the Entity type is RN and PT = 0 (IS41 subscriber), the SPORTTYPE option value is GSM or NONE, the behavior is the same as when the Service Portability feature is OFF.

If the Service Portability feature is ON, and a DN is not found in the RTDB, the DN is found but no Entity is found, or the DN is found and the Entity type is not SP or RN with PT = 0, the behavior is the same as when the Service Portability feature is OFF

When the Service Portability feature is OFF, the Routing Number digits are encoded as the ATIDFLTRN option value instead of the Entity ID, if the ATIDFLTRN value is not NONE and one of the following conditions is true:
  • MSISDN was found but No Entity found in RTDB.
  • MSISDN was not found in RTDB (only in the case of ATINPTYPE=ALWAYS; for ATINPTYPE=ANY, this results in a lookup failure).
  • Entity was found with type SP or considered to be type SP.

In all other cases, the Routing Number parameter is not included in the ATI ACK response.

This is the default value.

RNSP If an Entity was found in RTDB lookup and Entity type was either SP or RN, encode Routing Number digits as the found Entity ID.

The Routing Number digits are encoded as the ATIDFLTRN option value if the ATIDFLTRN value is not NONE and one of the following conditions is true:

  • MSISDN found but Entity was not found.
  • MSISDN was not found in RTDB (Only in case of ATINPTYPE=ALWAYS. For ATINPTYPE=ANY, this results in a lookup failure).
  • Entity of type other than SP or RN was found.

In all other cases, the Routing Number parameter is not included in the response.

ASDDLMRNSP Encode the Routing Number as ASD (if available from lookup Entity) + ATIDLM (if not NONE) + RNSP.

RNSP is encoded as described for the ATIACKRN=RNSP value.

If formatting results in 0 digits or only DLM digits, the Routing Number parameter is not included in the response message.

If ATIDLM is not NONE, and ASD digits are available, DLM is included even if RN/SP does not have any digits (resulting in ASD+DLM).

The ASD field is returned in the Entity lookup data, if Entity was found. If the ASD field is not provisioned in EPAP, it is not included in any formats specifying ASD.

RNSPDLMASD Encode Routing Number digits as RN/SP + ATIDLM (if not NONE) + ASD (if available from lookup Entity).

RN/SP is encoded as described for the ATIACKRN=RNSP option.

If formatting results in 0 digits or only DLM digits, the Routing Number is not included in the response message.

If ATIDLM is not NONE and ASD digits are available, DLM is included even if RN/SP does not have any digits, resulting in DLM+ASD.
SRFIMSI Encode Routing Number digits as SRFIMSI configured in the entity data.

If SRFIMSI was not found (MSISDN not found in RTDB, MSISDN found but no Entity found, or Entity found but SRFIMSI not configured), then the Routing Number is not included in the response message.

SRFIMSIDLMASD Encode Routing Number digits as SRFIMSI + ATIDLM (if not NONE) + ASD (if available from lookup Entity).

SRFIMSI is encoded as described for the ATIACKRN=SRFIMSI option.

If formatting results in 0 digits or only DLM digits, the Routing Number is not included in the response message.

If ATIDLM is not NONE and ASD digits are available, DLM is included even if SRFIMSI does not have any digits, resulting in DLM+ASD.

ASDDLMSRFIMSI Encode Routing Number as ASD (if available from lookup Entity) + ATIDLM (if not NONE) + SRFIMSI.

SRFIMSI is encoded as described for the ATIACKRN=SRFIMSI option.

If formatting results in 0 digits or only DLM digits, the Routing Number parameter is not included in the response message.

If ATIDLM is not NONE and ASD digits are available, DLM is included even if SRFIMSI does not have any digits (resulting in ASD+DLM).

The ASD field is returned in the Entity lookup data (if Entity was found). If the ASD field is not provisioned in EPAP, it is not included in any formats specifying ASD.

GRNDLMRNSP Encode Routing Number as GRN (if supported and available from lookup Entity) + ATIDLM (if not NONE) + RNSP.

RNSP is encoded as described for the ATIACKRN = RNSP option.

If formatting results in 0 digits or only DLM digits, the Routing Number parameter is not included in the response message.

If ATIDLM is not NONE and GRN digits are available, DLM is included even if RN/SP does not have any digits, resulting in GRN+DLM.

The GRN field is returned in the Entity lookup data, if GRN Entity was found. If the GRN field is not provisioned in EPAP, it is not included in any formats specifying GRN.

RNSPDLMGRN Encode Routing Number as RN/SP + ATIDLM (if not NONE) + GRN (if supported and available from lookup entity).

RN/SP is encoded as described for the ATIACKRN = RNSP option.

If formatting results in 0 digits or only DLM digits, the Routing Number parameter is not included in the response message.

If ATIDLM is not NONE and GRN digits are available, DLM is included even if RN/SP does not have any digits, resulting in DLM+GRN.

The GRN field is returned in the Entity lookup data, if GRN Entity was found. If the GRN field is not provisioned in EPAP, it is not included in any formats specifying GRN.

SRFIMSIDLMGRN Encode Routing Number as SRFIMSI + ATIDLM (if not NONE) + GRN (if supported and available from lookup entity).

Note: SRFIMSI digits configured with RN or SP entity data are used only to encode the Routing Number.

SRFIMSI is encoded as described for the ATIACKRN = SRFIMSI option.

If formatting results in 0 digits or only DLM digits, the Routing Number parameter is not included in the response message.

If ATIDLM is not NONE and GRN digits are available, DLM is included even if SRFIMSI does not have any digits, resulting in DLM+GRN.

The GRN field is returned in the Entity lookup data, if GRN Entity was found. If the GRN field is not provisioned in EPAP, it is not included in any formats specifying GRN.

GRNDLMSRFIMSI Encode Routing Number as GRN (if supported and available from lookup entity) + ATIDLM (if not NONE) + SRFIMSI.

SRFIMSI digits configured with RN or SP entity data are used only to encode the Routing Number.

SRFIMSI is encoded as described for the ATIACKRN = SRFIMSI option.

If formatting results in 0 digits or only DLM digits, the Routing Number parameter is not included in the response message.

If ATIDLM is not NONE and GRN digits are available, DLM is included even if SRFIMSI does not have any digits, resulting in GRN+DLM.

The GRN field is returned in the Entity lookup data, if GRN Entity was found. If the GRN field is not provisioned in EPAP, it is not included in any formats specifying GRN.

ATIACKVLRNUM - specifies the formatting of the vlr-number within Location Information in the ATI ACK response; affects protocol processing only if ATINP feature is turned on

Note:

If vlr-number does not have any digits to encode due to Entity not found or ATIDFLTRN not provisioned, then the incoming MSISDN is encoded as vlr-number.
ASD

The vlr-number is encoded as ASD configured in the Entity data.

If ASD was not found (for example: MSISDN is not found in RTDB or MSISDN is found but no ASD is found), then the vlr-number is encoded as incoming MSISDN.
ASDDLMRNSP

The vlr-number is encoded as ASD, if available from RTDB lookup + ATINPQOPTS:ATIDLM (if not NONE) + RNSP. The RNSP part is encoded as described in the option ATIACKVLRNUM = RNSP, except for the MSISDN encoding if RN/SP is not found.

If ATIDLM is not NONE and ASD digits are available, DLM is included even if RN/SP does not have any digits (resulting in ASD+DLM).

If the formatting results in no digits or only DLM digits, the vlr-number is encoded with only MSISDN in the response.
ASDDLMSRFIMSI

The routing number is encoded as ASD (if available from RTDB lookup) + ATINPQOPTS:ATIDLM (if not NONE) + SRFIMSI. The SRFIMSI part is encoded as described in the option ATIACKVLRNUM = SRFIMSI.

If ATIDLM is not NONE and ASD digits are available, DLM is included even if SRFIMSI does not have any digits (resulting in DLM+ASD).

If the formatting results in no digits or only DLM digits, the vlr-number is encoded with only MSISDN in the response.
ASDMSISDN

The vlr-number in the ATI ACK response is encoded as ASD (if found during RTDB lookup) + incoming MSISDN.

If ASD was not found (for example: MSISDN is not found in RTDB or MSISDN is found but no ASD is found), then the vlr-number is encoded as incoming MSISDN.
GRNDLMSRFIMSI

The vlr-number is encoded as GRN (if available from RTDB lookup) + ATINPQOPTS:ATIDLM (if not NONE) + SRFIMSI. The SRFIMSI part is encoded as described in the option ATIACKVLRNUM= SRFIMSI.

If ATIDLM is not NONE and GRN digits are available, DLM is included even if SRFIMSI does not have any digits (resulting in GRN+DLM).

If the formatting results in no digits or only DLM digits, the vlr-number is encoded with only MSISDN in the response.
GRNDLMRNSP

The vlr-number is encodedas GRN (if available from RTDB lookup) + ATINPQOPTS:ATIDLM (if not NONE) + RNSP. The RNSP part is encoded as described in the option ATIACKVLRNUM = RNSP, except for the MSISDN encoding if RN/SP is not found.

If ATIDLM is not NONE and GRN digits are available, DLM is included even if RN/SP does not have any digits (resulting in GRN+DLM).

If the formatting results in no digits or only DLM digits, the vlr-number is encoded with only MSISDN in the response.
MSISDN

The vlr-number in the ATI ACK response is encoded as the incoming MSISDN.
RN If Entity = RN was found in RTDB lookup, the subscriber is considered to be a foreign subscriber, except in the special case when Entity = RN/PT=0 and either the IGM feature is turned on or the S-Port feature was enabled. If the S-Port feature was enabled, the subscriber is considered IS41 Own Subscriber and is not considered to be a foreign subscriber.

For Foreign Subscriber

Encode vlr-number digits as found in Entity (RN). This specifies that the vlr-number in the ATI ACK response is encoded as RN, if found during RTDB lookup. This is not affected by Service Portability (S-Port).

For Own Subscriber

When the Service Portability feature (S-Port) is ON:

IF Entity type SP is found (considered GSM subscribers)

IF SPORTTYPE = GSM or ALL,

IF EPAP GRN is available,

THEN Encode vlr-number as EPAP GRN.

ELSE

  • UIM: 1426 S-Port: Missing GRN for srvc prtd subs
  • Standard ATI ACK response is encoded with MSISDN as vlr-number.

ELSE (SPORTTYPE = IS41 or NONE)

Same behavior as when Service Portability is off

ELSE IF Entity is found with data RN/PT=0 (IS-41 subscribers):

IF SPORTTYPE = IS41 or ALL,

IF EPAP GRN is available,

THEN Encode vlr-number as EPAP GRN.

ELSE

  • UIM: 1426: S-Port: Missing GRN for srvc prtd subs
  • Standard ATI response is encoded with MSISDN as vlr-number.

ELSE (SPORTTYPE = GSM or NONE)

Same behavior as when Service Portability is off

ELSE

(implies S-Port is ON and either:

  • DN not found in RTDB, or
  • DN found and no entity, or
  • DN found and Entity neither SP nor RN/0)

Same behavior as when Service Portability is off

When the Service Portability feature (S-Port) is OFF:

IF ATINPQOPTS:ATIDFLTRN is not NONE and any of the following is true:

  • MSISDN was found but no Entity was found in RTDB.
  • MSISDN was not found in RTDB. (This applies only when ATINPTYPE=ALWAYS. For ATINPTYPE=ANY, this results in an RTDB lookup failure.)
  • Entity was found with type SP. (If IGM is ON or S-Port is enabled, and Entity is RN/PT=0,then this is considered to be Entity type SP, not RN.)

THEN ATIDFLTRN is used in place of the Entity. The vlr-number digits are encoded as ATIDFLTRN.

ELSE The vlr-number parameter is encoded as incoming MSISDN in the response.
RNMSISDN

The vlr-number in the ATI ACK response is encoded as RN, if found during RTDB lookup, + incoming MSISDN.

IF ATINPQOPTS:ATIDFLTRN is not NONE and any of the following is true:

  • MSISDN was found but no Entity found in RTDB
  • MSISDN was not found in RTDB (This applies only when ATINPTYPE=ALWAYS. For ATINPTYPE=ANY, this results in an RTDB lookup failure.)
  • Entity was found with type SP (If IGM is ON or S-Port is enabled, and entity data is RN/PT=0, it is considered to be of type SP, not RN.)

THEN ATIDFLTRN is used in place of Entity. The vlr-number is encoded as ATIDFLTRN + incoming MSISDN.

IF ATINPQOPTS:ATIDFLTRN is NONE,

THEN the vlr-number is encoded as incoming MSISDN in the response.
RNSP If Entity was found during NPDB lookup and Entity type was either SP or RN, encode vlr-number as the found entity ID.

Otherwise, if ATINPQOPTS:ATIDFLTRN is not NONE and any of the following conditions are met, the vlr-number is encoded as ATIDFLTRN:

  • MSISDN was found, but Entity was not found in RTDB.
  • MSISDN was not found in RTDB. This applies only when ATINPTYPE=ALWAYS. For ATINPTYPE=ANY, this results in a lookup failure.
  • Entity of type other than SP or RN was found.

In all other cases, vlr-number is encoded as the incoming MSISDN in the ATI ACK response.
RNSPDLMASD

The vlr-number is encloded as RN/SP + ATIDLM (if not NONE) + ASD (if available from RTDB lookup). RN/SP is encoded as described in the option ATIACKRN = RNSP, except for the MSISDN encoding if RN/SP not found.

If ATIDLM is not NONE and ASD digits are available, DLM is included even if RN/SP does not have any digits (resulting in DLM+ASD).

If the formatting results in no digits or only DLM digits, the vlr-number is encoded with only MSISDN in the response.
RNSPDLMGRN

The vlr-number is encoded as RN/SP + ATIDLM (if not NONE) + GRN (if available from RTDB lookup). RN/SP is encoded as described in the option ATIACKRN = RNSP, except for the MSISDN encoding if RN/SP is not found.

If ATIDLM is not NONE and GRN digits are available, DLM is included even if RN/SP does not have any digits (resulting in DLM+GRN).

If the formatting results in no digits or only DLM digits, the vlr-number is encoded with only MSISDN in the response.
RNSPMSISDN

This is the default value.

If Entity was found during RTDB lookup and Entity type was SP or RN, encode vlr-number as the found Entity type + incoming MSISDN.

ELSE IF ATINPQOPTS:ATIDFLTRN is not NONE and any of the following is true:

  • MSISDN was found, but Entity was not found in RTDB.
  • MSISDN was not found in RTDB. This applies only when ATINPTYPE=ALWAYS. For ATINPTYPE=ANY, this results in a lookup failure.
  • Entity of type other than SP or RN was found.

THEN vlr-number is encoded as ATIDFLTRN.

IF ATINPQOPTS:ATIDFLTRN is NONE,

THEN vlr-number is encoded as incoming MSISDN in the response.
SRFIMSI

The vlr-number is encoded as SRFIMSI is configured in the Entity data.

If SRFIMSI was not found (for example: MSISDN not found in RTDB, MSISDN found but no Entity found, or SP/RN Entity found but SRFIMSI not configured), then the vlr-number is encoded as the incoming MSISDN.

SRFIMSI digits configured with only Entity type RN or SP are used to encode vlr-number.
SRFIMSIDLMASD

The vlr-number is encoded as SRFIMSI + ATIDLM (if not NONE) + ASD (if supported and available from RTDB lookup). SRFIMSI is encoded as described in the option ATIACKVLRNUM = SRFIMSI.

If ATIDLM is not NONE and ASD digits are available, DLM is included even if SRFIMSI does not have any digits (resulting in DLM+ASD).

If the formatting results in no digits or only DLM digits, the vlr-number is encoded with only MSISDN in the response.
SRFIMSIDLMGRN

The vlr-number is encoded as SRFIMSI + ATIDLM (if not NONE) + GRN (if available from RTDB lookup). SRFIMSI is encoded as described in the option ATIACKVLRNUM= SRFIMSI.

If ATIDLM is not NONE and GRN digits are available, DLM is included even if SRFIMSI does not have any digits (resulting in DLM+GRN).

If the formatting results in no digits or only DLM digits, the vlr-number is encoded with only MSISDN in the response.
ATIDFLTRN - Default Routing Number used in encoding outgoing formats in the ATI ACK response in cases where an RN is not returned from an RTDB lookup NONE

This option can be set to NONE at any time. The default value is NONE.

The specific encoding is described further in other option value descriptions.
HEX (1-15 digits)
ATIDLM - specifies whether delimiter digits or no delimiter is to be used in encoding outbound digits in ATI ACK response NONE

This option can be set to NONE at any time by the user. The default value is NONE.

HEX (1-15 digits)
ATINPTYPE - specifies when an RTDB lookup is successful ANY

MSISDN lookup is considered successful when any match is found (RN, SP, and match with no entity, GRN with PT=0xFF). See ATINP Protocol Handling of MSUs for a description of determination of success.

This specifically excludes the case when MSISDN is not found in RTDB.
ALWAYS

The lookup is always considered to be successful whether or not MSISDN is found in RTDB match.

ENTITYLEN - maximum number of digits to be used from RTDB lookup data (SRFIMSI or Entity ID) to encode Routing Number digits in the encoding format specified by the ATIACKRN option

If Entity ID or SRFIMSI is not being used by the specified ATIACKRN format, this option does not apply.

NONE

This is the default value.

The SRFIMSI or Entity ID is used without modification in the ATIACKRN format specified.
Decimal (1-15)

Example: If the SRFIMSIDLMASD format is specified, ENTITYLEN = 5, SRFIMSI from Entity = 1234567890 (10 digits), ASD = 123, and DLM = 55, then a maximum of 5 digits is used from SRFIMSI to encode the format as 12345 + 55 + 123.

If ENTITYLEN = NONE, then all ten digits from SRFIMSI would be used.

The same applies to formats that encode an Entity ID.

OFF - Disables or turns off a comma-separated list of feature options

 ATISUPP

LOCINFO

 This value specifies that Location Information request is not processed by the ATINP subsystem if the ATINP feature is turned on.

This is the default value for ATISUPPLOCINFO.

ON - Enables or turns on a comma-separated list of feature options

 ATISUPP

LOCINFO

 This value specifies that Location Information request is processed by the ATINP subsystem if the ATINP feature is turned on.
SNAI - specifies either that the NAI of the incoming MSISDN digits is considered to be International or International regardless of the NAI value in the incoming MSISDN, or that the NAI value determines whether number conditioning to International format is needed before RTDB lookup INTL The NAI of the incoming MSISDN digits is considered to be International. No conditioning is performed on the MSISDN before RTDB lookup.
NAT The NAI of the incoming MSISDN digits is considered to be National. The MSISDN is conditioned to international format before RTDB lookup by pre-pending the provisioned STPOPTS default country code (DEFCC) parameter value.

The STPOPTS DEFCC parameter must be provisioned to a value other than NONE before the ATINP feature can be turned on. The DEFCC value cannot be set to NONE after the ATINP feature is turned on.
NAI

This is the default value.

The NAI field of the MSISDN parameter determines whether number conditioning is required before RTDB lookup.

If NAI is INTL (0x01) or Network Specific Number (0x3), then the number is considered to be International and no conditioning is performed before RTDB lookup.

If NAI is not considered INTL, it is considered to be National. The STPOPTS default country code (DEFCC) value is pre-pended to the MSISDN to condition it to international format before RTDB lookup.

SPORTTYPE - indicates the Service Portability processing that is requested for ATI queries for own-network subscribers; can be provisioned when the Service Portability feature is enabled but not turned on; impacts protocol processing only if the Service Portability feature is turned on. NONE

This is the default value.

No Service Portability processing is requested.

GSM

Service Portability is requested for ATI queries for own-network GSM subscribers (Entity = SP).

IS41

Service Portability is requested for ATI queries for own-network IS41 subscribers (Entity = RN, PT = 0).

ALL

GSM and IS41 Service Portability is requested for own-network subscribers (Entity = SP or Entity = RN, PT = 0).

VLRNUMLEN - indicates the maximum number of digits that can be encoded as vlr-number in ATI ACK, as defined by ATIACKVLRNUM

 Decimal (1-40)

The default value is 40.

Example: If ATIACKVLRNUM = RNSPMSISDN format is specified, VLRNUMLEN = 12, MSISDN is 1234567890, entity RN from RTDB lookup was 13579, then the vlr-number digits would be 135791234567890. With VLRNUMLEN = 12, the vlr- number digits in the Location Information field of response message are encoded as 135791234567.

Note:

If the Service Portability feature is enabled or the IGM feature is turned on, and RTDB lookup results in Entity = RN and PT=0, then the Entity is considered to be SP.

If the RTDB lookup matched on odd number of digits, then the MSISDN is encoded with the match in the RTDB without the trailing 0.

ATINP Protocol Handling of MSUs

ATINP supports SCCP UDT and non-segmented XUDT Class 0 and Class 1 messages.

The high-level ATINP message processing flow, after the MSU reaches the active local subsystem is:

  1. Decode and verify the incoming ATI message.

    The requestedInfo parameter must be MNP Requested Info or Location Information. If message contains both requests (MNP Requested Info and Location Information), then MNP Requested Info is processed.

    The incoming MSISDN must have at least one digit.

    The information in each MSU is decoded and verified on the LIM card. SCCP messages to the EAGLE (Service Indicator = 3) are forwarded to Service Module cards for processing.

    Response messages and UIMs (see ATINPQ Subsystem UIMs) can be generated for various common decode errors and for some ATINP-specific decode errors. Some malformed messages do not generate any response.

  2. Condition the incoming MSISDN to international format if it is not considered to be international already.

    An MSISDN of 15 digits or less will be conditioned to International format if needed.

    The MSISDN is considered to be in International format if either of the following conditions is true:
    • The ATINP option SNAI=INTL is provisioned. See ATINP Configuration Options.
    • The ATINP option SNAI=NAI is provisioned and the Nature of Address field in the MSISDN is INTL (0x1) or Network Specific Number (0x3).

      An MSISDN of more than 15 digits is not conditioned for lookup. If the provisioned value of the ATINPTYPE option is ALWAYS, a response is sent for "MSISDN NOT Found in NPDB".

      A trailing Stop Digit (0xF) in the MSISDN is treated as filler and will not be considered as part of the MSISDN during lookup.

  3. Search the RTDB to locate the conditioned MSISDN.

    If the conditioned MSISDN is not found in the individual entries, the range entries are searched (odd/even number lookups are supported).

  4. Determine whether the lookup is considered successful, based on provisioned ATINP options.

    The provisioned ATINPTYPE option value determines whether the lookup is considered to be successful. See Table 2-3.

  5. If the lookup is successful, use the lookup information and ATINP options to encode the ATI ACK response message, and route the response to the originator of the ATI query. See ATINP Configuration Options.

    Note:

    In a successful DN lookup, if ASD is part of one of the entities, Additional Subscriber Data will be considered in formatting of the outgoing response message.
  6. If the lookup is not successful, send an ATI NACK response message with the appropriate error code.
  7. Discard the original ATI message.

See ATINP Configuration Options for option descriptions and response formats.

Table 2-3 RTDB Lookup Success Determination

ATINPTYPE Option DN found in RTDB Entity Found Entity Type Portability Type Lookup Success
ALWAYS N/A N/A N/A N/A Success
ANY No N/A N/A N/A Failure
  Yes No N/A N/A Success
  Yes SP N/A Success
RN N/A Success
GRN 0xFF Success
VMS 0xFF Success
All other cases are considered lookup failure.

ATINP Return Result Message

A Return Result message ("ATI ACK" message) is used to return the result of the ATI NP Query when the RTDB lookup is considered to be successful.

The Return Result message includes Number Portability Status. Routing Number digits, MSISDN digits, and IMSI digits can be included, and ASD and GRN data can be used, depending on RTDB lookup results and ATINP configuration option values. ATINP Configuration Options describes the options and the encoding results for each option value.

Routing Number

If the ATIACKRN option value is not none, routing number information is included in the response message. The ATIACKRN option values determine the data from the RTDB lookup that is used in the outgoing RN. (See ATINP Configuration Options.)

A default routing number can be provisioned using the ATIDFLTRN option, to be used in the outgoing message formats when an RN is not returned from the RTDB lookup.

Additional Subscriber Data is included in some of the formats of the return result information if it is available in the found Entity. The following formats consider Additional Subscriber Data (ASD) digits for encoding the outgoing RN parameter:
  • ASD+DLM+RNSP
  • RNSP+DLM+ASD
  • SRFIMSI+DLM+ASD
  • ASD+DLM+SRFIMSI
Generic Routing Number (GRN) digits included in an Entity can be used in formatting the outgoing RN. The Generic Routing Number can be used in identifying GSM or IS41 own-network subscribers for Service Portability, or for identifying members of ROPs (CNL clusters). The following formats consider Generic Routing Number (GRN) digits for encoding the outgoing RN parameter:
  • GRN+DLM+RNSP
  • RNSP+DLM+GRN
  • SRFIMSI+DLM+GRN
  • GRN+DLM+SRFIMSI

Note:

If the RTDB Entity type is RN with PT=0 and either the IGM feature is On or the Service Portability feature is enabled, the subscriber is considered to be an own-network IS41 subscriber, and the Entity type is treated as SP. See the ATIACKRN=RN configuration option description in ATINP Configuration Options.

A maximum of 40 digits will be encoded in the routeingNumber field. Though the specified length of routeingNumber is 1-5 bytes, ATINP allows encoding of up to 40 digits, based on the ATIACKRN ATINP option value. if the format results in more than 40 digits, the digits will be truncated to satisfy the 40-digit limit. If truncation of digits occurs, UIM 1403 “LSS: Dgts truncated in encd parms” will be generated.

An outbound message digits delimiter and a maximum number of digits to be used from Entity data can be provisioned for use in the encoding formats.

If an odd number of digits is encoded, a filler of 0xF is used as the last digit.

IMSI Digits

If the ATIACKIMSI option value is not none, IMSI digits are included in the response, as indicated by the following ATIACKIMSI values:
  • SRFIMSI - If an Entity was found during lookup and SRFIMSI was provisioned in the Entity, then the IMSI digits are encoded as the SRFIMSI value.
  • ASD - If an Entity was found during RTDB lookup and ASD (Additional Subscriber Data) was provisioned in the EPAP Entity, then IMSI digits are encoded as the ASD. If ASD is not available, the IMSI parameter will not be encoded in the response message.
  • GRN - If an Entity was found during RTDB lookup and GRN (Generic Routing Number) was provisioned in the EPAP Entity, then IMSI digits are encoded as the GRN. If GRN is not available, the IMSI parameter will not be encoded in the response message.

The ASD format considers ASD digits for encoding the outgoing IMSI parameter.

The Generic Routing Number can be used in identifying GSM or IS41 own-network subscribers for Service Portability, or for identifying members of ROPs (CNL clusters). The GRN format considers GRN digits for encoding the outgoing IMSI parameter.

If an odd number of digits is encoded, a filler of 0xF is used as the last digit.

MSISDN

If the ATIACKMSISDN option value is not none, MSISDN digits are included in the response. The digits can be either the MSISDN from the incoming message, Additional Subscriber Data found in the EPAP Entity, Generic Routing Number found in the EPAP Entity, or a combination of MSISDN, ASD or GRN, and digits delimiter.

The following formats consider ASD digits for encoding the outgoing MSISDN parameter:
  • ASD
  • ASD+DLM+MSISDN
Generic Routing Number (GRN) digits included in an Entity can be used in formatting the outgoing MSISDN. The Generic Routing Number can be used in identifying GSM or IS41 own-network subscribers for Service Portability, or for identifying members of ROPs (CNL clusters). The following formats consider GRN digits for encoding the outgoing MSISDN parameter:
  • GRN
  • GRN+DLM+MSISDN

A maximum of 40 digits will be encoded in the MSISDN digits field. Though the specified length of MSISDN is 1-9 bytes – 1 byte for nature of address/numbering plan, eight bytes for digits, ATINP will allow encoding of up to 40 digits for this field, based on the ATIACKMSISDN ATINP option value. If the format results in more than 40 digits, the digits will be truncated to satisfy the 40 digit limit. UIM 1403: “LSS: Dgts truncated in encd parms” will be generated.

If an odd number of digits was encoded, a filler of 0xF is used as the last digit. The Nature of Address field will be copied from the incoming MSISDN.

Number Portability Status

The portability type of the MSISDN can represent the following types of numbers:
  • An own number ported out
  • An own number not ported out
  • A foreign number ported in
  • A foreign number ported to foreign network
  • Foreign number not known to be ported

Because the existing EPAP portability does not support options for “Own number not ported out” and “Foreign number ported in”, this feature cannot distinguish between these two types of numbers that belong to own network. Using configured data, a best fit match will be made for returning number portability status (encoded value is in parentheses), as follows:

Table 2-4 Encoded Number Portability Status value

Encoded Number Portability Status value Criterion
Not Known To Be Ported (0)
  • MSISDN not found in the NPDB
  • MSISDN found with no entity and EPAP portability type (PT) provisioned as one of the following values:
    • 0 (NOT KNOWN TO BE PORTED)
    • 1 (OWN NUMBER PORTED OUT)
    • 2 (FOREIGN NUMBER PORTED TO FOREIGN NETWORK)
    • 36 (NOT IDENTIFIED TO BE PORTED)
    • 0xFF (none - NO STATUS)
  • MSISDN and Entity found in RTDB with Entity type = RN, PT = 0,S-Port is not enabled,andIGM feature is OFF.
  • MSISDN and Entity found in RTDB with Entity type = RN, and PT=0xFF (none - NO STATUS) or PT=36 (Not identified to be ported).

Note: This says that if a routing number was not found in RTDB (no Entity) then the MNP SRF cannot provide any useful information to the querying node about the network that owns this MSISDN. The querying node uses its available digits to route the call. PT=5 implies migrated customer (own network) and PT=3, 4, and 6-35 are prepaid servers that are also own subscribers.

Own Number Ported Out (1) MSISDN and Entity found in RTDB with Entity type=RN and PT=1 (OWN NUMBER PORTED OUT)
Foreign Number Ported To Foreign Network (2) MSISDN and Entity found in RTDB with Entity type=RN and PT=2 (FOREIGN NUMBER PORTED TO FOREIGN NETWORK)
Own Number Not Ported Out (4)
  • MSISDN and Entity found in RTDB with Entity type other than RN. (Non-RN Entity type in general implies own subscriber).

    Note: The combinations of 1 RN and 1 VMS ID, and 1 RN and 1 GRN, are valid combinations for network entities. In this case, the Entity type is considered to be RN (presumably, our own network is providing voice mail support for a foreign number).

  • MSISDN found in RTDB with no Entity and PT=Migrated (5)
  • MSISDN found in RTDB with no Entity but PT=Prepaid (3, 4, 6-35).
  • MSISDN and Entity found in RTDB with Entity type=RN, PT=0, andS-Port is enabledor IGM feature is turned ON (migrated subscriber is considered own subscriber).
  • MSISDN and Entity found in RTDB with Entity type=RN, and PT=5 (migrated) or PT=Prepaid (3,4,6-35).
Foreign Number Ported In (5) Not Supported. (Imported) Numbers that meet criteria for "Own Number Not Ported Out" have portability status value of 4.

ATINP Error Response MSU Encoding

The EAGLE can return any of the following error messages after processing an ATI message:

  • Return Error

    A response message with a Return Error component is referred to as an ATI NACK message or Return Error message. A Return Error component is used for the receipt of an ATI message when the ATINP feature is turned off (ATINP must be enabled – if ATINP is disabled, the message will not reach the subsystem), for ATI lookup problems, and for some decoding issues.

    Refer to 3GPP TS 29.002 version 6.15.0, ETSI TS 129 002 V6.15.0 (2005-12), Digital Cellular Telecommunications System (Phase2+); Mobile Application Part (MAP ) Specification .

  • Reject

    Reject messages are used for decoding errors in the Component portion of the original MSU.

  • U-Abort

    U-Abort messages are used for decode errors in the Dialog or Component portion of the original MSU.

  • P-Abort

    P-Abort messages are used for certain errors detected during decode of the Transaction portion of the original MSU.

Reject, P-Abort, and U-Abort error codes are described in ITU-T Recommendation Q.773, Transaction Capabilities Formats and Encoding.

Hardware Requirements

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.

MPS/EPAP Platform

Oracle provides the Multi-Purpose Server (MPS) platform as a subsystem of the Oracle Communications EAGLE. The MPS provides support for EPAP-related features that perform Real Time Database (RTDB) lookups.

The MPS is composed of hardware and software components that interact to create a secure and reliable platform. For details about the MPS hardware, refer to Application B Card Hardware and Installation Guide. The MPS provides the means of connecting the customer provisioning application with the EAGLE and accepts the customer number portability data, while accommodating numbers of varying lengths.

The Oracle Communications EAGLE Application Processor (EPAP) is software that runs on the MPS hardware platform. EPAP collects and organizes customer provisioning data, and forwards the data to the EAGLE Service Module cards. For detailed information about EPAP, refer to Administration Guide for EPAP.

In this manual, Service Module card refers to an E5-SM4G, E5-SM8G-B, or SLIC card unless a specific card is required. For more information about the supported cards, refer to Hardware Reference.